Methods, devices, and systems for UE connection resumption in wireless network
The methods for UE context retrieval in wireless networks address the challenge of Xn interface absence by enabling direct retrieval from the core network using a resume ID or pre-stored context, optimizing UE connection resumption and reducing signaling overhead and latency.
Patent Information
- Application Number
- PCT/CN2025/093035
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
In wireless communication networks, particularly in 5G and beyond, when a user equipment (UE) transitions to the RRC Inactive state, the lack of an Xn interface between base stations hinders efficient UE context retrieval, leading to increased signaling overhead and data transmission delays, especially for Small Data Transmission (SDT) scenarios.
Methods for UE context retrieval and transfer are implemented, allowing the new base station to retrieve UE context from the core network directly, either by using a resume ID to identify the old base station or by pre-storing UE context in the core network, thereby reducing signaling overhead and minimizing service delay.
These methods enable efficient UE connection resumption and reduced signaling overhead by optimizing UE context retrieval, especially for SDT, by either using a resume ID to locate the UE context or by pre-storing it in the core network, thus enhancing network efficiency and reducing latency.
Smart Images

Figure CN2025093035_12112026_PF_FP_ABST
Abstract
Description
METHODS, DEVICES, AND SYSTEMS FOR UE CONNECTION RESUMPTION IN WIRELESS NETWORKTECHNICAL FIELD
[0001] This disclosure is directed generally to wireless communications, and particularly to methods, devices, and systems for UE connection resumption and UE context transferring in a wireless communication network, such as 4G, 5G, and 6G wireless communication network.BACKGROUND
[0002] Wireless communication technology keeps evolving with new emerging services such as Extended Reality (XR) services, which include Virtual Reality (VR) , Augmented Reality (AR) , and Mixed Reality (MR) . These services rely on wireless networks for data transmission. The evolution of wireless communication technologies, especially with the advent of 5G and beyond, has opened new opportunities for such emerging services by providing the necessary infrastructure to support high-quality, immersive experiences. A new generation network is expected to provide high speed, low latency and ultra-reliable communication capabilities and fulfill the requirements from different industries and users.SUMMARY
[0003] This disclosure is directed to a method, device, and system for wireless communication, and more specifically, for UE connection resumption and UE context transferring in a wireless communication system, such as 4G, 5G, and 6G wireless communication network.
[0004] In some embodiments, a method performed by a first network element is disclosed. The method may include: transmitting, to a second network element, a first message carrying at least one of: context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context; a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; or a session identifier identifying the context of the wireless device.
[0005] In some embodiments, a method performed by a first network element is disclosed. The method may include: receiving, from a second network element, a first message carrying at least one of: context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context; a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; or a first session identifier identifying the context of the wireless device assigned by the second network element.
[0006] In some embodiments, a method performed by a first network element is disclosed. The method may include: transmitting, to a second network element, a first message requesting context of a wireless device that is in an inactive state, the first message carrying at least one of: a first session identifier identifying the context of the wireless device; a second session identifier assigned by the second network element for identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device.
[0007] In some embodiments, there is a network node or a wireless communication node comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement any methods recited in any of the embodiments.
[0008] In some embodiments, a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement any method recited in any of the embodiments.
[0009] The above embodiments and other aspects and alternatives of their implementations are described in greater detail in the drawings, the descriptions, and the claims below.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 shows an example wireless communication network.
[0011] FIG. 2 shows an example wireless network node.
[0012] FIG. 3 shows an example user equipment.
[0013] FIGs. 4-8 show various flow diagrams of exemplary embodiments for wireless communication involving UE context or SDT relevant UE context transferring.DETAILED DESCRIPTION
[0014] The present disclosure will now be described in detail hereinafter with reference to the accompanied drawings, which form a part of the present disclosure, and which show, by way of illustration, specific examples of embodiments. Please note that the present disclosure may, however, be embodied in a variety of different forms and, therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments to be set forth below. It is to be understood that the embodiments described herein are merely intended to explain the present application and not to limit the present application.
[0015] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” or “in some embodiments” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” or “in other embodiments” as used herein does not necessarily refer to a different embodiment. The phrase “in one implementation” or “in some implementations” as used herein does not necessarily refer to the same implementation and the phrase “in another implementation” or “in other implementations” as used herein does not necessarily refer to a different implementation. It is intended, for example, that claimed subject matter includes combinations of exemplary embodiments or implementations in whole or in part.
[0016] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and / or, ” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a” , “an” , or “the” , again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
[0017] Wireless Communication Network
[0018] FIG. 1 shows an exemplary wireless communication network 100 that includes a core network 110 and a radio access network (RAN) 120. The core network 110 further includes at least one Mobility Management Entity (MME) 112 and / or at least one Access and Mobility Management Function (AMF) . Other functions that may be included in the core network 110 are not shown in FIG. 1. The RAN 120 further includes multiple base stations, for example, base stations 122 and 124. The base stations may include at least one evolved NodeB (eNB) for 4G LTE, an enhanced LTE eNB (ng-eNB) , or a Next generation NodeB (gNB) for 5G New Radio (NR) , 6G network or any other type of signal transmitting / receiving device such as a UMTS NodeB. The eNB 122 communicates with the MME 112 via an S1 interface. Both the eNB 122 and gNB 124 may connect to the AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, the base station gNB 124 may be configured to manage and support cell 1, cell 2, and cell 3.
[0019] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU) . The CU and the DU may be co-located in a same location, or they may be split in different locations. The CU and the DU may be connected via an F1 interface. Alternatively, for an eNB which is capable of connecting to the 5G network, it may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and the ng-eNB-DU may be connected via a W1 interface.
[0020] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1 labeled as 140 includes cell 1, cell 2, and cell 3, and may further include more cells that may be managed by other base stations and not shown in FIG. 1. The wireless communication network 100 may also include at least one UE 160. The UE may select a cell among multiple cells supported by a base station to communication with the base station through Over the Air (OTA) radio communication interfaces and resources, and when the UE 160 travels in the wireless communication network 100, it may reselect a cell for communications. For example, the UE 160 may initially select cell 1 to communicate with base station 124, and it may then reselect cell 2 at certain later time point. The cell selection or reselection by the UE 160 may be based on wireless signal strength / quality in the various cells and other factors.
[0021] The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, 5G, or 6G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as a 2G base station, a 3G NodeB, an LTE eNB, a 5G NR gNB, or a 6G base station. The UE 160 may be implemented as mobile or fixed communication devices which are capable of accessing the wireless communication network 100. The UE 160 may include but is not limited to mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC / eMTC devices, distributed remote sensor devices, roadside assistant equipment, XR devices, and desktop computers. The UE 160 may also be generally referred to as a wireless communication device, or a wireless terminal. The UE 160 may support sidelink communication to another UE via a PC5 interface.
[0022] While the description below focuses on cellular wireless communication systems as shown in FIG. 1, the underlying principles are applicable to other types of wireless communication systems for paging wireless devices. These other wireless systems may include but are not limited to Wi-Fi, Bluetooth, ZigBee, and WiMax networks.
[0023] FIG. 2 shows an example of electronic device 200 to implement a network base station (e.g., a radio access network node) , a core network (CN) , and / or an operation and maintenance (OAM) . Optionally in one implementation, the example electronic device 200 may include radio transmitting / receiving (Tx / Rx) circuitry 208 to transmit / receive communication with UEs and / or other base stations. Optionally in one implementation, the electronic device 200 may also include network interface circuitry 209 to communicate the base station with other base stations and / or a core network, e.g., optical or wireline interconnects, Ethernet, and / or other data transmission mediums / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator or the like.
[0024] The electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor (s) 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for the one or more of the processors 221 to perform the functions of the network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.
[0025] FIG. 3 shows an example of an electronic device to implement a terminal device 300 (for example, a user equipment (UE) ) . The UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle. The UE 300 may include a portion or all of the following: communication interfaces 302, a system circuitry 304, an input / output interfaces (I / O) 306, a display circuitry 308, and a storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the inputs / output (I / O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements. Additional examples of the I / O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
[0026] Referring to FIG. 3, the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation / demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and / or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings. As one specific example, the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G / Long Term Evolution (LTE) , 5G NR, and 6G standards. The techniques described below, however, are applicable to other wireless communications technologies whether arising from the 3rd Generation Partnership Project (3GPP) , GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.
[0027] Referring to FIG. 3, the system circuitry 304 may include one or more processors 321 and memories 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G or other data that the UE 300 will send, or has received, through the communication interfaces 302. In various implementations, a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.
[0028] The present disclosure describes various embodiments generally relate to UE context retrieval / transfer, which may be implemented, partly or totally, on the core network, the network base station, the network element, and / or the user equipment described above in FIGS. 1 -3.
[0029] UE power saving state
[0030] The Radio Resource Control (RRC) Inactive state (or RRC_INACTIVE state) , introduced in 5G New Radio (NR) , is a power-efficient mode designed to achieve a balance between maintaining connectivity and reducing energy consumption. Unlike the RRC Idle state, where no UE context is retained, the UE in the RRC Inactive state preserves its UE context, such as security parameters, bearer configurations, and other relevant information, at the last serving base station (e.g., gNB) . Note that the UE context may be retained at the last serving base station (which releases the UE to the RRC inactive state) . This enables the UE to quickly resume data transmission without undergoing a full connection re-establishment, thereby minimizing latency and signaling overhead. In some implementations, the last serving base station may be the base station that releases, or transitions the UE to the RRC inactive state.
[0031] After being released to the RRC Inactive state by the last serving base station (referred to as the “old base station” ) , the UE may move into an area covered or served by a different base station (referred to as the "new base station" or "receiving base station" ) . If the UE needs to resume communication, such as initiating data transmission, it may trigger the RRC Resume Procedure. The new base station may then retrieve the UE’s context from the old base station over the Xn interface, enabling the resumption of the connection.
[0032] In some implementations, the UE context may include at least one of the following:
[0033] · UE identification information, such as IMSI (International Mobile Subscriber Identity) , SUPI (Subscription Permanent Identifier) , GUTI (Globally Unique Temporary Identifier) ;
[0034] · Radio Access Technology (RAT) / Frequency Selection Priority of the UE;
[0035] · UE Radio Capability information;
[0036] · Mobility restriction area for the UE, e.g., the allowed / forbidden accessing cells, Public Land Mobile Networks (PLMNs) , Tracking Areas (TAs) , etc.;
[0037] · UE location / positioning information;
[0038] · Session and bearer context, including at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information;
[0039] · UE Security Information including at least one of: ciphering key, integrity protection keys, security algorithms selected; or
[0040] · Connection and mobility information, such as RNTI (Radio Network Temporary Identifier) , last known cell or tracking area, mobility state, and paging configuration.
[0041] In some scenarios, a UE in RRC inactive state may use Small Data Transmission (SDT) to send and / or receive small amount of data (e.g., one or a few data packets) without fully establishing an RRC connection. In order to perform SDT transmission, SDT relevant UE context is required for the base station serving the RRC inactive UE. The SDT relevant UE context may include at least one of the following:
[0042] · A configuration of a list of Data Radio Bearers (DRBs) that support SDT. This may include Radio Link Control (RLC) bearer configuration of each DRB, the QoS flow (s) mapped to each DRB, etc.; or
[0043] · A configuration of a list of Signaling Radio Bearers (SRBs) that support SDT. This may include RLC bearer configuration of each SRB, the QoS flow (s) mapped to each SRB, etc.
[0044] Note that SDT relevant UE context is a subset of the complete UE context, enabling reduced signaling overhead when transferred. When transferring SDT relevant UE context, non SDT related UE context is not transferred.
[0045] In some scenarios, when there is no Xn connection between the new base station and the old base station, the new base station is unable to retrieve the UE's context and must fall back to establishing a new RRC connection with the UE.
[0046] In some scenarios, after a UE is transitioned to the RRC Inactive state, it may move from the old base station (from which the UE is released) to a new base station. For example, UE may move to a new area that is covered by the new base station. However, there is a chance that there is no Xn interface between the two base stations, and the new base station is unable to directly retrieve the UE context from the old base station. As a result, UE context transfer is not supported through the Xn-based procedures. Instead, a fall back procedure needs to be used to establish a new RRC connection between the new base station and the UE. This may lead to increased data transmission delay and additional signaling overhead.
[0047] In this disclosure, various embodiments are disclosed aiming to address the issues (e.g., for UE context retrieval) when there is no Xn connectivity between the new and old base stations. Additionally, certain embodiments specifically address scenarios where the UE resumes the connection for Small Data Transmission (SDT) . In such cases, further optimization can be applied by retrieving only a partial UE context that is SDT relevant, thereby reducing signaling overhead and minimizing service delay.
[0048] The exemplary embodiments in this disclosure merely serve as examples and do not pose limitations. Any steps and / or operations in one same embodiment / implementation or more than one different embodiments / implementation in the present disclosure may be partially performed, combined, or arranged in any amount or order, as desired. Two or more of the steps and / or operations may be performed in parallel. Various embodiments and implementations in the disclosure may be used separately or combined in any order. Further, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits) .
[0049] Embodiment 1:
[0050] Various embodiments in the present disclosure describes methods for a new base station retrieving UE context of a UE in RRC inactive state. The embodiments may apply to a UE released by an old base station (previous serving base station, or last serving base station) and then attempts to acquire service from a new base station, while there is no Xn connection between these two base stations.
[0051] FIG. 4 shows a non-limiting example of a method including a portion or all of the following steps.
[0052] Step 0: This step is pre-condition. The UE has been released / transitioned to the RRC Inactive state by the old base station (last serving base station) , which retains the UE context. The UE is then covered by a new base station (new serving base station, or receiving base station) due to, for example, UE movement. The UE decides to resume its connection with the new base station, for example, for data transmission. There is no Xn interface connection between the new base station and the old base station.
[0053] Step 1: The UE may send a message, such as an RRCResumeRequest message to the new base station, including an identifier, such as a resume ID (also referred to as a session ID, or a context ID) , in order to resume its RRC connection. The resume ID serves as an identifier for identifying or locating the UE context that is retained by the old base station (or another entity) . Exemplarily, the resume ID may include an I-RNTI (Inactive Radio Network Temporary Identifier) of the UE. I-RNTI is a temporary identifier that can uniquely identify a UE and its context when the UE transitions to the RRC inactive (RRC_INACTIVE) state, and facilitates the efficient resumption process through, for example, an RRC resume procedure. The I-RNTI may include two components: 1) a base station (e.g., gNB) identifier component: this component identifies the specific base station that last served the UE in RRC_CONNECTED mode and placed the UE into RRC Inactive state. For example, it may encode the identity of this base station; and 2) a UE identifier: this component represents the UE identifier assigned by, for example, the last serving base station, which can be used to distinguish the UE's context within that base station. Therefore, given an I-RNTI, the specific base station that released the UE to RRC inactive state and retains the UE context may be identified based on the base station identifier component, and the UE context of the UE may then be retrieved based on the UE identifier component.
[0054] Step 2. Based on the received resume ID (e.g., I-RNTI) , the new base station identifies the old base station. The new base station may then check whether there is an Xn connection with the old base station. If there is no Xn interface connection between the new base station and the old base station, the new base station determines that it needs to retrieve the UE context from the Core Network (CN) (or a node in the CN) . It then initiates the retrieval by sending a message, such as an NGAP RAN Retrieve UE Context Request message to the CN, including the resume ID.
[0055] In some implementations, it is possible that a Network Entity (NF) may be used in place of the CN. For example, there may be an NF hosting / storing UE context.
[0056] Step 3. Upon receiving the message sent in step 2 (e.g., RAN Retrieve UE Context Request message) , the CN identifies the old base station (Last Serving base station) that holds the UE context based on the resume ID (e.g., I-RNTI) and forwards the request by sending a message, such as an NGAP CN Retrieve UE Context Request message to the old base station. This message may include the resume ID, and may optionally include a UE context release indicator.
[0057] In this step, UE context release indicator is used as an early indication indicating that the old base station may release the UE context once it fulfills the UE context retrieval request. As typically the old base station will release / flush the UE context only after the path switch is completed during the UE resumption procedure and a context release instruction is received from the CN, this early indication may improve the overall efficiency, reduce storage requirements at the old base station, and minimize signaling overhead.
[0058] Step 4. The old base station identifies / locates the UE context using the received resume ID and prepares to transfer it to the CN. The old base station may respond the request in step 3 with a response message, such as an NGAP CN Retrieve UE Context Response message to CN, which includes the UE context. Refer to earlier sections for details on the content of UE context.
[0059] If the UE context release indicator is present in the CN Retrieve UE Context Request message, the old base station will release the UE context.
[0060] In some implementations, the UE context in the response message (e.g., CN Retrieve UE Context Response message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRING or BIT STRING) , allowing the recipient (e.g., CN) to forward the UE context directly without needing to decode its content. The encoding may be based on, for example, Abstract Syntax Notation One (ASN. 1) , Type-Length-Value (TLV) encoding.
[0061] Step 5. The CN may forward the received UE context to the new base station by sending a message, such as an NGAP RAN Retrieve UE Context Response message, including the UE context.
[0062] In some implementations, the UE context in above message (e.g., RAN Retrieve UE Context Response message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRING or BIT STRING) .
[0063] Step 6. After receiving the UE context, the new base station and the UE complete the RRC connection resumption procedure. For example, the new base station may allocate resource (e.g., Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RCL) layer, and / or layer 1 resources) for PDU session (s) , to resume some or all the PDU session (s) for data transmission, and reestablish new DRB (s) for the PDU session (s) . After the connection is resumed, the new base station stores / maintains the UE context. The UE may transition to RRC_CONNECTED state for data transmission. Alternatively, the UE may remain in RRC_INACTIVE state for small packet (s) (or small data) transmission.
[0064] Step 7. The new base station initiates a Path Switch procedure with the CN to update the user plane path by sending a Path Switch Request message to the CN.
[0065] Step 8. After the Path Switch procedure is completed, uplink (UL) and downlink (DL) user data transfer resumes between the UE and the core network through the new base station.
[0066] Steps 9 and 10 are optional and apply if the CN does not include a UE context release indicator in Step 3.
[0067] Step 9. (Optional) The CN may send a message, such as an NGAP UE Context Release message to the old base station to explicitly trigger release of the UE context.
[0068] Step 10. (Optional) The old base station releases the UE context upon receiving the message in step 9.
[0069] Embodiment 2
[0070] This embodiment describes methods for handling SDT scenarios. A UE in RRC inactive state may decide to initiate an SDT for small data transmission and / or reception, and the UE is covered or served by a new base station different from the old base station that put the UE into the RRC Inactive state. The SDT procedure is considered lightweight in comparison to procedures designed for standard data transmissions involving regular-sized data packets. In this embodiment, to further optimize and improve efficiency of the SDT procedure, only SDT relevant UE context is retrieved by the new base station. That is, UE context that is not relevant to, or associated with the SDT procedure will not be retrieved and transferred.
[0071] FIG. 5 shows a non-limiting example of a method including a portion or all of the following steps.
[0072] Step 0: This step is same as step 0 in Embodiment 1, and the details are skipped for simplicity.
[0073] Step 1: This step is same as step 2 in Embodiment 1, and the details are skipped for simplicity.
[0074] Step 2: Based on the received resume ID (e.g., I-RNTI) , the new base station identifies the old base station. The new base station checks whether there is an Xn interface connection with the old base station. If there is no Xn interface connection available, the new base station determines that it needs to retrieve the UE context from the CN (or a node in the CN) . Note that in some implementations, an NF may be used in place of the CN. For example, the NF is dedicated for storing UE context.
[0075] If the UE's resume cause is for SDT (i.e., the connection resumption is triggered by SDT) , which may be indicated by the message received in step 1 (e.g., RRCResumeRequest message) , the new base station then initiates the UE context retrieval by sending a message, such as an NGAP RAN Retrieve UE Context Request message to the CN, including the resume ID, and an SDT information.
[0076] The SDT information may include at least one of the following:
[0077] · A first SDT indicator indicating that there is only one SDT packet to be transmitted (no subsequent SDT transmission is expected) ;
[0078] · A second SDT indicator indicating that there are multiple SDT packets to be transmitted (more than one SDT transmissions are expected) ; or
[0079] · A third SDT indicator indicating that an SDT transmission is expected for the UE.
[0080] Step 3: Upon receiving the message send in step 2 (e.g., RAN Retrieve UE Context Request message) , the CN identifies the old base station (Last Serving base station) that holds the UE context based on the resume ID (e.g., I-RNTI) and forwards the request by sending a message, such as an NGAP CN Retrieve UE Context Request message to the old base station. This message may include the resume ID and the SDT information.
[0081] Step 4: The old base station identifies / locates the UE context using the received resume ID and prepares to transfer it to the CN. The old base station may determine whether full UE context is required to be sent to the CN based on the SDT information (or the presence of the SDT information) . For example, if the received SDT information indicating that there is only one SDT packet to be transmitted, then the old base station may determine that only partial UE context which is relevant to the SDT transmission needs to be sent to the CN, and it will not send UE context irrelevant to the SDT transmission. Additionally, the old base station may determine a subset of SDT relevant context based on the SDT information (e.g., only selected SDT relevant context is required) . Exemplarily, the SDT relevant UE context may include UE context related to the configuration of SDT DRBs and / or SDT SRBs. After this SDT information checking, the old base station may send a response message, such as an NGAP RAN-CN UE Partial Context Transfer message to the CN, carrying SDT relevant UE context (i.e., only partial UE context is sent to the CN) .
[0082] In some implementations, the SDT relevant UE context may include at least one of the following:
[0083] · A configuration of a list of Data Radio Bearers (DRBs) that support SDT. This may include Radio Link Control (RLC) bearer configuration of each DRB, the QoS flow (s) mapped to each DRB, etc.; or
[0084] · A configuration of a list of Signaling Radio Bearers (SRBs) that support SDT. This may include RLC bearer configuration of each SRB, the QoS flow (s) mapped to each SRB, etc.
[0085] Step 5: The CN may forward the received UE context to the new base station by sending a message, such as an NGAP CN-RAN UE Partial Context Transfer message, including the UE context that is only relevant to SDT (e.g., UE context related to the configuration of SDT DRBs and / or SDT SRBs) . The SDT relevant UE context may be referred to as partial UE context (as compared to a complete copy of UE context) .
[0086] In some implementations, the UE context in above message (e.g., NGAP CN-RAN UE Partial Context Transfer message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRlING or BIT STRING) .
[0087] Step 6: After receiving the partial UE context (SDT relevant UE context) , the new base station and the UE complete the RRC connection resumption procedure. For example, the new base station may allocate resource (e.g., PDCP laye, RLC layer, and / or layer 1 resources) for SDT DRB (s) and / or SRB (s) as indicated in the partial UE context, and resume the SDT DRB(s) and / or SDT SRB (s) (e.g., as indicated in the partial UE context) for small data transmission. The small data may include, for example, small user plane data, or small Access Stratum (AS) control plane data. The UE remains in RRC_INACTIVE state for small data transmission. Note that as UE only requires SDT session, it does not need to transition to RRC_CONNECTED STATE.
[0088] Step 7. The new base station initiates a Path Switch procedure with the CN to update the user plane path by sending a Path Switch Request message to the CN.
[0089] Step 8. After the Path Switch procedure is completed, uplink (UL) and downlink (DL) small user data transfer resumes between the UE and the core network through the new base station.
[0090] Embodiment 3
[0091] In embodiments 1 and 2, the UE context retrieval / transfer is triggered by UE request (e.g., RRC resume request) . The CN first needs to request the UE context from the old base station and then forward it to the new base station. In contrast, in this embodiment, the old base station sends the full UE context to the CN at the time of releasing the UE to the RRC Inactive state. The CN stores the UE context, allowing it to directly provide the context to the new base station upon receiving a subsequent context retrieval request from the new base station, without needing to communicate the old base station again, thereby reducing signaling overhead and improving UE resumption efficiency.
[0092] FIG. 6 shows a non-limiting example of a method including a portion or all of the following steps.
[0093] Step 1: The UE is in RRC_CONNECTED state and is being served by a base station (after the UE is released by this base station, it becomes the old base station) . The base station decides to transition the UE to RRC_INACTIVE state, e.g., due to non-data transmission during this period or energy-saving reasons. The base station may send an RRC Release Request message to the UE, requesting UE to transition to RRC_INACTIVE state. This message includes a resume ID, (e.g., I-RNTI of the UE) , which will be used by UE later for resumption of the RRC connection. Note that the resume ID may be assigned by the base station.
[0094] Step 2: The base station may then notify the CN that the UE has been released to the RRC Inactive state by sending a message, such as an NGAP RRC Inactive Transition Report message to the CN. This message may include at least one: RRC state of UE (i.e., RRC Inactive) , the resume ID (e.g., I-RNTI) , or the UE context. Note that the UE context may be a complete copy of the UE context maintained by the base station (i.e., a full UE context) , or a partial copy that is only SDT relevant.
[0095] In some implementations, after the message is sent, the base station may choose to release / flush the UE context.
[0096] In some implementations, rather than notifying the CN and using the CN as a central storage for the UE context, the base station may notify a Network Function (NF) entity supporting Service Based Interface (SBI) that the UE has been released to the RRC Inactive state by sending, for example, an HTTP-based message, such as an HTTP-based RRC Inactive Transition Report message over the SBI interface. This message may include at least one of: UE's new RRC state (i.e., RRC Inactive) , the resume ID (e.g., I-RNTI) , or the UE context.
[0097] In some implementations, the UE context in above message (e.g., NGAP RRC Inactive Transition Report message, HTTP-based RRC Inactive Transition Report message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRING or BIT STRING) . Optionally, the above message may carry an additional container, which carries only SDT relevant UE context (that is encoded / encapsulated in the additional container) .
[0098] Step 3: Upon receiving the message in step 2, the CN (or the NF, depending on which entity receives the message / UE context) stores the UE context, and the associated resume ID for the UE.
[0099] Embodiment 4
[0100] In this embodiment, the old base station sends the UE context to the CN right before releasing the UE to the RRC Inactive state. The CN stores the UE context, allowing it to directly provide the context to the new base station upon receiving a subsequent context retrieval request from the new base station, without needing to communicate the old base station again, thereby reducing signaling overhead and improving UE resumption efficiency. The CN allocates a resume ID for the UE and sends it back to the old base station, this resume ID is then passed to the UE when the old base station releases the UE to RRC inactive state. The resume ID assigned by the CN has a naming scope of the entire CN.
[0101] FIG. 7 shows a non-limiting example of a method including a portion or all of the following steps.
[0102] Step 1: The UE is in RRC_CONNECTED state and is being served by a serving base station (after the UE is released by this base station, it becomes the old base station) . The serving base station decides to transition the UE to RRC_INACTIVE state, e.g., due to non-data transmission during this period or energy-saving reasons.
[0103] Before requesting the UE to transition to RRC_INACTIVE state, the serving base station notifies the CN that the UE will be released to the RRC Inactive state by sending a message, such as an NGAP RRC Inactive Transition Report message. This message may include at least one of: new RRC state of UE (i.e., RRC Inactive) , or the UE context. Note that the UE context may be a complete copy of the UE context maintained by the serving base station (i.e., a full UE context) , or a partial copy that is only SDT relevant.
[0104] In some implementations, rather than notifying the CN and using the CN as a central storage for the UE context, the serving base station may notify an NF entity that the UE is about to be released to (or transitioned to) the RRC Inactive state by sending, for example, an HTTP-based message, such as an HTTP-based RRC Inactive Transition Report message over the SBI interface. This message may include at least one of: UE's new RRC state (i.e., RRC Inactive) , or the UE context.
[0105] In some implementations, the UE context in above message (e.g., NGAP RRC Inactive Transition Report message, HTTP-based RRC Inactive Transition Report message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRING or BIT STRING) . Optionally, the above message may carry an additional container, which carries only SDT relevant UE context (that is encoded / encapsulated in the additional container) .
[0106] Step 2: Upon receiving the message in step 1, the CN (or the NF, depending on which entity receives the message) stores the UE context, and allocate a unique resume ID for the UE.
[0107] Step 3. the CN sends a response message to the serving base station, this message may include the resume ID allocated by the CN.
[0108] In some implementation, the NF entity sends a HTTP based response a message to the serving base station via SBI interface, this message includes the resume ID allocated by the NF entity.
[0109] Step 4: The serving base station sends a message, such as an RRC Release Request message to the UE, to transition the UE to RRC_INACTIVE state. This message may include the resume ID allocated by the CN or the NF entity, which will be used by UE later for resumption of the RRC connection.
[0110] The serving base station may release the UE context.
[0111] Embodiment 5
[0112] In embodiments 1 and 2, when a UE in RRC inactive state attempts to resume its connection, the CN first needs to request the UE context from the old base station and then forward it to the new base station. In embodiment 3 or 4, however, the CN (or an NF) has already stored the UE context, allowing it to directly provide the UE context to the new base station, without needing to communicate with the old base station again, thereby reducing signaling overhead and improving UE resumption efficiency.
[0113] In this embodiment, the new base station may request UE context from the CN (or the NF) without CN / NF further query the old base station. This embodiment is applicable irrespective of whether an Xn interface connection exists between the new base station and the old base station.
[0114] FIG. 8 shows a non-limiting example of a method including a portion or all of the following steps.
[0115] Step 0: This step is pre-condition. The UE has been released to the RRC Inactive state by the old base station (last serving base station) . The UE is then covered by a new base station (new serving base station, or receiving base station) due to, for example, UE movement. The UE decides to resume its connection with the new base station, for example, for data transmission.
[0116] Step 1: The UE may send a message, such as an RRCResumeRequest message to the new base station, including a resume ID, in order to resume the RRC connection. The resume ID may be allocated by the old base station (e.g., I-RNTI) as described in embodiments 1-3, or may be allocated by the CN as described in embodiment 4. Alternatively, in some implementations, the resume ID may be allocated by an NF entity as described in embodiment 4.
[0117] Step 2: the new base station may initiate the UE context retrieval process by sending a message, such as an NGAP RAN Retrieve UE Context Request message to the CN (or NF, is the NF stores the UE context) , including the resume ID (e.g., I-RNTI allocated by the old base station, or an ID allocated by the CN / NF) .
[0118] If the UE's resume cause is for small data transmission, single or multiple small packets are indicated based on the information in the received message received in step 1 (e.g., RRCResumeRequest message) , the new base station may additionally include SDT information in the UE context request message. The SDT information may be the same as defined in embodiment 2.
[0119] In some implementations, the new base station initiates the UE context retrieval process by sending, for example, an HTTP based message, such as an HTTP based RAN Retrieve UE Context Request message to an NF entity via SBI interface. This message may include the resume ID and may optionally include SDT information.
[0120] Step 3: In case that the CN is used to store the UE context (which means the new base station send UE context retrieval request to the CN) , the CN may identify / lookup the UE context using the received resume ID and prepare to transfer it to the new base station. If SDT information (e.g., single packet transmission) is received in the UE context retrieval request message, the CN determines, based on the SDT information, that only a partial UE context (i.e., only SDT relevant UE context) is needed for SDT purposes. Otherwise, the CN decides to transfer the full UE context to the new base station.
[0121] The CN then may then respond with a message, such as an NGAP response message to the new base station, including either the SDT relevant UE context (e.g., which is related to configuration of SDT DRBs / SRBs) or the full UE context.
[0122] Similarly, in case that the NF entity is used to store the UE context, the NF entity sends a response message, such as an HTTP based response message via SBI interface to the new base station, including either the SDT relevant UE context (e.g., which is related to configuration of SDT DRBs / SRBs) or the full UE context.
[0123] In some implementations, even if no SDT information is sent in step 2, the CN may by default only transfer SDT relevant UE context.
[0124] In some implementations, the full UE context or the SDT relevant UE context in the response message (e.g., NGAP response message, HTTP based response message) may be encoded as, or encapsulated in a container (e.g., an OCTET STRING or BIT STRING)
[0125] Step 4: After receives the UE context, the new base station and the UE complete the RRC connection resumption procedure (e.g., following 3GPP or other standard specifications) .
[0126] Step 5. The new base station initiates a Path Switch procedure with the CN to update the user plane path by sending a Path Switch Request message to the CN.
[0127] Step 6. After the Path Switch procedure is completed, uplink (UL) and downlink (DL) user data transfer resumes between the UE and the core network through the new base station. If SDT transmission is the cause for the UE connection resumption, then UE may perform SDT transmission.
[0128] In this disclosure, a resume ID may also referred to as a session ID, or a context ID.
[0129] A method performed by a first network element according to embodiments in this disclosure includes a portion or all of the following steps: step 1: transmitting, to a second network element, a first message carrying at least one of: context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context; a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; or a session identifier identifying the context of the wireless device.
[0130] In any portion or combination of the implementations above, the method further comprising: receiving, from the second network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the session identifier identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device, wherein the first message is a response to the second message.
[0131] In any portion or combination of the implementations above, the session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.
[0132] In any portion or combination of the implementations above, the SDT information comprises at least one of: a first SDT indicator indicating that there is only one SDT packet to be transmitted; a second SDT indicator indicating that there are multiple SDT packets to be transmitted; or a third SDT indicator indicating that an SDT transmission is expected for the wireless device.
[0133] In any portion or combination of the implementations above, when the second message carries the SDT information associated with the wireless device, the first message as a response to the second message only comprises SDT relevant context and not a complete context for the wireless device, and the SDT relevant context comprises at least one of: a configuration of a list of Data Radio Bearers (DRBs) that support SDT; or a configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.
[0134] In any portion or combination of the implementations above, the wireless device has been released to an inactive state by the first network element.
[0135] In any portion or combination of the implementations above, the context of the wireless device comprises at least one of: identification information; Radio Access Technology (RAT) ; frequency selection priority; radio capability information; mobility restriction area for the wireless device; location and positioning information; session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information; UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; or connection and mobility information.
[0136] In any portion or combination of the implementations above, before transmitting the first message, the method further comprises: transmitting a third message to the wireless device to release the wireless device to an RRC inactive state, the third message comprising the session identifier identifying the context of the wireless device.
[0137] In any portion or combination of the implementations above, the method further comprising releasing the context of the wireless device.
[0138] In any portion or combination of the implementations above, the method further comprising: receiving, from the second network element, a third message as response to the first message, the third message comprising a second session identifier assigned by the second network element for identifying the context of the wireless device; and transmitting, to the wireless device, a fourth message to release the wireless device to an RRC inactive state, the fourth message comprising the second session identifier.
[0139] In any portion or combination of the implementations above, the first network element comprises a base station; and the second network element comprises at least one of: a core network; a core network node; or a Network Function (NF) supporting Service Based Interface (SBI) .
[0140] A method performed by a first network element according to embodiments in this disclosure includes a portion or all of the following steps: step 1: receiving, from a second network element, a first message carrying at least one of: context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context; a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; or a first session identifier identifying the context of the wireless device assigned by the second network element.
[0141] In any portion or combination of the implementations above, the first session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.
[0142] In any portion or combination of the implementations above, before receiving the first message, the method further comprises: receiving, from a third network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the first session identifier identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device; and transmitting, to the second network element, a third message requesting the context of the wireless device, the third message carrying at least one of: the first session identifier; or the SDT information associated with the wireless device, wherein the first message is a response to the third message.
[0143] In any portion or combination of the implementations above, after receiving the first message, the method further comprising: receiving, from a third network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the first session identifier identifying the context of the wireless device; a second session identifier assigned by the first network element for identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device.
[0144] In any portion or combination of the implementations above, the SDT information comprises at least one of: a first SDT indicator indicating that there is only one SDT packet to be transmitted; a second SDT indicator indicating that there are multiple SDT packets to be transmitted; or a third SDT indicator indicating that an SDT transmission is expected for the wireless device.
[0145] In any portion or combination of the implementations above, when the second message carries the SDT information associated with the wireless device, the first message as a response to the third message only comprises SDT relevant context and not a complete context for the wireless device, and the SDT relevant context comprises at least one of: a configuration of a list of Data Radio Bearers (DRBs) that support SDT; or a configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.
[0146] In any portion or combination of the implementations above, before receiving the second message, the wireless device has been released to an inactive state by the second network element.
[0147] In any portion or combination of the implementations above, the method further comprising: transmitting, to the third network element, a third message as a response to the second message, the second message comprising the context of the wireless device.
[0148] In any portion or combination of the implementations above, the method further comprising: when the second message carries the SDT information, transmitting, to the third network element, a third message as a response to the second message, the second message comprising SDT relevant context, and the SDT relevant context comprising at least one of: a configuration of a list of DRBs that support SDT; or a configuration of a list of SRBs that support SDT.
[0149] In any portion or combination of the implementations above, the context of the wireless device comprises at least one of: identification information; Radio Access Technology (RAT) ; frequency selection priority; radio capability information; mobility restriction area for the wireless device; location and positioning information; session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information; UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; or connection and mobility information.
[0150] In any portion or combination of the implementations above, the method further comprising storing the context of the wireless device and the first session identifier.
[0151] In any portion or combination of the implementations above, the method further comprising: storing the context of the wireless device; allocating a second session identifier for identifying the context of the wireless device; and transmitting, to the second network element, a third message as a response to the first message, the third message carrying the second session identifier.
[0152] A method performed by a first network element according to embodiments in this disclosure includes a portion or all of the following steps: step 1: transmitting, to a second network element, a first message requesting context of a wireless device that is in an inactive state, the first message carrying at least one of: a first session identifier identifying the context of the wireless device; a second session identifier assigned by the second network element for identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device.
[0153] In any portion or combination of the implementations above, there is no Xn interface between the first network element and a third network element, wherein the third network element is a last serving base station for the wireless device and transitions the wireless device to the inactive state.
[0154] In any portion or combination of the implementations above, the method further comprising receiving from the second network element, one of: the context of the wireless device; or SDT relevant context of the wireless device.
[0155] In any portion or combination of the implementations above, the method further comprising: when the first message carrying the SDT information, receiving, from the second network element, SDT relevant context of the wireless device.
[0156] In any portion or combination of the implementations above, the SDT relevant context comprises at least one of: a configuration of a list of Data Radio Bearers (DRBs) that support SDT; or a configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.
[0157] In any portion or combination of the implementations above, the first session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.
[0158] In any portion or combination of the implementations above, the context of the wireless device comprises at least one of: identification information; Radio Access Technology (RAT) ; frequency selection priority; radio capability information; mobility restriction area for the wireless device; location and positioning information; session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information; UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; or connection and mobility information.
[0159] In any portion or combination of the implementations above, at least one of following conditions satisfies: the first network element comprising a first base station; the second network element comprising at least one of: a core network; a core network node; or a Network Function (NF) supporting Service Based Interface (SBI) ; or the third network element comprising a second base station.
[0160] In this disclosure, message types and / or message names (e.g., as shown in FIGs. 4-8) are for exemplary purpose only. The message may be a currently message defined in various wireless communication technologies, protocols, or standards. Alternatively, the message may be a newly defined / created message. Different message types and / or message names may be chosen in implementation, and should still be covered by this disclosure, as far as the underlying principle is the same, for example, if the messages are used for a same purpose.
[0161] In this disclosure, a single information element in a message (i.e., information carried in a message) may be split into multiple information elements. Multiple information element may also be combined into a single information element. For example, two parameters sent in separate messages (even these separate messages are described in different embodiment) may be combined into a single message, if there is no conflict. For another example, two parameters sent in one message may be split and sent in two separate messages.
[0162] In this disclosure, the steps in each embodiment are for illustration purposes only and other alternatives may be derived based on the disclosed embodiments as desired. For example, only part of the steps may need to be performed. For another example, the sequence of the steps may be adjusted. For another example, several steps may be combined (e.g., several messages may be combined in one message) . For yet another example, a single step may be split (e.g., one message may be sent via two sub-messages) .
[0163] The description and accompanying drawings above provide specific example embodiments and implementations. The described subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein. A reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, systems, or non-transitory computer-readable media for storing computer codes. Accordingly, embodiments may, for example, take the form of hardware, software, firmware, storage media or any combination thereof. For example, the method embodiments described above may be implemented by components, devices, or systems including memory and processors by executing computer codes stored in the memory.
[0164] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment / implementation” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment / implementation” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter includes combinations of example embodiments in whole or in part.
[0165] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and / or, ” as used herein may include a variety of meanings that may depend at least in part on the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for the existence of additional factors not necessarily expressly described, again, depending at least in part on context.
[0166] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.
[0167] It can be seen that those skilled in the art should understand that functional modules / units in all or part of the steps of the method, the system, and the apparatus disclosed above may be implemented as software (which may be implemented by computer program codes executable by a computing apparatus) , firmware, hardware and appropriate combinations thereof. In the hardware implementation, the division of the functional modules / units mentioned above may not correspond to the division of physical components. For example, one physical component may have multiple functions, or one function or step may be performed jointly by several physical components. Some or all physical components may be implemented as software executed by processors such as central processing units, digital signal processors or microcontrollers, may be implemented as hardware, or may be implemented as integrated circuits such as application-specific integrated circuits.
[0168] In addition, as is known to those of ordinary skill in the art, a communication medium generally includes computer-readable instructions, data structures, computer program modules, or other data in modulated data signals such as carriers or other transmission mechanisms and may include any information delivery medium. Therefore, the present application is not limited to any particular combination of hardware and software.
[0169] The above content is a more detailed description of the embodiments of the present disclosure in conjunction with specific implementations, and the specific implementation of the present application is not limited to the description. For those of ordinary skill in the art to which the present application pertains, a number of simple deductions or substitutions may be made without departing from the concept of the present application and should fall within the scope of the present application.
[0170] Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.
Claims
A method for wireless communication, performed by a first network element, comprising transmitting, to a second network element, a first message carrying at least one of:context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context;a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; ora session identifier identifying the context of the wireless device.The method of claim 1, further comprising:receiving, from the second network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the session identifier identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device, wherein the first message is a response to the second message.The method of claim 2, wherein the session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.The method of claim 2, wherein the SDT information comprises at least one of:a first SDT indicator indicating that there is only one SDT packet to be transmitted;a second SDT indicator indicating that there are multiple SDT packets to be transmitted; ora third SDT indicator indicating that an SDT transmission is expected for the wireless device.The method of claim 2, wherein, when the second message carries the SDT information associated with the wireless device, the first message as a response to the second message only comprises SDT relevant context and not a complete context for the wireless device, and the SDT relevant context comprises at least one of:a configuration of a list of Data Radio Bearers (DRBs) that support SDT; ora configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.The method of claim 2, wherein the wireless device has been released to an inactive state by the first network element.The method of any one of claims 1-3, wherein the context of the wireless device comprises at least one of:identification information;Radio Access Technology (RAT) ;frequency selection priority;radio capability information;mobility restriction area for the wireless device;location and positioning information;session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information;UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; orconnection and mobility information.The method of claim 1, wherein, before transmitting the first message, the method further comprises:transmitting a third message to the wireless device to release the wireless device to an RRC inactive state, the third message comprising the session identifier identifying the context of the wireless device.The method of claim 8, further comprising releasing the context of the wireless device.The method of claim 1, further comprising:receiving, from the second network element, a third message as response to the first message, the third message comprising a second session identifier assigned by the second network element for identifying the context of the wireless device; andtransmitting, to the wireless device, a fourth message to release the wireless device to an RRC inactive state, the fourth message comprising the second session identifier.The method of any one of claims 1-10, wherein:the first network element comprises a base station; andthe second network element comprises at least one of: a core network; a core network node; or a Network Function (NF) supporting Service Based Interface (SBI) .A method for wireless communication, performed by a first network element, comprising receiving, from a second network element, a first message carrying at least one of:context of a wireless device or Small Data Transmission (SDT) relevant context of the wireless device, the SDT relevant context being a subset of the context;a Radio Resource Control (RRC) state of the wireless device indicating that the wireless device is in an inactive state; ora first session identifier identifying the context of the wireless device assigned by the second network element.The method of claim 12, wherein the first session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.The method of claim 12, wherein, before receiving the first message, the method further comprises:receiving, from a third network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the first session identifier identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device; andtransmitting, to the second network element, a third message requesting the context of the wireless device, the third message carrying at least one of: the first session identifier; or the SDT information associated with the wireless device, wherein the first message is a response to the third message.The method of claim 12, wherein, after receiving the first message, the method further comprising:receiving, from a third network element, a second message requesting the context of the wireless device, the second message carrying at least one of: the first session identifier identifying the context of the wireless device; a second session identifier assigned by the first network element for identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device.The method of claim 14 or 15, wherein the SDT information comprises at least one of:a first SDT indicator indicating that there is only one SDT packet to be transmitted;a second SDT indicator indicating that there are multiple SDT packets to be transmitted; ora third SDT indicator indicating that an SDT transmission is expected for the wireless device.The method of claim 14, wherein, when the second message carries the SDT information associated with the wireless device, the first message as a response to the third message only comprises SDT relevant context and not a complete context for the wireless device, and the SDT relevant context comprises at least one of:a configuration of a list of Data Radio Bearers (DRBs) that support SDT; ora configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.The method of claim 14 or 15, wherein, before receiving the second message, the wireless device has been released to an inactive state by the second network element.The method of claim 14 or 15, further comprising:transmitting, to the third network element, a third message as a response to the second message, the second message comprising the context of the wireless device.The method of claim 14 or 15, further comprising:when the second message carries the SDT information, transmitting, to the third network element, a third message as a response to the second message, the second message comprising SDT relevant context, and the SDT relevant context comprising at least one of:a configuration of a list of DRBs that support SDT; ora configuration of a list of SRBs that support SDT.The method of claim 12, wherein the context of the wireless device comprises at least one of:identification information;Radio Access Technology (RAT) ;frequency selection priority;radio capability information;mobility restriction area for the wireless device;location and positioning information;session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information;UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; orconnection and mobility information.The method of claim 12, further comprising storing the context of the wireless device and the first session identifier.The method of claim 12, further comprising:storing the context of the wireless device;allocating a second session identifier for identifying the context of the wireless device; andtransmitting, to the second network element, a third message as a response to the first message, the third message carrying the second session identifier.A method for wireless communication, performed by a first network element, the method comprising:transmitting, to a second network element, a first message requesting context of a wireless device that is in an inactive state, the first message carrying at least one of: a first session identifier identifying the context of the wireless device; a second session identifier assigned by the second network element for identifying the context of the wireless device; or Small Data Transmission (SDT) information associated with the wireless device.The method of claim 24, wherein there is no Xn interface between the first network element and a third network element, wherein the third network element is a last serving base station for the wireless device and transitions the wireless device to the inactive state.The method of claim 24, further comprising receiving from the second network element, one of:the context of the wireless device; orSDT relevant context of the wireless device.The method of claim 24, further comprising:when the first message carrying the SDT information, receiving, from the second network element, SDT relevant context of the wireless device.The method of claim 26 or 27, wherein the SDT relevant context comprises at least one of:a configuration of a list of Data Radio Bearers (DRBs) that support SDT; ora configuration of a list of Signaling Radio Bearers (SRBs) that support SDT.The method of any one of claims 24-28, wherein the first session identifier comprises an Inactive Radio Network Temporary Identifier (I-RNTI) of the wireless device.The method of any one of claims 24-28, wherein the context of the wireless device comprises at least one of:identification information;Radio Access Technology (RAT) ;frequency selection priority;radio capability information;mobility restriction area for the wireless device;location and positioning information;session and bearer context comprising at least one of: a configuration for a list of Protocol Data Unit (PDU) sessions; Quality of Service (QoS) flows information; Data Radio Bearer (DRB) information; Signal Radio Bearer (SRB) information;UE security information comprising at least one of: ciphering and integrity protection keys, security algorithms selected; orconnection and mobility information.The method of any one of claims 24-30, wherein at least one of following conditions satisfies:the first network element comprising a first base station;the second network element comprising at least one of: a core network; a core network node; or a Network Function (NF) supporting Service Based Interface (SBI) ; orthe third network element comprising a second base station.A network element comprising a memory for storing computer instructions and a processor in communication with the memory, wherein, when the processor executes the computer instructions, the processor is configured to implement a method in any one of claims 1-31.A computer program product comprising a non-transitory computer-readable program medium with computer code stored thereupon, the computer code, when executed by one or more processors, causing the one or more processors to implement a method of any one of claims 1-31.
