Managing small data transmission configurations in mobile scenarios
By optimizing SDT configuration management in RAN nodes, the delay and efficiency problems of UE transition from inactive state to connection state are solved, and efficient data communication is achieved.
Patent Information
- Application Number
- CN202380030718.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-11
- Filing Date
- 2023-02-10
- Publication Date
- 2024-11-08
AI Technical Summary
The failure of the prior art to effectively manage small data transmission (SDT) configurations in radio access networks (RANs), resulting in data communication delays and network inefficiency, especially when user equipment (UE) transitions from inactive to connected states hour.
The RAN node receives the SDT configuration in the inactive state of the UE and discards some configurations if necessary to optimize the communication process and ensure data transmission efficiency and delay. The specific method includes receiving the SDT configuration during the handover process, discarding unnecessary configurations, and communicating on a UE context basis, or using a non-SDT configuration for subsequent communication when the UE transitions to a connection state, and sending handover preparation information to the target node. Exclude SDT configuration.
By optimizing SDT configuration management, data communication delay is reduced, network efficiency is improved, and efficient data transmission by UEs in different states is ensured.
Smart Images

Figure FT_1 
Figure FT_2 
Figure FT_3
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, and more particularly to communication of uplink and / or downlink data between a user equipment (UE) and a radio access network (RAN) when the UE is operating in an inactive or idle state associated with a protocol for controlling radio resources. Background Art
[0002] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors (to the extent that it is described in this background section) and aspects of the specification that might not have been considered prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0003] In general, a base station operating a cellular radio access network (RAN) uses a specific radio access technology (RAT) and multiple layers of a protocol stack to communicate with a user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the medium access control (MAC) sublayer, which in turn provides a logical channel to the radio link control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.
[0004] The RRC sublayer defines: an RRC_IDLE state, in which the UE does not have an active radio connection with a base station; an RRC_CONNECTED state, in which the UE has an active radio connection with a base station; and an RRC_INACTIVE state, which allows the UE to transition back to the RRC_CONNECTED state more quickly using RAN-level base station coordination and RAN paging procedures. In some cases, a UE in the RRC_INACTIVE state has only a relatively small packet to transmit. For situations such as these, 3GPP is discussing a small data transfer (SDT) procedure to enable 5G NR (New Radio), a wireless communication standard, to support data transmission for UEs operating in the RRC_INACTIVE state (i.e., without requiring the UE to transition to the RRC_CONNECTED state).
[0005] SDT is enabled on a radio bearer basis and is initiated by the UE only when: (1) the amount of uplink (UL) data waiting to be transmitted (on all radio bearers for which SDT is enabled) is below a configured threshold, (2) the downlink (DL) reference signal power (RSRP) is above a configured threshold, and (3) valid SDT resources are available. The SDT procedure can be initiated by the UE through a transmission on the random access channel (RACH) (i.e., random access SDT (RA-SDT)) or type 1 configured grant (CG) resources (i.e., CG-SDT). For RA-SDT, the network configures 2-step and / or 4-step random access resources for SDT. In RA-SDT, the UE can send an initial transmission including data in message 3 (Msg3) of a 4-step random access procedure or in the payload of message A (MsgA) of a 2-step random access procedure. After the random access procedure is completed, the network can then schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.
[0006] CG-SDT can only be initiated with valid UL timing alignment. The UE maintains UL time alignment based on the SDT-specific time alignment timer configured by the network and the DL RSRP of the configured number of highest-ranked synchronization signal blocks (SSBs). When the SDT-specific time alignment timer expires, the CG resources are released. When initiating CG-SDT, the UE uses the CG configuration to send an initial transmission including data on the CG opportunity, and the network can use dynamic grants to schedule subsequent UL transmissions on future CG resource opportunities. During CG-SDT, dynamic assignments are used to schedule DL transmissions. The UE can initiate subsequent UL transmissions only after receiving confirmation of the initial UL transmission from the network.
[0007] However, it is unclear how a base station of a RAN (including a distributed base station having a central unit (CU) and at least one distributed unit (DU)) manages the SDT configuration for a UE during a handover process. Failure to properly manage the SDT configuration during a handover may result in data communication delays and / or other network inefficiencies. Summary of the invention
[0008] In various implementations of the present disclosure, a RAN node (eg, a base station, or a CU of a distributed base station) performs operations to manage configurations (eg, SDT configurations) for a UE.
[0009] In a first aspect of the disclosure, during a handover procedure or a UE context retrieval procedure in which the first RAN node is a target node and the second RAN node is a source node, the first RAN node discards at least a portion of an SDT configuration received from the second RAN node.
[0010] In some implementations, the first RAN node receives an SDT configuration and a UE context from the second RAN node, and discards the SDT configuration but retains the UE context for use in communicating with the UE. Alternatively, the first RAN node may discard only a portion of the SDT configuration (e.g., the SDT DU configuration) while retaining another portion of the SDT configuration (e.g., the SDT CU configuration).
[0011] In other implementations, the first RAN node receives handover preparation information including at least one non-SDT configuration and an SDT configuration for the UE, and discards the SDT configuration but retains the non-SDT configuration.
[0012] In a second aspect of the present disclosure, during a handover procedure or a UE context retrieval procedure in which a first RAN node is a source node and a second RAN node is a target node, the first RAN node includes at least one non-SDT configuration in handover preparation information sent by the first RAN node to the second RAN node, but excludes the SDT configuration from the handover preparation information.
[0013] In a third aspect of the present disclosure, the CU of a distributed base station sends handover preparation information to a RAN node, wherein the handover preparation information excludes or includes configuration (e.g., SDT configuration) based on whether the RAN node is a DU or not a DU (e.g., a CU or other base station).
[0014] In one aspect, a method for managing configuration information for SDT operation is performed by a first RAN node. The method includes receiving an SDT configuration for a UE to use when the UE operates in an inactive state from a second RAN node during a handover procedure from the second RAN node to the first RAN node. The method also includes discarding at least a portion of the SDT configuration and communicating with the UE operating in the inactive state after the handover procedure or the UE context retrieval procedure.
[0015] In another aspect, a method for managing configuration information for SDT operation is performed by a first RAN node. The method includes: communicating with a UE in an inactive state using an SDT configuration, transitioning the UE from the inactive state to a connected state, communicating with the UE in the connected state using a non-SDT configuration, and determining to hand over the UE to a second RAN node. The method also includes: in response to the determination, sending handover preparation information to the second RAN node, the handover preparation information including the non-SDT configuration and excluding the SDT configuration.
[0016] In another aspect, a method for managing configuration information is performed by a CU of a distributed base station in a RAN. The method includes: communicating with a UE, and sending handover preparation information to a RAN node. When the RAN node is another base station or another CU, the handover preparation information includes a configuration for the UE to use when communicating with the RAN. When the RAN node is a DU, the handover preparation information excludes the configuration.
[0017] In one aspect, a method of managing configuration information for small data transfer (SDT) operations performed by a first radio access network (RAN) node includes: receiving a radio resource control (RRC) message from a user equipment (UE); receiving an SDT configuration for the UE to use when the UE operates in an RRC inactive state from the second RAN node during a handover process from the second RAN node to the first RAN node; and, after the handover process, communicating with the UE based on a UE context of the UE operating in the RRC inactive state.
[0018] In another aspect, a method for managing configuration information for a small data transfer (SDT) operation performed by a first radio access network (RAN) node includes: communicating with a user equipment (UE) operating in a radio resource control (RRC) inactive state using an SDT configuration; transitioning the UE from the RRC inactive state to an RRC connected state; communicating with the UE operating in the RRC connected state using a non-SDT configuration; determining to hand over the UE to a second RAN node; and in response to the determination, sending handover preparation information to the second RAN node, the handover preparation information excluding the SDT configuration. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] FIG1A is a block diagram of an example wireless communication system in which user devices and base stations of the present disclosure may implement techniques of the present disclosure (e.g., for reducing latency in data communications);
[0020] FIG. 1B is a block diagram of an example base station in which a centralized unit (CU) and a distributed unit (DU) may operate in the system of FIG. 1A ;
[0021] FIG2A is a block diagram of an example protocol stack according to which the UE of FIG1A communicates with a base station;
[0022] FIG2B is a block diagram of an example protocol stack according to which the UE of FIG1A communicates with the CU and the DU;
[0023] 3 to 6 illustrate several scenarios in which the apparatus of FIGS. 1A to 2B can manage small data transmission configurations in mobile scenarios according to the techniques of this disclosure; and
[0024] FIGS. 7-11 illustrate several methods that may be implemented by one or more of the devices of FIGS. 1A-2B for managing small data transmission configurations in mobile scenarios according to the techniques of this disclosure. DETAILED DESCRIPTION
[0025] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure to manage early data communications and to transition the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, and unless the context clearly indicates a more specific meaning, small data communications may refer to a small data transfer (SDT) from a network perspective (i.e., SDT in the downlink direction), or SDT from a UE perspective (i.e., SDT in the uplink direction).
[0026] 1A , an example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the CN 110. For example, the CN 110 may be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.
[0027] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104, 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).
[0028] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally, UPF 162 is configured to pass user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.
[0029] As illustrated in FIG. 1A , base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or handover from one of cells 124 and 126 to the other. In order to exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.
[0030] As discussed in detail below, the UE 102 and / or the RAN 105 may utilize the techniques of this disclosure when a radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 is operating in an inactive or idle state of a protocol for controlling radio resources between the UE 102 and the RAN 105. For clarity, the following examples relate to the RRC_INACTIVE or RRC_IDLE states of the RRC protocol.
[0031] As used herein, and unless a more specific meaning is indicated from the context of use, the term "data" or "data packet" may refer to signaling, control plane information at a protocol layer for controlling radio resources (e.g., RRC), controlling mobility management (MM), controlling session management (SM), or non-signaling, non-control plane information at one or more protocol layers above the layer of a protocol for controlling radio resources (e.g., RRC), above the layer of a protocol for controlling MM, above the layer of a protocol for controlling SM, and / or above the layer of a protocol for controlling quality of service (QoS) flows (e.g., Service Data Adaptation Protocol (SDAP)). The data to which the UE and / or RAN applies the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. Further, as discussed below, in some implementations, the UE 102 applies these techniques only if the size of the data is below a certain threshold. It should also be understood that as used herein (and unless the context of its usage indicates a more specific meaning), the term "configuration" can refer to a complete configuration, or to a subset of the parameters of a complete configuration (e.g., an "incremental" or other partial configuration that can augment an existing configuration without completely replacing the existing configuration).
[0032] In the example scenario discussed below, UE 102 transitions to RRC_INACTIVE or RRC_IDLE state, selects a cell of base station 104, and exchanges data with base station 104 via base station 106 or directly with base station 104 without transitioning to RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for UL transmission in RRC_INACTIVE or RRC_IDLE state, UE 102 may apply one or more security functions to UL data packets, generate a first UL protocol data unit (PDU) including a security-protected packet, include a UL RRC message together with the first UL PDU in a second UL PDU, and send the second UL PDU to RAN 105. UE 102 includes a UE identity / identifier (ID) of UE 102 in the UL RRC message. RAN 105 may identify UE 102 based on the UE ID. In some implementations, the UE ID may be an inactive radio network temporary identifier (I-RNTI), a recovery ID, or a non-access stratum (NAS) ID. The NAS ID can be an S-Temporary Mobile Subscriber Identity (S-TMSI) or a Globally Unique Temporary Identifier (GUTI).
[0033] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 may generate a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 may encrypt data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 may send the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.
[0034] In some implementations, the data is a UL service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (e.g., a UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which may be associated with a media access control (MAC) layer. Therefore, in these cases, the UE 102 sends the protected UL PDCP PDU in the UL MAC PDU. In some implementations, the UE 102 may include the UL RRC message in the UL MAC PDU. In other implementations, the UE 102 may not include the UL RRC message in the UL MAC PDU. In this case, the UE 102 may not include the UE ID of the UE 102 in the UL MAC PDU that does not include the UL RRC message. In yet other implementations, the UE 102 may include the UL PDCP PDU in the UL RLC PDU, and then include the UL RLC PDU in the UL MAC PDU. In some implementations where the UE 102 includes the UL RRC message in the UL MAC PDU, the UE 102 generates an RRC MAC-I and includes the RRC MAC-I in the UL RRC message. For example, the RRC MAC-I may be a resumeMAC-I field, as specified in 3GPP specification 38.331. In other implementations, the UE 102 may utilize an integrity key (e.g., K RRCintThe RRC MAC-I is obtained from the UL RRC message using a key, an integrity protection algorithm, and parameters such as COUNT (e.g., a 32-bit, 64-bit, or 128-bit value), BEARER (e.g., a 5-bit value), and DIRECTION (e.g., a 1-bit value).
[0035] In other implementations, the data is a UL SDU of NAS. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (such as a NAS PDU), which may be associated with a NAS layer. For example, the NAS layer may be an MM sublayer or an SM sublayer of a 5G, Evolved Packet System (EPS), or 6G. The UE 102 may then include the UL NASPDU in a second UL PDU (such as a UL RRC message). Thus, in these cases, the UE 102 sends the (first) protected UL NAS PDU in the UL RRC message. In some implementations, the UE 102 may include the UL RRC message in a UL MAC PDU and send the UL MAC PDU to a base station (e.g., base station 104 or 106) via a cell (e.g., cell 124 or 126). In this case, the UE 102 may not include the RRC MAC-I in the UL RRC message. Alternatively, the UE 102 may include the RRC MAC-I as described above.
[0036] In some implementations, the UL RRC message described above may be a common control channel (CCCH) message, an RRC recovery request message, or an RRC early data request message. The UL RRC message may include the UE ID of the UE 102 as described above.
[0037] More generally, the UE 102 may protect data using ciphering and / or integrity protection, include the protected data as a security-protected packet in a first UL PDU, and send the first UL PDU to the RAN 105 in a second UL PDU.
[0038] In some scenarios and implementations, the base station 106 may retrieve the UE ID of the UE 102 from the UL RRC message and identify the base station 104 as the destination of the data in the first UL PDU based on the determined UE ID. In one example implementation, the base station 106 retrieves the first UL PDU from the second UL PDU and sends the first UL PDU to the base station 104. The base station 104 then retrieves the security-protected packet from the first UL PDU, applies one or two security functions to decrypt the data and / or check integrity protection, and sends the data to the CN 110 (e.g., SGW 112, UPF 162, MME 114, or AMF 164) or an edge server. In some implementations, the edge server may operate within the RAN 105. More specifically, the base station 104 derives at least one security key from the UE context information of the UE 102. The base station 104 then retrieves the data from the security-protected packet by using the at least one security key and sends the data to the CN 110 or the edge server. When the security-protected packet is an encrypted packet, the base station 104 obtains data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 104 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.
[0039] In another implementation, the base station 106 retrieves the security-protected packet from the first UL PDU and performs a retrieve UE context procedure with the base station 104 to obtain UE context information of the UE 102 from the base station 104. Then, the base station 106 derives at least one security key from the UE context information. Thereafter, the base station 106 retrieves data from the security-protected packet by using at least one security key and sends the data to the CN 110 (e.g., UPF 162) or an edge server. When the security-protected packet is an encrypted packet, the base station 106 obtains the data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 106 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 106 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The base station 106 then determines whether the MAC-I is valid for the data. If the base station 106 determines that the MAC-I is valid, the base station 106 retrieves the data and forwards the data to the CN 110. However, if the base station 106 determines that the MAC-I is invalid, the base station 106 discards the packet.
[0040] In other scenarios and implementations, the base station 104 can retrieve the UE ID of the UE 102 from the UL RRC message and identify that the base station 104 stores the UE context information of the UE 102. Therefore, the base station 104 retrieves the security-protected packet from the first UL PDU, retrieves the data from the security-protected packet, and sends the data to the CN 110 or the edge server, as described above.
[0041] Further, in some implementations and scenarios, the RAN 105 sends data in the DL direction to the UE 102 operating in the RRC_INACTIVE or RRC_IDLE state.
[0042] In one implementation, when the base station 104 determines that data is available for downlink transmission to a UE 102 currently operating in an RRC_INACTIVE or RRC_IDLE state, the base station 104 may apply at least one security function to the data to generate a security-protected packet, generate a first DL PDU including the security-protected packet, and include the first DLPDU in a second DL PDU. In order to protect the data, the base station 104 may apply a security function (e.g., integrity protection and / or encryption) to the DL data. More particularly, when integrity protection is enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data, so that the security-protected packet includes the DL data and the MAC-I. When encryption is enabled, the base station 104 may encrypt the data to generate an encrypted packet, so that the security-protected packet is an encrypted packet. Further, when both integrity protection and encryption are enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. In some implementations, the base station 104 generates a first DL PDU (such as a DL PDCP PDU) using the security-protected packet, includes the first DL PDU in a second DL PDU (e.g., a DL MAC PDU) associated with a MAC layer, for example, and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 104 includes the DL PDCP PDU in the DL RLC PDU, includes the DL RLC PDU in the DL MAC PDU, and sends the DL MAC PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state.
[0043] In another implementation, the base station 104 sends the first DL PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the first DL PDU and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 106 generates a DL RLC PDU including the first DL PDU and includes the DL RLC PDU in the second DL PDU. In yet another implementation, the base station 104 includes the first DL PDU in the DL RLC PDU and sends the DL RLC PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the DL RLC PDU and sends the second DL PDU to the UE 102.
[0044] In some implementations, a base station (i.e., base station 104 or 106) generates downlink control information (DCI) and a cyclic redundancy check (CRC) scrambled with an ID of UE 102 to send a second DL PDU generated by the base station. In some implementations, the ID of UE 102 may be a radio network temporary identifier (RNTI). For example, the RNTI may be a cell RNTI (C-RNTI), a temporary C-RNTI, or an inactive C-RNTI. The base station sends the DCI and the scrambled CRC to UE 102 operating in an RRC_INACTIVE or RRC_IDLE state on a physical downlink control channel (PDCCH). The base station scrambles the CRC with the ID of UE 102. In some implementations, the base station may assign the ID of UE 102 to UE 102 in a random access response or message B (MsgB) sent by the base station in a random access process with UE 102 before sending the DCI and the scrambled CRC. In other implementations, the base station may assign the ID of UE 102 to UE 102 in an RRC message (e.g., an RRC release message or an RRC reconfiguration message) sent by the base station to UE 102 before sending the DCI and the scrambled CRC (e.g., when UE 102 is in the RRC_CONNECTED state).
[0045] A UE 102 operating in an RRC_INACTIVE or RRC_IDLE state may receive a DCI and a scrambled CRC on a PDCCH, and then confirm that a physical downlink shared channel (PDSCH) including a second DL PDU is addressed to the UE 102 based on the ID of the UE 102, the DCI, and the scrambled CRC. The UE 102 may then retrieve data from the security-protected packet. If the security-protected packet is an encrypted packet, the UE 102 may decrypt the encrypted packet using an appropriate decryption function and a security key to obtain the data. If the security-protected packet is an integrity-protected packet including data and a MAC-I, the UE 102 may determine whether the MAC-I is valid. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves the data. However, if the UE 102 determines that the MAC-I is invalid, the UE 102 discards the packet. If the security-protected packet is both encrypted and integrity-protected (having encrypted data and an encrypted MAC-I), the UE 102 can decrypt the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The UE 102 can then verify that the MAC-I is valid for the data. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves and processes the data. Otherwise, when the UE 102 determines that the MAC-I is invalid, the UE 102 discards the data.
[0046] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a MAC controller 132, which is configured to: perform a random access process with one or more user devices, receive UL MAC protocol data units (PDUs) from one or more user devices, and send DL MAC PDUs to one or more user devices. The processing hardware 130 may also include a PDCP controller 134, which is configured to send and / or receive PDCP PDUs according to the manner in which the base station 104 can send DL data and / or receive UL data. The processing hardware 130 may further include an RRC controller 136 to implement processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 130 includes an RRC inactive controller 138 that is configured to manage UL and / or DL communications with one or more UEs operating in an RRC_INACTIVE or RRC_IDLE state. The base station 106 may include generally similar components. In particular, the components 140, 142, 144, 146, and 148 of the base station 106 may be similar to the components 130, 132, 134, 136, and 138, respectively.
[0047] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. In an example implementation, the processing hardware 150 includes an RRC inactive controller 158, which is configured to manage uplink and / or downlink communications when UE 102 operates in an RRC_INACTIVE state. In an example implementation, the processing hardware 150 includes a MAC controller 152, which is configured to perform a random access procedure with a base station, send an uplink MAC PDU to the base station, and receive a downlink MAC PDU from the base station. The processing hardware 150 may also include a PDCP controller 154, which is configured to send and / or receive PDCP PDUs according to the manner in which UE 102 sends UL data and / or receives DL data. The processing hardware may further include an RRC controller 156 to implement processes and message delivery at the RRC sublayer of the protocol communication stack.
[0048] FIG. 1B depicts an example distributed or decomposed implementation of a base station 170, which may represent one or both of base stations 104, 106. In this implementation, base station 170 includes a central unit (CU) 172 and one or more distributed units (DU) 174. CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions that can be executed on a general-purpose processor, and / or a dedicated processing unit. For example, CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as PDCP controllers 134, 144, RRC controllers 136, 146, and / or RRC inactive controllers 138, 148. In some implementations, CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, CU 172 does not include an RLC controller.
[0049] Each DU in DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors, and / or dedicated processing units. For example, the processing hardware may include: a MAC controller (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or processes.
[0050] In some embodiments, the RAN 105 supports integrated access and backhaul (IAB) functionality. In some implementations, the DU 174 operates as an (IAB) node and the CU 172 operates as an IAB donor.
[0051] In some implementations, the CU 172 may include a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. The CU 172 may also include a logical node (CU-UP 172B) that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. The CU-CP 172A may send control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may send data packets (e.g., SDAP PDUs or Internet Protocol packets).
[0052] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the requested service of UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, connectivity between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.
[0053] Figure 2A illustrates in a simplified manner an example protocol stack 200 according to which a UE 102 may communicate with an eNB / ng-eNB 201A or a gNB 201B (e.g., one or both of base stations 104, 106).
[0054] In the example stack 200, the EUTRA PHY 202A provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn may provide data transfer services to the SDAP 212 or the RRC sublayer (not shown in FIG. 2A). In some implementations, as shown in FIG2A , the UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or to support DC implemented through EUTRA and NR interfaces. Further, as illustrated in FIG2A , the UE 102 may support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210.
[0055] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as SDUs (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as PDUs (e.g., to the RLC layer 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as "packets," except where the difference between SDUs and PDUs is relevant.
[0056] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a signaling radio bearer (SRB) or an RRC sublayer (not shown in FIG. 2A ) to exchange, for example, an RRC message or a NAS message. On the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a data radio bearer (DRB) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be an SDAP PDU, an Internet Protocol (IP) packet, or an Ethernet packet.
[0057] FIG. 2B illustrates in a simplified manner an example protocol stack 250 with which UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally split, as shown in the radio protocol stack 250 in FIG. 2B. The CU at either base station 104 or 106 can maintain all control and upper layer functions (e.g., RRC 214, SDAP 212, NR PDCP 210), while lower layer operations (e.g., NR RLC 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support a connection to a 5GC, NR PDCP 210 provides SRBs to RRC 214, and NR PDCP 210 provides DRBs to SDAP 212 and SRBs to RRC 214.
[0058] Next, several example scenarios involving various components of FIG. 1A and related to sending data in an inactive or idle state are discussed with reference to FIG. 3 to FIG. 6. To simplify the following description, "inactive state" may refer to RRC_INACTIVE or RRC_IDLE state, and "connected state" may refer to RRC_CONNECTED state.
[0059] Referring first to FIG. 3 , in a scenario 300 , the base station 104 includes a CU 172 and a DU 174 , and the CU 172 includes a CU-CP 172A and a CU-UP 172B. In this scenario 300 , the UE 102 initially operates in a connected state 302 , and communicates 304 with the DU 174 , for example, by using a DU configuration (i.e., a first non-SDT configuration), and communicates 304 with the CU-CP 172A and / or CU-UP 172B via the DU by using a CU configuration (i.e., a first non-SDTCU configuration). While the UE is communicating 304 with the base station 104 , the CU-CP 172A may send 306 a UE context modification request message. In response, the DU 174 sends 308 a UE context modification response message to the CU-CP 172A including a non-SDT configuration for the UE 102 (i.e., a second non-SDT configuration). CU-CP 172A generates an RRC reconfiguration message including the non-SDT DU configuration and sends 310 a first CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to DU 174. DU 174 then sends 312 the RRC reconfiguration message to UE 102. In response, UE 102 sends 314 an RRC reconfiguration complete message to DU 174, which then sends 316 a first DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to CU-CP 172A.
[0060] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the non-SDT DU configuration and communicates with the CU-CP 172A and / or CU-UP 172B via the DU. In the event that the RRC reconfiguration message does not include a CU configuration, the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the first non-SDT CU configuration. In the event that the RRC reconfiguration message includes a non-SDT CU configuration (i.e., a second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the second non-SDT CU configuration. In some implementations, the second non-SDT CU configuration may augment the first non-SDT CU configuration or include at least one new configuration parameter not included in the first non-SDT CU configuration. In such a case, the UE 102 and the CU-CP 172A and / or CU-UP 172B may communicate with each other using the second non-SDT CU configuration and also using configuration parameters in the first non-SDT CU configuration that are not augmented by the second non-SDT CU configuration 318. In some implementations, the first non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers (e.g., RRC 214 and / or NR PDCP 210), which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT CU configuration may include configuration parameters related to the operation of the RRC and / or PDCP protocol layers, which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT CU configuration may include configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE.
[0061] In some implementations, the second non-SDT DU configuration may extend the first non-SDT DU configuration or include at least one new configuration parameter not included in the first non-SDT DU configuration. In such cases, the UE 102 and the DU 174 may communicate 318 with each other using the second non-SDT DU configuration and also using configuration parameters in the first non-SDT DU configuration that are not extended by the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT DU configuration may include configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers, which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT DU configuration may include configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration may be CellGroupConfig IEs.
[0062] Events 306, 308, 310, 312, 314, 316, and 318 are collectively referred to in FIG. 3 as a non-SDT resource (re)configuration process 390, which may be optional.
[0063] While the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration process 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., based on the UE 102 in the connected state not having data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration process 390 (if performed), the UE 102 determines or detects data inactivity and sends 320 to the DU 174 UE assistance information (e.g., UEAssistanceInformation message) indicating that the UE 102 requests to transition to the inactive state configured with SDT. Then, the DU 174 sends 321 a UL RRC messaging message including the UE assistance information to the CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CU to DU message (e.g., a UE context setup request message or a UE context modification request message) to DU 174 to request or command DU 174 to perform data inactivity monitoring. In the case where DU 174 detects or determines that UE 102 is in data inactivity during monitoring, DU 174 may send 322 an inactivity notification (e.g., a UE inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from DU 174. In yet other implementations, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the event that CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may send 323 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from CU-UP 172B. In some implementations, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information, an inactivity notification of event 322, and / or an inactivity notification of event 323.
[0064] After a specific period of data inactivity, CU-CP 172A may determine that neither CU 172 (i.e., CU-CP 172A and / or CU-UP 172B) nor UE 102 sent any data in the downlink direction or the uplink direction, respectively, during the specific period. In response to this determination, CU-CP 172A may determine to transition UE 102 to an inactive state with SDT configured. Alternatively, in response to determining that UE 102 is in data inactivity, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured.
[0065] In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 326 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, in some implementations, the CU-CP 172A may send 328 a second CU-to-DU message (e.g., a UE context modification request message) to direct the DU 174 to provide an SDT DU configuration for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., an IE, such as a CG-SDT Query Indication IE) for requesting the SDT DU configuration in the second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 may send 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or sending the second DU-to-CU message, the DU 174 sends an additional DU-to-CU message (e.g., a UE context modification required message) including the SDT DU configuration to the CU-CP 172A. In response to the additional CU-to-DU message, the CU-CP 172A may send an additional CU-to-DU message (e.g., a UE context modification confirmation message) to the DU 174. In some alternative implementations, CU-CP 172A may send a second CU to DU message and receive a second DU to CU message or an additional DU to CU message before determining that UE 102 is in data inactivity. In other alternative implementations, CU-CP 172A may include an SDT request indication in the first CU to DU message of event 308, and in response to the SDT request indication, DU 174 includes the SDT DU configuration in the first DU to CU message of event 310.
[0066] In response to determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message or an RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include the SDT DU configuration (if obtained from DU 174) and / or the SDT CU configuration in the RRC release message. Then, CU-CP 172A sends 332 a third CU-to-DU message (e.g., a UE context release command message, a UE context modification request message, or a DL RRC messaging message) including the RRC release message to DU 174. Subsequently, DU 174 sends 334 the RRC release message to UE 102. In some implementations, DU 174 generates a MAC PDU including the RRC release message and sends 334 the MAC PDU to UE 102. The RRC release message directs UE 102 to transition to an inactive state. Upon receiving the RRC release message, the UE 102 transitions 336 from the connected state to the inactive state. In response to the third CU-to-DU message, the DU 174 may retain the SDT DU configuration (if generated by the DU 174 during processes 328, 330), and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. In response to the third CU-to-DU message, the DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to the CU-CP 172A.
[0067] When operating 302 in a connected state, UE 102 uses C-RNTI to monitor PDCCH to receive DCI. In response to receiving 334 to an RRC release message or thereafter, UE 102 stops using C-RNTI to monitor PDCCH. In some implementations, in response to receiving 334 to an RRC release message or transitioning 336 from a connected state to an inactive state or thereafter, UE 102 may retain C-RNTI. In some implementations, UE 102 performs a two-step or four-step random access process with a base station 104 (e.g., CU-CP 172A and / or DU 174), and receives a random access response message including C-RNTI from DU 174 during the random access process. In other implementations, UE 102 receives an RRC message (e.g., RRC reconfiguration message) including C-RNTI from CU-CP 172A or from another base station not shown in FIG. 3 (e.g., base station 106) via DU 174.
[0068] Events 320 (optional), 321 (optional), 322 (optional), 323, 324, 326, 328, 330, 332, and 334 are collectively referred to as the SDT configuration process 394 in FIG. 3 .
[0069] In some implementations, in response to the RRC release message, the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT DU configuration, or at least a portion of the first non-SDT DU configuration and at least a portion of the second non-SDT DU configuration. In other implementations, if the RRC release message directs the UE 102 to transition to an inactive state (i.e., RRC_IDLE), the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT configuration. In still other implementations, if the RRC release message directs the UE to transition to an inactive state (i.e., RRC_INACTIVE), the UE 102 releases the first non-SDT DU configuration and / or the first portion of the second non-SDT DU configuration, and retains the second portion of the first and / or second non-SDT DU configuration.
[0070] In some implementations, CU-CP 172A does not include an indication to direct DU 174 to retain the SDT DU configuration in the third CU to DU message, and DU 174 retains the SDT DU configuration, as described above. In other implementations, CU-CP 172A may include an indication to direct DU 174 to retain the SDT DU configuration in a third CU to DU message (e.g., a UE context release command message), and DU 174 retains the SDT DU configuration in response to the indication. If the UE context release command message excludes the indication, DU 174 releases the SDT DU configuration. In yet other implementations, CU-CP 172A does not include an indication to direct DU 174 to release the SDT DU configuration in a third CU to DU message (e.g., a UE context modification request message or a DL RRC messaging message) for UE 102. Therefore, in response to the third CU to DU message excluding the indication, DU 174 retains the SDT DU configuration. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.
[0071] In some implementations, parameters in the SDT CU configuration (e.g., SDT-Config IE) include a DRB list (e.g., std-DRB-List) including a list of DRB IDs indicating the IDs of the DRBs configured for SDT. In some implementations, parameters in the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. In some implementations, parameters in the SDT CU configuration may include a compression protocol continuation indication (e.g., sdt-DRB-ContinueROHC) indicating whether the PDCP entity of the DRB configured for SDT continues during SDT operation (i.e., the initial and / or subsequent SDT described in FIG. 4). For example, the compression protocol may be robust header compression (ROHC). In some implementations, the SDT CU configuration may include a data volume threshold (e.g., sdt-DataVolumeThreshold) for the UE 102 to determine whether the UE 102 can initiate an SDT. The CU-CP 172A may include the SDT DU configuration in the SDTCU configuration. The "SDT CU configuration" may also be referred to as the "SDT configuration" for short.
[0072] In some implementations, the SDT DU configuration includes at least one of a buffer status report (BSR) configuration, a power headroom report (PHR) configuration, and / or a CG-SDT configuration. The CG-SDT configuration may include or be one or more CG configurations for CG-SDT, a DL bandwidth part (BWP) configuration for CG-SDT, a time alignment timer value for CG-SDT (e.g., a CG-SDT time alignment timer value), and / or a timing advance validity threshold for CG-SDT. The DU 174 configures the timing advance validity threshold (e.g., including an RSRP range) for the UE 102 to determine whether the UE 102 can initiate SDT using the configuration grant configuration for CG-SDT, as described with respect to FIG. 4. Based on the timing advance validity threshold, the UE 102 may evaluate whether the stored timing advance value is still valid. If the UE 102 determines that the stored timing advance value is invalid, the UE 102 may initiate a RA-SDT with the CU 172 via the DU 174, as described with respect to FIG. 4. In some implementations, the SDT DU configuration may be an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE.
[0073] In some implementations, DU 174 may start or restart the DU CG-SDT timer in response to or after receiving an SDT request indication, generating a CG-SDT configuration, receiving 328 a second CU to DU message, sending 330 a CG-SDT configuration to CU 172, receiving 332 a third CU to DU message, or sending 334 a CG-SDT configuration to UE 102. In some implementations, DU 174 may start or restart the DU CG-SDT timer with a timer value to manage the CG-SDT configuration. In some implementations, the timer value is the same as the CG-SDT time alignment timer value. In other implementations, the timer value is close to the CG-SDT time alignment timer value. For example, the timer value may be greater than and close to the CG-SDT time alignment timer value. In another example, the timer value may be less than and close to the CG-SDT time alignment timer value. Only when the DU CG-SDT timer expires does DU 174 release the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 avoids receiving PUSCH transmissions from UE 102 on the radio resources reserved or configured for the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 may schedule transmissions of other UEs on the radio resources reserved or configured for the CG-SDT configuration.
[0074] As described above, in some implementations, the RRC release message 334 may include a CG-SDT configuration. In response to or after receiving the CG-SDT configuration, the UE 102 may start or restart a UE CG-SDT timer (e.g., a CG-SDT time alignment timer (CG-SDT-TAT)). In some implementations, the UE 102 may start or restart a UE CG-SDT timer with a CG-SDT time alignment timer value. The UE 102 releases the CG-SDT configuration only when the CG-SDT timer expires. When or after releasing the CG-SDT configuration, the UE 102 avoids sending PUSCH transmissions on radio resources reserved or configured for the CG-SDT configuration.
[0075] In some implementations, DU 174 reserves the radio resources configured in the configuration grant configuration. In some implementations, DU 174 releases the radio resources when releasing the SDT DU configuration or the CG-SDT configuration. In the case where DU 174 does not provide the CG-SDT configuration or the SDT DU configuration to CU-CP 172A, DU 174 releases all signaling and user data transmission resources for UE 102 in response to the third CU to DU message. In the case where DU 174 provides the SDT DU configuration or the CG-SDT configuration to CU-CP 172A, DU 174 reserves the signaling and user data transmission resources for UE 102 in response to receiving the third CU to DU message or thereafter.
[0076] In the case where the SDT DU configuration does not include configuration for CG-SDT, CU-CP 172A and / or DU 174 only configures RA-SDT for UE 102. In such a case, UE 102 may perform RA-SDT with CU 172 via DU 174, as described with respect to FIG.
[0077] In some implementations, when determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may not request DU 174 to provide an SDT DU configuration. In such cases, events 328 and 330 may be omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own (without requesting DU 174 to provide the SDT DU configuration) and include the SDT DU configuration in the RRC release message.
[0078] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 may send the SDT DU configuration to CU-CP 172A as described above. In some implementations, DU 174 may not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 may include the CG-SDT configuration in the SDT DU configuration, as described above.
[0079] In some implementations, when UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A may request DU 174 to provide SDT DU configuration, as described above. When UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. When the UE operates 302 in a connected state, CU-CP 172A may receive UE capabilities (e.g., UE-NR-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. UE capabilities indicate whether UE 102 supports CG-SDT. Therefore, CU-CP 172A may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, CU-CP 172A may receive a DU-to-CU message from DU 174 indicating whether DU 174 supports CG-SDT. The DU-to-CU message may be a second DU-to-CU message, a message of event 308 or 316, or a non-UE-associated message (e.g., a non-UE-associated F1AP message defined in 3GPP specification 38.473).
[0080] In some implementations, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the UE 102 supports CG-SDT. In addition to whether the UE 102 supports CG-SDT, the DU 174 may additionally determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the DU 174 supports CG-SDT. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). When the UE operates in a connected state 302 or in an inactive state before event 302, the DU 174 may receive the UE capabilities from the CU-CP 172A. Thus, the DU 174 may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, the DU 174 may send a DU-to-CU message to the CU-CP 172A indicating whether the DU 174 supports CG-SDT, as described above.
[0081] Referring now to FIG. 4 , scenario 400 depicts a small data transmission. In scenario 400 , base station 104 includes CU 172 and DU 174. CU 172 includes CU-CP 172A and CU-UP 172B. In scenario 400 , UE 102 initially operates 402 in an inactive state configured with SDT. In some implementations or scenarios, UE 102 may transition from a connected state to an inactive state configured with SDT, as described with respect to FIG. 3 . In such implementations, UE 102 may receive a first SDT CU configuration and / or a first SDT DU configuration in an RRC release message (e.g., event 334). In other implementations or scenarios, UE 102 may transition from an inactive state in which SDT is not configured to an inactive state in which SDT is configured. For example, UE 102 may receive an RRC release message from a base station (e.g., base station 104 or base station 106) that transitions UE 102 to an inactive state but does not configure SDT (e.g., indicates release of SDT, or does not include SDT configuration in the RRC release message). In this case, UE 102 transitions to an inactive state in which SDT is not configured in response to the RRC release message. UE 102 in an inactive state with or without SDT configured may perform a RAN Notification Area (RNA) update with the base station without a state transition. During the RNA update, UE 102 receives another RRC release message from the base station that includes a first SDT CU configuration and / or a first SDT DU configuration similar to the RRC release message of event 334.
[0082] Later, the UE 102 operating in an inactive state configured with SDT initiates an SDT. In response to or after initiating the SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message, and sends 404 the initial UL MAC PDU to the DU 174 on the cell 124. In response to initiating the SDT, the UE 102 may start an SDT session timer. In some implementations, the SDT session timer may be a new timer defined in the RRC specification (e.g., v17.0.0). The DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends 406 the first DU to CU message to the CU-CP 172A. In some implementations, the first DU to CU message may be an initial UL RRC messaging message. In other implementations, the first DU to CU message may be a UL RRC messaging message.
[0083] In a scenario where the UE 102 initiates an SDT to send UL data (e.g., a data packet) eligible for SDT, the UE 102 includes the UL data in an initial UL MAC PDU sent 404 by the UE 102. In a scenario where the UE 102 initiates an SDT to receive DL data, the UE 102 does not include the UL data packet in the initial UL MAC PDU sent 404 by the UE 102. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging from the DU 174. In such a scenario, the UE 102 may include an SDT indication in an initial UL MAC PDU or UL RRC message to indicate to the base station 104 that the UE 102 is initiating an SDT to receive DL data.
[0084] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to send 404 a UL MAC PDU. In such a case, the SDT may be a RA-SDT. For example, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In the case of the four-step random access procedure, the UE 102 sends a random access preamble to the DU 174, and in response, the DU 174 sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE 102, and the UE 102 sends 404 a UL MAC PDU according to the uplink grant. The DU 174 receives 404 the UL MAC PDU according to the uplink grant in the RAR. In the case of the two-step random access procedure, the UE 102 sends 404 a message A (MsgA) including a random access preamble and a UL MAC PDU to the DU 174 according to the two-step random access configuration parameters. In response to MsgA, UE 102 may receive message B (MsgB) including the temporary C-RNTI and the timing advance command from DU 174. UE 102 receives two-step random access configuration parameters in system information broadcast by DU 174 on cell 124 before sending 404 the UL MAC PDU. DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.
[0085] When UE 102 successfully resolves the contention problem in the random access process, UE 102 discards the previously reserved C-RNTI (e.g., as described for FIG. 3 ) and determines the temporary C-RNTI as a specific C-RNTI (i.e., a new C-RNTI). UE 102 monitors the PDCCH from DU 174 using the C-RNTI to communicate 418 data with DU 174. More specifically, UE 102 receives the DCI and the CRC of the DCI on the PDCCH from DU 174 and verifies the CRC using the C-RNTI. The DCI may include an uplink grant or a downlink assignment. If UE 102 verifies that the CRC is correct and the DCI includes an uplink grant, UE 102 sends 418 UL data to DU 174 using the uplink grant. If UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, UE 102 receives 418 DL data from DU 174 using the downlink assignment.
[0086] In other implementations, in the event that the UE 102 receives a CG configuration for SDT (i.e., a CG-SDT configuration) as described with respect to FIG3, the UE 102 may send 404 a UL MAC PDU on the radio resources configured in such configuration. Thus, the DU 174 receives 404 a UL MAC PDU on the radio resources.
[0087] In some implementations, the UE 102 may send 418 subsequent UL MAC PDUs including one or more UL data packets on the radio resources configured in the CG configuration. In some implementations, the UE 102 may send 418 subsequent UL MAC PDUs on the radio resources configured in the uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 may send 418 some of the subsequent UL MAC PDUs on the radio resources configured in the CG configuration and send 418 other of the subsequent UL MAC PDUs on the radio resources configured in the uplink grant.
[0088] If UE 102 includes UL data in the initial UL MAC PDU, DU 174 retrieves the UL data from the initial UL MAC PDU. In such a case, DU 174 may include the UL data in the DU to CU message of event 406. Alternatively, DU 174 may send 415 a DU to CU message including UL data to CU-CP 172A. In this alternative, the UL data may include or be a PDCP PDU, an RRC PDU, a NAS PDU, or an LTE Positioning Protocol (LPP) PDU. The PDCP PDU may include an RRCPDU. As yet another alternative, DU 174 may send 416 UL data to CU-UP 172B separately via a user plane (UP) connection as described below. In this alternative, the UL data may include or be a PDCP PDU, and the PDCP PDU may include an SDAP PDU, an IP packet, or an Ethernet packet.
[0089] After receiving 406 the first DU-to-CU message, in some implementations, the CU-CP 172A may send 408 a UE context setup request message to the DU 174 to establish a UE context for the UE 102 at the DU 174. In the UE context setup request message, the CU-CP 172A may include transport layer information of one or more GTP-U tunnels between the CU-UP 172B and the DU 174, so that the DU 174 may send UL data and / or subsequent UL data (e.g., in a small data communication 418) to the CU-UP 172B via the one or more GTP-U tunnels. In response, the DU 174 may send 410 a UE context setup response message to the CU-CP 172A. After receiving 406 the first DU to CU message, sending 408 the UE context setup request message, or receiving 410 the UE context setup response message, CU-CP 172A sends 412 a bearer context modification request message to CU-UP 172B to resume data transmission of UE 102. In response, CU-UP 172B resumes data transmission of UE 102 and sends 414 a bearer context modification response message to CU-CP 172A. After receiving 408 the UE context setup request message or sending 410 the UE context setup response message, in the case where the UL data of event 404 includes an RRC message or is associated with an SRB (e.g., SRB1 or SRB2), DU 174 may send 415 a DU to CU message including UL data to CU-CP 172A. In the case where the UL data is associated with a DRB, DU 174 may send 416 the UL data to CU-UP 172B.
[0090] In some implementations, the CU-CP 172A may include the transport layer information of the CU-UP 172B in the UE context setup request message. The transport layer information of the CU-UP 172B may include an IP address and / or an uplink tunnel endpoint ID (e.g., TEID). The DU 174 may send 416 UL data to the CU-UP 172B using the transport layer information of the CU-UP 172B. In the event that the UE 102 has subsequent UL data (e.g., one or more UL data packets) to send, the UE 102 may send 418 one or more subsequent UL MAC PDUs including the subsequent UL data to the DU 174. Then, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the event that the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 sends 418 one or more DU to CU messages (e.g., UL RRC messaging messages) including the subsequent UL data to the CU-CP 172A. Each DU to CU message may include a specific UL data packet of subsequent UL data. In the case where the CU-CP 172A receives DL data from the CN 110 or edge server, the CU-CP 172A may send 418 one or more CU to DU messages (e.g., DL RRC messaging messages) including the DL data (e.g., one or more DL data packets) to the DU 174. In turn, the DU 174 sends 418 one or more DL MAC PDUs including the DL data to the UE 102 operating in the inactive state. In some implementations, the DL data may include or be a NAS PDU and / or an LPP PDU.
[0091] In the case where the subsequent UL data is associated with one or more DRBs, DU 174 sends 418 the subsequent UL data to CU-UP 172B, which is similar to event 416. In some implementations, DU 174 may include DU transport layer information of DU 174 in the UE context setup response message. Then, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. The transport layer information of DU 174 may include an IP address and / or a downlink TEID. In the case where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B may use the transport layer information of DU 174 to send 418 DL data (e.g., one or more DL data packets) to DU 174. Then, DU 174 sends 418 one or more DL MAC PDUs including the DL data to UE 102 operating in an inactive state.
[0092] In some implementations, the UE 102 may include a buffer status report or a power headroom report in an initial and / or subsequent UL MAC PDU, e.g., based on a BSR configuration and / or a PHR configuration, respectively. In a buffer status report, the UE 102 may include or indicate a buffer status of one or more logical channels or logical channel groups thereof. In a power headroom report, the UE 102 may include or indicate a power headroom status or value.
[0093] In some example scenarios, the subsequent UL data and / or DL data described above include IP packets, Ethernet packets, or application packets. In other scenarios, the UL data may include or be a PDU (e.g., RRC PDU, PDCP PDU, or RLC PDU), which includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.
[0094] Events 404 , 406 , 408 , 410 , 412 , 414 , 415 , and 416 are collectively referred to as small data transfer process 492 in FIG. 4 .
[0095] In some implementations, the UL RRC message is an (existing) RRC recovery request message (e.g., RRCResumeRequest message, RRCResumeRequest message, RRCConnectionResumeRequest message, or RRCConnectionResumeRequest message). In other implementations, the UL RRC message may be a new RRC recovery request message similar to the existing RRC recovery request message. For example, the new RRC recovery request message may be defined in a future 3GPP standard document. The new RRC recovery request message may have the format of the existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message may include an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.
[0096] After the UE 102 sends 404 UL MAC PDU or communicates 418 subsequent UL data and / or DL data with the DU 174, the CU-CP 172A may determine to stop the SDT of the UE 102 based on data inactivity of the UE 102 (i.e., based on the UE 102 in an inactive state not having data activity with the base station 104). After the UE 102 sends 404 UL MAC PDU or communicates 418 subsequent UL data and / or DL data with the DU 174, the UE 102 in an inactive state determines or detects data inactivity and sends 420 UE assistance information (e.g., UEAssistanceInformation message) to the DU 174 indicating that the UE 102 decides (e.g., needs) to stop the SDT. Subsequently, the DU 174 sends 421 a UL RRC messaging message including the UE assistance information to the CU-CP 172A. Therefore, the CU-CP 172A may determine that the UE 102 is in data inactivity based on the UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CU to DU message (e.g., a UE context setup request message of event 408, or a UE context modification request message) to DU 174 to request or command DU 174 to perform data inactivity monitoring. In the case where DU 174 detects or determines that UE 102 is in data inactivity during monitoring, DU 174 may send 422 an inactivity notification (e.g., a UE inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from DU 174. In yet other implementations, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In some implementations, if sent before UE 102 initiates SDT, the CP to UP message may be a bearer context setup request message or a bearer context modification request message. In other implementations, if sent during SDT, the CP to UP message may be a bearer context modification request message (e.g., event 412). In the event that CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may send 423 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from CU-UP 172B.In some implementations, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information, the inactivity notification of event 422 , and / or the inactivity notification of event 423 .
[0097] After a specific period of data inactivity, CU-CP 172A may determine that neither CU 172 nor UE 102 sent any data in the downlink direction or the uplink direction during the specific period. In response to this determination, CU-CP 172A may determine to stop SDT. Alternatively, in response to determining that UE 102 is in data inactivity, CU-CP 172A may determine to immediately stop SDT for UE 102.
[0098] In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 424 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 426 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 428 a second CU-to-DU message (e.g., a UE context modification request message) to instruct the DU 174 to provide an SDT DU configuration (e.g., a second SDT DU configuration) for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., a field or IE) for requesting an SDT DU configuration in a second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 sends 430 a second DU-to-CU message (e.g., a UE context modification response message) including the second SDT DU configuration to the CU-CP 172A. Alternatively, the DU 174 does not include the second SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or sending the second DU-to-CU message, the DU 174 sends another DU-to-CU message (e.g., a UE context modification required message) including the second SDT DU configuration to the CU-CP 172A. In some alternative implementations, the CU-CP 172A may send a second CU-to-DU message and receive the second DU-to-CU message (or the other DU-to-CU message) before determining that the UE 102 is in data inactivity.
[0099] In response to determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message or an RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include a second SDT DU configuration (if obtained from DU 174) and / or a second SDT CU configuration in the RRC release message.
[0100] Alternatively, CU-CP 172A may not include the SDT configuration in the RRC release message. In this alternative, CU-CP 172A may indicate in the RRC release message whether UE 102 releases or retains the first SDT CU configuration and / or the first SDT DU configuration. For example, CU-CP 172A may include a release indication indicating the release of the first SDT CU configuration or the first SDT DU configuration in the RRC release message. If the RRC release message does not include a release indication, UE 102 retains the first SDT CU configuration and / or the first SDT DU configuration.
[0101] Then, the CU-CP 172A sends 432 a third CU-to-DU message including an RRC release message to the DU 174. Then, the DU 174 sends 434 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and sends 434 the MAC PDU to the UE 102. The RRC release message directs the UE 102 to be in an inactive state (e.g., transition to an inactive state or maintain an inactive state). The UE 102 stops the SDT upon receiving 434 the RRC release message and remains 436 in an inactive state.
[0102] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are collectively referred to as the SDT completion process 494 in FIG. 4 .
[0103] During the SDT session (i.e., events 492 and 494), UE 102 uses C-RNTI to monitor PDCCH to receive DCI. In some implementations, UE 102 receives C-RNTI during the random access process described for event 404. In other implementations, UE 102 can receive and retain C-RNTI as described for Figure 3. In response to receiving 434 to the RRC release message or thereafter, UE 102 stops using C-RNTI to monitor PDCCH. In response to receiving 434 to the RRC release message or transitioning 436 from the connected state to the inactive state or thereafter, UE 102 can retain C-RNTI. In the case where RRC release message 434 configures CG-SDT, in some implementations, UE 102 can retain C-RNTI. In the case where RRC release message 434 does not configure or release CG-SDT, in some implementations, UE 102 can release C-RNTI.
[0104] In some implementations, the second SDT CU configuration may be the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration may be different from the first SDT CU configuration. The UE 102 may update (e.g., replace or modify) the first SDT CU configuration using the second SDT CU configuration. In some implementations, the CU-CP 172A may include an indication in the RRC release message indicating that the UE 102 will update the first SDT CU configuration using the second SDT CU configuration. In such implementations, the UE 102 may update the first SDT CU configuration using the second SDT CU configuration in response to the indication. In other implementations, the CU-CP 172A may include a modification indication in the RRC release message indicating that the UE 102 will modify the first SDT CU configuration using the second SDT CU configuration. In such implementations, the UE 102 may modify the first SDT CU configuration using the second SDT CU configuration in response to the modification indication. In yet other implementations, the CU-CP 172A may include a setup indication in the RRC release message to indicate that the UE 102 will replace the first SDT CU configuration with the second SDT CU configuration. In such implementations, the UE 102 may replace the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.
[0105] In some implementations, the second SDT DU configuration may be the same as the first SDT DU configuration. In other implementations, the second SDT DU configuration may be different from the first SDT DU configuration. The UE 102 may update (e.g., replace or modify) the first SDT DU configuration using the second SDT DU configuration. In some implementations, the DU 174 may include in the second SDT DU configuration an indication to indicate that the UE 102 updates the first SDT DU configuration using the second SDT DU configuration. In such implementations, the UE 102 may update the first SDT DU configuration using the second SDT DU configuration in response to the indication. In other implementations, the DU 174 may include in the second SDT DU configuration a modification indication to indicate that the UE 102 modifies the first SDT DU configuration using the second SDT DU configuration. In such implementations, the UE 102 may modify the first SDT DU configuration using the second SDT DU configuration in response to the modification indication. In yet other implementations, the DU 174 may include a setup indication in the second SDT DU configuration to instruct the UE 102 to replace the first SDT DU configuration with the second SDT DU configuration. In such implementations, the UE 102 may replace the first SDT DU configuration with the second SDT DU configuration in response to the setup indication.
[0106] In the case where the CU-CP 172A and / or the DU 174 support incremental configuration, the CU-CP 172A may not send 428 a CU to DU message to obtain the second SDT DU configuration from the DU 174. The DU 174 retains the first SDT DU configuration unless the conditions for releasing the first SDT configuration are met. Alternatively, the CU-CP 172A may include the first SDT DU configuration in the second CU to DU message so that the DU 174 retains the first SDT DU configuration. In these cases, the CU-CP 172A may not include the SDT DU configuration and / or the SDT CU configuration in the RRC release message so that the UE 102 continues to use the first SDT CU configuration and / or the first SDT DU configuration. In some implementations, the CU-CP 172A may not include a release indication in the RRC release message so as to configure the UE 102 to continue to use the first SDT DU configuration and / or the first SDT CU configuration. The release indication indicates that the UE 102 will release the previously received SDT DU configuration and / or SDT CU configuration. In the case where the CU-CP 172A includes the release indication in the RRC release message, the UE 102 releases the first SDT CU configuration and / or the first SDT DU configuration in response to the release indication.
[0107] In the event that the CU-CP 172A and / or the DU 174 do not support incremental configuration, the CU-CP 172A may include the SDT DU configuration and / or the SDT CU configuration in the RRC release message, as described above.
[0108] In response to the third CU-to-DU message, DU 174 may retain the second SDT DU configuration and may or may not release the first non-SDT DU configuration and / or the second non-SDT DU configuration. In response to the third CU-to-DU message, DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A. In some implementations, if the RRC release message directs UE 102 to transition to an inactive state (i.e., RRC_IDLE), UE 102 releases the non-SDT configuration (e.g., the first non-SDT DU configuration, the first non-SDT CU configuration, the second non-SDT DU configuration, and / or the second non-SDT CU configuration described in FIG. 3 ) and at least one SDT configuration (e.g., the SDTDU configuration and the SDT CU configuration described in FIG. 3 ).
[0109] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are collectively referred to as SDT completion process 494 in FIG. 4, which is similar to process 394. The examples and implementations for events 320, 321, 322, 323, 324, 326, 328, 330, 332, 334 may be respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, 434. After stopping SDT, if UE 102 is still configured with SDT configuration, UE 102 may perform 493 another SDT process with base station 104, which is similar to process 492. After completing process 493 , base station 104 may perform 495 an SDT completion process with UE 102 , which is similar to process 494 .
[0110] In some implementations, CU-CP 172A may not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state configured with SDT. In such cases, events 428 and 430 may be omitted. In such cases, CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own and include the SDT DU configuration in the RRC release message.
[0111] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 may include the SDT DU configuration, as described above. In some implementations, DU 174 does not include the CG-SDT configuration in the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 may include at least one CG-SDT configuration in the SDT DU configuration, as described above.
[0112] In some implementations, in the case where the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the CU-CP 172A may request the DU 174 to provide the SDT DU configuration, as described above. In the case where the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the CU-CP 172A does not request the DU 174 to provide the SDT DU configuration. When the UE 102 is operating in an inactive state 402 before the UE initiates SDT, when the UE performs SDT (e.g., in a UE context setup request message of event 408 or a CU to DU message of event 428), or when the UE is operating in a connected state as described with respect to FIG. 3, the CU-CP 172A may receive the UE capabilities (e.g., UE-NR-Capability IE) of the UE 102 from the UE 102, the CN 110 (e.g., the MME 114 or the AMF 164), or the base station 106. The UE capability indicates whether the UE 102 supports CG-SDT. Therefore, the CU-CP 172A can determine whether the UE supports CG-SDT based on the UE capability. In some implementations, the CU-CP 172A can receive a DU-to-CU message from the DU 174 indicating whether the DU 174 supports CG-SDT. The DU-to-CU message can be a second DU-to-CU message, a message of event 308 or 316, or a non-UE-associated message (e.g., a non-UE-associated F1AP message defined in 3GPP specification 38.473).
[0113] In some implementations, DU 174 may determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether UE 102 supports CG-SDT. In addition to whether UE 102 supports CG-SDT, DU 174 may additionally determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether DU 174 supports CG-SDT. In the event that UE 102 supports CG-SDT and / or DU 174 supports or enables CG-SDT, DU 174 provides the SDT DU configuration for UE 102 to CU-CP 172A, as described above. In the event that UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, DU 174 does not provide the SDT DU configuration for UE 102 (e.g., DU 174 does not include the SDT DU configuration in the second DU to CU message). For example, when UE 102 is operating in a connected state or in an inactive state, DU 174 may receive UE capabilities from CU-CP 172A. Thus, DU 174 may determine whether UE 102 supports CG-SDT based on the UE capabilities. In some implementations, DU 174 may send a DU-to-CU message to CU-CP 172A indicating whether DU 174 supports CG-SDT, as described above.
[0114] Referring now to FIG5A, scenario 500A depicts a small data transmission and a transition from SDT to non-SDT. In scenario 500A, base station 104 includes CU 172 and DU 174, CU 172 includes CU-CP 172A and CU-UP 172B, and UE 102 initially operates 502 in an inactive state configured with SDT, which is similar to event 402. Then, UE 102 performs an SDT process 592 with base station 104, which is similar to event 492.
[0115] During the small data transfer process 592, the CU-CP 172A may determine whether to transition the UE 102 to a connected state, for example, based on the UL or DL data activity of the UE 102. In some implementations, the UE 102 may send 503 a non-SDT indication message to the DU 174 to indicate that UL data is available or request a transition to a connected state. In some implementations, the UE 102 may send 503 a non-SDT indication message to the DU 174 on the radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 may receive an uplink grant on the PDCCH from the DU 174 using the C-RNTI, and send 503 a non-SDT indication message to the DU 174 on the radio resources configured in the uplink grant. Then, the DU 174 sends 505 a UL RRC messaging message including the non-SDT indication message to the CU-CP 172A. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a non-SDT indication message. In other implementations, CU-UP 172B receives DL data from CN 110, and in response, sends 507 to CU-CP 172A a DL data notification (e.g., a DL data notification message) indicating that DL data is available for transmission. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A may determine to transition UE 102 to a connected state based on a measurement result received from UE 102. In yet other implementations, CU-CP 172A receives DL data (e.g., a NAS message) from CN 110, and in response, may determine to transition UE 102 to a connected state.
[0116] In some implementations, the non-SDT indication message may be an RRC message (eg, a UEAssistanceInformation message or a new RRC message).
[0117] In some implementations, UL data and / or DL data are associated with a radio bearer (e.g., SRB and / or DRB). For example, the UL data may include an RRC message or a NAS message associated with the SRB. In another example, the UL data includes an IP packet associated with the DRB. In some implementations, the UE 102 may include the ID of the radio bearer in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the ID. For example, if the radio bearer identified by the ID is not eligible for SDT, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In some implementations, the UE 102 may include data volume information of the UL data in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the data volume information. In one implementation, the data volume information includes the total data volume of the UL data, which can be quantized or rounded to a value that can be indicated in the data volume information. In another implementation, the data volume information includes the data volume of each radio bearer in the radio bearer, which can be quantized or rounded to a value that can be indicated in the data volume information. For example, if the total data volume is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In another example, if the data volume of a particular radio bearer is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In yet another example, if the total data volume is higher than a predetermined threshold and the data volume of a particular radio bearer is higher than another predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to the connected state.
[0118] In response to or after determining to transition the UE 102 to the connected state, the CU-CP 172A sends 506 a UE context request message (e.g., a UE context setup request message or a UE context modification request message) to the DU 174. In response, the DU 174 sends 508 a UE context response message (e.g., a UE context setup response message or a UE context modification response message) to the CU-CP 172A. In some implementations, the DU 174 may include a non-SDT DU configuration (i.e., a first non-SDT DU configuration) in the UE context response message. After receiving the UE context response message, the CU-CP 172A sends 510 a CU-to-DU message including an RRC resume message (e.g., an RRCResume message or an RRCConnectionResume message) to the DU 174. Then, the DU 174 sends 512 the RRC resume message to the UE 102. In some implementations, the DU 174 may send 512 one or more PDUs including the RRC resume message to the UE 102. The PDU may be a MAC PDU or an RLC PDU. In some implementations, the CU to DU message may be a DL RRC messaging message or a UE context modification request message. In the case of a UE context modification request message, in response, DU 174 may send a UE context modification response message to CU-CP 172A. In response to receiving the RRC resume message, UE 102 transitions 513 to a connected state and sends 514 an RRC recovery completion message (e.g., an RRCResumeComplete message or an RRCConnectionResumeComplete message) to DU 174. In the case where the UE context response message includes a non-SDT DU configuration, CU-CP 172A includes the non-SDT DU configuration in the RRC resume message. DU 174 sends 516 a DU to CU message including an RRC recovery completion message to CU-CP 172A. After determining to transition the UE 102 to the connected state, the CU-CP 172A may send 517 a bearer context request message (e.g., a bearer context setup request message or a bearer context modification request message) to the CU-UP 172B to instruct the CU-UP 172B to resume all suspended radio bearers of the UE 102. In response, the CU-UP 172B resumes all suspended radio bearers of the UE 102 and sends 519 a bearer context response message (e.g., a bearer context setup response message or a bearer context modification response message) to the CU-CP-172A.In some implementations, the CU-CP 172A may send 517 a bearer context request message after sending 506 a UE context request message, receiving 508 a UE context response message, sending 510 a CU to DU message, or receiving 516 a DU to CU message.
[0119] In some implementations, CU-CP 172A may include an indication indicative of DU 174 generating a non-SDT configuration in a UE context request message, and in response to the indication, DU 174 includes a first non-SDT DU configuration in a UE context response message. In yet other implementations, CU-CP 172A stores a non-SDT DU configuration (i.e., a second non-SDT DU configuration) used by a DU (e.g., DU 174 or another DU or base station) to communicate with UE 102. UE 102 may also store a second non-SDT DU configuration. In such cases, CU-CP 172A includes the second non-SDT DU configuration in a UE context request message, and DU 174 may include the first non-SDT DU configuration in a UE context response message in response to receiving the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration augments or replaces the second non-SDT DU configuration. Examples and implementations of the first non-SDT DU configuration and the second non-SDT DU configuration may be the same as those described above for the non-SDT DU configuration. In some implementations, the DU 174 may send an additional DU-to-CU message (e.g., a UE context modification required message) including the first non-SDT DU configuration to the CU-CP 172A instead of including the first non-SDT DU configuration in the UE context response message.
[0120] After transitioning to the connected state, the UE 102 communicates 518 UL data and / or DL data with the CU-CP 172A and / or CU-UP 172B via the DU 174. The UL data may include UL data that triggers the UE 102 to send a non-SDT indication message. The UL data may also include new UL data available for transmission. The DL data may include DL data received from the CN 110 as described above. The DL data may also include new DL data received from the CN 110. In the case where the RRC recovery message includes the first non-SDT DU configuration, the UE 102 communicates 518 with the DU 174 using the first non-SDT DU configuration. In the case where the second non-SDT DU configuration is not completely replaced by the first non-SDT DU configuration (i.e., the UE 102 does not release the second non-SDTDU configuration in response to the RRC recovery message), the UE 102 may communicate 518 with the DU 174 using configuration parameters in the second non-SDT DU configuration that are not extended by the first non-SDT DU configuration.
[0121] In some implementations, DU 174 may not provide the first non-SDT DU configuration to CU-CP 172A in the UE context response message and the attach DU to CU message. In such a case, the RRC resume message does not include the first non-SDT configuration, and UE 102 and DU 174 communicate 518 with each other using the second non-SDT DU configuration.
[0122] In some implementations, the UE 102 releases the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration) in response to an RRC recovery message or transitioning to a connected state. In some implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to or after transitioning the UE 102 to a connected state, receiving 510 to a CU to DU message, or sending 510, 512 an RRC recovery message. In other implementations, the base station 104 releases the SDT configuration in response to or after receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for a PDU including an RRC recovery message. In still other implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to or after communicating 506 a UE context request message or communicating 508 a UE context response message.
[0123] In other implementations, in response to receiving an RRC recovery message or transitioning to a connected state or thereafter, the UE 102 retains the SDT configuration (e.g., an SDT CU configuration, an SDT DU configuration, and / or a CG-SDT configuration). In some implementations, when operating in a connected state, the UE 102 avoids using the SDT configuration to communicate with the base station 104 (e.g., sending 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, when operating in a connected state, the UE 102 may use the SDT configuration to communicate with the base station 104 (e.g., 514 an RRC recovery complete message and / or 518 data). In some implementations, in response to transitioning the UE 102 to a connected state or sending an RRC recovery message or thereafter, the base station 104 retains the SDT configuration. In some implementations, the base station 104 avoids using the SDT configuration to communicate with the UE 102 operating in a connected state (e.g., receiving 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, the base station 104 may use the SDT configuration to communicate with the UE 102 operating in the connected state (e.g., receive 514 an RRC recovery complete message and / or communicate 518 data).
[0124] At a later time, the base station 104 may perform a non-SDT configuration process 590 and an SDT configuration process 594 with the UE 102, which are similar to the process 390 and the process 394, respectively. In response to receiving the RRC release message in the process 594, the UE 102 transitions 536 to the inactive state. The base station 104 may then perform an SDT process 593 and an SDT completion process 595 with the UE 102, which are similar to the process 492 and the process 494, respectively.
[0125] 5B, scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC connection recovery procedure instead of a small data communication procedure 592. The differences between scenarios 500B and 500A are discussed below.
[0126] In response to initiating the RRC connection recovery process, the UE 102 sends 542 an RRC recovery request message to the DU 174, which in turn sends 544 an initial UL RRC messaging message including an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCConnectionResumeRequest message) to the CU-CP 172A. In response to receiving the RRC recovery request message, the CU-CP 172A determines to transition the UE 102 to the connected state. In response to or after determining to transition the UE 102 to the connected state, the CU-CP 172A transitions the UE 102 to the connected state as described for scenario 500A.
[0127] In some implementations, the UE 102 may generate a UL MAC PDU including the RRC recovery request message and send 542 the UL MAC PDU to the DU 174. In some implementations, the UE 102 may send 542 the UL MAC PDU to the DU 174 on the radio resources configured in the CG configuration for the SDT. In other implementations, the UE 102 may perform a random access procedure to send the UL MAC PDU, similar to event 404.
[0128] 6, scenario 600 depicts SDT operation, which is similar to scenario 400 except for events 607 and 609. Events 602, 604, 606, 608, 610, 612, 614, 615, 616, 618, 694, 636 are similar to events 402, 404, 406, 408, 410, 412, 414, 415, 416, 418, 494, 436. The example and implementation of FIG4 may be applicable to FIG6. The differences between FIG4 and FIG6 are described below.
[0129] In scenario 600, UE 102 initially operates 602 in an inactive state with an SDT configuration configured by base station 104, as described above with respect to FIG. 3 or 4. In some implementations, the SDT configuration includes one or more CG-SDT configurations. In such a case, UE 102 may discard the CG-SDT configuration because base station 106 does not configure the CG-SDT configuration for UE 102, i.e., the CG-SDT configuration is not valid.
[0130] In response to or after receiving 606 the UL RRC message, the CU-CP 172A sends 607 a retrieve UE context request message to the base station 104. In response, the base station 104 sends 609 a retrieve UE context response message to the CU-CP 172A. After receiving the retrieve UE context response message, the CU-CP 172A sends 608 a UE context setup request message to the DU 174 and receives 610 a UE context setup response message from the DU 174. The CU-CP 172A sends 612 a bearer context setup request message to the CU-UP 172B to request the CU-UP 172B to set the bearer context of the SDT DRB configured in the SDT configuration. In response, the CU-UP 172B sets the bearer context of the SDT DRB and sends 614 a bearer context setup response message to the CU-CP 172A to confirm that the bearer context of the SDT DRB has been set.
[0131] In some implementations, the base station 104 may include the SDT configuration in the retrieve UE context response message. In the case where the SDT configuration includes one or more CG-SDT configurations, the base station 104 may exclude the CG-SDT configuration from the SDT configuration. Alternatively, the CU-CP 172A still includes the CG-SDT configuration from the SDT configuration. In some embodiments, when the CU-CP 172A receives the CG-SDT configuration, the CU-CP 172A discards the CG-SDT configuration. In some embodiments, in the case where the CU-CP 172A does not support incremental configuration, the CU-CP 172A may discard the SDT configuration. In the case where the CU-CP 172A supports incremental configuration, when the CU-CP 172A determines to transition the UE to an inactive state at the SDT completion process 694 (similar to process 494), the CU-CP 172A may take the SDT configuration (e.g., the first SDT configuration) into account.
[0132] In other implementations, the CU-CP 172A avoids including the SDT configuration in the Retrieve UE Context Request message.
[0133] Next, several example methods that may be implemented in one or more RAN nodes (eg, a base station, DU, or CU) to support data communication in an inactive state are discussed with reference to FIGS. 7A to 11 .
[0134] 7A illustrates a method 700A that may be implemented / performed by a first RAN node (eg, base station 104, CU 172 of base station 104, or CU-CP 172A of base station 104) for managing SDT of a UE (eg, UE 102).
[0135] Method 700A begins at block 702, where a first RAN node communicates with a UE using at least one configuration (e.g., events 312, 314, 318, 390, 320, 334, 394, 514, 518, 596, 598). At block 704, the first RAN node sends an RRC release message including an SDT configuration to the UE to stop communicating with the UE (e.g., events 334, 434, 394, 494, 594, 595). At block 706, the first RAN node receives a retrieve UE context request message requesting a UE context of the UE from a second RAN node (e.g., base station 106, CU 172 of base station 106, or CU-CP 172A of base station 106) (e.g., event 607). At block 708, the first RAN node sends a retrieve UE context response message including the at least one configuration and excluding the SDT configuration to the second RAN node (e.g., event 609).
[0136] In some implementations, the at least one configuration includes a plurality of configuration parameters. In some implementations, at block 702, the first RAN node communicates with a UE operating in a connected state. In some implementations, when the UE operates in a connected state, the first RAN node sends an RRC reconfiguration message to the UE including some or all of the plurality of configuration parameters. In other implementations, when the UE operates in an inactive state, the first RAN node sends an RRC recovery message to the UE including some or all of the plurality of configuration parameters. In some implementations, the plurality of configuration parameters may be configuration parameters included in a CellGroupConfig IE.
[0137] 7B is a flow chart of an example method 700B, which is similar to method 700A, except that method 700B includes blocks 705 and 709 instead of blocks 704 and 706. At block 705, the first RAN node sends an RRC release message including the SDT CU configuration and the SDT DU configuration to the UE to stop communicating with the UE (e.g., events 334, 434, 394, 494, 594, 595). At block 709, the first RAN node sends a retrieve UE context response message including the SDT CU configuration and excluding the SDT DU configuration to the second RAN node (e.g., events 334, 434, 394, 494, 594, 595).
[0138] 8A illustrates a method 800A that may be implemented / performed by a first RAN node (eg, base station 106, CU 172 of base station 106, or CU-CP 172A of base station 106) for managing SDT of a UE (eg, UE 102).
[0139] Method 800A begins at block 802, where a first RAN node receives an UL RRC message from a UE operating in an inactive state (e.g., events 404, 503, 542, 604). At block 804, in response to the UL RRC message, the first RAN node sends a retrieve UE context request message to a second RAN node (e.g., base station 104, CU 172 of base station 104, or CU-CP 172A of base station 104) to request a UE context for the UE (e.g., event 607). At block 806, the first RAN node receives a retrieve UE context response message including an SDT configuration for the UE and the UE context from the second RAN node (e.g., event 609). At block 808, the RAN node discards the SDT configuration and retains the UE context. At block 810, the RAN node communicates with the UE based on the UE context (e.g., events 512, 514, 518, 596, 598, 618, 694).
[0140] 8B is a flow diagram of an example method 800B, which is similar to method 800A, except that method 800B includes block 807 instead of block 806, and includes block 809 instead of block 808. At block 807, the first RAN node receives a retrieve UE context response message including an SDT CU configuration, an SDT DU configuration, and a UE context for the UE from the second RAN node (e.g., event 609). At block 809, the first RAN node retains the SDT CU configuration and the UE context, and discards the SDT DU configuration.
[0141] 9 illustrates a method 900 that may be implemented / performed by a first RAN node (eg, base station 104, CU 172, or CU-CP 172A) for managing SDT of a UE (eg, UE 102).
[0142] Method 900 begins at block 902, where a first RAN node sends an RRC release message including an SDT configuration to a UE to stop communicating with the UE (e.g., events 332, 334, 432, 434, 394, 494, 594, 595). At block 904, the first RAN node communicates with the UE operating in an inactive state using the SDT configuration (e.g., events 404, 406, 418, 492, 420, 421, 432, 434, 494, 592, 594, 593, 594). At block 906, the first RAN node transitions the UE to a connected state (e.g., events 510, 512). At block 908, the first RAN node communicates with the UE operating in a connected state using the at least one configuration (e.g., events 514, 516, 518). At block 910, the first RAN node determines to hand over the UE to a second RAN node (e.g., a base station 106, a CU 172 of the base station 106, or a CU-CP 172A of the base station 106). At block 912, in response to the determination, the RAN node sends handover preparation information including the at least one configuration and excluding the SDT configuration to the second RAN node. At block 914, the RAN node receives a handover command message for the UE from the second RAN node. At block 916, the RAN sends a handover command to the UE.
[0143] In some implementations, the second RAN node may generate a handover command message, which may be or include, for example, an RRC reconfiguration message. In some implementations, the first RAN node sends a handover request message including handover preparation information to the second RAN node. In response, the first RAN node receives a handover request confirmation message including the handover command message from the second RAN node.
[0144] In some implementations, the first RAN node sends the handover preparation information to the second RAN node via the CN (e.g., CN 110), and receives the handover command message from the second RAN node via the CN. For example, the first RAN node sends a handover request message including the handover preparation information to the CN (e.g., CN 110), and the CN then sends a handover request message including the handover preparation information to the second RAN node. In response, the second RAN node sends a handover request confirmation message including the handover command message to the CN, and the CN then sends a handover command message (i.e., an interface message, such as an X2 or Xn interface message) including the handover command message to the first RAN node.
[0145] 10 illustrates a method 1000 that may be implemented / performed by a first RAN node (eg, the base station 106, the CU 172 of the base station 106, or the CU-CP 172A of the base station 106) for managing SDT of a UE (eg, the UE 102).
[0146] The method 1000 begins at block 1002, where a first RAN node receives handover preparation information including at least one configuration and an SDT configuration for a UE from a second RAN node. At block 1004, the RAN node sends a handover command for the UE to the second RAN node. At block 1006, the RAN node retains the at least one configuration and discards the SDT configuration. At block 1008, the RAN node performs a random access procedure with the UE. At block 1010, the RAN node receives a handover completion message from the UE.
[0147] In some implementations, the first RAN node and the second RAN node of FIG. 10 may be the second RAN node and the first RAN node of FIG. 9 , respectively. The examples and implementations of FIG. 9 may be applicable to FIG.
[0148] FIG. 11 illustrates a method 1100 that may be implemented by a first CU (eg, CU 172 or CU-CP 172A) for managing SDT of a UE (eg, UE 102).
[0149] Method 1100 begins at block 1102, where the CU communicates with the UE. At block 1104, the first CU determines to send handover preparation information to the RAN node. At block 1106, the first CU determines whether the RAN node is a DU. If the CU determines that the RAN node is a DU, the process proceeds to block 1108. At block 1108, the first CU sends handover preparation information to the DU excluding a configuration (e.g., the SDT configuration described above). In some implementations, the first CU may send a CU to DU message including the handover preparation information to the DU. Otherwise, if the first CU determines that the RAN node is not a DU (e.g., the RAN node is a second CU or a base station), the process proceeds to block 1110. At block 1110, the first CU sends the handover preparation information including the configuration to the second CU. The example and implementation of sending handover preparation information in FIG. 9 may be applicable to FIG. 11.
[0150] The following list of examples reflects the various implementations expressly contemplated by the present disclosure:
[0151] Example 1. A method of managing configuration information for small data transfer (SDT) operations performed by a first radio access network (RAN) node, the method comprising: receiving a radio resource control (RRC) message from a user equipment (UE); receiving, from the second RAN node during a handover procedure from the second RAN node to the first RAN node, an SDT configuration for use by the UE when the UE operates in an RRC inactive state; and after the handover procedure, communicating with the UE based on a UE context of the UE operating in the RRC inactive state.
[0152] Example 2. The method of Example 1, wherein receiving the SDT configuration comprises receiving a UE context response message including the SDT configuration.
[0153] Example 3. The method of Example 2, further comprising: sending a UE Context Request message to the second RAN node after receiving the RRC message and before receiving the UE Context Response message.
[0154] Example 4. The method of Example 2 or 3, wherein receiving the SDT configuration comprises receiving a UE context response message including the SDT configuration and the UE context.
[0155] Example 5. A method as described in any one of Examples 1 to 4, wherein the RRC message is an RRC recovery message.
[0156] Example 6. The method of any one of Examples 1 to 5, further comprising: after receiving the SDT configuration, discarding at least a portion of the SDT configuration.
[0157] Example 7. A method of managing configuration information for small data transfer (SDT) operations performed by a first radio access network (RAN) node, the method comprising: receiving, from a second RAN node during a handover process from the second RAN node to the first RAN node, an SDT configuration for use by a user equipment (UE) when the UE operates in a radio resource control (RRC) inactive state; discarding at least a portion of the SDT configuration; and, after the handover process, communicating with the UE operating in the RRC inactive state.
[0158] Example 8. The method as described in Example 7 further includes: before receiving the SDT configuration from the second RAN node, sending a message requesting a UE context to the second RAN node, wherein receiving the SDT configuration includes receiving a message including the SDT configuration and the UE context, and wherein communicating with the UE operating in the RRC inactive state includes communicating with the UE based on the UE context.
[0159] Example 9. The method of Example 8, wherein discarding comprises discarding the SDT configuration.
[0160] Example 10. The method of Example 8, wherein discarding comprises discarding an SDT distributed unit (SDT DU) configuration and retaining an SDT central unit (SDT CU) configuration.
[0161] Example 11. The method as described in any one of Examples 8 to 10 further includes: before sending the message requesting the UE context, receiving an RRC message and uplink data from a UE operating in an RRC inactive state.
[0162] Example 12. The method of Example 7, wherein receiving the SDT configuration comprises receiving handover preparation information including a non-SDT configuration and the SDT configuration from the second RAN node, and wherein the method comprises retaining the non-SDT configuration and discarding the SDT configuration.
[0163] Example 13. The method of Example 12, further comprising: after receiving the handover preparation information, sending a handover command for the UE to the second RAN node.
[0164] Example 14. The method of Example 12 or 13, further comprising, after sending the handover command: performing a random access procedure with the UE; and receiving a handover complete message from the UE.
[0165] Example 15. The method of any one of Examples 12 to 14, wherein receiving the handover preparation information occurs via a core network (CN).
[0166] Example 16. A method as described in any one of Examples 7 to 15, wherein: the first RAN node is a target base station in a handover process; and the second RAN node is a source base station in the handover process.
[0167] Example 17. A method as described in any of Examples 7 to 15, wherein: the first RAN node is a central unit (CU) of a distributed base station, which is a target base station in a handover process; the second RAN node is a source base station in the handover process; and communication with the UE occurs via a distributed unit (DU) of the distributed base station.
[0168] Example 18. A method of managing configuration information for a small data transfer (SDT) operation performed by a first radio access network (RAN) node, the method comprising: communicating with a user equipment (UE) operating in a radio resource control (RRC) inactive state using an SDT configuration; transitioning the UE from the RRC inactive state to an RRC connected state; communicating with the UE operating in the RRC connected state using a non-SDT configuration; determining to hand over the UE to a second RAN node; and in response to the determination, sending handover preparation information to the second RAN node, the handover preparation information excluding the SDT configuration.
[0169] Example 19. The method of Example 18, wherein the handover preparation information includes a non-SDT configuration.
[0170] Example 20. The method of Example 18 or 19, further comprising: before communicating with the UE operating in the RRC inactive state, sending an RRC release message including the SDT configuration to the UE.
[0171] Example 21. A method as described in any of Examples 18 to 20, wherein transitioning the UE to an RRC connected state includes sending an RRC resume message to the UE.
[0172] Example 22. The method of any one of Examples 18 to 21, further comprising, after sending the handover preparation information to the second RAN node: receiving a handover command for the UE from the second RAN node; and sending the handover command to the UE.
[0173] Example 23. The method of any one of Examples 18 to 22, wherein sending the handover preparation information to the second RAN node comprises sending a handover request message including the handover preparation information to the second RAN node.
[0174] Example 24. The method of any one of Examples 18 to 23, wherein sending the handover preparation information to the second RAN node occurs via a core network (CN).
[0175] Example 25. A method as described in any one of Examples 18 to 24, wherein: the first RAN node is a source base station in a handover process; and the second RAN node is a target base station in the handover process.
[0176] Example 26. A method as described in any of Examples 18 to 24, wherein: the first RAN node is a central unit (CU) of a distributed base station, which is a source base station in a handover process; the second RAN node is a target base station in the handover process; and communication with a UE operating in an RRC inactive state and communication with a UE operating in an RRC connected state occur via a distributed unit (DU) of the distributed base station.
[0177] Example 27. A first radio access network (RAN) node comprising one or more processors and configured to perform a method as described in any one of Examples 1 to 26.
[0178] Example 28. A method for managing configuration information performed by a central unit (CU) of a distributed base station in a radio access network (RAN), the method comprising: communicating with a user equipment (UE); and sending handover preparation information to a RAN node, wherein (i) when the RAN node is another base station or another central unit (CU), the handover preparation information includes a configuration for the UE to use when communicating with the RAN, and (ii) when the RAN node is a distributed unit (DU), the handover preparation information excludes the configuration.
[0179] Example 29. The method of Example 28, wherein the RAN node is another base station or another CU, and the handover preparation information includes the configuration.
[0180] Example 30. The method of Example 28, wherein the RAN node is a DU, and the handover preparation information excludes the configuration.
[0181] Example 31. The method of any one of Examples 28 to 30, wherein the configuration is a small data transfer (SDT) configuration for use by the UE when the UE operates in a radio resource control (RRC) inactive state.
[0182] Example 32. The method of any one of Examples 28 to 31, wherein sending the handover preparation information to the RAN node comprises sending a handover request message including the handover preparation information to the RAN node.
[0183] Example 33. The method of any one of Examples 28 to 32, wherein sending the handover preparation information to the RAN node occurs via a core network (CN).
[0184] Example 34. A central unit (CU) of a distributed base station, the CU comprising one or more processors and configured to perform a method as described in any one of Examples 28 to 33.
[0185] The following description may be applicable to the above description.
[0186] In general, the description of any one of the above figures may apply to the other of the above figures. In some implementations, "message" is used and "information element (IE)" can be used to replace "message", and vice versa. In some implementations, "IE" is used and "field" can be used to replace "IE", and vice versa. In some implementations, "configuration" can be replaced with "configurations" or "configuration parameters", and vice versa. In some implementations, "small data transmission" can be replaced with "early data transmission (EDT)", and "SDT" can be replaced with "EDT", and vice versa. In some implementations, "small data transmission" can be replaced with "small data communication", and vice versa. In some implementations, "stop" can be replaced with "pause".
[0187] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell, or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0188] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module can be a software module (e.g., a code or machine-readable instruction stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and can be configured or arranged in a particular manner. A hardware module can include dedicated circuits or logic that are permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.). A hardware module can also include programmable logic or circuits that are temporarily configured by software to perform certain operations (e.g., as contained in a general-purpose processor or other programmable processor). The decision to implement a hardware module in a dedicated and permanently configured circuit or in a temporarily configured circuit (e.g., configured by software) can be driven by cost and time considerations.
[0189] When implemented in software, the techniques may be provided as part of an operating system, as a library used by multiple applications, as a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.
Claims
1. A method for managing configuration information for a small data transfer (SDT) operation performed by a first radio access network (RAN) node, the method comprising: receiving a radio resource control (RRC) message from a user equipment (UE); receiving, from the second RAN node during a handover procedure from the second RAN node to the first RAN node, an SDT configuration for use by the UE when the UE operates in an RRC inactive state; as well as After the handover process, communicating with the UE is performed based on a UE context of the UE operating in the RRC inactive state. 2 . The method of claim 1 , wherein receiving the SDT configuration comprises receiving a UE context response message including the SDT configuration.
3. The method of claim 2, further comprising: After receiving the RRC message and before receiving the UE Context Response message, sending a UE Context Request message to the second RAN node. 4 . The method of claim 2 , wherein receiving the SDT configuration comprises receiving a UE context response message including the SDT configuration and the UE context.
5. The method according to any one of claims 1 to 4, wherein the RRC message is an RRC recovery message.
6. The method according to any one of claims 1 to 5, further comprising: After receiving the SDT configuration, at least a portion of the SDT configuration is discarded.
7. A method, performed by a first radio access network (RAN) node, for managing configuration information for a small data transfer (SDT) operation, the method comprising: communicating with a user equipment (UE) operating in a radio resource control (RRC) inactive state using an SDT configuration; Transitioning the UE from the RRC inactive state to an RRC connected state; communicating with the UE operating in the RRC connected state using a non-SDT configuration; Determining to hand over the UE to a second RAN node; as well as In response to the determination, handover preparation information is sent to the second RAN node, the handover preparation information excluding the SDT configuration. The method of claim 7 , wherein the handover preparation information includes the non-SDT configuration.
9. The method of claim 7 or 8, further comprising: Prior to communicating with the UE operating in the RRC inactive state, an RRC release message including the SDT configuration is sent to the UE.
10. The method of any one of claims 7 to 9, wherein transitioning the UE to the RRC connected state comprises sending an RRC resume message to the UE.
11. The method according to any one of claims 7 to 10, further comprising, after sending the handover preparation information to the second RAN node: receiving a handover command for the UE from the second RAN node; and The handover command is sent to the UE.
12. The method of any one of claims 7 to 11, wherein sending the handover preparation information to the second RAN node comprises sending a handover request message including the handover preparation information to the second RAN node.
13. The method of any one of claims 7 to 12, wherein sending the handover preparation information to the second RAN node occurs via a Core Network (CN).
14. The method of any one of claims 7 to 13, wherein: The first RAN node is a source base station in a handover process; and The second RAN node is a target base station in the handover process.
15. The method of any one of claims 7 to 13, wherein: The first RAN node is a central unit (CU) of a distributed base station, and the distributed base station is a source base station in a handover process; The second RAN node is a target base station in the handover process; and Communicating with the UE operating in the RRC inactive state and communicating with the UE operating in the RRC connected state occurs via a distributed unit (DU) of the distributed base station.
16. A first Radio Access Network (RAN) node, the first RAN node comprising one or more processors and configured to perform the method of any one of claims 1 to 15.
Citation Information
Cited By
Communication methods and communication apparatus
WO2026157725A1
