Managing uplink synchronization for user equipment

By managing time alignment timers in the DU and CU of the distributed base station, the problem of uplink synchronization management of user equipment in the RRC_INACTIVE or RRC_IDLE state is solved, and the data communication delay and network efficiency are reduced.

CN118923167APending Publication Date: 2024-11-08GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030517.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-10-24
Filing Date
2023-02-10
Publication Date
2024-11-08

Smart Images

  • Figure CN118923167A_ABST
    Figure CN118923167A_ABST
Patent Text Reader

Abstract

A method of managing time alignment performed by a DU of a distributed base station including the DU and a CU includes: transmitting a timing advance command to a UE; starting or restarting a first time alignment timer indicating validity of the configured grant configuration when the UE is in an RRC connected state with the RAN; and determining to transition the UE from the RRC connected state to the RRC inactive state after starting or restarting the first time alignment timer. The method further includes, in response to the determination, (i) transitioning the UE from the RRC connected state to the RRC inactive state by sending a first message to the UE, (ii) stopping the first time alignment timer, and (iii) starting or restarting a second time alignment timer indicating validity of the CG-SDT configuration when the UE is in the RRC inactive state.
Need to check novelty before this filing date? Find Prior Art

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] Typically, a base station operating a cellular radio access network (RAN) uses a certain 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 located 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 use RAN-level base station coordination and RAN paging procedures to more quickly transition back to the RRC_CONNECTED state. In some cases, the UE in the RRC_INACTIVE state has only a relatively small packet to send. For cases such as these, 3GPP is discussing a small data transfer (SDT) procedure to enable the wireless communication standard 5G NR (New Radio) 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 data waiting to be sent (on all radio bearers for which SDT is enabled) is below a configured threshold, (2) the downlink (DL) reference signal received 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 a transmission on 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 may send an initial transmission of data in the payload of message 3 (Msg3) of a 4-step random access procedure or message A (MsgA) of a 2-step random access procedure. After completion of the random access procedure, the network may then schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.

[0006] CG-SDT can only be initiated by a valid uplink (UL) timing alignment. The UE maintains UL timing alignment based on the SDT-specific timing alignment timer configured by the network and the DL RSRP of the configured number of highest-ranked SSBs (synchronization signal blocks). After the SDT-specific timing alignment timer expires, the CG resources are released. After 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 or 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 not clear how to manage UL synchronization of CG-SDT. Failure to properly manage UL synchronization may result in data communication delays and / or other network inefficiencies. Summary of the invention

[0008] In some implementations of the present disclosure, at any given moment, for a particular UE, the base station maintains only one time alignment timer. In particular, when the base station transitions the UE from a connected state to an inactive state and configures the UE for CG-SDT operation (e.g., by sending an RRC release message containing a CG-SDT configuration to the UE), the base station stops the first time alignment timer used for connected state communication with the UE, and starts or restarts the second time alignment timer to be used for CG-SDT communication with the UE. At a later time, when the UE is transitioned back to a connected state, the base station may stop the second time alignment timer and start the first time alignment timer.

[0009] In other implementations, when the base station transitions the UE from a connected state to an inactive state and configures the UE for CG-SDT operation, the base station starts or restarts a second time alignment timer (i.e., a timer to be used for CG-SDT communication with the UE), but continues to run a first time alignment timer (i.e., a timer for connected state communication with the UE). For example, in some implementations in which the base station transitions the UE to an inactive state by sending an RRC release message to the UE, the base station can avoid stopping the first time alignment timer only if the base station includes the CG-SDT configuration in the RRC release message. For example, the base station can avoid stopping the first time alignment timer even if the base station resets the MAC entity when sending the RRC release message.

[0010] In still other implementations, the base station does not use a dedicated CG-SDT time alignment timer, but uses the same time alignment timer for both connected state communications and CG-SDT communications with a particular UE. In these implementations, when the base station transitions the UE from a connected state to an inactive state and configures the UE for CG-SDT operation, the base station restarts the (single) time alignment timer.

[0011] As used herein, unless otherwise specifically indicated, a "timer" may refer to a time alignment timer (e.g., a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration to be used when the UE is in an inactive state, or a non-CG-SDT time alignment timer indicating the validity of a non-CG-SDT configuration to be used when the UE is in a connected state).

[0012] In one aspect, a method for managing time alignment is performed by a distributed unit (DU) of a distributed base station including a distributed unit (DU) and a central unit (CU). The method includes: sending a timing advance command to a user equipment (UE); starting or restarting a first time alignment timer indicating the validity of a configuration grant (CG) configuration when the UE is in a radio resource control (RRC) connected state with a radio access network (RAN) including the distributed base station; after starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to the RRC inactive state; and in response to the determination, (i) transitioning the UE from the RRC connected state to the inactive state by sending a first message to the UE, (ii) stopping the first time alignment timer, and (iii) starting or restarting a second time alignment timer indicating the validity of a CG small data transmission (CG-SDT) configuration when the UE is in the RRC inactive state.

[0013] In another aspect, a method for managing time alignment is performed by a distributed unit (DU) of a distributed base station including a distributed unit (DU) and a central unit (CU). The method includes: sending a timing advance command to a user equipment (UE); starting or restarting a first time alignment timer indicating the validity of a configuration grant (CG) configuration when the UE is in a radio resource control (RRC) connected state with a radio access network (RAN) including the distributed base station; after starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to the RRC inactive state; and in response to the determination, (i) transitioning the UE from the connected state to the RRC inactive state by sending a first message to the UE, and (ii) starting or restarting a second time alignment timer indicating the validity of a CG small data transmission (CG-SDT) configuration when the UE is in the RRC inactive state while continuing to run the first time alignment timer. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG1A is a block diagram of an example wireless communication system in which a user device and a base station of the present disclosure may implement the techniques of the present disclosure, for example, to reduce latency in data communications;

[0015] FIG. 1B is a block diagram of an example base station in which a central unit (CU) and a distributed unit (DU) may operate in the system of FIG. 1A ;

[0016] FIG2A is a block diagram of an example protocol stack according to which the UE of FIG1A communicates with a base station;

[0017] FIG2B is a block diagram of an example protocol stack according to which the UE of FIG1A communicates with the CU and the DU;

[0018] 3 to 5B are message sequence charts illustrating several scenarios in which the apparatus of FIGS. 1A to 2B may implement uplink synchronization according to the techniques of the present disclosure; and

[0019] 6A-11 illustrate several methods for achieving uplink synchronization that may be implemented by one or more of the apparatuses of FIGS. 1A-2B , according to techniques of this disclosure. DETAILED DESCRIPTION

[0020] 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 for managing early data communications and transitioning the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, small data communications may refer to small data transmission (SDT) from a network perspective (i.e., SDT in the downlink direction), or to SDT from a UE perspective (i.e., SDT in the uplink direction), unless the context clearly indicates a more specific meaning.

[0021] 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.

[0022] 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). Base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).

[0023] 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. Generally speaking, the SGW 112 is configured to deliver user plane packets related to 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 deliver user plane packets associated with audio calls, video calls, Internet services, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.

[0024] As shown in FIG1A , 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 a cell, reselect a cell, or switch from one of cells 124 and 126 to another. In order to directly exchange messages or information, 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.

[0025] 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 examples below relate to the RRC_INACTIVE or RRC_IDLE states of the RRC protocol.

[0026] 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 may refer to non-signaling, non-control-plane information at one or more protocol layers above a layer of a protocol for controlling radio resources (e.g., RRC), above a layer of a protocol for controlling MM, above a layer of a protocol for controlling SM, and / or above a 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. In addition, 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 full configuration, or to a subset of the parameters of a full configuration (e.g., an "incremental" or other partial configuration that can augment an existing configuration without completely replacing it).

[0027] 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 in a second UL PDU along with the first 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. In some implementations, the NAS ID may be an S-Temporary Mobile Subscriber Identity (S-TMSI) or a Globally Unique Temporary Identifier (GUTI).

[0028] 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 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.

[0029] 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 secure SDU in a first UL PDU (e.g., 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 a secure 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 include the UL PDCP PDU in the UL RLC PDU, and then include the UL RLC PDU in the UL MAC PDU. RRCint The 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).

[0030] In other implementations, the data is a UL SDU of NAS. The UE 102 applies a security function to the SDU and includes the secure SDU in a first UL PDU (such as a NAS PDU) that may be associated with a NAS layer. For example, the NAS layer may be an MM sublayer or an SM sublayer of 5G, an evolved packet system (EPS), or 6G. The UE 102 may then include the UL NAS PDU in a second UL PDU (such as a UL RRC message). Thus, in these cases, the UE 102 sends a (first) secure UL NAS PDU in a 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.

[0031] 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 UE 102, as described above.

[0032] More generally, the UE 102 may secure data using ciphering and / or integrity protection, include the secured 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.

[0033] 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 decrypts the encrypted packet by using at least one security key (e.g., an encryption and / or decryption key) to obtain data. 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., an 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. In addition, 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 the 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 the edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.

[0034] 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 decrypts the encrypted packet by using at least one security key (e.g., encryption and / or decryption key) to obtain the data. 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. In addition, 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.

[0035] In other scenarios and implementations, the base station 104 can retrieve the UE ID of the UE 102 from the UL RRC message and recognize that the base station 104 stores the UE context information of the UE 102. Accordingly, 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.

[0036] Additionally, 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.

[0037] 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 DL PDU in a second DL PDU. In order to make the data secure, 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. In addition, 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.

[0038] 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.

[0039] 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).

[0040] 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, based on the ID of the UE 102, the DCI, and the scrambled CRC, confirm that a physical downlink shared channel (PDSCH) including a second DL PDU is addressed to the UE 102. 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 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 verifies 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.

[0041] 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, and the one or more general-purpose processors execute the instructions. 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 may also 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 configured to manage uplink and / or downlink communications when one or more UEs are operating in an RRC_INACTIVE or RRC_IDLE state. The base station 106 may include substantially 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.

[0042] 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 the base station 106 sends DL data and / or receives UL data. The processing hardware may also include an RRC controller 156 to implement processes and message delivery at the RRC sublayer of the protocol communication stack.

[0043] FIG. 1B depicts an example distributed or decomposed implementation of a base station 170 that may represent either or both of the base stations 104, 106. In this implementation, the base station 170 includes a central unit (CU) 172 and one or more distributed units (DUs) 174. The 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 executable on the general-purpose processors, and / or a dedicated processing unit. For example, the CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as the PDCP controllers 134, 144, the RRC controllers 136, 146, and / or the RRC inactive controllers 138, 148. In some implementations, the CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, the CU 172 does not include an RLC controller.

[0044] Each of the DUs 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 the one or more general-purpose processors, and / or a dedicated processing unit. For example, the processing hardware may include: a MAC controller (e.g., MAC controllers 132, 142), which is configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller, which is configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller, which is configured to manage or control one or more physical layer operations or processes.

[0045] 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.

[0046] 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).

[0047] 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 service requested by 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.

[0048] Figure 2A shows in a simplified manner an example protocol stack 200 according to which the UE 102 can communicate with the eNB / ng-eNB 201A or gNB 201B (e.g., one or both of the base stations 104, 106).

[0049] 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, the UE 102 supports both EUTRA and NR stacks, as shown in FIG2A, to support switching between EUTRA and NR base stations and / or to support DC on EUTRA and NR interfaces. In addition, as shown in FIG2A, the UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210.

[0050] 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.

[0051] On the control plane, for example, 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 RRC messages or NAS messages. 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.

[0052] FIG. 2B illustrates in a simplified manner an example protocol stack 250 with which the 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 the base station 104 or 106 can maintain all control and upper layer functionality (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 the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and SRBs to the RRC 214.

[0053] Next, several example scenarios involving various components of FIG. 1A and transmitting data in an inactive or idle state are discussed with reference to FIG. 3 to FIG. 5B . To simplify the following description, “inactive state” may represent RRC_INACTIVE or RRC_IDLE state, and “connected state” may represent RRC_CONNECTED state.

[0054] 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 the CU-UP 172B via the DU by using a CU configuration (i.e., a first non-SDT-CU 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 to the CU-CP 172A a UE context modification response message including a non-SDT configuration for the UE 102 (i.e., a second non-SDT configuration). The 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 the DU 174. In turn, the DU 174 sends 312 the RRC reconfiguration message to the UE 102. In response, the UE 102 sends 314 an RRC reconfiguration complete message to the DU 174, which in turn sends 316 a first DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to the CU-CP 172A.

[0055] 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 318 with the CU-CP 172A and / or CU-UP 172B via the DU. In the case where 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 case where 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 that is 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 318 using the second non-SDT CU configuration and also using configuration parameters in the first non-SDT CU configuration that are not expanded by the second non-SDT CU configuration. 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), and when the UE 102 operates in a connected state, the UE 102 and the CU 172 use the configuration parameters to communicate with each other. Similarly, the second non-SDT CU configuration may include configuration parameters related to the operation of the RRC and / or PDCP protocol layers, and when the UE 102 operates in a connected state, the UE 102 and the CU 172 use the configuration parameters to communicate with each other. 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.

[0056] 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 that is 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), and the UE 102 and the DU 174 communicate with each other using the configuration parameters 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 are used by the UE 102 and the DU 174 to communicate with each other when the UE 102 operates in the 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 includes 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-SDTDU configuration are CellGroupConfig IEs.

[0057] Events 306, 308, 310, 312, 314, 316 and 318 are collectively referred to as a non-SDT resource (re)configuration process 390 in FIG. 3, which may be optional.

[0058] 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 data inactivity of the UE 102 (i.e., based on the UE 102 in the connected state having no 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 UE assistance information (e.g., UEAssistanceInformation message) indicating that the UE 102 requests to transition to the inactive state of the configured SDT to the DU 174. In turn, 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 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 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 case where 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.

[0059] 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 has sent any data in the downlink direction or uplink direction, respectively, during the specific period. In response to the determination, CU-CP 172A may determine to transition UE 102 to an inactive state in which SDT is configured. Alternatively, CU-CP 172A may determine to transition UE 102 to an inactive state in which SDT is not configured in response to determining that UE 102 is in data inactivity.

[0060] In response to or after determining that the UE 102 is in data inactivity (for a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, 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 a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or after determining that the UE 102 is in data inactivity (for a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, 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 instruct 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) 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, 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, DU 174 sends an additional DU to CU message (e.g., a UE context modification request message) including the SDT DU configuration to CU-CP 172A. CU-CP 172A may send an additional CU to DU message (e.g., a UE context modification confirmation message) to DU 174 in response to the additional CU to DU message. In some alternative implementations, before determining that UE 102 is in data inactivity, CU-CP 172A may send a second CU to DU message and receive a second DU to CU message or additional DU to CU information. In other alternative implementations, CU-CP 172A may include an SDT request indication in the first CU to DU message of event 308, and DU 174 includes the SDT DU configuration in the first DU to CU message of event 310 in response to the SDT request indication.

[0061] In response to determining to transition UE 102 to an inactive state with SDT configured, CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message, 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) to DU 174, wherein the third CU to DU message includes the RRC release message. In turn, DU 174 sends 334 an 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 instructs UE 102 to transition to an inactive state. After 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 the 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. 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 in response to the third CU-to-DU message.

[0062] When operating 302 in a connected state, the UE 102 uses the C-RNTI to monitor the PDCCH to receive the DCI. In response to receiving 334 to the RRC release message, or after receiving 334 to the RRC release message, the UE 102 stops using the C-RNTI to monitor the PDCCH. In some implementations, the UE 102 may retain the C-RNTI in response to receiving 334 to the RRC release message or transitioning 336 from the connected state to the inactive state, or after receiving 334 to the RRC release message or transitioning 336 from the connected state to the inactive state. In some implementations, the UE 102 performs a two-step or four-step random access procedure with the base station 104 (e.g., CU-CP 172A and / or DU 174) and receives a random access response message including the C-RNTI from the DU 174 during the random access procedure. In other implementations, UE 102 receives an RRC message (eg, an RRC reconfiguration message) including the C-RNTI from CU-CP 172A via DU 174 or from another base station (eg, base station 106) not shown in FIG. 3 .

[0063] 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 .

[0064] 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 instructs 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 instructs 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 non-SDT DU configuration and / or the second non-SDT DU configuration.

[0065] In some implementations, CU-CP 172A does not include an indication instructing DU 174 to retain the SDT DU configuration in a 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 instructing 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 instructing 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 UE102. Therefore, DU 174 maintains the SDT DU configuration in response to the third CU to DU message excluding the indication. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.

[0066] In some implementations, the SDT CU configuration (e.g., SDT-Config IE) includes a DRB list (e.g., std-DRB-List), which includes a DRB ID list indicating the IDs of the DRBs configured for SDT. In some implementations, the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication), which indicates the SRB2 configured for SDT. In some implementations, the SDT CU configuration may include a compression protocol continue indication (e.g., sdt-DRB-ContinueROHC), which indicates whether the PDCP entity of the DRB configured for SDT continues during SDT operation (i.e., the initial and / or subsequent SDT described in Figure 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. In some implementations, the CU-CP 172A may include the SDT DU configuration in the SDT CU configuration. The “SDT CU configuration” may also be referred to as the “SDT configuration” for short.

[0067] 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 portion (BWP) configuration for CG-SDT, a time alignment timer value for CG-SDT (i.e., 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 configured grant configuration for CG-SDT, as described for 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 for 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.

[0068] In some implementations, the DU 174 may start or restart the DU CG-SDT timer in response to 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 the CU 172, receiving 332 a third CU to DU information, or sending 334 a CG-SDT configuration to the UE 102, 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 the CU 172, receiving 332 a third CU to DU information, or sending 334 a CG-SDT configuration to the UE 102. In some implementations, the 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. If and when the DU CG-SDT timer expires, the DU 174 releases the CG-SDT configuration. When the CG-SDT configuration is released, or after the CG-SDT configuration is released, the DU 174 avoids receiving PUSCH transmissions from the UE 102 on radio resources reserved or configured for the CG-SDT configuration. When the CG-SDT configuration is released, or after the CG-SDT configuration is released, the DU 174 may schedule transmissions of other UEs on radio resources reserved or configured for the CG-SDT configuration.

[0069] As described above, in some implementations, the RRC release message 334 may include a 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 response to receiving the CG-SDT configuration, or after receiving the CG-SDT configuration. In some implementations, the UE 102 may start or restart the UE CG-SDT timer with a CG-SDT time alignment timer value. If and when the CG-SDT timer expires, the UE 102 releases the CG-SDT configuration. When releasing the CG-SDT configuration, 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.

[0070] In some implementations, DU 174 reserves the radio resources configured in the configured authorization configuration. In some implementations, DU 174 releases the radio resources when the SDT DU configuration or the CG-SDT configuration is released. 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 after receiving the third CU to DU message.

[0071] In the case where the SDT DU configuration does not include a configuration for CG-SDT, CU-CP 172A and / or DU 174 configures only 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.

[0072] In some implementations, when determining to transition UE 102 to an inactive state with SDT configured, 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.

[0073] 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.

[0074] In some implementations, in the case where 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. In the case where 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 AMF164), or base station 106. UE capabilities indicate whether UE 102 supports CG-SDT. Therefore, CU-CP 172A can 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).

[0075] In some implementations, depending on whether the UE 102 supports CG-SDT, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In addition to whether the UE 102 supports CG-SDT, depending on whether the DU 174 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. In the case where 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 case where 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 is operating 302 in a connected state or in an inactive state before event 302, DU 174 may receive UE capabilities from CU-CP 172A. Thus, DU 174 may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, DU 174 may send a DU to CU message to CU-CP 172A to indicate whether DU 174 supports or does not support CG-SDT, as described above.

[0076] 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 not configured with SDT to an inactive state configured with SDT. 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 the 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 including a first SDT CU configuration and / or a first SDT DU configuration, similar to the RRC release message of event 334.

[0077] At a later time, the UE 102 operating in an inactive state with SDT configured initiates an SDT. In response to initiating the SDT, 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. The UE 102 may start an SDT session timer in response to initiating the SDT. 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.

[0078] In a scenario where the UE 102 initiates an SDT to send UL data (e.g., a data packet) that is eligible for the SDT, the UE 102 includes the UL data in an initial UL MAC PDU that the UE 102 transmits 404. 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 that the UE 102 transmits 404. 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.

[0079] 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. The UE 102 may receive a message B (MsgB) including a temporary C-RNTI and a timing advance command from the DU 174 in response to the MsgA. Prior to sending 404 the UL MAC PDU, the UE 102 receives two-step random access configuration parameters in system information broadcast by the DU 174 on the cell 124. The DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.

[0080] When UE 102 successfully performs contention resolution in the random access process, UE 102 discards the previously reserved C-RNTI (e.g., described with respect to FIG. 3 ) and determines the temporary C-RNTI as a specific C-RNTI (i.e., a new C-RNTI). UE 102 uses C-RNTI to monitor the PDCCH from DU 174 to communicate 418 data with DU 174. More specifically, UE 102 receives DCI and the CRC of the DCI from DU 174 on the PDCCH and verifies the CRC using 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 uses the uplink grant to send 418 UL data to DU 174. If UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, UE 102 uses the downlink assignment to receive 418 DL data from DU 174.

[0081] In other implementations, where the UE 102 receives such a configuration (as described with respect to FIG. 3 ), the UE 102 may send 404 the UL MAC PDU on the radio resources configured in the CG configuration for SDT (i.e., CG-SDT configuration). Thus, the DU 174 receives 404 the UL MAC PDU on the radio resources.

[0082] In some implementations, the UE 102 may send 418 a subsequent UL MAC PDU 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 the subsequent UL MAC PDU 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 another of the subsequent UL MAC PDUs on the radio resources configured in the uplink grant.

[0083] 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.

[0084] 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.

[0085] 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 use the transport layer information of the CU-UP 172B to send 416 UL data to the CU-UP 172B. In the case where 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. In turn, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the case where 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.

[0086] 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, 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 DL data to UE 102 operating in an inactive state.

[0087] 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.

[0088] 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., an RRC PDU, a PDCP PDU, or an RLC PDU), and the PDU includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.

[0089] Events 404 , 406 , 408 , 410 , 412 , 414 , 415 , and 416 are collectively referred to as small data transfer process 492 in FIG. 4 .

[0090] In some implementations, the UL RRC message is an (existing) RRC recovery request message (e.g., RRCResumeRequest messageRRCResumeRequest 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 an 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.

[0091] 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 the data inactivity of the UE 102 (i.e., based on the fact that the UE 102 in the inactive state has no 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 the 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) or requests to stop the SDT. In turn, 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 or a UE context modification request message of event 408) 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 establishment 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 case where 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. Therefore, 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, the CU-CP 172A may determine that the UE 102 is in data inactivity based on the UE assistance information, the inactivity notification of event 422 , and / or the inactivity notification of event 423 .

[0092] 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 uplink direction, respectively, during the specific period. In response to the determination, CU-CP 172A may determine to stop SDT. Alternatively, CU-CP 172A may determine to immediately stop SDT for UE 102 in response to determining that UE 102 is in data inactivity.

[0093] In response to or after determining that the UE 102 is in data inactivity (for a certain period of time) or determining to transition the UE 102 to an inactive state with SDT configured, 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 (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or after determining that the UE 102 is in data inactivity (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, 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) 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 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, 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, DU 174 sends another DU to CU message (e.g., UE context modification required message) including the second SDT DU configuration to CU-CP 172A. In some alternative implementations, CU-CP 172A may send the second CU to DU message and receive the second DU to CU message (or another DU to CU message) before determining that UE 102 is in data inactivity.

[0094] In response to determining to transition UE 102 to the inactive state for which SDT is configured, CU-CP 172A may generate an RRC release message (e.g., RRCRelease message, RRCConnectionRelease message) to transition UE 102 to the inactive state. CU-CP 172A may include the second SDT DU configuration (if obtained from DU 174) and the second SDT CU configuration in the RRC release message.

[0095] 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.

[0096] 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 an 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 instructs the UE 102 to be in an inactive state (e.g., transition to an inactive state, or maintain an inactive state). After receiving 434 the RRC release message, the UE 102 stops the SDT and remains 436 in the inactive state.

[0097] 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 .

[0098] 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 in 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 after receiving 434 to the RRC release message, UE 102 stops using C-RNTI to monitor PDCCH. UE 102 can retain C-RNTI in response to receiving 434 to the RRC release message or transitioning 436 from a connected state to an inactive state. In the case where the RRC release message 434 configures CG-SDT, in some implementations, UE 102 can retain C-RNTI. In the case where the RRC release message 434 does not configure or release CG-SDT, in some implementations, UE 102 can release C-RNTI.

[0099] 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 with 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 is to update the first SDT CU configuration with the second SDT CU configuration. In such implementations, the UE 102 may update the first SDT CU configuration with 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 is to modify the first SDT CU configuration with the second SDT CU configuration. In such implementations, the UE 102 may modify the first SDT CU configuration with the second SDT CU configuration in response to the modification indication. In yet other implementations, the CU-CP 172A may include in the RRC release message a setup indication indicating that the UE 102 is to 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.

[0100] 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 with the second SDT DU configuration. In some implementations, the DU 174 may include in the second SDT DU configuration an indication indicating that the UE 102 is to update the first SDT DU configuration with the second SDT DU configuration. In such implementations, the UE 102 may update the first SDT DU configuration with 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 indicating that the UE 102 is to modify the first SDT DU configuration with the second SDT DU configuration. In such implementations, the UE 102 may modify the first SDT DU configuration with 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 indicating that the UE 102 is 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.

[0101] In the case where the CU-CP 172A and / or the DU 174 support delta configuration, the CU-CP 172 A may not send 428 a CU to DU message to obtain a second SDT DU configuration from the DU 174. Unless the condition for releasing the first SDT configuration is met, the DU 174 retains the first SDT DU configuration. Alternatively, the CU-CP 172A may include the first SDTDU 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 is to 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 SDTCU configuration and / or the first SDT DU configuration in response to the release indication.

[0102] In the case where the CU-CP 172A and / or the DU 174 do not support incremental configuration, the CU-CP 172A may include the SDTDU configuration and / or the SDT CU configuration in the RRC release message, as described above.

[0103] In response to the third CU-to-DU message, DU 174 may retain the first SDT DU configuration and may or may not release the first non-SDT DU configuration and / or the second non-SDT DU configuration. 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 response to the third CU-to-DU message. In some implementations, if the RRC release message instructs 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 with respect to FIG. 3 ) and at least one SDT configuration (e.g., the SDT DU configuration and the SDT CU configuration described with respect to FIG. 3 ).

[0104] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are collectively referred to as an SDT completion process 494 in FIG. 4, similar to process 394. The examples and implementations of 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, UE 102 may perform 493 another SDT process with base station 104, similar to process 492. After completing process 493, base station 104 may perform 495 an SDT completion process with UE 102, similar to process 494.

[0105] 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 with SDT configured. 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.

[0106] 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.

[0107] 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 an 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 an SDT DU configuration. Before the UE 102 initiates SDT, when the UE operates in an inactive state 402, 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 operates in a connected state as described for FIG. 3, the CU-CP 172A may receive UE capabilities (e.g., UE-NR-Capability IE) of the UE 102 from the UE 102, the CN 110 (e.g., MME 114 or 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).

[0108] In some implementations, depending on whether the UE 102 supports CG-SDT, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In addition to whether the UE 102 supports CG-SDT, depending on whether the DU 174 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. In the case where the UE 102 supports CG-SDT and / or the DU 174 supports or enables CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, 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 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). 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 to indicate whether DU 174 supports or does not support CG-SDT, as described above.

[0109] Referring now to FIG5A , scenario 500A depicts a small data transfer and 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 (similar to event 402). Then, UE 102 performs 592 a small data transfer process with base station 104, similar to event 492.

[0110] 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 radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 may use the C-RNTI to receive an uplink grant from the DU 174 on the PDCCH 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 a 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 a DL data notification (e.g., a DL data notification message) to CU-CP 172A to indicate 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.

[0111] In some implementations, the non-SDT indication message may be an RRC message (eg, a UEAssistanceInformation message or a new RRC message).

[0112] In some implementations, UL data and / or DL ​​data are associated with a radio bearer (e.g., SRB and / or DRB). For example, UL data may include an RRC message or a NAS message associated with an SRB. In another example, UL data includes an IP packet associated with a DRB. In some implementations, UE 102 may include the ID of the radio bearer in a non-SDT indication message. Therefore, CU-CP 172A may determine whether to transition 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, CU-CP 172A may determine to transition UE 102 to a connected state. Otherwise, CU-CP 172A may determine not to transition UE 102 to a connected state. In some implementations, UE 102 may include data volume information of UL data in a non-SDT indication message. Therefore, CU-CP 172A may determine whether to transition 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 of the radio bearers, 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.

[0113] In response to determining to transition UE 102 to a connected state, or after determining to transition UE 102 to a connected state, 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 DU 174. In response, 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 CU-CP 172A. In some implementations, 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, 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 DU 174. Then, DU 174 sends 512 an RRC resume message to UE 102. In some implementations, DU 174 may send 512 one or more PDUs including an RRC recovery message to 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 the RRC recovery 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 recovery message. DU 174 sends 516 a DU to CU message including an RRC recovery completion message to CU-CP 172A. After determining to transition UE 102 to the connected state, 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 CU-UP 172B to instruct CU-UP 172B to resume all suspended radio bearers for UE 102. In response, CU-UP 172B resumes all suspended radio bearers for 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 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.

[0114] In some implementations, the CU-CP 172A may include an indication indicating that the DU 174 generates a non-SDT configuration in a UE context request message, and the DU 174 includes the first non-SDT DU configuration in a UE context response message in response to the indication. In other implementations, the CU-CP 172A stores a non-SDT DU configuration (i.e., a second non-SDT DU configuration) used by the DU (e.g., DU 174 or another DU or base station) to communicate with the UE 102. The UE 102 may also store a second non-SDT DU configuration. In such cases, the CU-CP 172A includes the second non-SDT DU configuration in the UE context request message, and the DU 174 may include the first non-SDT DU configuration in the 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 with respect to 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.

[0115] 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 a 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-SDT DU 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 augmented by the first non-SDT DU configuration.

[0116] 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.

[0117] 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 transitioning the UE 102 to a connected state, receiving 510 to a CU to DU message, or sending 510, 512 an RRC recovery message, 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 receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for the PDU including an RRC recovery message, or after receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for the PDU including an RRC recovery message. In yet 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 the UE context request message or communicating 508 the UE context response message.

[0118] In other implementations, the UE 102 retains the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration) in response to receiving an RRC recovery message or transitioning to a connected state, or after receiving an RRC recovery message or transitioning to a connected state. 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, the base station 104 retains the SDT configuration in response to transitioning the UE 102 to a connected state or sending an RRC recovery message, or after transitioning the UE 102 to a connected state or sending an RRC recovery message. In some implementations, the base station 104 avoids using the SDT configuration to communicate with the UE 102 operating in the 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., receiving 514 an RRC recovery complete message and / or communicating 518 data).

[0119] At a later time, the base station 104 may perform a non-SDT configuration procedure 590 and an SDT configuration procedure 594 with the UE 102, similar to the procedures 390 and 394, respectively. The UE 102 transitions 536 to an inactive state in response to receiving the RRC release message in the procedure 594. The base station 104 may then perform a small data transfer procedure 593 and an SDT completion procedure 595 with the UE 102, similar to the procedures 492 and 494, respectively.

[0120] 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.

[0121] 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 a connected state. In response to determining to transition the UE 102 to a connected state, or after determining to transition the UE 102 to a connected state, the CU-CP 172A transitions the UE 102 to a connected state, as described for scenario 500A.

[0122] 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 for the SDT in the CG configuration. In other implementations, the UE 102 may perform a random access procedure to send the UL MAC PDU, similar to event 404.

[0123] Next, several example methods that may be implemented in one or more base stations, DUs or CUs, or more generally in a RAN to support data communications in an inactive state are discussed with reference to FIGS. 6A to 11 .

[0124] FIG. 6A illustrates a method 600A that may be implemented by a base station (eg, base station 104) for managing uplink synchronization of a UE (eg, UE 102).

[0125] Method 600A begins at block 602, where a base station sends a timing advance command to a UE. At block 604, the base station starts or restarts an uplink synchronization (time alignment) timer in response to sending the timing advance command. In some implementations, while the uplink synchronization timer is running, the base station determines that the timing advance command is valid, the uplink transmission timing of the UE is valid, or the UE is synchronized with the base station in uplink transmissions. In the case where the base station determines or detects that the uplink synchronization timer expires, the base station may determine that the timing advance command is invalid, the uplink transmission timing of the UE is invalid, or the UE is not synchronized with the base station in uplink transmissions.

[0126] At box 606, the base station sends a first message to the UE to configure CG-SDT and transition the UE to an inactive state (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595). At box 608, the base station stops the uplink synchronization timer in response to transitioning the UE to an inactive state. At box 610, the base station starts or restarts the CG-SDT timer (e.g., the DU CG-SDT timer described above) in response to sending the first message or configuring CG-SDT. In some implementations, while the CG-SDT timer is running, the base station determines that the timing advance command is valid, the UE's uplink transmission timing is valid, the UE is synchronized with the base station in uplink transmission, and / or the UE is configured with CG-SDT (i.e., the UE is configured with a CG-SDT configuration). In a case where the base station determines or detects that the CG-SDT timer has expired, the base station may determine that the timing advance command is invalid, the UE's uplink transmission timing is invalid, the UE is not synchronized with the base station in the uplink transmission, and / or the CG-SDT or CG-SDT configuration is invalid.

[0127] At box 612 (optional), the base station may communicate data with the UE operating in the inactive state (e.g., events 404, 406, 415, 416, 418, 492, 592). At box 614, the base station sends a second message to the UE to transition the UE from the inactive state to the connected state (e.g., events 510, 512). At box 616, the base station starts an uplink synchronization timer in response to sending the second message to the UE or sending a PDU including the second message, or after sending the second message to the UE or sending a PDU including the second message. At box 618, the base station communicates data with the UE operating in the connected state (e.g., events 514, 516, 518). Depending on whether the base station sends a (new) timing advance command to the UE, the process can proceed to box 602 or 606.

[0128] In some implementations, the base station sends a timing advance command (i.e., a first timing advance command) to a UE operating in a connected state at block 602. For example, the base station sends a MAC PDU including a first timing advance command to a UE operating in a connected state. The MAC PDU may include a MAC SDU, the MAC SDU including a data packet or a portion of a data packet. In another example, the base station receives a random access preamble from a UE operating in a connected state and sends a random access response including a first timing advance command to the UE operating in a connected state. In yet another example, the base station receives a message A (MsgA) from a UE operating in a connected state and sends a message B (MsgB) including a first timing advance command to the UE operating in a connected state.

[0129] In some implementations, the base station sends a timing advance command (i.e., a first timing advance command) to a UE operating in an inactive state at block 602. For example, the base station sends a MAC PDU including a first timing advance command to a UE operating in an inactive state during an SDT session. The MAC PDU may include a MAC SDU, the MAC SDU including a data packet or a portion of a data packet. In another example, the base station receives a random access preamble from a UE operating in an inactive state and sends a random access response including a first timing advance command to the UE operating in an inactive state. In yet another example, the base station receives a message A (MsgA) from a UE operating in an inactive state and sends a message B (MsgB) including a first timing advance command to the UE operating in an inactive state.

[0130] In some implementations, the base station sends a timing advance command (i.e., a first timing advance command) to a UE operating in an idle state at block 602. For example, the base station may receive a random access preamble from the UE operating in the idle state and send a random access response including the first timing advance command to the UE operating in the idle state. In yet another example, the base station may receive a message A (MsgA) from the UE operating in the idle state and send a message B (MsgB) including the first timing advance command to the UE operating in the idle state.

[0131] In some implementations, the base station may include a CG-SDT configuration that configures the CG-SDT in the first message. In other implementations, the base station may send another message including the CG-SDT configuration to the UE before sending the first message (e.g., events 332, 334). In such implementations, the base station may not include the CG-SDT configuration in the first message, and may configure the UE to continue using the CG-SDT configuration previously received by the UE (e.g., events 432, 434).

[0132] In some implementations, the PDU is a MAC PDU. In some implementations, the MAC PDU may include a timing advance command to update the uplink transmit timing of the UE and cause the UE to start or restart a time alignment timer for managing uplink synchronization with the base station. In other implementations, the MAC PDU does not include a timing advance command.

[0133] In some implementations, the base station may send a timing advance command to the UE during communication with the UE at block 612. In such implementations, the base station may start or restart the CG-SDT timer.

[0134] In some implementations, the base station starts the uplink synchronization timer at block 616 with a timer value. In some implementations, the timer value may be based on (e.g., the same as or close to) the remaining time of the CG-SDT timer. In other implementations, the timer value may be based on (e.g., the same as or close to) a TimeAlignmentTimer or timeAlignmentTimerCommon in a system information block (SIB) broadcast by the base station. In other implementations, the timer value may be the same as or close to the TimeAlignmentTimer or timeAlignmentTimerCommon in the second message.

[0135] In some implementations, the base station restarts the uplink synchronization timer in response to sending the second timing advance command to the UE operating in the connected state.For example, the base station may send a MAC PDU including the second timing advance command to the UE operating in the connected state.

[0136] 6B is a flow chart of an example method 600B similar to method 600A, except that method 600B includes block 609 instead of blocks 608 and 616. At block 609, the base station avoids stopping the uplink synchronization timer in response to transitioning the UE to an inactive state. That is, the base station may maintain or keep the uplink synchronization timer running in response to transitioning the UE to an inactive state, or after transitioning the UE to an inactive state. In some implementations, the base station may send a timing advance command to the UE during communication with the UE at block 612. In such implementations, the base station may start or restart the uplink synchronization timer.

[0137] 6C is a flow chart of an example method 600C similar to method 600B, except that method 600C includes block 611 instead of block 610. At block 611, the base station restarts the uplink synchronization timer in response to sending the first message or configuring the CG-SDT, rather than starting or restarting the CG-SDT timer. That is, the base station uses the uplink synchronization timer to manage uplink synchronization of UEs operating in different states (e.g., connected state and inactive state), rather than using different uplink synchronization timers for different states.

[0138] FIG. 7A illustrates a method 700A that may be implemented by a base station (eg, base station 104) for managing uplink synchronization of a UE (eg, UE 102).

[0139] Method 700A begins at box 702, where the base station sends a timing advance command to the UE. At box 704, the base station determines whether the CG-SDT timer is running. If the base station determines that the CG-SDT timer is running, the process proceeds to box 706. At box 706, the base station restarts the CG-SDT timer in response to sending the timing advance command. Otherwise, if the base station determines that the CG-SDT timer is not running, the process proceeds to box 708. At box 708, the base station starts or restarts the uplink synchronization timer in response to sending the timing advance command. In some implementations, the base station starts a CG-SDT timer (e.g., a DUCG-SDT timer), as described above.

[0140] 7B is a flow chart of an example method 700B similar to method 700A, except that in method 700B, the base station starts or restarts the uplink synchronization timer in response to sending the timing advance command at block 708, regardless of whether the CG-SDT timer is running at the base station. If the base station determines that the CG-SDT timer is not running, the process proceeds to block 710, where the process ends.

[0141] The examples and implementations described above for method 600A may be applicable to methods 700A and 700B.

[0142] FIG. 8A illustrates a method 800A that may be implemented by a base station (eg, base station 104) for managing uplink synchronization of a UE (eg, UE 102).

[0143] Method 800A begins at box 802, where the base station sends a timing advance command to the UE. At box 804, the base station starts an uplink synchronization timer in response to sending the timing advance command. At box 806, the base station sends a first message to the UE that transitions the UE to an inactive state (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595). At box 808, the base station determines whether the first message configures the CG-SDT of the UE. If the base station determines that the first message configures the CG-SDT of the UE, the process proceeds to box 810. At box 810, the base station avoids stopping the uplink synchronization timer (i.e., continues to run the uplink synchronization timer). At box 812 (optional), the base station may proceed to boxes 610, 612, 614, and / or 616. Otherwise, if the base station determines that the first message does not configure the CG-SDT of the UE, the process proceeds to box 814. At block 814, the base station stops the uplink synchronization timer.

[0144] In some implementations, the base station resets a MAC entity that the base station uses to communicate with the UE, for example, by sending a timing advance command and / or a first message to the UE. In some implementations, when the base station resets the MAC entity, the base station sets a new data indicator (NDI) of the uplink HARQ process of the MAC entity to a default value (e.g., zero), refreshes the soft buffer for the uplink HARQ process of the MAC entity, and / or treats the next transmission of a transport block as a new transmission for each of the downlink HARQ processes of the MAC entity. The base station uses an uplink HARQ process to receive data from the UE before sending the first message to the UE (e.g., events 404, 418, 492, 514, 518, 592, 593). The base station uses a downlink HARQ process to send data and / or a first message to the UE (e.g., events 418 518, 592, 593). In a case where the first message configures the CG-SDT configuration, the base station avoids stopping the uplink synchronization timer (i.e., continues to run the uplink synchronization timer) when resetting the MAC entity, in response to resetting the MAC entity, or after resetting the MAC entity.

[0145] 8B is a flow chart of an example method 800B similar to method 800A, except that method 800B includes blocks 811 and 815 instead of blocks 810 and 814. At block 811, the base station resets the MAC entity and avoids stopping the uplink synchronization timer when resetting the MAC entity (i.e., continues to run the uplink synchronization timer). At block 815, the base station resets the MAC entity instead of starting the uplink synchronization timer. When the base station resets the MAC entity, the base station stops the uplink synchronization timer.

[0146] The examples and implementations described above for method 600A may be applicable to methods 800A and 800B.

[0147] FIG. 9A illustrates a method 900A that may be implemented by a DU (eg, DU 174) for managing uplink synchronization of a UE (eg, UE 102).

[0148] The method 900A begins at block 902, where the DU sends a timing advance command to the UE. At block 904, the DU starts or restarts an uplink synchronization timer in response to sending the timing advance command. While the uplink synchronization timer is running, the DU determines that the timing advance command is valid, the uplink transmission timing of the UE is valid, or the UE is synchronized with the DU in uplink transmissions. In the case where the DU determines or detects that the uplink synchronization timer expires, the DU determines that the timing advance command is invalid, the uplink transmission timing of the UE is invalid, or the UE is not synchronized with the DU in uplink transmissions.

[0149] At box 906, the DU receives a first CU-to-DU message (e.g., events 328, 332, 428, 432, 394, 494, 495, 594, 595) from the CU for configuring the CG-SDT of the UE. In some implementations, the DU may send a first DU-to-CU message (e.g., events 330, 430, 394, 494, 495, 594, 595) to the CU in response to the first CU-to-DU message. In the case where the first CU-to-DU message is a UE context release command message, the first DU-to-CU message may be a UE context release complete message. At box 908, the DU stops the uplink synchronization timer in response to the first CU-to-DU message. At box 910, the DU starts or restarts the CG-SDT timer in response to configuring the CG-SDT. While the CG-SDT timer is running, the DU determines that the timing advance command is valid, the uplink transmission timing of the UE is valid, the UE is synchronized with the DU in the uplink transmission, and / or the UE is configured with CG-SDT (i.e., the UE is configured with a CG-SDT configuration). In the case where the DU determines or detects that the uplink synchronization timer expires, the DU determines that the timing advance command is invalid, the uplink transmission timing of the UE is invalid, the UE is not synchronized with the DU in the uplink transmission, and / or the CG-SDT or CG-SDT configuration is invalid.

[0150] At block 912 (optional), the DU may communicate data with a UE operating in an inactive state (e.g., events 404, 418, 492, 592). At block 914, the DU receives a second CU-to-DU message from the CU for transitioning the UE to a connected state (e.g., event 510). At block 916, the DU starts an uplink synchronization timer in response to the second CU-to-DU message. At block 918, the DU communicates data with a UE operating in a connected state (e.g., events 514, 518). Then, depending on whether the base station sends a (new) timing advance command to the UE, the flow may proceed to block 902 or 906.

[0151] 9B is a flow chart of an example method 900B similar to method 900A, except that method 900B includes block 909 instead of blocks 908 and 916. At block 909, the DU avoids stopping the uplink synchronization timer in response to the first CU-to-DU message. That is, when the UE transitions to the inactive state, or after the UE transitions to the inactive state, the DU may maintain or keep the uplink synchronization timer running.

[0152] 9C is a flow chart of an example method 900C similar to method 900B, except that method 900C includes block 911 instead of block 910. At block 911, the DU restarts the uplink synchronization timer in response to configuring the CG-SDT, instead of starting or restarting the CG-SDT timer. That is, the base station uses the uplink synchronization timer to manage uplink synchronization of UEs operating in different states (e.g., connected state and inactive state).

[0153] The examples and implementations described above for method 600A may be applicable to methods 900A, 900B, and 900C.

[0154] FIG. 10A illustrates a method 1000A that may be implemented by a DU (eg, DU 174) for managing uplink synchronization of a UE (eg, UE 102).

[0155] Method 1000A begins at block 1002, where the DU sends a timing advance command to the UE. At block 1004, the DU starts an uplink synchronization timer in response to sending the timing advance command. At block 1006, the DU receives a UE context release command message for the UE from the CU (see, e.g., events 332, 432, 394, 494, 594, 595). At block 1008, the DU determines whether the UE context release command message indicates to retain (part of) the UE context. If the DU determines that the UE context release command message indicates to retain (part of) the UE context, the process proceeds to block 1010. At block 1010, the DU avoids stopping the uplink synchronization timer (i.e., continues to run the uplink synchronization timer). At block 1012 (optional), the DU may proceed to blocks 910, 912, 914, and / or 916. Otherwise, if the DU determines that the UE context release command message does not indicate to retain (part of) the UE context, the process proceeds to block 1014. At block 1014, the DU stops the uplink synchronization timer.

[0156] In some implementations, the DU resets a MAC entity that the DU uses to communicate with the UE, for example by sending a timing advance command to the UE. In the case where the UE context release command message indicates to retain part of the UE context, the DU avoids stopping the uplink synchronization timer in response to resetting the MAC entity or after resetting the MAC entity.

[0157] 10B is a flow chart of an example method 1000B similar to method 1000A, except that method 1000B includes blocks 1011 and 1015 instead of blocks 1010 and 1014. At block 1011, the DU resets the MAC entity and avoids stopping the uplink synchronization timer when resetting the MAC entity (i.e., continues to run the uplink synchronization timer). At block 1015, the DU resets the MAC entity instead of stopping the uplink synchronization timer.

[0158] The examples and implementations described above for method 600A may be applicable to methods 1000A and 1000B.

[0159] 11 illustrates a method 1100 that may be implemented by a RAN node (eg, base station 104 or DU 174) for managing uplink synchronization of a UE (eg, UE 102).

[0160] The method 1100 begins at block 1102, where the RAN node starts or restarts an uplink synchronization timer for the UE, e.g., as described above. At block 1104, the RAN node starts or restarts a CG-SDT timer (e.g., a DU CG-SDT timer) for the UE, e.g., as described above. At block 1106, the RAN node determines or detects that the uplink synchronization timer expires. At block 1108, the RAN node determines whether the CG-SDT timer is running. If the RAN node determines that the CG-SDT timer is running, the flow proceeds to block 1110. At block 1110, the RAN node performs an uplink synchronization timer expiration procedure in response to the expiration of the uplink time synchronization timer. Otherwise, if the RAN node determines that the CG-SDT is not running (e.g., stopped or expired), the flow proceeds to block 1112. At block 1112, the RAN node avoids performing the uplink synchronization timer expiration procedure.

[0161] In some implementations, the uplink synchronization timer expiration procedure includes at least one of the following actions:

[0162] · Flushing one or more HARQ buffers of the MAC entity

[0163] Release PUCCH resources and / or configuration

[0164] Release Sounding Reference Signal (SRS) resources and / or configuration

[0165] Clear any configured downlink assignments and / or configured uplink grants

[0166] The following list of examples reflects the various implementations expressly contemplated by this disclosure:

[0167] Example 1. A method for managing time alignment performed by a radio access network (RAN) node, the method comprising: sending a timing advance command to a user equipment (UE); starting or restarting a first time alignment timer indicating the validity of a configuration grant (CG) configuration when the UE is in a radio resource control (RRC) connected state; after starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to an RRC inactive state; and in response to the determination, (i) transitioning the UE from the RRC connected state to the inactive state by sending a first message to the UE, (ii) stopping the first time alignment timer, and (iii) starting or restarting a second time alignment timer indicating the validity of a CG small data transfer (CG-SDT) configuration when the UE is in the RRC inactive state.

[0168] Example 2. The method as described in Example 1 further includes, after stopping the first time alignment timer and starting or restarting the second time alignment timer: transitioning the UE from the inactive state to the RRC connected state by sending a second message to the UE; and after sending the second message, (i) starting the first time alignment timer again, and (ii) communicating data with the UE operating in the RRC connected state.

[0169] Example 3. The method of Example 2, wherein the node is a distributed unit (DU) of a distributed base station including a central unit (CU).

[0170] Example 4. The method as described in Example 3 further includes: receiving a first CU to DU message from the CU for configuring the CG-SDT of the UE; and receiving a second CU to DU message from the CU for transitioning the UE to the connected state, wherein stopping the first time alignment timer is in response to the first CU to DU message, and wherein restarting the first time alignment timer is in response to the second CU to DU message.

[0171] Example 5. The method of Example 4, wherein the first CU-to-DU message is a UE context release command message, and wherein the second CU-to-DU message is an RRC resume message or an RRC connection resume message.

[0172] Example 6. The method of Example 2, wherein restarting the first time alignment timer comprises setting a timer value of the first time alignment timer based on a remaining time of the second time alignment timer.

[0173] Example 7. The method of Example 2, wherein restarting the first time alignment timer comprises setting a timer value of the first time alignment timer based on a parameter broadcast by the RAN.

[0174] Example 8. The method of any one of Examples 1 to 7, wherein sending the timing advance command occurs when the UE is in the RRC connected state.

[0175] Example 9. A method as described in any one of Examples 1 to 7, wherein sending the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before determining to transition the UE from the RRC connected state to the RRC inactive state, transitioning the UE from the RRC inactive state to the RRC connected state.

[0176] Example 10. The method of any one of Examples 1 to 9, wherein the first message includes the CG-SDT configuration.

[0177] Example 11. A method as described in any one of Examples 1 to 10, wherein the first message is an RRC release message.

[0178] Example 12. The method of any one of Examples 1 to 11, wherein sending the timing advance command comprises sending a medium access control (MAC) protocol data unit (PDU) including the timing advance command.

[0179] Example 13. The method of any one of Examples 1 to 11, wherein sending the timing advance command comprises sending a random access channel message including the timing advance command.

[0180] Example 14. The method of any one of Examples 1 to 13, further comprising: determining that the second time alignment timer is not running, wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.

[0181] Example 15. The method as described in any one of Examples 1 to 13 further includes, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.

[0182] Example 16. The method as described in any one of Examples 1 to 13 further includes, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; starting or restarting the first time alignment timer again; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.

[0183] Example 17. A method for managing time alignment performed by a radio access network (RAN) node, the method comprising: sending a timing advance command to a user equipment (UE); starting or restarting a first time alignment timer indicating the validity of a configuration grant (CG) configuration when the UE is in a radio resource control (RRC) connected state; after starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to an RRC inactive state; and in response to the determination, (i) transitioning the UE from the connected state to the RRC inactive state by sending a first message to the UE, and (ii) starting or restarting a second time alignment timer indicating the validity of a CG small data transfer (CG-SDT) configuration when the UE is in the RRC inactive state while continuing to run the first time alignment timer.

[0184] Example 18. The method as described in Example 17 further includes, after starting or restarting the second time alignment timer: transitioning the UE from the inactive state to the RRC connected state by sending a second message to the UE; and after sending the second message, communicating data with the UE operating in the RRC connected state.

[0185] Example 19. The method of Example 18, wherein the node is a distributed unit (DU) of a distributed base station including a central unit (CU).

[0186] Example 20. The method as described in Example 19 further includes: receiving a first CU to DU message from the CU for configuring the CG-SDT of the UE; and receiving a second CU to DU message from the CU for transitioning the UE to the RRC connected state, wherein transitioning the UE from the RRC connected state to the RRC inactive state and starting or restarting the second time alignment timer while continuing to run the first time alignment timer occur after receiving the first CU to DU message, and wherein transitioning the UE from the RRC inactive state to the RRC connected state occurs after receiving the second CU to DU message.

[0187] Example 21. The method of Example 20, wherein the first CU-to-DU message is a UE context release command message, and wherein the second CU-to-DU message is an RRC resume message or an RRC connection resume message.

[0188] Example 22. The method as described in Example 19 further includes, after starting or restarting the first time alignment timer: receiving a CU to DU message from the CU; and determining that the CU to DU message indicates that a portion of the UE context is to be retained, wherein continuing to run the first time alignment timer is in response to determining that the CU to DU message indicates that the portion of the UE context is to be retained.

[0189] Example 23. The method of Example 22, wherein the CU to DU message is a UE context release command message.

[0190] Example 24. The method of Example 22 or 23, wherein continuing to run the first time alignment timer includes avoiding stopping the first time alignment timer when a medium access control (MAC) entity is reset at the DU.

[0191] Example 25. The method of any one of Examples 17 to 24, wherein sending the timing advance command occurs when the UE is in the RRC connected state.

[0192] Example 26. A method as described in any one of Examples 17 to 24, wherein sending the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before the determining, transitioning the UE from the RRC inactive state to the RRC connected state.

[0193] Example 27. A method as described in any one of Examples 17 to 26, wherein the first message includes the CG-SDT configuration.

[0194] Example 28. The method of Example 27, wherein continuing to run the first time alignment timer is based on the first message including the CG-SDT configuration.

[0195] Example 29. The method of Example 27 or 28, wherein continuing to run the first time alignment timer comprises avoiding stopping the first time alignment timer when a media access control (MAC) entity is reset at the node.

[0196] Example 30. A method as described in any one of Examples 17 to 29, wherein the first message is an RRC release message.

[0197] Example 31. The method of any one of Examples 17 to 30, wherein sending the timing advance command comprises sending a medium access control (MAC) protocol data unit (PDU) including the timing advance command.

[0198] Example 32. The method of any one of Examples 17 to 30, wherein sending the timing advance command comprises sending a random access channel message including the timing advance command.

[0199] Example 33. The method of any one of Examples 17 to 32, further comprising: determining that the second time alignment timer is not running, wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.

[0200] Example 34. A method as described in any one of Examples 17 to 32, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.

[0201] Example 35. A method as described in any one of Examples 17 to 32, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; starting or restarting the first time alignment timer again; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.

[0202] Example 36. A method for managing time alignment with a user equipment (UE) performed by a node of a radio access network (RAN), the method comprising: sending a timing advance command to the UE; starting or restarting a time alignment timer indicating the validity of a configured grant (CG) configuration to be used when the UE is in a radio resource control (RRC) connected state; after starting or restarting the time alignment timer, determining to transition the UE from the RRC connected state to an RRC inactive state; and in response to the determination, (i) transitioning the UE from the RRC connected state to the RRC inactive state by sending a first message to the UE, and (ii) restarting the time alignment timer to indicate the validity of a CG small data transfer (CG-SDT) configuration to be used when the UE is in the RRC inactive state.

[0203] Example 37. The method as described in Example 36 further includes, after restarting the time alignment timer: transitioning the UE from the RRC inactive state to the RRC connected state by sending a second message to the UE; and after sending the second message, communicating data with the UE operating in the RRC connected state.

[0204] Example 38. The method of Example 37, wherein the node is a distributed unit (DU) of a distributed base station including a central unit (CU).

[0205] Example 39. The method as described in Example 38 further includes: receiving a first CU to DU message from the CU for configuring the CG-SDT of the UE; and receiving a second CU to DU message from the CU for transitioning the UE to the RRC connected state, wherein transitioning the UE from the RRC connected state to the RRC inactive state and restarting the time alignment timer occur after receiving the first CU to DU message, and wherein transitioning the UE from the RRC inactive state to the RRC connected state occurs after receiving the second CU to DU message.

[0206] Example 40. The method of Example 39, wherein the first CU-to-DU message is a UE context release command message, and wherein the second CU-to-DU message is an RRC resume message or an RRC connection resume message.

[0207] Example 41. A method as described in any of Examples 36 to 40, wherein sending the timing advance command occurs when the UE is in the RRC connected state.

[0208] Example 42. A method as described in any one of Examples 36 to 40, wherein sending the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before the determining, transitioning the UE from the RRC inactive state to the RRC connected state.

[0209] Example 43. A method as described in any one of Examples 36 to 42, wherein the first message includes the CG-SDT configuration.

[0210] Example 44. A method as described in any of Examples 36 to 43, wherein the first message is an RRC release message.

[0211] Example 45. The method of any one of Examples 36 to 44, wherein sending the timing advance command comprises sending a medium access control (MAC) protocol data unit (PDU) including the timing advance command.

[0212] Example 46. The method of any one of Examples 36 to 44, wherein sending the timing advance command comprises sending a random access channel message including the timing advance command.

[0213] Example 47. A node of a radio access network (RAN), the node comprising one or more processors and configured to perform a method as described in any one of Examples 1 to 46.

[0214] The following description may be applicable to the above description.

[0215] In some implementations, "message" is used and "information element (IE)" may be substituted for "message" and vice versa. In some implementations, "IE" is used and "field" may be substituted for "IE" and vice versa. In some implementations, "configuration" or "configuration parameter" may be substituted for "configuration" and vice versa. In some implementations, "early data transfer (EDT)" may be substituted for "small data transfer" and "EDT" may be substituted for "SDT" and vice versa. In some implementations, "small data communication" may be substituted for "small data transfer" and vice versa. In some implementations, "pause" may be substituted for "stop".

[0216] 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 smart phone, 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. In addition, 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 be operated 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.

[0217] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code or machine-readable instruction stored on a non-temporary machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module may include a dedicated circuit system or logic that is 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 may also include a programmable logic or circuit system (e.g., contained in a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0218] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, 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 time alignment performed by a distributed unit (DU) of a distributed base station comprising a distributed unit (DU) and a central unit (CU), the method comprising: Sending a timing advance command to a user equipment (UE); starting or re-starting a first time alignment timer indicating validity of a configuration grant (CG) configured when the UE is in a radio resource control (RRC) connected state with a radio access network (RAN) including the distributed base station; After starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to an RRC inactive state; as well as In response to the determination, (i) the UE is transitioned from the RRC connected state to the inactive state by sending a first message to the UE, (ii) the first time alignment timer is stopped, and (iii) a second time alignment timer indicating the validity of a CG small data transfer (CG-SDT) configuration when the UE is in the RRC inactive state is started or restarted.

2. The method of claim 1 , further comprising, after stopping the first time alignment timer and starting or restarting the second time alignment timer: transitioning the UE from the inactive state to the RRC connected state by sending a second message to the UE; and After sending the second message, (i) the first time alignment timer is restarted, and (ii) data is communicated with the UE operating in the RRC connected state.

3. The method according to claim 1 or 2, further comprising: receiving, from the CU, a first CU-to-DU message for configuring a CG-SDT of the UE; as well as receiving from the CU a second CU-to-DU message for transitioning the UE to the connected state, wherein stopping the first time alignment timer is in response to the first CU to DU message, and Wherein restarting the first time alignment timer is in response to the second CU to DU message.

4. The method of claim 3, wherein the first CU-to-DU message is a UE context release command message, and wherein the second CU-to-DU message is an RRC resume message or an RRC connection resume message.

5. The method of claim 2, wherein restarting the first time alignment timer comprises setting a timer value of the first time alignment timer based on: (i) a remaining time of the second time alignment timer, or (ii) a parameter broadcast by the RAN.

6. The method according to any one of claims 1 to 5, further comprising: determining that the second time alignment timer is not running, Wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.

7. The method according to any one of claims 1 to 5, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; determining that the second time alignment timer is running; and In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.

8. The method according to any one of claims 1 to 5, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; Restarting or re-starting the first time alignment timer; determining that the second time alignment timer is running; and In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.

9. A method for managing time alignment performed by a distributed unit (DU) of a distributed base station comprising a distributed unit (DU) and a central unit (CU), the method comprising: Sending a timing advance command to a user equipment (UE); starting or re-starting a first time alignment timer indicating validity of a configuration grant (CG) configured when the UE is in a radio resource control (RRC) connected state with a radio access network (RAN) including the distributed base station; After starting or restarting the first time alignment timer, determining to transition the UE from the RRC connected state to an RRC inactive state; as well as In response to the determination, (i) the UE is transitioned from the connected state to the RRC inactive state by sending a first message to the UE, and (ii) a second time alignment timer is started or restarted while continuing to run the first time alignment timer to indicate the validity of a CG small data transfer (CG-SDT) configuration when the UE is in the RRC inactive state.

10. The method of claim 9, further comprising: After starting or restarting the second time alignment timer, (i) transitioning the UE from the inactive state to the RRC connected state by sending a second message to the UE; and (ii) after sending the second message, communicating data with the UE operating in the RRC connected state; receiving, from the CU, a first CU-to-DU message for configuring a CG-SDT of the UE; as well as receiving from the CU a second CU-to-DU message for transitioning the UE to the RRC connected state, wherein transitioning the UE from the RRC connected state to the RRC inactive state and starting or restarting the second time alignment timer while continuing to run the first time alignment timer occurs after receiving the first CU to DU message, and Wherein transitioning the UE from the RRC inactive state to the RRC connected state occurs after receiving the second CU-to-DU message.

11. The method of claim 10, further comprising, after starting or restarting the first time alignment timer: receiving a CU-to-DU message from the CU; and determining that the CU to DU message indicates that part of the UE context is to be retained, The continuing to run the first time alignment timer is in response to determining that the CU-to-DU message indicates that the portion of the UE context is to be retained.

12. The method according to any one of claims 9 to 11, further comprising: determining that the second time alignment timer is not running, Wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.

13. The method according to any one of claims 9 to 11, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; determining that the second time alignment timer is running; and In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.

14. The method according to any one of claims 9 to 11, further comprising, after starting or restarting the second time alignment timer: sending an additional timing advance command to the UE; Restarting or re-starting the first time alignment timer; determining that the second time alignment timer is running; and In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.

15. A distributed unit (DU) of a distributed base station, the DU comprising one or more processors and configured to execute the method according to any one of claims 1 to 14.