Managing small data transmissions with configuration authorization configurations
By resetting the MAC entity and maintaining the CG-SDT timer after receiving the RRC release message by the user equipment (UE), the problem of data communication delay and inefficiency caused by improper management of CG-SDT timer is solved, and wireless communication is improved efficiency.
Patent Information
- Application Number
- CN202380030492.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-08-09
- Filing Date
- 2023-02-08
- Publication Date
- 2024-11-12
AI Technical Summary
Prior art When managing uplink and downlink data communications of user equipment (UE) in the radio access network (RAN) in an inactive or idle state, it is difficult to effectively manage the CG-SDT timer, resulting in delay in data communication. and network inefficiency.
After receiving the RRC release message, the UE resets the Media Access Control (MAC) entity and starts or maintains the CG-SDT timer after reset to avoid its premature stop or reset, ensuring that it continues to execute in an inactive state. Data communication.
It effectively avoids premature stop or reset of the CG-SDT timer, improves the timeliness of data communication and network efficiency, and reduces delay.
Smart Images

Figure CN118947215A_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 specifies: 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 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 less than the configured amount of uplink data is waiting to be transmitted on all radio bearers for which SDT is enabled, the downlink (DL) reference signal received power (RSRP) is above the configured threshold and valid SDT resources are available. The SDT process can be initiated by the UE through a transmission on a random access channel (RACH) (i.e., random access SDT (RA-SDT)) or a type 1 configuration grant (CG) resource (i.e., CG-SDT). For RA-SDT, the network configures 2-step and / or 4-step random access resources for SDT. In RA-SDT, the UE can transmit an initial transmission including data in message 3 (MSG3) of a 4-step random access process or in the payload of message A (MSGA) of a 2-step random access process. After completing the random access process, the network can then schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.
[0006] CG-SDT can only be initiated if there is valid uplink (UL) timing alignment. The UE maintains UL timing alignment based on the network-configured SDT-specific timing alignment timer and the configured number of DL RSRPs of the highest-ranked SSBs. 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 may use dynamic grants or schedule subsequent UL transmissions on future CG resource opportunities. During CG-SDT, DL transmissions are scheduled using dynamic assignments. The UE may initiate subsequent UL transmissions only after receiving confirmation of the initial UL transmission from the network.
[0007] However, it is unclear how to manage UL synchronization for CG-SDT. Failure to properly manage UL synchronization may result in data communication delays and / or other network inefficiencies, such as due to premature expiration of the CG-SDT timer. Summary of the invention
[0008] According to certain techniques of the present disclosure, the UE can ensure that the CG-SDT timer is not stopped or reset prematurely. In some implementations and scenarios, when the UE receives an RRC release message (e.g., including a CG-SDT configuration associated with the CG-SDT timer) from a base station of the RAN, the UE responds by resetting the UE's media access control (MAC) entity, and then starting the CG-SDT timer after resetting the MAC entity. The RRC release message can also cause the UE to transition to an inactive state (if the UE is in a connected state when the RRC release message is received), or the UE can maintain an inactive state (if the UE is already in an inactive state when the RRC release message is received).
[0009] In other implementations, the UE starts the CG-SDT timer (and transitions to an inactive state, if not already in an inactive state) in response to the RRC release message, and resets the MAC entity, but avoids stopping the CG-SDT timer when resetting the MAC entity. In some of these implementations, the UE resets the MAC entity (without stopping the CG-SDT timer) in response to the RRC release message. In other of these implementations, and in certain scenarios, while the CG-SDT timer is running and the UE is in an inactive state, the UE determines to perform a CG-SDT with the base station using a CG-SDT configuration. The UE may then reset the MAC entity (without stopping the CG-SDT timer) in response to this determination.
[0010] In some implementations and scenarios, while the UE is in an inactive state and the CG-SDT timer is running, the UE may perform a random access procedure with the RAN, for example as a mechanism for requesting on-demand system information from the RAN. In these implementations and scenarios, if the UE receives a random access response from the RAN that includes a timing advance command, the UE may avoid restarting the CG-SDT timer despite having received the timing advance command. In some implementations, the UE avoids restarting the CG-SDT timer upon receiving a timing advance command only if the UE has initiated or performed a random access procedure for the specific purpose of requesting on-demand system information.
[0011] In some implementations and scenarios where the UE receives a timing advance command while the UE is in an inactive state and a CG-SDT timer is running, the UE starts or restarts a non-CG-SDT timer upon receiving the timing advance command. However, upon detecting expiration of a non-CG-SDT timer, the UE maintains the running CG-SDT timer instead of stopping or resetting the CG-SDT timer.
[0012] As used herein, “CG-SDT timer” may specifically refer to a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration, and “non-CG-SDT timer” may specifically refer to a non-CG-SDT time alignment timer indicating the validity of a non-CG-SDT configuration.
[0013] In one example, a method implemented by a UE to manage a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration includes: receiving a radio resource control (RRC) release message from a radio access network (RAN); and in response to the RRC release message, (i) resetting a media access control (MAC) entity of the UE, and (ii) starting the CG-SDT time alignment timer after resetting the MAC entity.
[0014] In another example, a method implemented by a UE to manage a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration includes: starting the CG-SDT time alignment timer; receiving a timing advance command from a radio access network (RAN) when the UE is in an inactive state and the CG-SDT time alignment timer is running; and avoiding restarting the CG-SDT time alignment timer when the timing advance command is received.
[0015] In another example, a method implemented by a UE to manage a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration includes: starting the CG-SDT time alignment timer; while the UE is in an inactive state and the CG-SDT time alignment timer is running, performing a random access procedure with a radio access network (RAN), wherein the execution includes sending a random access message to the RAN; receiving a random access response message from the RAN, the random access response message including a timing advance command; in response to receiving the timing advance command, starting or restarting a non-CG-SDT time alignment timer; and avoiding stopping or restarting the CG-SDT time alignment timer when the non-CG-SDT time alignment timer expires. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] 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);
[0017] Figure 1B The centralized unit (CU) and the distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.
[0018] Figure 2A yes Figure 1AA block diagram of an example protocol stack according to which a UE communicates with a base station;
[0019] 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;
[0020] Figures 3 to 5B is an example of Figures 1A to 2B A message sequence diagram of several scenarios of small data transmission according to the technology of the present disclosure can be implemented by the device; and
[0021] Figure 6 to Fig.10 The example can be Figures 1A to 2B Several methods implemented by one or more devices in for managing small data transmission according to the techniques of this disclosure. DETAILED DESCRIPTION
[0022] 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, small data communications may refer to small data transmission (SDT) from a network perspective (i.e., SDT in a downlink direction), or SDT from a UE perspective (i.e., SDT in an uplink direction).
[0023] 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.
[0024] 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).
[0025] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. Generally speaking, the SGW 112 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally speaking, the UPF 162 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions.
[0026] 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.
[0027] 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.
[0028] 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" can refer to a complete configuration, or to a subset of the parameters of a complete configuration (e.g., an "incremental" or other partial configuration that can augment an existing configuration without completely replacing the existing configuration).
[0029] 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 along with the first UL PDU in a second 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).
[0030] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 may generate a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 may encrypt data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 may transmit the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.
[0031] In some implementations, the data is a UL service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (e.g., a UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which may be associated with a media access control (MAC) layer. Therefore, in these cases, the UE 102 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 including 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).
[0032] 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 5G, an 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.
[0033] 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.
[0034] 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.
[0035] 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 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.
[0036] In another implementation, the base station 106 retrieves the security-protected packet from the first UL PDU and performs a UE context retrieval process 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 the 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.
[0037] 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.
[0038] 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.
[0039] For example, when the base station 104 determines that data is available for downlink transmission to a UE 102 currently operating in an RRC_INACTIVE or RRC_IDLE state, the base station 104 may apply at least one security function to the data to generate a security-protected packet, generate a first DL PDU including the security-protected packet, and include the first DL PDU in a second DL PDU. In order to protect the data, the base station 104 may apply a security function (e.g., integrity protection and / or encryption) to the DL data. More specifically, 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 an RRC_INACTIVE or RRC_IDLE state to an RRC_CONNECTED state. In some implementations, the base station 104 includes the DL PDCP PDU in a DL RLC PDU, includes the DL RLC PDU in a DL MAC PDU, and transmits the DL MAC PDU to the UE 102 without first causing the UE 102 to transition from an RRC_INACTIVE or RRC_IDLE state to an RRC_CONNECTED state.
[0040] 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.
[0041] 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).
[0042] 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.
[0043] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a MAC controller 132, which is configured to perform a random access process with one or more user devices, receive UL MAC protocol data units (PDUs) from one or more user devices, and transmit DL MAC PDUs to one or more user devices. 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. Specifically, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to components 130, 132, 134, 136, and 138, respectively.
[0044] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. In an example implementation, the processing hardware 150 includes an RRC inactive controller 158, which is configured to manage uplink and / or downlink communications when UE 102 operates in an RRC_INACTIVE state. In an example implementation, the processing hardware 150 includes a MAC controller 152, which is configured to perform a random access procedure with a base station, 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 processes and message delivery at the RRC sublayer of the protocol communication stack.
[0045] Figure 1BAn example distributed or decomposed implementation of one or both of the base stations 104, 106 is depicted. In this implementation, the base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DUs) 174. The CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processors, and / or a dedicated processing unit. For example, the CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as the PDCP controllers 134, 144, the RRC controllers 136, 146, and / or the RRC inactive controllers 138, 148. In some implementations, the CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, the CU 172 does not include an RLC controller.
[0046] 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 a dedicated processing unit. 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.
[0047] 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.
[0048] 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., SDAP PDUs or Internet Protocol packets).
[0049] 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.
[0050] 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 or gNB (e.g., one or both of base stations 104, 106).
[0051] 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 sublayer 212 or the RRC sublayer ( Figure 2A In some implementations, UE 102 may provide data transfer services. Figure 2A As shown, both EUTRA and NR stacks are supported to support handover between EUTRA and NR base stations and / or to support DC over 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.
[0052] 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.
[0053] 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.
[0054] 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 provides SRBs to the RRC 214.
[0055] Next, refer to Figures 3 to 5B To discuss the 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.
[0056] First reference Figure 3In the scenario 300, the base station 104 includes a CU 172 and a DU 174, and the CU 172 includes a CU-CP 172A and a CU-UP 172B. In this scenario 300, the UE 102 initially operates in a connected state 302, and communicates 304 with the DU 174, for example, by using a DU configuration (i.e., a first non-SDT configuration), and communicates 304 with the CU-CP 172A and / or CU-UP 172B via the DU by using a CU configuration (i.e., a first non-SDT CU configuration). While the UE is communicating 304 with the base station 104, the CU-CP 172A may send 306 a UE context modification request message. In response, the DU 174 sends 308 to the CU-CP 172A a UE context modification response message including a non-SDT configuration for the UE 102 (i.e., a second non-SDT configuration). The CU-CP 172A generates an RRC reconfiguration message including the first 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 the DU 174. In turn, the DU 174 transmits 312 the RRC reconfiguration message to the UE 102. In response, the UE 102 transmits 314 an RRC reconfiguration complete message to the 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 the CU-CP 172A.
[0057] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the first 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 and 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 RadoBearerConfig 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 RadoBearerConfig 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 RadoBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadoBearerConfig IE and / or a MeasConfig IE.
[0058] 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 includes configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration may be CellGroupConfig IEs.
[0059] Events 306, 308, 310, 312, 314, 316, and 318 are Figure 3 The non-SDT resource (re)configuration process 390 is collectively referred to as the non-SDT resource (re)configuration process, which may be optional.
[0060] While the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration process 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., based on the UE 102 in the connected state not having data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration process 390 (if performed), the UE 102 determines or detects data inactivity and transmits 320 UE assistance information (e.g., UEAssistanceInformation message) to the DU 174, the UE assistance information indicating that the UE 102 prefers or requests to transition to the inactive state configured with SDT. Then, the DU 174 transmits 321 a UL RRC messaging message including the UE assistance information to the CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may 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.
[0061] After a specific period of data inactivity, CU-CP 172A may determine that CU 172 (i.e., CU-CP 172A and / or CU-UP 172B) or UE 102 did not transmit 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, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured in response to determining that UE 102 is in data inactivity.
[0062] 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 instruct the DU 174 to provide an SDT DU configuration for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., an IE, such as a CG-SDT Query Indication IE) for requesting an 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, 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 after receiving the second CU-to-DU message or transmitting the second DU-to-CU 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 response to the additional CU-to-DU message. In some alternative implementations, CU-CP 172A may transmit a second CU to DU message and receive a second DU to CU message or additional DU to CU messages 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.
[0063] 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., RRCRelease message, RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include the SDT DU configuration (if obtained from DU 174) and / or the SDT CU configuration in the RRC release message. Then, CU-CP 172A sends 332 a third CU-to-DU message (e.g., a UE context release command message, a UE context modification request message, or a DL RRC messaging message) including the RRC release message to DU 174. Subsequently, DU 174 transmits 334 the RRC release message to UE 102. In some implementations, DU 174 generates a MAC PDU including the RRC release message and transmits 334 the MAC PDU to UE 102. The RRC release message instructs 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. DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A in response to the third CU-to-DU message.
[0064] UE 102 uses C-RNTI to monitor PDCCH to receive DCI when operating 302 in connected state. In response to receiving 334 to RRC release message or thereafter, UE 102 stops using C-RNTI to monitor PDCCH. In some implementations, UE 102 may retain C-RNTI in response to receiving 334 to RRC release message or transitioning 336 from connected state to inactive state or thereafter. In some implementations, UE 102 performs a two-step or four-step random access procedure with base station 104 (e.g., CU-CP 172A and / or DU 174) and receives a random access response message including C-RNTI from DU 174 during the random access procedure. In other implementations, UE 102 receives a random access response message from CU-CP 172A or from DU 174 via 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.
[0065] Events 320 (optional), 321 (optional), 322 (optional), 323, 324, 326, 328, 330, 332, and 334 are Figure 3 Collectively referred to as the SDT configuration process 394.
[0066] In some implementations, 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 response to the RRC release message. In other implementations, if the RRC release message instructs the UE 102 to transition to an inactive state (i.e., RRC_IDLE), the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT configuration. In still other implementations, if the RRC release message instructs the UE to transition to an inactive state (i.e., RRC_INACTIVE), the UE 102 releases the first 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.
[0067] In some implementations, CU-CP 172A does not include an indication for instructing 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 for instructing DU 174 to retain the SDT DU configuration in a third CU to DU message (e.g., a UE context release command message), and DU 174 retains the SDT DU configuration in response to the indication. If the UE context release command message excludes the indication, DU 174 releases the SDT DU configuration. In yet other implementations, CU-CP 172A does not include an indication for instructing DU 174 to release the SDT DU configuration in a third CU to DU message (e.g., a UE context modification request message or a DL RRC messaging message) for UE 102. Therefore, DU 174 retains the SDT DU configuration in response to the third CU to DU message excluding the indication. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.
[0068] 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”.
[0069] 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.
[0070] 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 CU172, 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 the DU CG-SDT timer using a timer value to manage the CG-SDT configuration. In some implementations, the timer value is the same as the CG-SDT time alignment timer value. In other implementations, the timer value is close to the CG-SDT time alignment timer value. For example, the timer value may be greater than and close to the CG-SDT time alignment timer value. In another example, the timer value may be less than and close to the CG-SDT time alignment timer value. Only when the DU CG-SDT timer expires does DU 174 release the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 avoids receiving PUSCH transmissions from UE 102 on 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.
[0071] 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 using a CG-SDT time alignment timer value. The UE 102 releases the CG-SDT configuration only when the CG-SDT timer expires. 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.
[0072] In some implementations, DU 174 reserves the radio resources configured in the configuration grant configuration. In some implementations, DU 174 releases the radio resources when releasing the SDT DU configuration or the CG-SDT configuration. In the case where DU 174 does not provide the CG-SDT configuration or the SDT DU configuration to CU-CP 172A, DU 174 releases all signaling and user data transmission resources for UE 102 in response to the third CU to DU message. In the case where DU 174 provides the SDT DU configuration or the CG-SDT configuration to CU-CP 172A, DU 174 reserves the signaling and user data transmission resources for UE 102 in response to receiving the third CU to DU message or thereafter.
[0073] 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.
[0074] 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 first SDT DU configuration in the RRC release message.
[0075] 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-CP172A 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.
[0076] 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 can determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, CU-CP 172A may receive a DU-to-CU message from DU 174 indicating whether DU 174 supports CG-SDT. The DU-to-CU message may be a second DU-to-CU message, a message of event 308 or 316, or a non-UE-associated message (e.g., a non-UE-associated F1AP message defined in 3GPP specification 38.473).
[0077] In some implementations, DU 174 may determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether UE 102 supports CG-SDT. In addition to whether UE 102 supports CG-SDT, DU 174 may additionally determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether DU 174 supports CG-SDT. In the case that UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, DU 174 provides the first SDT DU configuration for UE 102 to CU-CP 172A, as described above. In the case that UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, DU 174 does not provide the SDT DU configuration for UE 102 (e.g., DU 174 does not include the SDT DU configuration in the second DU to CU message). 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.
[0078] 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.
[0079] Later, the UE 102 operating in an inactive state configured with SDT initiates an SDT. In response to or after initiating the SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message, and transmits 404 the initial UL MAC PDU to the DU 174 on the cell 124. The UE 102 may start an SDT session timer in response to initiating the SDT. In some implementations, the SDT session timer may be a new timer defined in the RRC specification (e.g., v17.0.0). The DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends 406 the first DU to CU message to the CU-CP 172A. In some implementations, the first DU to CU message may be an initial UL RRC messaging message. In other implementations, the first DU to CU message may be a UL RRC messaging message.
[0080] 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 to indicate to the base station 104 that the UE 102 is initiating an SDT to receive DL data in an initial UL MAC PDU or UL RRC message.
[0081] 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 a 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. UE 102 may receive message B (MsgB) including a temporary C-RNTI and a timing advance command from DU 174 in response to MsgA. 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.
[0082] When UE 102 successfully resolves contention during the random access procedure, UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3418 UL data from DU 174. 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 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.
[0083] 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.
[0084] 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.
[0085] If UE 102 includes UL data in the initial UL MAC PDU, DU 174 retrieves the UL data from the initial UL MAC PDU. In such a case, DU 174 may include the UL data in the DU to CU message of event 406. Alternatively, DU 174 may send 415 a DU to CU message including UL data to CU-CP 172A. In this alternative, the UL data may include or be a PDCP PDU, an RRC PDU, a NAS PDU, or an LTE Positioning Protocol (LPP) PDU. The PDCP PDU may include an RRCPDU. As yet another alternative, DU 174 may send 416 UL data to CU-UP 172B separately via a user plane (UP) connection as described below. In this alternative, the UL data may include or be a PDCP PDU, and the PDCP PDU may include an SDAP PDU, an IP packet, or an Ethernet packet.
[0086] 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 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, the CU-CP 172A transmits 412 a bearer context modification request message to the CU-UP 172B to resume data transmission for the UE 102. In response, CU-UP 172B resumes data transmission for 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 event that 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 the UL data to CU-CP 172A. In the event that the UL data is associated with a DRB, DU 174 may transmit 416 the UL data to CU-UP 172B.
[0087] 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 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 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 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.
[0088] 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 use the transport layer information of DU 174 to transmit 418 DL data (e.g., one or more DL data packets) to DU 174. Then, DU 174 transmits 418 one or more DL MAC PDUs including DL data to UE 102 operating in an inactive state.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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 an existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message may include an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.
[0093] 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 an 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 an inactive state determines or detects data inactivity and transmits 420 UE assistance information (e.g., a UEAssistanceInformation message) indicating that the UE 102 prefers or requests to stop the SDT to the DU 174. Subsequently, the DU 174 transmits 421 a UL RRC messaging message including the UE assistance information to the CU-CP 172A. Therefore, the CU-CP 172A may determine that the UE 102 is in data inactivity based on the UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may 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 (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 .
[0094] 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, CU-CP 172A may determine to immediately stop SDT of UE 102 in response to determining that UE 102 is in data inactivity.
[0095] 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 SDT DU configuration (e.g., a second SDT DU configuration) for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., a field or IE) for requesting an SDT DU configuration in the 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, 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 after receiving the second CU-to-DU message or transmitting the second DU-to-CU message. 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.
[0096] 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., RRCRelease message, RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include the second SDT DU configuration (if obtained from DU 174) and the second SDT CU configuration in the RRC release message.
[0097] 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 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.
[0098] Then, the CU-CP 172A sends 432 a third CU-to-DU message including an RRC release message to the DU 174. Subsequently, 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 334 the MAC PDU to the UE 102. The RRC release message instructs the UE 102 to transition to an inactive state. Upon receiving 434 the RRC release message, the UE 102 stops the SDT and remains 436 in the inactive state.
[0099] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 are collectively referred to as SDT completion process 494.
[0100] 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.
[0101] In some implementations, the second SDT CU configuration may be the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration may be different from the first SDT CU configuration. The UE 102 may update (e.g., replace or modify) the first SDT CU configuration using the second SDT CU configuration. In some implementations, the CU-CP 172A may include an indication in the RRC release message indicating that the UE 102 is about 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 indicating that the UE 102 is about 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, the CU-CP 172A may include a setup indication in the RRC release message indicating that the UE 102 is to replace the first SDT CU configuration with the second SDT CU configuration. In such implementations, the UE 102 may replace the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.
[0102] 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 DU configuration. In such implementations, the UE 102 may update the first SDT DU configuration using the second SDT DU configuration in response to the indication. In other implementations, the DU 174 may include in the second SDT DU configuration a modification indication 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 indicating that the UE 102 is to replace the first SDT DU configuration with the second SDT DU configuration. In such implementations, the UE 102 may replace the first SDT DU configuration with the second SDT DU configuration in response to the setup indication.
[0103] 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 is to release the previously received SDT DU configuration and / or SDT CU configuration. In the case where the CU-CP 172A includes the release indication in the RRC release message, the UE 102 releases the first SDT CU configuration and / or the first SDT DU configuration in response to the release indication.
[0104] 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.
[0105] 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. DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A in response to the third CU-to-DU message. In some implementations, if the RRC release message instructs UE 102 to transition to an inactive state (i.e., RRC_IDLE), UE 102 releases the non-SDT configuration (e.g., for 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 / or SDT CU configuration described above).
[0106] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 492. The SDT completion process is collectively referred to as SDT completion process 494, which is similar to 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 SDT, UE 102 can perform 493 another SDT process with base station 104, which is similar to process 492. After completing process 493, base station 104 can perform 495 an SDT completion process with UE 102, which is similar to process 494.
[0107] In some implementations, CU-CP 172A may not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state configured with SDT. In such cases, events 428 and 430 may be omitted. In such cases, CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own and include the SDT DU configuration in the RRC release message.
[0108] 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.
[0109] In some implementations, in the case where UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A may request DU 174 to provide SDT DU configuration, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. Before UE 102 initiates SDT when UE is operating in inactive state 402, when UE performs SDT (e.g., in UE context setup request message of event 408 or 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 defined in 3GPP specification 38.473).
[0110] In some implementations, DU 174 may determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether UE 102 supports CG-SDT. In addition to whether UE 102 supports CG-SDT, DU 174 may additionally determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether DU 174 supports CG-SDT. In the event that UE 102 supports CG-SDT and / or DU 174 supports or enables CG-SDT, DU 174 provides the SDT DU configuration for UE 102 to CU-CP 172A, as described above. In the event that UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, DU 174 does not provide the SDT DU configuration for UE 102 (e.g., DU 174 does not include the SDT DU configuration in the second DU to CU message). For example, when UE 102 is operating in a connected state or in an inactive state, DU 174 may receive UE capabilities from CU-CP 172A. 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.
[0111] Reference now Figure 5A , scenario 500A depicts a small data transmission and a transition from SDT to non-SDT. In scenario 500A, base station 104 includes CU 172 and DU 174, CU 172 includes CU-CP 172A and CU-UP 172B, and UE 102 initially operates 502 in an inactive state configured with SDT (which is similar to event 402). Then, UE 102 performs 592 a small data transmission process with base station 104, which is similar to event 492.
[0112] During the small data transmission process 592, the CU-CP 172A may determine whether to transition the UE 102 to a connected state, for example, based on the UL or DL data activity of the UE 102. In some implementations, the UE 102 may transmit 503 a non-SDT indication message to the DU 174 for indicating that UL data is available or requesting a transition to a connected state. In some implementations, the UE 102 may transmit 503 a non-SDT indication message to the DU 174 on the radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 may use the C-RNTI to receive an uplink grant on the PDCCH from the DU 174, and transmit 503 a non-SDT indication message to the DU 174 on the radio resources configured in the uplink grant. Then, the DU 174 transmits 505 a UL RRC messaging message including a non-SDT indication message to the CU-CP 172A. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a non-SDT indication message. In other implementations, CU-UP 172B receives DL data from CN 110, and in response, transmits 507 to CU-CP 172A a DL data notification (e.g., a DL data notification message) indicating that DL data is available for transmission. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A may determine to transition UE 102 to a connected state based on a measurement result received from UE 102. In yet other implementations, CU-CP 172A receives DL data (e.g., a NAS message) from CN 110, and in response, may determine to transition UE 102 to a connected state.
[0113] In some implementations, the non-SDT indication message may be an RRC message (eg, a UEAssistanceInformation message or a new RRC message).
[0114] In some implementations, UL data and / or DL data are associated with a radio bearer (e.g., SRB and / or DRB). For example, the UL data may include an RRC message or a NAS message associated with the SRB. In another example, the UL data includes an IP packet associated with the DRB. In some implementations, the UE 102 may include the ID of the radio bearer in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the ID. For example, if the radio bearer identified by the ID is not eligible for SDT, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In some implementations, the UE 102 may include data volume information of the UL data in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the data volume information. In one implementation, the data volume information includes the total data volume of the UL data, which can be quantized or rounded to a value that can be indicated in the data volume information. In another implementation, the data volume information includes the data volume of each radio bearer in the radio bearer, which can be quantized or rounded to a value that can be indicated in the data volume information. For example, if the total data volume is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In another example, if the data volume of a particular radio bearer is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In yet another example, if the total data volume is higher than a predetermined threshold and the data volume of a particular radio bearer is higher than another predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to the connected state.
[0115] In response to or after determining to transition UE 102 to a connected state, CU-CP 172A transmits 506 a UE context request message (e.g., a UE context setup request message or a UE context modification request message) to DU 174. In response, DU 174 transmits 508 a UE context response message (e.g., a UE context setup response message or a UE context modification response message) to CU-CP 172A. In some implementations, DU 174 may include a non-SDT DU configuration (i.e., a first non-SDT DU configuration) in the UE context response message. After receiving the UE context response message, CU-CP 172A transmits 510 a CU-to-DU message including an RRC resume message (e.g., an RRCResume message or an RRCConnectionResume message) to DU 174. Then, DU 174 transmits 512 an RRC resume message to UE 102. In some implementations, DU 174 may transmit 512 one or more PDUs including an RRC resume message to UE 102. The PDU may be a MAC PDU or an RLC PDU. In some implementations, the CU to DU message may be a DL RRC messaging message or a UE context modification request message. In the case of a UE context modification request message, in response, DU 174 may transmit a UE context modification response message to CU-CP 172A. In response to the RRC resume message, UE 102 transitions 513 to a connected state and transmits 514 an RRC resume completion message (e.g., an RRCResumeComplete message or an RRCConnectionResumeComplete message) to DU 174. In the case where the UE context response message includes a non-SDT DU configuration, CU-CP 172A includes the non-SDT DU configuration in the RRC resume message. DU 174 transmits 516 a DU to CU message including an RRC resume completion message to CU-CP 172A. After determining to transition the UE 102 to the connected state, the CU-CP 172A may transmit 517 a bearer context request message (e.g., a bearer context setup request message or a bearer context modification request message) to the CU-UP 172B to instruct the CU-UP 172B to resume all suspended radio bearers of the UE 102. In response, the CU-UP 172B resumes all suspended radio bearers of the UE 102 and transmits 519 a bearer context response message (e.g., a bearer context setup response message or a bearer context modification response message) to the CU-CP-172A.In some implementations, the CU-CP 172A may transmit 517 a bearer context request message after transmitting 506 a UE context request message, receiving 508 a UE context response message, transmitting 510 a CU to DU message, or receiving 516 a DU to CU message.
[0116] In some implementations, CU-CP 172A may include an indication indicating that DU 174 generates a non-SDT configuration in a UE context request message, and DU 174 includes the first non-SDT DU configuration in a UE context response message in response to the indication. In yet other implementations, CU-CP 172A stores a non-SDT DU configuration (i.e., a second non-SDT DU configuration) used by a DU (e.g., DU 174 or another DU or base station) to communicate with UE 102. UE 102 may also store a second non-SDTDU configuration. In such cases, CU-CP 172A includes the second non-SDT DU configuration in a UE context request message, and DU 174 may include the first non-SDT DU configuration in a UE context response message in response to receiving the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration augments or replaces the second non-SDT DU configuration. Examples and implementations of the first non-SDT DU configuration and the second non-SDT DU configuration may be the same as those of the non-SDT DU configuration described above. In some implementations, DU 174 may transmit an additional DU-to-CU message (e.g., a UE context modification required message) including the first non-SDT DU configuration to CU-CP 172A instead of including the first non-SDT DU configuration in the UE context response message.
[0117] After transitioning to the connected state, the UE 102 communicates 518 UL data and / or DL data with the CU-CP 172A and / or CU-UP 172B via the DU 174. The UL data may include UL data that triggers the UE 102 to transmit a non-SDT indication message. The UL data may also include new UL data that may be used for transmission. The DL data may include DL data received from the CN 110 as described above. The DL data may also include new DL data received from the CN 110. In the case where the RRC recovery message includes the first non-SDT DU configuration, the UE 102 uses the first non-SDT DU configuration to communicate 518 with the DU 174. In the case where the second non-SDT DU configuration is not completely replaced by the first non-SDT DU configuration (i.e., the UE 102 does not release the second non-SDT DU configuration in response to the RRC recovery message), the UE 102 may use the configuration parameters in the second non-SDT DU configuration that are not extended by the first non-SDT DU configuration to communicate 518 with the DU 174.
[0118] In some implementations, DU 174 may not provide the first non-SDT DU configuration to CU-CP 172A in the UE context response message and the attach DU to CU message. In such a case, the RRC resume message does not include the first non-SDT configuration, and UE 102 and DU 174 communicate 518 with each other using the second non-SDT DU configuration.
[0119] In some implementations, the UE 102 releases the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration) in response to an RRC recovery message or transitioning to a connected state. In some implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to transitioning the UE 102 to a connected state, receiving 510 to a CU to DU message, or transmitting 510, 512 an RRC recovery message, or thereafter. In other implementations, the base station 104 releases the SDT configuration in response to receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for a PDU including an RRC recovery message, or thereafter. In yet other implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to communicating 506 a UE context request message or communicating 508 a UE context response message, or thereafter.
[0120] In other implementations, in response to receiving an RRC recovery message or transitioning to a connected state or thereafter, the UE 102 retains the SDT configuration (e.g., an SDT CU configuration, an SDT DU configuration, and / or a CG-SDT configuration). In some implementations, when operating in a connected state, the UE 102 avoids using the SDT configuration to communicate with the base station 104 (e.g., transmitting 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, when operating in a connected state, the UE 102 may use the SDT configuration to communicate with the base station 104 (e.g., 514 an RRC recovery complete message and / or 518 data). In some implementations, in response to transitioning the UE 102 to a connected state or transmitting an RRC recovery message or thereafter, the base station 104 retains the SDT configuration. In some implementations, the base station 104 avoids using the SDT configuration to communicate with the UE 102 operating in a connected state (e.g., receiving 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, the base station 104 may use the SDT configuration to communicate with the UE 102 operating in the connected state (e.g., receive 514 an RRC recovery complete message and / or communicate 518 data).
[0121] Later, the base station 104 may perform a non-SDT configuration process 590 and an SDT configuration process 594 with the UE 102, which are similar to the process 390 and the process 394, respectively. The UE 102 transitions 536 to an inactive state in response to receiving the RRC release message in the process 594. The base station 104 may then perform an SDT data transmission process 593 and an SDT completion process 595 with the UE 102, which are similar to the process 492 and the process 494, respectively.
[0122] Next reference Figure 5B , scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC connection recovery procedure instead of a small data communication procedure 592. The differences between scenarios 500B and 500A are discussed below.
[0123] In response to initiating the RRC connection recovery process, the UE 102 in the inactive state transmits 542 an RRC recovery request message to the DU 174, which in turn transmits 544 an initial UL RRC messaging message including an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCConnectionResumeRequest message) to the CU-CP 172A. In response to receiving the RRC recovery request message, the CU-CP 172A determines to transition the UE 102 to the connected state. In response to or after determining to transition the UE 102 to the connected state, the CU-CP 172A transitions the UE 102 to the connected state as described for scenario 500A.
[0124] In some implementations, the UE 102 may generate a UL MAC PDU including the RRC recovery request message and transmit 542 the UL MAC PDU to the DU 174. In some implementations, the UE 102 may transmit 542 the UL MAC PDU to the DU 174 on the radio resources configured in the CG configuration for the SDT. In other implementations, the UE 102 may perform a random access procedure to transmit the UL MAC PDU, similar to event 404.
[0125] Next, refer to FIG. 6A to FIG. 10 Several example methods that may be implemented in one or more UEs to support data communication in an inactive state are discussed.
[0126] Fig. 6A A method 600A is illustrated that may be implemented by a UE (eg, UE 102) for managing small data transmissions using a configuration grant configuration.
[0127] Method 600A begins at box 602, where when operating in a connected state, the UE performs communication with a base station (e.g., base station 104) (e.g., events 302, 304, 310, 312, 314, 316, 318, 320, 321, 332, 334, 513, 514, 516, 518, 590). At box 604, the UE receives an RRC release message configuring CG-SDT from the base station (e.g., events 332, 334, 594). At box 606, in response to the RRC release message, the UE resets the MAC entity of the UE and transitions to an inactive state (e.g., events 336, 536). At box 608, the UE starts a CG-SDT timer (e.g., CG-SDT-TAT) after resetting the MAC entity. At block 610, when operating in an inactive state, the UE transmits data to the base station using the CG-SDT configuration (e.g., events 404, 418, 420, 492, 592, 593). At block 612, when operating in an inactive state, the UE receives data from the base station (e.g., events 418, 432, 434, 494, 495, 592, 593, 595).
[0128] Because the UE starts the CG-SDT timer at the MAC entity after the UE performs the MAC reset process to reset the MAC entity at block 606. Therefore, the UE does not stop the CG-SDT timer when resetting the MAC entity.
[0129] In some implementations, the UE uses the C-RNTI to perform communications with the base station at block 602, and uses the C-RNTI to receive a DL MAC PDU including an RRC release message at block 604. In response to receiving the RRC release message or thereafter, the UE retains the C-RNTI. In such implementations, the UE retains the C-RNTI at the MAC entity after resetting the MAC entity. Thus, the UE may use the C-RNTI to receive data from the base station at block 612.
[0130] In some implementations, the UE resets a MAC entity, which the UE uses at box 602 to communicate with a base station and at box 604 to receive an RRC release message. In some implementations, in response to resetting the MAC entity, the UE sets a new data indicator (NDI) of an uplink HARQ process (HARQ process) of the MAC entity to a default value (e.g., zero), refreshes a soft buffer of an uplink HARQ process of the MAC entity, and / or determines (e.g., considers) a next transmission of a transport block as a new transmission for each downlink HARQ process in a downlink HARQ process of the MAC entity. After resetting the MAC entity, the UE uses the uplink HARQ process to transmit data to the base station (e.g., events 404, 418, 492, 542, 593). After resetting the MAC entity, the UE uses the downlink HARQ process to receive data from the base station (e.g., events 418, 492, 512, 593). In some implementations, the UE initializes one or more parameters for logical channel prioritization in response to resetting the MAC entity. After resetting the MAC entity, the UE performs logical channel prioritization with the initialized parameters to transmit data to the base station (e.g., events 404, 418, 492, 593). In some implementations, the UE refreshes the Msg3 or MsgA buffer in response to resetting the MAC entity. After resetting the MAC entity, the UE may utilize the refreshed Msg3 or MsgA buffer to perform a random access procedure to transmit data to the base station (e.g., events 404, 492, 542, 593).
[0131] Figure 6B 6 is a flow chart of an example method 600B, which is similar to method 600A, except that method 600B includes blocks 607 and 609 instead of blocks 606 and 608. At block 607, in response to the RRC release message, the UE starts the CG-SDT timer, resets the UE's MAC entity and transitions to an inactive state (e.g., events 336, 536). At block 609, the UE avoids stopping the CG-SDT timer when resetting the MAC layer.
[0132] In some implementations, the UE may start the CG-SDT timer at the MAC entity. When the UE performs a MAC reset procedure at block 607 to reset the MAC entity, the UE avoids stopping the CG-SDT timer at block 609. In other implementations, the UE may start the CG-SDT timer outside the MAC entity to avoid stopping the CG-SDT timer when resetting the MAC entity. For example, the UE may start the CG-SDT timer at the RRC entity of the UE.
[0133] Figure 6C 6 is a flow chart of an example method 600C, which is similar to methods 600A and 600B, except that method 600C includes blocks 605, 611, and 614 instead of blocks 607 and 608. At block 605, in response to the RRC release message, the UE starts the CG-SDT timer and transitions to an inactive state (e.g., event 336, 536). At block 611, when operating in the inactive state, the UE determines to perform a CG-SDT with a base station using a configuration authorization configured in the CG-SDT configuration. At block 614, in response to the determination of block 611, the UE resets the MAC entity of the UE.
[0134] Fig. 7A A method 700A is illustrated that may be implemented by a UE (eg, UE 102) for managing small data transmissions using a configuration grant configuration.
[0135] Method 700A begins at box 702, where when operating in a connected state, the UE performs communication with a base station (e.g., base station 104) (e.g., events 404, 418, 420, 492, 592, 593). At box 704, the UE receives an RRC release message that configures a CG-SDT configuration (e.g., events 434, 494, 594). At box 706, in response to the RRC release message, the UE resets the MAC entity of the UE and remains in an inactive state (e.g., events 436, 536). At box 708, the UE starts the CG-SDT timer after resetting the MAC layer. At box 710, when operating in an inactive state, the UE uses the CG-SDT configuration to transmit data to the base station (e.g., events 493, 593). At box 712, when operating in an inactive state, the UE receives data from the base station (e.g., events 493, 495, 593, 595).
[0136] In some implementations, the UE may start the CG-SDT timer at the MAC entity after the UE performs a MAC reset procedure to reset the MAC entity at block 706. Thus, the UE avoids stopping the CG-SDT timer when resetting the MAC entity.
[0137] In some implementations, the UE uses the C-RNTI to perform communications with the base station at block 702, and uses the C-RNTI to receive a DL MAC PDU including an RRC release message at block 704. In response to receiving the RRC release message or thereafter, the UE retains the C-RNTI. In such implementations, the UE retains the C-RNTI at the MAC entity after resetting the MAC entity. Thus, the UE may use the C-RNTI to receive data from the base station at block 712.
[0138] Figure 7B 700B is a flow chart of an example method 700B, which is similar to method 700A, except that method 700B includes blocks 707 and 709 instead of blocks 706 and 708. At block 707, in response to the RRC release message, the UE starts the CG-SDT timer, resets the UE's MAC entity and remains in an inactive state (e.g., events 436, 536). At block 709, the UE avoids stopping the CG-SDT timer when resetting the MAC layer.
[0139] In some implementations, the UE may start the CG-SDT timer at the MAC entity. When the UE performs a MAC reset procedure at block 707 to reset the MAC entity, the UE avoids stopping the CG-SDT timer at block 709. In other implementations, the UE may start the CG-SDT timer outside the MAC entity to avoid stopping the CG-SDT timer when resetting the MAC entity. For example, the UE may start the CG-SDT timer at the RRC entity of the UE.
[0140] Figure 7C 700C is a flow chart of an example method 700C, which is similar to methods 700A and 700B, except that method 700C includes blocks 705, 711, and 714 instead of blocks 707 and 708. At block 705, in response to the RRC release message, the UE starts the CG-SDT timer and remains in an inactive state (e.g., events 436, 536). At block 711, when operating in an inactive state, the UE determines to use the configuration authorization configured in the CG-SDT configuration to perform a CG-SDT with the base station. At block 714, in response to the determination of block 711, the UE resets the MAC entity of the UE.
[0141] Figure 8 A method 800 is illustrated that may be implemented by a UE (eg, UE 102) for managing small data transmissions using a configuration grant configuration.
[0142] Method 800 begins at box 802, where the UE maintains the CG-SDT timer running when the UE operates in an inactive state. In some implementations, the UE starts or restarts the CG-SDT timer as described above. At box 804, when operating in an inactive state and maintaining the CG-SDT timer running, the UE performs a random access procedure with a base station (e.g., base station 104). At box 806, the UE receives a random access response including a timing advance command from the base station during the random access procedure. At box 808, the UE avoids starting or restarting the CG-SDT timer when receiving the timing advance command. That is, the UE maintains (or keeps) the CG-SDT timer running when receiving the timing advance command.
[0143] In some implementations, when operating in an inactive state and maintaining the CG-SDT timer running, the UE performs a random access procedure to request on-demand system information. In some implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in Msg3 of the random access procedure to request on-demand system information. In other implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in MsgA of the random access procedure to request on-demand system information.
[0144] In some implementations, the UE avoids applying the timing advance command to adjust the uplink transmission timing in the CG-SDT. Instead, the UE applies the timing advance command to adjust the uplink transmission timing in the CG-SDT.
[0145] Fig. 9 A method 900 is illustrated that may be implemented by a UE (eg, UE 102) for managing small data transmissions using a configuration grant configuration.
[0146] Method 900 starts at box 902, where the UE maintains the CG-SDT timer running when the UE is operating in an inactive state. In some implementations, the UE starts or restarts the CG-SDT timer as described above. At box 904, when operating in an inactive state and maintaining the CG-SDT timer running, the UE performs a random access process with a base station. At box 906, the UE receives a random access response including a timing advance command from the base station during the random access process. At box 908, the UE determines whether the UE performs a random access process for the purpose of requesting on-demand system information. If the UE determines that the UE performs a random access process for the purpose of requesting on-demand system information, the process proceeds to box 910. At box 910, the UE avoids restarting the CG-SDT timer when receiving the timing advance command. Otherwise, if the UE determines that the UE performs a random access process for a purpose other than requesting on-demand system information, the process proceeds to box 912. At box 912, the UE restarts the CG-SDT timer when receiving the timing advance command.
[0147] In the case where the UE performs a random access procedure to request on-demand system information, the UE avoids applying the timing advance command to adjust the uplink transmission timing in the CG-SDT. Instead, the UE applies the timing advance command to adjust the uplink transmission timing in the CG-SDT. In some implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in Msg3 of the random access procedure to request on-demand system information. In other implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in MsgA of the random access procedure to request on-demand system information.
[0148] In some implementations, the UE restarts the CG-SDT timer with the timer value at block 912. In some implementations, the UE receives the timer value in an RRC release message received by the UE from the base station (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595). In other implementations, the UE receives the timer value in a system information block (SIB) broadcast by the base station.
[0149] Fig.10 A method 1000 is illustrated that may be implemented by a UE (eg, UE 102) for managing small data transmissions using a configuration grant configuration.
[0150] Method 1000 begins at box 1002, where the UE maintains a CG-SDT timer running when the UE operates in an inactive state. At box 1004, while operating in an inactive state and maintaining the CG-SDT timer running, the UE performs a random access procedure with a base station. At box 1006, the UE receives a random access response including a timing advance command from the base station during the random access procedure. At box 1008, the UE starts or restarts a non-CG-SDT timer upon receiving the timing advance command. At box 1010, the UE detects expiration of a non-CG-SDT timer. At box 1012, the UE maintains the CG-SDT timer running when it detects that the non-CG-SDT timer has expired.
[0151] In some implementations, the CG-SDT timer may be a CG-SDT-TAT. In some implementations, the non-CG-SDT timer may be a non-CG-SDT TAT (eg, timeAlignmentTimer).
[0152] In the case where the UE performs a random access procedure to request on-demand system information, the UE avoids applying the timing advance command to adjust the uplink transmission timing in the CG-SDT. Instead, the UE applies the timing advance command to adjust the uplink transmission timing in the CG-SDT. In some implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in Msg3 of the random access procedure to request on-demand system information. In other implementations, the UE may transmit an RRCSystemInfoRequest message to the base station in MsgA of the random access procedure to request on-demand system information.
[0153] In some implementations, the UE avoids stopping the CG-SDT timer upon detecting expiration of a non-CG-SDT timer. In some implementations, the UE avoids restarting the CG-SDT timer upon receiving a timing advance command. Alternatively, the UE restarts the CG-SDT timer upon receiving a timing advance command.
[0154] Prior to block 1002, the UE starts or restarts the CG-SDT timer (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595) using the timer value received by the UE in the RRC release message from the base station. In some implementations, the UE restarts the non-CG-SDT timer at block 1008 using the timer value in the system information block (SIB) broadcast by the base station.
[0155] The following list of examples reflects the various implementations expressly contemplated by the present disclosure:
[0156] Example 1. A method implemented by a user equipment (UE) to manage a CG-SDT time alignment timer that indicates the validity of a configuration of a granted small data transmission (CG-SDT), the method comprising: receiving a radio resource control (RRC) release message from a radio access network (RAN); in response to the RRC release message, (i) resetting a media access control (MAC) entity of the UE, and (ii) starting the CG-SDT time alignment timer after resetting the MAC entity.
[0157] Example 2. A method as described in Example 1, wherein the RRC release message includes a CG-SDT configuration.
[0158] Example 3. A method as described in Example 1 or 2, wherein the receiving occurs when the UE is in a connected state.
[0159] Example 4. The method as described in Example 3 further includes: in response to an RRC release message, transitioning from a connected state to an inactive state.
[0160] Example 5. A method as described in Example 1 or 2, wherein the receiving occurs when the UE is in an inactive state.
[0161] Example 6. The method as described in any one of Examples 1 to 5 further includes: after starting the CG-SDT time alignment timer and when the UE is in an inactive state, using the CG-SDT configuration to transmit uplink data to the RAN.
[0162] Example 7. The method as described in any of Examples 1 to 5, further comprising: in response to resetting the MAC entity, (i) setting a new data indicator (NDI) of one or more uplink HARQ processes of the MAC entity to a default value, and / or (ii) refreshing a soft buffer of one or more uplink HARQ processes of the MAC entity; and using one or more uplink HARQ processes to transmit uplink data to the RAN.
[0163] Example 8. The method as described in any of Examples 1 to 5, further comprising: initializing one or more parameters for logical channel prioritization in response to resetting the MAC entity; and transmitting uplink data to the RAN using the logical channel prioritization having the one or more initialized parameters to transmit uplink data.
[0164] Example 9. The method as described in any one of Examples 6 to 8 further includes: refreshing one or more Msg3 or MsgA buffers used for the random access process in response to resetting the MAC entity; and performing the random access process using the refreshed one or more Msg3 or MsgA buffers to transmit uplink data to the RAN.
[0165] Example 10. The method as described in any one of Examples 1 to 9 further includes: receiving downlink data from the RAN after starting the CG-SDT time alignment timer and when the UE is in an inactive state.
[0166] Example 11. The method as described in any of Examples 1 to 9 further includes: in response to resetting the MAC entity, determining that the next transmission of the transport block is a new transmission of one or more downlink HARQ processes of the MAC entity; and using one or more downlink HARQ processes to receive downlink data from the RAN.
[0167] Example 12. A method implemented by a user equipment (UE) to manage a CG-SDT time alignment timer that indicates the validity of a configuration of a granted small data transmission (CG-SDT), the method comprising: starting the CG-SDT time alignment timer through processing hardware of the UE; receiving a timing advance command from a radio access network (RAN) when the UE is in an inactive state and the CG-SDT time alignment timer is running; and avoiding restarting the CG-SDT time alignment timer when the timing advance command is received.
[0168] Example 13. The method as described in Example 12 includes: when the UE is in an inactive state and the CG-SDT time alignment timer is running, performing a random access procedure with the RAN, wherein the execution includes sending a random access message to the RAN, and receiving a random access response message from the RAN, the random access response message including a timing advance command.
[0169] Example 14. The method of Example 13, wherein the UE performs a random access procedure to request on-demand system information from the RAN.
[0170] Example 15. The method of Example 14, wherein the UE avoids restarting the CG-SDT time alignment timer based on the random access procedure being a random access procedure for requesting on-demand system information from the RAN.
[0171] Example 16. The method of any one of Examples 12 to 15, further comprising: avoiding applying a timing advance command to adjust the uplink transmission timing of the CG-SDT.
[0172] Example 17. The method as described in any of Examples 12 to 15 further includes: applying a timing advance command to adjust the uplink transmission timing of the CG-SDT.
[0173] Example 18. A method implemented by a user equipment (UE) to manage a CG-SDT time alignment timer that indicates the validity of a configuration authorized small data transmission (CG-SDT) configuration, the method comprising: starting the CG-SDT time alignment timer through processing hardware of the UE; while the UE is in an inactive state and the CG-SDT time alignment timer is running, performing a random access procedure with a radio access network (RAN), wherein the execution comprises sending a random access message to the RAN; receiving a random access response message from the RAN, the random access response message comprising a timing advance command; in response to receiving the timing advance command, starting or restarting a non-CG-SDT time alignment timer; and when the non-CG-SDT time alignment timer expires (e.g., when the UE detects the timer), avoiding stopping or restarting the CG-SDT time alignment timer.
[0174] Example 19. The method of Example 18, wherein the UE performs a random access procedure to request on-demand system information from the RAN.
[0175] Example 20. The method of Example 18 or 19, further comprising: avoiding applying a timing advance command to adjust the uplink transmission timing of the CG-SDT.
[0176] Example 21. The method of any one of Examples 18 to 20, further comprising: applying a timing advance command to adjust the uplink transmission timing of the CG-SDT.
[0177] Example 22. A user equipment (UE) comprising processing hardware and configured to implement a method as described in any one of Examples 1 to 21.
[0178] Example 23. A method implemented by a user equipment (UE) to manage a CG-SDT time alignment timer that indicates the validity of a configured authorized small data transmission (CG-SDT) configuration, the method comprising: receiving a radio resource control (RRC) release message from a radio access network (RAN) through processing hardware of the UE; after receiving the RRC release message, resetting the media access control (MAC) entity of the UE; and avoiding resetting the CG-SDT time alignment timer when resetting the MAC entity.
[0179] Example 24. The method of Example 23, wherein the RRC release message includes a CG-SDT configuration.
[0180] Example 25. The method of Example 23 or 24, wherein the receiving occurs when the UE is in a connected state.
[0181] Example 26. The method of Example 25, further comprising: transitioning from a connected state to an inactive state in response to an RRC release message.
[0182] Example 27. The method of Example 23 or 24, wherein the receiving occurs when the UE is in an inactive state.
[0183] Example 28. A method as described in any of Examples 23 to 27, wherein resetting the MAC entity is in response to an RRC release message.
[0184] Example 29. The method as described in any one of Examples 23 to 27 further includes: starting a CG-SDT time alignment timer after receiving an RRC release message; and after starting the CG-SDT time alignment timer, determining to use the CG-SDT configuration to perform CG-SDT with the RAN, wherein the reset is in response to the determination.
[0185] Example 30. The method as described in any of Examples 23 to 29 further includes: after avoiding stopping the CG-SDT time alignment timer and when the UE is in an inactive state, using the CG-SDT configuration to transmit uplink data to the RAN.
[0186] Example 31. The method as described in any of Examples 23 to 29 further includes: in response to resetting the MAC entity, (i) setting a new data indicator (NDI) of one or more uplink HARQ processes of the MAC entity to a default value, and / or (ii) refreshing a soft buffer of one or more uplink HARQ processes of the MAC entity; and using one or more uplink HARQ processes to transmit uplink data to the RAN.
[0187] Example 32. The method as described in Example 30 or 31 further includes: initializing one or more parameters for logical channel prioritization in response to resetting the MAC entity; and transmitting uplink data to the RAN using the logical channel prioritization having the one or more initialized parameters to transmit uplink data.
[0188] Example 33. The method as described in any one of Examples 30 to 32 further includes: refreshing one or more Msg3 or MsgA buffers used for a random access process in response to resetting the MAC entity; and performing a random access process using the refreshed one or more Msg3 or MsgA buffers to transmit uplink data to the RAN.
[0189] Example 34. The method as described in any of Examples 23 to 33 further includes: receiving downlink data from the RAN after starting the CG-SDT time alignment timer and when the UE is in an inactive state.
[0190] The following description can be applied to the above description.
[0191] In some implementations, "message" is used and "information element (IE)" may be substituted for "message" and vice versa. In some implementations, "IE" is used and "field" may be substituted for "IE" and vice versa. In some implementations, "configuration" or "configuration parameter" may be substituted for "configuration" and vice versa. In some implementations, "early data transmission (EDT)" may be substituted for "small data transmission" and "EDT" may be substituted for "SDT" and vice versa. In some implementations, "small data transmission" may be substituted for "small data communication" and vice versa. In some implementations, "stop" may be substituted for "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 smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit or an advanced driver assistance system (ADAS) of a vehicle. Further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[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 implemented by a user equipment (UE) for managing a CG-SDT time alignment timer indicating validity of a CG-SDT configuration, the method comprising: receiving a radio resource control (RRC) release message from a radio access network (RAN); as well as In response to the RRC release message, (i) a medium access control (MAC) entity of the UE is reset, and (ii) after resetting the MAC entity, the CG-SDT time alignment timer is started.
2. The method of claim 1, wherein the RRC release message includes the CG-SDT configuration.
3. The method of claim 1 or 2, wherein the receiving occurs when the UE is in a connected state, and wherein the method further comprises: In response to the RRC release message, transition is made from the connected state to an inactive state.
4. The method of claim 1 or 2, wherein the receiving occurs when the UE is in an inactive state.
5. The method according to any one of claims 1 to 4, further comprising: In response to resetting the MAC entity, determining that a next transmission of a transport block is a new transmission for one or more downlink HARQ processes of the MAC entity; as well as Downlink data is received from the RAN using the one or more downlink HARQ processes.
6. A method implemented by a user equipment (UE) for managing a CG-SDT time alignment timer indicating validity of a CG-SDT configuration, the method comprising: Starting the CG-SDT time alignment timer; receiving a timing advance command from a radio access network (RAN) while the UE is in an inactive state and the CG-SDT time alignment timer is running; as well as When the timing advance command is received, restarting the CG-SDT time alignment timer is avoided.
7. The method of claim 6, comprising: When the UE is in the inactive state and the CG-SDT time alignment timer is running, a random access procedure with the RAN is performed, wherein the performing includes sending a random access message to the RAN and receiving a random access response message from the RAN, wherein the random access response message includes the timing advance command.
8. The method of claim 7, wherein the UE performs the random access procedure to request on-demand system information from the RAN, and wherein the UE avoids restarting the CG-SDT time alignment timer based on that the random access procedure is a random access procedure for requesting on-demand system information from the RAN.
9. The method according to any one of claims 6 to 8, further comprising: Avoid applying the timing advance command to adjust the uplink transmission timing of the CG-SDT.
10. The method according to any one of claims 6 to 8, further comprising: The timing advance command is applied to adjust the uplink transmission timing of the CG-SDT.
11. A method implemented by a user equipment (UE) to manage a configuration grant small data transmission (CG-SDT) time alignment timer indicating validity of a CG-SDT configuration, the method comprising: Starting the CG-SDT time alignment timer; performing a random access procedure with a radio access network (RAN) while the UE is in an inactive state and the CG-SDT time alignment timer is running, wherein the performing comprises sending a random access message to the RAN; receiving a random access response message from the RAN, the random access response message including a timing advance command; In response to receiving the timing advance command, starting or restarting a non-CG-SDT time alignment timer; as well as When the non-CG-SDT time alignment timer expires, avoid stopping or restarting the CG-SDT time alignment timer.
12. The method of claim 11, wherein the UE performs the random access procedure to request on-demand system information from the RAN.
13. The method of claim 11 or 12, further comprising: Avoid applying the timing advance command to adjust the uplink transmission timing of the CG-SDT.
14. The method of any one of claims 11 to 13, further comprising: The timing advance command is applied to adjust the uplink transmission timing of the CG-SDT.
15. A user equipment (UE) comprising processing hardware and configured to implement the method of any one of claims 1 to 14.
