Managing small data transmissions with network

By supporting RA-SDT or CG-SDT determination in UE and RAN nodes, and employing appropriate transmission methods for data encryption and integrity protection, the problem of low data transmission efficiency in small data transmission under RRC_INACTIVE or RRC_IDLE states is solved, and efficient data transmission in inactive states is achieved.

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

Patent Information

Application Number
CN202380032220.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-08
Filing Date
2023-04-06
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In RRC_INACTIVE or RRC_IDLE states, during small data transmission (SDT) between the user equipment (UE) and the radio access network (RAN), existing technologies fail to effectively manage whether the UE and RAN nodes support RA-SDT or CG-SDT, resulting in low transmission efficiency and wasted resources.

Method used

Based on whether the UE and the RAN node support RA-SDT or CG-SDT, the UE determines which transmission method to use through a random access procedure or configuration authorization, and performs data transmission in the inactive state, including data encryption and integrity protection, and uses the configured SDT resources for uplink and downlink communication.

Benefits of technology

It improves data transmission efficiency in inactive states, reduces resource waste, and enables efficient small data transmission in RRC_INACTIVE or RRC_IDLE states.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure FT_1
    Figure FT_1
  • Figure FT_2
    Figure FT_2
  • Figure FT_3
    Figure FT_3
Patent Text Reader

Abstract

A radio access network (RAN) and a user equipment (UE) may implement a method for managing small data transmissions (SDT). The method comprises: (i) operating in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; (ii) receiving an SDT configuration from the RAN; and (iii) performing a communication procedure with the RAN node to transmit or receive small data based on whether the UE and the RAN node support a random access procedure dependent SDT type.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of the filing date of Provisional U.S. Patent Application No. 63 / 329,333, entitled “MANAGING SMALL DATA TRANSMISSION WITH A NETWORK,” filed on April 8, 2022. The entire contents of the provisional application are hereby expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to uplink and / or downlink data communications 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

[0004] This background description is provided to generally present the context of the present disclosure. The work of the presently named inventors is neither explicitly nor implicitly admitted to be prior art to the present disclosure to the extent that it is described in this background section and in all aspects that may not have otherwise qualified as prior art at the time of filing.

[0005] Typically, a base station operating a cellular radio access network (RAN) uses a certain radio access technology (RAT) and multiple layers of a protocol stack to communicate with a user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the media access control (MAC) sublayer, which provides a logical channel to the radio link control (RLC) sublayer. The RLC sublayer similarly provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.

[0006] 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 to allow 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 a relatively small packet to send. A small data transfer (SDT) procedure can support data transmission for a UE operating in the RRC_INACTIVE state without transitioning to the RRC_CONNECTED state.

[0007] The device enables SDT for a specific radio bearer. The UE may initiate SDT 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. In addition, the UE may initiate the SDT process by transmission on the random access channel (RACH) as part of a random access SDT (RA-SDT) session, or by transmission on type 1 configured grant (CG) resources as part of a CG-SDT session. For RA-SDT, the network configures 2-step and / or 4-step random access resources for SDT transmission. In a RA-SDT session, the UE may perform an initial transmission including data in message 3 (MSG3) of a 4-step random access procedure or in message A (MSGA) of a 2-step random access procedure. Then, after the random access procedure is completed, the network may schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.

[0008] The UE can initiate a CG-SDT session with only valid uplink (UL) timing alignment. The UE uses the network-configured SDT-specific timing alignment timer and the downlink (DL) RSRP of the configured number of highest-ranked synchronization signal blocks (SSBs) to maintain UL timing alignment. After the SDT-specific timing alignment timer expires, the UE releases the CG resources. After initiating CG-SDT, the UE uses the CG to perform an initial transmission including data during the CG opportunity, and the network can use dynamic grants to schedule subsequent uplink transmissions. Alternatively, uplink transmissions can be performed during subsequent CG resource opportunities. During the CG-SDT, the base station uses dynamic assignments to schedule downlink transmissions. The UE can initiate subsequent uplink transmissions only after receiving confirmation of the initial transmission from the network.

[0009] However, in some scenarios and implementations, the UE may be connected to a radio access network (RAN) node including one or more base stations. In further scenarios and implementations, the UE may receive a CG configuration that configures CG resources from a base station of the RAN. When the RAN configures the CG configuration for the UE, it is unclear whether the UE can perform a random access procedure to send SDT data. Summary of the invention

[0010] The UE manages small data transmission with a network (e.g., RAN) including a network node. The UE operates in an inactive state and receives an SDT configuration from the RAN. The UE then performs a communication process with the network node based at least on whether the UE or the network node supports RA-SDT communication and / or whether the SDT conditions are met. Depending on the implementation, the communication process may further depend on whether the UE or the network node supports CG-SDT and / or whether the conditions for CG-SDT are met. The communication process may be any one of a CG-SDT process, a RA-SDT process, or an RRC recovery process.

[0011] The UE may further perform a random access procedure during the CG-SDT procedure, in response to initiation of the RRC recovery procedure, or during some other time period. The UE may then determine whether to send data via a configured grant or a dynamic grant based on the time at which the random access procedure occurs. In some implementations, the UE further makes the determination based on whether the UE and / or the RAN supports RA-SDT.

[0012] An example embodiment of these techniques is a method for managing a small data transfer (SDT) with a radio access network (RAN) including a RAN node, the method being implemented in a user equipment (UE). The method includes operating in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; receiving an SDT configuration from the RAN; and performing a communication procedure with the RAN node to send or receive small data based on whether the UE and the RAN node support an SDT type that depends on a random access procedure.

[0013] Another example embodiment of these techniques is a method for managing a small data transfer (SDT) with a radio access network (RAN) including a RAN node, the method being implemented in a user equipment (UE). The method includes receiving an SDT configuration from the RAN node; performing a random access procedure; and sending a data packet to the RAN node on one of a configured grant or a dynamic grant based at least on whether the UE and the RAN node support an SDT type that depends on the random access procedure. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] 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 managing small data transmissions;

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

[0016] Figure 2A yes Figure 1AA block diagram of an example protocol stack according to which a UE communicates with a base station;

[0017] 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;

[0018] Figure 3 An example scenario is shown in which the UE communicates with the DU of the RAN using a non-SDT configuration before the UE receives an SDT configuration from the DU and transitions to an inactive state;

[0019] Figure 4 An example scenario is shown in which the UE communicates with the DU of the RAN in an inactive state before the UE receives an SDT configuration from the DU and remains in an inactive state;

[0020] Figure 5A An example scenario is shown in which the UE transitions from an inactive state to a connected state before the UE receives an SDT configuration from a DU and transitions back to an inactive state;

[0021] Figure 5B Shown with Figure 5A A similar scenario, but where the UE does not initially communicate small data with the DU when in the initial inactive state;

[0022] Figure 6 An example scenario is shown in which the UE communicates with the DU of the RAN while in an inactive state, but as part of the SDT communication, the base station retrieves the context of the UE from another base station;

[0023] Fig. 7A is a flow chart of an example method implemented in a UE for determining whether to perform an SDT or RRC recovery procedure based on whether the UE supports RA-SDT communications;

[0024] Figure 7B It is implemented in UE and Fig. 7A A flow chart of a similar example method, but wherein the determination is made based on whether the RAN supports RA-SDT communications;

[0025] Figure 7C It is implemented in UE and Fig. 7A A flow chart of a similar example method, but wherein the determination is made based on whether the UE and the RAN support RA-SDT communications;

[0026] Figure 8 is a flow chart of an example method implemented in a UE for determining whether to perform an SDT or RRC recovery procedure based on whether the UE and / or RAN supports RA-SDT communication and whether conditions for initiating RA-SDT communication are met;

[0027] Fig. 9 is a flow chart of an example method implemented in a UE for determining whether to perform an SDT or RRC recovery procedure based on whether the UE and / or RAN supports RA-SDT communications and whether conditions for initiating RA-SDT and / or CG-SDT communications are met;

[0028] Fig.10 is a flow chart of an example method implemented in a UE for performing CG-SDT communication according to a CG-SDT configuration and subsequently performing a random access procedure during the CG-SDT communication;

[0029] Fig.11 is a flow chart of an example method implemented in a UE for determining whether to configure RA-SDT based on whether the UE supports RA-SDT communication and whether conditions for initiating RA-SDT communication are met;

[0030] Fig.12 is a flow chart of an example method implemented in a UE for determining whether to include SDT data in a data packet based on whether the UE and / or RAN supports RA-SDT communications;

[0031] Fig.13 is a flow chart of an example method implemented in a UE for determining whether to send a data packet using a configured grant or a dynamic grant based on whether the UE performs a random access procedure during CG-SDT communication;

[0032] Fig.14 is a flow chart of an example method implemented in a UE for managing small data transmissions with the UE; and

[0033] Fig.15 is a flow chart of an example method implemented in a UE for managing small data transmissions with the UE. DETAILED DESCRIPTION

[0034] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure for managing early / small data communications and transitioning the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, small data communications may refer to small data transmission (SDT) from a network perspective (i.e., SDT in a downlink direction), or SDT from a UE perspective (i.e., SDT in an uplink direction).

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

[0036] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104, 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).

[0037] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally speaking, UPF 162 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging, and other related functions, and SMF 166 is configured to manage PDU sessions.

[0038] like Figure 1A As shown, base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or handover from one of cells 124 and 126 to the other. In order to exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0039] As discussed in detail below, the UE 102 and / or RAN 105 utilize techniques of the present disclosure when a radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 operates 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.

[0040] As used in the present disclosure, the term "data" or "data packet" refers to signaling, control plane information at the protocol layer for controlling radio resources (e.g., RRC), controlling mobility management (MM), controlling session management (SM); or non-signaling, non-control plane information at the protocol layer above the layer of the protocol for controlling radio resources (e.g., RRC), above the layer of the protocol for controlling mobility management (MM), above the layer of the protocol for controlling session management (SM), or above the layer of the protocol for controlling quality of service (QoS) flow (e.g., Service Data Adaptation Protocol (SDAP)). Some non-signaling, non-control plane information may be referred to as user plane data. The data to which the UE 102 and / or RAN 105 apply the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. In addition, as discussed below, in some implementations, the UE 102 applies these techniques only if the size of the data is below a certain threshold.

[0041] In the example scenario discussed below, UE 102 transitions to the RRC_INACTIVE or RRC_IDLE state, selects a cell of base station 104, and exchanges data with base station 104 (via base station 106 or directly with base station 104) without transitioning to the RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for 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 a UL RRC message in a second UL PDU along with the first UL PDU, and send the second UL PDU to RAN 105. UE 102 includes a UE identity / identifier (ID) of UE 102 in the UL RRC message. RAN 105 may identify UE 102 based on the UE ID. In some implementations, the UE ID is 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).

[0042] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 generates 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 encrypts the 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 generates a MAC-I for protecting the integrity of the data and encrypts the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 sends the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.

[0043] 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 security functions to the SDU and includes the secure SDU in a first UL PDU (e.g., UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which is associated with a media access control (MAC) layer depending on the implementation. Therefore, in such a case, the UE 102 sends a secure UL PDCP PDU in the UL MAC PDU. In some implementations, the UE 102 includes the UL RRC message in the UL MAC PDU. In further implementations, the UE 102 does not include the UL RRC message in the UL MAC PDU. In some such cases, the UE 102 does 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 includes the UL PDCP PDU in a UL radio link control (RLC) PDU, and then includes the UL RLC PDU in a UL MAC PDU. In some implementations where the UE 102 includes the UL RRC message in the UL MAC PDU, the UE 102 generates an RRC MAC-I and includes the RRC MAC-I in the UL RRC message. For example, the RRC MAC-I is a resumeMAC-I field, as specified in 3GPP specification 38.331. In further implementations, the UE generates an RRC MAC-I field using an integrity key (e.g., K RRCint The UE may obtain the RRC MAC-I from the UL RRC message by including the following parameters: a key, an integrity protection algorithm, and / or 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). In some implementations, the UE sets the bits of COUNT, BEARER, and DIRECTION to binary ones to generate the RRC MAC-I.

[0044] In a further implementation, the data is a UL service data unit (SDU) of NAS. The UE 102 applies a security function to the SDU and includes the secure SDU in a first UL PDU (such as a NAS PDU), which may be associated with a NAS layer. For example, depending on the implementation, the NAS layer is an MM sublayer or an SM sublayer of 5G, an evolved packet system (EPS), or 6G. Then, in some implementations, the UE 102 includes the UL NAS PDU in a second UL PDU (such as a UL RRC message). Therefore, in such a case, the UE 102 sends a (first) secure UL NAS PDU in the UL RRC message. In some implementations, the UE 102 includes the UL RRC message in a UL MAC PDU and sends the UL MAC PDU to a base station (e.g., base station 104 or 106) via a cell (e.g., cell 124 or 126). In this case, the UE 102 does not include the RRC MAC-I in the UL RRC message. Alternatively, UE 102 includes RRC MAC-I as described above.

[0045] In some implementations, the UL RRC message described above is a common control channel (CCCH) message, an RRC recovery request message, or an RRC early data request message. In further implementations, the UL RRC message includes the UE ID of the UE 102 as described above.

[0046] More generally, the UE 102 may secure data using at least one of ciphering and integrity protection, include the secured data as a security-protected packet in a first UL PDU, and send the first UL PDU to the RAN 105 in a second UL PDU.

[0047] In some scenarios and implementations, the base station 106 retrieves the UE ID of the UE 102 from the UL RRC message and identifies 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 multiple 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 operates 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.

[0048] When the security-protected packet is an encrypted packet, the base station 104 decrypts the encrypted packet by using at least one security key (e.g., an encryption and / or decryption key) to obtain data. In some implementations, if the security-protected packet is an integrity-protected packet, the integrity-protected packet includes data and MAC-I. The base station 104 can verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., an integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. In a further implementation, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet includes an encrypted packet and an encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.

[0049] In a further 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 the 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., an encryption and / or decryption key).

[0050] In some implementations, if the security-protected packet is an integrity-protected packet, the integrity-protected packet includes data and MAC-I. The base station 106 can verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., an integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. In addition, in an implementation in which the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet includes an encrypted packet and an 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. Then, the base station 106 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.

[0051] In other scenarios and implementations, the base station 104 retrieves the UE ID of the UE 102 from the UL RRC message and identifies that the base station 104 stores the UE context information of the UE 102. Accordingly, the base station 104 retrieves the security-protected packet from the first UL PDU, retrieves the data from the security-protected packet, and sends the data to the CN 110 or edge server, as described above.

[0052] Furthermore, 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.

[0053] For example, when the base station 104 determines that the data is available for downlink transmission to the UE 102 currently operating in the RRC_INACTIVE or RRC_IDLE state, the base station 104 applies at least one security function to the data to generate a security-protected packet, a first DL PDU including the security-protected packet, and includes the first DL PDU in the second DL PDU. Depending on the implementation, in order to make the data secure, the base station 104 applies 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. In addition, in an implementation in which both integrity protection and encryption are enabled, the base station 104 generates a MAC-I for protecting the integrity of the data and encrypts 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.

[0054] In a further implementation, the base station 104 sends the first DL PDU to the base station 106, which then generates a second PDU (e.g., DL MAC PDU) including the first DL PDU and sends the second 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 a further 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.

[0055] 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, depending on the implementation, the RNTI is 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 the 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 assigns 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 assigns 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, such as when UE 102 is in the RRC_CONNECTED state.

[0056] In some implementations, a UE 102 operating in an RRC_INACTIVE or RRC_IDLE state receives a DCI and a scrambled CRC on a PDCCH. The UE 102 then confirms that a physical downlink shared channel (PDSCH) including a second DLPDU is addressed to the UE 102 based on the ID of the UE 102, the DCI, and the scrambled CRC. The UE 102 then retrieves data from the security-protected packet. If the security-protected packet is an encrypted packet, the UE 102 may decrypt the encrypted packet using an appropriate decryption function and a security key to obtain the data. If the security-protected packet is an integrity-protected packet including data and a MAC-I, the UE 102 may determine whether the MAC-I is valid. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves the data. However, if the UE 102 determines that the MAC-I is invalid, the UE 102 discards the packet. In addition, in an implementation where the security-protected packet is both encrypted and integrity-protected (having encrypted data and encrypted MAC-I), the UE 102 decrypts 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.

[0057] 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 that stores instructions executed by 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 procedure 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: send DL PDCP PDUs in some scenarios, according to which the base station 104 can send data in the downlink direction; and receive UL PDCP PDUs in other scenarios, according to which the base station 104 can receive 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, which 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. Specifically, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to components 130, 132, 134, 136, and 138, respectively.

[0058] 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 special-purpose processing units. In an example implementation, 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, 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 uplink MAC protocol data units (PDUs) to the base station, and receive downlink MAC PDUs from the base station. The processing hardware 150 may also include a PDCP controller 154 configured to: transmit a DL PDCP PDU in some scenarios, according to which the base station 106 may transmit data in a downlink direction; and receive a UL PDCP PDU in further scenarios, according to which the base station 106 may receive data in an 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.

[0059] 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 that can be executed 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 includes a radio link control (RLC) controller that is configured to manage or control one or more RLC operations or processes. In further implementations, the CU 172 does not include an RLC controller.

[0060] Each of the DUs 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or a dedicated processing unit. For example, the processing hardware may include: a MAC controller (e.g., MAC controllers 132, 142) 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.

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

[0062] In some implementations, the CU 172 includes a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. In further implementations, the CU 172 includes 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. Depending on the implementation, the CU-CP 172A sends control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B sends data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0063] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the requested service of UE 102. In some implementations, a single CU-UP 172B is 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 is connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such an implementation, CU-CP 172A establishes connectivity between CU-UP 172B and DU 174 by using a bearer context management function.

[0064] Figure 2AAn example protocol stack 200 is shown in a simplified manner, according to which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or both of base stations 104, 106).

[0065] 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. In some implementations, the NR PDCP sublayer 210 then provides data 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 shown, the UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210.

[0066] 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). Unless the difference between SDUs and PDUs is relevant, for simplicity, this disclosure refers to both SDUs and PDUs as "packets".

[0067] In some implementations, for example, on the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2AIn the embodiment of the present invention, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may be used to exchange RRC messages or non-access stratum (NAS) messages. In a further implementation, on the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 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.

[0068] Figure 2B An example protocol stack 250 is shown in a simplified manner, via which the UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally 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.

[0069] Next, follow-up reference Figures 3 to 6 To discuss the Figure 1A Several components of and several example scenarios related to sending data in an inactive or idle state. In order to simplify the following description, "inactive state" is used and it can represent RRC_INACTIVE or RRC_IDLE state, and "connected state" is also used and it can represent RRC_CONNECTED state.

[0070] First reference Figure 3, the figure shows a scenario 300 in which a base station 104 includes a central unit (CU) 172 and a distributed unit (DU) 174. CU 172 further includes CU-CP 172A and CU-UP 172B. In scenario 300, UE 102 initially operates in a connected state 302 and communicates 304 with DU 174, such as by using a DU configuration (i.e., a first non-SDT DU configuration). UE 102 further communicates 304 with CU-CP 172A and / or CU-UP 172B via the DU by using the CU configuration (i.e., the first non-SDT CU configuration). While the UE is communicating 304 with the base station 104, CU-CP 172A may send 306 a UE context modification request message. In response, DU 174 sends 308 a UE context modification response message to CU-CP 172A including a non-SDT configuration for UE 102 (i.e., a second non-SDT configuration). CU-CP 172A generates an RRC reconfiguration message including the second non-SDTDU configuration and sends 310 a first CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to DU 174. DU 174, in turn, sends 312 the RRC reconfiguration message to UE 102. In response, UE 102 sends 314 an RRC reconfiguration complete message to 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 CU-CP 172A.

[0071] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the second non-SDT DU configuration. The UE 102 further communicates with the CU-CP 172A and / or the 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 the 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., the second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or the CU-UP 172B via the DU 174 using the second non-SDT CU configuration.

[0072] In some implementations, the second non-SDT CU configuration modifies or 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 such a case, the UE 102 and at least one of the CU-CP 172A and / or CU-UP 172B may communicate 318 with each other using the second non-SDU CU configuration and the configuration parameters in the first non-SDT CU configuration that are not modified or augmented by the second non-SDU CU configuration. In some implementations, the first non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers (e.g., RRC 214 and / or NR PDCP 210), and the UE 102 and the CU 172 use the configuration parameters to communicate with each other when the UE 102 operates in a connected state. Similarly, in a further implementation, the second non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers, and when the UE 102 operates in the connected state, the UE 102 and the CU 172 communicate with each other using the configuration parameters.

[0073] In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. Similarly, the second non-SDT CU configuration includes configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. In some implementations, the first non-SDTCU 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.

[0074] In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which are used by the UE 102 and the DU 174 to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT DU configuration may include configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers, which are used by the UE 102 and the DU 174 to communicate with each other when the UE 102 operates in a connected state.

[0075] In some implementations, the first non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. Similarly, the second non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration are CellGroupConfig IEs.

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

[0077] While the UE 102 is communicating with the base station 104, or after the non-SDT resource configuration / reconfiguration process 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., 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 configuration / reconfiguration process 390 (if performed), the UE 102 determines or detects the data inactivity and sends 320 UE assistance information (e.g., a UEAssistanceInformation message) to the DU 174, the UE assistance information indicating that the UE 102 prefers or requests to transition to the inactive state or leave the connected state. In some implementations, the UE 102 indicates in the UE assistance information that the UE 102 prefers or requests to transition to the inactive state of the configured SDT. Then, DU 174 sends 321 a UL RRC messaging message including the UE assistance information to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 has data inactivity based on the UE assistance information.

[0078] In other implementations, the DU 174 performs data inactivity monitoring for the UE 102. The CU-CP 172A may send (not shown) 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 during monitoring that the UE 102 has data inactivity, 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 has data inactivity based on the inactivity notification received from the DU 174.

[0079] In yet other implementations, CU-UP 172B performs data inactivity monitoring for UE 102. CU-CP 172A may send (not shown) a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the event that CU-UP 172B detects or determines that UE 102 has data inactivity during monitoring, CU-UP 172B may send 323 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 has data inactivity based on the inactivity notification received from CU-UP 172B. In some implementations, CU-CP 172A determines that UE 102 has data inactivity based on UE assistance information from events 320, 321, an inactivity notification of event 322, and / or an inactivity notification of event 323.

[0080] In some implementations, after a specific period of data inactivity, CU-CP 172A determines that neither CU 172 (i.e., CU-CP 172A and / or CU-UP 172B) nor UE 102 has sent any data in the downlink direction or uplink direction, respectively, during the specific period. In response to the determination, CU-CP 172A may determine to transition UE 102 to an inactive state with SDT configured. Alternatively, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured in response to determining that UE 102 has data inactivity.

[0081] In response to determining that the UE 102 has data inactivity (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CU-CP 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 some implementations, in response to determining that the UE 102 has data inactivity (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or thereafter, the CU-CP 172A sends 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 includes an SDT request indication (eg, an IE such as a CG-SDT Query Indication IE or an SDT Query Indication IE) requesting SDT DU configuration in the second CU-to-DU message.

[0082] In a further implementation, in response to the SDT request indication or the second CU-to-DU message, the DU 174 sends 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or sending the second DU-to-CU message, the DU 174 sends (not shown) an additional DU-to-CU message (e.g., a UE context modification request message) including the SDT DU configuration to the CU-CP 172A. In some implementations, the CU-CP 172A sends (not shown) 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.

[0083] In other implementations, the CU-CP 172A sends 328 a second CU to DU message and receives 330 a second DU to CU message or an additional DU to CU message before determining that the UE 102 has data inactivity. In still other implementations, the CU-CP 172A includes an SDT request indication in the first CU to DU message at event 308, and the DU 174 includes an SDT DU configuration in the first DU to CU message at event 310 in response to the SDT request indication.

[0084] Depending on the implementation, in response to determining to transition the UE 102 to the inactive state in which the SDT is configured, the CU-CP 172A generates an RRC release message (e.g., an RRCRelease message, an RRCConnectionRelease message) to transition the UE 102 to the 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 the inactive state. UE 102 transitions 336 from the connected state to the inactive state upon receiving the RRC release message. Depending on the implementation, in response to the third CU to DU message, DU 174 retains the SDT DU configuration (if generated by DU 174 during processes 328, 330) and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. In response to the third CU to DU message, DU 174 may send (not shown) 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.

[0085] 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 an RRC release message, or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. In some implementations, in response to receiving 334 an RRC release message or transitioning 336 from a connected state to an inactive state, or thereafter, the UE 102 retains the C-RNTI. In some implementations, the UE 102 performs a two-step or four-step random access procedure with a base station 104 (e.g., CU-CP 172A and / or DU 174) and receives a random access response message including the C-RNTI from the DU 174 during the random access procedure. In other implementations, the UE 102 receives a random access response message from the CU-CP 172A or from the DU 174 via the DU 174. Figure 3 Another base station (eg, base station 106) not shown in the figure receives an RRC message (eg, an RRC reconfiguration message) including the C-RNTI.

[0086] Events 320 (optional), 321 (optional), 322 (optional), 323, 324, 326, 328, 330, 332, and 334 are Figure 3 It is collectively referred to as the SDT configuration process 394.

[0087] In some implementations, in response to the RRC release message, the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT DU configuration. In further implementations, in response to the RRC release message, the UE 102 releases at least a portion of the first non-SDT DU configuration and / or at least a portion of the second non-SDT DU configuration. In other implementations, if the RRC release message instructs the UE 102 to transition to an idle 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 non-SDT DU configuration and / or the first portion of the second non-SDT DU configuration, and retains the second portion of the first non-SDT DU configuration and / or the second non-SDT DU configuration. In still other implementations, if the RRC release message instructs the UE 102 to transition to an inactive state (ie, RRC_INACTIVE), the UE 102 retains the first non-SDT DU configuration (if received, not augmented by the second non-SDT DU configuration) and / or the second non-SDT DU configuration.

[0088] 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 by default. In other implementations, CU-CP 172A includes an indication for instructing DU 174 to retain the SDT DU configuration in the 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 the third CU to DU message (e.g., a UE context modification request message or a DL RRC messaging message) for UE 102. Therefore, in response to the third CU to DU message excluding the indication, DU 174 retains the SDT DU configuration. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.

[0089] In some implementations, the SDT CU configuration (e.g., SDT-Config IE) includes a DRB list (e.g., std-DRB-List) including a DRB ID list indicating the IDs of the DRBs configured for SDT. In some implementations, the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. In some implementations, the SDT CU configuration includes a compression protocol continuation indication (e.g., sdt-DRB-ContinueROHC) indicating that the PDCP entity for the DRBs configured for SDT is in SDT operation (i.e., for Figure 4 In some implementations, the CU-CP 172A includes the SDT DU configuration in the SDT CU configuration. In some implementations, the “SDT CU configuration” is simplified to “SDT configuration”.

[0090] 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 configured 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. Depending on the implementation, the UL BWP configuration includes a CG configuration, a PUCCH configuration, a 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 DL BWP configuration includes a PDCCH configuration and / or a PDSCH configuration for the UE to receive DL control signals from DU 174 on the PDCCH and data from DU 174 on the PDSCH when UE 102 performs CG-SDT with DU 174. Each of the CG configurations configures periodic radio resources (i.e., CG resources) that 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 resources occur periodically. In some implementations, the periodicity is a fixed number of symbols, time slots, or subframes. Depending on the implementation, some or all of the CG configurations have the same periodicity or different periodicities.

[0091] In some implementations, each of the CG configurations configures or includes an offset that indicates a time domain offset (e.g., timeDomainOffset) of the CG resources relative to a reference time (e.g., system frame number (SFN)). In some implementations, the CG configuration configures or includes a reference time (e.g., timeReferenceSFN). In some implementations, the CG configuration is or is similar to the ConfiguredGrantConfig IE specified in 3GPP specification 38.331. DU 174 configures a timing advance validity threshold (e.g., including an RSRP range) for UE 102 to determine whether UE 102 can initiate SDT using a configured grant configuration for CG-SDT, such as for Figure 4 Based on the timing advance validity threshold, UE 102 evaluates whether the stored timing advance value is still valid. In an implementation where UE 102 determines that the stored timing advance value is invalid, UE 102 initiates a RA-SDT with CU 172 via DU 174, as described for Figure 4 In some implementations, the SDTDU configuration is an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE.

[0092] In some implementations, "SDT DU configuration" is replaced with "CG-SDT configuration". In such implementations, the configurations in the SDT DU configuration are specific to CG-SDT. In other implementations, some of the configurations in the SDT DU configuration described above are part of the CG-SDT configuration, while other configurations in the SDT DU configuration (e.g., BSR configuration and / or PHR configuration) are not within the CG-SDT configuration. The SDT DU configuration includes the CG-SDT configuration. In such a case, UE 102 configures other configurations for CG-SDT or RA-SDT. In other implementations, the "SDT DU configuration" is simplified to the "SDT configuration".

[0093] In some implementations, the DU 174 starts or restarts the DU CG-SDT timer in response to or after receiving the SDT request indication, generating the CG-SDT configuration, receiving 328 the second CU to DU message, sending 330 the CG-SDT configuration to the CU 172, receiving 332 the third CU to DU message, or sending 334 the CG-SDT configuration to the UE 102. In further implementations, the DU 174 starts or restarts the DU CG-SDT timer with the timer value to manage the CG-SDT configuration.

[0094] In some implementations, the timer value is the same as the CG-SDT time alignment timer value. In other implementations, the timer value is close to the CG-SDT time alignment timer value. For example, the timer value may be greater than and close to the CG-SDT time alignment timer value. In another example, the timer value may be less than and close to the CG-SDT time alignment timer value. In the event that the DU CG-SDT timer expires, DU 174 releases the CG-SDT configuration or the CG resources configured in the CG-SDT configuration. When the CG-SDT configuration is released, or thereafter, DU 174 avoids receiving PUSCH transmissions from UE 102 on radio resources reserved or configured by RAN 105 for the CG-SDT configuration. In some implementations, when the CG-SDT configuration is released, or thereafter, DU 174 schedules transmissions for other UEs on radio resources reserved or configured for the CG-SDT configuration.

[0095] As described above, in some implementations, the RRC release message 334 includes a CG-SDT configuration. In response to receiving the CG-SDT configuration, or thereafter, the UE 102 starts or restarts a UE CG-SDT timer (e.g., CG-SDT-TAT). In some implementations, in response to receiving the CG-SDT configuration, or thereafter, the UE 102 starts or restarts a UE CG-SDT timer (i.e., a first UE CG-SDT timer). In some cases where the UE CG-SDT timer expires, the UE 102 releases the CG-SDT configuration. In other cases where the UE CG-SDT timer expires, the UE 102 instead 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. Depending on the implementation, when the UE CG-SDT timer expires, the UE 102 releases 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 refrains from sending one or more SRSs to the DU 174 on the SRS resources.

[0096] When the UE CG-SDT timer is running, the UE 102 in an inactive state communicates with the DU 174 via the dedicated DL BWP and the dedicated ULBWP (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 UE 102 in an inactive state switches from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In some such cases, the UE 102 readjusts the transceiver of the UE 102 to switch to the initial DL BWP and the initial UL BWP. In some implementations, when the RAN 105 configures the UE 102 using the CG-SDT configuration, the UE 102 in an inactive state switches to the initial DL BWP and the initial UL BWP to perform a random access procedure. Depending on the implementation, the UE 102 performs a random access procedure for different situations as described below. In some implementations, the UE 102 in the inactive state switches 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.

[0097] In some implementations, the DU 174 or the CU-CP 172A configures 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 some such implementations, when the UE CG-SDT timer expires, the UE 102 does not switch from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In further such cases, the UE 102 does not readjust the transceiver of the UE 102 due to switching BWP. In still further such cases, when the UE 102 in an inactive state performs a random access procedure with the DU 174, the UE 102 performs the random access procedure without switching to the initial DL BWP and the initial UL BWP. In such a case, while performing CG-SDT with the DU 174, the UE 102 performs measurements on the SSBs sent by the DU 174 within the initial DL BWP.

[0098] In some implementations, in response to expiration of the UE CG-SDT timer, or thereafter, the UE 102 performs RA-SDT with the CU 172 via the DU 174 on the initial UL BWP and the initial DL BWP, such as for Figure 4 That is, in response to the UE CG-SDT timer expiring, or thereafter, the UE 102 determines that the RA-SDT is valid.

[0099] In some implementations, DU 174 reserves the CG resources configured in the CG configuration. In further 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 some 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.

[0100] In the case where DU 174 does not provide CG-SDT configuration or SDT DU configuration to CU-CP 172A, in response to the third CU-to-DU message, DU 174 releases all signaling and user data transmission resources for UE 102. In the case where DU 174 provides SDT DU configuration or CG-SDT configuration to CU-CP 172A, in response to receiving the third CU-to-DU message, or thereafter, DU 174 reserves signaling and user data transmission resources for UE 102.

[0101] 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 some such cases, UE 102 performs RA-SDT with CU 172 via DU 174, such as for Figure 4 described.

[0102] In some implementations, when determining to transition UE 102 to an inactive state with SDT configured, CU-CP 172A does not request DU 174 to provide an SDT DU configuration. In some such cases, events 328 and 330 are omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A generates the SDT DU configuration on its own without requesting DU 174 to provide the SDT DU configuration, and includes the SDT DU configuration in the RRC release message.

[0103] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message. In some such implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message because UE 102 does not support CG-SDT, and therefore DU 174 does not support CG-SDT. In other implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message because DU 174 does not have available radio resources for CG-SDT. In such a case, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 sends the SDT DU configuration to CU-CP 172A as described above.

[0104] In some implementations, DU 174 does not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message. In some such implementations, DU 174 does not include the configuration for CG-SDT because UE 102 does not support CG-SDT, and therefore DU 174 does not support CG-SDT. In other implementations, DU 174 does not include the configuration for CG-SDT because DU 174 does not have available radio resources for CG-SDT. In such a case, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 includes the CG-SDT configuration in the SDT DU configuration, as described above.

[0105] In some implementations, such as when UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A requests DU 174 to provide SDT DU configuration, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. Depending on the implementation, when UE 102 operates 302 in a connected state, CU-CP 172A receives UE capabilities (e.g., UE-EUTRA-Capability IE, UE-NR-Capability IE, or UE-6G-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. Thus, CU-CP 172A may determine whether UE 102 supports CG-SDT based on UE capabilities. In some implementations, CU-CP 172A receives a DU-to-CU message from DU 174 indicating whether DU 174 supports CG-SDT. Depending on the implementation, the DU-to-CU message is 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).

[0106] In some implementations, depending on whether the UE 102 supports CG-SDT, the DU 174 determines whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In further implementations, depending on whether the DU 174 supports CG-SDT, the DU 174 additionally determines whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). In some implementations, when UE 102 is operating 302 in a connected state or in an inactive state before event 302, DU 174 receives UE capabilities from CU-CP 172A. Therefore, DU 174 can determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, DU 174 sends a DU-to-CU message to CU-CP 172A indicating whether DU 174 supports CG-SDT, as described above.

[0107] 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 transitions from a connected state with SDT configured to an inactive state, such as for Figure 3Described. In such an implementation, the UE receives 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 transitions from an inactive state where SDT is not configured to an inactive state where SDT is configured. For example, the UE 102 receives an RRC release message from a base station (e.g., base station 104 or base station 106) that causes the UE 102 to transition to an inactive state but does not configure SDT (e.g., indicates release of SDT, or does not include the SDT configuration in the RRC release message). In this case, the UE 102 transitions to an inactive state where SDT is not configured in response to the RRC release message. The UE 102 in an inactive state where SDT is configured or not configured performs 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.

[0108] At a later time, the UE 102 operating in the inactive state with SDT configured initiates SDT. In response to initiating SDT, or thereafter, the UE 102 generates an initial UL MAC PDU including an UL RRC message and initiates SDT in a cell (e.g., cell 124 or cell 126). Figure 1A 406 DU-CP 172A sends the initial UL MAC PDU to DU 174 on another cell of base station 104 not shown in the figure). The following events between UE 102 and DU 174 occur on the cell. In some implementations, UE 102 starts the SDT session timer in response to initiating SDT. In some implementations, the SDT session timer is a new timer (e.g., T319a) defined in the RRC specification (e.g., Version 17.0.0). DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends the first DU to CU message to CU-CP 172A. In some implementations, the first DU to CU message is an initial UL RRC message delivery message. In other implementations, the first DU to CU message is a UL RRC message delivery message.

[0109] In a scenario where the UE 102 initiates an SDT to send UL data (e.g., data packets) that is eligible for the SDT, the UE 102 sends 404 an initial UL MAC PDU including the UL data. In a scenario where the UE 102 initiates an SDT to receive DL data, the UE 102 sends 404 an initial UL MAC PDU without an UL data packet. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging message (not shown) from the DU 174. In such a scenario, the UE 102 may include an SDT indication for indicating to the base station 104 that the UE 102 is initiating an SDT to receive DL data in the initial UL MAC PDU or UL RRC message.

[0110] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to send 404 a UL MAC PDU. In such a case, the SDT may be a RA-SDT. For example, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In the case where the procedure is 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 a dynamic uplink grant, a temporary C-RNTI, and a timing advance command to the UE 102. The UE 102 then sends 404 a UL MAC PDU to the DU 174 according to the dynamic uplink grant. The DU 174 receives 404 a UL MAC PDU according to the dynamic uplink grant in the RAR, and in response, sends a DL MAC PDU including a contention resolution MAC control element to the UE 102.

[0111] In the case where the procedure is a two-step random access procedure, the UE 102 sends 404 a message A (MsgA) including a random access preamble and a UL MAC PDU to the DU 174 according to the two-step random access configuration parameters. The UE 102 receives 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 includes a contention resolution MAC control element in the MsgB. The UE 102 receives the two-step random access configuration parameters in the system information broadcast by the DU 174 on the cell 124 before sending 404 the UL MAC PDU. The DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.

[0112] When UE 102 successfully performs contention resolution (i.e., receives a contention resolution MAC control element) during the random access procedure, UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3418 . The UE 102 uses the C-RNTI to monitor the PDCCH from the DU 174 to transmit 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 a dynamic uplink grant or a downlink assignment. If the UE 102 verifies that the CRC is correct and the DCI includes a dynamic uplink grant, the UE 102 uses the dynamic 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. In some implementations, the DU 174 scrambles the CRC using the C-RNTI, and the UE 102 verifies the scrambled CRC using the C-RNTI.

[0113] In other implementations, for example, Figure 3 As described, when UE 102 receives a CG configuration or RAN 105 configures UE 102 using a CG configuration, UE 102 sends 404 UL MAC PDU on CG resources. In such a case, 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 some such implementations, after generating or sending 404 UL MAC PDU, if CU-CP 172A or DU 174 configures UE 102 to apply a UE timer during SDT, UE 102 starts a UE timer (e.g., a second UE CG-SDT timer). In some implementations, UE 102 starts a UE timer using a UE timer value (e.g., a cg-SDT-RetransmissionTimer value). After sending 404 the UL MAC PDU, when the UE 102 receives the DCI and the CRC of the DCI from the DU 174 on the PDCCH and verifies that the CRC is correct using the C-RNTI, the UE 102 stops the UE timer. In some implementations, the DU 174 scrambles the CRC using the C-RNTI and the UE 102 verifies the scrambled CRC using the C-RNTI.

[0114] In a further implementation, similar to events 332, 334, UE 102 receives 434, 432 an RRC release message including a UE timer value from base station 104. CU-CP 172A includes the UE timer value in the CG-SDT configuration and sends the RRC release message including the CG-SDT configuration to UE 102 via DU174. In other implementations, UE 102 receives the UE timer value in a system information block (SIB) broadcast by DU174 via cell 124. When 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 receiving 404 to the UL MAC PDU on the CG resources, or thereafter, 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 is equal to or greater than the UE timer value. While the DU timer is running, DU 174 processes the UL transmission received from UE 102 on the CG resources as a new transmission.

[0115] In some implementations, the UE 102 sends 418 a subsequent UL MAC PDU including one or more UL data packets on the CG radio resources. In further implementations, the UE 102 sends 418 the subsequent UL MAC PDU on radio resources configured in a dynamic uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 sends 418 some of the subsequent UL MAC PDUs on radio resources configured in the CG configuration and sends 418 the remainder of the subsequent UL MAC PDUs on radio resources configured in the dynamic uplink grant.

[0116] In some implementations in which the UE 102 sends 418 subsequent UL MAC PDUs on CG resources, the UE 102 starts or restarts a timer (e.g., a second UE CG-SDT timer) after generating or sending 418 each of the subsequent UL MAC PDUs. The UE 102 may start or restart the timer using the timer value as described above. When the UE timer is running, the UE 102 in an inactive state or SDT session avoids resending the UL MAC PDU. In some implementations, in response to receiving 418 each of the subsequent UL MAC PDUs on the CG resources, or thereafter, the DU 174 starts or restarts the DU timer (e.g., a second DU CG-SDT timer) using the DU timer value. When 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. In other implementations, the DU 174 processes 404, 418 UL MAC PDUs without starting the DU timer.

[0117] If UE 102 includes UL data in the initial UL MAC PDU 404, DU 174 retrieves the UL data from the initial UL MAC PDU. In some such cases, DU 174 includes the UL data in the DU to CU message of event 406. Alternatively, DU 174 sends 415 a DU to CU message including the UL data to CU-CP 172A. In such an alternative implementation, the UL data includes or is a PDCP PDU, an RRC PDU, a NAS PDU, or an LTE Positioning Protocol (LPP) PDU. Depending on the implementation, the PDCP PDU includes an RRC PDU. In a further implementation, DU 174 sends 416 UL data to CU-UP 172B separately via a user plane (UP) connection as described below. In some such implementations, the UL data includes or is a PDCP PDU, and the PDCP PDU includes an SDAP PDU, an IP packet, or an Ethernet packet.

[0118] After receiving 406 the first DU-to-CU message, in some implementations, the CU-CP 172A sends 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 some implementations, the CU-CP 172A includes transport layer information of one or more GTP-U tunnels between the CU-UP 172B and the DU 174 in the UE context setup request message so that the DU 174 can send UL data and / or subsequent UL data (e.g., in a small data communication 418) to the CU-UP 172B via the one or more GTP-U tunnels. In response, the DU 174 sends 410 a UE context setup response message to the CU-CP 172A. After receiving 406 the first DU to CU message, sending 408 the UE context setup request message, or receiving 410 the UE context setup response message, CU-CP 172A sends 412 a bearer context modification request message to CU-UP 172B to resume data transmission for 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. In some cases where the UL data of event 404 includes an RRC message or is associated with an SRB (e.g., SRB1 or SRB2), after receiving 408 the UE context setup request message or sending 410 the UE context setup response message, DU 174 sends 415 a DU to CU message including the UL data to CU-CP 172A. In some cases where the UL data is associated with a DRB, DU 174 sends 416 the UL data to CU-UP 172B. In some cases where CU-CP 172A determines that DU 174 already has the UE context of UE 102, CU-CP 172A omits events 408 and 410. For example, in the case of the CG-SDT described above, CU-CP 172A instructs DU 174 to retain the UE context of UE 102. In some such cases, instead of a UE context setup request message, CU-CP 172A sends a UE context modification request message to DU 174 to modify the UE context, and in response, DU 174 sends a UE context modification response message.

[0119] In some implementations, the CU-CP 172A may include transport layer information for the CU-UP 172B in the UE context setup request message. The transport layer information for the CU-UP 172B may include an IP address and / or an uplink tunnel endpoint ID (e.g., TEID). The DU 174 uses the transport layer information for the CU-UP 172B to send 416 UL data to the CU-UP 172B. In some cases where the UE 102 has subsequent UL data (e.g., one or more UL data packets) to send, the UE 102 sends 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 case where the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 sends 418 one or more DU to CU messages (e.g., UL RRC messaging messages) including the subsequent UL data to the CU-CP 172A. Each DU to CU message may include a specific UL data packet of subsequent UL data. In some cases where the CU-CP 172A receives DL data from the CN 110 or edge server, the CU-CP 172A sends 418 one or more CU to DU messages (e.g., DL RRC messaging messages) including the DL data (e.g., one or more DL data packets) to the DU 174. In turn, the DU 174 sends 418 one or more DL MAC PDUs including the DL data to the UE 102 operating in the inactive state. In some implementations, the DL data includes NAS PDUs and / or LPP PDUs.

[0120] In the case where the subsequent UL data is associated with one or more DRBs, similar to event 416, DU 174 sends 418 the subsequent UL data to CU-UP 172B. In some implementations, DU 174 includes DU transport layer information for DU 174 in the UE context establishment response message. Subsequently, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. Depending on the implementation, the transport layer information of DU 174 includes an IP address and / or a downlink TEID. In some cases where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B uses the transport layer information of DU174 to send 418 DL data (e.g., one or more DL data packets) to DU 174. Subsequently, DU174 sends 418 one or more DL MAC PDUs including the DL data to UE 102 operating in an inactive state.

[0121] In some implementations, the UE 102 includes a buffer status report or a power headroom report in an initial and / or subsequent UL MAC PDU according to the BSR configuration and / or the PHR configuration, respectively. In the buffer status report, the UE 102 includes or indicates the buffer status of one or more logical channels or logical channel groups. In the power headroom report, the UE 102 includes or indicates the power headroom status or value.

[0122] 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 includes a PDU (e.g., an RRC PDU, a PDCP PDU, or an RLC PDU), which includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.

[0123] Events 404, 406, 408, 410, 412, 414, 415, and 416 are Figure 4 It is collectively referred to as small data transmission process 492.

[0124] In some implementations, the UL RRC message is an existing RRC recovery request message (e.g., RRCResumeRequest message, RRCResumeRequest1 message, RRCConnectionResumeRequest message, or RRCConnectionResumeRequest1 message). In other implementations, the UL RRC message is a new RRC recovery request message, similar to the existing RRC recovery request message. For example, the new RRC recovery request message may be defined in a future 3GPP standard document. The new RRC recovery request message may be in a format similar to the existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message includes 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.

[0125] In some implementations, after the UE 102 sends 404 a UL MAC PDU or communicates 418 subsequent UL data and / or DL ​​data with the DU 174, the CU-CP 172A determines to stop the SDT of the UE 102 based on data inactivity of the UE 102 (i.e., the UE 102 in the inactive state has no data activity with the base station 104). After the UE 102 sends 404 a UL MAC PDU or communicates 418 subsequent UL data and / or DL ​​data with the DU 174, the UE 102 in the inactive state determines or detects data inactivity and sends 420 UE assistance information (e.g., a UEAssistanceInformation message) to the DU 174 indicating that the UE 102 prefers or requests to stop the SDT.

[0126] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 492. In the embodiment of the present invention, the UE 102 performs 495 an SDT completion procedure with the base station 104, which is similar to the procedure 494. The examples and implementations of events 320, 321, 322, 323, 324, 326, 328, 330, 332, 334 are respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, 434. Depending on the implementation, after stopping the SDT, the UE 102 performs 493 another small data transmission procedure with the base station 104, which is similar to the procedure 492. In a further implementation, after completing the procedure 493, the UE 102 performs 495 an SDT completion procedure with the base station 104, which is similar to the procedure 494.

[0127] 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 receives and retains 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. Depending on the implementation, the UE 102 retains the C-RNTI after receiving 434 the RRC release message or transitioning 436 from the connected state to the inactive state. In some cases where the RRC release message 434 configures the CG-SDT, the UE 102 retains the C-RNTI. In further cases where the RRC release message 434 does not configure or release the CG-SDT, the UE 102 releases the C-RNTI.

[0128] After UE 102 ends the SDT session, the inactive UE 102 monitors the PDCCH using a paging RNTI (P-RNTI). In some scenarios or 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 sends 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 the paging message, a CRC of the DCI; scrambles the CRC using the P-RNTI to obtain a 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 with the G-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. The UE 102 then retrieves the paging message from the PDSCH transmission.

[0129] In some implementations, the second SDT CU configuration is the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration is different from the first SDT CU configuration. Depending on the implementation, the UE 102 updates (e.g., replaces or modifies) the first SDT CU configuration with the second SDT CU configuration. In some implementations, the CU-CP 172A includes an indication in the RRC release message for indicating that the UE 102 updates the first SDT CU configuration with the second SDT CU configuration. In some such implementations, the UE 102 updates the first SDT CU configuration with the second SDT CU configuration in response to the indication.

[0130] In other implementations, CU-CP 172A includes a modification indication for instructing UE 102 to modify the first SDT CU configuration with the second SDT CU configuration in the RRC release message. In some such implementations, UE 102 modifies the first SDT CU configuration with the second SDT CU configuration in response to the modification indication. In still other implementations, CU-CP 172A includes a setup indication for instructing UE 102 to replace the first SDT CU configuration with the second SDT CU configuration in the RRC release message. In some such implementations, UE 102 replaces the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.

[0131] 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. Depending on the implementation, the UE 102 updates (e.g., replaces or modifies) the first SDT DU configuration with the second SDT DU configuration. In some implementations, the DU 174 includes an indication in the second SDT DU configuration that the UE 102 updates the first SDT DU configuration with the second SDT DU configuration. In some such implementations, the UE 102 updates the first SDT DU configuration with the second SDT DU configuration in response to the indication.

[0132] In other implementations, DU 174 includes a modification indication for instructing UE 102 to modify the first SDTDU configuration with the second SDTDU configuration in the second SDTDU configuration. In some such implementations, UE 102 modifies the first SDTDU configuration with the second SDTDU configuration in response to the modification indication. In still other implementations, DU 174 includes a setup indication for instructing UE 102 to replace the first SDTDU configuration with the second SDTDU configuration in the second SDTDU configuration. In some such implementations, UE 102 replaces the first SDTDU configuration with the second SDTDU configuration in response to the setup indication.

[0133] In some cases where the CU-CP 172A and / or DU 174 support delta configuration, the CU-CP 172A does not send 428 a CU to DU message to obtain a second SDT DU configuration from the DU 174. Unless the conditions for releasing the first SDT configuration are met, the DU 174 retains the first SDT DU configuration. Alternatively, the CU-CP 172A includes the first SDT DU configuration in the second CU to DU message so that the DU 174 retains the first SDT DU configuration. In some such cases, the CU-CP 172A does 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 SDU DU configuration. In some implementations, the CU-CP 172A does not include a release indication in the RRC release message so that the UE 102 is configured 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 CU-CP 172A includes the release indication in the RRC release message, UE 102 releases the first SDT CU configuration and / or the first SDTDU configuration in response to the release indication. In some cases where CU-CP 172A and / or DU 174 do not support incremental configuration, CU-CP 172A includes the SDT DU configuration and / or SDT CU configuration in the RRC release message as described above.

[0134] In some implementations, in response to the third CU-to-DU message, DU 174 retains the second SDT DU configuration and may release the first non-SDT DU configuration and / or the second non-SDT DU configuration. In response to the third CU-to-DU message, DU 174 sends a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A. In some implementations, if the RRC release message instructs UE 102 to transition to an idle 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 SDT DU configuration and SDT CU configuration described above).

[0135] In some implementations, CU-CP 172A does not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state with SDT configured. In some such cases, events 428 and 430 are omitted. In such cases, CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A generates the SDT DU configuration separately and includes the SDT DU configuration in the RRC release message.

[0136] In some implementations, similar to the above description of Figure 3 In the process described above, DU 174 does not include the SDT DU configuration in the second DU to CU message. Figure 3 According to the described process, DU 174 does not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message.

[0137] In some implementations where UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A requests DU 174 to provide SDT DU configuration, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. Depending on the implementation, before UE 102 initiates SDT, when UE 102 operates 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 in a state such as for a CU-to-DU message, the CU-CP 172A requests DU 174 to provide SDT DU configuration. Figure 3 When operating in the described connected state, CU-CP 172A receives UE capabilities (e.g., UE-EUTRA-Capability IE, UE-NR-Capability IE, or UE-6G-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. The 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 receives a DU to CU message from DU 174 indicating whether DU 174 supports CG-SDT. The DU to CU message can be a second DU to CU message, a message of event 308 or 316, or a non-UE associated message (e.g., a non-UE associated F1AP message defined in 3GPP specification 38.473).

[0138] In some implementations, depending on whether UE 102 or DU 174 supports CG-SDT, DU 174 determines whether to provide SDT DU configuration for UE 102 to CU-CP 172A, similar to the above. Figure 3 In addition, DU 174 may determine and signal UE 102 whether CG-SDT is supported, similar to the above Figure 3 .

[0139] Reference now Figure 5A , scenario 500A depicts a small data transfer and a transition from SDT to non-SDT. In scenario 500, 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 with SDT configured, similar to event 402 or 436. Then, UE 102 performs 592 a small data transfer process with base station 104, similar to event 492 or 493.

[0140] During the small data transfer process 592, the CU-CP 172A determines whether to transition the UE 102 to a connected state, for example, based on the UL or DL ​​data activity of the UE 102. In some implementations, the UE 102 sends 503 a non-SDT indication as a message or within a message to the DU 174 to indicate that non-SDT UL data is available or to request a transition to a connected state. In some implementations, the UE 102 sends 503 a non-SDT indication to the DU 174 on radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 uses the C-RNTI to receive a dynamic uplink grant from the DU 174 on the PDCCH and sends 503 a non-SDT indication to the DU 174 on radio resources configured in the dynamic uplink grant. Then, the DU 174 sends 505 a UL RRC messaging message including a non-SDT indication to the CU-CP 172A.

[0141] In some implementations, CU-CP 172A determines to transition UE 102 to a connected state in response to or based on a non-SDT indication. In other implementations, CU-UP 172B receives DL data from CN 110, and in response to receiving the DL data, sends 507 a DL data notification (e.g., a DL data notification message) to CU-CP 172A to indicate that the DL data is available for transmission. In further implementations, CU-CP 172A determines to transition UE 102 to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A determines to transition UE 102 to a connected state based on a measurement result received from UE 102. In other implementations, CU-CP 172A receives DL data (e.g., a NAS message) from CN 110, and in response to receiving the DL data, determines to transition UE 102 to a connected state.

[0142] In some implementations, UL data and DL data are associated with radio bearers (e.g., SRBs and / or DRBs). For example, the UL data includes an RRC message or a NAS message associated with the SRB. In another example, the UL data includes an IP packet associated with the DRB. In some implementations, the UE 102 may include the ID of the radio bearer in a message with a non-SDT indication. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the ID. For example, if the radio bearer ID identifier is not eligible for SDT, the CU-CP 172A determines to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A determines not to transition the UE 102 to a connected state.

[0143] In some implementations, UE 102 includes data volume information for UL data in a message including a non-SDT indication. Thus, CU-CP 172A may determine whether to cause UE 102 to transition to a connected state based on the data volume information. In some implementations, the data volume information includes the total data volume of UL data, and UE 102 may quantize or round the total data volume to a value for the data volume information. In another implementation, the data volume information includes the data volume of each of the radio bearers, and UE 102 may quantize or round the data volume to a value for the data volume information. For example, if the total data volume is higher than a predetermined threshold, CU-CP 172A determines 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 another example, if the data volume for a particular radio bearer is higher than a predetermined threshold, CU-CP 172A determines to cause UE 102 to transition to a connected state. Otherwise, CU-CP 172A determines not to cause UE 102 to transition to a connected state. In yet another example, if the total data amount is above a predetermined threshold and the data amount for a specific radio bearer is above another predetermined threshold, the CU-CP 172A determines to transition the UE 102 to the connected state. Otherwise, the CU-CP 172A determines not to transition the UE 102 to the connected state.

[0144] Typically, each of events 506, 508, 510, and 512 is similar to Figure 3 Events 306, 308, 310, and 312 of the present invention are described in detail below, except for events 306, 308, 310, and 312 that occur when UE 102 is in an inactive state and as described below. In response to determining to transition UE 102 to a connected state, or thereafter, CU-CP 172A sends 506 a UE context request message (e.g., a UE context establishment 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 establishment 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. Then, the DU 174 sends 512 an RRC resume message to the UE 102 .

[0145] In some implementations, DU 174 sends 512 one or more PDUs including an RRC recovery message to UE 102. The PDU may be a MAC PDU or an RLC PDU. In some implementations, the CU to DU message is a DL RRC messaging message or a UE context modification request message. In some cases where the message is a UE context modification request message, in response, DU 174 sends a UE context modification response message to CU-CP 172A. In response to the RRC recovery message, UE 102 transitions 513 to a connected state and sends 514 an RRC recovery completion message (e.g., an RRCResumeComplete message or an RRCConnectionResumeComplete message) to DU 174. In the case where the UE context response message includes a non-SDT DU configuration, CU-CP 172A includes the non-SDT DU configuration in the RRC recovery message. DU 174 sends 516 a DU to CU message including an RRC recovery completion message to CU-CP 172A.

[0146] After determining to transition the UE 102 to the connected state, the CU-CP 172A sends 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 for 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 sends 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 the radio bearers of UE 102 are not suspended when determining to transition UE 102 to the connected state, CU-CP 172A does not send the bearer context request message 517 to CU-UP 172B.

[0147] In some implementations, CU-CP 172A includes an indication indicating that DU 174 generates a non-SDT configuration in the UE context request message at event 506, and DU 174 includes the first non-SDT DU configuration in the UE context response message at event 508 in response to the indication. In 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 the second non-SDT DU configuration. In such a case, CU-CP 172A includes the second non-SDT DU configuration in the UE context request message, and DU 174 includes the first non-SDT DU configuration in the UE context response message in response to receiving the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration augments or replaces the second non-SDT DU configuration. Examples and implementations 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.

[0148] 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 using the non-SDT configuration. Depending on the implementation, the UL data includes UL data that triggers the UE to send a non-SDT indication and / or new UL data available for transmission. In a further implementation, the DL data includes DL data received from the CN 110 as described above and / or new DL data received from the CN 110. In the case where the RRC recovery message includes the first non-SDT DU configuration, the UE 102 communicates 518 with the DU 174 using the first non-SDT DU configuration. In some cases where the first non-SDT DU configuration does not completely replace the second non-SDT DU (i.e., the UE 102 does not release the second non-SDT DU configuration in response to the RRC resume message), the UE 102 communicates 518 with the DU 174 using configuration parameters in the second non-SDT DU configuration that are not extended by the first non-SDT DU configuration.

[0149] In some implementations, DU 174 does 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.

[0150] In some implementations, in response to an RRC recovery message or transitioning to a connected state, the UE 102 releases the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration). In some implementations, in response to transitioning the UE 102 to a connected state, receiving 510 a CU to DU message, or sending 510, 512 an RRC recovery message, or thereafter, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration. In other implementations, in response to receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for a PDU including an RRC recovery message, or thereafter, the base station 104 releases the SDT configuration. In yet other implementations, in response to transmitting 506 a UE context request message or transmitting 508 a UE context response message, or thereafter, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration.

[0151] In other implementations, in response to receiving the RRC recovery message or transitioning to the connected state, 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 the connected state, the UE 102 avoids using the SDT configuration to communicate with the base station 104 (e.g., transmitting 514 an RRC recovery complete message and / or transmitting 518 data). In other implementations, when operating in the connected state, the UE 102 uses the SDT configuration to communicate with the base station 104 (e.g., transmitting 514 an RRC recovery complete message and / or transmitting 518 data).

[0152] In some implementations, in response to or after transitioning the UE 102 to the connected state or sending the RRC recovery message, 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 the connected state (e.g., transmitting 514 the RRC recovery complete message and / or transmitting 518 data). In other implementations, the base station 104 uses the SDT configuration to communicate with the UE 102 operating in the connected state (e.g., transmitting 514 the RRC recovery complete message and / or transmitting 518 data).

[0153] In some implementations, the non-SDT indication message is in an RRC message (e.g., a UEAssistanceInformation message or a new RRC message). In some such implementations, the UE 102 continues to perform 518 data communication with the base station 104 after sending the non-SDT indication. In some implementations, the UE 102 sends a ULMAC PDU including a non-SDT indication to the CU-CP 172A via DU 174. In some implementations, in addition to the non-SDT indication, the UE 102 also includes data in the UL MAC PDU. In other implementations, the UE avoids including the data in the UL MAC PDU. In some implementations, the UE 102 sends a non-SDT indication to the CU-CP 172A via DU 174 and SRB1. In such an implementation, in response to determining to send a non-SDT indication, the UE 102 avoids reestablishing the UE PDCP entity for SRB1. UE 102 generates an UL PDCP PDU including a non-SDT indication using the UE PDCP entity, and sends 503, 505 the UL PDCP PDU to CU-CP 172A via DU 174. Then, UE 102 receives 512 a DL PDCP PDU including an RRC recovery message using the UE PDCP entity without reestablishing the UE PDCP entity. CU-CP 172A receives 505 the UL PDCP PDU using the CU-CP PDCP entity. In response to receiving the non-SDT indication, CU-CP 172A avoids reestablishing the CU-CP PDCP entity for SRB1. CU-CP 172A generates a DL PDCP PDU using the CU-CP PDCP entity, and sends 510, 512 the DL PDCP PDU to UE 102 via DU 174 and SRB1. The UE 102 generates a UL PDCP PDU including an RRC recovery complete message using the UE PDCP entity, and transmits 514, 516 the UL PDCP PDU to the CU-CP 172A via DU 174 and SRB1. The CU-CP 172A receives 514, 516 the UL PDCP PDU from the UE 102 via DU 174 using the CU-CP PDCP entity. In such an implementation, the UE 102 and the CU-CP 172A transmit the PDCP PDU via SRB1 without reestablishing the UE PDCP entity and the CU-CP PDCP entity.

[0154] In other implementations, the non-SDT indication is in an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCResumeConnectionRequest message). In some such implementations, the UE 102 stops 518 data communication with the base station 104 to send the non-SDT indication. In some implementations, the UE 102 sends the non-SDT indication to the CU-CP 172A via the DU 174 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 receives 512 a DL PDCP PDU using the UE PDCP entity. Similarly, after receiving the non-SDT indication, the CU-CP 172A reestablishes the CU-CP PDCP entity. After re-establishing the CU-CP PDCP entity, the CU-CP 172A generates DL PDCP PDUs using the CU-CP PDCP entity and transmits 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 transmits 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 UL PDCP PDUs from the UE 102 via DU 174 using the CU-CP PDCP entity.

[0155] 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 Described. In some implementations, in response to receiving a timing advance command from DU 174 during the small data transfer process 592, UE 102 starts or restarts a first UE CG-SDT timer. In some implementations, in response to receiving 512 to the RRC resume message, or thereafter, UE 102 maintains (e.g., keeps running or does not stop, start or restart) the first UE CG-SDT timer (e.g., CG-SDT-TAT). In other implementations, in response to receiving 512 to the RRC resume message or thereafter, UE 102 stops the first UE CG-SDT timer.

[0156] Similarly, in some implementations, the DU 174 runs a first DU CG-SDT timer for the UE 102 operating 502 in the inactive state, such as for Figure 3 and Figure 4 Described. In some implementations, in response to sending (not shown) a timing advance command to UE 102, DU 174 starts or restarts a first DU CG-SDT timer. In some implementations, 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, DU 174 maintains (e.g., keeps running or does not stop, start, or restart) a first DU CG-SDT timer. In other implementations, 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, DU 174 stops the first DU CG-SDT timer. In some cases where the first DU CG-SDT timer expires, DU 174 releases the CG-SDT configuration. In other cases where 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 cases, the DU 174 releases the CG resources or determines that the CG resources are invalid.

[0157] In some implementations, the UE 102 in an inactive state runs a second UE CG-SDT timer during the 592 small data transfer process, as described for process 492. In some implementations in which the second UE CG-SDT timer is running, in response to receiving 512 to an RRC recovery message or transitioning 513 to a connected state, or thereafter, the UE 102 stops the second UE CG-SDT timer. In some implementations, in response to receiving 512 to an RRC recovery message or transitioning 513 to a connected state, or thereafter, the UE 102 maintains the second UE CG-SDT timer running. 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 complete message to the CU-CP 172A via the DU 174.

[0158] Similarly, depending on the implementation, DU 174 runs a second DU CG-SDT timer during the 592 small data transmission process. In some implementations, DU 174 starts or restarts the second DU CG-SDT timer when, or after, receiving a PUSCH transmission on the radio resources configured in the CG-SDT configuration from UE 102. In a further implementation, when the second DU CG-SDT timer is running, DU 174 sends a PDCCH using the C-RNTI. While 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 after that. 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 after that. The DU 174 sends a PDCCH (DCI on PDCCH) to the UE 102 operating in the connected state using the C-RNTI regardless of the second DU CG-SDT timer (eg, running, expired, or stopped).

[0159] In some implementations, at a later time, the base station 104 performs 590 a non-SDT resource (re)configuration procedure with the UE 102 and performs 594 an SDT configuration procedure with the UE 102, similar to the procedures 390 and 394, respectively. The UE 102 transitions 536 to the inactive state in response to receiving the RRC release message in the procedure 594. Depending on the implementation, after transitioning to the inactive state, the UE 102 in the inactive state performs 593 a small data transfer procedure with the base station 104 and / or performs 595 an SDT completion procedure with the base station 104, similar to the procedures 492 and 494, respectively.

[0160] Next reference Figure 5B , scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC recovery procedure instead of performing 592 a small data transfer procedure. The differences between scenarios 500B and 500A are discussed below.

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

[0162] 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 further implementations, the UE 102 sends 542 the UL MAC PDU to the DU 174 on the radio resources configured for the SDT in the CG configuration. In other implementations, the UE 102 performs a random access procedure to send the UL MAC PDU, similar to event 404.

[0163] 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 when a periodic RAN Notification Area Update (RNAU) timer expires, and initiates an RRC recovery procedure in response to the expiration of the periodic RNAU timer. In some implementations, the RRC layer (e.g., RRC 214) starts or restarts an RNAU timer, maintains the RNAU timer, and initiates an RRC recovery procedure in response to the expiration of the RNAU timer.

[0164] Next reference Figure 6, scenario 600 depicts a small data transfer, similar to scenario 400. Except for events 607 and 609, events 602, 604, 606, 608, 610, 612, 614, 615, 616, 618, 694, 636 are similar to events 402, 404, 406, 408, 410, 412, 414, 415, 416, 418, 494, 436. Figure 4 Examples and implementations can be applied to Figure 6 The following describes Figure 4 and Figure 6 The difference between.

[0165] In scenario 600, UE 102 initially operates 602 in an inactive state with an SDT configuration configured by base station 104, such as for Figure 3 or Figure 4 In some implementations, the SDU configuration includes a CG-SDT configuration. In some such cases, the UE 102 discards the CG-SDT configuration because the base station 106 does not configure the CG-SDT configuration for the UE 102, i.e., the CG-SDT configuration is invalid.

[0166] In response to receiving 606 the UL RRC message, or thereafter, the CU-CP 172A sends 607 a retrieve UE context request message to the base station 104. In response, the base station 104 sends 609 a retrieve UE context response message to the CU-CP 172A. After receiving the retrieve UE context response message, the CU-CP 172A sends 608 a UE context establishment request message to the DU 174, receives 610 a UE context establishment response message from the DU 174, and sends 612 an RRC recovery message to the DU 174. The CU-CP 172A sends 612 a bearer context establishment request message to the CU-UP 172B to request the CU-UP 172B to establish a bearer context for the SDT DRB configured in the SDT configuration. In response, the CU-UP 172B establishes a bearer context for the SDT DRB and sends 614 a bearer context establishment response message to the CU-CP 172A to confirm that the bearer context for the SDT DRB has been established.

[0167] In some implementations, the base station 104 includes the SDT configuration in the retrieval UE context response message. In some cases where the SDT configuration includes a CG-SDT configuration, the base station 104 excludes the CG-SDT configuration from the SDT configuration. Alternatively, the CU-CP 172A still includes the CG-SDT configuration from the SDT configuration. In some implementations, when the CU-CP 172A receives the CG-SDT configuration, the CU-CP 172A discards the CG-SDT configuration. In further implementations, such as when the CU-CP 172A does not support incremental configuration, the CU-CP 172A discards the SDT configuration. In some cases where the CU-CP 172A supports incremental configuration, when the CU-CP 172A determines that the UE is transitioned to an inactive state at the SDT completion process 694 similar to process 494, the CU-CP 172A takes the SDT configuration (e.g., the first SDT configuration) into account. In other implementations, the CU-CP 172A avoids including the SDT configuration in the retrieval UE context request message.

[0168] Next, refer to FIG. 7A to FIG. 15 Several example methods that can be implemented in a UE, a base station, a DU of a base station, or a CU of a base station are discussed. Each of these methods can be implemented using processing hardware such as one or more processors to execute instructions stored on a non-transitory computer-readable medium such as a computer memory. For clarity, FIG. 7A to FIG. 15 The method is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172 and DU 174.

[0169] First reference Fig. 7A The method 700A may be implemented in a suitable UE and includes determining whether to proceed with the SDT process based on whether the UE supports RA-SDT communication.

[0170] At block 702, UE 102 receives an SDT configuration ( Figures 3 to 6 At block 704, when operating in an inactive state, UE 102 initiates an SDT process (e.g., Figures 4 to 6Events 492 / 493 / 494, 592 / 593 / 595, and 692 / 694). In some implementations, if the UE 102 determines that one or more conditions for initiating the SDT process are met, the UE 102 initiates or determines to initiate the SDT process. In some implementations, the conditions include: 1) the system information block 1 (SIB1) of the cell in which the UE 102 is currently residing includes an SDT configuration (e.g., sdt-ConfigCommon); 2) all pending data for transmission are associated only with radio bearers of the SDT; 3) the data volume of all pending data is lower than or equal to a threshold (e.g., sdt-DataVolumeThreshold); and / or 4) the signal strength of the downlink path loss reference (e.g., RSRP) is higher than a threshold (e.g., sdt-RSRP-Threshold).

[0171] At block 706, the flow splits depending on whether the UE 102 supports RA-SDT communications. In implementations where the UE 102 supports RA-SDT communications, the flow continues to block 708. Otherwise, the flow continues to block 710. At block 708, the UE 102 continues the SDT process with the RAN 105 while continuing to operate in an inactive state (e.g., Figures 4 to 5B Events 493 and 593).

[0172] In addition, in some implementations where UE 102 supports RA-SDT communication, UE 102 sends a RA-SDT support indication to RAN 105 indicating support for RA-SDT communication. In some implementations where UE 102 does not support RA-SDT communication, UE 102 avoids sending a RA-SDT support indication to RAN 105. In another example, UE 102 sends a message including a capability ID to CN 110 via RAN 105, which identifies multiple UE capabilities of UE 102. Depending on the implementation, multiple UE capabilities include RA-SDT capabilities. In some such implementations, RAN 105 receives UE capabilities from CN 110. In some implementations, UE 102 may be preconfigured to support RA-SDT communication. For example, UE 102 may store a first flag in a non-volatile memory. When the first flag is set to a first value, UE 102 enables or supports RA-SDT communication. When the first flag is set to a second value, UE disables or does not support RA-SDT communication.

[0173] At block 710, UE 102 performs an RRC recovery procedure with RAN 105 to transition from an inactive state to a connected state (e.g., Figures 4 to 5BIn some implementations, at block 710, the UE 102 stops performing the SDT process altogether.

[0174] In some implementations, UE 102 supports CG-SDT communication. In some such implementations, UE 102 sends a CG-SDT support indication to RAN 105 or to CN 110 via RAN 105 indicating support for CG-SDT communication. In some implementations where UE 102 does not support CG-SDT communication, UE 102 avoids sending a CG-SDT support indication to RAN 105 or CN 110. In a further implementation, UE 102 is preconfigured to support CG-SDT communication. For example, UE 102 stores a first flag in a non-volatile memory. When the second flag is set to a third value, UE 102 enables or supports CG-SDT communication. When the second flag is set to a fourth value, UE 102 disables or does not support CG-SDT communication. In some implementations, the first flag and the second flag may be the same flag. In other implementations, the first flag and the second flag may be different flags.

[0175] Next reference Figure 7B The method 700B may be implemented in a suitable UE and includes determining whether to proceed with the SDT process based on whether the RAN supports RA-SDT communication. Figure 7B and Fig. 7A Very similar. Figure 7B and Fig. 7A The difference is that the decision block 707 focuses on whether the RAN (rather than the UE) supports RA-SDT.

[0176] In some implementations, if the SDT configuration (e.g., SDT-Config) includes a RA-SDT configuration, the UE 102 determines that the RAN 105 supports RA-SDT communication. Otherwise, in such an implementation, if the SDT configuration does not include a RA-SDT configuration, the UE 102 determines that the RAN 105 does not support RA-SDT communication. In some implementations, the RA-SDT configuration is a RA-SDT indication or a RA-SDT enable indication. In other implementations, the RA-SDT configuration is a random access configuration or a timer value of the RA-SDT, such as logicalChannelSR-DelayTimer. In other implementations, the UE 102 receives the SDT configuration and resides on a cell of the RAN 105, and determines whether the cell or the RAN 105 supports RA-SDT communication based on the SIB (e.g., SIB1) received by the UE 102 on the cell. The RAN 105 broadcasts the SIB on the cell. For example, if the SIB includes an SDT configuration (e.g., sdt-ConfigCommon, SDT-ConfigCommonSIB, or SDT-ConfigCommonSIB-r17), the UE 102 determines that the RAN 105 or cell supports RA-SDT communication. If the SIB does not include an SDT configuration, the UE 102 determines that the cell does not support RA-SDT communication. In another example, if the SIB or the SDT configuration in the SIB includes an RA-SDT configuration, the UE 102 determines that the RAN 105 or cell supports RA-SDT communication. If the SIB or the SDT configuration does not include an RA-SDT configuration, the UE 102 determines that the RAN 105 or cell does not support RA-SDT communication. In some implementations, the RA-SDT configuration is an RA-SDT indication or an RA-SDT enable indication. In other implementations, the RA-SDT configuration is a random access configuration or a timer value of the RA-SDT, such as logicalChannelSR-DelayTimer. In yet other implementations, the RA-SDT configuration is a signal strength or quality threshold configuration (e.g., sdt-RSRP-Threshold, sdt-RSRP-Threshold-r17, or RSRP-Range) for the UE 102 to determine whether to initiate the RA_SDT process. For example, the UE 102 obtains the signal strength or quality of the downlink path loss reference. Depending on the implementation, if the signal strength or quality is higher than the threshold in the threshold configuration, the UE 102 initiates the RA-SDT process. Otherwise, the UE 102 avoids initiating the RA-SDT process.

[0177] Next reference Figure 7CThe method 700C may be implemented in a suitable UE and includes determining whether to proceed with the SDT process based on whether both the UE and the RAN support RA-SDT communication. Figure 7C Fusion Fig. 7A Box 706 and Figure 7B Box 707 in and all related descriptions.

[0178] Next reference Figure 8 The method 800 may be implemented in a suitable UE and includes determining whether to perform an SDT process based on whether the UE and / or the RAN supports RA-SDT communication and whether conditions for initiating RA-SDT are met.

[0179] Blocks 802 and 804 are similar to blocks 702 and 704, as described with respect to Fig. 7A At block 805, the UE 102 determines whether a condition for initiating RA-SDT is met. In an implementation where the condition is met, the flow continues to block 806. Otherwise, the flow continues to block 810. At block 806, the UE 102 determines whether either the UE 102 or the RAN 105 supports RA-SDT communications. In an implementation where either supports RA-SDT communications, the flow continues to block 808. Otherwise, the flow continues to block 810. At block 808, when operating in an inactive state, the UE 102 performs an SDT procedure with the RAN 105 to send data (e.g., Figures 4 to 5B At block 810, UE 102 performs an RRC recovery procedure with RAN 105 to transition from the inactive state to the connected state (e.g., Figures 4 to 5B Events 495 and 595 of FIG. 4 ). In some implementations, at block 810, UE 102 avoids performing an SDT procedure to send data. At block 812, UE 102 sends data to RAN 105 after transitioning to the connected state (e.g., Figures 4 to 5B Events 495 and 595).

[0180] against FIG. 7A to FIG. 7C The examples and implementations described can be applied to Figure 8 .

[0181] Next reference Fig. 9 , method 900 can be implemented in a suitable UE and includes determining whether to perform a CG-SDT process, a RA-SDT process, or an RRC recovery process based on whether conditions for initiating CG-SDT or RA-SDT are met.

[0182] At block 902, UE 102 receives an SDT configuration including a CG-SDT configuration from a node of RAN 105 (such as base station 104). Figures 3 to 6 At block 904, when operating in an inactive state, the UE 102 determines to send data (e.g., Figures 4 to 6 At block 906, the UE 102 determines whether the conditions for initiating CG-SDT are met. In an implementation where the conditions are met, the flow continues to block 908. Otherwise, the flow continues to block 910. At block 908, when operating in the inactive state, the UE 102 performs a CG-SDT procedure with the RAN 105 according to the CG-SDT configuration (e.g., Figures 4 to 5B Events 493 and 593 of FIG. 4 ). At block 910, the UE 102 alternatively determines whether the conditions for initiating RA-SDT are met. In an implementation where the conditions are met, the flow proceeds to block 912. Otherwise, the flow proceeds to block 916. At block 912, the UE 102 further determines whether the UE 102 or the RAN 105 supports RA-SDT communications. In an implementation where either supports RA-SDT communications, the flow proceeds to block 914. Otherwise, the flow proceeds to block 916. At block 914, when operating in an inactive state, the UE 102 continues to perform RA-SDT procedures with the RAN 105 (e.g., Figures 4 to 5B At block 916, UE 102 performs an RRC recovery procedure with RAN 105 to transition from the inactive state to the connected state (e.g., Figures 4 to 5B Events 495 and 595).

[0183] In some implementations, the conditions for initiating CG-SDT include: Fig. 7A Conditions 1), 2), 3) and / or 4), and / or 5) described herein are that at least one SSB configured for CG-SDT is available, where the synchronization signal reference signal received power (SS-RSRP) is above the CG-SDT RSRP threshold (e.g., cg-SDT-RSRP-ThresholdSSB). In some implementations, the CG-SDT configuration includes the CG-SDT RSRP threshold. In some implementations, the conditions for initiating RA-SDT include: Fig. 7A Conditions 1), 2), 3) and / or 4) described.

[0184] The examples and implementations described in the previous figures may be applicable to Fig. 9 .

[0185] Next reference Fig.10, method 1000 can be implemented in a suitable UE and includes indicating that CG-SDT communication is supported and RA-SDT communication is not supported before performing CG-SDT according to a configuration received from a RAN.

[0186] At block 1002, the UE 102 sends a message to a node of the RAN 105 (such as the base station 104) indicating that CG-SDT communication is supported but RA-SDT communication is not supported ( Figures 3 to 6 At block 1004, UE 102 receives an SDT configuration including a CG-SDT configuration from RAN 105 ( Figures 3 to 6 At block 1006, UE 102 performs CG-SDT with RAN 105 according to the CG-SDT configuration (e.g., Figures 4 to 6 In some implementations, the UE 102 configures time and / or frequency resources according to the CG-SDT configuration before performing a CG-SDT with the RAN 105. At block 1008, the UE 102 performs a random access procedure with the RAN 105 during the CG-SDT, regardless of whether RA-SDT communications are supported. In some implementations, the UE 102 determines that the UE 102 is between transmission periods based on the time or frequency resources configured according to the CG-SDT configuration, and in response, determines to perform a random access procedure between the periods, as described below with respect to Fig.13 Describe in more detail.

[0187] Next reference Fig.11 , method 1100 may be implemented in a suitable UE and includes determining whether to configure RA-SDT for UE 102 based on whether UE 102 supports RA-SDT communication.

[0188] At block 1102, the UE 102 receives an SDT configuration including an SDT common configuration and a CG-SDT configuration from a node of the RAN 105 (such as the base station 104). Figures 3 to 6 334 / 394, 402 / 434 / 494, 502 / 594, and 602 / 694). At block 1104, the flow diverges based on whether UE 102 supports RA-SDT communications. In implementations where UE 102 does support RA-SDT communications, the flow continues to block 1106. Otherwise, the flow continues to block 1108. At block 1106, UE 102 determines that RA-SDT is configured ( Figures 3 to 6At block 1108, UE 102 determines that RA-SDT is not configured ( Figures 3 to 6 In implementations where the UE 102 does not support RA-SDT communication and receives an SDT configuration that does not include a RA-SDT specific configuration, the UE 102 still determines that the SDT configuration is valid.

[0189] In some implementations, UE 102 sends a message to RAN 105 indicating support for CG-SDT communications. For example, UE 102 may send a message (e.g., UECapabilityInformation) including CG-SDT capabilities to RAN 105. In another example, UE 102 may send a message including a capability ID to CN 110 via RAN 105, which capability ID identifies multiple UE capabilities of UE 102. The multiple UE capabilities may include CG-SDT capabilities. In some such implementations, RAN 105 receives UE capabilities from CN 110 and includes the CG-SDT configuration in the SDT configuration in response to receiving the CG-SDT capabilities.

[0190] The examples and implementations described in the previous figures may be applicable to Fig.11 .

[0191] Next reference Fig.12 , method 1200 may be implemented in a suitable UE and includes selecting a second cell and sending an uplink packet to the RAN, and determining whether to include SDT data in the uplink packet based on whether the UE or the RAN supports RA-SDT communication.

[0192] At block 1202, the UE 102 receives an SDT configuration including an SDT common configuration and a CG-SDT configuration from a node of the RAN 105 (such as the base station 104) via a first cell. Figures 3 to 6 334 / 394, 402 / 434 / 494, 502 / 594 and 602 / 694). At block 1204, UE 102 selects or reselects a second cell. At block 1206, after selecting or reselecting the second cell, UE 102 initiates an RRC recovery procedure to send SDT data with RAN 105 via the second cell. At block 1208, UE 102 performs a random access procedure ( Figure 4 and Figure 6At block 1210, UE 102 includes the RRC recovery request message in an uplink packet such as a MAC PDU (e.g., Figure 4 and Figure 6 At block 1212, the UE 102 determines whether the UE 102 and / or the RAN 105 support RA-SDT communication. In implementations where at least one supports RA-SDT communication, the flow proceeds to block 1214. Otherwise, the flow proceeds directly to block 1216. At block 1214, the UE 102 includes the SDT data in the uplink packet (e.g., Figure 4 and Figure 6 At block 1216, UE 102 sends an uplink packet to RAN 105 via the second cell using the uplink dynamic grant for the random access procedure (e.g., Figure 4 and Figure 6 Events 493 / 495 and 694).

[0193] The examples and implementations described in the previous figures may be applicable to Fig.12 .

[0194] Next reference Fig.13 , method 1300 can be implemented in a suitable UE and includes determining whether to send an SDT data packet using a configured grant or a dynamic grant based on whether the UE performs a random access procedure during a CG-SDT.

[0195] At block 1302, the UE 102 receives an SDT configuration including an SDT common configuration and a CG-SDT configuration from a node of the RAN 105 (such as the base station 104). Figures 3 to 6 At block 1304, when operating in an inactive state, UE 102 performs a random access procedure to send a first SDT data packet ( Figures 4 to 6 404 / 494 / 495, 542 / 592, and 604 / 694 / 695 of FIG. ... Figures 4 to 6404 / 494 / 495, 542 / 592 and 604 / 694 / 695 of FIG. ... of FIG. 404 / 494 / 495, 542 / 592 and 604 / 694 / 695 of FIG. 404 / 494 / 495 of FIG. 40 Figures 4 to 6 At block 1312, UE 102 sends an RRC resume request message ( RRC_RESUME_RETURN_PREQUEST_MESSAGE_TO_RAN 105 ) using the uplink grant for the random access procedure. Figures 4 to 6 Depending on the implementation, the configuration of the uplink grant is similar to the uplink grant in block 1308. At block 1314, the UE 102 receives an RRC resume message (e.g., Figure 5A and Figure 5B At block 1316, UE 102 transitions to a connected state (e.g., Figure 5A and Figure 5B At block 1318, UE 102 uses dynamic authorization and sends the first SDT data packet to RAN 105 after transitioning to the connected state (e.g., Figure 5A and 5B In some implementations, at block 1320, the UE 102 sends a second portion of the first SDT data packet or a second SDT data packet (e.g., Figure 5A and Figure 5B In some implementations, when the UE 102 does not support RA-SDT communication, the UE 102 only performs the method 1300. In such implementations, when the UE 102 does support RA-SDT communication, the UE 102 instead performs RA-SDT communication according to the methods described herein.

[0196] The examples and implementations described in the previous figures may be applicable to Fig.13 .

[0197] Next reference Fig.14 , method 1400 may be implemented in a suitable UE and includes managing small data transmissions with a network.

[0198] At block 1402, UE 102 operates in a state of a protocol for controlling radio resources, wherein the UE is not connected to a RAN (e.g., Figures 4 to 9492 / 493 / 494, 592 / 593 / 595, 692 / 694, 704, 804, and 904). Depending on the implementation, this state is an inactive state or an idle state. At block 1404, UE 102 receives an SDT configuration (e.g., Figures 3 to 11 At block 1406, the UE 102 performs a communication procedure (e.g., RA-SDT) with the RAN node based on whether the UE and the RAN node support a SDT type that depends on a random access procedure (e.g., RA-SDT). Figures 4 to 5B and FIG. 7A to FIG. 11 events 493 / 495, 593 / 595, 705 / 706 / 707 / 708 / 710, 806 / 808 / 810, 912 / 914 / 916, 1006 and 1104 / 1106 / 1108).

[0199] The examples and implementations described in the previous figures may be applicable to Fig.14 .

[0200] Next reference Fig.15 , method 1500 may be implemented in a suitable UE and includes managing small data transmissions with a network.

[0201] At block 1502, UE 102 receives an SDT configuration (e.g., Figures 3 to 6 , Fig.12 and Fig.13 At block 1504, UE 102 performs a random access procedure (e.g., Figure 4 , Figure 6 , Fig.12 and Fig.13 At block 1506, UE 102 sends a data packet to the RAN node on one of the uplink configured grants or the dynamic grants (e.g., Figure 4 , Figure 6 , Fig.12 and Fig.13 Events 493 / 495, 694, 1212 / 1216 and 1306 / 1308 / 1318).

[0202] The examples and implementations described in the previous figures may be applicable to Fig.15 .

[0203] The following list of examples reflects the various embodiments expressly contemplated by the present disclosure:

[0204] Example 1. A method for managing small data transfer (SDT) with a radio access network (RAN) including a RAN node, the method being implemented in a user equipment (UE) and comprising: operating in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; receiving an SDT configuration from the RAN; and performing a communication procedure with the RAN node to send or receive small data based on whether the UE and the RAN node support an SDT type that depends on a random access procedure.

[0205] Example 2. The method as described in Example 1, wherein executing the communication process includes: in a first case, when the UE supports the SDT type, executing the SDT process according to the SDT type; and in a second case, when the UE does not support the SDT type, executing a recovery process.

[0206] Example 3. The method of Example 2 further comprises: sending an indication to the RAN node that the UE supports RA-SDT.

[0207] Example 4. The method as described in Example 2 or 3 further includes: when the support flag is set to a first value, determining that the UE supports the SDT type; and when the support flag is set to a second value, determining that the UE does not support the SDT type.

[0208] Example 5. The method as described in Example 2 or 3 further includes: when the UE stores a support flag, determining that the UE supports the SDT type; and when the UE does not store the support flag, determining that the UE does not support the SDT type.

[0209] Example 6. The method as described in Example 1, wherein performing the communication process includes: in a first case, when the RAN node supports the SDT type, performing the SDT process according to the SDT type; and in a second case, when the RAN node does not support SDT type communication, performing a recovery process.

[0210] Example 7. The method of Example 6, further comprising: when the SDT configuration includes a configuration specific to the SDT type, determining that the RAN node supports the SDT type based on the SDT configuration.

[0211] Example 8. The method of Example 6 or 7, further comprising: when the SDT configuration does not include a configuration specific to the SDT type, determining that the RAN node does not support RA-SDT communication based on the SDT configuration.

[0212] Example 9. The method of Example 7 or 8, wherein the configuration specific to the SDT type comprises at least one of: (i) a random access configuration or (ii) a timer value for the SDT type.

[0213] Example 10. A method as described in any of the preceding examples, wherein executing the communication process includes: when the UE and the RAN node support the SDT type, executing the SDT process according to the SDT type; and when at least one of the UE or the RAN node does not support the SDT type, executing a recovery process.

[0214] Example 11. A method as described in any of the preceding examples, wherein performing the communication process comprises: initiating an SDT communication process; and determining whether at least one of the UE or the RAN node supports the SDT type after initiating the SDT communication process.

[0215] Example 12. The method of Example 11, further comprising: after determining that at least one of the UE or the RAN node does not support the SDT type, stopping the SDT communication process.

[0216] Example 13. The method of Example 11 or 12, wherein the initiating is in response to determining that one or more SDT initiation conditions are satisfied.

[0217] Example 14. A method as described in Example 13, wherein the one or more SDT initiation conditions include at least one of the following: (i) whether the system information block of the cell currently used by the UE includes an SDT configuration; (ii) whether all pending data for transmission are associated with a radio bearer for SDT; (iii) whether the data volume of all pending data is lower than or equal to a first predetermined threshold; or (iv) whether the signal strength of a downlink path loss reference is higher than a second predetermined threshold.

[0218] Example 15. The method of Example 1, further comprising: detecting whether one or more initiation conditions for the SDT type are satisfied; wherein the performing is further based on whether the one or more initiation conditions for the SDT type are satisfied.

[0219] Example 16. A method as described in Example 15, wherein executing the communication process includes: when at least one of the UE or the RAN node supports the SDT type and satisfies the one or more initiation conditions for the SDT type, executing the SDT process according to the SDT type; and when the UE and the RAN node do not support the SDT type or do not satisfy the one or more initiation conditions for the SDT type, executing a recovery process.

[0220] Example 17. A method as described in any of the preceding examples, wherein the SDT type is a first SDT type, and the SDT configuration includes a configuration of a second SDT type that depends on resources previously allocated to the UE, the method further comprising: detecting whether one or more initiation conditions for the second SDT type are met; and further wherein the execution is further based on whether the one or more initiation conditions for the second SDT type are met.

[0221] Example 18. A method as described in Example 24, wherein executing the communication process includes: in a first case, when the one or more initiation conditions for the second SDT type are met, executing the SDT process according to the second SDT type; and in a second case, when the one or more initiation conditions for the second SDT type are not met, executing one of the SDT process or the recovery process according to the first type.

[0222] Example 19. The method of Example 17 or 18, wherein the performing is further based on at least whether the UE supports the second SDT type.

[0223] Example 20. The method of Example 19, further comprising: determining that the UE supports the second SDT type when the support flag is set to a first value; and determining that the UE does not support the SDT type when the support flag is set to a second value.

[0224] Example 21. The method as described in Example 19 further includes: when the UE stores a support flag, determining that the UE supports the second SDT type; and when the UE does not store the support flag, determining that the UE does not support the second SDT type.

[0225] Example 22. The method of any one of Examples 17 to 21, wherein receiving the SDT configuration is in response to sending a message to the RAN indicating that the UE supports at least one of the first SDT type or the second SDT type.

[0226] Example 23. The method as described in Example 22 further includes: performing a random access procedure during the SDT process regardless of whether the UE supports the first SDT type.

[0227] Example 24. A method as described in Example 1, wherein the SDT configuration includes an SDT configuration common to multiple types of SDT communications, and further wherein executing the communication process includes: determining whether the UE is configured according to the SDT type based on whether the UE supports the SDT type; and executing the communication process based on the determination.

[0228] Example 25. The method of Example 24, wherein the SDT type is a first SDT type, the SDT configuration further includes a configuration for the second SDT type, and receiving the SDT configuration is in response to sending a message including one or more SDT capabilities of the UE to the RAN node.

[0229] Example 26. A method for managing small data transfer (SDT) with a radio access network (RAN) comprising a RAN node, the method being implemented in a user equipment (UE) and comprising: receiving an SDT configuration from the RAN node; performing a random access procedure; and sending a data packet to the RAN node on one of an uplink configured grant or a dynamic grant based at least on whether the UE and the RAN node support an SDT type that depends on the random access procedure.

[0230] Example 27. A method as described in Example 26, wherein receiving the SDT configuration is performed via a first cell, the method further comprising: selecting a second cell for communicating with the RAN node; and initiating a recovery process to send SDT data associated with the SDT configuration via the second cell; wherein sending the data packet includes sending the data packet on the uplink as configured.

[0231] Example 28. The method of Example 27, wherein when at least one of the UE or the RAN node supports the SDT type, the data packet includes the SDT data associated with the SDT configuration.

[0232] Example 29. The method of Example 28, wherein the data packet includes a recovery message.

[0233] Example 30. A method as described in Example 26, wherein the SDT type is a first SDT type, the SDT configuration includes a configuration of a second SDT type that depends on resources previously allocated to the UE, and at least one of the UE or the RAN node does not support the first SDT type, further wherein the sending includes: sending the data packet based on whether the random access procedure is during communication according to the second SDT type.

[0234] Example 31. The method of Example 30, further comprising: determining a transmission schedule based on resources associated with the second SDT type; wherein the sending the data packet is in response to determining that the data packet is sent without complying with the transmission schedule.

[0235] Example 32. A method as described in Example 30, wherein the sending includes: sending the data packet on the uplink configured grant when the random access procedure occurs during the communication according to the second SDT type; and sending the data packet on the dynamic grant when the random access procedure does not occur during the communication according to the second SDT type.

[0236] Example 33. The method of Example 32, wherein the data packet is a first portion of a data packet, and further wherein the random access procedure occurs during the communication according to the second type, the method further comprising: sending a second portion of the data packet using the configuration for the second type.

[0237] Example 34. A method as described in Example 32, wherein the random access process does not occur during the communication according to the second type, the method further comprising: sending a recovery message using the dynamic grant; and in response to sending the recovery message, receiving an indication for transitioning to a connected state; wherein sending the data packet includes sending the data packet on the dynamic grant.

[0238] Example 35. The method of Example 34, wherein the data packet is a first portion of data packets, the method further comprising: sending a second portion of the data packet on the dynamic grant.

[0239] Example 36. A user device comprising processing hardware and configured to implement any of the preceding examples.

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

[0241] In general, the description for any one of the above figures may apply to the other of the above figures. The above events or boxes may be optional or omitted. For example, the events or boxes with dotted lines in the figure may be optional. In some implementations, "message" is used, and "message" can be replaced with "information element (IE)", and vice versa. In some implementations, "IE" is used and "field" can be replaced with "IE", and vice versa. In some implementations, "configuration" or "configuration parameter" can be replaced with "configuration", and vice versa. In some implementations, "early data transmission (EDT)" can be replaced with "small data transmission", and "SDT" can be replaced with "EDT", and vice versa. In some implementations, "small data transmission" can be replaced with "small data communication", and vice versa. In some implementations, "stop" can be replaced with "pause".

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

[0243] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. In addition, in some cases, the user device can be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

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

[0245] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method for managing a small data transfer (SDT) with a radio access network (RAN) comprising a RAN node, the method being implemented in a user equipment (UE) and comprising: operating in a state of a protocol for controlling radio resources wherein the UE is not connected to the RAN; receiving an SDT configuration from the RAN; In the first case, when the UE supports an SDT type that depends on a random access procedure, performing an SDT procedure according to the SDT type; as well as In the second case, when the UE does not support the SDT type, the SDT process is avoided.

2. The method of claim 1, wherein said avoiding comprises: In the second case, when the UE does not support the SDT type, a recovery procedure is performed.

3. The method of claim 1 or 2, wherein the SDT type is RA-SDT, and the method further comprises, in the first case: Sending an indication to the RAN node that the UE supports RA-SDT.

4. The method of any one of the preceding claims, wherein the SDT type is a first SDT type, the method further comprising: detecting whether one or more initiation conditions are met for a second SDT type dependent on resources previously allocated to the UE; as well as Prior to the performing in the first case or the avoiding in the second case, it is determined that the one or more initiating conditions are not satisfied.

5. The method of claim 4, further comprising: In a third case, when the one or more initiation conditions are met, the SDT process is performed according to the second SDT type.

6. The method of claim 1, wherein the first case further corresponds to when the RAN node supports the SDT type.

7. The method of claim 6, wherein said avoiding comprises: In the second case, when the RAN node does not support the SDT type, a recovery procedure is performed.

8. The method of claim 6 or 7, further comprising: When the SDT configuration includes a configuration specific to the SDT type, it is determined based on the SDT configuration that the RAN node supports the SDT type.

9. The method according to any one of claims 6 to 8, further comprising: When the SDT configuration does not include a configuration specific to the SDT type, determining that the RAN node does not support SDT type communication based on the SDT configuration.

10. The method of claim 8 or 9, wherein the configuration specific to the SDT type comprises at least one of: (i) a random access configuration or (ii) a timer value for the SDT type.

11. The method of any one of the preceding claims, further comprising: Initiate SDT communication process; as well as After initiating the SDT communication process, it is determined whether the UE supports the SDT type.

12. The method of claim 11, further comprising: In the second case, after determining that the UE does not support the SDT type, the SDT communication process is stopped.

13. The method of claim 11 or 12, wherein the initiating is in response to determining that one or more SDT initiation conditions are satisfied.

14. The method of claim 13, wherein the one or more SDT initiation conditions include at least one of the following: (i) whether the system information block of the cell currently used by the UE includes an SDT configuration; (ii) whether all pending data for transmission are associated with a radio bearer of the SDT; (iii) whether the amount of all data to be processed is less than or equal to a first predetermined threshold; or (iv) Whether the signal strength of the downlink path loss reference is higher than a second predetermined threshold.

15. A user equipment comprising processing hardware and configured to implement any of the preceding claims.