# US 2023/0069669 A1 · Methods, devices, and medium for communication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0069669 A1
- Document ID: US20230069669A1
- Status: Published application
- Kind: A1
- Application number: 17/793,706
- Filed: 2020-01-22
- Published: 2023-03-02
- Earliest claimed: 2020-01-22
- Assignees: NEC Corporation
- Applicants: NEC Corporation
- Inventors: Gang WANG
- Web page: https://patentgrep.com/patent/US20230069669A1

## CPC

- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 48/20: Selecting an access point
- H04W 8/08: Mobility data transfer
- H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 92/20: between access points
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Embodiments of the present disclosure relate to methods, devices, and medium for communication. A method for communication comprises in accordance with a determination that a terminal device in an inactive state requests a first network device for a transmission of uplink data, determining whether to relocate an anchor for a context of the terminal device from a second network device to the first network device, the second network device maintaining the context of the terminal device. The method further comprises in accordance with a determination of non-relocation of the anchor for the context of the terminal device, causing the uplink data to be forwarded to a destination via the second network device based on the maintained context of the terminal device.

## Claims

### Claim at position 1

1-24. (canceled).

### Claim 25

A method performed by a second network device, the method comprising:
receiving, from a first network device, a request message regarding a transaction of Small Data Transmission (SDT) of a User Equipment (UE) in an inactive state;
determining not to relocate a context of the UE from the second network device; and
transmitting to the first network device, User Plane (UP) Transport Layer information indicating an address for uplink (UL) data of the SDT on an Xn user plane interface between the first network device and the second network device;
receiving the UL data of the SDT on the Xn user plane interface from the first network device.

### Claim 26 (depends on 25)

The method of claim 25, further comprising:
delivering the UL data of the SDT to a core network.

### Claim 27 (depends on 25)

The method of claim 25, wherein the address is a destination address of the second network device.

### Claim 28 (depends on 25)

The method of claim 25, wherein the request message is a RETRIEVE UE CONTEXT REQUEST message.

### Claim 29 (depends on 25)

The method of claim 25, wherein the request message comprises first information indicating a quantitative value of the UL data of the SDT, and the first network device determines not to relocate the context of the UE from the second network device, based on the request message.

### Claim 30 (depends on 25)

The method of claim 25, further comprising:
receiving a control message containing UL data of the SDT from the first network device.

### Claim 31 (depends on 25)

The method of claim 25, wherein a Radio Link Control (RLC) entity related to the SDT is established at the first network device, and a Packet Data Convergence Protocol (PDCP) entity is kept at the second network device.

### Claim 32 (depends on 25)

The method of claim 25, wherein the UL data of the SDT is received in a form of Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU).

### Claim 33 (depends on 25)

The method of claim 25, further comprising:
receiving, from the first network device, second information indicating an address for downlink (DL) data of the SDT on the Xn user plane interface between the first network device and the second network device.

### Claim 34 (depends on 33)

The method of claim 33, further comprising:
receiving the DL data of the SDT from a core network; and
transferring the DL data of the SDT to the first network device.

### Claim 35 (depends on 33)

The method of claim 33, further comprising:
transmitting a Radio Resource Control (RRC) transfer message containing DL control data of the SDT to the first network device.

### Claim 36 (depends on 25)

The method of claim 25, further comprising:
transmitting, to the first network device, a message including a Radio Resource Control (RRC) Release message encapsulated therein, wherein the RRC Release message includes indication for the UE to be in the inactive state.

### Claim 37

A method performed by a User Equipment (UE), the method comprising:
transmitting, to a first network device, uplink (UL) data of Small Data
Transmission (SDT), while remaining in an inactive state; wherein,
a request message regarding a transaction of the SDT is transmitted from the first network device to a second network device,
a context of the UE is determined not to be relocated from the second
network device,
User Plane (UP) Transport Layer information indicating an address for the UL data of the SDT on an Xn user plane interface between the first network device and the second network device is transmitted from the second network device to the first network device, and
the UL data of the SDT is received by the second network device on the Xn user plane interface from the first network device.

### Claim 38 (depends on 37)

The method of claim 37, further comprising:
receiving, from the first network device, a Radio Resource Control (RRC) Release message, wherein,
the RRC Release message includes indication for the UE to be in the inactive state, and
a message including the RRC Release message encapsulated therein, is transmitted from the second network device to the first network device.

### Claim 39

A second network device comprising:
a memory configured to store instructions: and
a processor configured to execute the instructions to:
receive, from a first network device, a request message regarding a transaction of Small Data Transmission (SDT) of a User Equipment (UE) in an inactive state;
determine not to relocate a context of the UE from the second network device; and
transmit to the first network device, User Plane (UP) Transport Layer information indicating an address for uplink (UL) data of the SDT on an Xn user plane interface between the first network device and the second network device;
receive the UL data of the SDT on the Xn user plane interface from the first network device.

### Claim 40 (depends on 39)

The second network device of claim 39, wherein the processor is further configured to execute the instructions to:
deliver the UL data of the SDT to a core network.

### Claim 41 (depends on 39)

The second network device of claim 39, wherein the address is a destination address of the second network device.

### Claim 42 (depends on 39)

The second network device of claim 39, wherein the request message is a RETRIEVE UE CONTEXT REQUEST message.

### Claim 43 (depends on 39)

The second network device of claim 39, wherein the request message comprises first information indicating a quantitative value of the UL data of the SDT, and the first network device determines not to relocate the context of the UE from the second network device, based on the request message.

### Claim 44 (depends on 39)

The second network device of claim 39, wherein the processor is further configured to execute the instructions to:
receive a control message containing UL data of the SDT from the first network device.
