Delay of requests for resources related to small data transmissions
By realizing delay configuration and resource request management in the cellular radio access network, the data transmission delay problem of user equipment in the inactive state is solved, and data transmission efficiency and delay performance are improved.
Patent Information
- Application Number
- CN202380033326.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-22
- Filing Date
- 2023-02-22
- Publication Date
- 2024-11-29
AI Technical Summary
In cellular radio access networks, when user equipment performs uplink and downlink data communication in an inactive or idle state, it is difficult for the prior art to effectively manage resource requests and scheduling, resulting in data transmission delay and inefficiency.
By implementing latency configuration and resource request management between user equipment and radio access network, request and scheduling of resources is delayed to optimize the small data transmission process and reduce data communication delay.
Effectively manage resource requests of user equipment in an inactive state, improve data transmission efficiency and delay performance, and reduce resource scheduling delays of user equipment by radio access network.
Smart Images

Figure HDA0005077107380000011 
Figure HDA0005077107380000021 
Figure HDA0005077107380000022
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, and more particularly to communication of uplink and / or downlink data at 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] Generally speaking, base stations operating in a cellular radio access network (RAN) use a specific radio access technology (RAT) and multiple layers of a protocol stack to communicate with user equipment (UE). For example, the physical layer (PHY) of the RAT provides transport channels to the media access control (MAC) sublayer, which in turn provides logical channels 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 due to radio access network (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. A small data transfer (SDT) procedure may enable the network to support data transmission for a UE operating in the RRC_INACTIVE state (i.e., without transitioning 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 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., referred to as random access SDT (RA-SDT)) or a transmission on a type 1 configuration grant (CG) resource (i.e., referred to as CG-SDT). For RA-SDT, the network configures two-step and / or four-step random access resources for SDT. In RA-SDT, the UE can send an initial transmission including data in message three (MSG3) of a four-step random access process or in the payload of message A (MSGA or MsgA) of a two-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 (or CG-SDT session) can only be initiated with valid UL timing alignment. UL timing alignment is maintained by the UE based on the SDT specific timing alignment timer configured by the network and the DL RSRP of the configured number of highest ranked synchronization signal blocks (SSBs). When the SDT specific timing alignment timer expires, the CG resources are released. When CG-SDT is initiated, the UE uses the CG to send an initial transmission including data on the CG opportunity, and the network can use dynamic grants to schedule subsequent uplink transmissions. Alternatively, subsequent transmissions can be performed on subsequent CG resource opportunities. During CG-SDT, downlink transmissions are scheduled using dynamic assignments. The UE can initiate subsequent uplink transmissions only after receiving confirmation of the initial transmission from the network.
[0007] In some scenarios and implementations, the UE performs an SDT with a base station (e.g., a 5G NR base station such as a gNB). When the UE has SDT data to send and does not have UL resources scheduled by the base station, the UE sends an SDT resource request (e.g., a random access preamble of a four-step random access procedure or a MsgA of a two-step random access procedure) to request the base station to schedule uplink resources for the UE. In some implementations, the base station may schedule uplink resources for the UE less frequently than for non-SDT because the data eligible for SDT (i.e., SDT data) is not urgent. In such cases, the base station does not expect to receive an SDT resource request from the UE or to service this request by scheduling uplink resources for the UE. In other implementations, the base station provides the UE with a CG configuration for SDT and tends to restrict the UE to sending SDT data only on the CG resources configured in the CG configuration. However, there is no mechanism for the base station to prevent the UE from sending an SDT resource request to the base station to request the base station to schedule uplink resources for the UE. Summary of the invention
[0008] An example embodiment of the technology of the present disclosure is a method of sending a control element (CE) to a radio access network (RAN). The method is implemented in a user equipment (UE) and includes: when the UE is performing a small data transfer (SDT) procedure, determining that resources for sending the CE to the RAN are unavailable; and in response to the determination and according to a delay configuration, delaying the transmission of a request for the resource to the RAN.
[0009] Another example embodiment of the techniques is a method for configuring a user equipment (UE). The method is implemented in a radio access node (RAN) and includes: generating a delay configuration during a small data transfer (SDT) procedure, according to which the UE will delay requesting resources for transmission to the RAN; sending the delay configuration to the UE; and receiving a request for the resources from the UE according to the delay configuration. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] 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 disclosed techniques for reducing latency in data communications;
[0011] 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.
[0012] Figure 2A yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a base station;
[0013] 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;
[0014] Figure 3 Illustrate an example scenario in which a UE uses a non-SDT configuration to communicate with a distributed base station in a connected state until the base station determines to cause the UE to transition to an inactive state;
[0015] Figure 4 Examples and Figure 3 An example scenario similar but in which the UE communicates with the distributed base station via UL resources while in an inactive state and remains in an inactive state;
[0016] Figure 5A An example scenario is illustrated in which a UE communicates with a distributed base station via a non-small data transfer (SDT) before sending a non-SDT indication to a base station and entering a connected state;
[0017] Figure 5B Examples and Figure 5A A similar example scenario but where the UE sends a request to the distributed base station to resume the radio connection with the UE;
[0018] Fig. 6A An example method implemented at a base station for generating an SDT configuration including a delay configuration for a UE and sending the configuration to the UE is illustrated;
[0019] Figure 6B Examples and Fig. 6A An example method similar to the one described above but wherein the base station generates an SDT configuration including a delay configuration when the SDT is a CG-SDT;
[0020] Figure 6C Examples and Fig. 6A and Figure 6B An example method similar to this but wherein the base station generates an SDT configuration including the delay configuration when the base station determines to configure such a delay configuration;
[0021] Figure 7 An example method implemented at a DU for generating a delay configuration for delaying an SDT resource request and sending the delay configuration to a CU and a UE is illustrated;
[0022] Figure 8 illustrating an example method implemented at a DU for generating a first delay configuration or a second delay configuration based on whether a CU-to-DU message requests a lower configuration for an SDT;
[0023] Fig. 9Illustrate an example method implemented at a base station for sending a first delay configuration and a second delay configuration to a UE to delay an SDT resource request and a non-SDT resource request, respectively;
[0024] Fig.10 An example method implemented in a base station for determining whether to send a first delay configuration or a second delay configuration to a UE based on whether a request from the UE is for SDT or non-SDT operation is illustrated;
[0025] Fig.11 An example method implemented in a base station for determining to configure a UE to delay requesting resources for SDT operation and non-SDT operation and sending a configuration for the UE to delay requesting the resources is illustrated;
[0026] Fig.12 An example method implemented in a base station for sending a first plurality of configuration parameters and a second plurality of configuration parameters to a UE and communicating with the UE based on the configuration parameters is illustrated;
[0027] Fig.13A An example method implemented in a UE for determining whether to send a data packet to a RAN node during an SDT session or to delay initiation of an SDT resource request based on whether the UE has uplink resources for sending data is illustrated;
[0028] Fig. 13B Example of implementation in UE Fig.13A An example method similar to the one described above but wherein the UE further determines whether to delay or initiate an SDT resource request based on whether the UE is configured to delay the SDT resource request;
[0029] Fig.14A Illustrate an example method implemented in a UE for determining whether to send a data packet or delay initiation of an SDT resource request based on whether the UE has uplink resources to send a MAC control element;
[0030] Fig. 14B Example of implementation in UE Fig.14A An example method similar to the one described above but wherein the UE further determines whether to delay or initiate an SDT resource request based on whether the UE is configured to delay the SDT resource request;
[0031] Fig.15 Illustrate an example method implemented in a UE for receiving a delay configuration from a RAN node, applying the configuration when in an inactive state, and suspending application of the configuration when in a connected state;
[0032] Fig.16Illustrate an example method implemented in a UE for applying a delay configuration when in a connected state, performing SDT when in an inactive state, and suspending application of the delay configuration or applying the delay configuration during the SDT;
[0033] Fig.17 illustrating an example method implemented in a UE for determining whether to apply a delay configuration when in a connected state or in an inactive state based on whether the delay configuration is applicable to a connected state or an inactive state; and
[0034] Fig.18 An example method implemented in a UE for receiving a first plurality of configuration parameters and a second plurality of configuration parameters and using the configuration parameters to communicate with a RAN node is illustrated. DETAILED DESCRIPTION
[0035] 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 small data or 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, early data communications may refer to early data transmission (EDT) or small data transmission (SDT) from a network perspective (i.e., EDT or SDT in a downlink direction), or EDT or SDT from a UE perspective (i.e., EDT or SDT in an uplink direction).
[0036] 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 core network (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.
[0037] 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 and 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).
[0038] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets 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. In general, 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.
[0039] 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.
[0040] 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.
[0041] As used in the present disclosure, the term "data" or "data packet" may refer to: signaling, control plane information at a protocol layer that controls radio resources (e.g., RRC), controls mobility management (MM), or controls session management (SM); or non-signaling, non-control plane information at a protocol layer above a layer of a protocol for controlling radio resources (e.g., RRC), above a layer of a protocol for controlling mobility management (MM), above a layer of a protocol for controlling session management (SM), and / or above a layer of a protocol for controlling quality of service (QoS) flows (e.g., Service Data Adaptation Protocol (SDAP)). The data to which the UE and / or RAN applies the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. 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.
[0042] In the example scenarios discussed below, UE 102 transitions to an 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 an RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for uplink transmission in the RRC_INACTIVE or RRC_IDLE state, UE 102 may apply one or more security functions to an uplink (UL) data packet, generate a first UL protocol data unit (PDU) including a security-protected packet, include an UL RRC message in a second UL PDU along with the first UL PDU, and send the second UL PDU to RAN 105. UE 102 includes a UE identity / identifier (ID) of UE 102 in the UL RRC message. RAN 105 may identify UE 102 based on the UE ID. In some implementations, the UE ID may be an Inactive Radio Network Temporary Identifier (I-RNTI), a Recovery ID, or a Non-Access Stratum (NAS) ID. The NAS ID may be an S-Temporary Mobile Subscriber Identity (S-TMSI) or a Globally Unique Temporary Identifier (GUTI).
[0043] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 may generate a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 may encrypt data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 may send the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.
[0044] In some implementations, the data is an uplink (UL) service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (e.g., UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which may be associated with a media access control (MAC) layer. Therefore, in these cases, the UE 102 sends the protected UL PDCP PDU in the UL MACPDU. In some implementations, the UE 102 may include the UL RRC message in the UL MAC PDU. In a further implementation, 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 further implementations, the UE 102 may include the UL PDCP PDU in a UL radio link control (RLC) PDU, and then include the UL RLC PDU in a UL MAC PDU. In the case of including the UL RRC message in the UL MAC PDU, in some implementations, 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 is the resumeMAC-I field, as specified in 3GPP specification 38.331. In further implementations, the UE may utilize an integrity key (e.g., K RRCint The RRCMAC-I is obtained from the UL RRC message using a key), an integrity protection algorithm, and other parameters 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).
[0045] In a further implementation, the data is a UL service data unit (SDU) of NAS. 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. Then, UE 102 may include the UL NAS PDU in a second UL PDU such as a UL RRC message. Therefore, in these cases, UE 102 sends the (first) protected UL NAS PDU in the UL RRC message. In some implementations, UE 102 may include the UL RRC message in a UL MAC PDU and send the UL MAC PDU to a base station (e.g., base station 104 or 106) via a cell (e.g., cell 124 or 126). In this case, UE 102 may not include the RRC MAC-I in the UL RRC message. Alternatively, UE 102 may include the RRC MAC-I as described above.
[0046] 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.
[0047] More generally, the UE 102 may protect data using at least one of ciphering and integrity protection, include the protected data as a security-protected packet in a first UL PDU, and send the first UL PDU to the RAN 105 in a second UL PDU.
[0048] In some scenarios and implementations, the base station 106 may retrieve the UE ID of the UE 102 from the UL RRC message and identify the base station 104 as the destination of the data in the first UL PDU based on the determined UE ID. In one example implementation, the base station 106 retrieves the first UL PDU from the second UL PDU and sends the first UL PDU to the base station 104. The base station 104 then retrieves the security-protected packet from the first UL PDU, applies one or two security functions to decrypt the data and / or check integrity protection, and sends the data to the CN 110 (e.g., SGW 112, UPF 162, MME 114, or AMF 164) or an edge server. In some implementations, the edge server may operate within the RAN 105. More specifically, the base station 104 derives at least one security key from the UE context information of the UE 102. The base station 104 then retrieves the data from the security-protected packet by using the at least one security key and sends the data to the CN 110 or the edge server. When the security-protected packet is an encrypted packet, the base station 104 obtains data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 104 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.
[0049] In another implementation, the base station 106 retrieves the security-protected packet from the first UL PDU. The base station 106 performs a retrieve UE context procedure with the base station 104 to obtain UE context information of the UE 102 from the base station 104. The base station 106 derives at least one security key from the UE context information. Then, the base station 106 retrieves data from the security-protected packet by using at least one security key and sends the data to the CN 110 (e.g., UPF 162) or an edge server. When the security-protected packet is an encrypted packet, the base station 106 obtains the data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 106 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 106 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The base station 106 then determines whether the MAC-I is valid for the data. If the base station 106 determines that the MAC-I is valid, the base station 106 retrieves the data and forwards the data to the CN 110. However, if the base station 106 determines that the MAC-I is invalid, the base station 106 discards the packet.
[0050] 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.
[0051] Further, in some cases, the RAN 105 sends data in the downlink (DL) direction to the UE 102 operating in the RRC_INACTIVE or RRC_IDLE state.
[0052] For example, when the base station 104 determines that data is available for downlink transmission to the UE 102 currently operating in the 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 a first DL PDU in the 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 data. More specifically, when integrity protection is enabled, the base station 104 generates a MAC-I for protecting the integrity of the data, so that the security-protected packet includes the data and the MAC-I. When encryption is enabled, the base station 104 encrypts the data to generate an encrypted packet, so that the security-protected packet is an encrypted packet. Further, when both integrity protection and encryption are enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. In some implementations, the base station 104 generates a first DL PDU (such as a DL PDCP PDU) using the security-protected packet, includes the first DL PDU in a second DL PDU (e.g., a DL MAC PDU) associated with a MAC layer, for example, and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 104 includes the DL PDCP PDU in the DL RLC PDU, includes the DL RLC PDU in the DL MAC PDU, and sends the DL MAC PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state.
[0053] In another implementation, the base station 104 sends the first DL PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the first DL PDU, and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 106 generates a DL RLC PDU including the first DL PDU, and includes the DL RLC PDU in the second DL PDU. In yet another implementation, the base station 104 includes the first DL PDU in the DL RLC PDU, and sends the DL RLC PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the DL RLC PDU, and sends the second DL PDU to the UE 102.
[0054] In some implementations, a base station (i.e., base station 104 or 106) generates downlink control information (DCI) and a cyclic redundancy check (CRC) scrambled with an ID of UE 102 to send a second DL PDU generated by the base station. In some implementations, the ID of UE 102 may be a radio network temporary identifier (RNTI). For example, the RNTI may be a cell RNTI (C-RNTI), a temporary C-RNTI, or an inactive C-RNTI. The base station sends the DCI and the scrambled CRC to UE 102 operating in an RRC_INACTIVE or RRC_IDLE state on a physical downlink control channel (PDCCH). The base station scrambles the CRC with the ID of UE 102. In some implementations, the base station may assign the ID of UE 102 to UE 102 in a random access response or message B (MsgB) sent by the base station in a random access process with UE 102 before sending the DCI and the scrambled CRC. In a further implementation, the base station may assign the ID of UE 102 to UE 102 in an RRC message (e.g., an RRC release message or an RRC reconfiguration message) sent by the base station to UE 102 before sending the DCI and the scrambled CRC (e.g., when UE 102 is in the RRC_CONNECTED state).
[0055] UE 102 operating in RRC_INACTIVE or RRC_IDLE state can receive DCI and scrambled CRC on PDCCH. Then, UE 102 confirms 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 scrambled CRC. Then, UE 102 can retrieve data from the security-protected packet. If the security-protected packet is an encrypted packet, UE 102 can use an appropriate decryption function and security key to decrypt the encrypted packet to obtain data. If the security-protected packet is an integrity-protected packet including data and MAC-I, UE 102 can determine whether MAC-I is valid. If UE 102 confirms that MAC-I is valid, UE 102 retrieves data. However, if UE 102 determines that MAC-I is invalid, UE 102 discards the packet. Finally, when the security-protected packet is both encrypted and integrity-protected (having the encrypted data and the 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.
[0056] 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 media access control (MAC) controller 132, which is configured to perform a random access process with one or more user devices, receive uplink MAC protocol data units (PDUs) of one or more user devices, and send downlink MAC PDUs to one or more user devices. The processing hardware 130 may also include a packet data convergence protocol (PDCP) controller 134, which is configured to: in some scenarios, send a DL PDCP PDU according to which the base station 104 can send data in the downlink direction; and in other scenarios, receive a UL PDCP PDU according to which the base station 104 receives data in the uplink direction. 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 substantially similar components. In particular, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to components 130, 132, 134, 136, and 138, respectively.
[0057] 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 executable 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 media access control (MAC) controller 152, which is configured to perform a random access procedure with a base station, send an uplink MAC protocol data unit (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: in some scenarios, send a DL PDCP PDU according to which the base station 106 can send data in the downlink direction; and in further scenarios, receive a UL PDCP PDU according to which the base station 106 receives data in the uplink direction. The processing hardware may further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.
[0058] Figure 1B An example distributed or decentralized implementation of any one or more 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 (DU) 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 a radio link control (RLC) controller configured to manage or control one or more RLC operations or processes. In further implementations, the CU 172 does not include an RLC controller.
[0059] 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.
[0060] 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.
[0061] In some implementations, the CU 172 may include a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. The CU 172 may also include a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. The CU-CP 172A may send control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may send data packets (e.g., SDAP PDUs or Internet Protocol packets).
[0062] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the service requested by UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, the connection between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.
[0063] Figure 2AAn example protocol stack 200 is illustrated in a simplified manner by which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).
[0064] In the example stack 200, the physical layer (PHY) 202A of EUTRA 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 delivery services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 may in turn provide data transfer services to the Service Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As illustrated, the UE 102 may support NR PDCP 210 layered on top of EUTRA RLC 206A and SDAP sublayer 212 layered on top of NR PDCP sublayer 210.
[0065] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as service data units (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 protocol data units (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.
[0066] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide signaling radio bearers (SRBs) to the RRC sublayer ( Figure 2AThe 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.
[0067] Figure 2B An example protocol stack 250 is illustrated in a simplified manner by which UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and SRBs to the RRC 214.
[0068] Next, refer to Figures 3 to 5B To discuss the Figure 1A Several components of the present invention and several example scenarios related to sending data in an inactive or idle state. To simplify the following description, "inactive state" is used and may refer to the RRC_INACTIVE or RRC_IDLE state, and "connected state" is used and may refer to the RRC_CONNECTED state.
[0069] First, referring to the example scene 300 Figure 3, in which the base station 104 includes a central unit (CU) 172 and a distributed unit (DU) 174, and the CU 172 includes a CU-CP 172A and a CU-UP 172B. In this scenario, 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 DU configuration), and communicates 304 with the CU-CP 172A and / or the CU-UP 172B via the DU by using a CU configuration (i.e., a first non-SDT CU configuration). While the UE is communicating 304 with the base station 104, the CU-CP 172A may send 306 a UE context modification request message to the DU 174. In response, the DU 174 sends 308 a UE context modification response message including a non-SDT configuration for the UE 102 (i.e., a second non-SDT configuration) to the CU-CP 172A. The CU-CP 172A generates an RRC reconfiguration message including the non-SDT DU configuration and sends 310 a first CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to the DU 174. In turn, the DU 174 sends 312 the RRC reconfiguration message to the UE 102. In response, the UE 102 sends 314 an RRC reconfiguration complete message to the DU 174, which in turn sends 316 a first DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to the CU-CP 172A.
[0070] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the non-SDT DU configuration, and communicates with the CU-CP 172A and / or CU-UP 172B via the DU 174. In the event that the RRC reconfiguration message does not include a CU configuration, the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the first non-SDT CU configuration. In the event that the RRC reconfiguration message includes a non-SDT CU configuration (i.e., a second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the second non-SDT CU configuration. In some implementations, the second non-SDT CU configuration augments the first non-SDT CU configuration, or includes at least one new configuration parameter not included in the first non-SDT CU configuration. In some such cases, the UE 102 and the CU-CP 172A and / or CU-UP 172B may communicate 318 with each other using the second non-SDU CU configuration and configuration parameters of the first non-SDT CU configuration that are not augmented by the second non-SDU CU configuration.
[0071] 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., RRC214 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, in some implementations, the second non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers, which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE (e.g., as defined in 3GPP specification 38.331v16.7.0). Similarly, the second non-SDT CU configuration includes configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE. In some implementations, the first non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE.
[0072] In some implementations, the second non-SDT DU configuration augments the first non-SDT DU configuration, or includes at least one new configuration parameter not included in the first non-SDT DU configuration. In some such cases, the UE 102 and the DU 174 communicate 318 with each other using the second non-SDT DU configuration and configuration parameters in the first non-SDT DU configuration that are not augmented by the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), and the UE 102 and the DU 174 communicate with each other using the configuration parameters when the UE 102 operates in a connected state. Similarly, in some implementations, the second non-SDT DU configuration includes 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 (e.g., as defined in 3GPP specification 38.331 v16.7.0). Similarly, the second non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration are CellGroupConfig IEs.
[0073] 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.
[0074] 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 cause the UE 102 to transition from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., the UE 102 in the connected state does not have data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration process 390 (if performed), the UE 102 determines or detects data inactivity and sends 320 UE assistance information (e.g., UEAssistanceInformation message) 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. Subsequently, the DU 174 sends 321 a UL RRC messaging message including the UE assistance information to the CU-CP 172A. Thus, the CU-CP 172A may determine that the UE 102 is in a data inactive state based on the UE assistance information. In other implementations, the DU 174 may perform data inactivity monitoring for the UE 102. The CU-CP 172A may send a CU to DU message (e.g., a UE context setup request message or a UE context modification request message) to the DU 174 to request or command the DU 174 to perform data inactivity monitoring. In the event that the DU 174 detects or determines that the UE 102 is in a data inactive state during monitoring, the DU 174 may send 322 an inactivity notification (e.g., a UE inactivity notification message) to the CU-CP 172A. Thus, the CU-CP 172A may determine that the UE 102 is in a data inactive state based on the inactivity notification received from the DU 174.
[0075] In yet other implementations, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the case where CU-UP 172B detects or determines that UE 102 is in a state of data inactivity during monitoring, CU-UP 172B may send 323 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Therefore, CU-CP 172A may determine that UE 102 is in a state of 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 a state of data inactivity based on UE auxiliary information, an inactivity notification of event 322, and / or an inactivity notification of event 323.
[0076] 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 send any data in the downlink direction or uplink direction during the specific period, respectively. In response to this determination, CU-CP 172A may determine to cause UE 102 to transition to an inactive state with SDT configured. Alternatively, CU-CP 172A may determine to cause UE 102 to transition to an inactive state without SDT configured in response to determining that UE 102 is in a state of data inactivity.
[0077] In response to determining that the UE 102 is in a state of data inactivity (for the specific period of time) or determining to cause the UE 102 to transition to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CU-UP 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 a state of data inactivity (for the specific period of time) or determining to cause the UE 102 to transition 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 send 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, 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 sending the second DU-to-CU message. The CU-CP 172A may send an additional CU-to-DU message (e.g., a UE context modification confirmation message) to the DU 174 in response to the additional CU-to-DU message. In some alternative implementations, CU-CP 172A may send 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 a data inactive state. In further 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.
[0078] In response to determining that the UE 102 is caused to transition to an inactive state configured with SDT, the CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message, an RRCConnectionRelease message) to cause the UE 102 to transition to an inactive state. The CU-CP 172A may include the SDT DU configuration (if obtained from the DU 174) and / or the SDT CU configuration in the RRC release message. Then, the 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 the DU 174. Subsequently, the DU 174 sends 334 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and sends 334 the MAC PDU to the UE 102. The RRC release message instructs the UE 102 to transition to an inactive state. UE 102 transitions 336 from the connected state to the inactive state upon receiving the RRC release message. In response to the third CU-to-DU message, DU 174 may retain the SDT DU configuration (if generated by DU 174 during processes 328, 330), and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. 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.
[0079] In some implementations, when operating 302 in a connected state, the UE 102 uses the C-RNTI to monitor the PDCCH to receive DCI. In response to receiving 334 to the RRC release message or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. In some implementations, in response to receiving 334 to the RRC release message or transitioning 336 from the connected state to the inactive state or thereafter, the UE 102 may retain the C-RNTI. In some implementations, the UE 102 performs a two-step or four-step random access procedure with the base station 104 (e.g., CU-CP 172A and / or DU 174) and receives a random access response message including the C-RNTI from the DU 174 during the random access procedure. In other implementations, the UE 102 receives a random access response message from the CU-CP 172A or DU 174 via the DU 174. Figure 3 Another base station (eg, base station 106) not shown in the figure receives an RRC message (eg, an RRC reconfiguration message) including the C-RNTI.
[0080] 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.
[0081] 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 yet other implementations, if the RRC release message instructs the UE 102 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.
[0082] 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. 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.
[0083] 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 includes an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. In some implementations, the SDT CU configuration includes an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the PDCP entity of the DRB configured for SDT in SDT operation (i.e., for Figure 4 In some implementations, the SDT CU configuration includes a data volume threshold (e.g., sdt-DataVolumeThreshold) for the UE 102 to use to determine whether the UE 102 can initiate an SDT. In further implementations, the CU-CP 172A includes the SDT DU configuration in the SDT CU configuration. In some implementations, the "SDT CU configuration" can be simplified to "SDT configuration".
[0084] In some implementations, the SDT DU configuration includes at least one of: a buffer status report (BSR) configuration, a power headroom report (PHR) configuration, a configuration grant (CG) configuration for CG-SDT, a UL bandwidth part (BWP) configuration, a DL BWP configuration for CG-SDT, a time alignment timer value for CG-SDT (e.g., a CG-SDT time alignment timer (CG-SDT-TAT) value), and / or a timing advance validity threshold for CG-SDT. In some implementations, the UL BWP configuration configures a dedicated UL BWP for the UE 102 to perform CG-SDT. The UL BWP configuration may include a CG configuration, a physical uplink control channel (PUCCH) configuration, a physical uplink shared channel (PUSCH) configuration, and / or a sounding reference signal (SRS) configuration. In some implementations, the DL BWP configuration configures a dedicated DL BWP for the UE 102 during the CG-SDT. In some implementations, the DLBWP configuration includes a PDCCH configuration and / or a PDSCH configuration for the UE 102 to receive DL control signals from the DU 174 on the PDCCH and data from the DU on the PDSCH when the UE 102 performs a CG-SDT with the DU 174 .
[0085] Each of the CG configurations configures a periodic radio resource (e.g., a CG resource) that the UE 102 can use to send data without receiving a dynamic grant for data transmission. Each of the CG configurations configures or includes a periodicity indicating that the CG resource occurs periodically. In some implementations, the periodicity may be a fixed number of symbols, time slots, or subframes. Some or all of the CG configurations may have the same periodicity or different periodicities. In some implementations, each of the CG configurations configures or includes an offset that indicates a time domain offset (e.g., timeDomainOffset) related to a reference time (e.g., a system frame number (SFN)) of the CG resource. In some implementations, the CG configuration configures or includes a reference time (e.g., timeReferenceSFN). In some implementations, the CG configuration may be or may be similar to a ConfiguredGrantConfig IE (e.g., as specified in 3GPP specification 38.331).
[0086] DU 174 configures a timing advance validity threshold (e.g., including an RSRP range) for use by UE 102 in determining whether UE 102 can initiate SDT using the configuration grant 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 As described. In some implementations, the SDT DU configuration may be an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE. In some implementations, the "SDT DU configuration" may be replaced by the "CG-SDT configuration". In such implementations, the configuration in the SDT DU configuration is specific to the CG-SDT. In other implementations, some of the configurations in the SDT DU configuration described above may be grouped into the CG-SDT configuration, and other configurations in the SDT DU configuration (e.g., BSR configuration and / or PHR configuration) are not within the CG-SDT configuration. In some implementations, the SDT DU configuration includes a CG-SDT configuration. In such cases, other configurations may be configured for the CG-SDT or RA-SDT.
[0087] In some implementations, DU 174 starts or restarts the DU CG-SDT timer in response to or after receiving an SDT request indication, generating a CG-SDT configuration, receiving 328 a second CU to DU message, sending 330 a CG-SDT configuration to CU 172, receiving 332 a third CU to DU message, or sending 334 a CG-SDT configuration to UE 102. In some implementations, DU 174 uses a timer value to start or restart the DU CG-SDT timer 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 (e.g., within a predetermined range of 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. When the DU CG-SDT timer expires, the DU 174 releases the CG-SDT configuration or the CG resources configured in the CG-SDT configuration. Upon or after releasing the CG-SDT configuration, the DU 174 avoids receiving PUSCH transmissions from the UE 102 on the radio resources reserved or configured for the CG-SDT configuration. Upon or after releasing the CG-SDT configuration, the DU 174 may schedule transmissions of other UEs on the radio resources reserved or configured for the CG-SDT configuration.
[0088] As described above, in some implementations, the RRC release message 334 includes a CG-SDT configuration. In some implementations, in response to receiving the CG-SDT configuration or thereafter, the UE 102 uses the CG-SDT time alignment timer value to start or restart the UE CG-SDT timer (i.e., the first UE CG-SDT timer). When the UE CG-SDT timer expires, the UE 102 can release the CG-SDT configuration. Alternatively, when the UE CG-SDT timer expires, the UE 102 retains the CG-SDT configuration and avoids sending UL transmissions (e.g., MAC PDUs) on CG resources. In some such cases, the UE 102 releases the CG resources or determines that the CG resources are invalid. When the UE CG-SDT timer expires, the UE 102 can release the SRS configuration or the SRS resources configured in the SRS configuration. Alternatively, when the UE CG-SDT timer expires, the UE 102 retains the SRS configuration and avoids sending one or more SRSs to the DU 174 on the SRS resources.
[0089] While the UE CG-SDT timer is running, the inactive UE 102 communicates with the DU 174 via the dedicated DL BWP and the dedicated UL BWP (e.g., performs CG-SDT, sends SRS and / or receives DL control signals (e.g., DCI) and / or data). In some implementations, when the UE CG-SDT timer expires, the inactive UE 102 may switch from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In such cases, the UE 102 may re-tune the transceiver of the UE 102 to switch to the initial DL BWP and the initial UL BWP. In some implementations, when the UE 102 is configured with a CG-SDT configuration, the inactive UE 102 may switch to the initial DL BWP and the initial UL BWP to perform a random access procedure. The UE 102 may perform a random access procedure for different situations, as described below. In some implementations, the UE 102 in the inactive state may switch to the initial DL BWP and the initial UL BWP to perform measurements on the SSBs sent by the DU 174 on the initial DL BWP.
[0090] In some implementations, the DU 174 or the CU-CP 172A may configure the dedicated DL BWP and the dedicated UL BWP to be the same as or include the initial DL BWP and the initial UL BWP, respectively. In such implementations, when the UE CG-SDT timer expires, the UE 102 may not switch from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In such cases, the UE 102 may not re-tune the transceiver of the UE 102 due to switching BWP. In such cases, when the UE 102 in an inactive state performs a random access procedure with the DU 174, the UE 102 may perform a random access procedure without switching to the initial DL BWP and the initial UL BWP. In such cases, the UE 102 may perform measurements on the SSBs sent by the DU 174 within the initial DL BWP when performing the CG-SDT with the DU 174.
[0091] In some implementations, in response to or after the expiration of the UE CG-SDT timer, the UE 102 may perform a RA-SDT with the CU 172 via the DU 174 on the initial UL BWP and the initial DL BWP, as described for Figure 4 That is, in response to or after the UE CG-SDT timer expires, the UE 102 determines that the RA-SDT is valid.
[0092] In some implementations, DU 174 reserves the CG resources configured in the CG configuration. In some implementations, DU 174 releases the CG resources when the SDT DU configuration or the CG-SDT configuration is released or when the DU CG-SDT timer expires. In further implementations, DU 174 releases the SRS resources configured in the SRS configuration when the SDT DU configuration or the CG-SDT configuration is released or when the DU CG-SDT timer expires.
[0093] In the case where DU 174 does not provide CG-SDT configuration or 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 SDT DU configuration or CG-SDT configuration to CU-CP 172A, DU 174 reserves signaling and user data transmission resources for UE 102 in response to or after receiving the third CU-to-DU message.
[0094] 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.
[0095] In some implementations, when determining to cause UE 102 to transition to an inactive state configured with SDT, CU-CP 172A may not request DU 174 to provide an SDT DU configuration. In some such cases, events 328 and 330 may be omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own without requesting DU 174 to provide the SDT DU configuration, and include the SDT DU configuration in the RRC release message.
[0096] In some implementations, DU 174 may not include the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 may send the SDT DU configuration to CU-CP 172A as described above. In some implementations, DU 174 may not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In such cases, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 may include the CG-SDT configuration in the SDT DU configuration, as described above.
[0097] 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).
[0098] 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 102 operates in the connected state 302 or in the inactive state before the event 302, the DU 174 may receive the UE capabilities from the CU-CP 172A. Therefore, the DU 174 may determine whether the UE 102 supports CG-SDT based on the UE capabilities. In some implementations, the DU 174 may send a DU-to-CU message to the CU-CP 172A indicating whether the DU 174 supports CG-SDT, as described above.
[0099] 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 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 from a base station (e.g., base station 104 or base station 106) that transitions the UE 102 to an inactive state and does not configure SDT (e.g., indicates release of SDT or does not include the SDT configuration in the RRC release message). In this case, 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.
[0100] Later, the UE 102 operating in the inactive state configured with SDT initiates SDT. In response to or after initiating SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message and sends an initial UL MAC PDU to a cell (e.g., cell 124 or base station 104). Figure 1A 404 an initial UL MAC PDU is sent to DU 174 on another cell (not shown in FIG). The following events between UE 102 and DU 174 occur on the cell. UE 102 may start an SDT session timer in response to initiating an SDT. In some implementations, the SDT session timer may be a new timer defined in an RRC specification (e.g., v17.0.0). DU 174 retrieves an 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 CU-CP 172A. In some implementations, the first DU to CU message is an initial UL RRC messaging message. In other implementations, the first DU to CU message is a UL RRC messaging message.
[0101] In a scenario where the UE 102 initiates an SDT to send UL data (e.g., a data packet) eligible for SDT, the UE 102 includes the UL data in an initial UL MAC PDU sent 404 by the UE 102. In a scenario where the UE 102 initiates an SDT to receive DL data, the UE 102 does not include the UL data packet in the initial UL MAC PDU sent 404 by the UE 102. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging message 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 a UL RRC message.
[0102] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to send 404 an UL MAC PDU. In some such implementations, the SDT is 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 a four-step random access procedure, the UE 102 sends a random access preamble to the DU 174, and in response, the DU 174 sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE 102, and the UE 102 sends 404 an UL MAC PDU to the DU 174 according to the uplink grant. The DU 174 receives 404 an UL MAC PDU according to the uplink grant in the RAR, and in response, sends a DL MAC PDU including a contention resolution MAC control element to the UE 102. In an implementation with a two-step random access procedure, the UE 102 sends 404 a MsgA including a random access preamble and a UL MACPDU to the DU 174 according to the two-step random access configuration parameters. The UE 102 may receive a message B (MsgB) including a temporary C-RNTI and a timing advance command from the DU 174 in response to the MsgA. The DU 174 may include a contention resolution MAC control element in the MsgB. The UE 102 receives the two-step random access configuration parameters in the system information broadcasted by the DU 174 on the cell 124 before sending 404 the UL MACPDU. The DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.
[0103] When UE 102 successfully resolves contention during the random access procedure (e.g., receives a contention resolution MAC control element), UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3418 UL data and / or DL data). The UE 102 uses the C-RNTI to monitor the PDCCH from the DU 174 to communicate 418 data (e.g., UL data and / or DL data) with the base station 104. In detail, the UE 102 receives the DCI and the cyclic redundancy check (CRC) of the DCI on the PDCCH from the DU 174, and verifies the CRC using the C-RNTI. The DCI may include an uplink grant or a downlink assignment. If the UE 102 verifies that the CRC is correct and the DCI includes an uplink grant, the UE 102 uses the uplink grant to send 418 UL data to the DU 174. If the UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, the UE 102 uses the downlink assignment to receive 418 DL data from the DU 174.
[0104] In other implementations, when UE 102 receives or is configured with a CG configuration (e.g., Figure 3404 UL MAC PDU on CG resources. In some such cases, UE 102 performs CG-SDT. UE 102 does not perform a random access procedure for sending 404 UL MAC PDU. Therefore, DU 174 receives 404 UL MAC PDU on CG resources. In such implementations, in response to or after generating or sending 404 UL MAC PDU, UE 102 may start a UE timer (e.g., a second UE CG-SDT timer), for example when CU-CP 172A or DU 174 configures UE 102 to apply UE timer during SDT. In some implementations, UE 102 may start a UE timer using a UE timer value (e.g., a cg-SDT-RetransmissionTimer value). In some implementations, UE 102 may receive an RRC release message including a UE timer value from base station 104, similar to events 332, 334, 432, 434. CP-CP 172A may include the UE timer value in the CG-SDT configuration and send an RRC release message including the CG-SDT configuration to UE 102 via DU 174. In other implementations, UE 102 may receive the UE timer value in a system information block broadcast by DU 174 via cell 124. While the UE timer is running, UE 102 in an inactive state or SDT session avoids retransmitting UL MAC PDUs on CG resources. In some implementations, in response to or after receiving 404 to a UL MAC PDU on CG resources, DU 174 starts a DU timer (e.g., a second DU CG-SDT timer) using the DU timer value. In some implementations, the DU timer value may be the same as or greater than the UE timer value. While the DU timer is running, DU 174 processes UL transmissions received from UE 102 on CG resources as new transmissions.
[0105] In some implementations, the UE 102 may send 418 a subsequent UL MAC PDU including one or more UL data packets on the CG radio resources. In some implementations, the UE 102 may send 418 the subsequent UL MAC PDU on the radio resources configured in the uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 may send 418 some of the subsequent UL MAC PDUs on the radio resources configured in the CG configuration and send 418 other of the subsequent UL MAC PDUs on the radio resources configured in the uplink grant.
[0106] In the case where the UE 102 sends 418 subsequent UL MAC PDUs on the CG resources, in response to or after generating or sending 418 each of the subsequent UL MAC PDUs, the UE 102 may start or restart a timer (e.g., a second UE CG-SDT timer). The UE 102 may start or restart the timer using a timer value as described above. While the UE timer is running, the UE 102 in an inactive state or SDT session avoids retransmitting the UL MAC PDU. In some implementations, in response to or after receiving 418 each of the subsequent UL MAC PDUs on the CG resources, the DU 174 starts or restarts the DU timer (e.g., a second DU CG-SDT timer) according to the DU timer value. While the DU timer is running, the DU 174 processes the UL transmission received from the UE 102 on the CG resources as a new transmission.
[0107] If the UE 102 includes the UL data in the initial UL MAC PDU 404, the DU 174 retrieves the UL data from the initial UL MAC PDU. In such a case, the DU 174 may include the UL data in the DU to CU message at event 406. Alternatively, the DU 174 may send 415 a DU to CU message including the UL data to the CU-CP 172A. In some such implementations, 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 RRC PDU. As another alternative, the DU 174 may send 416 UL data to the 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.
[0108] After receiving 406 the first DU to CU message, in some implementations, the CU-CP 172A may send 408 a UE context setup request message to the DU 174 to establish a UE context for the UE 102 at the DU 174. In the UE context setup request message, the CU-CP 172A may include transport layer information of one or more GTP-U tunnels between the CU-UP 172B and the DU 174, so that the DU 174 may send UL data and / or subsequent UL data (e.g., in small data communication 418) to the CU-UP 172B via the one or more GTP-U tunnels. In response, the DU 174 may send 410 a UE context setup response message to the CU-CP 172A. After receiving 406 the first DU to CU message, sending 408 the UE context setup request message, or receiving 410 the UE context setup response message, the CU-CP 172A sends 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 sends 414 a bearer context modification response message to CU-CP 172A. After receiving 408 a UE context setup request message or sending 410 a UE context setup response message, such as in the case where the UL data of event 404 includes an RRC message or is associated with an SRB (e.g., SRB1 or SRB2), DU 174 may send 415 a DU to CU message including the UL data to CU-CP 172A. In the case where the UL data is associated with a DRB, DU 174 may send 416 the UL data to CU-UP 172B.
[0109] In some implementations, the CU-CP 172A may include the transport layer information of the CU-UP 172B in the UE context setup request message. The transport layer information of the CU-UP 172B may include an IP address and / or an uplink tunnel endpoint ID (e.g., TEID). The DU 174 may use the transport layer information of the CU-UP 172B to send 416 UL data to the CU-UP 172B. In the event that the UE 102 has subsequent UL data (e.g., one or more UL data packets) to send, the UE 102 may send 418 one or more subsequent UL MAC PDUs including the subsequent UL data to the DU 174. Then, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the event that the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 sends 418 one or more DU to CU messages (e.g., UL RRC messaging messages) including the subsequent UL data to the CU-CP 172A. Each DU to CU message may include a specific UL data packet of subsequent UL data. In the case where the CU-CP 172A receives DL data from the CN 110 or edge server, the CU-CP 172A may send 418 one or more CU to DU messages (e.g., DL RRC messaging messages) including DL data (e.g., one or more DL data packets) to the DU 174. In turn, the DU 174 sends 418 one or more DL MAC PDUs including 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.
[0110] In the case where the subsequent UL data is associated with one or more DRBs, DU 174 sends 418 the subsequent UL data to CU-UP 172B, which is similar to event 416. In some implementations, DU 174 may include DU transport layer information of DU 174 in the UE context setup response message. Subsequently, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. The transport layer information of DU 174 may include an IP address and / or a downlink TEID. In the case where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B may use the transport layer information of DU 174 to send 418 DL data (e.g., one or more DL data packets) to DU 174. Subsequently, DU 174 sends 418 one or more DL MAC PDUs including DL data to UE 102 operating in an inactive state.
[0111] 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.
[0112] In some example scenarios, the subsequent UL data and / or DL data described above include Internet Protocol (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.
[0113] Events 404, 406, 408, 410, 412, 414, 415, and 416 are Figure 4 It is collectively referred to as small data transmission process 492.
[0114] In some implementations, the UL RRC message is an (existing) RRC recovery request message (e.g., an RRCResumeRequest message, an RRCResumeRequest1 message, an RRCConnectionResumeRequest message, or an RRCConnectionResumeRequest1 message). In other implementations, the UL RRC message may be a new RRC recovery request message similar to the existing RRC recovery request message. The new RRC recovery request message may be the format of the existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message may include an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.
[0115] After UE 102 sends 404 UL MAC PDU or communicates 418 subsequent UL data and / or DL data with DU 174, CU-CP 172A may determine to stop SDT of UE 102 based on data inactivity of UE 102 (i.e., UE 102 in an inactive state does not have data activity with base station 104). After UE 102 sends 404 UL MAC PDU or communicates 418 subsequent UL data and / or DL data with DU 174, UE 102 in an inactive state determines or detects data inactivity and sends 420 UE assistance information (e.g., UEAssistanceInformation message) to DU 174 indicating that UE 102 prefers or requests to stop SDT. Subsequently, DU 174 sends 421 a UL RRC messaging message including the UE assistance information to CU-CP 172A. Therefore, CU-CP 172A may determine that UE 102 is in a data inactive state based on the UE assistance information.
[0116] In a further implementation, the DU 174 may perform data inactivity monitoring for the UE 102. The CU-CP 172A may send a CU-to-DU message (e.g., a UE context setup request message of event 408, or a UE context modification request message) to the DU 174 to request or command the DU 174 to perform data inactivity monitoring. In the event that the DU 174 detects or determines that the UE 102 is in a state of data inactivity during the monitoring period, the DU 174 may send 422 an inactivity notification (e.g., a UE inactivity notification message) to the CU-CP 172A. Thus, the CU-CP 172A may determine that the UE 102 is in a state of data inactivity based on the inactivity notification received from the DU 174.
[0117] In a further implementation, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In some implementations, 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, during SDT, the CP to UP message may be a bearer context modification request message (event 412). In the case where CU-UP 172B detects or determines that UE 102 is in a state of data inactivity during monitoring, CU-UP 172B may send 423 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Therefore, CU-CP 172A may determine that UE 102 is in a state of 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 a data inactive state based on UE assistance information, the inactivity notification of event 422 , and / or the inactivity notification of event 423 .
[0118] After a specific period of data inactivity, CU-CP 172A may determine that neither CU 172 nor UE 102 sent any data in the downlink direction or the uplink direction during the specific period. In response to this determination, CU-CP 172A may determine to stop SDT. Alternatively, CU-CP 172A may determine to immediately stop SDT of UE 102 in response to determining that UE 102 is in a state of data inactivity.
[0119] In response to determining that the UE 102 is in a state of data inactivity (for the specific period of time) or determining to cause the UE 102 to transition to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 424 a bearer context modification request message to the CU-UP 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 a state of data inactivity (for the specific period of time) or determining to cause the UE 102 to transition to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 428 a second CU-to-DU message (e.g., a UE context modification request message) to instruct the DU 174 to provide an SDT DU configuration (e.g., a second SDT DU configuration) for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., a field or IE) for requesting an SDT DU configuration in a second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 sends 430 a second DU-to-CU message (e.g., a UE context modification response message) including a 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 a second SDT DU configuration to the CU-CP 172A after receiving the second CU-to-DU message or sending the second DU-to-CU message. In some alternative implementations, the CU-CP 172A may send a second CU-to-DU message and receive a second DU-to-CU message or another DU-to-CU message before determining that the UE 102 is in a data-inactive state.
[0120] In response to determining to cause UE 102 to transition to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., RRCRelease message, RRCConnectionRelease message) to cause UE 102 to transition 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.
[0121] Alternatively, CU-CP 172A may not include the SDT configuration in the RRC release message. In this alternative, CU-CP 172A may indicate to UE 102 in the RRC release message to release or retain the first SDT CU configuration and / or the first SDT DU configuration. For example, CU-CP 172A may include a release indication indicating the release of the first SDT CU configuration or the first SDT DU configuration in the RRC release message. If the RRC release message does not include a release indication, UE 102 retains the first SDT CU configuration and / or the first SDT DU configuration.
[0122] 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 sends 434 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and sends 334 the MAC PDU to the UE 102. The RRC release message instructs the UE 102 to transition to an inactive state. The UE 102 stops the SDT upon receiving 434 the RRC release message and remains 436 in the inactive state.
[0123] Events 420, 421, 422, 423, 424, 426, 428, 430, 432, and 434 are Figure 4 are collectively referred to as SDT completion process 494.
[0124] 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 3 In response to receiving 434 the RRC release message or thereafter, the UE 102 ends the SDT session and 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.
[0125] After UE 102 ends the SDT session, the inactive UE 102 uses a paging RNTI (P-RNTI) to monitor the PDCCH. In some implementations, the CU-CP 172A determines to page the UE 102 to receive a mobile terminated call or data. In response to the determination, the CU-CP 172A may send a CU to DU message (e.g., a paging message) to the DU 174 to request the DU 174 to page the UE 102. In response to the CU to DU message, the DU 174 generates a paging message, a DCI for scheduling a PDSCH transmission including a paging message, and a CRC of the DCI. The DU 174 further uses the P-RNTI to scramble the CRC to obtain the scrambled C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH monitored by the UE 102. The UE 102 receives the DCI and the scrambled CRC on the PDCCH, and verifies the scrambled CRC using the P-RNTI. In the event that the UE 102 verifies that the scrambled CRC is valid, the UE 102 receives and decodes the PDSCH transmission according to the DCI and retrieves the paging message from the PDSCH transmission.
[0126] 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 for indicating to the UE 102 that the first SDT CU configuration is updated using the second SDT CU configuration in the RRC release message. 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 includes a modification indication for indicating to the UE 102 that the first SDT CU configuration is modified using the second SDT CU configuration in the RRC release message. 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 includes a setup indication in the RRC release message for indicating to the UE 102 to replace the first SDT CU configuration with the second SDT CU configuration. In such implementations, the UE 102 may replace the first SDTCU configuration with the second SDT CU configuration in response to the setup indication.
[0127] In some implementations, the second SDT DU configuration is the same as the first SDT DU configuration. In other implementations, the second SDT DU configuration is 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 includes in the second SDT DU configuration an indication for indicating to the UE 102 that the first SDT DU configuration is updated using the second SDT DU configuration. In some such implementations, the UE 102 updates the first SDT DU configuration using the second SDT DU configuration in response to the indication. In other implementations, the DU 174 includes in the second SDT DU configuration a modification indication for indicating to the UE 102 that the first SDT DU configuration is modified using the second SDT DU configuration. In further such implementations, the UE 102 modifies the first SDT DU configuration using the second SDT DU configuration in response to the modification indication. In yet other implementations, DU 174 includes in the second SDT DU configuration a setup indication for indicating to UE 102 to replace the first SDT DU configuration with the second SDT DU configuration. In some such implementations, UE 102 replaces the first SDT DU configuration with the second SDT DU configuration in response to the setup indication.
[0128] 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 to continue to use the first SDT DU configuration and / or the first SDT CU configuration. The release indication indicates the release of 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.
[0129] 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.
[0130] 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).
[0131] Events 420, 421, 422, 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, and 334 may be respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, and 434. After stopping the SDT, the UE 102 may perform 493 another small data transmission process with the base station 104, which is similar to process 492. After completing process 493, the base station 104 may perform 495 an SDT completion process with the UE 102, which is similar to process 494.
[0132] 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.
[0133] In some implementations, DU 174 may not include the SDT DU configuration in the second DU to CU message (e.g., 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 some 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 may not include the CG-SDT configuration in the SDT DU configuration in the second DU to CU message (e.g., 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.
[0134] 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. 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. According to the implementation, before UE 102 initiates SDT, when UE 102 is operating in an inactive state 402, when UE 102 performs SDT (e.g., in a UE context setup request message of event 408 or a CU to DU message of event 428), or when UE 102 is performing SDT as directed to Figure 3 When operating in the connected state, the CU-CP 172A may receive UE capabilities.
[0135] In some implementations, the UE capabilities indicate whether the UE 102 supports CG-SDT. Therefore, the CU-CP 172A can determine whether the UE 102 supports CG-SDT based on the UE capabilities. In some implementations, the CU-CP 172A can receive a DU-to-CU message from the DU 174 indicating whether the DU 174 supports CG-SDT. The DU-to-CU message can be a second DU-to-CU message, a message detailed with respect to event 308 or 316, or a non-UE-associated message (e.g., a non-UE-associated F1AP message as defined in 3GPP specification 38.473).
[0136] In some implementations, the DU 174 determines whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the UE 102 supports CG-SDT. In addition to whether the UE 102 supports CG-SDT, the DU 174 may additionally determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the DU 174 supports CG-SDT. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports or enables CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). DU 174 may receive UE capabilities from CU-CP 172A (e.g., when UE 102 is operating in a connected state or in an inactive state). Thus, DU 174 may determine whether UE 102 supports CG-SDT based on the UE capabilities. In some implementations, DU 174 may send a DU-to-CU message to CU-CP 172A indicating whether DU 174 supports CG-SDT, as described above.
[0137] Reference now Figure 5A , scenario 500A depicts a small data transfer 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. In scenario 500A, 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 transfer process with base station 104, which is similar to event 492.
[0138] During the small data transmission process 592, the CU-CP 172A may determine (e.g., based on the UL or DL data activity of the UE 102) whether to cause the UE 102 to transition to a connected state. In some implementations, the UE 102 may send 503 a non-SDT indication message to the DU 174 to indicate that UL data is available or request a transition to a connected state. In some implementations, the UE 102 may send 503 a non-SDT indication message to the DU 174 on the radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 may use the C-RNTI to receive an uplink grant on the PDCCH from the DU 174, and send 503 a non-SDT indication message to the DU 174 on the radio resources configured in the uplink grant. Subsequently, the DU 174 sends 505 a UL RRC messaging message including a non-SDT indication message to the CU-CP 172A. CU-CP 172A may determine to cause UE 102 to transition 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 to receiving the DL data, sends 507 to CU-CP 172A a DL data notification (e.g., a DL data notification message) indicating that DL data is available for transmission. CU-CP 172A may determine to cause UE 102 to transition to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A may determine to cause UE 102 to transition 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 may determine to cause UE 102 to transition to a connected state in response to receiving the DL data.
[0139] In some implementations, UL data and DL data are associated with radio bearers (e.g., SRBs and / or DRBs). For example, UL data includes an RRC message or a NAS message associated with an SRB. In another example, UL data includes an IP packet associated with a DRB. In some implementations, UE 102 may include the ID of the radio bearer in a non-SDT indication message. Therefore, CU-CP 172A may determine whether to cause UE 102 to transition to a connected state based on the ID. For example, if the radio bearer identified by the ID is not eligible for SDT, CU-CP 172A may determine to cause UE 102 to transition to a connected state. Otherwise, CU-CP 172A may determine not to cause UE 102 to transition to a connected state. In some implementations, UE 102 may include data volume information of UL data in a non-SDT indication message. Therefore, CU-CP 172A may determine whether to cause UE 102 to transition 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 cause the UE 102 to transition to a connected state. Otherwise, the CU-CP 172A may determine not to cause the UE 102 to transition 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 cause the UE 102 to transition to a connected state. Otherwise, the CU-CP 172A may determine not to cause the UE 102 to transition 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 cause the UE 102 to transition to a connected state. Otherwise, CU-CP 172A may determine not to cause UE 102 to transition to the connected state.
[0140] In response to or after determining that UE 102 is caused to transition to a connected state, CU-CP 172A sends 506 a UE context request message (e.g., a UE context setup request message or a UE context modification request message) to DU 174. In response, DU 174 sends 508 a UE context response message (e.g., a UE context setup response message or a UE context modification response message) to CU-CP 172A. In some implementations, DU 174 includes a non-SDT DU configuration (i.e., a first non-SDT DU configuration) in the UE context response message. After receiving the UE context response message, CU-CP 172A sends 510 a CU-to-DU message including an RRC resume message (e.g., an RRCResume message or an RRCConnectionResume message) to DU 174. Subsequently, DU 174 sends 512 an RRC resume message to UE 102. In some implementations, DU 174 sends 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 is a DL RRC messaging message or a UE context modification request message. In the case of a UE context modification request message, in response, DU 174 may send a UE context modification response message to CU-CP 172A. In response to the RRC resume message, UE 102 transitions 513 to a connected state and sends 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 sends 516 a DU to CU message including an RRC resume completion message to CU-CP 172A.
[0141] After determining to cause the UE 102 to transition to the connected state, the CU-CP 172A may send 517 a bearer context request message (e.g., a bearer context setup request message or a bearer context modification request message) to the CU-UP 172B to instruct the CU-UP 172B to resume all suspended radio bearers of the UE 102. In response, the CU-UP 172B resumes all suspended radio bearers of the UE 102 and sends 519 a bearer context response message (e.g., a bearer context setup response message or a bearer context modification response message) to the CU CP-172A. In some implementations, the CU-CP 172A may send 517 the bearer context request message after sending 506 a UE context request message, receiving 508 a UE context response message, sending 510 a CU to DU message, or receiving 516 a DU to CU message. In the event that CU-CP 172A determines that no radio bearers of UE 102 are suspended when determining to cause UE 102 to transition to the connected state, CU-CP 172A does not send 517 a bearer context request message to CU-UP 172B.
[0142] In some implementations, CU-CP 172A may include an indication to DU 174 that a non-SDT configuration is generated 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-SDT DU configuration. In some such implementations, CU-CP 172A includes the second non-SDT DU 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 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 for the first non-SDT DU configuration and the second non-SDT DU configuration are similar to the non-SDT DU configuration described above. In some implementations, DU 174 sends an additional DU to CU message (e.g., 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.
[0143] 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 causes the UE 102 to send a non-SDT indication message. The UL data may also include new UL data that can 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.
[0144] 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.
[0145] 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 causing the UE 102 to transition to a connected state, receiving 510 to a CU to DU message, or sending 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 or after communicating 506 a UE context request message or communicating 508 a UE context response message.
[0146] 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., SDT CU configuration, SDT DU configuration, and / or 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., 514RRC recovery complete message and / or 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., 514RRC recovery complete message and / or 518 data). In some implementations, in response to causing the UE 102 to transition to a connected state or sending an RRC recovery message or thereafter, the base station 104 retains the SDT configuration. In some implementations, the base station 104 avoids using the SDT configuration to communicate with the UE 102 operating in a connected state (e.g., 514RRC recovery complete message and / or 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., 514 RRC recovery complete message and / or 518 data).
[0147] In some implementations, the non-SDT indication message is an RRC message (e.g., a UEAssistanceInformation message or a new RRC message). In such implementations, the UE 102 may continue to perform 518 data communication with the base station 104 after sending the non-SDT indication message. In some implementations, the UE 102 sends a UL MAC PDU including the non-SDT indication message to the CU-CP 172A via the DU 174. In some implementations, the UE 102 includes data in the UL MAC PDU in addition to the non-SDT indication message. In other implementations, the UE avoids including the data in the UL MAC PDU.
[0148] In some implementations, the UE 102 sends a non-SDT indication message to the CU-CP 172A via the DU 174 and the SRB1. In such implementations, in response to determining to send the non-SDT indication message, the UE 102 avoids reestablishing the UE PDCP entity of the SRB1. The UE 102 uses the UE PDCP entity to generate a UL PDCP PDU including the non-SDT indication message, and sends 503, 505 the UL PDCP PDU to the CU-CP 172A via the DU 174. Then, the UE 102 uses the UE PDCP entity to receive 512 a DL PDCP PDU including an RRC recovery message without reestablishing the UE PDCP entity. The CU-CP 172A uses the CU-CP PDCP entity to receive 505 the UL PDCP PDU. In response to receiving the non-SDT indication message, the CU-CP 172A avoids reestablishing the CU-CP PDCP entity of the SRB1. The CU-CP 172A generates DL PDCP PDUs using the CU-CP PDCP entity, and sends 510, 512 the DL PDCP PDUs to the UE 102 via DU 174 and SRB1. The UE 102 generates UL PDCP PDUs including an RRC recovery complete message using the UE PDCP entity, and sends 514, 516 the UL PDCP PDUs to the CU-CP 172A via DU 174 and SRB1. The CU-CP 172A receives 514, 516 the UL PDCP PDUs from the UE 102 via DU 174 using the CU-CP PDCP entity. In these implementations, the UE 102 and the CU-CP 172A communicate PDCP PDUs via SRB1 without reestablishing the UE PDCP entity and the CU-CP PDCP entity.
[0149] In other implementations, the non-SDT indication message may be an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCResumeConnectionRequest message). In such implementations, the UE 102 may stop 518 data communication with the base station 104 to send the non-SDT indication message. In some implementations, the UE 102 sends a non-SDT indication message to the CU-CP 172A via DU174 and SRB0. In some implementations, the UE 102 reestablishes the UE PDCP entity in response to determining to send a non-SDT indication. After reestablishing the UE PDCP entity, the UE 102 uses the UE PDCP entity to receive 512 DL PDCP PDUs. Similarly, the CU-CP 172A reestablishes the CU-CP PDCP entity upon receiving the non-SDT indication message. After re-establishing the CU-CP PDCP entity, the CU-CP 172A generates DL PDCP PDUs using the CU-CP PDCP entity, and sends 510, 512 the DL PDCP PDUs to the UE 102 via DU 174 and SRB1. After re-establishing the UE PDCP entity, the UE 102 generates UL PDCP PDUs including an RRC recovery complete message using the UE PDCP entity, and sends 514, 516 the UL PDCP PDUs to the CU-CP 172A via DU 174 and SRB1. After re-establishing the CU-CP PDCP entity, the CU-CP 172A receives 514, 516 the UL PDCP PDUs from the UE 102 via DU 174 using the CU-CP PDCP entity.
[0150] Prior to performing 592 the small data transfer procedure, the UE 102 operating 502 in the inactive state starts or restarts a first UE CG-SDT timer (e.g., CG-SDT-TAT), such as for Figure 3 and Figure 4 In some implementations, UE 102 may start or restart a first UE CG-SDT timer in response to receiving a timing advance command from DU 174 during a 592 small data transmission process. In some implementations, in response to receiving an RRC recovery message or thereafter, UE 102 maintains (e.g., keeps or does not stop, start or restart) the first UE CG-SDT timer (e.g., CG-SDT-TAT) running. In other implementations, in response to receiving an RRC recovery message or thereafter, UE 102 stops the first UE CG-SDT timer.
[0151] Similarly, the DU 174 may run a first DU CG-SDT timer for the UE 102 operating 502 in the inactive state, such as for Figure 3 and Figure 4 As described. In some implementations, DU 174 may start or restart the first DU CG-SDT timer in response to sending a timing advance command to UE 102. In some implementations, in response to receiving 506 to a UE context request message, sending 508 to a UE context response message, or sending 512 to a recovery message or thereafter, DU 174 maintains (e.g., keeps or does not stop, start or restart) the first DU CG-SDT timer running. In other implementations, in response to receiving 506 to a UE context request message, sending 508 to a UE context response message, or sending 512 to an RRC recovery message or thereafter, DU 174 stops the first DU CG-SDT timer. When the first DU CG-SDT timer expires, DU 174 may release the CG-SDT configuration. Alternatively, when the first DU CG-SDT timer expires, DU 174 retains the CG-SDT configuration and avoids receiving or attempting to receive UL transmissions (e.g., MAC PDUs) on CG resources. In some such implementations, the DU 174 releases the CG resources or determines that the CG resources are invalid.
[0152] In some implementations, the UE 102 in an inactive state may run a second UE CG-SDT timer during the 592 small data transfer process, as described for process 492. In the case where the second UE CG-SDT timer is running, in some implementations, in response to receiving 512 to the RRC recovery message or transitioning 513 to the connected state or thereafter, the UE 102 stops the second UE CG-SDT timer. Alternatively, in response to receiving 512 to the RRC recovery message or transitioning 513 to the connected state or thereafter, the UE 102 maintains the second UE CG-SDT timer. In some implementations, the UE 102 receives an RRC setup message (e.g., an RRCSetup message) instead of an RRC recovery message. In response to receiving the RRC setup message or thereafter, the UE 102 stops the second UE CG-SDT timer and sends an RRC setup completion message to the CU-CP 172A via the DU 174. In other implementations, the UE 102 receives an RRC reject message (eg, an RRCReject message) instead of the RRC resume message. In response to or after receiving the RRC reject message, the UE 102 stops the second UE CG-SDT timer.
[0153] Similarly, DU 174 may run a second DU CG-SDT timer during the small data transfer process 592. In some implementations, DU 174 starts or restarts the second DU CG-SDT timer when or after receiving a PUSCH transmission from UE 102 on the radio resources configured in the CG-SDT configuration. While the second DU CG-SDT timer is running, DU 174 may use the C-RNTI to send the PDCCH. In some implementations in which the second DU CG-SDT timer is running, DU 174 stops the second DU CG-SDT timer in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message or thereafter. In other implementations, DU 174 maintains the second DU CG-SDT timer in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message or thereafter. The DU 174 sends DCI on the PDCCH to the UE 102 operating in the connected state using the C-RNTI that is independent of the second DU CG-SDT timer (eg, running, expired, or stopped).
[0154] Later, the base station 104 may perform a non-SDT configuration process 590 and a process 594 with the UE 102, which are similar to the process 390 and the process 394, respectively. The UE 102 transitions 536 to the inactive state in response to receiving the RRC release message in the process 594. After transitioning to the inactive state, the UE 102 in the inactive state may perform a small data transmission process 593 and an SDT completion process 595 with the base station 104, which are similar to the processes 492 and 494, respectively.
[0155] Next reference Figure 5B , scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC recovery procedure instead of a small data transfer procedure 592. The differences between scenarios 500B and 500A are discussed below.
[0156] In response to initiating the RRC recovery process, the UE 102 in the inactive state sends 542 an RRC recovery request message to the DU 174, which in turn sends 544 an initial UL RRC messaging message including an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCConnectionResumeRequest message) to the CU-CP 172A. In response to receiving the RRC recovery request message, the CU-CP 172A determines to cause the UE 102 to transition to the connected state. In response to or after determining to cause the UE 102 to transition to the connected state, the CU-CP 172A transitions the UE to the connected state as described for scenario 500A.
[0157] In some implementations, the UE 102 generates a UL MAC PDU including the RRC recovery request message and sends 542 the UL MAC PDU to the DU 174. In some implementations, the UE 102 sends 542 the UL MAC PDU to the DU 174 on the radio resources configured in the CG configuration for the SDT. In other implementations, the UE 102 may perform a random access procedure to send the UL MAC PDU, similar to event 404.
[0158] In some implementations, the UE 102 initiates an RRC recovery procedure to send non-SDT data (i.e., data that is not eligible for SDT). More specifically, an upper protocol layer (e.g., a NAS layer) of the UE 102 requests an RRC layer (e.g., RRC 214) of the UE 102 to initiate an RRC recovery procedure. In other implementations, the UE 102 receives a paging message from the DU 174 and initiates an RRC recovery procedure in response to the paging message. In some implementations, the RRC layer (e.g., RRC 214) initiates an RRC recovery procedure in response to the paging message. In yet other implementations, the UE 102 detects that a periodic RAN notification area update (RNAU) timer has expired, and in response, the UE 102 initiates an RRC recovery procedure. In some implementations, the RRC layer (e.g., RRC 214) starts or restarts an RNAU timer, maintains the RNAU timer running, and initiates an RRC recovery procedure in response to the expiration of the RNAU timer.
[0159] Next, refer to FIG. 6A to FIG. 18 Several example methods that may be implemented in one or more base stations, DUs or CUs, or in a RAN to support data communications in an inactive state are discussed.
[0160] Fig. 6AAn example method 600A is illustrated, which may be implemented by a RAN node (eg, base station 104, CU 172, CU-CP 172A, or DU 174) for delaying an SDT resource request from a UE (eg, UE 102).
[0161] Method 600A begins at block 602, where a RAN node determines to configure an SDT for a UE. At block 604, the RAN node generates an SDT configuration in response to the determination, the SDT configuration including a delay configuration for delaying an SDT resource request. At block 606, the RAN node sends a first message (e.g., an RRC release message) including the SDT configuration to the UE (see, e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595). At block 608, the RAN node uses the SDT configuration to perform data communications with the UE operating in an inactive state (see, e.g., events 404, 406, 415, 416, 418, 492, 503, 505, 510, 512, 514, 516, 518, 542, 544, 592).
[0162] In some implementations, the SDT configuration configures one or more SDT radio bearers (RBs). The SDT RBs include SDT SRBs (e.g., SRB1 and / or SRB2) and / or SDT DRBs. The RAN node configures a specific RB ID for each of the SDT RBs. For example, the SDT configuration includes an RB list that includes the RB IDs of the SDT RBs. In some implementations, the SDT configuration may include an indication of SRB2 being suitable for SDT. In such cases, the SDT configuration does not include the RB ID of SRB2. In some implementations, the SDT configuration includes neither the RB ID of SRB1 nor an indication that SRB1 is suitable for SDT. In such cases, SRB1 may be predefined as an SDT RB by default.
[0163] In some implementations, the delay configuration is associated with the first SDT RB. In other implementations, the delay configuration is associated with the first logical channel associated with the first SDT RB. When the UE detects data available for transmission (associated with the first logical channel or the first SDT RB), the UE may trigger the transmission of a buffer status report to report the amount of data of the data to the RAN node. If the UE has no UL resources for sending data or a buffer status report and is configured with a delay configuration, the UE delays the SDT resource request for requesting UL resources for a predetermined time period. In some implementations, the RAN node may configure the predetermined time period. For example, the RAN node sends a delay timer value specifying the predetermined time period to the UE in a first message. In another example, the RAN node sends a delay timer value specifying the predetermined time period to the UE in another message (see, e.g., events 310, 312). In some implementations, upon detecting data available for transmission, the UE starts a delay timer using the delay timer value. While the delay timer is running, the UE avoids sending an SDT resource request to the RAN node for sending a buffer status report or data associated with the first logical channel or the first SDT RB. After the delay timer expires, the UE may send an SDT resource request for sending a buffer status report or data to the RAN node. In some scenarios or implementations, the RAN node does not configure a delay configuration for a (second) SDT RB or a (second) logical channel associated with the second SDT RB. The second SDT RB may be an SDT SRB or an SDT DRB. When the UE detects data available for transmission (associated with or for the second SDT RB), the UE may trigger the transmission of a buffer status report to report the amount of data for the data. If the UE does not have UL resources for sending a buffer status report or data, the UE sends an SDT resource request to the RAN node to request the RAN node to provide UL resources. In some implementations, the UE may receive a delay configuration for other logical channels associated with one or more of the other SDT RBs from the RAN node. In such cases, the UE may apply the delay configuration as described above.
[0164] In other implementations, the delay configuration (i.e., a single delay configuration) applies to all SDT RBs configured in the SDT configuration (e.g., SDT SRBs and / or SDT DRBs). When the UE detects data available for transmission (associated with (one or any of) the SDT radio bearers) and there are no UL resources for transmission of the data, the UE delays the SDT resource request for requesting UL resources to send the data for a predetermined period of time. In some implementations, the RAN node configures the predetermined period of time. For example, the RAN node sends a delay timer value specifying the predetermined period of time to the UE in a first message. In another example, the RAN node sends a delay timer value specifying the predetermined period of time to the UE in a second message (see, e.g., events 310, 312). In yet another example, the delay timer value is a default value (e.g., as defined in the 3GPP specification). In some implementations, the UE starts a delay timer using the delay timer value when or when data available for transmission is detected. While the delay timer is running, the UE avoids sending an SDT resource request to the RAN node for sending data associated with the SDT RB. After the delay timer expires, the UE may send an SDT resource request to the RAN node for sending data.
[0165] In some implementations, the SDT SRBs include SRB0, SRB1, and / or SRB2. In some implementations, the delay configuration is not applicable to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to be sent on SRB0, the UE may send an SDT resource request to the RAN node for sending the UL RRC message. In other implementations, the delay configuration is applicable to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to be sent on SRB0, the UE delays the transmission or initiation of the SDT resource request to the RAN node. In some implementations, the delay configuration is not applicable to SRB1. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., a non-SDT indication message or a UE assistance information message) to be sent on SRB1, the UE may initiate or send an SDT resource request to the RAN node. In other implementations, the delay configuration is applicable to SRB1. In such implementations, when a UE in an inactive state has a UL RRC message (eg, a non-SDT indication message or a UE assistance information message) to send on SRB1, the UE delays transmission or initiation of an SDT resource request to the RAN node.
[0166] In the case where the RAN node is a CU (e.g., CU 172 or CU-CP 172A), the CU generates an SDT configuration (e.g., an SDTCU configuration). In some implementations, the CU obtains a delay configuration and / or a delay timer value from the DU. For example, the CU may receive at least one DU-to-CU message including a delay configuration and / or a delay timer value from the DU (see, e.g., events 308, 330, 430).
[0167] In the case where the delay configuration is associated with a logical channel, the DU may include the logical channel identifier (LCID) of the logical channel in the delay configuration. Alternatively, the DU may generate a container IE (e.g., a logical channel configuration, a non-SDT DU configuration, an SDT DU configuration, a CG configuration, or a CG-SDT configuration) including the delay configuration and the LCID, and include the container IE in the DU to CU message. The CU may include the container IE and / or the delay timer value in the first message or the second message. Alternatively, the delay configuration includes a bitmap in which the bit corresponds to a specific RB ID in the RB list. The DU may set each bit to one of two values (i.e., 0 or 1). One of the two values of the bit in the bitmap (e.g., value 1) indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. Another value of the bit (e.g., value 0) indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB IDs 1, ..., N, where N is a positive integer. The delay configuration may include a bitmap of bits 1, ..., N for RB IDs 1, ..., N, respectively. In order to configure the UE to delay the SDT resource request for the transmission of data associated with RB ID X (1 <= X <= N), the DU may set bit X to a value of 1. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for the SDT RB based on the corresponding bit in the bitmap. In the case where SRB2 is the SDT RB, in some implementations, the DU may include the delay configuration for SRB2 in the DU to CU message. The CU includes the delay configuration specific to SRB2 in the SDT configuration. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for SRB2 based on the SRB2-specific delay configuration. Alternatively, the DU is not configured with a delay configuration for SRB2.
[0168] In other implementations, the CU generates a delay configuration and / or a delay timer value instead of the DU. In the case where the delay configuration is associated with a specific logical channel associated with a specific SDT RB, the CU generates a container IE including the LCID of the logical channel and the delay configuration, and includes the container IE in the SDT configuration. In the case where the delay configuration is associated with a specific SDT RB, the CU generates a container IE including the RB ID of the SDT RB and the delay configuration, and includes the container IE in the SDT configuration. Alternatively, the CU includes the RB ID of the SDT RB in the delay configuration. In a further implementation, the delay configuration includes a bitmap in which a bit corresponds to a specific RB ID in the RB list. The CU can set each bit to one of two values (ie, 0 or 1). One of the two values of the bit in the bitmap indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. The other value of the bit indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB ID 1, ..., N, where N is a positive integer. The delay configuration may include a bitmap for bits 1, ..., N for RB IDs 1, ..., N, respectively. In the case where SRB2 is an SDT RB, in some implementations, the CU includes a delay configuration specific to SRB2 in the SDT configuration. That is, the delay configuration may be specific to SDT SRB2. Alternatively, the DU is not configured with a delay configuration for SDT SRB2.
[0169] In some implementations, the SDT resource request is a random access preamble of a four-step random access procedure or a MsgA of a two-step random access procedure. In some implementations, the SDT resource request is a four-step random access procedure or a two-step random access procedure. In such implementations, "sending an SDT resource request" may be replaced with "initiating an SDT resource request".
[0170] After a predetermined time period has passed or a delay timer has expired, the UE may initiate a four-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a random access preamble to the RAN node. In response to receiving the random access preamble, the RAN node sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE, and the UE 102 sends a UL MAC PDU including data or a portion of the data to the RAN node according to the uplink grant. In some implementations, the UE includes a buffer status report and / or the UE's C-RNTI in the UL MAC PDU. The RAN node receives the UL MAC PDU according to the uplink grant in the RAR. In response to receiving the UL MAC PDU, the RAN node may use the C-RNTI to send a DCI on the PDCCH. More specifically, the RAN node generates a DCI and a CRC for the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the UL MAC PDU, the UE uses the C-RNTI to monitor the PDCCH. When the UE receives the DCI and the scrambled CRC on the PDCCH, the UE verifies the scrambled CRC using the DCI and the C-RNTI. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the four-step random access procedure is successful.
[0171] Further, after a predetermined time period has passed or a delay timer expires, the UE may initiate a two-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a MsgA including a random access preamble and a UL MAC PDU to the RAN node according to the two-step random access configuration parameters. In response to receiving the UL MAC PDU, the RAN node may use the C-RNTI to send DCI on the PDCCH. More specifically, the RAN node generates the DCI and a CRC of the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the UL MAC PDU, the UE attempts to receive the PDCCH using the C-RNTI. When the UE receives the DCI and the scrambled CRC, the UE verifies the scrambled CRC using the DCI and the C-RNTI. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the two-step random access procedure is successful.
[0172] Figure 6B6 is a flow chart of an example method 600B, which is similar to method 600A, except that method 600B includes blocks 603 and 605. At block 603, the RAN node determines whether the SDT is a CG-SDT. If the RAN node determines that CG-SDT is configured for the UE, the process proceeds to Fig. 6A If the RAN node determines to configure RA-SDT for the UE, the flow proceeds to block 605. At block 605, the RAN node generates an SDT configuration in response to the determination, the SDT configuration excluding a delay configuration for delaying the SDT resource request.
[0173] 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 block 613. At block 613, the RAN node determines whether to configure a delay configuration for an SDT radio bearer (RB). If the RAN node determines to configure a delay configuration for an SDT radio bearer (RB), the process proceeds to the above-described Fig. 6A If the RAN node determines not to configure a delay configuration for an SDT radio bearer (RB), the flow proceeds to block 604 as described above with respect to Figure 6B The frame 605 described above.
[0174] In some implementations, the RAN node determines whether to configure a delay configuration for the SDT RB based on one or more QoS parameters of the SDT RB. For example, if the QoS parameter requires a specific delay, the RAN node determines not to configure a delay configuration for the SDT RB. Otherwise, the RAN node determines to configure a delay configuration for the SDT RB.
[0175] Figure 7 An example method 700 is shown that may be implemented by a DU (eg, DU 174) for delaying an SDT resource request from a UE (eg, UE 102).
[0176] Method 700 begins at block 702, where the DU receives a CU-to-DU message from the CU to configure SDT for the UE (e.g., events 328, 394, 428, 494, 495, 594, 595). At block 704, the DU generates a delay configuration for delaying an SDT resource request from the UE. At block 706, the DU sends a DU-to-CU message including the delay configuration to the CU (e.g., events 330, 394, 430, 494, 495, 594, 595). At block 708, the DU sends an RRC release message to the UE including the delay configuration. Fig. 6A Examples and implementations can be applied to Figure 7 .
[0177] Figure 8 A method 800 is illustrated that may be implemented by a DU (eg, DU 174) for delaying a resource request from a UE (eg, UE 102).
[0178] Method 800 begins at block 802, where the DU receives a CU-to-DU message from the CU requesting a lower configuration for the UE (see, e.g., events 306, 328, 394, 428, 494, 495, 594, 595). At block 804, the DU determines whether the CU-to-DU message requests a lower configuration for SDT. If the DU determines at block 804 that the CU-to-DU message requests a lower configuration for SDT, the process proceeds to block 806. At block 806, the DU generates a first delay configuration for the UE. At block 808, the DU sends a DU-to-CU message to the CU including the first delay configuration (see, e.g., events 330, 394, 430, 494, 495, 594, 595). If the DU determines at block 804 that the CU-to-DU message requests a lower configuration for non-SDT operation, the process proceeds to block 810. At block 810, the DU generates a second delay configuration for the UE. At block 812, the DU sends a DU-to-CU message including a second delay configuration to the CU (see, eg, event 308).
[0179] In some implementations, the first delay configuration is configured with respect to Fig. 6A The delay configuration described is similar and specific to Fig. 6A Examples and implementations can be applied to Figure 8 . In some implementations, the second delay configuration is specific to the RB or a logical channel associated with the RB, or is associated with the RB or the logical channel. In some implementations, when operating in an inactive state, the UE applies the first delay configuration during the SDT, and when operating in a connected state, the UE applies the second delay configuration during data communication with the RAN node. For example, the second delay configuration may be logicalChannelSR-DelayTimerApplied. In some such implementations, the DU generates a logical channel configuration (e.g., LogicalChannelConfig) including the second delay configuration and the LCID of the logical channel, and further generates an RLC bearer configuration (e.g., RLC-BearerConfig) including the logical channel configuration and the RB ID of the RB. The DU then includes the RLC bearer configuration in a cell group configuration (e.g., CellGroupConfig). The DU sends a DU to CU message including the cell group configuration to the CU at box 812.
[0180] In some scenarios or implementations, when a UE in a connected state detects data available for transmission (e.g., associated with an RB or a logical channel), the UE may trigger the transmission of a buffer status report to report the amount of data for the data. If the UE has no UL resources for the transmission of the data or buffer status report, the UE in a connected state delays the transmission of an SDT resource request for requesting UL resources for sending data for a predetermined period of time. In some implementations, the UE in a connected state starts a delay timer using a delay timer value in response to the trigger to delay the SDT resource request. While the delay timer is running, the UE in a connected state avoids sending or initiating a non-SDT resource request for sending a buffer status report or data to the DU. After the delay timer expires, the UE in a connected state may initiate or send a non-SDT resource request for sending a buffer status report or data. In some implementations, the non-SDT resource request includes a scheduling request process, a four-step random access process, or a two-step random access process. In some implementations, the non-SDT request is a dedicated scheduling request on a PUCCH, a random access preamble of a four-step random access process, or a MsgA of a two-step random access process.
[0181] Fig. 9 An example method 900 is illustrated, which may be implemented by a RAN node (eg, base station 104, CU 172, CU-CP 172A, or DU 174) for delaying a resource request from a UE (eg, UE 102).
[0182] Method 900 begins at block 902, where a RAN node communicates with a UE (e.g., events 304, 390). At block 904, the RAN node determines to configure the UE to delay SDT resource requests. At block 906, the RAN node sends a first delay configuration to the UE in response to the determination at block 904 (see, e.g., events 332, 334, 394, 432, 434, 494, 495, 595, 595). At block 908, the RAN node determines to configure the UE to delay non-SDT resource requests. At block 910, the RAN node sends a second delay configuration to the UE in response to the determination at block 908 (see, e.g., events 310, 312).
[0183] Examples and implementations for the first delay configuration and the second delay configuration are similar to those for Figure 8 The first delay configuration and the second delay configuration are similar.
[0184] Fig.10An example method 1000 is illustrated, which may be implemented by a RAN node (eg, RAN 105, base station 104, CU 172, CU-CP 172A, or DU 174) for delaying a resource request from a UE (eg, UE 102).
[0185] Method 1000 begins at block 1002, where a RAN node communicates with a UE (e.g., events 304, 390, 404, 406, 418, 420, 492, 493, 592, 593). At block 1004, the RAN node determines to configure the UE to delay resource requests. At block 1006, the RAN node determines whether the resource request is for SDT or non-SDT operation. If the RAN node determines at block 1006 that the resource request is for SDT (i.e., the RAN node determines to delay resource requests for SDT), the flow proceeds to block 1008. At block 1008, the RAN node sends a first delay configuration to the UE (see, e.g., events 332, 334, 394, 432, 434, 494, 495, 595, 595). If the RAN node determines at block 1006 that the resource request is for non-SDT operation (i.e., the RAN node determines to delay resource requests for non-SDT), flow proceeds to block 1010. At block 1010, the RAN node sends a second delay configuration to the UE (see, e.g., events 310, 312).
[0186] Examples and implementations for the first delay configuration and the second delay configuration are similar to those for Figure 8 The first delay configuration and the second delay configuration are similar.
[0187] Fig.11 An example method 1100 is illustrated, which may be implemented by a RAN node (eg, RAN 105, base station 104, CU 172, CU-CP 172A, or DU 174) for delaying a resource request from a UE (eg, UE 102).
[0188] Method 1100 begins at block 1102, where a RAN node communicates with a UE (e.g., events 304, 390, 404, 406, 418, 420, 492, 493, 592, 593). At block 1104, the RAN node determines to configure the UE to delay requesting resources for SDT and non-SDT. At block 1106, the RAN node sends a delay configuration for SDT and non-SDT to the UE in response to the determination (see, e.g., events 310, 312).
[0189] In some implementations, the delay configuration is similar to the second delay configuration described above. The UE in the connected state receives the delay configuration and applies the delay configuration. After transitioning from the connected state to the inactive state, the UE in the inactive state applies the delay configuration in a manner similar to that described for the first delay configuration.
[0190] Fig.12 An example method 1200 may be implemented by a RAN node (eg, RAN 105, base station 104, CU 172, CU-CP 172A, or DU 174) for delaying a resource request from a UE (eg, UE 102).
[0191] Method 1200 begins at block 1202, where a RAN node sends a first plurality of configuration parameters to a UE (see, e.g., events 310, 312, 390, 510, 512). At block 1204, the RAN node uses the first plurality of configuration parameters to communicate with the UE operating in a connected state (see, e.g., events 318, 320, 514, 516, 518). At block 1206, the RAN node sends a second plurality of configuration parameters to the UE (see, e.g., 332, 334, 394, 432, 434, 494, 495, 594, 595). At block 1208, the RAN node uses the second plurality of configuration parameters and a portion of the first plurality of configuration parameters to communicate with the UE operating in an inactive state (see, e.g., events 404, 406, 418, 420, 432, 434, 492, 493, 592, 593).
[0192] In some implementations, the RAN node sends at least one RRC message (e.g., an RRC reconfiguration message and / or an RRC resume message) including the first plurality of configuration parameters to the UE at block 1202. The RAN node may receive an RRC reconfiguration complete message from the UE in response to each of the RRC reconfiguration messages. For example, the RRC message includes an RRC configuration including the first plurality of configuration parameters, such as a cell group configuration (e.g., CellGroupConfig IE), a measurement configuration (e.g., MeasConfig IE), and / or a radio bearer configuration (e.g., RadioBearerConfig IE). The cell group configuration includes an RLC bearer configuration including RLC configuration parameters and a logical channel configuration (e.g., LogicalChannelConfig IE) for RBs configured in the radio bearer configuration. In some implementations, one or more of the logical channel configurations include a delay configuration (e.g., logicalChannelSR-DelayTimerApplied).
[0193] In some implementations, the RAN node sends at least one RRC release message including a second plurality of configuration parameters to the UE. In some implementations, each of the at least one RRC release message includes (a portion of) the second plurality of configuration parameters. For example, at least one RRC release message includes an SDT configuration (e.g., an SDT-Config IE), the SDT configuration including the second plurality of configuration parameters. In some implementations, the SDT configuration includes an SDT DRB list, an SDT SRB2 indication, an SDT-MAC-PHY-Config, an SDT-MAC-PHY-CG-Config, an SDT session timer value, and / or an SDT data volume threshold. In some implementations, the second plurality of configuration parameters may not include a delay configuration. In other implementations, the second plurality of configuration parameters include a delay configuration, as described above.
[0194] In some implementations, a portion of the first plurality of configuration parameters includes configuration parameters in a radio bearer configuration. In some implementations, a portion of the first plurality of configuration parameters at block 1208 includes configuration parameters in a cell group configuration, an RLC bearer configuration, and / or a logical channel configuration.
[0195] Fig.13A An example method 1300A is illustrated, which may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0196] Method 1300A begins at block 1302, where the UE determines data available for transmission during an SDT session. At block 1304, the UE determines whether the UE has UL resources to send data. If the UE determines at block 1304 that the UE has UL resources to send data, the process proceeds to block 1306. At block 1306, the UE sends a UL MAC PDU including data to a first RAN node (e.g., base station 104 or DU 174A of base station 104) during the SDT session (see, e.g., events 418, 420, 492, 493, 592, 593). If the UE determines at block 1304 that the UE does not have UL resources to send data, the process proceeds to block 1308. At block 1308, the UE delays initiation (e.g., transmission) of an SDT resource request for sending data. That is, the UE avoids initiating an SDT resource request for sending data.
[0197] Before performing or initiating an SDT session, the UE receives a first message (e.g., an RRC release message) including an SDT configuration from a first RAN node or a second RAN node (e.g., base station 106, DU 174 of base station 106, or DU 174B of base station 104) (see, e.g., events 332, 334, 394, 432, 434, 494, 495, 594, 595). The UE transitions to an inactive state or remains in an inactive state in response to the RRC release message or the SDT configuration (see, e.g., events 336, 402, 436). Then, the UE initiates or performs an SDT session with the first RAN node according to the SDT configuration (see, e.g., events 404, 492, 493, 592, 593).
[0198] In some implementations, the SDT configuration configures one or more SDT radio bearers (RBs). The SDT RBs include SDT SRBs (e.g., SRB1 and / or SRB2) and / or SDT DRBs. The RAN node (i.e., the first RAN node or the second RAN node) configures a specific RB ID for each of the SDT RBs. For example, the SDT configuration includes an RB list including the RB ID of the SDT RB. In some implementations, the SDT configuration may include an indication of SRB2 that is suitable for SDT. In such cases, the SDT configuration does not include the RB ID of SRB2. In some implementations, the SDT configuration includes neither the RB ID of SRB1 nor an indication that SRB1 is suitable for SDT. In such cases, SRB1 may be predefined as an SDT RB by default. In some implementations, the SDT configuration includes a delay configuration. In other implementations, the UE receives the delay configuration in another message (see, e.g., events 310, 312, 390).
[0199] In some implementations, the delay configuration is associated with the first SDT RB. In other implementations, the delay configuration is associated with the first logical channel associated with the first SDT RB. When the UE detects data available for transmission (associated with the first logical channel or the first SDT RB) at block 1302, the UE may trigger the transmission of a buffer status report to report the amount of data of the data to the RAN node. If the UE has no UL resources for sending data or a buffer status report, the UE delays the SDT resource request for requesting UL resources for a predetermined time period. In some implementations, the RAN node configures the predetermined time period. For example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a first message. In another example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a second message (see, e.g., events 310, 312, 390). In some implementations, the UE starts a delay timer using the delay timer value when or when data available for transmission is detected. While the delay timer is running, the UE avoids sending an SDT resource request to the first RAN node for sending a buffer status report or data associated with the first logical channel or the first SDT RB. After the delay timer expires, the UE may send an SDT resource request to the first RAN node for sending a buffer status report or data. In some implementations, the RAN node does not configure a delay configuration for a (second) SDT RB or a (second) logical channel associated with the second SDT RB. The second SDT RB may be an SDT SRB or an SDT DRB. When the UE detects data available for transmission (associated with or for the second SDT RB), the UE may trigger transmission of a buffer status report to report the amount of data of the data. If the UE has no UL resources for sending the buffer status report or data, the UE sends an SDT resource request to the first RAN node to request the first RAN node to provide UL resources.
[0200] In other implementations, the delay configuration applies to all SDT RBs (e.g., SDT SRBs and / or SDT DRBs) configured with the SDT configuration. When the UE detects data available for transmission (associated with any one of the SDT radio bearers) and there are no UL resources for the transmission of the data, the UE delays the SDT resource request for requesting UL resources to send the data for a predetermined period of time. In some implementations, the RAN node configures the predetermined period of time. For example, the RAN node may send a delay timer value specifying the predetermined period of time to the UE in a first message. In another example, the RAN node may send a delay timer value specifying the predetermined period of time to the UE in a second message (see, e.g., events 310, 312, 390). In yet another example, the delay timer value may be a default value (e.g., as defined in the 3GPP specification). In some implementations, upon detecting data available for transmission, the UE starts a delay timer using the delay timer value. While the delay timer is running, the UE avoids sending an SDT resource request for sending data associated with any one of the SDT RBs to the first RAN node. After the delay timer expires, the UE may send an SDT resource request for sending data to the first RAN node.
[0201] In some implementations, the SDT SRBs include SRB0, SRB1, and / or SRB2. In some implementations, the delay configuration is not applicable to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to be sent on SRB0, the UE may send an SDT resource request to the first RAN node to send the UL RRC message. In other implementations, the delay configuration is applicable to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to be sent on SRB0, the UE delays transmission or initiation of the SDT resource request to the first RAN node. In some implementations, the delay configuration is not applicable to SRB1. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., a non-SDT indication message or a UE assistance information message) to be sent on SRB1, the UE may initiate or send an SDT resource request to the first RAN node. In other implementations, the delay configuration is applicable to SRB1. In such implementations, when a UE in an inactive state has a UL RRC message (eg, a non-SDT indication message or a UE assistance information message) to send on SRB1, the UE delays transmission or initiation of an SDT resource request to the RAN node.
[0202] In the case where the RAN node is a CU (e.g., CU 172 or CU-CP 172A), the CU generates an SDT configuration (e.g., an SDTCU configuration). In some implementations, the CU may obtain a delay configuration and / or a delay timer value from the DU. For example, the CU may receive at least one DU-to-CU message including a delay configuration and / or a delay timer value from the DU (see, e.g., events 308, 330, 430).
[0203] In the case where the delay configuration is associated with a logical channel, the DU may include the logical channel identifier (LCID) of the logical channel in the delay configuration. Alternatively, the DU may generate a container IE (e.g., a logical channel configuration, a non-SDT DU configuration, an SDT DU configuration, a CG configuration, or a CG-SDT configuration) including the delay configuration and the LCID, and include the container IE in the DU to CU message. The CU may include the container IE and / or the delay timer value in the first message or the second message. Alternatively, the delay configuration includes a bitmap in which the bit corresponds to a specific RB ID in the RB list. The DU may set each bit to one of two values (i.e., 0 or 1). One of the two values of the bit in the bitmap (e.g., value 1) indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. Another value of the bit (e.g., value 0) indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB ID1, ..., N, where N is a positive integer. The delay configuration may include a bitmap of bits 1, ..., N for RB IDs 1, ..., N, respectively. In order to configure the UE to delay the SDT resource request for the transmission of data associated with RB ID X (1 <= X <= N), the DU may set bit X to a value of 1. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for the SDT RB based on the corresponding bit in the bitmap. In the case where SRB2 is the SDT RB, in some implementations, the DU may include the delay configuration for SRB2 in the DU to CU message. The CU includes the delay configuration specific to SRB2 in the SDT configuration. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for SRB2 based on the SRB2-specific delay configuration. Alternatively, the DU is not configured with a delay configuration for SRB2.
[0204] In other implementations, the CU generates a delay configuration and / or a delay timer value instead of the DU. In the case where the delay configuration is associated with a specific logical channel to which a specific SDT RB is associated, the CU generates a container IE including the LCID of the logical channel and the delay configuration, and includes the container IE in the SDT configuration. In the case where the delay configuration is associated with a specific SDT RB, the CU generates a container IE including the RB ID of the SDT RB and the delay configuration, and includes the container IE in the SDT configuration. Alternatively, the CU includes the RB ID of the SDT RB in the delay configuration. Alternatively, the delay configuration includes a bitmap in which the bit corresponds to a specific RB ID in the RB list. The CU can set each bit to one of two values (i.e., 0 or 1). One of the two values of the bit in the bitmap indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. The other value of the bit indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB ID 1, ..., N, where N is a positive integer. The delay configuration may include a bitmap of bits 1, ..., N for RB IDs 1, ..., N, respectively. Therefore, the UE may determine whether to delay the transmission or initiation of the SDT resource request for the SDT RB according to the corresponding bits in the bitmap. In the case where SRB2 is the SDT RB, in some implementations, the CU includes a delay configuration specific to SRB2 in the SDT configuration. Therefore, the UE may determine whether to delay the transmission or initiation of the SDT resource request for SRB2 according to the SRB2-specific delay configuration. Alternatively, the DU is not configured with a delay configuration for SRB2.
[0205] In some implementations, the SDT resource request may be a random access preamble of a four-step random access procedure or a MsgA of a two-step random access procedure. In other implementations, the SDT resource request may be a two-step random access procedure. In such implementations, "sending an SDT resource request" may be replaced with "initiating an SDT resource request".
[0206] After a predetermined time period has passed or a delay timer has expired, the UE may initiate a four-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a random access preamble to the RAN node. In response to the random access preamble, the RAN node sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE, and the UE 102 sends a UL MAC PDU including data or a portion of the data to the RAN node according to the uplink grant. In some implementations, the UE includes a buffer status report and / or the UE's C-RNTI in the UL MAC PDU. The RAN node receives the UL MAC PDU according to the uplink grant in the RAR. In response to receiving the UL MAC PDU, the RAN node may use the C-RNTI to send DCI on the PDCCH. More specifically, the RAN node generates the DCI and a CRC of the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the UL MAC PDU, the UE uses the C-RNTI to monitor the PDCCH. When the UE receives the DCI and the scrambled CRC on the PDCCH, the UE verifies the scrambled CRC using the DCI and the C-RNTI. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the four-step random access procedure is successful.
[0207] After a predetermined time period has passed or a delay timer expires, the UE may initiate a two-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a MsgA including a random access preamble and a UL MAC PDU to the RAN node according to the two-step random access configuration parameters. In response to receiving the ULMAC PDU, the RAN node may use the C-RNTI to send DCI on the PDCCH. More specifically, the RAN node generates the DCI and a CRC of the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the ULMAC PDU, the UE attempts to receive the PDCCH using the C-RNTI. When the UE receives the DCI and the scrambled CRC, the UE uses the DCI and the C-RNTI to verify the scrambled CRC. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the two-step random access procedure is successful.
[0208] Fig. 13B1300B, which is similar to method 1300A, except that method 1300B includes blocks 1307 and 1310. At block 1307, the UE determines whether the UE is configured to delay SDT resource requests. If the UE determines at block 1307 that the UE is configured to delay SDT resource requests, the process proceeds to Fig.13A Otherwise, if the UE determines at block 1307 that the UE is not configured to delay the SDT resource request, the flow proceeds to block 1310. At block 1310, the UE initiates an SDT resource request for sending data. That is, the UE sends an SDT resource request to the RAN node (i.e., the first RAN node) at block 1310 to request the RAN node to schedule UL resources for the UE to send data.
[0209] Fig.14A An example method 1400A is illustrated, which may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0210] Method 1400A begins at block 1402, where the UE determines to send a MAC control element during an SDT session. At block 1404, the UE determines whether the UE has UL resources to send the MAC control element. If the UE determines at block 1404 that the UE has UL resources to send the MAC control element, the flow proceeds to block 1406. At block 1406, the UE sends a UL MAC PDU including the MAC control element to a first RAN node (e.g., base station 104 or DU 174A of base station 104) during the SDT session (see, e.g., events 418, 420, 492, 493, 592, 593). If the UE determines at block 1404 that the UE does not have UL resources to send the MAC control element, the flow proceeds to block 1408. At block 1408, the UE delays initiation (e.g., transmission) of an SDT resource request for sending the MAC control element. That is, the UE avoids initiating an SDT resource request for sending the MAC control element.
[0211] Before performing or initiating an SDT session, the UE receives a first message (e.g., an RRC release message) including an SDT configuration from a first RAN node or a second RAN node (e.g., base station 106, DU 174 of base station 106, or DU 174B of base station 104) (see, e.g., events 332, 334, 394, 432, 434, 494, 495, 594, 595). The UE transitions to an inactive state or remains in an inactive state in response to the RRC release message or the SDT configuration (see, e.g., events 336, 402, 436). Then, the UE initiates or performs an SDT session with the first RAN node according to the SDT configuration (see, e.g., events 404, 492, 493, 592, 593).
[0212] In some implementations, the MAC Control Element (CE) may be a Buffer Status Report (BSR) or a Power Headroom Report (PHR).
[0213] In some implementations, the SDT configuration configures one or more SDT radio bearers (RBs). The SDT RBs include SDT SRBs (e.g., SRB1 and / or SRB2) and / or SDT DRBs. The RAN node (i.e., the first RAN node or the second RAN node) configures a specific RB ID for each of the SDT RBs. For example, the SDT configuration includes an RB list including the RB IDs of the SDT RBs. In some implementations, the SDT configuration may include an indication that SRB2 is suitable for SDT. In such cases, the SDT configuration does not include the RB ID of SRB2. In some implementations, the SDT configuration includes neither the RB ID of SRB1 nor the indication that SRB1 is suitable for SDT. In such cases, SRB1 may be predefined as an SDT RB by default. In some implementations, the SDT configuration includes a delay configuration. In other implementations, the UE receives the delay configuration in another message (see, e.g., events 310, 312, 390).
[0214] In yet other implementations, the delay configuration is associated with a MAC control element (e.g., BSR or PHR). If the UE detects that a MAC control element is available for transmission, no UL resources are available for sending a MAC control element, or is configured with a delay configuration, the UE delays initiation or transmission of the MAC control element.
[0215] In some implementations, the delay configuration may be associated with the first SDT RB. In other implementations, the delay configuration may be associated with the first logical channel associated with the first SDT RB. When the UE detects data available for transmission (associated with the first logical channel or the first SDT RB), the UE determines to send a buffer status report (i.e., a MAC control element) at block 1402 to report the amount of data of the data to the RAN node. If the UE has no UL resources for sending the buffer status report and is configured with a delay configuration, the UE delays the SDT resource request for requesting UL resources for a predetermined time period. In some implementations, the RAN node may configure the predetermined time period. For example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a first message. In another example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a second message (see, e.g., events 310, 312, 390). In some implementations, at or when determining to send the buffer status report, the UE starts a delay timer using the delay timer value. While the delay timer is running, the UE avoids sending an SDT resource request for sending the buffer status report to the first RAN node. After the delay timer expires, the UE may send an SDT resource request for sending a buffer status report or data to the first RAN node. In some scenarios or implementations, the RAN node does not configure a delay configuration for a (second) SDT RB or a (second) logical channel associated with the second SDT RB. The second SDT RB may be an SDT SRB or an SDT DRB. When the UE detects data available for transmission (associated with or for the second SDT RB), the UE determines to send a buffer status report to report the amount of data of the data. If the UE has no UL resources for sending the buffer status report or data, the UE sends an SDT resource request to the first RAN node to request the first RAN node to provide UL resources. In some implementations, the UE may receive a delay configuration for other logical channels associated with one or more of the other SDT RBs from the RAN node. In such cases, the UE may apply the delay configuration as described above.
[0216] In other implementations, the delay configuration (i.e., a single delay configuration) applies to all SDT RBs (e.g., SDT SRBs and / or SDT DRBs) configured in the SDT configuration. In some implementations, the delay configuration applies to the transmission of a MAC control element. When the UE detects data available for transmission (associated with (one or any of) the SDT radio bearers), the UE determines to send a buffer status report. If the UE does not have UL resources for the transmission of the buffer status report, the UE delays the SDT resource request for requesting UL resources to send the buffer status report for a predetermined time period. In some implementations, the RAN node may configure the predetermined time period. For example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a first message. In another example, the RAN node may send a delay timer value specifying the predetermined time period to the UE in a second message (see, e.g., events 310, 312, 390). In yet another example, the delay timer value may be a default value (e.g., as defined in the 3GPP specification). In some implementations, upon detecting data available for transmission, the UE starts the delay timer using the delay timer value. While the delay timer is running, the UE avoids sending an SDT resource request for sending a buffer status report to the first RAN node. After the timer expires, the UE may send an SDT resource request for sending a buffer status report to the first RAN node. In some implementations, the SDT SRBs include SRB0, SRB1, and / or SRB2. In some implementations, the delay configuration does not apply to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to send on SRB0, the UE may send an SDT resource request to the first RAN node to send the UL RRC message. In other implementations, the delay configuration applies to SRB0. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., an RRC recovery request message) to send on SRB0, the UE delays transmission or initiation of the SDT resource request to the first RAN node. In some implementations, the delay configuration does not apply to SRB1. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., a non-SDT indication message or a UE assistance information message) to send on SRB1, the UE may initiate or send an SDT resource request to the first RAN node. In other implementations, the delay configuration applies to SRB1. In such implementations, when the UE in an inactive state has an UL RRC message (e.g., a non-SDT indication message or a UE assistance information message) to send on SRB0, the UE delays transmission or initiation of an SDT resource request to the RAN node.
[0217] In the case where the RAN node is a CU (e.g., CU 172 or CU-CP 172A), the CU generates an SDT configuration (e.g., an SDTCU configuration). In some implementations, the CU obtains a delay configuration and / or a delay timer value from the DU. For example, the CU may receive at least one DU-to-CU message including a delay configuration and / or a delay timer value from the DU (see, e.g., events 308, 330, 430).
[0218] In the case where the delay configuration is associated with a logical channel, the DU may include the logical channel identifier (LCID) of the logical channel in the delay configuration. Alternatively, the DU generates a container IE (e.g., a logical channel configuration, a non-SDT DU configuration, an SDT DU configuration, a CG configuration, or a CG-SDT configuration) including the delay configuration and the LCID, and includes the container IE in the DU to CU message. The CU may include the container IE and / or the delay timer value in the first message or the second message. In a further implementation, the delay configuration includes a bitmap in which a bit corresponds to a specific RB ID in the RB list. The DU may set each bit to one of two values (i.e., 0 or 1). One of the two values of the bit in the bitmap (e.g., value 1) indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. Another value of the bit (e.g., value 0) indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB ID1, ..., N, where N is a positive integer. The delay configuration may include a bitmap of bits 1, ..., N for RB IDs 1, ..., N, respectively. In order to configure the UE to delay the SDT resource request for the transmission of data associated with RB ID X (1 <= X <= N), the DU may set bit X to a value of 1. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for the SDT RB based on the corresponding bit in the bitmap. In the case where SRB2 is the SDT RB, in some implementations, the DU may include the delay configuration for SRB2 in the DU to CU message. The CU includes the delay configuration specific to SRB2 in the SDT configuration. Thus, the UE may determine whether to delay the transmission or initiation of the SDT resource request for SRB2 based on the SRB2-specific delay configuration. Alternatively, the DU is not configured with a delay configuration for SRB2.
[0219] In other implementations, the CU generates a delay configuration and / or a delay timer value instead of the DU. In the case where the delay configuration is associated with a specific logical channel in which a specific SDT RB is associated, the CU generates a container IE including the LCID of the logical channel and the delay configuration, and includes the container IE in the SDT configuration. In the case where the delay configuration is associated with a specific SDT RB, the CU generates a container IE including the RB ID of the SDT RB and the delay configuration, and includes the container IE in the SDT configuration. Alternatively, the CU includes the RB ID of the SDT RB in the delay configuration. In other implementations, the delay configuration includes a bitmap in which a bit corresponds to a specific RB ID in the RB list. The CU can set each bit to one of two values (ie, 0 or 1). One of the two values of the bit in the bitmap indicates that the UE delays the SDT resource request for the corresponding RB ID in the RB list. The other value of the bit indicates that the corresponding RB ID in the RB list indicates that the UE is allowed to send an SDT resource request for the corresponding RB ID in the RB list. For example, the RB list includes RB ID 1, ..., N, where N is a positive integer. The delay configuration may include a bitmap of bits 1, ..., N for RB IDs 1, ..., N, respectively. Therefore, the UE may determine whether to delay the transmission or initiation of the SDT resource request for the SDT RB according to the corresponding bits in the bitmap. In the case where SRB2 is the SDT RB, the CU may include a delay configuration specific to SRB2 in the SDT configuration. Therefore, the UE may determine whether to delay the transmission or initiation of the SDT resource request for SRB2 according to the SRB2-specific delay configuration. Alternatively, the DU is not configured with a delay configuration for SRB2.
[0220] In some implementations, the SDT resource request may be a random access preamble of a four-step random access procedure or a MsgA of a two-step random access procedure. In other implementations, the SDT resource request may be a two-step random access procedure. In such implementations, "sending an SDT resource request" may be replaced with "initiating an SDT resource request".
[0221] After a predetermined time period has passed or a delay timer has expired, the UE may initiate a four-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a random access preamble to the RAN node. In response to the random access preamble, the RAN node sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE, and the UE 102 sends a UL MAC PDU including data or a portion of the data to the RAN node according to the uplink grant. In some implementations, the UE includes a buffer status report and / or the UE's C-RNTI in the UL MAC PDU. The RAN node receives the UL MAC PDU according to the uplink grant in the RAR. In response to receiving the UL MAC PDU, the RAN node may use the C-RNTI to send DCI on the PDCCH. More specifically, the RAN node generates the DCI and a CRC of the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the UL MAC PDU, the UE uses the C-RNTI to monitor the PDCCH. When the UE receives the DCI and the scrambled CRC on the PDCCH, the UE verifies the scrambled CRC using the DCI and the C-RNTI. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the four-step random access procedure is successful.
[0222] After a predetermined time period has passed or a delay timer expires, the UE may initiate a two-step random access procedure for sending data associated with a first logical channel or a first SDT RB. In response to the initiation, the UE sends a MsgA including a random access preamble and a UL MAC PDU to the RAN node according to the two-step random access configuration parameters. In response to receiving the ULMAC PDU, the RAN node may use the C-RNTI to send DCI on the PDCCH. More specifically, the RAN node generates the DCI and a CRC of the DCI, scrambles the CRC using the C-RNTI, and sends the DCI and the scrambled CRC on the PDCCH. After sending the ULMAC PDU, the UE attempts to receive the PDCCH using the C-RNTI. When the UE receives the DCI and the scrambled CRC, the UE uses the DCI and the C-RNTI to verify the scrambled CRC. If the UE verifies that the CRC is correct, the UE determines that the contention resolution of the two-step random access procedure is successful.
[0223] Fig. 14B1400B is a flow chart of an example method 1400B, which is similar to method 1400A, except that method 1400B includes blocks 1407 and 1410. At block 1407, the UE determines whether the UE is configured to delay SDT resource requests. If the UE determines at block 1407 that the UE is configured to delay SDT resource requests, the process proceeds to Fig.14A Otherwise, if the UE determines at block 1407 that the UE is not configured to delay the SDT resource request, the flowchart proceeds to block 1410. At block 1410, the UE initiates an SDT resource request for sending a MAC control element. That is, the UE sends an SDT resource request to the RAN node (i.e., the first RAN node) at block 1410 to request the RAN node to schedule UL resources for the UE to send the MAC control element.
[0224] Fig.15 An example method 1500 is shown that may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0225] Method 1500 begins at block 1502, where the UE receives a delay configuration from a RAN (e.g., RAN 105, base station 104 / 106, or DU 174 of base station 104 / 106) (see, e.g., events 332, 334, 394, 432, 434, 494, 495, 594, 595). At block 1504, when operating in an inactive state, the UE applies the delay configuration (see, e.g., events 418, 420, 492, 493, 592, 593). At block 1506, when operating in a connected state, the UE suspends applying the delay configuration (see, e.g., events 513, 514, 518). That is, when operating in a connected state, the UE avoids applying the delay configuration.
[0226] against Fig.13A and Fig.14A The examples and implementations described may be applicable to method 1500A. In some implementations, the UE applies a delay configuration, such as for Fig.13A or Fig.14A In some implementations, a UE in an inactive state runs a delay timer to delay initiation or transmission of an SDT resource request, and in response to or after a transition from the inactive state to the connected state, the UE stops the delay timer. In some implementations, the delay configuration may be specific to the inactive state or SDT.
[0227] In some implementations, in response to or after transitioning to a connected state, the UE releases the delay configuration. In other implementations, in response to or after transitioning to a connected state, the UE retains the delay configuration. Later, the UE in the connected state receives an RRC release message that transitions the UE to an inactive state. If the RRC release message does not indicate the release of the delay configuration, the UE may resume applying the delay configuration after transitioning back from the connected state to the inactive state.
[0228] Fig.16 An example method 1600 is shown that may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0229] Method 1600 begins at block 1602, where the UE receives a delay configuration from a RAN (e.g., RAN 105, base station 104 / 106, or DU 174 of base station 104 / 106) (see, e.g., events 310, 312, 390). At block 1604, when operating in a connected state, the UE applies the delay configuration (see, e.g., events 318, 390, 320, 513, 514, 518). At block 1606, when operating in an inactive state, the UE performs an SDT with the RAN (see, e.g., events 418, 420, 492, 493, 592, 593). The flow proceeds to block 1608 or block 1609. At block 1608, the UE suspends applying the delay configuration during the SDT (see, e.g., events 418, 420, 492, 493, 592, 593). That is, the UE avoids applying the delay configuration during the SDT. In case the delay configuration is applicable only to the connected state, the UE suspends applying the delay configuration during the SDT. At block 1609, the UE applies the delay configuration during the SDT. In case the delay configuration may be applicable to the connected state and the inactive state, the UE applies the delay configuration during the SDT.
[0230] In some implementations, the delay configuration is logicalChannelSR-DelayTimerApplied. The UE may receive a cell group configuration (e.g., CellGroupConfig) from the RAN at block 1602. The cell group configuration includes an RLC bearer configuration (e.g., RLC-BearerConfig). The RLC bearer configuration includes a logical channel configuration (e.g., LogicalChannelConfig), which includes a delay configuration and a logical channel identifier of a logical channel to which the delay configuration applies. A logical channel is associated with an RB. When a UE in a connected state detects data (associated with an RB or a logical channel) available for transmission, the UE determines to send a buffer status report to report the amount of data of the data. If the UE has no UL resources for transmission of data or a buffer status report, the UE delays transmission of an SDT resource request for requesting UL resources to send data for a predetermined period of time. In some implementations, in response to determining to send a buffer status report, the UE in a connected state starts a delay timer using a delay timer value to delay an SDT resource request. While the delay timer is running, the UE avoids sending to the RAN or initiating at the RAN a non-SDT resource request for sending a buffer status report or data. After the delay timer expires, the UE in the connected state may initiate or send a non-SDT resource request for sending a buffer status report or data. In some implementations, the non-SDT resource request includes a scheduling request procedure, a four-step random access procedure, or a two-step random access procedure. In some implementations, the non-SDT request includes a dedicated scheduling request on the PUCCH, a random access preamble of a four-step random access procedure, or a MsgA of a two-step random access procedure.
[0231] In some implementations, the UE applies a delay configuration during the SDT, such as for Fig.13A or Fig.14A described.
[0232] Fig.17 An example method 1700 is shown that may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0233] Method 1700 begins at block 1702, where the UE receives a delay configuration from a RAN (e.g., RAN 105, base station 104 / 106, or DU 174 of base station 104 / 106) (see, e.g., events 310, 312, 390, 332, 334, 394, 432, 434, 494, 495, 594, 595). At block 1704, the UE determines whether the delay configuration applies to a connected state or an inactive state. If the UE determines at block 1704 that the delay configuration applies to a connected state, the process proceeds to block 1706. At block 1706, when operating in a connected state, the UE applies the delay configuration (see, e.g., events 318, 390, 320, 513, 514, 518). In some implementations, the UE in the connected state applies the delay configuration, such as for an inactive state. Fig. 9 Otherwise, if the UE determines at block 1704 that the delay configuration is applicable to the inactive state, then when operating in the inactive state, the UE applies the delay configuration (see, e.g., events 418, 420, 492, 493, 592, 593). In some implementations, the UE in the inactive state applies the delay configuration, such as for Fig.13A or Fig.14A described.
[0234] Fig.18 An example method 1800 is illustrated, which may be implemented by a UE (eg, UE 102) for managing data transmission when the UE operates in an inactive state.
[0235] Method 1800 begins at block 1802, where the UE receives a first plurality of configuration parameters from a RAN (e.g., RAN 105, base station 104 / 106, or DU 174 of base station 104 / 106) (see, e.g., events 310, 312, 390, 510, 512). At block 1804, while operating in a connected state, the UE communicates with the RAN using the first plurality of configuration parameters (see, e.g., events 318, 320, 514, 516, 518). At block 1806, the UE receives a second plurality of configuration parameters from the RAN (see, e.g., 332, 334, 394, 432, 434, 494, 495, 594, 595). At block 1808, while operating in the inactive state, the UE communicates with the RAN using the second plurality of configuration parameters and a portion of the first plurality of configuration parameters (see, e.g., events 404, 406, 418, 420, 432, 434, 492, 493, 592, 593).
[0236] In some implementations, the UE receives at least one RRC message (e.g., an RRC reconfiguration message and / or an RRC resume message) from the RAN at block 1802 that includes the first plurality of configuration parameters. The UE may send an RRC reconfiguration complete message to the RAN in response to any of the RRC reconfiguration messages. For example, the at least one RRC message includes an RRC configuration including the first plurality of configuration parameters, such as a cell group configuration (e.g., CellGroupConfig IE), a measurement configuration (e.g., MeasConfig IE), and / or a radio bearer configuration (e.g., RadioBearerConfig IE). The cell group configuration includes an RLC bearer configuration that includes RLC configuration parameters and a logical channel configuration (e.g., LogicalChannelConfig IE) for an RB configured according to the radio bearer configuration. In some implementations, one or more of the logical channel configurations include a delay configuration (e.g., logicalChannelSR-DelayTimerApplied)
[0237] In some implementations, the UE receives at least one RRC release message including a second plurality of configuration parameters from the RAN at block 1806. In some implementations, each of the at least one RRC release message includes (a portion of) the second plurality of configuration parameters. For example, at least one RRC release message includes an SDT configuration (e.g., an SDT-Config IE), the SDT configuration including the second plurality of configuration parameters. In some implementations, the SDT configuration includes an SDT DRB list, an SDT SRB2 indication, an SDT-MAC-PHY-Config, an SDT-MAC-PHY-CG-Config, an SDT session timer value, and / or an SDT data volume threshold. In some implementations, the second plurality of configuration parameters may not include a delay configuration. In other implementations, the second plurality of configuration parameters include a delay configuration, as described above.
[0238] In some implementations, a portion of the first plurality of configuration parameters includes configuration parameters in a radio bearer configuration. In some implementations, a portion of the first plurality of configuration parameters at block 1808 includes configuration parameters in a cell group configuration, an RLC bearer configuration, and / or a logical channel configuration.
[0239] The following description can be applied to the above description.
[0240] In general, a description of one of the above figures may apply to another of the above figures. In some implementations, "message" is used and "information element (IE)" may be used to replace "message", and vice versa. In some implementations, "IE" is used and "field" may be used to replace "IE", and vice versa. In some implementations, "configuration" may be replaced with "configurations" or "configuration parameters", and vice versa. In some implementations, "small data transfer" may be replaced with "early data transfer (EDT)", and "SDT" may be replaced with "EDT", and vice versa. In some implementations, "small data transfer" may be replaced with "small data communication", and vice versa. In some implementations, "stop" may be replaced with "pause".
[0241] In some implementations, the “second UE CG-SDT timer” may be replaced with the “CG-SDT retransmission timer (cg-SDT-RetransmissionTimer)”. In some implementations, “CG-SDT”, “CG”, and “SDT-CG” may be interchangeable.
[0242] 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.
[0243] 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.
[0244] 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 of sending a control element (CE) to a radio access network (RAN), the method being implemented in a user equipment (UE) and comprising: When the UE is performing a small data transfer (SDT) procedure, determining that resources for sending the CE to the RAN are unavailable; as well as Responsive to the determination and in accordance with a delay configuration, transmission of the request for the resources to the RAN is delayed.
2. The method of claim 1, wherein the delay configuration is specific to a logical channel associated with the SDT process.
3. The method of claim 2, further comprising: A radio link control (RLC) bearer configuration including a logical channel configuration is received from the RAN, the logical channel configuration including the delay configuration and a logical channel identification of the logical channel. The method of claim 3 , wherein the logical channel configuration is a LogicalChannelConfig field.
5. The method of claim 1, wherein the delay configuration is specific to a radio bearer (RB) associated with the SDT procedure.
6. The method according to any one of the preceding claims, further comprising: The delay configuration is received in an SDT configuration, the SDT configuration specifying a set of RBs for the SDT process.
7. The method according to any one of claims 1 to 5, further comprising: The delay configuration is received in a non-SDT configuration.
8. The method of claim 6 or 7, wherein the receiving of the delay configuration comprises: A radio resource control (RRC) reconfiguration message is received.
9. The method of any of the preceding claims, wherein the delay configuration comprises a logicalChannelSR-DelayTimerApplied indicator.
10. The method of claim 1, further comprising: receiving the delay configuration from the RAN; as well as determining whether the delay configuration is applicable to the SDT process or a non-SDT process; as well as Further in response to determining that the delay configuration is applicable to the SDT process, the transmission of the request for the resource is delayed according to the delay configuration.
11. The method of any one of the preceding claims, wherein the CE is a Medium Access Control (MAC) CE.
12. The method of claim 8, wherein the MAC CE comprises a buffer status report (BSR).
13. The method of claim 9, further comprising: The BSR is generated in response to detecting data available for transmission to the RAN using the SDT procedure.
14. A method as claimed in any one of the preceding claims, wherein: The delay configuration includes a value of a delay timer; The delays include: activating the delay timer, avoiding the transmission of the request for the resource while the delay timer is running, and After expiration of the delay timer, the request for the resource is sent to the RAN.
15. A user equipment, comprising: Transceiver; as well as Processing hardware configured to implement a method according to any one of the preceding claims.
16. A method for configuring a user equipment (UE), the method being implemented in a radio access node (RAN) and comprising: generating a delay configuration according to which the UE is to delay requesting resources for transmission to the RAN during a small data transfer (SDT) procedure; sending the delay configuration to the UE; and The request for the resources is received from the UE according to the delay configuration. 17 . The method of claim 16 , wherein the transmitting of the delay configuration is performed when the UE operates in a connected state of a protocol for controlling radio resources between the UE and the RAN.
18. The method of claim 15 or 16, wherein the sending of the delay configuration comprises sending a command for reconfiguring a radio connection between the UE and the RAN.
19. The method of claim 15 or 16, wherein the sending of the delay configuration comprises sending a command for releasing a radio connection between the UE and the RAN.
20. The method of claim 19, wherein: The delay configuration is an SDT delay configuration; The method further comprises: A command for reconfiguring a radio connection between the UE and the RAN is sent to the UE, the command for reconfiguring the radio connection comprising a non-SDT delay configuration.
21. The method of claim 16 or 17, wherein the generating of the delay configuration comprises: A common configuration for the SDT process and the non-SDT process is generated.
22. The method of claim 16 or 17, wherein the generating of the delay configuration comprises: generating a first delay configuration for the SDT process, and A second delay configuration is generated for the non-SDT process.
23. The method of claim 16, wherein the method is implemented in a distributed base station including a central unit (CU) and a distributed unit (DU), the method comprising: sending, from the CU to the DU, a radio resource control (RRC) reconfiguration including the delay configuration; as well as The RRC reconfiguration is sent from the DU to the UE.
24. The method of any one of claims 17 to 20 or 23, wherein the delay configuration is specific to a logical channel associated with the SDT procedure.
25. The method of claim 24, wherein sending the delay configuration comprises sending a radio link control (RLC) bearer configuration comprising a logical channel configuration, the logical channel configuration comprising the delay configuration and a logical channel identification of the logical channel.
26. The method of claim 25, wherein the logical channel configuration is a LogicalChannelConfig field.
27. The method of any one of claims 16 to 26, wherein the delay configuration comprises a logicalChannelSR-DelayTimerApplied indicator.
28. The method of any one of claims 16 to 27, further comprising: providing the resource to the UE; as well as A medium access control (MAC) control element (CE) is received from the UE on the resource.
29. The method of claim 28, wherein the MAC CE comprises a buffer status report (BSR).
30. A node in a radio access network (RAN), the node comprising: Transceiver; as well as Processing hardware configured to implement the method according to any one of claims 16 to 29.
