Managing uplink synchronization at user equipment
By managing time alignment timer and CG-SDT configuration in the UE, the uplink synchronization problem of UE in the inactive state is solved, and the efficiency and latency performance of data communication are improved.
Patent Information
- Application Number
- CN202380030370.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-11-10
- Filing Date
- 2023-02-10
- Publication Date
- 2024-11-12
AI Technical Summary
When the user equipment (UE) of the cellular radio access network is inactive or idle state, synchronization issues of uplink and downlink data communications are managed, resulting in data communication delays and network inefficiency.
After receiving the timing advance command, the UE starts or restarts the time alignment timer and manages the second time alignment timer configured by the CG-SDT to ensure the uplink. synchronous.
By effectively managing the time alignment timer, the UE can maintain synchronization of data communication during the state transition between the UE and the radio access network, reduce data communication delays and improve network efficiency.
Smart Images

Figure CN118947185A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, and more particularly to communication of uplink and / or downlink data between a user equipment (UE) and a radio access network (RAN) when the UE is operating in an inactive or idle state associated with a protocol for controlling radio resources. Background Art
[0002] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors (to the extent that it is described in this background section) and aspects of the specification that may not have been identified as prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.
[0003] In general, a base station operating a cellular radio access network (RAN) communicates with a user equipment (UE) using a specific radio access technology (RAT) and multiple layers of a protocol stack. For example, the physical layer (PHY) of the RAT provides a transport channel to the medium access control (MAC) sublayer, which in turn provides a logical channel to the radio link control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.
[0004] The RRC sublayer defines: an RRC_IDLE state, in which the UE does not have an active radio connection with a base station; an RRC_CONNECTED state, in which the UE has an active radio connection with a base station; and an RRC_INACTIVE state, which allows the UE to transition back to the RRC_CONNECTED state more quickly using RAN-level base station coordination and RAN paging procedures. In some cases, a UE in the RRC_INACTIVE state has only a relatively small packet to send. For situations such as these, 3GPP is discussing a small data transmission (SDT) procedure to enable 5G NR (New Radio), a wireless communication standard, to support data transmission by UEs operating in the RRC_INACTIVE state (i.e., without requiring the UE to transition to the RRC_CONNECTED state).
[0005] SDT is enabled on a radio bearer basis and is initiated by the UE only when: (1) the amount of uplink data to be sent (across all radio bearers for which SDT is enabled) is below a configured threshold, (2) the downlink (DL) reference signal received power (RSRP) is above a configured threshold, and (3) valid SDT resources are available. The SDT procedure can be initiated by the UE using a transmission on the random access channel (RACH) (i.e., random access SDT (RA-SDT)) or a type 1 configured grant (CG) resource (i.e., CG-SDT). For RA-SDT, the network configures 2-step and / or 4-step random access resources for SDT. In RA-SDT, the UE can send an initial transmission including data in message 3 (Msg) of a 4-step random access procedure or in the payload of message A (MsgA) of a 2-step random access procedure. Then, after the random access procedure is completed, the network can schedule subsequent uplink and / or downlink transmissions using dynamic uplink grants and downlink assignments, respectively.
[0006] CG-SDT can only be initiated with a valid uplink (UL) timing alignment. The UE maintains UL time alignment based on the network-configured SDT-specific time alignment timer and the configured number of DL RSRPs of the highest-ranked SSBs (synchronization signal blocks). When the SDT-specific time alignment timer expires, the CG resources are released. When CG-SDT is initiated, the UE sends an initial transmission including data on the CG opportunity using the CG configuration, and the network may schedule subsequent UL transmissions using dynamic grants on future CG resource opportunities. During CG-SDT, DL transmissions are scheduled using dynamic assignment. The UE can initiate subsequent UL transmissions only after receiving confirmation of the initial UL transmission from the network.
[0007] However, it is unclear how to manage UL synchronization for CG-SDT. Failure to properly manage UL synchronization may result in data communication delays and / or other network inefficiencies. Summary of the invention
[0008] In some implementations of the present disclosure, the UE maintains only one time alignment timer at any given moment. In particular, when the base station transitions the UE from a connected state to an inactive state and configures the UE for CG-SDT operation (e.g., by sending an RRC release message containing a CG-SDT configuration to the UE), the UE stops a first time alignment timer for connected state communications with the RAN, and starts or restarts a second time alignment timer for CG-SDT communications with the RAN. Later, when transitioning back to the connected state, the UE may stop the second time alignment timer and start the first time alignment timer.
[0009] In other implementations, when the base station transitions the UE from a connected state to an inactive state and configures the UE for CG-SDT operation, the UE starts or restarts a second time alignment timer (i.e., a timer for CG-SDT communication with the RAN), but continues to run a first time alignment timer (i.e., a timer for connected state communication with the RAN). In some implementations in which the base station transitions the UE to an inactive state by sending an RRC release message to the UE, for example, the UE avoids stopping the first time alignment timer only if the base station includes the CG-SDT configuration in the RRC release message. For example, the UE may avoid stopping the first time alignment timer even if the UE resets the MAC entity upon receiving the RRC release message.
[0010] In still other implementations, the UE does not use a dedicated CG-SDT time alignment timer and instead uses the same time alignment timer for both connected state communications with the RAN and CG-SDT communications. In these implementations, the UE restarts the (single) time alignment timer when the base station transitions the UE from the connected state to the inactive state and configures the UE for CG-SDT operation.
[0011] As used herein, unless otherwise specifically indicated, a "timer" may refer to a time alignment timer (e.g., a CG-SDT time alignment timer indicating the validity of a CG-SDT configuration for use when the UE is in an inactive state, or a non-CG-SDT time alignment timer indicating the validity of a non-CG-SDT configuration for use when the UE is in a connected state).
[0012] In one aspect, a method for managing time alignment performed by a UE comprises: receiving a timing advance command from a RAN, starting or restarting a first time alignment timer indicating the validity of a CG configuration while the UE is in an RRC connected state with the RAN, and after starting or restarting the first time alignment timer, receiving a first message from the RAN. The method further comprises: in response to the first message, (i) transitioning from the RRC connected state to an RRC inactive state, (ii) stopping the first time alignment timer, and (iii) starting or restarting a second time alignment timer indicating the validity of a CG-SDT configuration while the UE is in the RRC inactive state. The method further comprises: after stopping the first time alignment timer and starting or restarting the second time alignment timer, (i) receiving a second message from the RAN, and (ii) in response to the second message, transitioning from the RRC inactive state to the RRC connected state, restarting the first time alignment timer, and communicating data with the RAN while operating in the RRC connected state. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1A is a block diagram of an example wireless communication system in which user devices and base stations of the present disclosure may implement the techniques of the present disclosure (e.g., for reducing latency in data communications);
[0014] Figure 1B The central unit (CU) and distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.
[0015] Figure 2A yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a base station;
[0016] 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;
[0017] Figures 3 to 5B It shows that Figures 1A to 2B A message sequence diagram of several scenarios in which the apparatus can implement uplink synchronization according to the technology of the present disclosure; and
[0018] Figure 6 to Fig. 9 It is shown that the technology according to the present disclosure can be Figures 1A to 2B Several methods for managing uplink synchronization implemented by one or more devices of. DETAILED DESCRIPTION
[0019] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure to manage early data communications and to transition the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, unless the context clearly indicates a more specific meaning, small data communications may refer to small data transmission (SDT) from a network perspective (i.e., SDT in the downlink direction), or SDT from a UE perspective (i.e., SDT in the uplink direction).
[0020] First reference Figure 1A , the example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the CN 110. For example, the CN 110 may be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.
[0021] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104 and 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). Base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).
[0022] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. In general, the UPF 162 is configured to deliver user plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions.
[0023] 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.
[0024] As discussed in detail below, the UE 102 and / or the RAN 105 may utilize the techniques of this disclosure when a radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 is operating in an inactive or idle state of a protocol for controlling radio resources between the UE 102 and the RAN 105. For clarity, the following examples relate to the RRC_INACTIVE or RRC_IDLE states of the RRC protocol.
[0025] As used herein, and unless a more specific meaning is indicated from the context of use, the term "data" or "data packet" may refer to signaling, control plane information at a protocol layer that controls radio resources (e.g., RRC), controls mobility management (MM), or controls session management (SM), or may refer to non-signaling, non-control plane information at one or more protocol layers above the layer of a protocol for controlling radio resources (e.g., RRC), above the layer of a protocol for controlling MM, above the layer of a protocol for controlling SM, and / or above the layer of a protocol for controlling quality of service (QoS) flows (e.g., Service Data Adaptation Protocol (SDAP)). The data to which the UE and / or RAN applies the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. Further, as discussed below, in some implementations, the UE 102 applies these techniques only if the size of the data is below a certain threshold. It should also be understood that as used herein (and unless the context of its usage indicates a more specific meaning), the term "configuration" may refer to a complete configuration, or to a subset of parameters of a complete configuration (e.g., an "incremental" or other partial configuration that may augment an existing configuration without completely replacing the existing configuration).
[0026] In the example scenario discussed below, UE 102 transitions to an RRC_INACTIVE or RRC_IDLE state, selects a cell of base station 104, and exchanges data with base station 104 via base station 106 or directly with base station 104 without transitioning to an RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for UL transmission in the RRC_INACTIVE or RRC_IDLE state, UE 102 may apply one or more security functions to UL data packets, generate a first UL protocol data unit (PDU) including a security-protected packet, then include an UL RRC message in a second UL PDU along with the first UL PDU, and then send the second UL PDU to RAN 105. UE 102 includes a UE identity / identifier (ID) of UE 102 in the UL RRC message. RAN 105 may identify UE 102 based on the UE ID. In some implementations, the UE ID may be an inactive radio network temporary identifier (I-RNTI), a recovery ID, or a non-access stratum (NAS) ID. The NAS ID can be an S-Temporary Mobile Subscriber Identity (S-TMSI) or a Globally Unique Temporary Identifier (GUTI).
[0027] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 may generate a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 may encrypt data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 may send the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.
[0028] In some implementations, the data is a UL service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (e.g., a UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which may be associated with a media access control (MAC) layer. Therefore, in these cases, the UE 102 sends the protected UL PDCP PDU in the UL MAC PDU. In some implementations, the UE 102 may include the UL RRC message in the UL MAC PDU. In other implementations, the UE 102 may not include the UL RRC message in the UL MAC PDU. In this case, the UE 102 may not include the UE ID of the UE 102 in the UL MAC PDU that does not include the UL RRC message. In yet other implementations, the UE 102 may include the UL PDCP PDU in the UL RLC PDU, and then include the UL RLC PDU in the UL MAC PDU. In some implementations where the UE 102 includes the UL RRC message in the UL MAC PDU, the UE 102 generates an RRC MAC-I and includes the RRC MAC-I in the UL RRC message. For example, the RRC MAC-I may be a resumeMAC-I field, as specified in 3GPP specification 38.331. In other implementations, the UE 102 may include the UL PDCP PDU in the UL RLC PDU, and then include the UL RLC PDU in the UL MAC PDU. RRCint The RRC MAC-I is obtained from the UL RRC message including a key, an integrity protection algorithm, and parameters such as COUNT (e.g., a 32-bit, 64-bit, or 128-bit value), BEARER (e.g., a 5-bit value), and DIRECTION (e.g., a 1-bit value).
[0029] In other implementations, the data is a UL SDU of NAS. The UE 102 applies a security function to the SDU and includes the protected SDU in a first UL PDU (such as a NAS PDU), which may be associated with a NAS layer. For example, the NAS layer may be an MM sublayer or an SM sublayer of 5G, an evolved packet system (EPS), or 6G. The UE 102 may then include the UL NASPDU in a second UL PDU (such as a UL RRC message). Thus, in these cases, the UE 102 sends the (first) protected UL NAS PDU in the UL RRC message. In some implementations, the UE 102 may include the UL RRC message in a UL MAC PDU and send the UL MAC PDU to a base station (e.g., base station 104 or 106) via a cell (e.g., cell 124 or 126). In this case, the UE 102 may not include the RRC MAC-I in the UL RRC message. Alternatively, the UE 102 may include the RRC MAC-I as described above.
[0030] In some implementations, the UL RRC message described above may be a common control channel (CCCH) message, an RRC recovery request message, or an RRC early data request message.The UL RRC message may include the UE ID of the UE 102 as described above.
[0031] More generally, the UE 102 may protect data using ciphering and / or integrity protection, include the protected data as a security-protected packet in a first UL PDU, and send the first UL PDU to the RAN 105 in a second UL PDU.
[0032] In some scenarios and implementations, the base station 106 may retrieve the UE ID of the UE 102 from the UL RRC message and identify the base station 104 as the destination of the data in the first UL PDU based on the determined UE ID. In one example implementation, the base station 106 retrieves the first UL PDU from the second UL PDU and sends the first UL PDU to the base station 104. The base station 104 then retrieves the security-protected packet from the first UL PDU, applies one or two security functions to decrypt the data and / or check integrity protection, and sends the data to the CN 110 (e.g., SGW 112, UPF 162, MME 114, or AMF 164) or an edge server. In some implementations, the edge server may operate within the RAN 105. More specifically, the base station 104 derives at least one security key from the UE context information of the UE 102. The base station 104 then retrieves the data from the security-protected packet by using the at least one security key and sends the data to the CN 110 or the edge server. When the security-protected packet is an encrypted packet, the base station 104 obtains data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 104 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.
[0033] In another implementation, the base station 106 retrieves the security-protected packet from the first UL PDU and performs a retrieve UE context procedure with the base station 104 to obtain UE context information of the UE 102 from the base station 104. Then, the base station 106 derives at least one security key from the UE context information. Thereafter, the base station 106 retrieves data from the security-protected packet by using at least one security key and sends the data to the CN 110 (e.g., UPF 162) or an edge server. When the security-protected packet is an encrypted packet, the base station 106 obtains the data by decrypting the encrypted packet using at least one security key (e.g., encryption and / or decryption key). If the security-protected packet is an integrity-protected packet, the integrity-protected packet may include data and MAC-I. The base station 106 may verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. Further, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet may include the encrypted packet together with the encrypted MAC-I. In this case, the base station 106 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The base station 106 then determines whether the MAC-I is valid for the data. If the base station 106 determines that the MAC-I is valid, the base station 106 retrieves the data and forwards the data to the CN 110. However, if the base station 106 determines that the MAC-I is invalid, the base station 106 discards the packet.
[0034] In other scenarios and implementations, the base station 104 can retrieve the UE ID of the UE 102 from the UL RRC message and identify that the base station 104 stores the UE context information of the UE 102. Therefore, the base station 104 retrieves the security-protected packet from the first UL PDU, retrieves the data from the security-protected packet, and sends the data to the CN 110 or the edge server, as described above.
[0035] Further, in some implementations and scenarios, the RAN 105 sends data in the DL direction to the UE 102 operating in the RRC_INACTIVE or RRC_IDLE state.
[0036] In one implementation, when the base station 104 determines that data is available for downlink transmission to a UE 102 currently operating in an RRC_INACTIVE or RRC_IDLE state, the base station 104 may apply at least one security function to the data to generate a security-protected packet, generate a first DL PDU including the security-protected packet, and include the first DLPDU in a second DL PDU. In order to protect the data, the base station 104 may apply a security function (e.g., integrity protection and / or encryption) to the DL data. More particularly, when integrity protection is enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data, so that the security-protected packet includes the DL data and the MAC-I. When encryption is enabled, the base station 104 may encrypt the data to generate an encrypted packet, so that the security-protected packet is an encrypted packet. Further, when both integrity protection and encryption are enabled, the base station 104 may generate a MAC-I for protecting the integrity of the data and encrypt the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. In some implementations, the base station 104 generates a first DL PDU (such as a DL PDCP PDU) using the security-protected packet, includes the first DL PDU in a second DL PDU (e.g., a DL MAC PDU) associated with a MAC layer, for example, and 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.
[0037] In another implementation, the base station 104 sends the first DL PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the first DL PDU and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 106 generates a DL RLC PDU including the first DL PDU and includes the DL RLC PDU in the second DL PDU. In yet another implementation, the base station 104 includes the first DL PDU in the DL RLC PDU and sends the DL RLC PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the DL RLC PDU and sends the second DL PDU to the UE 102.
[0038] In some implementations, a base station (i.e., base station 104 or 106) generates downlink control information (DCI) and a cyclic redundancy check (CRC) scrambled with an ID of UE 102 to send a second DL PDU generated by the base station. In some implementations, the ID of UE 102 may be a radio network temporary identifier (RNTI). For example, the RNTI may be a cell RNTI (C-RNTI), a temporary C-RNTI, or an inactive C-RNTI. The base station sends the DCI and the scrambled CRC to UE 102 operating in an RRC_INACTIVE or RRC_IDLE state on a physical downlink control channel (PDCCH). The base station scrambles the CRC with the ID of UE 102. In some implementations, the base station may assign the ID of UE 102 to UE 102 in a random access response or message B (MsgB) sent by the base station in a random access process with UE 102 before sending the DCI and the scrambled CRC. In other implementations, the base station may assign the ID of UE 102 to UE 102 in an RRC message (e.g., an RRC release message or an RRC reconfiguration message) that the base station sends to UE 102 before sending the DCI and the scrambled CRC (e.g., when UE 102 is in the RRC_CONNECTED state).
[0039] UE 102 operating in RRC_INACTIVE or RRC_IDLE state may receive DCI and the scrambled CRC on PDCCH, and then confirm that the physical downlink shared channel (PDSCH) including the second DL PDU is addressed to UE 102 according to the ID of UE 102, DCI and the scrambled CRC. UE 102 may then retrieve data from the security-protected packet. If the security-protected packet is an encrypted packet, UE 102 may decrypt the encrypted packet using an appropriate decryption function and a security key to obtain the data. If the security-protected packet is an integrity-protected packet including data and MAC-I, UE 102 may determine whether MAC-I is valid. If UE 102 confirms that MAC-I is valid, UE 102 retrieves the data. However, if UE 102 determines that MAC-I is invalid, UE 102 discards the packet. If the security-protected packet is both encrypted and integrity-protected (having encrypted data and an encrypted MAC-I), the UE 102 can decrypt the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The UE 102 can then verify that the MAC-I is valid for the data. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves and processes the data. Otherwise, when the UE 102 determines that the MAC-I is invalid, the UE 102 discards the data.
[0040] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a MAC controller 132, which is configured to: perform a random access process with one or more user devices, receive UL MAC protocol data units (PDUs) from one or more user devices, and send DL MAC PDUs to one or more user devices. The processing hardware 130 may also include a PDCP controller 134, which is configured to send and / or receive PDCP PDUs according to the manner in which the base station 104 can send DL data and / or receive UL data. The processing hardware may further include an RRC controller 136 to implement processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 130 includes an RRC inactive controller 138 that is configured to manage uplink and / or downlink communications with one or more UEs operating in an RRC_INACTIVE or RRC_IDLE state. The base station 106 may include substantially similar components. In particular, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to components 130, 132, 134, 136, and 138, respectively.
[0041] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors such as CPUs, and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. In an example implementation, the processing hardware 150 includes an RRC inactive controller 158, which is configured to manage uplink and / or downlink communications when UE 102 operates in an RRC_INACTIVE state. In an example implementation, the processing hardware 150 includes a MAC controller 152, which is configured to perform a random access procedure with a base station, send an uplink MAC PDU to the base station, and receive a downlink MAC PDU from the base station. The processing hardware 150 may also include a PDCP controller 154, which is configured to send and / or receive PDCP PDUs according to the manner in which the base station 106 sends DL data and / or receives UL data. The processing hardware may further include an RRC controller 156 to implement processes and message delivery at the RRC sublayer of the protocol communication stack.
[0042] Figure 1BAn example distributed or decomposed implementation of a base station 170 is depicted, which may represent one or both of base stations 104, 106. In this implementation, base station 170 includes a central unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on general-purpose processors, and / or dedicated processing units. For example, CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as PDCP controllers 134, 144, RRC controllers 136, 146, and / or RRC inactive controllers 138, 148. In some implementations, CU 172 may include an RLC controller configured to manage or control one or more RLC operations or processes. In other implementations, CU 172 does not include an RLC controller.
[0043] 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.
[0044] 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.
[0045] In some implementations, the CU 172 may include a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. The CU 172 may also include a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. The CU-CP 172A may send control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B may send data packets (e.g., SDAPPDUs or Internet Protocol packets).
[0046] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the service requested by UE 102. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In these implementations, connectivity between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.
[0047] Figure 2A An example protocol stack 200 is shown in a simplified manner, according to which a UE 102 can communicate with an eNB / ng-eNB 201A or a gNB 201B (e.g., one or both of base stations 104, 106).
[0048] In the example stack 200, the EUTRA PHY 202A provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 may in turn provide data to the SDAP 212 or RRC sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210.
[0049] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as SDUs (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as PDUs (e.g., to the RLC layer 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as "packets," except where the difference between SDUs and PDUs is relevant.
[0050] On the control plane, for example, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2A The NR PDCP sublayer 210 may be a SDAP PDU, an Internet Protocol (IP) packet, or an Ethernet packet.
[0051] Figure 2B An example protocol stack 250 is shown in a simplified manner in which UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and provides SRBs to the RRC 214.
[0052] Next, refer to Figures 3 to 5B To discuss the Figure 1A The present invention provides various components of the present invention and several example scenarios related to sending data in an inactive or idle state. To simplify the following description, the "inactive state" may represent the RRC_INACTIVE or RRC_IDLE state, and the "connected state" may represent the RRC_CONNECTED state.
[0053] First reference Figure 3, in scenario 300, base station 104 includes CU 172 and DU 174, and CU 172 includes CU-CP 172A and CU-UP 172B. In this scenario 300, UE 102 initially operates in connected state 302, and communicates 304 with DU 174, for example, by using DU configuration (i.e., first non-SDT configuration), and communicates 304 with CU-CP 172A and / or CU-UP 172B via DU by using CU configuration (i.e., first non-SDT CU configuration). While UE is communicating 304 with base station 104, CU-CP 172A may send 306 a UE context modification request message. In response, DU 174 sends 308 a UE context modification response message including a non-SDT configuration for UE 102 (i.e., second non-SDT configuration) to CU-CP 172A. CU-CP 172A generates an RRC reconfiguration message including the non-SDT DU configuration and 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 then 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.
[0054] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the non-SDT DU configuration and communicates with the CU-CP 172A and / or CU-UP 172B via the DU. In the case where the RRC reconfiguration message does not include a CU configuration, the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the first non-SDT CU configuration. In the case where the RRC reconfiguration message includes a non-SDT CU configuration (i.e., a second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the second non-SDT CU configuration. In some implementations, the second non-SDT CU configuration may augment the first non-SDT CU configuration or include at least one new configuration parameter not included in the first non-SDT CU configuration. In these cases, the UE 102 and the CU-CP 172A and / or CU-UP 172B may communicate 318 with each other using the second non-SDT CU configuration and also using configuration parameters in the first non-SDT CU configuration that are not augmented by the second non-SDT CU configuration. In some implementations, the first non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers (e.g., RRC 214 and / or NR PDCP 210), which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT CU configuration may include configuration parameters related to the operation of the RRC and / or PDCP protocol layers, which the UE 102 and CU 172 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT CU configuration may include configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE.
[0055] In some implementations, the second non-SDT DU configuration may extend the first non-SDT DU configuration or include at least one new configuration parameter not included in the first non-SDT DU configuration. In these cases, the UE 102 and the DU 174 may communicate 318 with each other using the second non-SDT DU configuration and also using configuration parameters in the first non-SDT DU configuration that are not extended by the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT DU configuration may include configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers, which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the first non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. Similarly, the second non-SDT DU configuration may include configuration parameters in a CellGroupConfig IE as defined in 3GPP specification 38.331 v16.7.0. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration may be CellGroupConfig IEs.
[0056] Events 306, 308, 310, 312, 314, 316, and 318 are Figure 3 This is collectively referred to as the non-SDT resource (re)configuration process 390, which may be optional.
[0057] While the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration procedure 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., based on the UE 102 in the connected state not having data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource (re) configuration procedure 390 (if performed), the UE 102 determines or detects the data inactivity and sends 320 to the DU 174 UE assistance information (e.g., a UEAssistanceInformation message) indicating that the UE 102 requests to transition to the inactive state configured with SDT. Then, the DU 174 sends 321 to the CU-CP 172A a UL RRC messaging message including the UE assistance information. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CU to DU message (e.g., a UE context setup request message or a UE context modification request message) to DU 174 to request or command DU 174 to perform data inactivity monitoring. In the case where DU 174 detects or determines that UE 102 is in data inactivity during monitoring, DU 174 may send 322 an inactivity notification (e.g., a UE inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from DU 174. In yet other implementations, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the case where CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may send 323 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from CU-UP 172B. In some implementations, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information, an inactivity notification of event 322, and / or an inactivity notification of event 323.
[0058] After a specific period of data inactivity, CU-CP 172A may determine that CU 172 (i.e., CU-CP 172A and / or CU-UP 172B) or UE 102 did not send any data in the downlink direction or uplink direction, respectively, during the specific period. In response to this determination, CU-CP 172A may determine to transition UE 102 to an inactive state with SDT configured. Alternatively, in response to determining that UE 102 is in data inactivity, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured.
[0059] In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 326 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period of time) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, in some implementations, the CU-CP 172A may send 328 a second CU-to-DU message (e.g., a UE context modification request message) to direct the DU 174 to provide an SDT DU configuration for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., an IE, such as a CG-SDT Query Indication IE) for requesting an SDT DU configuration in the second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 may send 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or after sending the second DU-to-CU message, the DU 174 sends an additional DU-to-CU message (e.g., a UE context modification required message) including the SDT DU configuration to the CU-CP 172A. The CU-CP 172A may send an additional CU-to-DU message (e.g., a UE context modification confirmation message) to the DU 174 in response to the additional CU-to-DU message. In some alternative implementations, CU-CP 172A may send a second CU to DU message and receive a second DU to CU message or additional DU to CU messages before determining that UE 102 is in data inactivity. In other alternative implementations, CU-CP 172A may include an SDT request indication in the first CU to DU message of event 308, and DU 174 includes an SDT DU configuration in the first DU to CU message of event 310 in response to the SDT request indication.
[0060] In response to determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., RRCRelease message, RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include the SDT DU configuration (if obtained from DU 174) and / or the SDT CU configuration in the RRC release message. Then, CU-CP 172A sends 332 a third CU-to-DU message (e.g., a UE context release command message, a UE context modification request message, or a DL RRC messaging message) including the RRC release message to DU 174. Subsequently, DU 174 sends 334 the RRC release message to UE 102. In some implementations, DU 174 generates a MAC PDU including the RRC release message and sends 334 the MAC PDU to UE 102. The RRC release message directs UE 102 to transition to an inactive state. UE 102 transitions 336 from the connected state to the inactive state upon receiving the RRC release message. In response to the third CU-to-DU message, DU 174 may retain the SDT DU configuration (if generated by DU 174 during processes 328, 330) and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A in response to the third CU-to-DU message.
[0061] When operating 302 in a connected state, the UE 102 monitors the PDCCH using the C-RNTI to receive DCI. In response to receiving 334 an RRC release message or thereafter, the UE 102 stops monitoring the PDCCH using the C-RNTI. In some implementations, the UE 102 may retain the C-RNTI in response to receiving 334 an RRC release message or in transitioning 336 from a connected state to an inactive state or thereafter. 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.
[0062] 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.
[0063] In some implementations, the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT DU configuration or at least a portion of the first non-SDT DU configuration and at least a portion of the second non-SDT DU configuration in response to the RRC release message. In other implementations, if the RRC release message directs the UE 102 to transition to an inactive state (i.e., RRC_IDLE), the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT configuration. In still other implementations, if the RRC release message directs the UE to transition to an inactive state (i.e., RRC_INACTIVE), the UE 102 releases the first portion of the first and / or second non-SDT DU configuration and retains the second portion of the first and / or second non-SDT DU configuration.
[0064] In some implementations, CU-CP 172A does not include an indication for guiding DU 174 to retain the SDT DU configuration in the third CU to DU message, and DU 174 retains the SDT DU configuration as described above. In other implementations, CU-CP 172A may include an indication for guiding 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 guiding 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, DU 174 retains the SDT DU configuration in response to the third CU to DU message not including the indication. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.
[0065] In some implementations, the SDT CU configuration (e.g., SDT-Config IE) includes a DRB list (e.g., std-DRB-List) including a DRB ID list indicating the IDs of the DRBs configured for SDT. In some implementations, the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. In some implementations, the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. Figure 4 The CU-CP 172A may include an SDT DU configuration in the SDT CU configuration. The "SDT CU configuration" may also be referred to as the "SDT configuration".
[0066] In some implementations, the SDT DU configuration includes at least one of a buffer status report (BSR) configuration, a power headroom report (PHR) configuration, and / or a CG-SDT configuration. The CG-SDT configuration may include or be one or more CG configurations for CG-SDT, a DL bandwidth part (BWP) configuration for CG-SDT, a time alignment timer value for CG-SDT (i.e., a "CG-SDT time alignment timer value"), and / or a timing advance validity threshold for CG-SDT. The DU 174 configures the timing advance validity threshold (e.g., including an RSRP range) for the UE 102 to determine whether the UE 102 can be used as directed to Figure 4 The SDT is initiated using the authorization configuration configured for the CG-SDT. Based on the timing advance validity threshold, the UE 102 can evaluate whether the stored timing advance value is still valid. If the UE 102 determines that the stored timing advance value is invalid, the UE 102 can Figure 4 The RA-SDT is initiated with the CU 172 via the DU 174. In some implementations, the SDT DU configuration may be an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE.
[0067] In some implementations, the DU 174 may start or restart the DU CG-SDT timer in response to or after receiving an SDT request indication, generating a CG-SDT configuration, receiving 328 a second CU to DU message, sending 330 a CG-SDT configuration to the CU 172, receiving 332 a third CU to DU message, or sending 334 a CG-SDT configuration to the UE 102. In some implementations, the DU 174 may start or restart the DU CG-SDT timer with a timer value to manage the CG-SDT configuration. In some implementations, the timer value is the same as the CG-SDT time alignment timer value. In other implementations, the timer value is close to the CG-SDT time alignment timer value. For example, the timer value may be greater than and close to the CG-SDT time alignment timer value. In another example, the timer value may be less than and close to the CG-SDT time alignment timer value. If and when the DU CG-SDT timer expires, the DU 174 releases the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 avoids receiving PUSCH transmissions from UE 102 on radio resources reserved or configured for the CG-SDT configuration. When or after the CG-SDT configuration is released, DU 174 may schedule transmissions for other UEs on radio resources reserved or configured for the CG-SDT configuration.
[0068] As described above, in some implementations, the RRC release message 334 may include a CG-SDT configuration. The UE 102 may start or restart a UE CG-SDT timer (e.g., a CG-SDT time alignment timer (CG-SDT-TAT)) in response to or after receiving the CG-SDT configuration. In some implementations, the UE 102 may start or restart the UE CG-SDT timer using a CG-SDT time alignment timer value. If and when the CG-SDT timer expires, the UE 102 releases the CG-SDT configuration. When or after releasing the CG-SDT configuration, the UE 102 avoids sending PUSCH transmissions on radio resources reserved or configured for the CG-SDT configuration.
[0069] In some implementations, DU 174 reserves the radio resources configured in the configured grant configuration. In some implementations, DU 174 releases the radio resources when releasing the SDT DU configuration or the CG-SDT configuration. In the case where DU 174 does not provide the CG-SDT configuration or the SDT DU configuration to CU-CP 172A, DU 174 releases all signaling and user data transmission resources for UE 102 in response to the third CU to DU message. In the case where DU 174 provides the SDT DU configuration or the CG-SDT configuration to CU-CP 172A, DU 174 reserves the signaling and user data transmission resources for UE 102 in response to receiving the third CU to DU message or thereafter.
[0070] In cases 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 these cases, UE 102 may configure RA-SDT as for Figure 4 The RA-SDT with CU 172 is performed via DU 174 .
[0071] In some implementations, when determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may not request DU 174 to provide an SDT DU configuration. In these cases, events 328 and 330 may be omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own (without requesting DU 174 to provide the SDT DU configuration) and include the SDT DU configuration in the RRC release message.
[0072] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In these cases, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 may send the SDT DU configuration to CU-CP 172A as described above. In some implementations, DU 174 may not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In these cases, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 may include the CG-SDT configuration in the SDT DU configuration as described above.
[0073] In some implementations, in the case where UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A may request DU 174 to provide an 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 an SDT DU configuration. When the UE operates 302 in a connected state, CU-CP 172A may receive UE capabilities (e.g., UE-NR-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. UE capabilities indicate whether UE 102 supports CG-SDT. Therefore, CU-CP 172A may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, CU-CP 172A may receive a DU-to-CU message from DU 174 indicating whether DU 174 supports CG-SDT. The DU-to-CU message may be a second DU-to-CU message, a message of event 308 or 316, or a non-UE associated message (e.g., a non-UE associated F1AP message defined in 3GPP specification 38.473).
[0074] In some implementations, DU 174 may determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether UE 102 supports CG-SDT. In addition to whether UE 102 supports CG-SDT, DU 174 may additionally determine whether to provide the SDT DU configuration for UE 102 to CU-CP 172A based on whether DU 174 supports CG-SDT. In the case where UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, DU 174 provides the SDT DU configuration for UE 102 to CU-CP 172A, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, DU 174 does not provide the SDT DU configuration for UE 102 (e.g., DU 174 does not include the SDT DU configuration in the second DU to CU message). When the UE operates in a connected state 302 or in an inactive state before event 302, the DU 174 may receive the UE capabilities from the CU-CP 172A. Therefore, the DU 174 may determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, the DU 174 may send a DU-to-CU message to the CU-CP 172A indicating whether the DU 174 supports or does not support CG-SDT, as described above.
[0075] Reference now Figure 4 , scenario 400 depicts 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 configured with SDT 402. In some implementations or scenarios, UE 102 may be configured as described for Figure 3The transition from a connected state to an inactive state configured with SDT. In these implementations, UE 102 may receive a first SDT CU configuration and / or a first SDT DU configuration in an RRC release message (e.g., event 334). In other implementations or scenarios, UE 102 may transition from an inactive state where SDT is not configured to an inactive state where SDT is configured. For example, UE 102 may receive an RRC release message (e.g., indicating the release of SDT or not including the SDT configuration in the RRC release message) from a base station (e.g., base station 104 or base station 106) that transitions UE 102 to an inactive state but does not configure SDT. In this case, UE 102 transitions to an inactive state where SDT is not configured in response to the RRC release message. A UE 102 in an inactive state where SDT is configured or not configured can perform a RAN Notification Area (RNA) update with a base station without a state transition. During the RNA update, UE 102 receives another RRC release message similar to the RRC release message of event 334 from the base station including the first SDT CU configuration and / or the first SDT DU configuration.
[0076] Later, the UE 102 operating in an inactive state configured with SDT initiates an SDT. In response to or after initiating the SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message, and sends 404 the initial UL MAC PDU to the DU 174 on the cell 124. The UE 102 may start an SDT session timer in response to initiating the SDT. In some implementations, the SDT session timer may be a new timer defined in the RRC specification (e.g., v17.0.0). The DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends 406 the first DU to CU message to the CU-CP 172A. In some implementations, the first DU to CU message may be an initial UL RRC messaging message. In other implementations, the first DU to CU message may be a UL RRC messaging message.
[0077] In scenarios where the UE 102 initiates an SDT to send UL data (e.g., data packets) eligible for SDT, the UE 102 includes the UL data in an initial UL MAC PDU that the UE 102 transmits 404. In scenarios where the UE 102 initiates an SDT to receive DL data, the UE 102 does not include the UL data packets in the initial UL MAC PDU that the UE 102 transmits 404. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging from the DU 174. In these scenarios, the UE 102 may include an SDT indication to indicate to the base station 104 that the UE 102 is initiating an SDT to receive DL data in an initial UL MAC PDU or UL RRC message.
[0078] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to send 404 the UL MAC PDU. In these cases, the SDT may be a RA-SDT. For example, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In the case of the four-step random access procedure, the UE 102 sends a random access preamble to the DU 174, and in response, the DU 174 sends a random access response (RAR) including an uplink grant, a temporary C-RNTI, and a timing advance command to the UE 102, and the UE 102 sends 404 the UL MAC PDU according to the uplink grant. The DU 174 receives 404 the UL MAC PDU according to the uplink grant in the RAR. In the case of the two-step random access procedure, the UE 102 sends 404 a message A (MsgA) including a random access preamble and a UL MAC PDU to the DU 174 according to the two-step random access configuration parameters. UE 102 may receive message B (MsgB) including the temporary C-RNTI and the timing advance command in response to MsgA from DU 174. UE 102 receives two-step random access configuration parameters in system information broadcast by DU 174 on cell 124 before sending 404 the UL MAC PDU. DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.
[0079] When UE 102 successfully resolves the contention problem during the random access procedure, UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3418 UE 102 receives 418 the UL data from the DU 174 using the C-RNTI. UE 102 uses the C-RNTI to monitor the PDCCH from DU 174 to communicate 418 data with DU 174. More specifically, UE 102 receives the DCI and the CRC of the DCI on the PDCCH from DU 174 and verifies the CRC using the C-RNTI. The DCI may include an uplink grant or a downlink assignment. If UE 102 verifies that the CRC is correct and the DCI includes an uplink grant, UE 102 sends 418 UL data to DU 174 using the uplink grant. If UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, UE 102 receives 418 DL data from DU 174 using the downlink assignment.
[0080] In other implementations, in which UE 102 is directed to Figure 3 In the case of receiving the CG configuration for SDT (ie, CG-SDT configuration), the UE 102 may send 404 the UL MAC PDU on the radio resources configured in such configuration. Thus, the DU 174 receives 404 the UL MAC PDU on the radio resources.
[0081] In some implementations, the UE 102 may send 418 subsequent UL MAC PDUs including one or more UL data packets on the radio resources configured in the CG configuration. In some implementations, the UE 102 may send 418 subsequent UL MAC PDUs on the radio resources configured in the uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 may send 418 some subsequent UL MAC PDUs on the radio resources configured in the CG configuration and send 418 other subsequent UL MAC PDUs on the radio resources configured in the uplink grant.
[0082] If UE 102 includes UL data in the initial UL MAC PDU, DU 174 retrieves the UL data from the initial UL MAC PDU. In these cases, DU 174 may include the UL data in the DU to CU message of event 406. Alternatively, DU 174 may send 415 a DU to CU message including UL data to CU-CP 172A. In this alternative, the UL data may include or be a PDCP PDU, an RRC PDU, a NAS PDU, or an LTE Positioning Protocol (LPP) PDU. The PDCP PDU may include an RRCPDU. As yet another alternative, DU 174 may send 416 the UL data separately to CU-UP 172B via a user plane (UP) connection as described below. In this alternative, the UL data may include or be a PDCP PDU, and the PDCP PDU may include an SDAP PDU, an IP packet, or an Ethernet packet.
[0083] After receiving 406 the first DU to CU message, in some implementations, the CU-CP 172A may send 408 a UE context setup request message to the DU 174 to establish a UE context for the UE 102 at the DU 174. In the UE context setup request message, the CU-CP 172A may include transport layer information of one or more GTP-U tunnels between the CU-UP 172B and the DU 174, so that the DU 174 may send UL data and / or subsequent UL data (e.g., in small data communication 418) to the CU-UP 172B via the one or more GTP-U tunnels. In response, the DU 174 may send 410 a UE context setup response message to the CU-CP 172A. After receiving 406 the first DU to CU message, sending 408 the UE context setup request message, or receiving 410 the UE context setup response message, the CU-CP 172A sends 412 a bearer context modification request message to the CU-UP 172B to resume data transmission for the UE 102. In response, CU-UP 172B resumes data transmission for UE 102 and sends 414 a bearer context modification response message to CU-CP 172A. After receiving 408 the UE context setup request message or sending 410 the UE context setup response message, in the case where the UL data of event 404 includes an RRC message or is associated with an SRB (e.g., SRB1 or SRB2), DU 174 may send 415 a DU to CU message including the UL data to CU-CP 172A. In the case where the UL data is associated with a DRB, DU 174 may send 416 the UL data to CU-UP 172B.
[0084] In some implementations, the CU-CP 172A may include the transport layer information of the CU-UP 172B in the UE context setup request message. The transport layer information of the CU-UP 172B may include an IP address and / or an uplink tunnel endpoint ID (e.g., TEID). The DU 174 may send 416 UL data to the CU-UP 172B using the transport layer information of the CU-UP 172B. In the case where the UE 102 has subsequent UL data to send (e.g., one or more UL data packets), the UE 102 may send 418 one or more subsequent UL MAC PDUs including the subsequent UL data to the DU 174. Then, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the case where the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 sends 418 one or more DU to CU messages (e.g., UL RRC messaging messages) including the subsequent UL data to the CU-CP 172A. Each DU to CU message may include a specific UL data packet of subsequent UL data. In the case where the CU-CP 172A receives DL data from the CN 110 or edge server, the CU-CP 172A may send 418 one or more CU to DU messages (e.g., DL RRC messaging messages) including the DL data (e.g., one or more DL data packets) to the DU 174. In turn, the DU 174 sends 418 one or more DL MAC PDUs including the DL data to the UE 102 operating in the inactive state. In some implementations, the DL data may include or be a NAS PDU and / or a LPPPDU.
[0085] In the case where the subsequent UL data is associated with one or more DRBs, DU 174 sends 418 the subsequent UL data to CU-UP 172B, similar to event 416. In some implementations, DU 174 may include DU transport layer information of DU 174 in the UE context setup response message. Then, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. The transport layer information of DU 174 may include an IP address and / or a downlink TEID. In the case where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B may send 418 the DL data (e.g., one or more DL data packets) to DU 174 using the transport layer information of DU 174. Then, DU 174 sends 418 one or more DL MAC PDUs including the DL data to UE 102 operating in an inactive state.
[0086] In some implementations, the UE 102 may include a buffer status report or a power headroom report in an initial and / or subsequent UL MAC PDU, e.g., based on a BSR configuration and / or a PHR configuration, respectively. In a buffer status report, the UE 102 may include or indicate a buffer status of one or more logical channels or logical channel groups thereof. In a power headroom report, the UE 102 may include or indicate a power headroom status or value.
[0087] In some example scenarios, the subsequent UL data and / or DL described above include IP packets, Ethernet packets, or application packets. In other scenarios, the UL data may include or be a PDU (e.g., an RRC PDU, a PDCP PDU, or an RLC PDU) that includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.
[0088] Events 404, 406, 408, 410, 412, 414, 415, and 416 are Figure 4 It is collectively referred to as the small data sending process 492.
[0089] In some implementations, the UL RRC message is an (existing) RRC recovery request message (e.g., RRCResumeRequest message, RRCResumeRequest message, RRCConnectionResumeRequest message, or RRCConnectionResumeRequest message). In other implementations, the UL RRC message may be a new RRC recovery request message similar to the existing RRC recovery request message. For example, the new RRC recovery request message may be defined in a future 3GPP standard document. The new RRC recovery request message may have the format of an existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message may include an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.
[0090] 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 may determine to stop the SDT of the UE 102 based on data inactivity of the UE 102 (i.e., based on the UE 102 in the inactive state having 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 to the DU 174 UE assistance information (e.g., UEAssistanceInformation message) indicating that the UE 102 decides (e.g., needs) or requests to stop the SDT. Then, the DU 174 sends 421 to the CU-CP 172A a UL RRC messaging message including the UE assistance information. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information. In other implementations, DU 174 may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CU to DU message (e.g., a UE context setup request message or a UE context modification request message of event 408) to DU 174 to request or command DU 174 to perform data inactivity monitoring. In the case where DU 174 detects or determines that UE 102 is in data inactivity during monitoring, DU 174 may send 422 an inactivity notification (e.g., a UE inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 is in data inactivity based on an inactivity notification received from DU 174. In yet other implementations, CU-UP 172B may perform data inactivity monitoring for UE 102. CU-CP 172A may send a CP to UP message to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In some implementations, if sent before UE 102 initiates SDT, the CP to UP message may be a bearer context setup request message or a bearer context modification request message. In other implementations, if sent during SDT (e.g., event 412), the CP to UP message may be a bearer context modification request message. In the case where CU-UP 172B detects or determines that UE 102 is in data inactivity during monitoring, CU-UP 172B may send an inactivity notification (e.g., a bearer context inactivity notification message) 423 to CU-CP 172A. Therefore, CU-CP 172A may determine that UE 102 is in data inactivity based on the inactivity notification received from CU-UP 172B.In some implementations, CU-CP 172A may determine that UE 102 is in data inactivity based on UE assistance information, the inactivity notification of event 422 , and / or the inactivity notification of event 423 .
[0091] After a specific period of data inactivity, CU-CP 172A may determine that neither CU 172 nor UE 102 sent any data in the downlink direction or uplink direction, respectively, during the specific period. In response to this determination, CU-CP 172A may determine to stop SDT. Alternatively, CU-CP 172A may determine to stop SDT of UE 102 immediately in response to determining that UE 102 is in data inactivity.
[0092] In response to determining that the UE 102 is in data inactivity (for the specific period) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 424 a bearer context modification request message to the CP-CU 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 426 a bearer context modification response message to the CU-CP 172A. In response to determining that the UE 102 is in data inactivity (for the specific period) or determining to transition the UE 102 to an inactive state configured with SDT or thereafter, the CU-CP 172A sends 428 a second CU-to-DU message (e.g., a UE context modification request message) to instruct the DU 174 to provide an SDTDU configuration (e.g., a second SDT DU configuration) for the UE 102. In some implementations, the CU-CP 172A may include an SDT request indication (e.g., a field or IE) for requesting an SDT DU configuration in a second CU-to-DU message. In response to the SDT request indication or the second CU-to-DU message, the DU 174 sends 430 a second DU-to-CU message (e.g., a UE context modification response message) including the second SDT DU configuration to the CU-CP 172A. Alternatively, the DU 174 does not include the second SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message and / or sending the second DU-to-CU message, the DU 174 sends another DU-to-CU message (e.g., a UE context modification required message) including the second SDTDU configuration to the CU-CP 172A. In some alternative implementations, the CU-CP 172A may send a second CU-to-DU message and receive the second DU-to-CU message (or the other DU-to-CU message) before determining that the UE 102 is in data inactivity.
[0093] In response to determining to transition UE 102 to an inactive state configured with SDT, CU-CP 172A may generate an RRC release message (e.g., an RRCRelease message or an RRCConnectionRelease message) to transition UE 102 to an inactive state. CU-CP 172A may include the second SDT DU configuration (if obtained from DU 174) and the second SDT CU configuration in the RRC release message.
[0094] Alternatively, CU-CP 172A may not include the SDT configuration in the RRC release message. In this alternative, CU-CP 172A may indicate in the RRC release message whether UE 102 releases or retains the first SDT CU configuration and / or the first SDT DU configuration. For example, CU-CP 172A may include a release indication indicating the release of the first SDT CU configuration or the first SDT DU configuration in the RRC release message. If the RRC release message does not include a release indication, UE 102 retains the first SDT CU configuration and / or the first SDT DU configuration.
[0095] Then, the CU-CP 172A sends 432 a third CU-to-DU message including an RRC release message to the DU 174. Then, the DU 174 sends 434 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 434 the MAC PDU to the UE 102. The RRC release message directs the UE 102 to be in an inactive state (e.g., transition to an inactive state or maintain an inactive state). Upon receiving 434 the RRC release message, the UE 102 stops the SDT and remains 436 in an inactive state.
[0096] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 The SDT completion process is collectively referred to as 494.
[0097] During the SDT session (i.e., events 492 and 494), UE 102 monitors PDCCH using C-RNTI to receive DCI. In some implementations, UE 102 receives C-RNTI during the random access procedure described for event 404. In other implementations, UE 102 may receive C-RNTI as described for event 404. Figure 3The receiving and retaining C-RNTI. In response to receiving 434 the RRC release message or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. The UE 102 may retain the C-RNTI in response to receiving 434 the RRC release message or transitioning 436 from the connected state to the inactive state or thereafter. In the case where the RRC release message 434 configures the CG-SDT, in some implementations, the UE 102 may retain the C-RNTI. In the case where the RRC release message 434 does not configure or release the CG-SDT, in some implementations, the UE 102 may release the C-RNTI.
[0098] In some implementations, the second SDT CU configuration may be the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration may be different from the first SDT CU configuration. The UE 102 may update (e.g., replace or modify) the first SDT CU configuration using the second SDT CU configuration. In some implementations, the CU-CP 172A may include an indication in the RRC release message indicating that the UE 102 is to update the first SDT CU configuration using the second SDT CU configuration. In these implementations, the UE 102 may update the first SDT CU configuration using the second SDT CU configuration in response to the indication. In other implementations, the CU-CP 172A may include a modification indication in the RRC release message indicating that the UE 102 is to modify the first SDT CU configuration using the second SDT CU configuration. In these implementations, the UE 102 may modify the first SDT CU configuration using the second SDT CU configuration in response to the modification indication. In yet other implementations, CU-CP 172A may include a setup indication in the RRC release message for indicating that UE 102 is to replace the first SDT CU configuration with the second SDT CU configuration. In these implementations, UE 102 may replace the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.
[0099] In some implementations, the second SDT DU configuration may be the same as the first SDT DU configuration. In other implementations, the second SDT DU configuration may be different from the first SDT DU configuration. The UE 102 may update (e.g., replace or modify) the first SDT DU configuration using the second SDT DU configuration. In some implementations, the DU 174 may include in the second SDT DU configuration an indication indicating that the UE 102 is to update the first SDT DU configuration using the second SDT DU configuration. In these implementations, the UE 102 may update the first SDT DU configuration using the second SDT DU configuration in response to the indication. In some implementations, the DU 174 may include in the second SDT DU configuration a modification indication indicating that the UE 102 is to modify the first SDT DU configuration using the second SDT DU configuration. In these implementations, the UE 102 may modify the first SDT DU configuration using the second SDT DU configuration in response to the modification indication. In yet other implementations, DU 174 may include a setup indication in the second SDT DU configuration for indicating that UE 102 is to replace the first SDT DU configuration with the second SDT DU configuration. In these implementations, UE 102 may replace the first SDT DU configuration with the second SDT DU configuration in response to the setup indication.
[0100] In the case where the CU-CP 172A and / or the DU 174 support incremental configuration, the CU-CP 172A may not send 428 a CU to DU message to obtain a second SDT DU configuration from the DU 174. The DU 174 retains the first SDT DU configuration unless the conditions for releasing the first SDT configuration are met. Alternatively, the CU-CP 172A may include the first SDT DU configuration in the second CU to DU message so that the DU 174 retains the first SDT DU configuration. In these cases, the CU-CP 172A may not include the SDTDU configuration and / or the SDT CU configuration in the RRC release message so that the UE 102 continues to use the first SDT CU configuration and / or the first SDT DU configuration. In some implementations, the CU-CP 172A may not include a release indication in the RRC release message so as to configure the UE 102 to continue to use the first SDT DU configuration and / or the first SDT CU configuration. The release indication indicates that the UE 102 is to release the previously received SDT DU configuration and / or SDT CU configuration. In the case where the CU-CP 172A includes the release indication in the RRC release message, the UE 102 releases the first SDT CU configuration and / or the first SDTDU configuration in response to the release indication.
[0101] In a case where the CU-CP 172A and / or the DU 174 do not support incremental configuration, the CU-CP 172A may include the SDT DU configuration and / or the SDT CU configuration in the RRC release message as described above.
[0102] In response to the third CU-to-DU message, DU 174 may retain the second SDT DU configuration and may or may not release the first non-SDT DU configuration and / or the second non-SDT DU configuration. DU 174 may send a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A in response to the third CU-to-DU message. In some implementations, if the RRC release message directs UE 102 to transition to an inactive state (i.e., RRC_IDLE), UE 102 releases the non-SDT configuration (e.g., for RRC_CONTENT). Figure 3 The first non-SDT DU configuration, the first non-SDT CU configuration, the second non-SDT DU configuration and / or the second non-SDT CU configuration) and at least one SDT configuration (e.g., for Figure 3 The SDTDU configuration and SDT CU configuration described above).
[0103] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 492. The SDT completion process 494 is collectively referred to as the SDT completion process 494, which is similar to the process 394. The examples and implementations for events 320, 321, 322, 323, 324, 326, 328, 330, 332, 334 can be respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, 434. After stopping the SDT, the UE 102 can perform 493 another SDT process with the base station 104 similar to the process 492. After completing the process 493, the base station 104 can perform 495 an SDT completion process with the UE 102 similar to the process 494.
[0104] In some implementations, CU-CP 172A may not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state configured with SDT. In these cases, events 428 and 430 may be omitted. In these cases, CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A may generate the SDT DU configuration on its own and include the SDT DU configuration in the RRC release message.
[0105] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In these cases, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 may include the SDT DU configuration as described above. In some implementations, DU 174 does not include the CG-SDT configuration in the SDT DU configuration in the second DU to CU message, for example, if or because UE 102 does not support CG-SDT, DU 174 does not support CG-SDT, or DU 174 does not have available radio resources for CG-SDT. In these cases, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 may include at least one CG-SDT configuration in the SDT DU configuration as described above.
[0106] In some implementations, in the case where the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the CU-CP 172A may request the DU 174 to provide the SDT DU configuration as described above. In the case where the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the CU-CP 172A does not request the DU 174 to provide the SDT DU configuration. Before the UE 102 initiates SDT, when the UE is operating in an inactive state 402, when the UE performs SDT (e.g., in a UE context setup request message of event 408 or a CU to DU message of event 428), or when the UE is performing SDT such as for Figure 3 When operating in the connected state, CU-CP172A can receive UE capabilities (e.g., UE-NR-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. 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 can receive 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).
[0107] In some implementations, the DU 174 may determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the UE 102 supports CG-SDT. In addition to whether the UE 102 supports CG-SDT, the DU 174 may additionally determine whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A based on whether the DU 174 supports CG-SDT. In the case where the UE 102 supports CG-SDT and / or the DU 174 supports or enables CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the case where the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). For example, when the UE 102 is operating in a connected state or in an inactive state, the DU 174 may receive the UE capabilities from the CU-CP 172A. Therefore, the DU 174 may determine whether the UE 102 supports CG-SDT based on the UE capabilities. In some implementations, the DU 174 may send a DU-to-CU message to the CU-CP 172A indicating whether the DU 174 supports or does not support CG-SDT, as described above.
[0108] Reference now Figure 5A , scenario 500A depicts small data transmission and transition from SDT to non-SDT. In scenario 500A, base station 104 includes CU 172 and DU 174, CU 172 includes CU-CP 172A and CU-UP 172B, and UE 102 initially operates 502 in an inactive state configured with SDT, similar to event 402. Then, UE 102 performs 592 a small data transmission process with base station 104, similar to event 492.
[0109] During the small data transmission process 592, the CU-CP 172A may determine whether to transition the UE 102 to the connected state, for example, based on the UL or DL data activity of the UE 102. In some implementations, the UE 102 may send 503 a non-SDT indication message to the DU 174 to indicate that UL data is available or request to transition to the connected state. In some implementations, the UE 102 may send 503 the non-SDT indication message to the DU 174 on the radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 may receive an uplink grant on the PDCCH from the DU 174 using the C-RNTI, and send 503 the non-SDT indication message to the DU 174 on the radio resources configured in the uplink grant. Then, the DU 174 sends 505 a UL RRC messaging message including the non-SDT indication message to the CU-CP 172A. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a non-SDT indication message. In other implementations, CU-UP 172B receives DL data from CN 110, and in response, sends 507 to CU-CP 172A a DL data notification (e.g., a DL Data Notification message) indicating that DL data is available for transmission. CU-CP 172A may determine to transition UE 102 to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A may determine to transition UE 102 to a connected state based on a measurement result received from UE 102. In yet other implementations, CU-CP 172A receives DL data (e.g., a NAS message) from CN 110, and in response, may determine to transition UE 102 to a connected state.
[0110] In some implementations, the non-SDT indication message may be an RRC message (eg, a UEAssistanceInformation message or a new RRC message).
[0111] In some implementations, UL data and / or DL data are associated with a radio bearer (e.g., SRB and / or DRB). For example, the UL data may include an RRC message or a NAS message associated with the SRB. In another example, the UL data includes an IP packet associated with the DRB. In some implementations, the UE 102 may include the ID of the radio bearer in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transform the UE 102 into a connected state based on the ID. For example, if the radio bearer identified by the ID is not eligible for SDT, the CU-CP 172A may determine to transform the UE 102 into a connected state. Otherwise, the CU-CP 172A may determine not to transform the UE 102 into a connected state. In some implementations, the UE 102 may include the data volume information of the UL data in the non-SDT indication message. Therefore, the CU-CP 172A may determine whether to transform the UE 102 into a connected state based on the data volume information. In one implementation, the data volume information includes the total data volume of the UL data, which can be quantized or rounded to a value that can be indicated in the data volume information. In another implementation, the data volume information includes the data volume of each of the radio bearers, which can be quantized or rounded to a value that can be indicated in the data volume information. For example, if the total data volume is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In another example, if the data volume of a particular radio bearer is higher than a predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A may determine not to transition the UE 102 to a connected state. In yet another example, if the total data volume is higher than a predetermined threshold and the data volume of a particular radio bearer is higher than another predetermined threshold, the CU-CP 172A may determine to transition the UE 102 to a connected state. Otherwise, CU-CP 172A may determine not to transition UE 102 to the connected state.
[0112] In response to or after determining to transition UE 102 to a connected state, CU-CP 172A sends 506 a UE context request message (e.g., a UE context setup request message or a UE context modification request message) to DU 174. In response, DU 174 sends 508 a UE context response message (e.g., a UE context setup response message or a UE context modification response message) to CU-CP 172A. In some implementations, DU 174 may include a non-SDT DU configuration (i.e., a first non-SDT DU configuration) in the UE context response message. After receiving the UE context response message, CU-CP 172A sends 510 a CU to DU message including an RRC resume message (e.g., an RRCResume message or an RRCConnectionResume message) to DU 174. Then, DU 174 sends 512 an RRC resume message to UE 102. In some implementations, DU 174 may send 512 one or more PDUs including the RRC resume message to UE 102. The PDU may be a MAC PDU or an RLC PDU. In some implementations, the CU to DU message may be a DL RRC messaging message or a UE context modification request message. In the case of a UE context modification request message, in response, DU 174 may send a UE context modification response message to CU-CP 172A. In response to receiving the RRC resume message, UE 102 transitions 513 to a connected state and sends 514 an RRC resume completion message (e.g., an RRCResumeComplete message or an RRCConnectionResumeComplete message) to DU 174. In the case where the UE context response message includes a non-SDT DU configuration, CU-CP 172A includes the non-SDT DU configuration in the RRC resume message. DU 174 sends 516 a DU to CU message including an RRC resume completion message to CU-CP 172A. After determining to transition the UE 102 to the connected state, the CU-CP 172A may send 517 a bearer context request message (e.g., a bearer context setup request message or a bearer context modification request message) to the CU-UP 172B to instruct the CU-UP 172B to resume all suspended radio bearers of the UE 102. In response, the CU-UP 172B resumes all suspended radio bearers of the UE 102 and sends 519 a bearer context response message (e.g., a bearer context setup response message or a bearer context modification response message) to the CU CP-172A.In some implementations, the CU-CP 172A may send 517 a bearer context request message after sending 506 a UE context request message, receiving 508 a UE context response message, sending 510 a CU to DU message, or receiving 516 a DU to CU message.
[0113] In some implementations, CU-CP 172A may include an indication indicative of DU 174 generating a non-SDT configuration in a UE context request message, and DU 174 includes the first non-SDT DU configuration in a UE context response message in response to the indication. In yet other implementations, CU-CP 172A stores a non-SDT DU configuration (i.e., a second non-SDT DU configuration) used by a DU (e.g., DU 174 or another DU or base station) to communicate with UE 102. UE 102 may also store a second non-SDT DU configuration. In these cases, CU-CP 172A includes the second non-SDT DU configuration in a UE context request message, and DU 174 may include the first non-SDT DU configuration in a UE context response message in response to receiving the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration augments or replaces the second non-SDT DU configuration. Examples and implementations of the first non-SDT DU configuration and the second non-SDT DU configuration may be the same as those described above for the non-SDT DU configuration. In some implementations, the DU 174 may send an additional DU to CU message (e.g., a UE context modification required message) including the first non-SDT DU configuration to the CU-CP 172A instead of including the first non-SDT DU configuration in the UE context response message.
[0114] After transitioning to the connected state, the UE 102 communicates 518 UL data and / or DL data with the CU-CP 172A and / or CU-UP 172B via the DU 174. The UL data may include UL data that triggers the UE 102 to send a non-SDT indication message. The UL data may also include new UL data available for transmission. The DL data may include DL data received from the CN 110 as described above. The DL data may also include new DL data received from the CN 110. In the case where the RRC recovery message includes the first non-SDT DU configuration, the UE 102 communicates 518 with the DU 174 using the first non-SDT DU configuration. In the case where the second non-SDT DU configuration is not completely replaced by the first non-SDT DU configuration (i.e., the UE 102 does not release the second non-SDT DU configuration in response to the RRC recovery message), the UE 102 may communicate 518 with the DU 174 using configuration parameters in the second non-SDT DU configuration that are not extended by the first non-SDT DU configuration.
[0115] In some implementations, DU 174 may not provide the first non-SDT DU configuration to CU-CP 172A in the UE context response message and the attach DU to CU message. In these cases, 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.
[0116] In some implementations, the UE 102 releases the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration) in response to an RRC recovery message or transitioning to a connected state. In some implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to transitioning the UE 102 to a connected state, receiving 510 a CU to DU message, or sending 510, 512 an RRC recovery message, or thereafter. In other implementations, the base station 104 releases the SDT configuration in response to receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for a PDU including an RRC recovery message, or thereafter. In yet other implementations, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration in response to communicating 506 a UE context request message or communicating 508 a UE context response message, or thereafter.
[0117] In other implementations, in response to receiving an RRC recovery message or transitioning to a connected state or thereafter, the UE 102 retains the SDT configuration (e.g., an SDT CU configuration, an SDT DU configuration, and / or a CG-SDT configuration). In some implementations, when operating in a connected state, the UE 102 avoids communicating with the base station 104 using the SDT configuration (e.g., sending 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, when operating in a connected state, the UE 102 may communicate with the base station 104 using the SDT configuration (e.g., 514 an RRC recovery complete message and / or 518 data). In some implementations, in response to transitioning the UE 102 to a connected state or sending an RRC recovery message or thereafter, the base station 104 retains the SDT configuration. In some implementations, the base station 104 avoids communicating with the UE 102 operating in a connected state using the SDT configuration (e.g., receiving 514 an RRC recovery complete message and / or communicating 518 data). In other implementations, the base station 104 may communicate (eg, receive 514 an RRC recovery complete message and / or communicate 518 data) with a UE 102 operating in a connected state using an SDT configuration.
[0118] At a later time, the base station 104 may perform a non-SDT configuration process 590 and an SDT configuration process 594 with the UE 102, similar to process 390 and process 394, respectively. The UE 102 transitions 536 to an inactive state in response to receiving the RRC release message in process 594. The base station 104 may then perform an SDT process 593 and an SDT completion process 595 with the UE 102, similar to process 492 and process 494, respectively.
[0119] Next reference Figure 5B , scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC connection recovery procedure instead of a small data communication procedure 592. The differences between scenarios 500B and 500A are discussed below.
[0120] In response to initiating the RRC connection 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.
[0121] In some implementations, the UE 102 may generate a UL MAC PDU including the RRC recovery request message and send 542 the UL MAC PDU to the DU 174. In some implementations, the UE 102 may send 542 the UL MAC PDU to the DU 174 on the radio resources configured in the CG configuration for the SDT. In other implementations, the UE 102 may perform a random access procedure to send the UL MAC PDU, similar to event 404.
[0122] Next, refer to FIG. 6A to FIG. 9 Several example methods are discussed that may be implemented / performed by one or more UEs to support data communications (eg, while the UEs are in an inactive state).
[0123] Fig. 6A A method 600A is shown that may be implemented / performed by a UE (eg, UE 102) for managing uplink synchronization with a RAN (eg, RAN 105, or more specifically, base station 104 or DU 174, etc.).
[0124] The method 600A begins at block 602, where the UE receives a timing advance command from the RAN. At block 604, the UE starts or restarts a time alignment timer (which may be the same as the time alignment timer of block 618 discussed below) in response to the timing advance command. In some implementations, if the time alignment timer is running, the UE determines that the timing advance command is valid, the UE's uplink transmission timing is valid, or the UE is synchronized with the base station in uplink transmissions. Conversely, if the UE determines or detects that the time alignment timer expires, the UE determines that the timing advance command is invalid, the UE's uplink transmission timing is invalid, or the UE is not synchronized with the base station in uplink transmissions.
[0125] At box 606, the UE receives a first message (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595) from the RAN that configures the CG-SDT and transitions the UE to an inactive state (or maintains the UE in an inactive state). At box 608, the UE stops the time alignment timer in response to the first message. At box 610, the UE starts or restarts the CG-SDT timer (e.g., the UE CG-SDT timer described above) in response to the first message. In some implementations, if the CG-SDT timer is running, the UE determines that the timing advance command is valid, the UE's uplink transmission timing is valid, the UE is synchronized with the base station in the uplink transmission, and / or the UE is configured with CG-SDT (i.e., the UE is configured with a CG-SDT configuration). Conversely, if the UE determines or detects that the CG-SDT timer expires, the UE determines that the timing advance command is invalid, the UE's uplink transmission timing is invalid, the UE is not synchronized with the base station in the uplink transmission, and / or the CG-SDT or CG-SDT configuration is invalid.
[0126] At block 612 (optional), while the UE is operating in the inactive state, the UE may communicate data with the RAN (e.g., events 404, 406, 415, 416, 418, 492, 592). At block 614, while the UE is operating in the inactive state, the UE receives a second message from the RAN to transition the UE to a connected state (e.g., events 510, 512). At block 616, the UE transitions from the inactive state to the connected state in response to the second message (e.g., event 513). The UE in the connected state then communicates data with the RAN (e.g., events 514, 516, 518). At block 618, the UE starts a time alignment timer after (e.g., in response to) receiving the second message from the RAN or receiving a PDU including the second message. The flow may then proceed to block 602 or 606, depending on whether the UE receives or does not receive a (new) timing advance command from the RAN, respectively.
[0127] In some implementations and / or scenarios, at block 602, when the UE is operating in a connected state, the UE receives a timing advance command (i.e., a first timing advance command) from the RAN. For example, the UE in the connected state may receive a MAC PDU including the first timing advance command from the RAN. The MAC PDU may include a MAC SDU including a data packet or a portion of a data packet. In another example, the UE in the connected state sends a random access preamble to the RAN and receives a random access response including the first timing advance command from the RAN in response. In yet another example, the UE in the connected state sends a message A (MsgA) to the RAN and receives a message B (MsgB) including the first timing advance command from the RAN.
[0128] In some implementations and / or scenarios, at box 602, when the UE is operating in an inactive state, the UE receives a timing advance command (i.e., a first timing advance command) from the RAN. For example, the UE in the inactive state may receive a MAC PDU including the first timing advance command from the RAN during an SDT session. The MAC PDU may include a MAC SDU, which includes a data packet or a portion of a data packet. In another example, the UE in the inactive state sends a random access preamble to the RAN and receives a random access response including the first timing advance command from the RAN in response. In yet another example, the UE in the inactive state sends a message A (MsgA) to the RAN and receives a message B (MsgB) including the first timing advance command in response to MsgA from the RAN.
[0129] In some implementations and / or scenarios, at block 602, while the UE is operating in an idle state, the UE receives a timing advance command (i.e., a first timing advance command) from the RAN. For example, the UE in the idle state may send a random access preamble to the RAN, and in response receive a random access response including the first timing advance command from the RAN. In yet another example, the UE in the idle state sends a message A (MsgA) to the RAN, and receives a message B (MsgB) including the first timing advance command in response to MsgA from the RAN.
[0130] In some implementations, the first message may include a CG-SDT configuration for configuring the CG-SDT for the UE. In other implementations, the UE may receive the CG-SDT configuration before receiving the first message. In these implementations, the first message may not include the CG-SDT configuration, and the UE may be configured to maintain use of the CG-SDT configuration previously received by the UE.
[0131] In some implementations, the PDU is a MAC PDU. In some implementations, the MAC PDU may include a timing advance command. In other implementations, the MAC PDU does not include a timing advance command.
[0132] In some implementations, the CG-SDT timer is a CG-SDT time alignment timer (CG-SDT-TAT or cg-SDT-TimeAlignmentTimer). In some implementations, at block 618, the UE starts a time alignment timer (e.g., timeAlignmentTimer) having a timer value equal to the remaining time of the CG-SDT timer.
[0133] In other implementations, at block 618, the UE starts a time alignment timer with a timer value. In some implementations, the UE receives a system information block (SIB) including a timer value (e.g., TimeAlignmentTimer or timeAlignmentTimerCommon) from the RAN. In other implementations, the second message includes the timer value.
[0134] In some implementations, when operating in a connected state, the UE restarts the time alignment timer upon receiving the second timing advance command from the RAN. For example, when the UE operates in a connected state, the UE may receive a MAC PDU including the second timing advance command from the RAN.
[0135] Figure 6B6 is a flow chart of an example method 600B similar to method 600A, except that method 600B includes block 609 instead of blocks 608 and 618. At block 609, the UE refrains from stopping the time alignment timer in response to the first message. That is, the UE may maintain or keep the uplink synchronization timer running in response to or after transitioning to the inactive state (or remaining in the inactive state).
[0136] Figure 6C is a flow chart of an example method 600C similar to method 600B, except that method 600C includes block 611 instead of block 610. At block 611, the UE restarts the time alignment timer in response to the first message instead of starting or restarting the CG-SDT timer. That is, when operating in different states (e.g., connected state and inactive state), the UE manages uplink synchronization with the RAN using the time alignment timer.
[0137] In method 600C, the UE does not use a CG-SDT timer (eg, CG-SDT-TAT). Instead, the UE maintains a time alignment timer when operating in a connected state and an inactive state, and uses the time alignment timer to manage the validity of the CG-SDT configuration.
[0138] Fig. 7A A method 700A is shown that may be implemented / performed by a UE (eg, UE 102) for managing uplink synchronization with a RAN (eg, RAN 105, base station 104, DU 174).
[0139] Method 700A begins at box 702, where the UE receives a timing advance command from the RAN. At box 704, the UE determines whether the CG-SDT timer is running. If the UE determines that the CG-SDT timer is running, the process proceeds to box 706. At box 706, the UE restarts the CG-SDT timer in response to the timing advance command. Otherwise, if the UE determines that the CG-SDT timer is not running, the process proceeds to box 708. At box 708, the UE starts or restarts the time alignment timer in response to the timing advance command. In some implementations, the UE starts a CG-SDT timer (e.g., a UE CG-SDT timer or a CG-SDT-TAT), as described above.
[0140] Figure 7B700A, except that in method 700B, at block 708, the UE starts or restarts an uplink synchronization timer (i.e., a time alignment timer) in response to a timing advance command, regardless of whether the CG-SDT timer is running at the base station. If the UE determines that the CG-SDT timer is not running, the flow proceeds to block 710 where the flow ends.
[0141] The examples and implementations of method 600A may be applied to methods 700A and 700B.
[0142] Fig. 8A A method 800A is shown that may be implemented / performed by a UE (eg, UE 102) for managing uplink synchronization with a RAN (eg, RAN 105, base station 104, DU 174).
[0143] Method 800A begins at block 802, where the UE receives a timing advance command from the RAN. At block 804, the UE starts a time alignment timer in response to the timing advance command. At block 806, the UE receives a first message from the RAN that transitions the UE to an inactive state. At block 808, the UE transitions to an inactive state or remains in an inactive state in response to the first message (e.g., events 332, 334, 432, 434, 394, 494, 495, 594, 595). At block 810, the UE determines whether the first message configures CG-SDT. If the UE determines that the first message configures CG-SDT, the process proceeds to block 812. At block 812, the UE avoids stopping the time alignment timer in response to receiving the first message or thereafter. At (optional) block 814, the UE may proceed to blocks 610, 612, 614, and / or 616. Otherwise, if the UE determines that the first message does not configure CG-SDT, the process proceeds to block 816. At block 816, the UE stops the time alignment timer in response to or after receiving the first message.
[0144] In some implementations, the UE resets a MAC entity that the UE uses to communicate with the RAN (e.g., to receive a timing advance command and / or a first message from the RAN). In some implementations, in response to resetting the MAC entity, the UE sets a new data indicator (NDI) of an uplink HARQ process of the MAC entity to a default value (e.g., zero), refreshes a soft buffer of an uplink HARQ process of the MAC entity, and / or determines (e.g., considers) a next transmission of a transmission frame as a new transmission of each downlink HARQ process of the MAC entity. The UE sends data to the RAN using an uplink HARQ process before receiving the first message from the RAN (e.g., events 404, 418, 492, 514, 518, 592, 593). The UE receives data and / or a first message from the RAN using a downlink HARQ process (e.g., events 418, 518, 592, 593). In a case where the first message is configured with a CG-SDT configuration, the UE avoids stopping a time alignment timer when, in response to, or after resetting the MAC entity. In some implementations, the UE initializes one or more parameters for logical channel prioritization in response to resetting the MAC entity. In some implementations, the UE flushes the Msg3 or MsgA buffer in response to resetting the MAC entity.
[0145] Figure 8B is a flow chart of an example method 800B similar to method 800A, except that method 800B includes blocks 813 and 817 instead of blocks 812 and 816. At block 813, the UE resets the MAC entity in response to the first message and avoids stopping the time alignment timer (i.e., continues to run the time alignment timer) when resetting the MAC entity. At block 817, the UE resets the MAC entity in response to the first message instead of stopping the time alignment timer in response to or after receiving the first message. When resetting the MAC entity or in response to the resetting, the UE stops the uplink synchronization timer.
[0146] The examples and implementations described above for method 600A may be applied to methods 800A and 800B.
[0147] Fig. 9 A method 900 is shown that may be implemented / performed by a UE (eg, UE 102) for managing uplink synchronization with a RAN (eg, RAN 105, base station 104, DU 174).
[0148] Method 900 begins at box 902, where the UE starts or restarts a time alignment timer, such as described above. At box 904, the UE starts or restarts a CG-SDT timer (e.g., CG-SDT-TAT or UE CG-SDT timer), such as described above. At box 906, the UE determines or detects that the time alignment timer has expired. At box 908, the UE determines whether the CG-SDT timer is running. If the UE determines that the CG-SDT timer is running, the process proceeds to box 910. At box 910, the UE performs a time alignment timer expiration process in response to the expiration of the time alignment timer. Otherwise, if the UE determines that the CG-SDT is not running (e.g., stopped or expired), the process proceeds to box 912. At box 912, the UE avoids performing a time alignment timer expiration process.
[0149] In some implementations, the time alignment timer expiration process includes at least one of the following actions:
[0150] Flushing one or more HARQ buffers of the MAC entity;
[0151] Release PUCCH resources and / or configuration;
[0152] Release of Sounding Reference Signal (SRS) resources and / or configuration;
[0153] Clear any configured downlink assignments and / or configured uplink grants;
[0154] • Maintain NTA as defined, for example, in 3GPP specification 38.211.
[0155] The following list of examples reflects various implementations expressly contemplated by the present disclosure:
[0156] Example 1. A method for managing time alignment performed by a user equipment (UE), the method comprising: receiving a timing advance command from a radio access network (RAN); when the UE is in an RRC connected state with the RAN, starting or restarting a first time alignment timer indicating the validity of a configured grant (CG) configuration; after starting or restarting the first time alignment timer, receiving a first message from the RAN; and in response to the first message, (i) transitioning from the RRC connected state to an RRC inactive state, (ii) stopping the first time alignment timer, and (iii) when the UE is in the RRC inactive state, starting or restarting a second time alignment timer indicating the validity of a CG small data transmission (CG-SDT) configuration.
[0157] Example 2. The method as described in Example 1 further includes: after stopping the first time alignment timer and starting or restarting the second time alignment timer: receiving a second message from the RAN, and in response to the second message, transitioning from the RRC inactive state to the RRC connected state, starting the first time alignment timer again, and communicating data with the RAN while operating in the RRC connected state.
[0158] Example 3. The method as described in Example 2 further includes: receiving a first timer value from the RAN, wherein restarting the first time alignment timer includes: setting the timer value of the first time alignment timer to the first timer value.
[0159] Example 4. A method as described in any one of Examples 1 to 3, wherein receiving the timing advance command occurs when the UE is in the RRC connected state.
[0160] Example 5. A method as described in any one of Examples 1 to 3, wherein receiving the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before receiving the second message, transitioning from the RRC inactive state to the RRC connected state.
[0161] Example 6. A method as described in any one of Examples 1 to 5, wherein the first message includes the CG-SDT configuration.
[0162] Example 7. A method as described in any of Examples 1 to 6, wherein the first message is a radio resource control (RRC) release message.
[0163] Example 8. A method as described in any one of Examples 1 to 7, wherein receiving the timing advance command includes: receiving a media access control (MAC) protocol data unit (PDU) including the timing advance command.
[0164] Example 9. A method as described in any one of Examples 1 to 7, wherein receiving the timing advance command includes: receiving a random access channel message including the timing advance command.
[0165] Example 10. The method as described in any one of Examples 1 to 9, further comprising: determining that the second time alignment timer is not running, wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.
[0166] Example 11. The method as described in any one of Examples 1 to 9, further comprising: after starting or restarting the second time alignment timer: receiving an additional timing advance command from the RAN; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.
[0167] Example 12. The method as described in any one of Examples 1 to 9, further comprising: after starting or restarting the second time alignment timer: receiving an additional timing advance command from the RAN; starting or restarting the first time alignment timer again; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.
[0168] Example 13. A method for managing time alignment performed by a user equipment (UE), the method comprising: receiving a timing advance command from a radio access network (RAN); starting or restarting a first time alignment timer indicating the validity of a configured grant (CG) configuration for use when the UE is in an RRC connected state with the RAN; after starting or restarting the first time alignment timer, receiving a first message from the RAN; and in response to the first message, (i) transitioning from the RRC connected state to an RRC inactive state, and (ii) while continuing to run the first time alignment timer, starting or restarting a second time alignment timer indicating the validity of a CG small data transmission (CG-SDT) configuration for use when the UE is in the RRC inactive state.
[0169] Example 14. The method as described in Example 13 further includes: after starting or restarting the second time alignment timer: receiving a second message from the RAN; and in response to the second message, transitioning from the RRC inactive state to the RRC connected state.
[0170] Example 15. The method of Example 13 or 14, wherein receiving the timing advance command occurs when the UE is in the RRC connected state.
[0171] Example 16. A method as described in Example 13 or 14, wherein receiving the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before receiving the first message, transitioning from the RRC inactive state to the RRC connected state.
[0172] Example 17. The method of Example 13 or 14, wherein the first message includes the CG-SDT configuration.
[0173] Example 18. The method of Example 17, wherein continuing to run the first time alignment timer is in response to the first message including the CG-SDT configuration.
[0174] Example 19. A method as described in Example 17 or 18, wherein continuing to run the first time alignment timer includes: avoiding stopping the first time alignment timer when a media access control (MAC) entity at the UE is reset.
[0175] Example 20. A method as described in any of Examples 13 to 19, wherein the first message is a radio resource control (RRC) release message.
[0176] Example 21. A method as described in any of Examples 13 to 20, wherein receiving the timing advance command includes: receiving a media access control (MAC) protocol data unit (PDU) including the timing advance command.
[0177] Example 22. The method of any one of Examples 13 to 20, wherein receiving the timing advance command comprises: receiving a random access channel message including the timing advance command.
[0178] Example 23 The method as described in any one of Examples 13 to 22 further includes: determining that the second time alignment timer is not running, wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.
[0179] Example 24. The method as described in any one of Examples 13 to 22, further comprising: after starting or restarting the second time alignment timer: receiving an additional timing advance command from the RAN; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.
[0180] Example 25. The method as described in any one of Examples 13 to 22 further includes: after starting or restarting the second time alignment timer: receiving an additional timing advance command from the UE; starting or restarting the first time alignment timer again; determining that the second time alignment timer is running; and in response to determining that the second time alignment timer is running, restarting the second time alignment timer.
[0181] Example 26. A method for managing time alignment performed by a user equipment (UE), the method comprising: receiving a timing advance command from a radio access network (RAN); starting or restarting a time alignment timer indicating the validity of a configured grant (CG) configuration; after starting or restarting the time alignment timer, receiving a first message from the RAN; and in response to the first message, (i) transitioning from an RRC connected state to an RRC inactive state, and (ii) restarting the time alignment timer.
[0182] Example 27. The method as described in Example 26 further includes: after restarting the time alignment timer: receiving a second message from the RAN, and in response to the second message, transitioning from the RRC inactive state to the RRC connected state, and communicating data with the RAN while operating in the RRC connected state.
[0183] Example 28. The method of Example 26 or 27, wherein receiving the timing advance command occurs when the UE is in the RRC connected state.
[0184] Example 29. A method as described in Example 26 or 27, wherein receiving the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further includes: before receiving the first message, transitioning from the RRC inactive state to the RRC connected state.
[0185] Example 30. A method as described in any of Examples 26 to 29, wherein the first message includes the CG-SDT configuration.
[0186] Example 31. A method as described in any of Examples 26 to 30, wherein the first message is a radio resource control (RRC) release message.
[0187] Example 32. A method as described in any of Examples 26 to 31, wherein receiving the timing advance command includes: receiving a media access control (MAC) protocol data unit (PDU) including the timing advance command.
[0188] Example 33. A method as described in any one of Examples 26 to 31, wherein receiving the timing advance command includes: receiving a random access channel message including the timing advance command.
[0189] Example 34. A user equipment (UE) comprising one or more processors and configured to implement a method as described in any one of Examples 1 to 33.
[0190] The following description may be applicable to the above description.
[0191] In some implementations, "message" is used and "information element (IE)" may be substituted for "message", and vice versa. In some implementations, "IE" is used and "field" may be substituted for "IE", and vice versa. In some implementations, "configuration" may be substituted for "configurations" or "configuration parameters", and vice versa. In some implementations, "small data transmission" may be substituted for "early data transmission (EDT)", and "SDT" may be substituted for "EDT", and vice versa. In some implementations, "small data transmission" may be substituted for "small data communication", and vice versa. In some implementations, "stop" may be substituted for "pause".
[0192] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell, or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0193] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code or machine-readable instruction stored on a non-transitory 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.
[0194] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.
Claims
1. A method for managing time alignment performed by a user equipment UE, the method comprising: receiving a timing advance command from a radio access network RAN; When the UE is in a radio resource control (RRC) connected state with the RAN, starting or restarting a first time alignment timer indicating validity of a configured authorized CG configuration; receiving a first message from the RAN; In response to the first message, (i) transition from the RRC connected state to an RRC inactive state, (ii) stop the first time alignment timer, and (iii) when the UE is in the RRC inactive state, start or restart a second time alignment timer indicating the validity of a CG small data transmission CG-SDT configuration; as well as After stopping the first time alignment timer and starting or restarting the second time alignment timer, (i) receiving a second message from the RAN, and (ii) in response to the second message, transitioning from the RRC inactive state to the RRC connected state, starting the first time alignment timer again, and communicating data with the RAN while operating in the RRC connected state.
2. The method of claim 1, further comprising: receiving a first timer value from the RAN, Wherein restarting the first time alignment timer comprises: setting the timer value of the first time alignment timer to the first timer value.
3. The method of claim 1 or 2, wherein receiving the timing advance command occurs when the UE is in the RRC connected state.
4. The method of claim 1 or 2, wherein receiving the timing advance command occurs when the UE is in the RRC inactive state, and wherein the method further comprises: Before receiving the second message, transitioning from the RRC inactive state to the RRC connected state.
5. The method according to any one of claims 1 to 4, wherein the first message includes the CG-SDT configuration.
6. The method according to any one of claims 1 to 5, wherein the first message is an RRC release message.
7. The method of any one of claims 1 to 6, wherein receiving the timing advance command comprises: A medium access control MAC protocol data unit (PDU) including the timing advance command is received.
8. The method of any one of claims 1 to 6, wherein receiving the timing advance command comprises: A random access channel message including the timing advance command is received.
9. The method according to any one of claims 1 to 8, further comprising: determining that the second time alignment timer is not running, Wherein starting or restarting the first time alignment timer is in response to determining that the second time alignment timer is not running.
10. The method of any one of claims 1 to 8, further comprising: After starting or restarting the second time alignment timer: receiving an additional timing advance command from the RAN; determining that the second time alignment timer is running; as well as In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.
11. The method of any one of claims 1 to 8, further comprising: After starting or restarting the second time alignment timer: receiving an additional timing advance command from the RAN; Starting or restarting the first time alignment timer again; determining that the second time alignment timer is running; and In response to determining that the second time alignment timer is running, the second time alignment timer is restarted.
12. A user equipment (UE), comprising one or more processors and configured to implement the method according to any one of claims 1 to 11.
