RAN node and method performed by the RAN node
By employing differentiated control messages for RAN nodes based on uplink data presence, the mechanism facilitates efficient uplink data transmission to the core network without relocating the UE context, addressing limitations in existing RRC_INACTIVE state technologies.
Patent Information
- Application Number
- JP2023059768
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-02-13
- Filing Date
- 2023-04-03
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-11-30
AI Technical Summary
Existing technologies in RRC_INACTIVE state do not allow for uplink data transmission to the core network without relocating the UE context from the old RAN node to the new RAN node, limiting efficient data transmission capabilities.
Implementing a mechanism where RAN nodes send different types of control messages based on the presence of uplink data with the RRC resume request, allowing the new RAN node to request the UE context from the old node or directly transmit data without context relocation, using enhanced XnAP messages to facilitate efficient data transfer.
Enables uplink data transmission to the core network without relocating the UE context, enhancing data transmission efficiency and reducing network latency in RRC_INACTIVE state.
Smart Images

Figure 0007586218000001 
Figure 0007586218000002 
Figure 0007586218000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to wireless communication networks, and more particularly to data transmission for wireless terminals in a Radio Resource Control (RRC)_INACTIVE state. [Background technology]
[0002] The 3rd Generation Partnership Project (3GPP) will begin discussions on Release 17 in the first quarter of 2020. Release 17 is scheduled to support small data transmission in RRC_INACTIVE (see Non-Patent Document 1). One of the objectives is to enable small data transmission in RRC_INACTIVE without anchor relocation, i.e., without relocation of the UE context from an Old Radio Access Network (RAN) node (last serving RAN node) to a New RAN node.
[0003] 3GPP Release 15 already supports early data transmission (EDT) for Long Term Evolution category M (LTE-M) devices and Narrow Band Internet of Things (NB-IoT) devices. EDT technologies include control-plane EDT (CP-EDT) and user-plane EDT (UP-EDT). One of the main concepts of EDT is that uplink (UL) data and downlink (DL) data are transmitted early in a contention-based random access procedure. Specifically, EDT allows UL data and DL data to be transmitted in the third message (Msg3) and fourth message (Msg4) of the random access procedure, respectively.
[0004] In UP-EDT, a radio terminal (User Equipment (UE)) that is RRC_INACTIVE transmits UL data to the base station (eNB) together with an RRC Connection Resume Request message in the third step of the contention-based random access procedure. Upon receiving the RRC Connection Resume Request message, the new eNB obtains the UE context from the old eNB (i.e., the last serving eNB) and requests a path switch from the Mobility Management Entity (MME). This causes the MME to change the path of the UE's Evolved Packet System (EPS) bearer from the old eNB to the new eNB. The new eNB transmits the UL data directly to the Serving Gateway (S-GW) via the modified EPS bearer (i.e., modified S1-U bearer). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] ZTE Corporation, "Work Item on NR small data transmissions in INACTIVE state", RP-193252, 3GPP TSG RAN Meeting #86, Sitges, Spain, December 9-12, 2019 Summary of the Invention [Problem to be solved by the invention]
[0006] The inventors have investigated small data transmission in RRC_INACTIVE and found various problems. One problem is that in the UP-EDT introduced in the above-mentioned Release 15, UL data cannot be transmitted to the core network without relocation of the UE context from the old eNB (last serving eNB) to the new eNB.
[0007] One of the objectives to be achieved by the embodiments disclosed herein is to provide an apparatus, a method, and a program that contribute to enabling UL data of a radio terminal in an RRC_INACTIVE state to be transmitted to a core network without relocation of the radio terminal context from an old RAN node (closest serving RAN node) to a new RAN node. Note that this objective is only one of the objectives to be achieved by the embodiments disclosed herein. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]
[0008] In a first aspect, a first Radio Access Network (RAN) node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to receive an RRC resume request message without uplink data from a radio terminal in a Radio Resource Control (RRC)_INACTIVE state and, when a radio terminal context of the radio terminal is not available in the first RAN node, send a first type control message requesting the radio terminal context to a second RAN node that is a closest serving RAN node of the radio terminal, the second RAN node being a closest serving RAN node of the radio terminal, the at least one processor further configured to receive the uplink data from the radio terminal in the RRC_INACTIVE state together with the RRC resume request message and, when the radio terminal context is not available in the first RAN node, send a second type control message requesting the radio terminal context and distinguished from the first type control message to the second RAN node.
[0009] In a second aspect, a second Radio Access Network (RAN) node includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to maintain a radio terminal context for a radio terminal in a Radio Resource Control (RRC)_INACTIVE state, the at least one processor configured to receive a control message from a first RAN node requesting the radio terminal context, and the at least one processor configured to determine whether the control message is of a specific type used when the first RAN node receives uplink data from the radio terminal in the RRC_INACTIVE state together with an RRC resume request message.
[0010] In a third aspect, a wireless terminal includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor configured to transmit uplink data and type information indicating a type of data activity with an RRC resume request message to a Radio Access Network (RAN) node when the wireless terminal is in a Radio Resource Control (RRC)_INACTIVE state.
[0011] In a fourth aspect, a method performed by a first Radio Access Network (RAN) node includes the following steps: (a) when receiving an RRC resumption request message without uplink data from a wireless terminal in a Radio Resource Control (RRC)_INACTIVE state and a radio terminal context of the wireless terminal is not available in the first RAN node, sending a first type control message requesting the radio terminal context to a second RAN node that is a proximate serving RAN node of the wireless terminal; and (b) receiving the uplink data from the radio terminal in the RRC_INACTIVE state together with the RRC resume request message and, if the radio terminal context is not available in the first RAN node, sending a second type control message to the second RAN node requesting the radio terminal context and distinguished from the first type control message.
[0012] In a fifth aspect, a method performed by a second Radio Access Network (RAN) node includes the steps of: (a) maintaining a radio terminal context of a radio terminal in a Radio Resource Control (RRC)_INACTIVE state; (b) receiving a control message from a first RAN node requesting the radio terminal context; and (c) determining whether the control message is of a specific type that is used when the first RAN node receives uplink data from the wireless terminal in the RRC_INACTIVE state together with an RRC resumption request message;
[0013] In a sixth aspect, a method performed by a wireless terminal includes, when the wireless terminal is in a Radio Resource Control (RRC)_INACTIVE state, sending uplink data and type information indicating a type of data activity together with an RRC resume request message to a Radio Access Network (RAN) node.
[0014] In a seventh aspect, a program comprises instructions (software code) which, when loaded into a computer, causes the computer to carry out a method according to the fourth, fifth or sixth aspect above. Effect of the Invention
[0015] According to the above-described aspects, it is possible to provide an apparatus, a method, and a program that contribute to enabling UL data of a radio terminal that is RRC_INACTIVE to be transmitted to a core network without relocation of the radio terminal context from an old RAN node (the closest serving RAN node) to a new RAN node. [Brief description of the drawings]
[0016] [Figure 1] 1 is a diagram illustrating an example of the configuration of a wireless communication network according to an embodiment. [Figure 2A] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 2B] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Diagram 3]A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 4] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Diagram 5] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 6] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 7] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 8] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 9] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 10] A sequence diagram showing an example of operations performed by a new gNB, an old gNB, and a UE according to an embodiment. [Figure 11] 1 is a diagram illustrating an example of the configuration of a wireless communication network according to an embodiment. [Figure 12] A sequence diagram showing an example of an operation performed by a new gNB and a UE according to an embodiment. [Figure 13] A block diagram showing an example configuration of a gNB according to an embodiment. [Figure 14] FIG. 2 is a block diagram showing an example of the configuration of a UE according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.
[0018] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different objects or problems and provide different effects.
[0019] The following embodiments are described with a focus on the 3rd Generation Partnership Project (3GPP) 5th generation mobile communication system (5G system (5GS)). However, these embodiments may be applied to other cellular communication systems that support small data transmission in RRC_INACTIVE.
[0020] <First embodiment> FIG. 1 illustrates an example of a wireless communication network (i.e., 5GS) according to some embodiments including the present embodiment. In the example of FIG. 1, the wireless communication network includes two Radio Access Network (RAN) nodes (i.e., gNBs) 1 and 2 and a wireless terminal (i.e., UE) 3. As described in detail below, the UE 3 can access the gNB 1 via an air interface 101 to perform small data transmission in RRC_INACTIVE, and the gNB 1 communicates with a gNB 2 having a UE context of the UE 3 in RRC_INACTIVE via a node-to-node interface 102. Therefore, in the following, the gNB 1 is referred to as a new gNB, and the gNB 2 is referred to as an old gNB or last serving gNB. The old gNB can also be expressed as a serving RAN node immediately prior to the UE 3.
[0021] The inter-node interface 102 between new gNB1 and old gNB2 is an Xn interface. The Xn interface includes a control plane interface (i.e., Xn-C interface) and a user plane interface (i.e., Xn-U interface). The Xn-C interface supports the Xn Application Protocol (XnAP) for signaling procedures. Meanwhile, the Xn-U interface uses the General Packet Radio Service (GPRS) Tunnelling Protocol for User Plane (GTP-U) protocol. Specifically, the transport network layer (TNL) of the Xn-U interface is built on top of a User Datagram Protocol (UDP) / Internet Protocol (IP) network and uses the GTP-U protocol on top of the UDP / IP protocol.
[0022] The UE 3 can initiate an RRC Resume procedure to transition from the RRC_INACTIVE state back to the RRC_CONNECTED state and to inform the NG-RAN of RAN Notification Area (RNA) updates. As is well known, the RRC_INACTIVE state can be said to be an intermediate state between the RRC_CONNETED and RRC_IDLE states. Some characteristics of the RRC_INACTIVE state are similar to those of the RRC_CONNETED state, while some other characteristics of the RRC_INACTIVE state are similar to those of the RRC_IDLE state.
[0023] More specifically, when UE3 is in RRC_INACTIVE state, UE3 and Next Generation (NG)-RAN (including gNBs1 and 2) maintain UE (Access Stratum (AS)) context. The UE (AS) context maintained for UE3 in RRC_INACTIVE state includes, for example, radio bearer configuration and AS security context. In addition, NG-RAN maintains control plane and user plane connections with the core network (i.e., 5G Core Network (5GC)) for UE3 in RRC_INACTIVE state. The 5GS Connection Management (CM) state in UE3 and 5GC (i.e., Access and Mobility Management Function (AMF)) for UE3 in RRC_INACTIVE state is CM-CONNECTED state. That is, 5GC does not distinguish whether UE3 is in RRC_CONNECTED state or RRC_INACTIVE state. These characteristics of RRC_INACTIVE state are similar to those of RRC_CONNETED state.
[0024] However, the mobility of a UE 3 in the RRC_INACTIVE state is similar to that of a UE 3 in the RRC_IDLE state. That is, the mobility of a UE 3 in the RRC_INACTIVE state is handled by cell reselection controlled by the UE 3. The location of a UE 3 in the RRC_INACTIVE state is known by the NG-RAN at the level of a RAN Notification Area (RNA). A RAN Notification Area (RNA) includes one or more cells, is determined by the NG-RAN, and is configured in the UE 3 by the NG-RAN. A UE 3 in the RRC_INACTIVE state does not need to notify (report) the cell reselection to the NG-RAN even if it moves between cells by cell reselection within the RAN notification area. When a UE 3 in the RRC_INACTIVE state reselects a cell outside the configured RNA or when a periodic RAN update is performed, the UE 3 initiates an RRC Resume procedure and requests a RAN notification area update from the NG-RAN.
[0025] Next, small data transmission in RRC_INACTIVE according to this embodiment will be described below. In this embodiment, the new gNB1 sends different types of control messages to the old gNB (last serving gNB)2 depending on whether or not it has received UL data from the UE3 in RRC_INACTIVE together with an RRC (connection) resume request message (e.g., an RRC Resume Request message).
[0026] More specifically, as shown in Figure 2A, when new gNB1 receives an RRC Resume Request message without UL data from UE3 that is RRC_INACTIVE (step 201) and the UE context of UE3 is not available in new gNB1, new gNB1 sends a first type control message to old gNB2 (step 202). The first type control message requests old gNB2 to provide the UE context of UE3.
[0027] In contrast, as shown in Fig. 2B, when new gNB1 receives UL data from UE3 in RRC_INACTIVE with an RRC Resume Request message (step 221) and the UE context of UE3 is not available in new gNB1, new gNB1 sends a second type control message to old gNB2 (step 222). The second type control message, like the first type control message, requests old gNB2 to provide the UE context of UE3. However, the second type control message is distinguished from the first type control message by new gNB1 and old gNB2.
[0028] In some implementations, the second type control message may be distinguished from the first type control message by the second type control message including an indication that directly or indirectly indicates the presence of UL data. More specifically, the first type control message may be similar to the existing XnAP: RETRIEVE UE CONTEXT REQUEST message. Meanwhile, the second type control message may be an improved RETRIEVE UE CONTEXT REQUEST message including a new Information Element (IE) or a new cause value that directly or indirectly indicates the presence of UL data. The indication that directly or indirectly indicates the presence of UL data may be, for example, a new IE indicating that (small) data is available (e.g., (small) data available) or a new cause value indicating that (small) data should be forwarded (e.g., (small) data to be forwarded). Alternatively, the second type control message may be a newly defined XnAP message that includes information of the RETRIEVE UE CONTEXT REQUEST message but is different from it. When the new gNB1 receives UL data from the UE3 in RRC_INACTIVE, the new gNB1 may use the new XnAP message to inform the old gNB2 of the presence of the UL data. The new XnAP message may be called, for example, a RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message or a DATA TRANSFER REQUEST message.
[0029] Additionally or alternatively, in some implementations, the second type control message may be distinguished from the first type control message by including an indication that the second type control message represents a request for transport network layer (TNL) information of the old gNB2. The TNL information may be referred to as transport layer information. More specifically, the first type control message may be similar to an existing XnAP: RETRIEVE UE CONTEXT REQUEST message. Meanwhile, the second type control message may be an improved RETRIEVE UE CONTEXT REQUEST message including a new information element (IE) or a new cause value representing a request for TNL information of the old gNB2. Alternatively, the second type control message may be a newly defined XnAP message that includes information of the RETRIEVE UE CONTEXT REQUEST message but is different from it. The new gNB1 may use the new XnAP message to request the TNL information of the old gNB2 when it receives UL data from the UE3 in RRC_INACTIVE. The new XnAP message may be called, for example, a RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message or a DATA TRANSFER REQUEST message.
[0030] The TNL information (or transport layer information) of the old gNB2 can also be referred to as the TNL address (or transport layer address) of the old gNB2. The TNL information or TNL address of the old gNB2 is used by the new gNB1 to send UL data from the new gNB1 to the old gNB2 via the user plane interface (i.e., Xn-U interface). Thus, the TNL information or TNL address of the old gNB2 may be a combination of the Tunnel Endpoint Identifier (TEID) indicating the endpoint of the GTP-U tunnel on the old gNB2 side and the IP address of the old gNB2. The IP address of the old gNB2 used to forward GTP-U / UDP / IP packets on the Xn-U interface (GTP-U tunnel) may be the same as or different from the IP address of the old gNB2 used to forward XnAP / Stream Control Transmission Protocol (SCTP) / IP packets on the Xn-C interface (XnAP protocol).
[0031] Additionally or alternatively, in some implementations, the second type control message may be distinguished from the first type control message by the second type control message including UL data (i.e., Dedicated Traffic Channel (DTCH) data) itself. More specifically, the first type control message may be similar to the existing XnAP: RETRIEVE UE CONTEXT REQUEST message. Meanwhile, the second type control message may be a RETRIEVE UE CONTEXT REQUEST message that is modified to piggyback the UL data (i.e., DTCH data). Alternatively, the second type control message may be a newly defined XnAP message that includes information of the RETRIEVE UE CONTEXT REQUEST message but is different from it. When the New gNB1 receives UL data from the UE3 in RRC_INACTIVE, the New gNB1 may use the new XnAP message to forward the UL data to the old gNB2. The new XnAP message may be called, for example, a RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message or a DATA TRANSFER REQUEST message. The New gNB1 may include additional information required for identifying or deciphering the UL data of the UE3 in the second type control message. The additional information may include one or both of a Data Radio Bearer (DRB) ID and a Logical Chanel ID (LCID).
[0032] The old gNB2 receives a control message (step 202 or 222) from the new gNB1 requesting a UE context for the UE3 that is RRC_INACTIVE. The old gNB2 then determines whether the received control message is of the first type or the second type. In other words, the old gNB2 identifies the type of the received control message. The old gNB2 may take different actions depending on the type of the received control message.
[0033] In some implementations, if the control message received from the new gNB1 is of the second type, the old gNB2 may operate to allow UL data of the UE3 to be transmitted to the core network (5GC) via the old gNB2 without providing the UE context of the UE3 to the new gNB1. More specifically, the old gNB2 may send an XnAP message (e.g., a RETRIEVE UE CONTEXT FAILURE message) indicating that the UE context of the UE3 is not relocated to the new gNB1. The XnAP message may include the TNL information of the old gNB2. That is, the XnAP message may indicate permission for UL data transfer via the old gNB2. Alternatively, the old gNB2 may send a message (e.g., an XN-U ADDRESS INDICATION message) indicating the TNL information of the old gNB2 to the new gNB1 separately from the XnAP message (e.g., a RETRIEVE UE CONTEXT FAILURE message) indicating that the UE context of the UE3 is not relocated. In response to receiving the XnAP message, the new gNB1 transmits the UL data of the UE3 to the old gNB2 via the Xn-U interface (i.e., GTP-U tunnel). The old gNB2 then extracts the IP data (i.e., one or more IP packets) by ciphering the UL data (i.e., DTCH data) received from the new gNB1. The old gNB2 then transmits the IP data to a core network node (i.e., User Plane Function (UPF) in the 5GC) via a user plane connection (i.e., N3 GTP-U tunnel) with the core network maintained for the RRC_INACTIVE UE3.
[0034] Additionally or alternatively, if the control message received from the new gNB1 is of the second type, the old gNB2 may determine whether to transmit UL data of the UE3, which is RRC_INACTIVE, to the core network (5GC) via the old gNB2. In response to the decision to transmit the UL data via the old gNB2, the old gNB2 may operate as described above. On the other hand, in response to the decision not to transmit the UL data via the old gNB2, the old gNB2 may provide the UE context of the UE3 to the new gNB1. In this case, the new gNB1 may receive the UE context of the UE3 from the old gNB2, decode the UL data of the UE3 using the UE context to extract IP data, and transmit the data directly (i.e., not via the old gNB2) to a core network node (i.e., User Plane Function (UPF) in the 5GC).
[0035] As can be understood from the above description, in this embodiment, the new gNB1 sends different types of messages to the old gNB2 (last serving gNB)2 depending on whether it receives UL data from the UE3 that is RRC_INACTIVE together with an RRC (connection) resume request message (e.g., an RRC Resume Request message). When the new gNB1 receives an RRC Resume Request message without UL data from the UE3 that is RRC_INACTIVE (step 201) and the UE context of the UE3 is not available in the new gNB1, it sends a first type of control message to the old gNB2 (step 202). The first type of control message requests the old gNB2 to provide the UE context of the UE3. In response, when the new gNB1 receives UL data from the UE3 that is RRC_INACTIVE together with an RRC Resume Request message (step 221) and the UE context of the UE3 is not available in the new gNB1, it sends a second type of control message to the old gNB2 (step 222). The second type control message, like the first type control message, requests the old gNB2 to provide the UE context of the UE3. However, the second type control message is distinguished from the first type control message by the new gNB1 and the old gNB2. The old gNB2 then determines whether the received control message is the first type or the second type. This allows the new gNB1 to inform the old gNB2 that there is UL data from the UE3 that is RRC_INACTIVE, and the old gNB2 can operate to enable the UL data to be transmitted to the core network via the old gNB2. Therefore, the present embodiment contributes to enabling the UL data of the UE3 that is RRC_INACTIVE to be transmitted to the core network without relocation of the UE context from the old gNB2 to the new gNB1.
[0036] <Second embodiment> This embodiment provides a specific example of data transmission in RRC_INACTIVE described in the first embodiment. A configuration example of a wireless communication network according to this embodiment is similar to the example shown in FIG.
[0037] FIG. 3 shows a first example of data transmission in RRC_INACTIVE according to the present embodiment. In step 301, UE3 in RRC_INACTIVE transmits UL data (i.e., DTCH data) to new gNB1 together with an RRC Resume Request message (i.e., Common Control Channel (CCCH) data). More specifically, when UE3 receives an RRC Release message including information (SuspendConfig IE) indicating an instruction to move from RRC_CONNECTED to RRC_INACTIVE from old gNB2 (which is an old gNB but is the serving gNB at the time of receiving the RRC Release message), UE3 holds configuration information (e.g., UE context) required to transmit the UL data in the RRC Resume Request message and uses it in step 301. The RRC Resume Request message and UL data may be transmitted in a third message of a 4-Step Contention Based Random Access (CBRA) procedure. Alternatively, the RRC Resume Request message and the UL data may be sent in the first message (Message A (MsgA)) of the Two-Step Contention Based Random Access (2-Step CBRA) procedure.
[0038] More specifically, in some implementations, the new gNB1 sends an UL resource grant for the transmission of an RRC Resume Request message (CCCH data) and a third message with the required transport block size (TBS) to transmit UL data (DTCH data) to the UE3 via the second message (Random Access Response) of the four-step random access procedure. Then, the RRC layer of the UE3 resumes all signaling radio bearers (SRBs) and data radio bearers (DRBs), derives new security keys, and re-establishes Access Stratum (AS) security. Meanwhile, in the User Plane (UP) protocol of the UE3, the Service Data Adaptation Protocol (SDAP) layer of the UE3 generates SDAP data from IP data (QoS flows) and passes it to the Packet Data Convergence Protocol (PDCP) layer. Then, the PDCP layer of the UE3 ciphers the SDAP data, generates PDCP data, and passes it to the Radio Link Control (RLC) layer of the UE3. The RLC layer of the UE3 generates RLC data (also called DTCH data) from the PDCP data, and passes it to the Medium Access Control (MAC) layer of the UE3. Then, the MAC layer of the UE3 multiplexes the MAC sub-Protocol Data Unit (PDU) containing the RRC Resume Request message (CCCH data) and the MAC sub-PDU containing the UL data (DTCH data) into one uplink MAC PDU. The Medium Access Control (MAC) layer of the UE3 transmits the uplink MAC PDU (transport block) in the Uplink Shared Channel (UL-SCH) resources allocated in the second message.New gNB1 extracts the RRC Resume Request message (CCCH data) and UL data (DTCH data) from the received uplink MAC PDU.
[0039] The DRBs that the UE3 resumes may be only the DRB(s) for which the old gNB2 has permitted data transmission in the RRC Resume of the UE3 in the RRC Release message. The SDAP layer of the UE3 may pass SDAP data to the PDCP layer based on the correspondence between the IP data (QoS flow) and the DRB (QoS flow to DRB mapping rule) that was used at the time when the UE3 entered the RRC_INACTIVE state. Additionally or alternatively, the PDCP layer of the UE3 may pass PDCP data to the RLC layer without encrypting the SDAP data. Furthermore, the RLC layer of the UE3 may pass PDCP data to the MAC layer as it is as RLC data (DTCH data) in Transparent Mode (TM).
[0040] Alternatively, the MAC layer of the UE3 may generate a first uplink MAC PDU including an RRC Resume Request message (CCCH data) and a second uplink MAC PDU including UL data (DTCH data), and transmit these two MAC PDUs in sequence on UL-SCH resources that are consecutive in time. The RRC Resume Request message may include information indicating that the UL data is transmitted successively. These resources may also be specified by the new gNB1 via a second message of the 4-Step Random Access (4-Step RA) procedure. If the 2-Step Random Access (2-Step RA) procedure is used, the UE3 may transmit these two MAC PDUs on the resources of the first message (MsgA) that are predefined. The new gNB1 may first receive the first uplink MAC PDU, recognize that the second uplink MAC PDU should be received consecutively from the first uplink MAC PDU, and further receive the second uplink MAC PDU. The new gNB1 extracts the RRC Resume Request message (CCCH data) from the first received uplink MAC PDU and extracts the UL data (DTCH data) from the second received uplink MAC PDU. In this case, the new gNB1 may send a second type control message to the old gNB2 when it receives UL data from the UE3 that is RRC_INACTIVE following the RRC Resume Request message and the UE context of the UE3 is not available in the new gNB1.
[0041] In step 302, in response to receiving the UL data with the RRC Resume Request message, the new gNB1 sends a second type control message to the old gNB2. More specifically, in the example of Fig. 3, the new gNB1 sends an improved RETRIEVE UE CONTEXT REQUEST message that includes a new IE or a new cause value (e.g., TNL INFORMATION REQUEST) indicating a request for TNL information of the old gNB2.
[0042] The old gNB2 detects that the received RETRIEVE UE CONTEXT REQUEST message includes an IE or a cause value indicating a request for TNL information of the old gNB2. Then, the old gNB2 decides not to relocate the UE context of the UE3 to the new gNB1. In step 303, the old gNB2 sends a RETRIEVE UE CONTEXT FAILURE message. The RETRIEVE UE CONTEXT FAILURE message includes an IE indicating the TNL information (e.g., TEID and IP address) of the old gNB2. Furthermore, the RETRIEVE UE CONTEXT FAILURE message includes an RRC Release message to be sent to the UE3. The RRC Release message is encapsulated in an Old NG-RAN node To New NG-RAN node Resume Container IE in the RETRIEVE UE CONTEXT FAILURE message. Additionally, the RETRIEVE UE CONTEXT FAILURE message may include a cause value indicating that the UE context is not relocated (e.g., Non-relocation of context). Alternatively, the RETRIEVE UE CONTEXT FAILURE message may include a cause value indicating data transfer without UE context relocation (e.g., Data transfer without context relocation).
[0043] In step 304, the new gNB1 transmits UL data (DTCH data) of the UE3 to the TNL address received in step 303. The old gNB2 extracts IP data (i.e., one or more IP packets) by performing ciphering on the UL data (i.e., DTCH data) received from the new gNB1. More specifically, the old gNB2 extracts an SDAP PDU from the decoded PDCP Service Data Unit (SDU). Then, based on the QoS flow and DRB mapping rule assigned to the UE3 that was stored, the old gNB2 extracts the SDAP SDU corresponding to the QoS flow and replaces it with IP data. Furthermore, the old gNB2 transmits the IP data to a core network node (i.e., User Plane Function (UPF) in the 5GC) via a user plane connection (i.e., N3 GTP-U tunnel) with the core network maintained for the UE3 that is RRC_INACTIVE.
[0044] In step 305, the new gNB1 forwards the RRC Release message received in step 303 to the UE3. The new gNB1 may transmit the RRC Release message in the fourth message (Msg4) of the four-step random access procedure. Alternatively, the new gNB1 may transmit the RRC Release message in the second message (message B (MsgB)) of the two-step random access procedure. In this case, the second message (MsgB) may include information for contention resolution (Contention Resolution MAC Control Element (CE)) and the RRC Release message. In response to receiving the RRC Release message, the UE3 remains in the RRC_INACTIVE state. This allows the UE3 to transmit UL data without moving from the RRC_INACTIVE state to the RRC_CONNECTED state.
[0045] The procedure of Fig. 3 may be modified as appropriate. For example, if the new gNB1 already knows the TNL address of the old gNB2, the new gNB1 may transmit the UL data of the UE3 to the old gNB2 on the Xn-U interface before receiving the RETRIEVE UE CONTEXT FAILURE message in step 303. For example, the new gNB1 may transmit the UL data of the UE3 on the Xn-U interface immediately after transmitting the RETRIEVE UE CONTEXT REQUEST message on the Xn-C interface in step 303. Alternatively, the new gNB1 may transmit the UL data of the UE3 on the Xn-U interface substantially simultaneously with transmitting the RETRIEVE UE CONTEXT REQUEST message on the Xn-C interface in step 303. This allows the UL data to be transmitted earlier.
[0046] Notification of the TNL address of the old gNB2 may be sent from the old gNB2 to the new gNB1 via another XnAP message independent of the RETRIEVE UE CONTEXT FAILURE message of step 303. The XnAP message may be an XN-U ADDRESS INDICATION message. The XnAP message (e.g., XN-U ADDRESS INDICATION message) may be sent prior to the RETRIEVE UE CONTEXT FAILURE message of step 303.
[0047] Fig. 4 shows a second example of data transmission in RRC_INACTIVE according to this embodiment. Steps 401 to 405 in Fig. 4 are basically the same as steps 301 to 305 in Fig. 3. However, the RETRIEVE UE CONTEXT REQUEST message in step 402 includes a new IE (e.g., UL DATA INDICATION) indicating the presence of UL data or a new cause value (e.g., Data available for transfer). The RETRIEVE UE CONTEXT FAILURE message in step 403 includes a cause value (e.g., Data transfer without context relocation) indicating data transfer without UE context relocation. The RETRIEVE UE CONTEXT FAILURE message may include an IE indicating TNL information of the old gNB2.
[0048] Figure 5 shows a third example of data transmission in RRC_INACTIVE according to this embodiment. As already described with reference to Figure 3, if new gNB1 already knows the TNL address of old gNB2, new gNB1 may transmit UL data of UE3 early, before receiving RETRIEVE UE CONTEXT FAILURE message (step 303). In the example of Figure 5, new gNB1 transmits UL data to old gNB2 (step 503) after transmitting RETRIEVE UE CONTEXT REQUEST message (step 502). Steps 501, 502, 504, and 505 are similar to the corresponding steps in Figure 3 or Figure 4.
[0049] Figure 6 shows a fourth example of data transmission in RRC_INACTIVE according to this embodiment. Step 601 is the same as step 301 in Figure 3, step 401 in Figure 4, and step 501 in Figure 5. In step 602, new gNB1 sends a newly defined XnAP message to old gNB2 that includes information of the existing RETRIEVE UE CONTEXT REQUEST message but is different from the existing RETRIEVE UE CONTEXT REQUEST message. The new XnAP message may be a RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message as shown in Figure 6.
[0050] As already explained with reference to Fig. 3, notification of the TNL address of the old gNB2 may be sent from the old gNB2 to the new gNB1 via another XnAP message independent of the RETRIEVE UE CONTEXT FAILURE message (step 303). In the example of Fig. 6, after receiving the RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message (step 602), the old gNB2 sends an XN-U ADDRESS INDICATION message to the new gNB1 (step 603). The XN-U ADDRESS INDICATION message indicates the TNL address (e.g., TEID and IP address) of the old gNB2. The old gNB2 then sends a RETRIEVE UE CONTEXT FAILURE FOR DATA TRANSFER message (step 605). After receiving UL data for UE3 from new gNB1 (step 604), old gNB2 may transmit a RETRIEVE UE CONTEXT FAILURE FOR DATA TRANSFER message (step 605). The RETRIEVE UE CONTEXT FAILURE FOR DATA TRANSFER message includes an RRC Release message to be transmitted to UE3. Similar to step 305 of FIG. 3, in step 606, new gNB1 forwards the RRC Release message received in step 605 to UE3. In response to receiving the RRC Release message, UE3 remains in RRC_INACTIVE state. This allows UE3 to transmit UL data without moving from RRC_INACTIVE state to RRC_CONNECTED state.
[0051] FIG. 7 shows a fifth example of data transmission in RRC_INACTIVE according to this embodiment. In the example of FIG. 7, DL data is transmitted in addition to UL data. Steps 701 to 704 are the same as, for example, steps 301 to 304 in FIG. 3 or steps 401 to 404 in FIG. 4. In step 705, the old gNB2 forwards the DL data of the UE3 to the new gNB1 via the Xn-U interface. To enable this, the RETRIEVE UE CONTEXT REQUEST message in step 702 may include an IE indicating the TNL information (e.g., TEID and IP address) of the new gNB1. The IP address of the new gNB1 used to forward GTP-U / UDP / IP packets related to the Xn-U interface (GTP-U tunnel) may be the same as or different from the IP address of the new gNB1 used to forward XnAP / SCTP / IP packets related to the Xn-C interface (XnAP protocol). The DL data transfer in step 705 may occur before the UL data transfer in step 704 or may occur in parallel with the UL data transfer in step 704 .
[0052] In step 706, the new gNB1 transmits the DL data received in step 705 to the UE3 together with the RRC Release message included in the RETRIEVE UE CONTEXT FAILURE message received in step 703. In response to receiving the RRC Release message, the UE3 remains in the RRC_INACTIVE state. This allows the UE3 to transmit UL data and receive DL data without transitioning from the RRC_INACTIVE state to the RRC_CONNECTED state.
[0053] The procedure in Fig. 7 may be modified as appropriate. For example, if new gNB1 already knows the TNL information of old gNB2, new gNB1 may transmit UL data of UE3 to old gNB2 over the Xn-U interface before receiving the RETRIEVE UE CONTEXT FAILURE message in step 703. Furthermore, if old gNB2 already knows the TNL information of new gNB1, old gNB2 may transmit DL data of UE3 to new gNB1 over the Xn-U interface before transmitting the RETRIEVE UE CONTEXT FAILURE message in step 703. Note that steps 704 and 705 may be performed before step 703.
[0054] Fig. 8 shows a sixth example of data transmission in RRC_INACTIVE according to this embodiment. In the example of Fig. 8, DL data transfer is added to the example shown in Fig. 6. Step 801 is the same as step 601 in Fig. 6. In step 802, a newly defined XnAP message that includes information of the existing RETRIEVE UE CONTEXT REQUEST message but is different from the existing RETRIEVE UE CONTEXT REQUEST message is sent to the old gNB2. The new XnAP message includes an IE indicating the TNL information of the new gNB1. The new XnAP message may be a RETRIEVE UE CONTEXT REQUEST FOR DATA TRANSFER message as shown in Fig. 8.
[0055] Step 803 is the same as step 603 in Figure 6. Step 804 is the same as step 604 in Figure 6. In step 805, the old gNB2 forwards DL data of the UE3 to the new gNB1 via the Xn-U interface. The DL data transfer in step 805 may be performed before the UL data transfer in step 804, or may be performed in parallel with the UL data transfer in step 804.
[0056] Step 806 is the same as step 605 in Fig. 6. In step 807, the new gNB1 forwards the RRC Release message received in step 806 via the RETRIEVE UE CONTEXT FAILURE FOR DATA TRANSFER message to the UE3. Furthermore, in step 807, the new gNB1 transmits the DL data received in step 805 together with the RRC Release message to the UE3. In response to receiving the RRC Release message, the UE3 remains in the RRC_INACTIVE state. This allows the UE3 to transmit UL data and receive DL data without moving from the RRC_INACTIVE state to the RRC_CONNECTED state.
[0057] <Third embodiment> This embodiment provides a specific example of data transmission in RRC_INACTIVE described in the first embodiment. A configuration example of a wireless communication network according to this embodiment is similar to the example shown in FIG.
[0058] FIG. 9 shows an example of data transmission in RRC_INACTIVE according to this embodiment. Step 901 is similar to step 301 in FIG. 3. In step 902, in response to receiving UL data together with the RRC Resume Request message, new gNB1 sends a second type control message to old gNB2. More specifically, in the example of FIG. 9, new gNB1 sends an improved RETRIEVE UE CONTEXT REQUEST message including a new IE including the UL data (i.e., DTCH data) itself. The XnAP message in step 902 may be a new XnAP message that includes information of the RETRIEVE UE CONTEXT REQUEST message but is different from it.
[0059] In some implementations, the UL data (i.e., DTCH data) may be included in an IE of a new transparent container (e.g., New NG-RAN node To Old NG-RAN node Resume Container) from the new gNB1 to the old gNB2. The name of the new IE may be, for example, Data Over CP IE or Data Container IE. The new gNB1 may include additional information required for identifying or deciphering the UL data of the UE3 in the XnAP message of step 902. The additional information may include a DRB ID and an LCID.
[0060] The old gNB2 detects that the received RETRIEVE UE CONTEXT REQUEST message includes an IE including UL data (i.e., DTCH data). Then, the old gNB2 decides not to relocate the UE context of UE3 to the new gNB1. In step 903, the old gNB2 transmits a RETRIEVE UE CONTEXT FAILURE message. The RETRIEVE UE CONTEXT FAILURE message includes an RRC Release message to be transmitted to UE3. The RRC Release message is encapsulated in an Old NG-RAN node To New NG-RAN node Resume Container IE in the RETRIEVE UE CONTEXT FAILURE message. The RETRIEVE UE CONTEXT FAILURE message may include a cause value (e.g., Non-relocation of context) indicating that the UE context is not relocated. Alternatively, the RETRIEVE UE CONTEXT FAILURE message may include a cause value indicating data transfer without UE context relocation (e.g., Data transfer without context relocation). The XnAP message of step 903 may be a new XnAP message that includes the information of the RETRIEVE UE CONTEXT FAILURE message but is different from the RETRIEVE UE CONTEXT FAILURE message.
[0061] In step 904, the new gNB1 forwards the RRC Release message received in step 903 to the UE3. The new gNB1 may transmit the RRC Release message in the fourth message (Msg4) of the four-step random access procedure. Alternatively, the new gNB1 may transmit the RRC Release message in the second message (message B (MsgB)) of the two-step random access procedure. In response to receiving the RRC Release message, the UE3 remains in the RRC_INACTIVE state. This allows the UE3 to transmit UL data without moving from the RRC_INACTIVE state to the RRC_CONNECTED state.
[0062] According to this embodiment, UL data of UE3 can be sent as soon as possible along with the first XnAP message from new gNB1 to old gNB2.
[0063] <Fourth embodiment> This embodiment provides a modified example of the data transmission in RRC_INACTIVE described in the first to third embodiments. An example of the configuration of a wireless communication network according to this embodiment is similar to the example shown in FIG.
[0064] In this embodiment, the UE 3 in RRC_INACTIVE state sends type information indicating the type of data activity to the new gNB 1 together with UL data and an RRC (connection) resume request message. The type information may be a new IE included in the RRC (connection) resume request message (e.g., RRC Resume Request message). The name of the new IE may be, for example, data activity IE.
[0065] In this embodiment, the new gNB1 further receives type information from the UE3, indicating a type of data activity of the UE3. Then, when the new gNB1 receives UL data from the UE3 together with an RRC Resume Request message and the UE context of the UE3 is not available in the new gNB1, it sends a second type control message to the old gNB2. The second type control message requests the old gNB2 to provide the UE context of the UE3, and indicates a type of data activity of the UE3. The second type control message may be an improved RETRIEVE UE CONTEXT REQUEST message or a new XnAP message.
[0066] In some implementations, the type of data activity of the UE 3 may be selected from multiple types including a first type where there is only one UL data transmission (e.g., one-shot data), a second type where additional UL data transmissions are expected to occur following the first UL data transmission (e.g., more data), and a third type where DL data transmissions are expected to occur after the UL data transmission (e.g., expect DL data). Note that data activity may also be referred to as a data pattern or a traffic pattern.
[0067] In some implementations, the old gNB2 may determine whether to transmit (initial) UL data of the UE3 that is RRC_INACTIVE to the core network (i.e., 5GC) via the old gNB2, taking into account the type of data activity of the UE3. In other words, the old gNB2 may determine whether to relocate (or provide) the UE context of the UE3 to the new gNB1, taking into account the type of data activity of the UE3.
[0068] FIG. 10 shows an example of the operation of new gNB1, old gNB2, and UE3 according to this embodiment. In step 1001, UE3, which is RRC_INACTIVE, transmits an RRC Resume Request message including an IE indicating a type of data activity (e.g., Data Activity IE) and UL data to new gNB1. The RRC Resume Request message and UL data may be transmitted in the third message of the four-step contention-based random access procedure. Alternatively, the RRC Resume Request message and UL data may be transmitted in the first message (message A (MsgA)) of the two-step contention-based random access procedure.
[0069] In step 1002, in response to receiving the UL data with the RRC Resume Request message, the new gNB1 sends a RETRIEVE UE CONTEXT REQUEST message to the old gNB2. The old gNB2 is the last serving gNB of the UE3. The RETRIEVE UE CONTEXT REQUEST message requests the old gNB2 to provide the UE context of the UE3. The RETRIEVE UE CONTEXT REQUEST message includes an information element (IE) indicating a type of data activity of the UE3. The name of the IE may be Data Activity IE, Data Pattern IE, or Traffic Pattern IE. Furthermore, the RETRIEVE UE CONTEXT REQUEST message may include additional information elements as described in the first to third embodiments. Specifically, the RETRIEVE UE CONTEXT REQUEST message may include a new IE or a new cause value indicating the presence of UL data. Additionally or alternatively, the RETRIEVE UE CONTEXT REQUEST message may include a new IE or a new cause value indicating a request for TNL information of the old gNB2. Additionally or alternatively, the RETRIEVE UE CONTEXT REQUEST message may include a new IE containing the UL data (i.e., DTCH data) itself.
[0070] In step 1003, the old gNB2 determines whether to relocate (or provide) the UE context of the UE3 to the new gNB1, taking into account the type of data activity of the UE3. In other words, the old gNB2 determines whether to transmit (initial) UL data of the UE3, which is RRC_INACTIVE, to the core network (i.e., 5GC) via the old gNB2, taking into account the type of data activity of the UE3.
[0071] For example, if the data activity type of UE3 is the above-mentioned first type (e.g., one-shot data), old gNB2 may decide not to relocate the UE context of UE3 to new gNB1 and transmit UL data of UE3 that is RRC_INACTIVE to the core network (i.e., 5GC) via old gNB2. In contrast, old gNB2 may decide to relocate the UE context of UE3 to new gNB1 if the data activity type of UE3 is the above-mentioned second type (e.g., more data) or third type (e.g., expect DL data).
[0072] In response to determining not to relocate the UE context of UE3 to new gNB1, old gNB2 enables UL data (and DL data) of UE3 to be forwarded via old gNB2. This operation may be similar to any of the examples described in the first to fourth embodiments.
[0073] Meanwhile, in response to the decision to relocate the UE context of UE3 to new gNB1, old gNB2 provides the UE context of UE3 to new gNB1. In this case, new gNB1 may receive the UE context of UE3 from old gNB2, decode the UL data of UE3 using the UE context to extract IP data, and transmit the data directly (i.e., without going through old gNB2) to a core network node (i.e., UPF in 5GC). In addition, new gNB1 may receive DL data from a core network node and transmit it to UE3. If the data activity type of UE3 is the above-mentioned second type (e.g., more data) or the above-mentioned third type (e.g., expect DL data), new gNB1 may transmit an RRC Resume message to UE3 in the fourth message of the four-step random access procedure (or the second message of the two-step random access procedure) instead of an RRC Release message. In this case, UE3 enters RRC_CONNECTED state and may transfer more UL or DL data or both with new gNB1.
[0074] According to this embodiment, the UE3 in RRC_INACTIVE state can provide its data activity type to the new gNB1, and further provide it to the old gNB2 via the new gNB1, thereby assisting the old gNB2 to decide whether to relocate the UE context of the UE3.
[0075] <Fifth embodiment> This embodiment provides a modified example of the data transmission in RRC_INACTIVE described in the first to fourth embodiments. The data transmission in RRC_INACTIVE described in the first to fourth embodiments may be applied to the case of Inter-Radio Access Technology (RAT) INACTIVE mobility. More specifically, when an LTE eNB (also called ng-eNB) having a function of cooperating with 5GS is used, the LTE eNB may support the RRC_INACTIVE state of 5G UEs. In this case, when a UE3 in an RRC_INACTIVE state in a cell of an NR gNB selects a cell of an LTE ng-eNB (i.e., inter-RAT cell reselection), the UE3 may stay in the cell of the ng-eNB while remaining in the RRC_INACTIVE state (i.e., without moving to an RRC_CONNECTED state or an RRC_IDLE state).
[0076] As shown in FIG. 11, UE3 may become RRC_INACTIVE in a New Radio (NR) area (e.g., a cell of old gNB2), and then select a cell of ng-eNB4 by inter-RAT cell reselection. If the cell of ng-eNB4 is included in the RNA specified by the RRC Release message of old gNB2, UE3 may remain in the RRC_INACTIVE state. When UE3 starts an RRC Resume procedure for UL data transmission, UE3 may transmit an RRC Resume Request message and UL data to ng-eNB4 in the cell of ng-eNB4. At this time, UE3 may include information (IE or Cause value) that explicitly or implicitly indicates that it is an Inter-RAT resume in the RRC Resume Request message, as shown in FIG. 12. According to any of the examples described in the first to fourth embodiments, the ng-eNB4 (i.e., new RAN node) may send a second type control message (e.g., improved RETRIEVE UE CONTEXT REQUEST message or new XnAP message) to the old gNB2 (i.e., old RAN node or last serving RAN node). Note that, contrary to the example shown in Fig. 11, the UE3 may become RRC_INACTIVE in a cell of the ng-eNB (i.e., old ng-eNB) and select a cell of a gNB (i.e., new gNB), and then transmit UL data in the cell of the gNB by the RRC Resume procedure.
[0077] Furthermore, in this embodiment, the instruction to UE3 to move from RRC_CONNECTED to RRC_INACTIVE (e.g., SuspendConfig IE in RRC Release message) may explicitly or implicitly indicate whether UE3 is capable of performing Inter-RAT INACTIVE mobility (i.e., whether UE3 is authorized to do so). To implicitly indicate this, the instruction may indicate that a cell of a different RAT (e.g., LTE) or a RAN area code (ranac) is included in the RNA. Additionally or alternatively, UE3 may perform Inter-RAT INACTIVE mobility if a cell of a target RAT (e.g., LTE ng-eNB) explicitly or implicitly indicates that it is authorized.
[0078] Next, configuration examples of gNB1, gNB2, UE3, and ng-eNB4 according to the above-mentioned embodiments will be described below. FIG. 13 is a block diagram showing a configuration example of gNB1 according to the above-mentioned embodiments. Configuration examples of gNB2 and ng-eNB4 are also similar to FIG. 13. Referring to FIG. 13, gNB1 includes a Radio Frequency (RF) transceiver 1301, a network interface 1303, a processor 1304, and a memory 1305. The RF transceiver 1301 performs analog RF signal processing to communicate with UEs including UE3. The RF transceiver 1301 may include multiple transceivers. The RF transceiver 1301 is coupled to an antenna array 1302 and a processor 1304. The RF transceiver 1301 receives modulation symbol data from the processor 1304, generates a transmission RF signal, and provides the transmission RF signal to the antenna array 1302. The RF transceiver 1301 also generates a baseband receive signal based on the receive RF signal received by the antenna array 1302 and supplies the baseband receive signal to the processor 1304. The RF transceiver 1301 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
[0079] The network interface 1303 is used to communicate with network nodes (eg, other gNBs, AMF, and User Plane Function (UPF)). The network interface 1303 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.
[0080] The processor 1304 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The processor 1304 may include multiple processors. For example, the processor 1304 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing.
[0081] For example, digital baseband signal processing by the processor 1304 may include signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer, and control plane processing by the processor 1304 may include processing of Non-Access Stratum (NAS) messages, RRC messages, MAC CEs, and DCIs.
[0082] The processor 1304 may include a digital beamformer module for beamforming, which may include a Multiple Input Multiple Output (MIMO) encoder and a precoder.
[0083] The memory 1305 is configured by a combination of volatile memory and non-volatile memory. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. The memory 1305 may include storage located remotely from the processor 1304. In this case, the processor 1304 may access the memory 1305 via the network interface 1303 or an I / O interface not shown.
[0084] The memory 1305 may store one or more software modules (computer programs) 1306 including instructions and data for performing the processing by the gNB1 described in the above-mentioned embodiments. In some implementations, the processor 1304 may be configured to read the software modules 1306 from the memory 1305 and execute them to perform the processing by the gNB1 described in the above-mentioned embodiments.
[0085] In addition, when gNB1 is a gNB Central Unit (gNB-CU) in a cloud RAN (C-RAN) deployment, gNB1 may not include RF transceiver 1301 (and antenna array 1302).
[0086] FIG. 14 is a block diagram showing a configuration example of the UE3. The Radio Frequency (RF) transceiver 1401 performs analog RF signal processing to communicate with NG-RAN nodes (eg, gNB1, gNB2, and ng-eNB4). The RF transceiver 1401 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1401 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1401 is coupled to the antenna array 1402 and the baseband processor 1403. The RF transceiver 1401 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1403, generates a transmission RF signal, and provides the transmission RF signal to the antenna array 1402. The RF transceiver 1401 also generates a baseband reception signal based on the reception RF signal received by the antenna array 1402, and provides the baseband reception signal to the baseband processor 1403. The RF transceiver 1401 may include an analog beamformer circuit for beamforming, which may include, for example, multiple phase shifters and multiple power amplifiers.
[0087] The baseband processor 1403 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission line coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management of layer 1 (e.g., transmission power control), layer 2 (e.g., radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling related to attachment, mobility, and call management).
[0088] For example, the digital baseband signal processing by the baseband processor 1403 may include signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Also, the control plane processing by the baseband processor 1403 may include processing of a Non-Access Stratum (NAS) protocol, a Radio Resource Control (RRC) protocol, and MAC Control Elements (CEs).
[0089] The baseband processor 1403 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.
[0090] The baseband processor 1403 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1404 described later.
[0091] The application processor 1404 is also called a CPU, an MPU, a microprocessor, or a processor core. The application processor 1404 may include multiple processors (multiple processor cores). The application processor 1404 executes a system software program (operating system (OS)) and various application programs (e.g., a calling application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 1406 or a memory not shown, thereby implementing various functions of the UE3.
[0092] In some implementations, the baseband processor 1403 and the application processor 1404 may be integrated on a single chip, as shown by the dashed line (1405) in Figure 14. In other words, the baseband processor 1403 and the application processor 1404 may be implemented as a single System on Chip (SoC) device 1405. An SoC device may also be called a system Large Scale Integration (LSI) or a chipset.
[0093] The memory 1406 is a volatile memory or a non-volatile memory, or a combination thereof. The memory 1406 may include a plurality of physically independent memory devices. The volatile memory is, for example, a Static Random Access Memory (SRAM) or a Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a Mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. For example, the memory 1406 may include an external memory device accessible from the baseband processor 1403, the application processor 1404, and the SoC 1405. The memory 1406 may include an internal memory device integrated in the baseband processor 1403, the application processor 1404, or the SoC 1405. Furthermore, the memory 1406 may include a memory in a Universal Integrated Circuit Card (UICC).
[0094] The memory 1406 may store one or more software modules (computer programs) 1407 including instructions and data for performing the processing by the UE 3 described in the above-mentioned embodiments. In some implementations, the baseband processor 1403 or the application processor 1404 may be configured to read the software module 1407 from the memory 1406 and execute it to perform the processing by the UE 3 described in the above-mentioned embodiments using the drawings.
[0095] In addition, the control plane processing and operations performed by UE3 described in the above embodiment can be realized by elements other than the RF transceiver 1401 and the antenna array 1402, i.e., at least one of the baseband processor 1403 and the application processor 1404, and the memory 1406 storing the software module 1407.
[0096] As described with reference to FIG. 13 and FIG. 14, each of the processors included in the gNB1, gNB2, UE3, and ng-eNB4 according to the above-described embodiments executes one or more programs including instructions for causing a computer to perform the algorithm described with reference to the drawings. The programs can be stored and provided to a computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)). The programs may also be provided to a computer by various types of transitory computer readable media. Examples of the temporary computer-readable medium include an electric signal, an optical signal, and an electromagnetic wave. The temporary computer-readable medium can provide the program to the computer via a wired communication path such as an electric wire or an optical fiber, or a wireless communication path.
[0097] <Other embodiments> The above-described embodiments may be implemented independently of each other, or the whole or part of the embodiments may be implemented in appropriate combination.
[0098] When the 2-Step Random Access (2-Step RA) procedure is used for transmitting UL data (DTCH data) by the UE3 in the above-mentioned embodiment, a fallback to the 4-Step Random Access (4-Step RA) procedure may be performed. Specifically, the UE3 transmits the UL data together with an RRC (connection) resume request message (e.g., an RRC Resume Request message) in the first message (MsgA) of the 2-Step RA procedure. If the New gNB1 can detect the random access preamble of the first message (MsgA) but cannot correctly decode the data (payload) of the first message (MsgA), the New gNB1 may transmit a random access response (fallback RAR) indicating a notification of a fallback to the 4-Step RA procedure to the UE3 in the second message (MsgB) of the 2-Step RA procedure. When UE3 receives the fallback notification to the 4-Step RA procedure, it transmits the RRC (connection) resumption request message and UL data transmitted in the first message (MsgA) of the 2-Step RA procedure in the third message (Msg3) of the 4-Step RA procedure. After that, new gNB1, old gNB2, and UE3 may perform the same operations as those in the above-mentioned embodiment using the 4-Step RA procedure.
[0099] In the above embodiment, the UE 3 transmits UL data (DTCH data) while remaining in the RRC_INACTIVE state. More specifically, this may be done as follows. When the UE 3 receives an RRC Release message including an instruction (SuspendConfig) to move from the RRC_CONNECTED state to the RRC_INACTIVE state, the UE 3 saves the UE context. This UE context is also called a UE Access Stratum (AS) context or a UE Inactive AS context. The UE context includes, for example, current security information, a cell identity (cellIdentity, PCI) of a serving cell (PCell), a C-RNTI assigned to the UE 3, and information on the correspondence between IP data (QoS flow) of the SDAP layer and a DRB (QoS flow to DRB mapping rule). Furthermore, the UE 3 may determine whether information indicating that UL data transmission in the RRC_INACTIVE state is permitted is included in the RRC Release message (e.g., SuspendConfig). Then, when the UE3 is in the RRC_INACTIVE state, if the upper layer (Non-access stratum (NAS) layer) of the UE3 notifies the RRC layer (AS layer) that there is data to be transmitted, the RRC layer of the UE3 determines whether or not UL data transmission in the RRC_INACTIVE state is permitted. Furthermore, the UE3 may determine whether or not it is permitted (or supported) in the serving cell (camping cell in the RRC_INACTIVE state). If the UE3 is permitted to transmit UL data in the RRC_INACTIVE state (and further, if it is permitted in the serving cell), the UE3 retrieves (restores) necessary information from the UE context it holds, and starts the RRC (connection) resumption request procedure.When the RRC (connection) resume request procedure is performed in a 4-step random access (4-Step RA) procedure, the UL data is transmitted in the third message (Msg3), and when the RRC (connection) resume request procedure is performed in a 2-step random access (2-Step RA) procedure, the UL data is transmitted in the data portion (MsgA payload) of the first message. At this time, the RRC Resume Request message transmitted together with the UL data may include a Cause value (e.g., UL-data-Inactive, mo-Data-Inactive) indicating that the UL data transmission is involved (or is intended for this). Then, when the UE 3 receives an RRC Release message in response to the RRC Resume Request message, the UE 3 remains in the RRC_INACTIVE state. At this time, the UE 3 replaces a part of the UE context it holds with the configuration information included in the RRC Release message (e.g., SuspendConfig IE) (overwrites the UE context with the configuration information). The configuration information may include, for example, RAN area information (e.g., ran-NotificationAreaInfo) and security information (e.g., nextHopChainingCount). Furthermore, the configuration information may include information indicating whether or not the UE 3 is permitted to transmit data in RRC Resume (in other words, whether or not the UE 3 is authorized to do so). The information may further indicate which of one or more DRBs configured in the UE 3 is permitted to transmit data in RRC Resume. This allows the UE 3 to transmit UL data while remaining in the RRC_INACTIVE state in the serving cell in which it is camped when UL data is generated again. On the other hand, when the UE 3 receives an RRC Resume message in response to the RRC Resume Request message, it transitions to the RRC_CONNECTED state.
[0100] As described in the above embodiment, the IP address of the old gNB2 used to forward GTP-U / UDP / IP packets on the Xn-U interface (GTP-U tunnel) may be the same as the IP address of the old gNB2 used to forward XnAP / SCTP / IP packets on the Xn-C interface (XnAP protocol). The old gNB2 may proactively signal with the new gNB1 to inform it that the same IP address will be used for both the Xn-U and Xn-C interfaces.
[0101] Similarly, the IP address of the new gNB1 used to forward GTP-U / UDP / IP packets on the Xn-U interface (GTP-U tunnel) may be the same as the IP address of the new gNB1 used to forward XnAP / SCTP / IP packets on the Xn-C interface (XnAP protocol). The new gNB1 may proactively signal with the old gNB2 to inform it that the same IP address will be used for both the Xn-U and Xn-C interfaces.
[0102] The above-mentioned embodiment may be implemented in LTE. Specifically, the above-mentioned embodiment may be applied to a case where the UE3 transmits UL data in an RRC_INACTIVE state in a cell of an LTE eNB (or an advanced version thereof) connected to an EPC (or an advanced version thereof). More specifically, when the new eNB receives UL data from the UE3 together with an RRC (connection) resumption request message and the UE context of the UE3 is not available in the new eNB, the new eNB sends a second type control message to the old eNB over the X2 interface. The old eNB decides whether to transmit the UL data to the core network (i.e., EPC) via the old eNB or transmit the UE context to the new eNB. When the old eNB decides to transmit the UL data to the core network via the old eNB, it may transmit the TNL information of the old eNB to the new eNB. In response to this, the new eNB may transmit the UL data to the old eNB. This allows the UL data to be transmitted to the core network without transferring the UE context of the UE3 from the old eNB to the new eNB.
[0103] The operations of the new gNB1 (or new ng-eNB4), the old gNB2, and the UE3 described in the above embodiment may be performed in cell reselection (also referred to as intra-RAT inter-system cell reselection) between a cell of an LTE eNB and a cell of an ng-eNB by the UE, or may be performed in inter-RAT cell reselection between a cell of an LTE eNB and a cell of a gNB. For example, the operations of the new gNB1 (or new ng-eNB4) and the old gNB2 described in the above embodiment may be performed between the LTE eNB and the ng-eNB, or may be performed between the LTE eNB and the gNB.
[0104] Furthermore, the above-described embodiment is merely an example of application of the technical idea obtained by the inventor of the present invention. In other words, the technical idea is not limited to the above-described embodiment, and various modifications are possible.
[0105] For example, some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.
[0106] (Appendix 1) A first Radio Access Network (RAN) node, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: when receiving an RRC resumption request message without uplink data from a wireless terminal in a Radio Resource Control (RRC)_INACTIVE state and a radio terminal context of the wireless terminal is not available in the first RAN node, sending a first type control message requesting the radio terminal context to a second RAN node that is a closest serving RAN node of the wireless terminal; configured to receive the uplink data from the radio terminal in the RRC_INACTIVE state together with the RRC resume request message and, if the radio terminal context is not available in the first RAN node, to send to the second RAN node a second type control message requesting the radio terminal context and distinguished from the first type control message. The first RAN node. (Appendix 2) the second type control message is distinguished from the first type control message by the second type control message including an indication, directly or indirectly, of the presence of the uplink data. 2. The first RAN node according to claim 1. (Appendix 3) the second type control message is distinguished from the first type control message by the second type control message including an indication representing a request for transport network layer (TNL) information of the second RAN node; 2. The first RAN node according to claim 1. (Appendix 4) The at least one processor: configured to receive a third control message from the second RAN node after transmitting the second type control message; and configured to transmit the uplink data to the second RAN node in response to the third control message indicating that relocation of the radio terminal context is not to be performed. 4. The first RAN node according to claim 1 . (Appendix 5) The at least one processor: configured to receive a third control message from the second RAN node after transmitting the second type control message; and configured to transmit the uplink data to the second RAN node in response to the third control message indicating permission for uplink data forwarding via the second RAN node. 4. The first RAN node according to claim 1 . (Appendix 6) the at least one processor is configured to transmit the uplink data to the second RAN node in response to receiving a third control message from the second RAN node indicating Transport Network Layer (TNL) information of the second RAN node after transmitting the second type control message. 4. The first RAN node according to claim 1 . (Appendix 7) the second type control message is distinguished from the first type control message by the second type control message including the uplink data itself; 2. The first RAN node according to claim 1. (Appendix 8) the at least one processor is configured to include additional information in the second type control message that is necessary to identify or decode the uplink data. 8. The first RAN node according to claim 7. (Appendix 9) the additional information includes one or both of a data radio bearer identifier and a logical channel identifier; 9. The first RAN node of claim 8. (Appendix 10) The at least one processor: configured to receive type information from the wireless terminal along with the uplink data, the type information indicating a type of data activity; and configured to inform the second RAN node of the type of data activity via a control message of the second type. 10. The first RAN node according to any one of Supplementary Notes 1 to 9. (Appendix 11) the type of data activity is selected from a plurality of types including a first type being only a transmission of the uplink data, a second type being an additional uplink data transmission expected to occur following the transmission of the uplink data, and a third type being a downlink data transmission expected to occur after the transmission of the uplink data. 11. The first RAN node of claim 10. (Appendix 12) the at least one processor is configured to include transport network layer (TNL) information of the first RAN node in the second type control message. 12. The first RAN node according to any one of Supplementary Notes 1 to 11. (Appendix 13) a second Radio Access Network (RAN) node, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: A radio terminal context of a radio terminal in a Radio Resource Control (RRC)_INACTIVE state is maintained; configured to receive a control message from a first RAN node requesting the radio terminal context; and determining whether the control message is of a specific type that is used when the first RAN node receives uplink data from the wireless terminal in the RRC_INACTIVE state together with an RRC resumption request message. A second RAN node. (Appendix 14) The particular type is distinguished from other types by the control message including an indication that directly or indirectly indicates the presence of the uplink data. 14. The second RAN node of claim 13. (Appendix 15) The particular type is distinguished from other types by the control message including an indication of a request for Transport Network Layer (TNL) information of the second RAN node. 14. The second RAN node of claim 13. (Appendix 16) The particular type is distinguished from other types by the fact that the control message includes the uplink data itself. 14. The second RAN node of claim 13. (Appendix 17) the at least one processor is configured to, if the control message is of the particular type, transmit the uplink data to a core network via the second RAN node without providing the radio terminal context to the first RAN node. 17. The second RAN node according to any one of Supplementary Notes 13 to 16. (Appendix 18) the at least one processor is configured to determine whether to transmit the uplink data to a core network via the second RAN node if the control message is of the particular type. 18. The second RAN node according to any one of Supplementary Notes 13 to 17. (Appendix 19) the at least one processor is configured to determine whether to transmit the uplink data to the core network via the second RAN node taking into account a type of data activity of the wireless terminal indicated by the control message. 19. The second RAN node of claim 18. (Appendix 20) the type of data activity is selected from a plurality of types including a first type being only a transmission of the uplink data, a second type being an additional uplink data transmission expected to occur following the transmission of the uplink data, and a third type being a downlink data transmission expected to occur after the transmission of the uplink data. 20. The second RAN node of claim 19. (Appendix 21) The at least one processor is configured to, in response to determining to transmit the uplink data to the core network via the second RAN node, send a control message to the first RAN node indicating Transport Network Layer (TNL) information of the second RAN node. 21. The second RAN node according to any one of Supplementary Notes 18 to 20. (Appendix 22) the at least one processor is configured to, in response to determining to transmit the uplink data to the core network via the second RAN node, send a control message to the first RAN node indicating that relocation of the radio terminal context is not to be performed. 21. The second RAN node according to any one of Supplementary Notes 18 to 20. (Appendix 23) the at least one processor is configured to, in response to determining to transmit the uplink data to the core network via the second RAN node, send a control message to the first RAN node indicating permission for uplink data forwarding via the second RAN node. 21. The second RAN node according to any one of Supplementary Notes 18 to 20. (Appendix 24) A wireless terminal, At least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor is configured to, when the wireless terminal is in a Radio Resource Control (RRC)_INACTIVE state, send uplink data and type information indicating a type of data activity together with an RRC resume request message to a Radio Access Network (RAN) node. Wireless terminal. (Appendix 25) the at least one processor is configured to select the type of data activity from a plurality of types including a first type being only a transmission of the uplink data, a second type being an expected occurrence of an additional uplink data transmission following the uplink data, and a third type being an expected occurrence of a downlink data transmission following the transmission of the uplink data. 25. The wireless terminal of claim 24. (Appendix 26) The type information is included in the RRC resume request message. 26. The wireless terminal of claim 24 or 25. (Appendix 27) 1. A method performed by a first Radio Access Network (RAN) node, comprising: receiving an RRC resumption request message without uplink data from a wireless terminal in a Radio Resource Control (RRC)_INACTIVE state and when a radio terminal context of the wireless terminal is not available in the first RAN node, sending a first type control message requesting the radio terminal context to a second RAN node that is a proximate serving RAN node of the wireless terminal; receiving the uplink data from the radio terminal in the RRC_INACTIVE state together with the RRC resume request message and, if the radio terminal context is not available in the first RAN node, sending a second type control message to the second RAN node requesting the radio terminal context and distinguished from the first type control message; A method for providing the above. (Appendix 28) A method performed by a second Radio Access Network (RAN) node, comprising: maintaining a radio terminal context of a radio terminal in a Radio Resource Control (RRC)_INACTIVE state; receiving a control message from a first RAN node requesting the radio terminal context; and determining whether the control message is of a specific type that is used when the first RAN node receives uplink data from the wireless terminal in the RRC_INACTIVE state together with an RRC resumption request message; A method for providing the above. (Appendix 29) 1. A method performed by a wireless terminal, comprising: sending uplink data and type information indicating a type of data activity together with an RRC resume request message to a Radio Access Network (RAN) node when the wireless terminal is in a Radio Resource Control (RRC)_INACTIVE state; A method for providing the above. (Appendix 30) A program for causing a computer to perform a method for a first Radio Access Network (RAN) node, comprising: The method comprises: receiving an RRC resumption request message without uplink data from a wireless terminal in a Radio Resource Control (RRC)_INACTIVE state and when a radio terminal context of the wireless terminal is not available in the first RAN node, sending a first type control message requesting the radio terminal context to a second RAN node that is a proximate serving RAN node of the wireless terminal; receiving the uplink data from the radio terminal in the RRC_INACTIVE state together with the RRC resume request message and, if the radio terminal context is not available in the first RAN node, sending a second type control message to the second RAN node requesting the radio terminal context and distinguished from the first type control message; A program that includes: (Appendix 31) A program for causing a computer to perform a method for a second Radio Access Network (RAN) node, comprising: The method comprises: maintaining a radio terminal context of a radio terminal in a Radio Resource Control (RRC)_INACTIVE state; receiving a control message from a first RAN node requesting the radio terminal context; and determining whether the control message is of a specific type that is used when the first RAN node receives uplink data from the wireless terminal in the RRC_INACTIVE state together with an RRC resumption request message; A program that includes: (Appendix 32) A program for causing a computer to perform a method for a wireless terminal, comprising: The method comprises, when the wireless terminal is in a Radio Resource Control (RRC)_INACTIVE state, sending uplink data and type information indicating a type of data activity together with an RRC resume request message to a Radio Access Network (RAN) node. program.
[0107] This application claims priority based on Japanese Patent Application No. 2020-022471, filed on February 13, 2020, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]
[0108] 1 gNB 2gNB 3. UE 4 ng-eNB 1304 Processor 1305 Memory 1306 Modules 1403 Baseband Processor 1404 Application Processor 1406 Memory 1407 Modules
Claims
1. A method performed by a second Radio Access Network (RAN) node, comprising: receiving a RETRIEVE UE CONTEXT REQUEST message from a first RAN node that has received uplink data sent from a User Equipment (UE) in a Radio Resource Control (RRC)_INACTIVE state and an RRC Resume Request message, the RETRIEVE UE CONTEXT REQUEST message including an indication of the presence of the uplink data; determining whether to relocate a UE context of the UE after receiving the RETRIEVE UE CONTEXT REQUEST message; if after receiving the RETRIEVE UE CONTEXT REQUEST message it is decided not to relocate the UE context, sending a RETRIEVE UE CONTEXT FAILURE message to the first RAN node; if it is determined not to relocate the UE context after receiving the RETRIEVE UE CONTEXT REQUEST message, sending to the first RAN node another message different from the RETRIEVE UE CONTEXT FAILURE message, the other message including Transport Network Layer (TNL) information; The method includes:
2. The method described in claim 1, wherein the RETRIEVE UE CONTEXT FAILURE message indicates not to relocate the UE context.
3. The method described in claim 1 or 2, wherein the TNL information is TNL information of the second RAN node.
4. 1. A method performed by a first Radio Access Network (RAN) node, comprising: receiving uplink data and an RRC Resume Request message from a User Equipment (UE) in a Radio Resource Control (RRC)_INACTIVE state; sending a RETRIEVE UE CONTEXT REQUEST message to a second RAN node, the second RAN node being the last serving RAN node for the UE, the RETRIEVE UE CONTEXT REQUEST message including an indication of the presence of the uplink data; receiving, from the second RAN node, a RETRIEVE UE CONTEXT FAILURE message sent in response to the RETRIEVE UE CONTEXT REQUEST message if the UE context of the UE is not relocated; receiving, after the second RAN node has received the RETRIEVE UE CONTEXT REQUEST message and determined not to relocate the UE context, another message different from the RETRIEVE UE CONTEXT FAILURE message from the second RAN node, the other message including Transport Network Layer (TNL) information; The method includes:
5. The method of claim 4 , wherein the RETRIEVE UE CONTEXT FAILURE message includes a cause value indicating that the UE context is not relocated.
6. 6. The method of claim 4, further comprising transmitting the uplink data to the second RAN node before receiving the RETRIEVE UE CONTEXT FAILURE message.
7. The method described in claim 4 or 5, wherein the TNL information is TNL information of the second RAN node.
8. The method according to claim 4 or 7, wherein the other message including the TNL information is received before the RETRIEVE UE CONTEXT FAILURE message.
9. The method of claim 4 , further comprising: sending an RRC Release message to the UE that is included in the RETRIEVE UE CONTEXT FAILURE message.
10. The method of claim 9 , wherein the RRC Release message includes a suspend configuration.
11. The method of claim 4 , wherein the uplink data and the RRC Resume Request message are transmitted from the UE using a random access procedure.
12. The method of claim 11, wherein the random access procedure is a two-step random access procedure.
13. a second Radio Access Network (RAN) node, means for receiving, from a first RAN node that has received uplink data transmitted from a User Equipment (UE) in a Radio Resource Control (RRC)_INACTIVE state and an RRC Resume Request message, a RETRIEVE UE CONTEXT REQUEST message including an indication of the presence of said uplink data; means for determining whether to relocate a UE context of the UE after receiving the RETRIEVE UE CONTEXT REQUEST message; means for sending a RETRIEVE UE CONTEXT FAILURE message to the first RAN node if it is determined not to relocate the UE context after receiving the RETRIEVE UE CONTEXT REQUEST message; means for transmitting, if after receiving the RETRIEVE UE CONTEXT REQUEST message, a message not to relocate the UE context, to the first RAN node, the message being different from the RETRIEVE UE CONTEXT FAILURE message, the message including Transport Network Layer (TNL) information; Including, A second RAN node.
14. The second RAN node of claim 13, wherein the RETRIEVE UE CONTEXT FAILURE message indicates not to relocate the UE context.
15. The TNL information of the second RAN node. A second RAN node according to claim 13 or 14.
16. a first Radio Access Network (RAN) node, Means for receiving uplink data and an RRC Resume Request message from a User Equipment (UE) in a Radio Resource Control (RRC)_INACTIVE state; means for transmitting a RETRIEVE UE CONTEXT REQUEST message, the RETRIEVE UE CONTEXT REQUEST message including an indication of the presence of the uplink data, to a second RAN node, the second RAN node being the last serving RAN node for the UE; means for receiving, from the second RAN node, a RETRIEVE UE CONTEXT FAILURE message transmitted in response to the RETRIEVE UE CONTEXT REQUEST message if the UE context of the UE is not relocated; means for receiving, after the second RAN node receives the RETRIEVE UE CONTEXT REQUEST message and decides not to relocate the UE context, another message different from the RETRIEVE UE CONTEXT FAILURE message from the second RAN node, the other message including Transport Network Layer (TNL) information; a first RAN node including:
17. The first RAN node of claim 16, wherein the RETRIEVE UE CONTEXT FAILURE message includes a cause value indicating that the UE context is not relocated.
18. 18. The first RAN node of claim 16 or 17, further comprising means for transmitting the uplink data to the second RAN node before receiving the RETRIEVE UE CONTEXT FAILURE message.
19. A first RAN node as described in claim 16 or 17, wherein the TNL information is TNL information of the second RAN node.
Citation Information
Patent Citations
Radio resource control resume without context fetch
WO2018142207A1
