Managing configuration authorization configuration for user equipment
By collaboratively managing the CG-SDT configuration and time alignment timer between the CU and DU of the distributed base station, the problems of data communication delay and network inefficiency of the UE in the inactive state are solved, and efficient data communication is achieved manage.
Patent Information
- Application Number
- CN202380030652.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-11-10
- Filing Date
- 2023-02-09
- Publication Date
- 2024-11-08
AI Technical Summary
Prior art is used to manage uplink and downlink data communication between user equipment (UE) and radio access network (RAN), especially in CG-SDT configuration management when the UE is inactive or idle state. , there are problems of data communication delay and network inefficiency.
Detect and manage the expiration of the timer by co-managing between the central unit (CU) and the distributed unit (DU) of the distributed base station, transmitting the CG-SDT configuration to the UE and starting or restarting the time alignment timer. to ensure effective data communication and resource configuration.
Effectively manage the synchronization status of the UE, reduce data communication delay, improve network efficiency, and ensure that data communication can be processed efficiently in an inactive state.
Smart Images

Figure CN118923168A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, and more particularly to communication of uplink and / or downlink data between a user equipment (UE) and a radio access network (RAN) when the UE is operating in an inactive or idle state associated with a protocol for controlling radio resources. Background Art
[0002] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors (to the extent that it is described in this background section) and aspects of the specification that may not have been counted as prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0003] In general, a base station operating a cellular radio access network (RAN) uses a specific radio access technology (RAT) and multiple layers of a protocol stack to communicate with a user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the medium access control (MAC) sublayer, which in turn provides a logical channel to the radio link control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.
[0004] The RRC sublayer defines: an RRC_IDLE state, in which the UE does not have an active radio connection with a base station; an RRC_CONNECTED state, in which the UE has an active radio connection with a base station; and an RRC_INACTIVE state, which allows the UE to transition back to the RRC_CONNECTED state more quickly using RAN-level base station coordination and RAN paging procedures. In some cases, a UE in the RRC_INACTIVE state has only one relatively small packet to transmit. For situations such as these, 3GPP is discussing a small data transmission (SDT) procedure to enable 5G NR (New Radio), a wireless communication standard, to support data transmission for UEs operating in the RRC_INACTIVE state (i.e., without requiring the UE to transition to the RRC_CONNECTED state).
[0005] SDT is enabled on a radio bearer basis and is initiated by the UE only when: (1) the amount of uplink data to be transmitted (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 type 1 configuration 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 (random access-based SDT), the UE can transmit an initial transmission including data in message 3 (Msg3) of a 4-step random access procedure or in the payload of message A (MsgA) of a 2-step random access procedure. After completing the random access procedure, the network can then schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.
[0006] CG-SDT (SDT based on configuration grant) can only be initiated if there is 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). When the SDT-specific timing alignment timer expires, the CG resources are released. When CG-SDT is initiated, the UE uses the CG configuration to transmit 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 unclear how the RAN's base station manages UL synchronization for CG-SDT. Failure to properly manage UL synchronization may result in data communication delays and / or other network inefficiencies. In addition, it is unclear how the base station manages the CG-SDT configuration. Failure to properly manage the CG-SDT configuration may likewise result in various network inefficiencies. Summary of the invention
[0008] In some implementations of the present disclosure, the base station maintains a CG-SDT time alignment timer indicating the validity of the CG-SDT configuration for the UE. The base station sends an RRC release message including the CG-SDT configuration to the UE, and then starts or restarts the time alignment timer. After subsequently receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration, the base station may detect that the time alignment timer has expired (and thus releases the CG-SDT configuration), or transmits a timing advance command to the UE (and thus restarts the time alignment timer).
[0009] In some implementations where the base station is a distributed base station, a distributed unit (DU) of the base station maintains a time alignment timer for CG-SDT operation. For example, the DU may transmit a CG-SDT configuration to the UE via a central unit (CU) of the distributed base station (e.g., by sending the CG-SDT configuration to the CU, receiving an RRC release message including the CG-SDT configuration from the CU in response, and then sending an RRC release message with the CG-SDT configuration to the UE), and then start or restart the time alignment timer. After subsequently receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration, the DU may detect that the time alignment timer has expired (and therefore stop attempting to receive the UE transmission), or transmit a timing advance command to the UE (and therefore restart the time alignment timer). In other distributed base station implementations, the CU, rather than the DU, maintains a time alignment timer for CG-SDT operation.
[0010] In some implementations, the CU of the distributed base station determines whether / when to release the CG-SDT configuration, and may transmit a CU-to-DU message to the DU indicating that the DU is to release the CG-SDT configuration. However, in other implementations, the DU determines whether / when to release the CG-SDT configuration, and may notify the CU that the CG-SDT configuration is to be released, or send a request to the CU to release the CG-SDT configuration.
[0011] In one aspect of the present disclosure, a method for managing synchronization with a UE implemented by a DU of a distributed base station includes: transmitting a CG-SDT configuration for use by the UE when the UE is in an inactive state to the UE via a CU of the distributed base station. The method also includes: after transmitting the CG-SDT configuration to the UE via the CU, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; and receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration while the time alignment timer is running.
[0012] In another aspect of the present disclosure, a method for managing synchronization with a UE implemented by a base station includes: transmitting an RRC release message to the UE including a CG-SDT configuration for use by the UE when the UE is in an inactive state. The method also includes: after transmitting the RRC release message to the UE, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; and receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration while the time alignment timer is running.
[0013] In another aspect of the present disclosure, a method for managing a CG-SDT configuration for use by a UE when the UE is in an inactive state, implemented by a CU of a distributed base station, includes: transitioning the UE from a connected state to an inactive state by transmitting a message to the UE via a DU of the distributed base station. The method also includes: after transitioning the UE, transmitting a CU to DU message to the DU indicating that the DU is to release the CG-SDT configuration.
[0014] In another aspect of the present disclosure, a method for managing a CG-SDT configuration for use by a UE when the UE is in an inactive state, implemented by a CU of a distributed base station, includes: transitioning the UE from a connected state to an inactive state by transmitting a message to the UE via a DU of the distributed base station. The method also includes: after transitioning the UE, receiving a DU to CU message from the DU indicating or requesting release of the CG-SDT configuration; and transmitting a CU to DU message to the DU in response to the DU to CU message.
[0015] In another aspect of the present disclosure, a method for managing a CG-SDT configuration for use by a UE when the UE is in an inactive state, implemented by a DU of a distributed base station, includes: transmitting the CG-SDT configuration to the UE. The method also includes: after transmitting the CG-SDT configuration, receiving a CU-to-DU message from a CU of the distributed base station indicating that the DU is to release the CG-SDT configuration; and releasing the CG-SDT configuration in response to the CU-to-DU message.
[0016] In another aspect of the present disclosure, a method for managing a CG-SDT configuration for use by a UE when the UE is in an inactive state, implemented by a DU of a distributed base station, includes: transmitting a CG-SDT configuration to the UE. The method also includes: after transmitting the CG-SDT configuration, determining to release the CG-SDT configuration; and in response to the determination, transmitting a DU to CU message indicating or requesting to release the CG-SDT configuration to a CU of the distributed base station. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1A is a block diagram of an example wireless communication system in which user devices and base stations of the present disclosure may implement the techniques of the present disclosure (e.g., for reducing latency in data communications);
[0018] Figure 1B The central unit (CU) and distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.
[0019] Figure 2A yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a base station;
[0020] Figure 2B yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a CU and a DU;
[0021] Figure 3 and Figure 4 is an example of Figures 1A to 2B The device can implement a message sequence diagram of a scenario in which the configuration authorization configuration according to the technology of the present disclosure; and
[0022] Figures 5 to 11 The example can be Figures 1A to 2B Several methods for configuring authorization according to the technology of the present disclosure are implemented / performed by one or more devices of the present invention. DETAILED DESCRIPTION
[0023] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure to manage early data communications and to transition the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, unless the context clearly indicates a more specific meaning, small data communication may refer to a small data transmission (SDT) from the network perspective (i.e., SDT in the downlink direction), or SDT from the UE perspective (i.e., SDT in the uplink direction).
[0024] First reference Figure 1A , the 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.
[0025] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104, 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).
[0026] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally, UPF 162 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.
[0027] like Figure 1A As illustrated, base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or handover from one of cells 124 and 126 to the other. To exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.
[0028] 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.
[0029] 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), or controlling session management (SM), or may refer to non-signaling, non-control plane information at one or more protocol layers above the layer of a protocol for controlling radio resources (e.g., RRC), above the layer of a protocol for controlling MM, above the layer of a protocol for controlling SM, and / or above the layer of a protocol for controlling quality of service (QoS) flows (e.g., Service Data Adaptation Protocol (SDAP)). The data to which the UE and / or RAN applies the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. Further, as discussed below, in some implementations, the UE 102 applies these techniques only if the size of the data is below a certain threshold. It should also be understood that, as used herein (and unless the context of its usage indicates a more specific meaning), the term "configuration" may refer to a complete configuration, or to a subset of the parameters of a complete configuration (e.g., an "incremental" or other partial configuration that may augment an existing configuration without completely replacing the existing configuration).
[0030] In the example scenario discussed below, UE 102 transitions to the 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 the RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for UL transmission in the 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 transmit 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).
[0031] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 may generate a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 may encrypt data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate the encrypted packet and the encrypted MAC-I. Then, UE 102 may transmit the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.
[0032] In some implementations, the data is a UL service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (e.g., 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 transmits the protected UL PDCP PDU in the UL MAC PDU. In some implementations, the UE 102 may include the UL RRC message in the UL MAC PDU. In other implementations, the UE 102 may not include the UL RRC message in the UL MAC PDU. In this case, the UE 102 may not include the UE ID of the UE 102 in the UL MAC PDU that does not include the UL RRC message. In yet other implementations, the UE 102 may include the UL PDCP PDU in the UL RLC PDU, and then include the UL RLC PDU in the UL MAC PDU. In some implementations where the UE 102 includes the UL RRC message in the UL MAC PDU, the UE 102 generates an RRC MAC-I and includes the RRC MAC-I in the UL RRC message. For example, the RRC MAC-I may be a resumeMAC-I field, as specified by 3GPP specification 38.331. In other implementations, the UE 102 may utilize an integrity key (e.g., K 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).
[0033] In other implementations, the data is a UL SDU of NAS. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (such as a NAS PDU), which may be associated with a NAS layer. For example, the NAS layer may be an MM sublayer or an SM sublayer of a 5G, Evolved Packet System (EPS), or 6G. The UE 102 may then include the UL NASPDU in a second UL PDU (such as a UL RRC message). Thus, in these cases, the UE 102 transmits the (first) protected UL NAS PDU in the UL RRC message. In some implementations, the UE 102 may include the UL RRC message in a UL MAC PDU and transmit 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.
[0034] In some implementations, the UL RRC message described above may be a common control channel (CCCH) message, an RRC recovery request message, or an RRC early data request message.The UL RRC message may include the UE ID of the UE 102 as described above.
[0035] More generally, the UE 102 may protect data using ciphering and / or integrity protection, include the protected data as a security-protected packet in a first UL PDU, and transmit the first UL PDU to the RAN 105 in a second UL PDU.
[0036] 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 transmits 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 transmits 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 transmits the data to the CN 110 or the edge server. When the security-protected packet is an encrypted packet, the base station 104 obtains data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 104 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.
[0037] 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 transmits the data to the CN 110 (e.g., UPF 162) or an edge server. When the security-protected packet is an encrypted packet, the base station 106 obtains the data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 106 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 106 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The base station 106 then determines whether the MAC-I is valid for the data. If the base station 106 determines that the MAC-I is valid, the base station 106 retrieves the data and forwards the data to the CN 110. However, if the base station 106 determines that the MAC-I is invalid, the base station 106 discards the packet.
[0038] In other scenarios and implementations, the base station 104 can retrieve the UE ID of the UE 102 from the UL RRC message and identify that the base station 104 stores the UE context information of the UE 102. Therefore, the base station 104 retrieves the security-protected packet from the first UL PDU, retrieves the data from the security-protected packet, and sends the data to the CN 110 or the edge server, as described above.
[0039] Further, in some implementations and scenarios, the RAN 105 transmits data in the DL direction to the UE 102 operating in the RRC_INACTIVE or RRC_IDLE state.
[0040] In one implementation, when the base station 104 determines that data is available for downlink transmission to a UE 102 currently operating in an RRC_INACTIVE or RRC_IDLE state, the base station 104 may apply at least one security function to the data to generate a security-protected packet, generate a first DL PDU including the security-protected packet, and include the first DLPDU in a second DL PDU. In order to protect the data, the base station 104 may apply a security function (e.g., integrity protection and / or encryption) to the DL data. More particularly, when integrity protection is enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data, so that the security-protected packet includes the DL data and the MAC-I. When encryption is enabled, the base station 104 may encrypt the data to generate an encrypted packet, so that the security-protected packet is an encrypted packet. Further, when both integrity protection and encryption are enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. In some implementations, the base station 104 generates a first DL PDU (such as a DL PDCP PDU) using the security-protected packet, includes the first DL PDU in a second DL PDU (e.g., a DL MAC PDU) associated with a MAC layer, for example, and transmits 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 transmits 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.
[0041] In another implementation, the base station 104 transmits 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 transmits 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 transmits 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 transmits the second DL PDU to the UE 102.
[0042] 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 transmit 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 transmits 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) transmitted by the base station in a random access process with UE 102 before transmitting 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) transmitted by the base station to UE 102 before transmitting the DCI and the scrambled CRC (e.g., when UE 102 is in the RRC_CONNECTED state).
[0043] UE 102 operating in RRC_INACTIVE or RRC_IDLE state may receive DCI and the scrambled CRC on PDCCH, and then confirm that the physical downlink shared channel (PDSCH) including the second DL PDU is addressed to UE 102 according to the ID of UE 102, DCI and the scrambled CRC. Then, UE 102 may retrieve data from the security-protected packet. If the security-protected packet is an encrypted packet, 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 MAC-I, UE 102 may determine whether MAC-I is valid. If UE 102 confirms that MAC-I is valid, UE 102 retrieves the data. However, if UE 102 determines that MAC-I is invalid, UE 102 discards the packet. If the security-protected packet is both encrypted and integrity-protected (having encrypted data and an encrypted MAC-I), the UE 102 can decrypt the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The UE 102 can then verify that the MAC-I is valid for the data. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves and processes the data. Otherwise, when the UE 102 determines that the MAC-I is invalid, the UE 102 discards the data.
[0044] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a MAC controller 132, which is configured to: perform a random access process with one or more user devices, receive UL MAC protocol data units (PDUs) from one or more user devices (UEs), and transmit DL MAC PDUs to one or more user devices (UEs). The processing hardware 130 may also include a PDCP controller 134, which is configured to transmit and / or receive PDCP PDUs according to the manner in which the base station 104 can transmit DL data and / or receive UL data. The processing hardware may further include an RRC controller 136 to implement processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 130 includes an RRC inactive controller 138 that is configured to manage uplink and / or downlink communications with one or more UEs operating in an RRC_INACTIVE or RRC_IDLE state. The base station 106 may include generally similar components. In particular, the components 140, 142, 144, 146, and 148 of the base station 106 may be similar to the components 130, 132, 134, 136, and 138, respectively.
[0045] 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 communication 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, transmit 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 transmit and / or receive PDCP PDUs according to the manner in which the base station 106 transmits DL data and / or receives UL data. The processing hardware may further include an RRC controller 156 to implement procedures and message delivery at the RRC sublayer of the protocol communication stack.
[0046] Figure 1BAn example distributed or decomposed implementation of a base station 170 is depicted, which may represent one or both of base stations 104, 106. In this implementation, base station 170 includes a central unit (CU) 172 and one or more distributed units (DU) 174. CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on a general-purpose processor, and / or a dedicated processing unit. For example, CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as PDCP controllers 134, 144, RRC controllers 136, 146, and / or RRC inactive controllers 138, 148. In some implementations, CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, CU 172 does not include an RLC controller.
[0047] Each DU in DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors, and / or dedicated processing units. For example, the processing hardware may include: a MAC controller (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or processes.
[0048] 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.
[0049] 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 transmit control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may transmit data packets (e.g., SDAPPDUs or Internet Protocol packets).
[0050] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the requested service of UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, connectivity between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.
[0051] Figure 2A An example protocol stack 200 is illustrated in a simplified manner according to which a UE 102 may communicate with an eNB / ng-eNB 201A or a gNB / en-gNB 201B (e.g., one or both of base stations 104, 106).
[0052] 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 may in turn provide data to the SDAP 212 or RRC sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As illustrated, the UE 102 may support NR PDCP 210 layered on top of EUTRA RLC 206A, and SDAP sublayer 212 layered on top of NR PDCP sublayer 210.
[0053] 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.
[0054] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2A The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide data radio bearers (DRBs) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.
[0055] Figure 2B An example protocol stack 250 is illustrated in a simplified manner by which UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the 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.
[0056] Next, refer to Figures 3 to 5 B to discuss Figure 1A The various components of and several example scenarios related to transmitting data in an inactive or idle state. To simplify the following description, the "inactive state" may represent the RRC_INACTIVE or RRC_IDLE state, and the "connected state" may represent the RRC_CONNECTED state.
[0057] First reference Figure 3, in scenario 300, base station 104 includes CU 172 and DU 174, and CU 172 includes CU-CP 172A and CU-UP 172B. In this scenario 300, UE 102 initially operates in connected state 302, and communicates 304 with DU 174, for example, by using DU configuration (i.e., first non-SDT configuration), and communicates 304 with CU-CP 172A and / or CU-UP 172B via DU by using CU configuration (i.e., first non-SDT CU configuration). While UE is communicating 304 with base station 104, CU-CP 172A may send 306 a UE context modification request message. In response, DU 174 sends 308 a UE context modification response message including a non-SDT configuration for UE 102 (i.e., second non-SDT configuration) to CU-CP 172A. CU-CP 172A generates an RRC reconfiguration message including the non-SDT DU configuration and transmits 310 a first CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to DU 174. DU 174, in turn, transmits 312 the RRC reconfiguration message to UE 102. In response, UE 102 transmits 314 an RRC reconfiguration complete message to DU 174, which in turn transmits 316 a first DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to CU-CP 172A.
[0058] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the non-SDT DU configuration and communicates with the CU-CP 172A and / or CU-UP 172B via the DU. In the event that the RRC reconfiguration message does not include a CU configuration, the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the first non-SDT CU configuration. In the event that the RRC reconfiguration message includes a non-SDT CU configuration (i.e., a second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the second non-SDT CU configuration. In some implementations, the second non-SDT CU configuration may augment the first non-SDT CU configuration or include at least one new configuration parameter not included in the first non-SDT CU configuration. In such a case, the UE 102 and the CU-CP 172A and / or CU-UP 172B may communicate with each other using the second non-SDT CU configuration and also using configuration parameters in the first non-SDT CU configuration that are not augmented by the second non-SDT CU configuration 318. In some implementations, the first non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers (e.g., RRC 214 and / or NR PDCP 210), which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT CU configuration may include configuration parameters related to the operation of the RRC and / or PDCP protocol layers, which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT CU configuration may include configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE.
[0059] In some implementations, the second non-SDT DU configuration may extend the first non-SDT DU configuration or include at least one new configuration parameter not included in the first non-SDT DU configuration. In such cases, the UE 102 and the DU 174 may communicate 318 with each other using the second non-SDT DU configuration and also using configuration parameters in the first non-SDT DU configuration that are not extended by the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT DU configuration may include configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers, which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT DU configuration may include configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration may be CellGroupConfig IEs.
[0060] Events 306, 308, 310, 312, 314, 316, and 318 are Figure 3 This is collectively referred to as the non-SDT resource (re)configuration process 390, which may be optional.
[0061] While the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration procedure 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., based on the UE 102 in the connected state not having data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration procedure 390 (if performed), the UE 102 determines or detects the data inactivity and transmits 320 to the DU 174 UE assistance information (e.g., a UEAssistanceInformation message) indicating that the UE 102 requests to transition to the inactive state configured with SDT. Then, the DU 174 transmits 321 to the CU-CP 172A a UL RRC messaging message including the UE assistance information. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may transmit 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 transmit 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 transmit a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the event that CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may transmit 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.
[0062] 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 transmitted any data in the downlink direction or the uplink direction, respectively, during the specific period. In response to this determination, CU-CP 172A may determine to transition UE 102 to an inactive state with SDT configured. Alternatively, in response to determining that UE 102 is in data inactivity, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured.
[0063] In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 326 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, in some implementations, the CU-CP 172A may send 328 a second CU-to-DU message (e.g., a UE context modification request message) to direct the DU 174 to provide an SDT DU configuration for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., an IE, such as a CG-SDT query indication IE) to request 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 transmit 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or transmitting the second DU-to-CU message, the DU 174 sends an additional DU-to-CU message (e.g., a UE context modification required message) including the SDT DU configuration to the CU-CP 172A. In response to the additional CU-to-DU message, the CU-CP 172A may transmit an additional CU-to-DU message (e.g., a UE context modification confirmation message) to the DU 174. In some alternative implementations, CU-CP 172A may transmit a second CU to DU message and receive a second DU to CU message or an additional DU to CU message before determining that UE 102 is in data inactivity. In other alternative implementations, CU-CP 172A may include an SDT request indication in the first CU to DU message of event 308, and DU 174 includes an SDT DU configuration in the first DU to CU message of event 310 in response to the SDT request indication.
[0064] In response to determining to transition the UE 102 to an inactive state configured with SDT, the CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message, an RRCConnectionRelease message) to transition the UE 102 to an inactive state. The CU-CP 172A may include the SDT DU configuration (if obtained from the DU 174) and / or the SDT CU configuration in the RRC release message. The CU-CP 172A then sends 332 a third CU-to-DU message (e.g., a UE context release command message, a UE context modification request message, or a DL RRC messaging message) including the RRC release message to the DU 174. Subsequently, the DU 174 transmits 334 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and transmits 334 the MAC PDU to the UE 102. The RRC release message directs the UE 102 to transition to an inactive state. UE 102 transitions 336 from the connected state to the inactive state upon receiving the RRC release message. In response to the third CU-to-DU message, DU 174 may retain the SDT DU configuration (if generated by DU 174 during processes 328, 330), and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. In response to the third CU-to-DU message, 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.
[0065] When operating 302 in a connected state, the UE 102 uses the C-RNTI to monitor the PDCCH to receive DCI. In response to receiving 334 an RRC release message or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. In some implementations, in response to receiving 334 an RRC release message or transitioning 336 from a connected state to an inactive state or thereafter, the UE 102 may retain the C-RNTI. In some implementations, the UE 102 performs a two-step or four-step random access procedure with a 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, the UE 102 receives a random access response message from the CU-CP 172A or from the DU 174 via the DU 174. Figure 3 Another base station (eg, base station 106) not shown in the figure receives an RRC message (eg, an RRC reconfiguration message) including the C-RNTI.
[0066] Events 320 (optional), 321 (optional), 322 (optional), 323, 324, 326, 328, 330, 332, and 334 are Figure 3 It is collectively referred to as the SDT configuration process 394.
[0067] In some implementations, in response to the RRC release message, the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT DU configuration or at least a portion of the first non-SDT DU configuration and at least a portion of the second non-SDT DU configuration. In other implementations, if the RRC release message directs the UE 102 to transition to an inactive state (i.e., RRC_IDLE), the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT configuration. In still other implementations, if the RRC release message directs the UE to transition to an inactive state (i.e., RRC_INACTIVE), the UE 102 releases the first portion of the first and / or second non-SDT DU configuration and retains the second portion of the first and / or second non-SDT DU configuration.
[0068] In some implementations, CU-CP 172A does not include an indication to direct DU 174 to retain the SDT DU configuration in the third CU to DU message, and DU 174 retains the SDT DU configuration, as described above. In other implementations, CU-CP 172A may include an indication to direct DU 174 to retain the SDT DU configuration in a third CU to DU message (e.g., a UE context release command message), and DU 174 retains the SDT DU configuration in response to the indication. If the UE context release command message excludes the indication, DU 174 releases the SDT DU configuration. In yet other implementations, CU-CP 172A does not include an indication to direct DU 174 to release the SDT DU configuration in a third CU to DU message (e.g., a UE context modification request message or a DL RRC messaging message) for UE 102. Therefore, in response to the third CU to DU message excluding the indication, DU 174 retains the SDT DU configuration. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.
[0069] In some implementations, the SDT CU configuration (e.g., SDT-Config IE) includes a DRB list (e.g., std-DRB-List) including 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) indicating the SRB2 configured for SDT. In some implementations, the SDT CU configuration may include an indication that the PDCP entity of the DRB configured for SDT is in SDT operation (i.e., Figure 4 In some implementations, the CU-CP 172A may include an SDT DU configuration in an SDT CU configuration. The “SDT CU configuration” may also be referred to as an “SDT configuration”.
[0070] In some implementations, the SDT DU configuration includes at least one of a buffer status report (BSR) configuration, a power headroom report (PHR) configuration, and / or a CG-SDT configuration. The CG-SDT configuration may include or be one or more CG configurations for CG-SDT, a DL bandwidth part (BWP) configuration for CG-SDT, a time alignment timer value for CG-SDT (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 use by the UE 102 to determine whether the UE 102 can initiate SDT using the configured authorization configuration for CG-SDT, such as for Figure 4 Based on the timing advance validity threshold, UE 102 may evaluate whether the stored timing advance value is still valid. If UE 102 determines that the stored timing advance value is invalid, UE 102 may initiate a RA-SDT with CU 172 via DU 174, as described for Figure 4 In some implementations, the SDT DU configuration may be an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE.
[0071] In some implementations, DU 174 may start or restart the DU CG-SDT timer in response to or after receiving an SDT request indication, generating a CG-SDT configuration, receiving 328 a second CU to DU message, transmitting 330 a CG-SDT configuration to CU 172, receiving 332 a third CU to DU message, or transmitting 334 a CG-SDT configuration to UE 102. In some implementations, DU 174 may start or restart a 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, DU 174 releases the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 avoids receiving PUSCH transmissions from UE 102 on radio resources reserved or configured for the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 may schedule transmissions of other UEs on radio resources reserved or configured for the CG-SDT configuration.
[0072] As described above, in some implementations, the RRC release message 334 may include a CG-SDT configuration. In response to receiving the CG-SDT configuration or thereafter, the UE 102 may start or restart a UE CG-SDT timer (e.g., a CG-SDT time alignment timer (CG-SDT-TAT)). In some implementations, the UE 102 may start or restart a UE CG-SDT timer with a CG-SDT time alignment timer value. If and when the CG-SDT timer expires, the UE 102 releases the CG-SDT configuration. When or thereafter the CG-SDT configuration is released, the UE 102 avoids transmitting PUSCH transmissions on radio resources reserved or configured for the CG-SDT configuration.
[0073] In some implementations, DU 174 reserves the radio resources configured in the CG configuration. In some implementations, DU 174 releases the radio resources when releasing the SDT DU configuration or the CG-SDT configuration. In the case where DU 174 does not provide the CG-SDT configuration or the SDT DU configuration to CU-CP 172A, DU 174 releases all signaling and user data transmission resources for UE 102 in response to the third CU to DU message. In the case where DU 174 provides the SDT DU configuration or the CG-SDT configuration to CU-CP 172A, DU 174 reserves the signaling and user data transmission resources for UE 102 in response to receiving the third CU to DU message or thereafter.
[0074] In the case where the SDT DU configuration does not include a configuration for CG-SDT, CU-CP 172A and / or DU 174 only configure RA-SDT for UE 102. In such a case, UE 102 may perform RA-SDT with CU 172 via DU 174, such as for Figure 4 described.
[0075] In some implementations, when determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may not request DU 174 to provide an SDT DU configuration. In such cases, events 328 and 330 may be omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own (without requesting DU 174 to provide the SDT DU configuration) and include the SDT DU configuration in the RRC release message.
[0076] 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 transmit 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.
[0077] In some implementations, when UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A may request DU 174 to provide SDT DU configuration, as described above. When UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. When the UE operates 302 in a connected state, CU-CP 172A may receive UE capabilities (e.g., UE-NR-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. UE capabilities indicate whether UE 102 supports CG-SDT. Therefore, CU-CP 172A may determine whether UE 102 supports CG-SDT based on 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).
[0078] In some implementations, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the UE 102 supports CG-SDT. In addition to whether the UE 102 supports CG-SDT, the DU 174 may additionally determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the DU 174 supports CG-SDT. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). When the UE operates in a connected state 302 or in an inactive state before event 302, the DU 174 may receive the UE capabilities from the CU-CP 172A. Therefore, the DU 174 may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, the DU 174 may send a DU-to-CU message to the CU-CP 172A indicating whether the DU 174 supports or does not support CG-SDT, as described above.
[0079] Reference now Figure 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 in an inactive state with SDT configured 402. In some implementations or scenarios, UE 102 may transition from a connected state to an inactive state with SDT configured, such as for Figure 3As described. In such an implementation, the 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, the UE 102 may transition from an inactive state where SDT is not configured to an inactive state where SDT is configured. For example, the UE 102 may receive an RRC release message (e.g., indicating the release of SDT, or not including the SDT configuration in the RRC release message) from a base station (e.g., base station 104 or base station 106) that transitions the UE 102 to an inactive state but does not configure SDT. In this case, the UE 102 transitions to an inactive state where SDT is not configured in response to the RRC release message. Both UEs 102 in an inactive state where SDT is configured or not configured may perform a RAN notification area (RNA) update with the base station without a state transition. During the RNA update, the UE 102 receives another RRC release message from the base station that includes a first SDT CU configuration and / or a first SDT DU configuration similar to the RRC release message of event 334.
[0080] Later, the UE 102 operating in the inactive state configured with SDT initiates the SDT. In response to or after initiating the SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message and transmits 404 the initial UL MAC PDU to the DU 174 on the cell 124. After initiating the SDT or transmitting the initial UL MAC PDU (e.g., in response thereto), the UE 102 may start the SDT session timer. In some implementations, the SDT session timer may be a new timer defined in the RRC specification (e.g., v17.0.0). The DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends 406 the first DU to CU message to the CU-CP 172A. In some implementations, the first DU to CU message may be an initial UL RRC messaging message. In other implementations, the first DU to CU message may be a UL RRC messaging message.
[0081] In a scenario where the UE 102 initiates an SDT to transmit UL data (e.g., a data packet) eligible for SDT, the UE 102 includes the UL data in an initial UL MAC PDU transmitted 404 by the UE 102. In a scenario where the UE 102 initiates an SDT to receive DL data, the UE 102 does not include the UL data packet in the initial UL MAC PDU transmitted 404 by the UE 102. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging from the DU 174. In such a scenario, the UE 102 may include an SDT indication in an initial UL MAC PDU or UL RRC message to indicate to the base station 104 that the UE 102 is initiating an SDT to receive DL data.
[0082] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to transmit 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 transmits a random access preamble to the DU 174, and in response, the DU 174 transmits 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 transmits 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 transmits 404 a message A (MsgA) including a random access preamble and a UL MAC PDU to the DU 174 according to the two-step random access configuration parameters. In response to MsgA, UE 102 may receive message B (MsgB) including a temporary C-RNTI and a timing advance command from DU 174. UE 102 receives two-step random access configuration parameters in system information broadcast by DU 174 on cell 124 before transmitting 404 the UL MAC PDU. DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.
[0083] When UE 102 successfully resolves contention during the random access procedure, UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3418 UE 102 receives 418 the UL data from the DU 174 using the C-RNTI. UE 102 uses the C-RNTI to monitor the PDCCH from DU 174 to communicate 418 data with DU 174. More specifically, UE 102 receives the DCI and the CRC of the DCI on the PDCCH from DU 174 and verifies the CRC using the C-RNTI. The DCI may include an uplink grant or a downlink assignment. If UE 102 verifies that the CRC is correct and the DCI includes an uplink grant, UE 102 transmits 418 UL data to DU 174 using the uplink grant. If UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, UE 102 receives 418 DL data from DU 174 using the downlink assignment.
[0084] In other implementations, after UE 102 receives the Figure 3 In the case of the CG configuration for SDT (ie, CG-SDT configuration), the UE 102 may transmit 404 the UL MAC PDU on the radio resources configured in this configuration. Thus, the DU 174 receives 404 the UL MAC PDU on the radio resources.
[0085] In some implementations, the UE 102 may transmit 418 subsequent UL MAC PDUs including one or more UL data packets on the radio resources configured in the CG configuration. In some implementations, the UE 102 may transmit 418 subsequent UL MAC PDUs on the radio resources configured in the uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 may transmit 418 some of the subsequent UL MAC PDUs on the radio resources configured in the CG configuration and transmit 418 other of the subsequent UL MAC PDUs on the radio resources configured in the uplink grant.
[0086] 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 PDUn, 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.
[0087] 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 transmit 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, transmitting 408 the UE context setup request message, or receiving 410 the UE context setup response message, CU-CP 172A transmits 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 transmits 414 a bearer context modification response message to CU-CP 172A. After receiving 408 the UE context setup request message or transmitting 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 transmit 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 transmit 416 the UL data to CU-UP 172B.
[0088] 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 transmit 416 the UL data to the CU-UP 172B using the transport layer information of the CU-UP 172B. In the event that the UE 102 has subsequent UL data (e.g., one or more UL data packets) to transmit, the UE 102 may transmit 418 one or more subsequent UL MAC PDUs including the subsequent UL data to the DU 174. Then, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the event that the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 transmits 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 transmit 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 transmits 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.
[0089] In the case where the subsequent UL data is associated with one or more DRBs, DU 174 transmits 418 the subsequent UL data to CU-UP 172B, which is similar to event 416. In some implementations, DU 174 may include DU transport layer information of DU 174 in the UE context setup response message. Then, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. The transport layer information of DU 174 may include an IP address and / or a downlink TEID. In the case where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B may transmit 418 DL data (e.g., one or more DL data packets) to DU 174 using the transport layer information of DU 174. Then, DU 174 transmits 418 one or more DL MAC PDUs including the DL data to UE 102 operating in an inactive state.
[0090] 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.
[0091] In some example scenarios, the subsequent UL data and / or DL data described above include IP packets, Ethernet packets, or application packets. In other scenarios, the UL data may include or be a PDU (e.g., RRC PDU, PDCP PDU, or RLC PDU), which includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.
[0092] Events 404, 406, 408, 410, 412, 414, 415, and 416 are Figure 4 It is collectively referred to as the small data transmission process 492.
[0093] In some implementations, the UL RRC message is an (existing) RRC recovery request message (e.g., RRCResumeRequest message, RRCResumeRequest message, RRCConnectionResumeRequest message, or RRCConnectionResumeRequest message). In other implementations, the UL RRC message may be a new RRC recovery request message similar to the existing RRC recovery request message. For example, the new RRC recovery request message may be defined in a future 3GPP standard document. The new RRC recovery request message may have the format of the existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message may include an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.
[0094] After the UE 102 transmits 404 a UL MAC PDU or communicates 418 subsequent UL data and / or DL data with the DU 174, the CU-CP 172A may determine to stop the SDT of the UE 102 based on data inactivity of the UE 102 (i.e., based on the UE 102 in the inactive state not having data activity with the base station 104). After the UE 102 transmits 404 a 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 transmits 420 to the DU 174 UE assistance information (e.g., UEAssistanceInformation message) indicating that the UE 102 decides (e.g., needs) or requests to stop the SDT. Then, the DU 174 transmits 421 to the CU-CP 172A a UL RRC messaging message including the UE assistance information. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may transmit a CU to DU message (e.g., a UE context setup request message of event 408, or a UE context modification request message) to DU 174 to request or command DU 174 to perform data inactivity monitoring. In the case where DU 174 detects or determines that UE 102 is in data inactivity during monitoring, DU 174 may transmit 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 transmit a CP to UP message to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In some implementations, if sent before UE 102 initiates SDT, the CP to UP message may be a bearer context setup request message or a bearer context modification request message. In other implementations, if sent during SDT, the CP to UP message may be a bearer context modification request message (e.g., event 412). In the event that CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may transmit 423 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from CU-UP 172B.In some implementations, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information, the inactivity notification of event 422 , and / or the inactivity notification of event 423 .
[0095] After a specific period of data inactivity, CU-CP 172A may determine that neither CU 172 nor UE 102 transmitted any data in the downlink direction or the uplink direction during the specific period. In response to this determination, CU-CP 172A may determine to stop SDT. Alternatively, in response to determining that UE 102 is in data inactivity, CU-CP 172A may determine to immediately stop SDT for UE 102.
[0096] In response to determining that the UE 102 is in data inactivity (for the specific period) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 424 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 426 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 428 a second CU-to-DU message (e.g., a UE context modification request message) to instruct the DU 174 to provide an SDTDU configuration (e.g., a second SDT DU configuration) for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., a field or IE) for requesting an SDT DU configuration in a second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 transmits 430 a second DU-to-CU message (e.g., a UE context modification response message) including the second SDT DU configuration to the CU-CP 172A. Alternatively, the DU 174 does not include the second SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or transmitting the second DU-to-CU message, the DU 174 sends another DU-to-CU message (e.g., a UE context modification required message) including the second SDT DU configuration to the CU-CP 172A. In some alternative implementations, the CU-CP 172A may transmit the second CU-to-DU message and receive the second DU-to-CU message (or the other DU-to-CU message) before determining that the UE 102 is in data inactivity.
[0097] In response to determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message or an RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include a second SDT DU configuration (if obtained from DU 174) and / or a second SDT CU configuration in the RRC release message.
[0098] 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.
[0099] 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 transmits 434 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and transmits 434 the MAC PDU to the UE 102. The RRC release message directs the UE 102 to be in an inactive state (e.g., transition to an inactive state or maintain an inactive state). The UE 102 stops the SDT upon receiving 434 the RRC release message and remains 436 in an inactive state.
[0100] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 The SDT completion process is collectively referred to as 494.
[0101] During the SDT session (i.e., events 492 and 494), UE 102 uses the C-RNTI to monitor the PDCCH to receive DCI. In some implementations, UE 102 receives the C-RNTI during the random access procedure described for event 404. In other implementations, UE 102 may receive and retain the C-RNTI, such as for Figure 3In response to receiving 434 the RRC release message or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. In response to receiving 434 the RRC release message or thereafter transitioning 436 from the connected state to the inactive state, the UE 102 may retain the C-RNTI. In the case where the RRC release message 434 configures the CG-SDT, in some implementations, the UE 102 may retain the C-RNTI. In the case where the RRC release message 434 does not configure or release the CG-SDT, in some implementations, the UE 102 may release the C-RNTI.
[0102] In some implementations, the second SDT CU configuration may be the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration may be different from the first SDT CU configuration. The UE 102 may update (e.g., replace or modify) the first SDT CU configuration using the second SDT CU configuration. In some implementations, the CU-CP 172A may include an indication in the RRC release message to indicate that the UE 102 is to update the first SDT CU configuration using the second SDT CU configuration. In such implementations, the UE 102 may update the first SDT CU configuration using the second SDT CU configuration in response to the indication. In other implementations, the CU-CP 172A may include a modification indication in the RRC release message to indicate that the UE 102 is to modify the first SDT CU configuration using the second SDT CU configuration. In such implementations, the UE 102 may modify the first SDT CU configuration using the second SDT CU configuration in response to the modification indication. In yet other implementations, CU-CP 172A may include a setup indication in the RRC release message to indicate that UE 102 is to replace the first SDT CU configuration with the second SDT CU configuration. In such implementations, UE 102 may replace the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.
[0103] In some implementations, the second SDT DU configuration may be the same as the first SDT DU configuration. In other implementations, the second SDT DU configuration may be different from the first SDT DU configuration. The UE 102 may update (e.g., replace or modify) the first SDT DU configuration using the second SDT DU configuration. In some implementations, the DU 174 may include in the second SDT DU configuration an indication indicating that the UE 102 is to update the first SDT DU configuration using the second SDT configuration. In such implementations, the UE 102 may update the first SDT DU configuration using the second SDT DU configuration in response to the indication. In some 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 using the second SDT DU configuration. In such implementations, the UE 102 may modify the first SDT DU configuration using the second SDT DU configuration in response to the modification indication. In yet other implementations, the DU 174 may include a setup indication in the second SDT DU configuration to indicate 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.
[0104] In the case where the CU-CP 172A and / or the DU 174 support incremental configuration, the CU-CP 172A may not send 428 a CU to DU message to obtain the second SDT DU configuration from the DU 174. The DU 174 retains the first SDT DU configuration unless the conditions for releasing the first SDT configuration are met. Alternatively, the CU-CP 172A may include the first SDT DU configuration in the second CU to DU message so that the DU 174 retains the first SDT DU configuration. In these cases, the CU-CP 172A may not include the SDT DU configuration and / or the SDT CU configuration in the RRC release message so that the UE 102 continues to use the first SDT CU configuration and / or the first SDT DU configuration. In some implementations, the CU-CP 172A may not include a release indication in the RRC release message so as to configure the UE 102 to continue to use the first SDT DU configuration and / or the first SDT CU configuration. The release indication indicates that the UE 102 will release the previously received SDT DU configuration and / or SDT CU configuration. In the case where the CU-CP 172A includes the release indication in the RRC release message, the UE 102 releases the first SDT CU configuration and / or the first SDT DU configuration in response to the release indication.
[0105] In the event that the CU-CP 172A and / or the DU 174 do not support incremental configuration, the CU-CP 172A may include the SDT DU configuration and / or the SDT CU configuration in the RRC release message, as described above.
[0106] In response to the third CU-to-DU message, DU 174 may retain the second SDT DU configuration and may or may not release the first non-SDT DU configuration and / or the second non-SDT DU configuration. In response to the third CU-to-DU message, DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A. In some implementations, if the RRC release message directs UE 102 to transition to an inactive state (i.e., RRC_IDLE), UE 102 releases the non-SDT configuration (e.g., for RRC_CONTENT). Figure 3 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) and at least one SDT configuration (e.g., for Figure 3 The SDTDU configuration and SDT CU configuration described above).
[0107] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 The SDT completion process 494 is collectively referred to as the SDT completion process 494, which is similar to the process 394. The examples and implementations for events 320, 321, 322, 323, 324, 326, 328, 330, 332, 334 can be respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, 434. After stopping the SDT, if the UE 102 is configured with the SDT configuration, the UE 102 can perform another SDT process 493 with the base station 104, which is similar to the process 492. After completing the process 493, the base station 104 can perform an SDT completion process 495 with the UE 102, which is similar to the process 494.
[0108] In some implementations, CU-CP 172A does not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state configured with SDT. In such cases, events 428 and 430 may be omitted, 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 and include the SDT DU configuration in the RRC release message.
[0109] 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.
[0110] In some implementations, in the case where the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the CU-CP 172A may request the DU 174 to provide the SDT DU configuration, as described above. In the case where the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the CU-CP 172A does not request the DU 174 to provide the SDT DU configuration. Before the UE 102 initiates SDT when the UE is operating 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 as for Figure 3 When the UE operates in a connected state, the CU-CP 172A may receive the UE capabilities (e.g., UE-NR-Capability IE) of the UE 102 from the UE 102, the CN 110 (e.g., the MME 114 or the AMF 164), or the base station 106. The UE capabilities indicate whether the UE 102 supports CG-SDT. Therefore, the CU-CP 172A may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, the CU-CP 172A may receive a DU to CU message from the DU 174 indicating whether the 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 as defined in 3GPP specification 38.473).
[0111] In some implementations, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the UE 102 supports or does not support CG-SDT. In addition to whether the UE 102 supports CG-SDT, the DU 174 may additionally determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the DU 174 supports CG-SDT. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports 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 event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). 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. Therefore, DU 174 may determine whether UE 102 supports CG-SDT based on the UE capabilities. In some implementations, DU 174 may send a DU-to-CU message to CU-CP 172A indicating whether DU 174 supports or does not support CG-SDT, as described above.
[0112] Next, refer to Figures 5 to 11 Several example methods that may be implemented in one or more base stations, DUs or CUs, or in a RAN to support data communications in an inactive state are discussed.In the following description, "CG-SDT" may be replaced with "CG" and vice versa.
[0113] Figure 5 The illustrated method 500 may be implemented / performed by a CU (eg, CU 172 or CU-CP 172A) for managing CG-SDT of a UE (eg, UE 102).
[0114] Method 500 starts at box 502, where the CU determines to configure CG-SDT for the UE. At box 504, in response to the determination at box 502, the CU obtains the CG configuration from the DU to configure the CG-SDT for the UE (e.g., events 328, 330, 428, 430, 394, 494, 495). At box 506, the CU transmits an RRC release message including the CG configuration to the UE via the DU (e.g., events 332, 334, 432, 434, 394, 494, 495). At box 508, the CU starts the CG timer to manage the CG configuration in response to the determination or the transmission of the RRC release message. After box 508, the process proceeds to box 510 and / or box 514. At box 510, the CU detects the expiration of the CG timer. At box 512, the CU transmits a CU to DU message to the DU to indicate the release of the CG configuration in response to (at box 510) detecting the expiration of the CG timer. Otherwise (or additionally), flow proceeds to block 514. At block 514, the CU receives a DU-to-CU message from the DU. At block 516, the CU restarts the CU timer in response to the DU-to-CU message.
[0115] To transmit the RRC release message to the UE via the DU, in some implementations, the CU generates a PDCP PDU including the RRC release message, and transmits a CU-to-DU message (e.g., a UE context release command message or a DL RRC messaging message) including the PDCP PDU to the DU. The DU retrieves the PDCP PDU from the CU-to-DU message, generates an RLC PDU including the PDCP PDU, generates a MAC PDU including the RLC PDU, and transmits the MAC PDU to the UE. To transmit the MAC PDU, the DU may generate a PDSCH transmission including the MAC PDU, and transmit the PDSCH transmission to the UE.
[0116] In some implementations, after transmitting an RRC release message, a PDCP PDU, an RLC PDU, or a MAC PDU, the DU resets the MAC entity used by the DU to communicate with the UE. In other implementations, after receiving an RLC acknowledgment for the RLC PDU (e.g., in response to the reception), the DU resets the MAC PDU entity. In still other implementations, in response to or after receiving a HARQ acknowledgment for a MAC PDU or PDSCH transmission, the DU resets the MAC entity.
[0117] In some implementations, the CU may receive a DU to CU message (e.g., a UE context modification required message) from the DU and restart the CU in response to the DU to CU message. In some implementations, when communicating with the UE using a CG configuration, the DU transmits a timing advance command to the UE. In response to transmitting the timing advance command to the UE, the DU may transmit a DU to CU message to the CU.
[0118] In some implementations, the UE starts or restarts the CG-SDT-TAT in response to receiving the RRC release message. The UE restarts the CG-SDT-TAT when the UE receives a timing advance command from the DU.
[0119] In some implementations, the CU may include an indication of releasing the CG configuration in the CU to DU message. In some implementations, the indication may be a cause value.
[0120] Fig. 6A Illustrated is a method 600A that may be implemented / performed by a DU (eg, DU 174) for managing CG-SDT of a UE (eg, UE 102).
[0121] Method 600A starts at box 602, where the DU receives a first CU-to-DU message from the CU requesting a CG configuration for the UE (e.g., events 328, 428, 394, 494, 495). At box 604, in response to the first CU-to-DU message, the DU transmits a first DU-to-CU message including a CG configuration for the UE to the CU. At box 606, the DU receives a second CU-to-DU message from the CU including an RRC release message for the UE (e.g., events 332, 432, 394, 494, 495). At box 608, the DU transmits an RRC release message to the UE (e.g., events 334, 434, 394, 494, 495). At box 610, the DU starts or restarts a CG timer to manage the CG configuration in response to the first CU-to-DU message or the second CU-to-DU message. At box 612, the DU (attempts) to receive a PUSCH transmission from the UE according to the CG configuration. After block 612, the flow proceeds to block 614 and / or block 618. At block 614, the DU detects expiration of the CG timer. At block 616, in response to detecting expiration of the CG timer, the DU stops attempting to receive or receiving PUSCH transmissions according to the CG configuration. Otherwise, the flow proceeds to block 618. At block 618, the DU transmits a timing advance command to the UE. At block 620, the DU restarts the CG timer in response to transmitting the timing advance command to the UE.
[0122] To transmit the RRC message to the DU in the second CU-to-DU message, in some implementations, the CU generates a PDCP PDU including the RRC release message and includes the PDCP PDU in the second CU-to-DU message. In such implementations, the DU receives the second CU-to-DU message including the PDCP PDU at block 906. Then, the DU generates an RLC PDU including the PDCP PDU, generates a MAC PDU including the RLC PDU, and transmits the MAC PDU to the UE. To transmit the MAC PDU, the DU may generate a PDSCH transmission including the MAC PDU and transmit the PDSCH transmission to the UE.
[0123] In some implementations, after transmitting an RRC release message, a PDCP PDU, an RLC PDU, or a MAC PDU, the DU resets the MAC entity used by the DU to communicate with the UE. In other implementations, the DU resets the MAC PDU entity in response to or after receiving an RLC acknowledgment for the RLC PDU. In still other implementations, the DU resets the MAC entity in response to or after receiving a HARQ acknowledgment for a MAC PDU or PDSCH transmission.
[0124] In some implementations, the DU may include a CG-SDT-TAT value in the CG configuration so that the UE manages the CG configuration. In some implementations, the DU may set a CG timer value of the CG timer to a value based on (e.g., close to) the CG-SDT-TAT value to ensure that the DU does not miss receiving a PUSCH transmission transmitted by the UE according to the CG configuration. For example, the DU may set the CG timer value to a value greater than or equal to the CG-SDT-TAT value to ensure that the UE releases the CG configuration before the DU releases the CG configuration.
[0125] In some implementations, the DU releases the CG configuration upon detecting the expiration of the CG timer. In some implementations, upon detecting the expiration of the CG timer or releasing the CG configuration, the DU may transmit a DU to CU message to the CU indicating that the CG configuration is released or that the UE is not configured with the CG configuration. In some implementations, the DU may reset the MAC entity in response to detecting the expiration of the CG timer.
[0126] Figure 6B6 is a flow chart of an example method 600B similar to method 600A. Method 600B begins at block 602, where the DU receives a first CU-to-DU message from the CU requesting a CG configuration for the UE (e.g., events 328, 428, 394, 494, 495). At block 604, in response to the first CU-to-DU message, the DU transmits a first DU-to-CU message including a CG configuration for the UE to the CU (e.g., events 328, 428, 394, 494, 495). At block 606, the DU receives a second CU-to-DU message from the CU including an RRC release message for the UE (e.g., events 332, 432, 394, 494, 495). At block 609, the DU transmits a DL MAC PDU including a timing advance command and an RRC release message to the UE (e.g., events 334, 434, 394, 494, 495). At box 611, in response to transmitting a timing advance command or a DL MAC PDU, the DU starts or restarts the CG timer to manage the CG configuration. At box 612, the DU (attempts) to receive PUSCH transmissions from the UE according to the CG configuration. After box 612, the process proceeds to box 614 and / or box 618. At box 614, the DU detects expiration of the CG timer. At box 616, in response to detecting expiration of the CG timer, the DU stops attempting to receive or receiving PUSCH transmissions according to the CG configuration. Otherwise, the process proceeds to box 618. At box 618, the DU transmits a timing advance command to the UE. At box 620, the DU restarts the CG timer in response to transmitting the timing advance command to the UE.
[0127] Figure 6C 600A and 600B are similar to the flowchart of the example method 600B. Method 600C starts at box 613, where the DU transmits the CG configuration to the UE via the CU (e.g., events 330, 332, 334, 430, 432, 434, 394, 494, 495). At box 615, in response to transmitting the CG configuration to the CU or thereafter, the DU starts or restarts the CG timer to manage the CG configuration. At box 612, the DU (attempts) to receive PUSCH transmissions from the UE according to the CG configuration. After box 612, the process proceeds to box 614 and / or box 618. At box 614, the DU detects the expiration of the CG timer. At box 616, in response to detecting the expiration of the CG timer, the DU stops attempting to receive or receiving PUSCH transmissions according to the CG configuration. Otherwise, the process proceeds to box 618. At box 618, the DU transmits a timing advance command to the UE. At block 620, the DU restarts the CG timer in response to transmitting a timing advance command to the UE.
[0128] Figure 7The method 700 illustrated may be implemented / performed by a base station (BS) (eg, base station 104) for managing CG-SDT of a UE (eg, UE 102).
[0129] Method 700 begins at box 708, where the BS transmits an RRC release message including a CG configuration to the UE (e.g., events 332, 334, 432, 434, 394, 494, 495). At box 710, in response to or after transmitting the RRC release message, the BS starts or restarts the CG timer to manage the CG configuration. At box 712, the BS (attempts) to receive PUSCH transmissions from the UE according to the CG configuration. After box 712, the process proceeds to box 714 and / or box 718. At box 714, the BS detects expiration of the CG timer. At box 716, the BS releases the CG configuration in response to detecting that the CG timer has expired. Otherwise, the process proceeds to box 718. At box 718, the BS transmits a timing advance command to the UE. At box 720, the BS restarts the CG timer in response to transmitting the timing advance command to the UE.
[0130] Figure 8 The illustrated method 800 may be implemented / performed by a CU (eg, CU 172 or CU-CP 172A) for managing CG-SDT of a UE (eg, UE 102).
[0131] Method 800 starts at block 802, where the CU determines to configure CG-SDT for the UE. At block 804, the CU obtains the CG configuration from the DU in response to the determination to configure CG-SDT for the UE (e.g., events 328, 330, 428, 430, 394, 494, 495). At block 806, the CU transmits an RRC release message including the CG configuration to the UE via the DU (e.g., events 332, 334, 432, 434, 394, 494, 495). At block 808, in response to the determination, the CU determines to release the CG configuration. At block 810, the CU transmits a CU to DU message to the DU to indicate that the DU is to release the CG configuration. At block 812, the CU receives a DU to CU message from the DU in response to the CU to DU message.
[0132] In some implementations, the CU to DU message and the DU to CU message may be a UE context modification request message and a UE context modification confirmation message, respectively. In other implementations, the CU to DU message and the DU to CU message may be a UE context release command message and a UE context release completion message, respectively.
[0133] Fig. 9Illustrated is a method 900 that may be implemented / performed by a DU (eg, DU 174) for managing CG-SDT of a UE (eg, UE 102).
[0134] Method 900 begins at block 902, where the DU transmits a CG configuration to the UE via the CU (e.g., events 330, 430, 394, 494, 495). At block 904, the DU attempts to receive or receives UL data from the UE according to the CG configuration (e.g., events 404, 418, 420). At block 906, the DU receives a CU-to-DU message from the CU to indicate the release of the CG configuration. At block 908, in response to the CU-to-DU message, the DU releases the CG configuration and transmits a DU-to-CU message to the CU.
[0135] Fig.10 Illustrated is a method 1000 that may be implemented / performed by a DU (eg, DU 174) for managing CG-SDT of a UE (eg, UE 102).
[0136] Method 1000 begins at block 1002, where the DU transmits a CG configuration to the UE via the CU (e.g., events 330, 430, 394, 494, 495). At block 1004, the DU attempts to receive or receives UL data from the UE according to the CG configuration (e.g., events 404, 418, 420). At block 1006, the DU determines to release the CG configuration. At block 1008, the DU transmits a DU to CU message to the CU in response to the determination. At block 1010, the DU receives a CU to DU message from the CU when transmitting the DU to CU message.
[0137] In some implementations, the CU may include a cause value indicating the release of the CG configuration in a CU to DU message. In some implementations, the CU to DU message may be a UE context release command message. In some implementations, the DU to CU message may be a UE context release request message.
[0138] In other implementations, the DU to CU message may be a UE context modification required message. In such implementations, the CU may transmit a UE context modification confirmation message to the DU in response to the UE context modification required message.
[0139] In some implementations, the DU releases the CG configuration in response to a CU-to-DU message. In some implementations, the DU stops attempting to receive or receiving PUSCH transmissions according to the CG configuration in response to determining to release the CG configuration or receiving a CU-to-DU message.
[0140] Fig.11The illustrated method 1100 may be implemented / performed by a CU (eg, CU 172 or CU-CP 172A) for managing CG-SDT of a UE (eg, UE 102).
[0141] Method 1100 starts at block 1102, where the CU determines to configure CG-SDT for the UE. At block 1104, in response to the determination, the CU obtains the CG configuration from the DU to configure CG-SDT for the UE (e.g., events 328, 330, 428, 430, 394, 494, 495). At block 1106, the CU transmits an RRC release message including the CG configuration to the UE via the DU (e.g., events 332, 334, 432, 434, 394, 494, 495). At block 1108, the CU receives a CU to DU message from the DU to indicate or request the release of the CG configuration. At block 1110, the CU transmits a CU to DU message to the DU in response to the DU to CU message.
[0142] In some implementations, the DU to CU message may be a UE context modification request message or a UE context release request message. In some implementations, the CU to DU message may be a UE context modification confirmation message or a UE context release command message. In the case of a UE context release command message, in response, the CU receives a UE context release completion message from the DU. In the case where the DU transmits a DU to CU to indicate the release of the CG configuration, the DU may (determine) release the CG configuration without waiting for the CU to DU message. In the case where the DU transmits a DU to CU to request the release of the CG configuration, the DU may release the CG configuration in response to the CU to DU message.
[0143] The following list of examples reflects the various implementations expressly contemplated by the present disclosure:
[0144] Example 1. A method for managing synchronization with a user equipment (UE) implemented by a distributed unit (DU) of a distributed base station, the method comprising: transmitting a configured authorized small data transmission (CG-SDT) configuration to the UE for use by the UE when the UE is in an inactive state; after transmitting the CG-SDT configuration to the UE, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; and while the time alignment timer is running, receiving or attempting to receive transmissions from the UE according to the CG-SDT configuration.
[0145] Example 2. The method of Example 1, further comprising: detecting expiration of a time alignment timer; and in response to the detection, ceasing to receive or attempt to receive transmissions from the UE according to a CG-SDT configuration.
[0146] Example 3. The method of Example 1 or 2, further comprising: transmitting a timing advance command to the UE; and after transmitting the timing advance command, restarting the time alignment timer.
[0147] Example 4. A method as described in any one of Examples 1 to 3, wherein transmitting the CG-SDT to the UE includes: transmitting the CG-SDT to the UE via a central unit (CU) of a distributed base station, and wherein the method further includes: receiving a first CU to DU message from the CU, wherein transmitting the CG-SDT configuration to the UE via the CU includes: transmitting a first DU to CU message including the CG-SDT configuration to the CU in response to the first CU to DU message.
[0148] Example 5. A method as described in Example 4, wherein transmitting a CG-SDT configuration to a UE via a CU includes: transmitting a first DU to CU message including a CG-SDT configuration to the CU in response to a first CU to DU message; receiving a second CU to DU message including a radio resource control (RRC) release message from the CU, the RRC release message including the CG-SDT configuration; and transmitting the RRC release message to the UE.
[0149] Example 6. The method of Example 5, wherein starting or restarting the time alignment timer is in response to the first CU-to-DU message or the second CU-to-DU message.
[0150] Example 7. A method as described in Example 4, wherein transmitting a CG-SDT configuration to a UE via a CU comprises: transmitting a first DU to CU message including the CG-SDT configuration to the CU; receiving a second CU to DU message including a radio resource control (RRC) release message from the CU, the RRC release message including the CG-SDT configuration; and transmitting a downlink (DL) media access control (MAC) protocol data unit (PDU) including the RRC release message and a timing advance command to the UE.
[0151] Example 8. A distributed unit (DU) of a distributed base station, the DU comprising one or more processors and configured to implement the method as described in any one of Examples 1 to 7.
[0152] Example 9. A method for managing synchronization with a user equipment (UE) implemented by a base station, the method comprising: transmitting a radio resource control (RRC) release message to the UE including a configured granted small data transmission (CG-SDT) configuration for use by the UE when the UE is in an inactive state; after transmitting the RRC release message to the UE, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; and while the time alignment timer is running, receiving or attempting to receive transmissions from the UE according to the CG-SDT configuration.
[0153] Example 10. The method of Example 9, further comprising: detecting expiration of a time alignment timer; and in response to the detection, releasing the CG-SDT configuration.
[0154] Example 11. The method of Example 9, further comprising: transmitting a timing advance command to the UE; and after transmitting the timing advance command, restarting the time alignment timer.
[0155] Example 12. The method of any one of Examples 9 to 11, wherein the base station is a distributed base station, and wherein the method is implemented by a distributed unit (DU) of the distributed base station.
[0156] Example 13. The method as described in Example 12 further includes: before transmitting an RRC release message to the UE: receiving a first CU to DU message from a central unit (CU) of a distributed base station; in response to the first CU to DU message, transmitting a first DU to CU message including a CG-SDT configuration to the CU; and receiving a second CU to DU message including an RRC release message from the CU.
[0157] Example 14. The method of Example 13, wherein starting or restarting the time alignment timer is in response to the first CU-to-DU message or the second CU-to-DU message.
[0158] Example 15. The method of Example 13 or 14, wherein transmitting the RRC release message to the UE comprises transmitting a downlink (DL) medium access control (MAC) protocol data unit (PDU) including the RRC release message and the timing advance command to the UE.
[0159] Example 16. A base station comprising one or more processors and configured to implement a method as described in any one of Examples 9 to 15.
[0160] Example 17. A method for managing a configured authorized small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, implemented by a central unit (CU) of a distributed base station, the method comprising: transitioning the UE from a connected state to an inactive state by transmitting a message to the UE via a distributed unit (DU) of the distributed base station; after transitioning the UE, transmitting a CU to DU message to the DU indicating that the DU will release the CG-SDT configuration.
[0161] Example 18. The method of Example 17, further comprising: obtaining a CG-SDT configuration from the DU before the transition.
[0162] Example 19. The method of Example 17 or 18, wherein the message is a radio resource control (RRC) release message including a CG-SDT configuration.
[0163] Example 20. A method as described in any of Examples 17 to 19, wherein the CU to DU message is a UE context modification request message.
[0164] Example 21. The method of Example 20, further comprising: receiving a UE context release complete message from the DU after transmitting the UE context modification request message.
[0165] Example 22. A method for managing a configured authorized small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, implemented by a central unit (CU) of a distributed base station, the method comprising: transitioning the UE from a connected state to an inactive state by transmitting a message to the UE via a distributed unit (DU) of the distributed base station; after transitioning the UE, receiving a DU to CU message from the DU indicating or requesting release of the CG-SDT configuration; and transmitting a CU to DU message to the DU in response to the DU to CU message.
[0166] Example 23. The method of Example 22, further comprising: obtaining a CG-SDT configuration from the DU before the transition.
[0167] Example 24. The method of Example 22 or 23, wherein the message is a radio resource control (RRC) release message including a CG-SDT configuration.
[0168] Example 25. A method as described in any one of Examples 22 to 24, wherein the DU to CU message is a UE context modification required message indicating release of the CG-SDT configuration, and the CU to DU message is a UE context modification confirmation message.
[0169] Example 26. A method as described in any of Examples 22 to 24, wherein the DU to CU message is a request to release the CG-SDT configuration, and the CU to DU message is a response indicating that the DU is to release the CG-SDT configuration.
[0170] Example 27. The method of Example 26, wherein the DU to CU message is a UE context release request message, and the CU to DU message is a UE context release command message.
[0171] Example 28. A central unit (CU) of a distributed base station, the CU comprising one or more processors and configured to implement a method as described in any one of Examples 17 to 27.
[0172] Example 29. A method for managing a configured authorized small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, implemented by a distributed unit (DU) of a distributed base station, the method comprising: transmitting the CG-SDT configuration to the UE; after transmitting the CG-SDT configuration, receiving a CU to DU message from a central unit (CU) of the distributed base station indicating that the DU is to release the CG-SDT configuration; and releasing the CG-SDT configuration in response to the CU to DU message.
[0173] Example 30. A method as described in Example 29, wherein transmitting the CG-SDT configuration to the UE includes: transmitting the CG-SDT configuration to the CU; receiving a radio resource control (RRC) release message including the CG-SDT configuration from the CU; and transmitting the RRC release message to the UE.
[0174] Example 31. The method of Example 30, wherein transmitting the RRC release message to the UE comprises transmitting a medium access control (MAC) protocol data unit (PDU) including the RRC release message.
[0175] Example 32. A method as described in any of Examples 29 to 31, wherein the CU to DU message is a UE context modification request message.
[0176] Example 33. The method of Example 32, further comprising: transmitting a UE context release complete message to the CU in response to the CU to DU message.
[0177] Example 34. A method for managing a configured authorized small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, implemented by a distributed unit (DU) of a distributed base station, the method comprising: transmitting the CG-SDT configuration to the UE; after transmitting the CG-SDT configuration, determining to release the CG-SDT configuration; and in response to the determination, transmitting a DU to CU message to a central unit (CU) of the distributed base station indicating or requesting the release of the CG-SDT configuration.
[0178] Example 35. A method as described in Example 34, wherein transmitting the CG-SDT configuration to the UE includes: transmitting the CG-SDT configuration to the CU; receiving a radio resource control (RRC) release message including the CG-SDT configuration from the CU; and transmitting the RRC release message to the UE.
[0179] Example 36. The method of Example 35, wherein transmitting the RRC release message to the UE comprises transmitting a medium access control (MAC) protocol data unit (PDU) including the RRC release message.
[0180] Example 37. The method as described in any one of Examples 34 to 36 further includes: after transmitting the DU to CU message, receiving a CU to DU message from the CU, wherein the DU to CU message is a UE context modification request message, and the CU to DU message is a UE context modification confirmation message.
[0181] Example 38. The method as described in any one of Examples 34 to 36 further includes: after transmitting the DU to CU message, receiving a CU to DU message from the CU, wherein the DU to CU message is a request to release the CG-SDT configuration, and the CU to DU message is a response indicating that the DU will release the CG-SDT configuration.
[0182] Example 39. The method of Example 38, wherein the DU to CU message is a UE context release request message, and the CU to DU message is a UE context release command message.
[0183] Example 40. A distributed unit (DU) of a distributed base station, the DU comprising one or more processors and configured to implement a method as described in any one of Examples 29 to 39.
[0184] Example 41. A method for managing synchronization with a user equipment (UE) implemented by a central unit (CU) of a distributed base station, the method comprising: transitioning a UE from a connected state to an inactive state by transmitting a message to the UE via a distributed unit (DU) of the distributed base station; and after transitioning the UE, starting a time alignment timer, the time alignment timer indicating the validity of a configured authorized small data transmission (CG-SDT) configuration for use by the UE when the UE is in an inactive state.
[0185] Example 42. The method of Example 41, further comprising: detecting expiration of a time alignment timer; and in response to the detection, transmitting a CU to DU message to the DU to indicate release of the CG-SDT configuration.
[0186] Example 43. The method of Example 41, further comprising: receiving a DU to CU message from the DU after transitioning the UE; and restarting the time alignment timer in response to the DU to CU message.
[0187] Example 44. The method as described in any one of Examples 41 to 43 further includes: obtaining a CG-SDT configuration from the DU before the transition.
[0188] Example 45. A method as described in any of Examples 41 to 44, wherein the message is a radio resource control (RRC) release message including a CG-SDT configuration.
[0189] Example 46. A central unit (CU) of a distributed base station, the CU comprising one or more processors and configured to implement a method as described in any one of Examples 41 to 45.
[0190] The following description can be applied to the above description.
[0191] In general, the description of any one of the above figures may apply to the other in the above figure. In some implementations, "message" is used and "information element (IE)" can be used to replace "message", and vice versa. In some implementations, "IE" is used and "field" can be used to replace "IE", and vice versa. In some implementations, "configuration" or "configuration parameter" can be used to replace "configuration", and vice versa. In some implementations, "early data transmission (EDT)" can be used to replace "small data transmission", and "EDT" can be used to replace "SDT", and vice versa. In some implementations, "small data transmission" can be replaced with "small data communication", and vice versa. In some implementations, "stop" can be replaced with "pause".
[0192] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell, or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0193] 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 particular manner. A hardware module may include a dedicated circuit system (circuitry) 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., as 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.
[0194] 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 synchronization with a user equipment (UE) implemented by a distributed unit (DU) of a distributed base station, the method comprising: transmitting, to the UE, a configuration grant small data transmission (CG-SDT) configuration for use by the UE when the UE is in an inactive state; After transmitting the CG-SDT configuration to the UE, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; as well as While the time alignment timer is running, receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration.
2. The method of claim 1, further comprising: detecting expiration of the time alignment timer; as well as In response to the detection, the receiving or attempting to receive transmissions from the UE according to the CG-SDT configuration is stopped.
3. The method according to claim 1 or 2, further comprising: transmitting a timing advance command to the UE; as well as After transmitting the timing advance command, the time alignment timer is restarted.
4. The method according to any one of claims 1 to 3, wherein transmitting the CG-SDT to the UE comprises: transmitting the CG-SDT to the UE via a central unit (CU) of the distributed base station, and wherein the method further comprises: receiving a first CU to DU message from the CU, Wherein transmitting the CG-SDT configuration to the UE via the CU comprises: in response to the first CU to DU message, transmitting (430) a first DU to CU message including the CG-SDT configuration to the CU.
5. The method of claim 4, wherein transmitting the CG-SDT configuration to the UE via the CU comprises: In response to the first CU-to-DU message, transmitting (430) the first DU-to-CU message including the CG-SDT configuration to the CU; receiving, from the CU, a second CU-to-DU message including a radio resource control (RRC) release message, the RRC release message including the CG-SDT configuration; as well as The RRC release message is transmitted to the UE. 6 . The method of claim 5 , wherein starting or restarting the time alignment timer is in response to the first CU-to-DU message or the second CU-to-DU message.
7. The method of claim 4, wherein transmitting the CG-SDT configuration to the UE via the CU comprises: transmitting the first DU to CU message including the CG-SDT configuration to the CU; receiving, from the CU, a second CU-to-DU message including a radio resource control (RRC) release message, the RRC release message including the CG-SDT configuration; as well as A downlink (DL) medium access control (MAC) protocol data unit (PDU) including the RRC release message and a timing advance command is transmitted to the UE.
8. A method implemented by a distributed unit (DU) of a distributed base station for managing a configuration-granted small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, the method comprising: transmitting the CG-SDT configuration to the UE; After transmitting the CG-SDT configuration, receiving a CU-to-DU message from a central unit (CU) of the distributed base station indicating that the DU is to release the CG-SDT configuration; and In response to the CU to DU message, the CG-SDT configuration is released.
9. A method implemented by a distributed unit (DU) of a distributed base station for managing a configuration-granted small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, the method comprising: transmitting the CG-SDT configuration to the UE; After transmitting the CG-SDT configuration, determining to release the CG-SDT configuration; as well as In response to the determination, a DU to CU message is transmitted to a central unit (CU) of the distributed base station indicating or requesting release of the CG-SDT configuration.
10. A distributed unit (DU) of a distributed base station, the DU comprising one or more processors and configured to implement the method according to any one of claims 1 to 9.
11. A method implemented by a base station for managing synchronization with a user equipment (UE), the method comprising: transmitting, to the UE, a radio resource control (RRC) release message including a configuration grant small data transmission (CG-SDT) configuration for use by the UE when the UE is in an inactive state; After transmitting the RRC release message to the UE, starting or restarting a time alignment timer indicating the validity of the CG-SDT configuration; as well as While the time alignment timer is running, receiving or attempting to receive a transmission from the UE according to the CG-SDT configuration.
12. A base station comprising one or more processors and configured to implement the method of claim 11.
13. A method implemented by a central unit (CU) of a distributed base station for managing a configured grant small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, the method comprising: transitioning the UE from a connected state to the inactive state by transmitting a message to the UE via a distributed unit (DU) of the distributed base station; After the UE is transitioned, a CU-to-DU message is transmitted to the DU indicating that the DU is to release the CG-SDT configuration.
14. A method implemented by a central unit (CU) of a distributed base station for managing a configuration-granted small data transmission (CG-SDT) configuration for use by a user equipment (UE) when the UE is in an inactive state, the method comprising: transitioning the UE from a connected state to the inactive state by transmitting a message to the UE via a distributed unit (DU) of the distributed base station; After transitioning the UE, receiving a DU to CU message from the DU indicating or requesting release of the CG-SDT configuration; and In response to the DU to CU message, a CU to DU message is transmitted to the DU.
15. A central unit (CU) of a distributed base station, the CU comprising one or more processors and configured to implement the method according to claim 13 or 14.
