Method and apparatus for mobile terminated small data transfer in wireless communication system

Abstract

Methods, systems, and devices for mobile terminated small data transfer in a wireless communication system are provided. A user equipment may apply downlink semi-persistent scheduling in a mobile terminated small data transfer procedure. A user equipment may handle configured downlink assignments for downlink semi-persistent scheduling. A method for a user equipment in a wireless communication system may include receiving one or more configurations for downlink semi-persistent scheduling of an RRCINACTIVE state, initiating a mobile terminated small data transfer procedure in response to receiving a page indicating a mobile terminated small data transfer, in one embodiment, one or more downlink transmissions are received using a configured downlink assignment for downlink semi-persistent scheduling during a mobile terminated small data transfer procedure in an RRCINACTIVE state, and maintain one or more configurations of downlink semi-persistent scheduling and enter an RRCCONNECTED state in response to receiving a radio resource control resume message during the mobile terminated small data transfer procedure.

Description

[0001] This invention is a divisional application of the invention patent application with application number 202310106444.2 filed on February 13, 2023, and invention name: “Method and device for small data transmission with mobile termination in wireless communication system”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 323,916, filed on March 25, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0004] The present disclosure relates generally to wireless communication networks, and more particularly, to methods and apparatus for mobile-terminated small data transfer in wireless communication systems. Background Art

[0005] With the rapidly growing demand for transferring large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that use Internet Protocol (IP) data packets for communication. This IP packet communication can provide IP-based voice, multimedia, multicast, and on-demand communication services to users of mobile communication devices.

[0006] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Consequently, changes to the current body of 3GPP standards are being submitted and considered to evolve and complete the 3GPP standards. Summary of the Invention

[0007] Provided are methods, systems, and devices for mobile-terminated small data transmission in a wireless communication system, wherein a user equipment (UE) can apply downlink (DL) semi-persistent scheduling (SPS) during / in a mobile-terminated small data transmission (MT-SDT) procedure. For example, when uplink (UL) non-SDT data arrives, the UE can handle a configured DL assignment for DL ​​SPS.

[0008] In various embodiments, with respect to this and other concepts, systems and methods of the present invention, a method for a UE in a wireless communication system includes: receiving one or more configurations of a DL SPS for a radio resource control inactive (RRC_INACTIVE) state, initiating an MT SDT procedure in response to receiving a paging indicating MT-SDT, receiving one or more DL transmissions using the configured DL assignments for the DL SPS during the MT-SDT procedure in the RRC_INACTIVE state, and maintaining the one or more configurations of the DL SPS and entering a radio resource control connected (RRC_CONNECTED) state in response to receiving an RRC recovery message during the MT-SDT procedure.

[0009] In various embodiments, with respect to this and other concepts, systems and methods of the present invention, a method for a UE in a wireless communication system includes: receiving one or more configurations of a DL SPS for an RRC_INACTIVE state, initiating an MT-SDT procedure in response to receiving a paging indicating MT-SDT, receiving one or more DL transmissions using the configured DL assignments for the DL SPS during the MT-SDT procedure in the RRC_INACTIVE state, and releasing the one or more configurations of the DL SPS, clearing the configured DL assignments and entering the RRC_CONNECTED state in response to receiving an RRC recovery message during the MT-SDT procedure. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A diagram illustrating a wireless communication system according to an embodiment of the present invention;

[0011] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention;

[0012] Figure 3 is a functional block diagram of a communication system according to an embodiment of the present invention;

[0013] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code;

[0014] Figure 5 It is from 3GPP TS 36.300V16.7.0 Figure 7 .3c-1: Reproduction of MT-EDT for control plane CIoT EPS optimization;

[0015] Figure 6 It is from 3GPP TS 36.300V16.7.0 Figure 7 .3c-2: Reproduction of MT-EDT for user plane CIoT EPS optimization;

[0016] Figure 7 It is from 3GPP TS 38.331V16.7.0 Figure 5 .3.2.1-1: Reappearance of paging;

[0017] Figure 8 It is from R2-2203768 Figure 5 .3.13.1-1: RRC connection recovery, successful reappearance;

[0018] Figure 9 It is from R2-2203768 Figure 5 .3.13.1-2: RRC connection recovery fallback to RRC connection establishment, successful reproduction;

[0019] Figure 10 It is from R2-2203768 Figure 5 .3.13.1-3: RRC connection recovery after network release, successful reproduction;

[0020] Figure 11 It is from R2-2203768 Figure 5 .3.13.1-4: RRC connection recovery after network suspension, successful reproduction;

[0021] Figure 12 It is from R2-2203768 Figure 5 .3.13.1-5: RRC connection recovery, reappearance of network rejection;

[0022] Figure 13 is a diagram illustrating a general concept of MO SDT according to an embodiment of the present invention;

[0023] Figure 14 is a diagram illustrating an example of non-SDT data arrival during MO-SDT according to an embodiment of the present invention;

[0024] Figure 15 is a diagram illustrating a general concept of MT-SDT according to an embodiment of the present invention;

[0025] Figure 16 is a diagram showing an example of MT-SDT with DL SPS according to an embodiment of the present invention;

[0026] Figure 17 is a flow chart of a UE receiving a first paging indicating MT-SDT from an NW according to an embodiment of the present invention;

[0027] Figure 18 is a flowchart of a UE receiving one or more configurations of a DL SPS for an RRC_INACTIVE state according to an embodiment of the present invention;

[0028] Figure 19 is a flowchart of a UE receiving one or more configurations of DL SPS for RRC_INACTIVE state according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. Furthermore, the present invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that with the information disclosed, one skilled in the art can readily adapt and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0030] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0031] In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by a consortium named "3rd Generation Partnership Project" referred to herein as 3GPP, including: [1] RP-193252, "New Work Item on NR Small Data Transfer in Inactive State"; [2] RP-212726, "WI on MT-SDT"; [3] 3GPP TS 36.300 V16.7.0, "E-UTRA, General Description"; [4] 3GPP TS 38.321 V16.7.0, "NR, Medium Access Control (MAC) Protocol Specification"; [5] 3GPP TS 38.300 V16.8.0, "NR, NR and NG-RAN General Description"; [6] 3GPP TS 38.331 V16.7.0, “NR, Radio Resource Control (RRC) Protocol Specification”; and [7] R2-2203768, “Introduction to SDT”. The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.

[0032] Figure 1 1 shows a multiple access wireless communication system according to an embodiment of the present invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and another including 112 and 114. Figure 1 , each antenna group is shown with only two antennas, however, each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than that used by reverse link 118.

[0033] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0034] In communications via forward links 120 and 126, the transmit antennas of access network 100 utilize beamforming to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network that transmits to access terminals randomly dispersed throughout its coverage area using beamforming causes less interference to access terminals in neighboring cells than an access network that transmits to all of its access terminals via a single antenna.

[0035] An AN may be a fixed station or base station for communicating with a terminal and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other terminology. An AT may also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other terminology.

[0036] Figure 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0037] In one embodiment, each data stream is transmitted through a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0038] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme selected for that data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulation symbols. Instructions executed by processor 230 may determine the data rate, coding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0039] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N Ttransmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0040] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. T The antennas 224a to 224t transmit N signals from transmitters 222a to 222t. T a modulated signal.

[0041] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0042] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R received symbol streams to provide N T The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0043] Processor 270 periodically determines which precoding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0044] The reverse link message may include various types of information regarding the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a through 254r, and transmitted back to the transmitter system 210.

[0045] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0046] The memory 232 may be used to temporarily store some buffered / calculated data from 240 or 242 via the processor 230, store some buffered data from 212, or store some specific program codes. In addition, the memory 272 may be used to temporarily store some buffered / calculated data from 260 via the processor 270, store some buffered data from 236, or store some specific program codes.

[0047] Go to Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in the communication device 300, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by the user through the input device 302 (for example, a keyboard or keypad), and can output images and sounds through the output device 304 (for example, a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0048] Figure 4 According to one embodiment of the present invention Figure 3 . In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connectivity.

[0049] For LTE, LTE-A, or NR systems, Layer 2 portion 404 may include the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer. Layer 3 portion 402 may include the Radio Resource Control (RRC) layer.

[0050] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each invention may be logically, reasonably and appropriately combined to form a specific method.

[0051] Any sentence, paragraph, (sub) bullet, key point, action or claim described in each of the following invention paragraphs or sections can be independently and individually implemented to form a specific method or device. Relevance such as "based on", "more specifically", "example" and the like in the following disclosure of the present invention is only one possible embodiment that does not limit a specific method or device.

[0052] The 3GPP Release 17 work items for (mobile-initiated) Small Data Transfer (SDT) are specified in [1] RP-193252 “New work items on NR Small Data Transfer in Inactive state” as follows:

[0053] ***************************** Quote begins [1]********************************

[0054] 3 reasons

[0055] NR supports the RRC_INACTIVE state, and UEs with infrequent (periodic and / or aperiodic) data transmissions are typically maintained by the network in the RRC_INACTIVE state. Until Rel-16, the RRC_INACTIVE state did not support data transmission. Therefore, the UE must restore the connection for any DL (MT) and UL (MO) data (i.e., move to the RRC_CONNECTED state). Each data transmission establishes a connection and then releases it to the INACTIVE state, but the data packets are small and infrequent. This results in unnecessary power consumption and signaling overhead.

[0056] […]

[0057] As mentioned in 3GPP TS 22.891, the NR system will:

[0058] - Efficient and flexible for short data bursts with low throughput

[0059] - Support efficient signaling mechanisms (e.g. signaling is smaller than payload)

[0060] - Overall reduction in signaling overhead

[0061] The signaling overhead of small data packets from UEs in the INACTIVE state is a common problem and will become a critical issue for more UEs in NR, not only for network performance and efficiency, but also for UE battery performance. In general, any device with intermittent small data packets in the INACTIVE state will benefit from enabling small data transmission in the INACTIVE state.

[0062] The key enablers for small data transmission in NR, namely the INACTIVE state, 2-step and 4-step RACH and configured grant type 1, have been specified as part of Rel-15 and Rel-16. Therefore, this work builds on these building blocks to enable small data transmission in NR in the INACTIVE state.

[0063] 4 goals

[0064] 4.1 Objectives of SI or Core WI or Test WI

[0065] This work item enables small data transmission in the RRC_INACTIVE state as follows:

[0066] -For RRC_INACTIVE state:

[0067] UL small data transmission based on RACH scheme (i.e., 2-step and 4-step RACH):

[0068] ■ Generic procedure for enabling UP data transfer of small packets from the INACTIVE state (e.g. using MSGA or MSG3) [RAN2]

[0069] ■ Enable flexible payload sizes for MSGA and MSG3 that are larger than the current Rel-16 CCCH message size that may be used for INACTIVE state to support UP data transfer in UL (actual payload size is up to network configuration) [RAN2]

[0070] ■ Context acquisition and data forwarding in the INACTIVE state for RACH-based solutions (with or without anchor relocation) [RAN2, RAN3]

[0071] NOTE 1: Security aspects of the above solution should be checked using SA3

[0072] o Transmission of UL data on pre-configured PUSCH resources (i.e., reusing configured grant type 1) - when TA is valid

[0073] ■ Generic procedure for small data transfer from INACTIVE state via configured grant type 1 [RAN2]

[0074] ■ Configuration of configured grant type 1 resources for small data transfer in UL in INACTIVE state [RAN2]

[0075] ********************************END OF QUOTE********************************

[0076] The work items for 3GPP Release 18 have been discussed in RAN meetings, and the work items for Mobile Terminated (MT) SDT are specified as follows in [2] RP-212726 “WI on MT-SDT”:

[0077] ****************************** Quote begins [2]********************************

[0078] 3 reasons

[0079] Rel-17 specifies MO-SDT to allow small packet transmission for UL-oriented packets. For DL, MT-SDT (i.e., DL-triggered small data) allows similar benefits, namely 1) reducing signaling overhead and UE power consumption by not transitioning to RRC_CONNECTED, and reducing latency by allowing fast transmission of (small and infrequent) packets, such as those used for positioning.

[0080] 4 goals

[0081] 4.1 Objectives of SI or Core WI or Test WI

[0082] Specify support for paging-triggered SDT (MT-SDT) [RAN2, RAN3]

[0083] ●MT-SDT triggering mechanism for UEs in RRC_INACTIVE, supporting RA-SDT and CG-SDT as UL responses;

[0084] • MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmission in RRC_INACTIVE.

[0085] ********************************END OF QUOTE********************************

[0086] The Stage 2 description of MT-EDT in LTE is specified in TS 36.300 ([3] 3GPP TS 36.300 V16.7.0, “E-UTRA, general description”) as follows:

[0087] ****************************** Quote begins [3]********************************

[0088] 7.3c MT-EDT

[0089] 7.3c.1 General

[0090] MT-EDT is intended for a single downlink data transmission during a random access procedure.

[0091] If the UE and the network support MT-EDT and there is a single DL data transmission for the UE, MT-EDT is initiated by the MME.

[0092] The MT-EDT for control plane CIoT EPS optimization and user plane CIoT EPS optimization as defined in TS 23.401

[17] is characterized as follows:

[0093] - Support for MT-EDT for control plane CIoT EPS optimization and / or for user plane CIoT EPS optimization is reported by the UE at NAS level;

[0094] -DL data size is included in the S1-AP paging message for the UE;

[0095] - The MT-EDT indication is included in the paging message for the UE over the Uu interface.

[0096] - For user plane CIoT EPS optimization, the UE has been provided with the NextHopChainingCount in the RRCConnectionRelease message with a suspension indication;

[0097] - In response to a paging message containing an MT-EDT indication, the UE triggers the MO-EDT procedure for control plane CIoT EPS optimization or for user plane CIoT EPS optimization if upper layers request the establishment or resumption of an RRC connection for a mobile terminated call;

[0098] - There is no transition to RRC CONNECTED.

[0099] MT-EDT is only applicable to BL UEs, UEs in enhanced coverage, and NB-IoT UEs.

[0100] 7.3c.2 MT-EDT for Control Plane CIoT EPS Optimization

[0101] MT-EDT program for control plane CIoT EPS optimization in Figure 7 .3c-1 shown.

[0102] Figure 5 It is from 3GPP TS 36.300V16.7.0 Figure 7 .3c-1: Reproduction of MT-EDT for control plane CIoT EPS optimization.

[0103] 1. Upon arrival of downlink data, the SGW may send the DL data size information to the MME for MT-EDT consideration by the MME.

[0104] 2. The MME includes the DL data size information in the S1-AP paging message to help the eNodeB trigger MT-EDT.

[0105] 3. If the data can fit into one single downlink transmission according to the UE category included in the UE radio capabilities provided in the S1-AP paging message for paging, the eNB includes an mt-EDT indication in the paging message for the UE.

[0106] 4. The UE initiates the MO-EDT procedure for control plane CIoT EPS optimization as described in clause 7.3b.2, with the following differences:

[0107] - In step 1, the UE sends an RRC EarlyDataRequest message with the establishment cause mt-Access and without user data.

[0108] - In step 7, in case of fallback to the RRC connection establishment procedure, the downlink data may optionally be included in the RRCConnectionSetup message.

[0109] 7.3c.3 MT-EDT for User Plane CIoT EPS Optimization

[0110] MT-EDT procedure for user plane CIoT EPS optimization in Figure 7 .3c-2 is shown.

[0111] Figure 6 It is from 3GPP TS 36.300V16.7.0 Figure 7 .3c-2: Reproduction of MT-EDT for user plane CIoT EPS optimization.

[0112] 1. Upon arrival of downlink data, the SGW may send the DL data size to the MME for MT-EDT consideration by the MME.

[0113] 2. The MME includes the DL data size in the S1-AP paging message to help the eNodeB trigger MT-EDT.

[0114] 3. If the data can fit into one single downlink transmission according to the UE category included in the UE radio capabilities provided in the S1-AP paging message for paging, the eNB includes an mt-EDT indication in the paging message for the UE.

[0115] 4.UE as per clause 7.3b.3 / Figure 7 The MO-EDT procedure for initiating user plane CIoT EPS optimization is described in .3b-2, with the following differences:

[0116] - In step 0, the UE selects a random access preamble that is not configured for EDT;

[0117] - In step 1, the UE sends an RRCConnectionResumeRequest message with the resumption cause mt-EDT and without user data.

[0118] - In step 4, the MME may include a pending data indication in the S1AP UE Context Resume Response message to inform the eNB of further data traffic beyond the data traffic initially sent in step 2. The eNB may use this indication to decide whether to release the UE.

[0119] ******************************End of Quote******************************

[0120] The procedures involving DL transmission and semi-persistent scheduling (SPS) in NR are specified in TS 38.321 ([4] 3GPP TS 38.321 V16.7.0, “NR, Medium Access Control (MAC) Protocol Specification”) and TS 38.300 ([5] 3GPP TS 38.300 V16.8.0, “NR, NR and NG-RAN Overall Description”) as follows:

[0121] ****************************** Quote begins [4]*******************************

[0122] 5.3 DL-SCH Data Transmission

[0123] 5.3.1 DL assignment reception

[0124] A downlink assignment received on the PDCCH indicates the presence of a transmission on the DL-SCH for a specific MAC entity and provides relevant HARQ information.

[0125] When the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI, the MAC entity shall, for each PDCCH opportunity during which it monitors the PDCCH and for each serving cell:

[0126] 1> If the C-RNTI or Temporary C-RNTI for the MAC entity has received a downlink assignment on the PDCCH for this PDCCH opportunity and this serving cell:

[0127] 2> If this is the first downlink assignment for this Temporary C-RNTI:

[0128] 3> Treat NDI as switched.

[0129] 2> If the downlink assignment is for a C-RNTI of the MAC entity and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was a downlink assignment or a configured downlink allocation for a CS-RNTI of the MAC entity:

[0130] 3>Regardless of the value of NDI, treat NDI as toggled.

[0131] 2> Indicates the presence of a downlink assignment and delivers the associated HARQ information to the HARQ entity.

[0132] 1> else if a downlink assignment for this PDCCH opportunity has been received on the PDCCH for the CS-RNTI of the MAC entity for this serving cell:

[0133] 2> If the NDI in the received HARQ information is 1:

[0134] 3> Treat the NDI for the corresponding HARQ process as not yet switched;

[0135] 3> Indicates the presence of a downlink assignment for this serving cell and delivers the associated HARQ information to the HARQ entity.

[0136] 2> If the NDI in the received HARQ information is 0:

[0137] 3> If the PDCCH content indicates SPS deactivation:

[0138] 4> Clear the configured downlink allocation for this serving cell (if any);

[0139] 4> If the timeAlignmentTimer associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted is running:

[0140] 5> Indicates positive confirmation of SPS deactivation to the physical layer.

[0141] 3> Otherwise if the PDCCH content indicates SPS activation:

[0142] 4>Store the downlink assignment and associated HARQ information for this serving cell as the configured downlink assignment;

[0143] 4> Initialize or reinitialize the configured downlink assignment for this serving cell to start in the associated PDSCH duration and recur according to the rules in clause 5.8.1;

[0144] For each serving cell and each configured downlink assignment (if configured and activated), the MAC entity shall:

[0145] 1> If the PDSCH duration of the configured downlink assignment does not overlap with the PDSCH duration of the downlink assignment received on the PDCCH for this serving cell:

[0146] 2> instruct the physical layer to receive transport blocks on the DL-SCH and deliver them to the HARQ entity according to the configured downlink assignment in this PDSCH duration;

[0147] 2> Set the HARQ process ID to the HARQ process ID associated with this PDSCH duration;

[0148] 2> Treat the NDI bit for the corresponding HARQ process as having been toggled;

[0149] 2> Indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity.

[0150] […]

[0151] 5.3.2 HARQ Operation

[0152] 5.3.2.1 HARQ Entity

[0153] The MAC entity includes a HARQ entity for each serving cell, which maintains multiple parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ process (see clause 5.3.2.2).

[0154] The number of parallel DL HARQ processes per HARQ entity is specified in TS 38.214 [7]. A dedicated broadcast HARQ process is used for BCCH.

[0155] When the physical layer is not configured for downlink spatial multiplexing, the HARQ process supports one TB.When the physical layer is configured for downlink spatial multiplexing, the HARQ process supports one or two TBs.

[0156] When the MAC entity is configured with pdsch-AggregationFactor > 1, the parameter pdsch-AggregationFactor provides the number of TB transmissions within a downlink assigned bundle. Bundling operation relies on the HARQ entity to invoke the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, pdsch-AggregationFactor - 1 HARQ retransmissions follow within the bundle.

[0157] The MAC entity will:

[0158] 1> If downlink assignment has been indicated:

[0159] 2> Allocate the TBs and associated HARQ information received from the physical layer to the HARQ process indicated by the associated HARQ information.

[0160] 1> If a downlink assignment has been indicated for a broadcast HARQ process:

[0161] 2> Allocate the received TB to the broadcast HARQ process.

[0162] 5.3.2.2 HARQ Process

[0163] When transmitting for a HARQ process, one or two (in case of downlink spatial multiplexing) TBs and associated HARQ information are received from the HARQ entity.

[0164] For each received TB and associated HARQ information, the HARQ process shall:

[0165] 1> if the NDI, when provided, has toggled compared to the value of the previous received transmission corresponding to this TB; or

[0166] 1> if the HARQ process is equal to the broadcast process and this is the first received transmission for the TB according to the system information schedule indicated by RRC; or

[0167] 1> If this is the first received transmission for this TB (i.e., there is no previous NDI for this TB):

[0168] 2> Treat this transmission as a new transmission.

[0169] 1> Otherwise:

[0170] 2> Treat this transmission as a retransmission.

[0171] The MAC entity shall then:

[0172] 1> If this is a new transmission:

[0173] 2>Try to decode the received data.

[0174] 1> Otherwise, if this is a retransmission:

[0175] 2> If this TB of data has not been successfully decoded, then:

[0176] 3> Instructs the physical layer to combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data.

[0177] 1> if the data that the MAC entity attempted to decode was successfully decoded for this TB; or

[0178] 1> If data for this TB was previously successfully decoded:

[0179] 2> If the HARQ process is equal to the broadcast process:

[0180] 3> Deliver the decoded MAC PDU to upper layers.

[0181] 2> Otherwise, if this is the first successful decode for this TB of data:

[0182] 3> Pass the decoded MAC PDU to the decomposition and demultiplexing entity.

[0183] 1> Otherwise:

[0184] 2> Instructs the physical layer to replace the data in the soft buffer for this TB with the data that the MAC entity attempts to decode.

[0185] 1> if the HARQ process is associated with a transmission indicated by the Temporary C-RNTI and contention resolution has not succeeded (see clause 5.1.5); or

[0186] 1> if the HARQ process is associated with the transmission indicated by the MSGB-RNTI and the random access procedure has not been successfully completed (see clause 5.1.4a); or

[0187] 1> if the HARQ process is equal to the broadcast process; or

[0188] 1> If the timeAlignmentTimer associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted stops or expires:

[0189] 2>Instructs the physical layer to generate confirmation of the data in this TB.

[0190] 1> Otherwise:

[0191] 2> Instructs the physical layer to generate an acknowledgement of the data in this TB.

[0192] ********************************Next Quote*****************************

[0193] 5.8 Transmission and Reception without Dynamic Scheduling

[0194] 5.8.1 Downlink

[0195] For each BWP, Semi-Persistent Scheduling (SPS) is configured by RRC for each serving cell. Multiple assignments can be active simultaneously in the same BWP. Activation and deactivation of DL SPS are independent among serving cells.

[0196] For DL ​​SPS, DL assignments are provided by PDCCH and are stored or cleared based on L1 signaling indicating SPS activation or deactivation.

[0197] When SPS is configured, RRC configures the following parameters:

[0198] -cs-RNTI: CS-RNTI used for activation, deactivation and retransmission;

[0199] -nrofHARQ-Processes: number of configured HARQ processes for SPS;

[0200] -harq-ProcID-Offset: offset of the HARQ process used for SPS;

[0201] - periodicity: The periodicity of the configured downlink assignments for SPS.

[0202] When the SPS is released by the upper layer, all corresponding configurations will be released.

[0203] After configuring downlink assignments for SPS, the MAC entity shall sequentially consider the Nth downlink assignment occurring in a time slot, where:

[0204] (numberOfSlotsPerFrame×SFN+number of slots in a frame)=[(numberOfSlotsPerFrame×SFN 开始时间 +slot 开始时间 )+N×periodicity×numberOfSlotsPerFrame / 10]modulo(1024×numberOfSlotsPerFrame)

[0205] SFN 开始时间 and slot 开始时间 SFN and timeslot, respectively, of the first transmission of PDSCH, where the configured downlink assignment is (re)initialized.

[0206] NOTE: In case of misaligned SFNs across carriers in a cell group, the SFNs of the serving cells involved are used to calculate the occurrence rate of configured downlink assignments.

[0207] *******************************End of Quote*****************************

[0208] ****************************** Quote begins [5]*******************************

[0209] 10.2 Downlink Scheduling

[0210] In the downlink, the gNB can dynamically allocate resources to the UE via the C-RNTI on the PDCCH. The UE always monitors the PDCCH for possible assignments when its downlink reception is enabled (an activity governed by DRX when configured). When Carrying out Carrying Out Carriers (CARs) is configured, the same C-RNTI applies to all serving cells.

[0211] The gNB can preempt an ongoing PDSCH transmission to one UE with a latency-critical transmission to another UE. The gNB can configure the UE to monitor for interrupted transmission indications using the INT-RNTI on the PDCCH. If a UE receives an interrupted transmission indication, it can assume that the resource elements included in the indication do not carry valid information for the UE, even if some of those resource elements have been scheduled for the UE.

[0212] Furthermore, using semi-persistent scheduling (SPS), the gNB can allocate downlink resources for initial HARQ transmissions to the UE: RRC defines the periodicity of the configured downlink assignments, while the PDCCH addressed to the CS-RNTI can transmit and activate or deactivate the configured downlink assignments; i.e., the PDCCH addressed to the CS-RNTI indicates that the downlink assignments can be implicitly reused according to the periodicity defined by RRC until deactivated.

[0213] NOTE: Retransmissions are explicitly scheduled on the PDCCH when needed.

[0214] Dynamically allocated downlink reception overrides configured downlink assignments in the same serving cell, provided they overlap in time. Otherwise, if activated, downlink reception according to the configured downlink assignments is assumed.

[0215] A UE may be configured with up to 8 active configured downlink assignments for a given BWP of a serving cell. When more than one is configured:

[0216] - The network decides which of these configured downlink assignments are active at a time (including all of them); and

[0217] - Each configured downlink assignment is activated individually using a DCI command, and deactivation of a configured downlink assignment is done using a DCI command, which may deactivate a single configured downlink assignment or deactivate multiple configured downlink assignments jointly.

[0218] ********************************END OF QUOTE********************************

[0219] The paging procedure in NR is specified in TS 38.331 ([6] 3GPP TS 38.331 V16.7.0, “NR, Radio Resource Control (RRC) Protocol Specification”) as follows:

[0220] ******************************* Quote begins [6]*******************************

[0221] 5.3.2 Paging

[0222] 5.3.2.1 General

[0223] Figure 7 It is from 3GPP TS 38.331V16.7.0 Figure 5 .3.2.1-1: Reappearance of paging.

[0224] The purpose of this program is to:

[0225] - Deliver paging information to UEs in RRC_IDLE or RRC_INACTIVE.

[0226] 5.3.2.2 Initiation

[0227] The network initiates the paging procedure by transmitting a paging message at the UE's paging occasions specified in TS 38.304

[20] . The network can address multiple UEs within a paging message by including one PagingRecord for each UE.

[0228] 5.3.2.3 UE Reception of Paging Message

[0229] After receiving the paging message, the UE shall:

[0230] 1> If in RRC_IDLE, then for each PagingRecord contained in a paging message (if any):

[0231] 2> If the ue-Identity contained in the PagingRecord matches the UE identity assigned by the upper layer:

[0232] 3>Forward ue-Identity and accessType (if present) to the upper layer;

[0233] 1> If in RRC_INACTIVE, then for each PagingRecord contained in the Paging Message (if any):

[0234] 2> If the ue-Identity contained in the PagingRecord matches the UE's stored fullI-RNTI:

[0235] 3> If the UE is configured by upper layers to have access identity 1:

[0236] 4> Initiate the RRC connection recovery procedure according to 5.3.13, where resumeCause is set to mps-PriorityAccess;

[0237] 3> Otherwise if the UE is configured by upper layers to have access identity 2:

[0238] 4> Initiate the RRC connection recovery procedure according to 5.3.13, where resumeCause is set to mcs-PriorityAccess;

[0239] 3> Otherwise if the UE is configured by upper layers with one or more access identities equal to 11-15:

[0240] 4> Initiate the RRC connection recovery procedure according to 5.3.13, where resumeCause is set to highPriorityAccess;

[0241] 3> Otherwise:

[0242] 4> Initiate the RRC connection recovery procedure according to 5.3.13, where resumeCause is set to mt-Access;

[0243] 2> Otherwise if the ue-Identity contained in the PagingRecord matches the UE identity assigned by upper layers:

[0244] 3>Forward ue-Identity to the upper layer and forward accessType (if present) to the upper layer;

[0245] 3> Perform actions after going to RRC_IDLE as specified in 5.3.11 due to release reason 'other'.

[0246] *******************************End of Quote******************************

[0247] The RRC recovery procedure in NR is specified in [6] 3GPP TS 38.331 V16.7.0 “NR, Radio Resource Control (RRC) Protocol Specification” and the relevant procedures in a running CR for (MO-)SDT are specified in [7] R2-2203768 “Introduction to SDT” as follows:

[0248] ***************************** Quote begins [7]********************************

[0249] 5.3.13 RRC Connection Recovery

[0250] 5.3.13.1 General

[0251] Figure 8 It is from R2-2203768 Figure 5 .3.13.1-1: RRC connection recovery, successful reproduction.

[0252] Figure 9 It is from R2-2203768 Figure 5.3.13.1-2: RRC connection recovery falls back to RRC connection establishment and is successfully reproduced.

[0253] Figure 10 It is from R2-2203768 Figure 5 .3.13.1-3: RRC connection recovery after network release, successful reproduction.

[0254] Figure 11 It is from R2-2203768 Figure 5 .3.13.1-4: RRC connection recovery after network suspension, successful reproduction.

[0255] Figure 12 It is from R2-2203768 Figure 5 .3.13.1-5: RRC connection recovery, recurrence of network rejection.

[0256] The purpose of this procedure is to resume a suspended RRC connection, including resuming SRBs and DRBs or performing RNA updates. This procedure is also used to initiate SDT in RRC_INACTIVE.

[0257] […]

[0258] 5.3.13.1b Conditions for initiating SDT

[0259] A UE in RRC_INACTIVE initiates the recovery procedure for SDT when all the following conditions are met:

[0260] 1> Upper layers request the resumption of the RRC connection; and

[0261] 1>SIB1 contains sdt-ConfigCommon; and

[0262] 1>sdt-Config is configured; and

[0263] 1> All pending data in UL is mapped to radio bearers configured for SDT; and

[0264] 1> Lower layer indications satisfy the conditions for initiating SDT as specified in TS 38.321 [3].

[0265] 5.3.13.2 Initiation

[0266] The procedure is initiated by the UE when upper layers or the AS (after triggering an RNA update while the UE is RRC_INACTIVE as specified in subclause 5.3.13.1a for NR sidelink communication / V2X sidelink communication) request resumption of a suspended RRC connection or when SDT is initiated as specified in subclause 5.3.13.1b.

[0267] Before initiating this procedure, the UE shall ensure that it has valid and up-to-date basic system information as specified in clause 5.2.2.2.

[0268] After initiating the procedure, the UE shall:

[0269] 1> If the resumption of the RRC connection is triggered by responding to an NG-RAN paging:

[0270] 2>Select '0' as the access category;

[0271] 2> Use the access category and one or more access identities provided by the upper layer to perform the unified access control procedures as specified in 5.3.14;

[0272] 3> If the access attempt is blocked, the procedure ends;

[0273] 1> Otherwise, if the recovery of the RRC connection is triggered by upper layers:

[0274] 2> If the upper layer provides an access category and one or more access identities:

[0275] 3> Use the access category and access identity provided by the upper layer to perform the unified access control procedures specified in 5.3.14;

[0276] 4> If the access attempt is blocked, the procedure ends;

[0277] 2> If the resumption occurs after the release redirected by mpsPriorityIndication:

[0278] 3> Set resumeCause to mps-PriorityAccess;

[0279] 2> Otherwise:

[0280] 3> Set resumeCause based on the information received from the upper layer;

[0281] […]

[0282] 1> As specified in the corresponding physical layer specification, the preset L1 parameter values ​​apply, except for parameters whose values ​​are provided in SIB1;

[0283] 1> As specified in 9.2.1, the default SRB1 configuration shall apply;

[0284] 1> Apply the preset MAC cell group configuration as specified in 9.2.2;

[0285] 1> If stored, release delayBudgetReportingConfig from the UE inactive AS context;

[0286] 1> Stop timer T342 (if it is running);

[0287] 1> If stored, release the overheatingAssistanceConfig from the UE inactive AS context;

[0288] 1> Stop timer T345 (if it is running);

[0289] 1> If stored, release the idc-AssistanceConfig from the UE inactive AS context;

[0290] 1> If stored, release the drx-PreferenceConfig for all configured cell groups from the UE inactive AS context;

[0291] 1> Stop all instances of timer T346a (if running);

[0292] 1> If stored, release the maxBW-PreferenceConfig for all configured cell groups from the UE inactive AS context;

[0293] 1> Stop all instances of timer T346b (if running);

[0294] 1> If stored, release the maxCC-PreferenceConfig of all configured cell groups from the UE inactive AS context;

[0295] 1> Stop all instances of timer T346c (if running);

[0296] 1> if stored, release the maxMIMO-LayerPreferenceConfig for all configured cell groups from the UE inactive AS context;

[0297] 1> Stop all instances of timer T346d (if running);

[0298] 1> If stored, release the minSchedulingOffsetPreferenceConfig for all configured cell groups from the UE inactive AS context;

[0299] 1> Stop all instances of timer T346e (if running);

[0300] 1> If stored, release releasePreferenceConfig from the UE inactive AS context;

[0301] 1> If stored, release wlanNameList from the UE inactive AS context;

[0302] 1> If stored, release btNameList from the UE inactive AS context;

[0303] 1> If stored, release sensorNameList from the UE inactive AS context;

[0304] 1> If stored, release obtainCommonLocation from the UE inactive AS context;

[0305] 1> Stop timer T346f (if it is running);

[0306] 1> If stored, release referenceTimePreferenceReporting from the UE inactive AS context;

[0307] 1> If stored, release sl-AssistanceConfigNR from the UE inactive AS context;

[0308] 1> Apply CCCH configuration as specified in 9.1.1.2;

[0309] 1>Apply timeAlignmentTimerCommon contained in SIB1;

[0310] 1>If sdt-MAC-PHY-CG-Config is configured:

[0311] 2> If the recovery procedure is initiated in a cell different from the PCell in which the UE received the stored sdt-MAC-PHY-CG-Config, then:

[0312] 3> Release the stored sdt-MAC-PHY-CG-Config;

[0313] 1> If the conditions for initiating SDT according to 5.3.13.1b are met, then:

[0314] 2> Consider initiating recovery proceedings against SDT;

[0315] 2>Start timer T319a;

[0316] 1> Otherwise:

[0317] 2>Start timer T319;

[0318] 2> Instruct the MAC entity to consider the cg-SDT-timeAlignmentTimer as expired (if it is running);

[0319] 1>Set the variable pendingRNA-Update to false;

[0320] 1> Initiate the transmission of RRCResumeRequest message or RRCResumeRequest1 according to 5.3.13.3.

[0321] 5.3.13.3 Actions related to the transmission of RRCResumeRequest or RRCResumeRequest1 messages

[0322] The UE shall set the content of the RRCResumeRequest or RRCResumeRequest1 message as follows:

[0323] 1> If the field useFullResumeID is sent in SIB1:

[0324] 2>Select RRCResumeRequest1 as the message to be used;

[0325] 2> Set resumeIdentity to the stored fullI-RNTI value;

[0326] 1> Otherwise:

[0327] 2>Select RRCResumeRequest as the message to use;

[0328] 2> Set resumeIdentity to the stored shortI-RNTI value;

[0329] 1> Restore the RRC configuration, RoHC state, stored QoS flow to DRB mapping rules, and K from the stored UE inactive AS context gNB and K RRCint Keys, except for the following:

[0330] -masterCellGroup;

[0331] - mrdc-SecondaryCellGroup, if stored; and

[0332] -pdcp-Config;

[0333] 1> Set resumeMAC-I to the 16 least significant bits of the calculated MAC-I:

[0334] 2> pass VarResumeMAC-Input encoded in ASN.1 according to clause 8 (i.e., a multiple of 8 bits);

[0335] 2>Use K in UE inactive AS context RRCint The key and previously configured integrity protection algorithm; and

[0336] 2> All input bits for count, load and direction are set to binary ones;

[0337] 1>Use the stored nextHopChainingCount value based on the current K gNB Key or NH export K gNB Key, as specified in TS 33.501

[11] ;

[0338] 1> Export K RRCenc Key, K RRCint Key, K UPint Key and K UPenc Key;

[0339] 1> Then use the configured algorithm and K derived in this subclause RRCint Key and K UPint The key configures the lower layers to apply integrity protection to all radio bearers except SRB0, i.e. integrity protection will be applied to all subsequent messages received and sent by the UE;

[0340] NOTE 1: Only DRBs that were previously configured with UP integrity protection will have their integrity protection restored.

[0341] 1> Configure lower layers to apply encryption to all radio bearers except SRB0 and apply the configured encryption algorithm derived in this subclause, K RRCenc Key and K UPenc The key, i.e., the encryption configuration will be applied to all subsequent messages received and sent by the UE;

[0342] 1> Re-establish the PDCP entity for SRB1;

[0343] 1>Restore SRB1;

[0344] 1> If a recovery procedure is initiated for SDT:

[0345] 2> For each radio bearer configured for SDT:

[0346] 3> Restore the configuration associated with the RLC bearer of masterCellGroup and pdcp-Config from the UE inactive AS context;

[0347] 3> Re-establish the PDCP entity for the radio bearer without triggering a PDCP status report;

[0348] 2>Restore all radio bearers configured for SDT;

[0349] 1>Submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to the lower layer.

[0350] Note 2: Only DRBs that were previously configured with UP encryption will resume encryption.

[0351] If the lower layers indicate an integrity check failure while T319 or T319a is in operation, then perform the actions specified in 5.3.13.5.

[0352] The UE shall continue cell reselection related measurements and cell reselection evaluation. If the conditions for cell reselection are met, the UE shall perform cell reselection as specified in 5.3.13.6.

[0353] 5.3.13.4UE Reception of RRCResume

[0354] The UE shall:

[0355] 1> Stop timer T319 (if it is running);

[0356] 1> Stop timer T319a (if it is running);

[0357] […]

[0358] 1> If RRCResume contains fullConfig:

[0359] 2> Perform the full configuration procedure as specified in 5.3.5.11;

[0360] 1> Otherwise:

[0361] 2>If RRCResume does not contain restoreMCG-SCells:

[0362] 3> If stored, release the MCG SCell from the UE inactive AS context;

[0363] 2> If RRCResume does not contain restoreSCG:

[0364] 3> if stored, release the MR-DC related configuration from the UE inactive AS context (i.e., as specified in 5.3.5.10);

[0365] 2> Restore masterCellGroup, mrdc-SecondaryCellGroup (if stored) and pdcp-Config from the UE inactive AS context;

[0366] 2> Configure lower layers to treat the recovered MCG and SCG SCell (if present) as being in a deactivated state;

[0367] 1> Abandon the UE inactive AS context;

[0368] 1> Release suspendConfig, except ran-NotificationAreaInfo;

[0369] 1>If RRCResume contains masterCellGroup:

[0370] 2>According to 5.3.5.5, perform cell group configuration for the received masterCellGroup;

[0371] 1> If RRCResume contains mrdc-SecondaryCellGroup:

[0372] 2> If the received mrdc-SecondaryCellGroup is set to nr-SCG:

[0373] 3> Perform RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message contained in nr-SCG;

[0374] 2> If the received mrdc-SecondaryCellGroup is set to eutra-SCG:

[0375] 3> Perform RRC connection reconfiguration for the RRCConnectionReconfiguration message contained in the eutra-SCG as specified in TS 36.331

[10] clause 5.3.5.3;

[0376] 1> If RRCResume contains radioBearerConfig:

[0377] 2> Perform radio bearer configuration according to 5.3.5.6;

[0378] 1> If the RRCResume message contains sk-Counter:

[0379] 2> Perform the security key update procedure as specified in 5.3.5.7;

[0380] 1> If the RRCResume message contains radioBearerConfig2:

[0381] 2> Perform radio bearer configuration according to 5.3.5.6;

[0382] 1> If the RRCResume message contains needForGapsConfigNR:

[0383] 2>If needForGapsConfigNR is set to setup:

[0384] 3> Consider itself configured to provide measurement gap requirement information for the NR target band;

[0385] 2> Otherwise:

[0386] 3> consider itself as not configured to provide measurement gap requirement information for the NR target band;

[0387] 1> Resume SRB2 (if suspended), SRB3 (if configured) and all DRBs (suspended);

[0388] 1> If stored, discard the cell reselection priority information provided by cellReselectionPriorities or inherited from another RAT;

[0389] 1> If it is running, stop timer T320;

[0390] 1> If the RRCResume message contains measConfig:

[0391] 2> Perform the measurement configuration procedure as specified in 5.5.2;

[0392] 1>Resume measurement (if paused);

[0393] 1> If the T390 is running, then:

[0394] 2> For all access categories, stop timer T390;

[0395] 2> Perform the actions specified in 5.3.14.4;

[0396] 1> If T302 is running:

[0397] 2> Stop timer T302;

[0398] 2> Perform the actions specified in 5.3.14.4;

[0399] 1>Enter RRC_CONNECTED;

[0400] 1> Indicate to the upper layer that the suspended RRC connection has been resumed;

[0401] 1>Stop the cell reselection procedure;

[0402] 1> Treat the current cell as PCell;

[0403] 1> Set the content of the RRCResumeComplete message as follows:

[0404] […]

[0405] 1> Submit the RRCResumeComplete message to the lower layer for transmission;

[0406] 1>The program ends.

[0407] 5.3.13.5 Handling of Failure to Restore the RRC Connection

[0408] The UE shall:

[0409] 1> If timer T319 expires:

[0410] 2> if the UE has connection establishment failure or connection recovery failure information available in VarConnEstFailReport and if RPLMN is equal to the plmn-identity stored in VarConnEstFailReport; or

[0411] 2> If the cell identity of the current cell is not equal to the cell identity in measResultFailedCell stored in VarConnEstFailReport:

[0412] 3>Reset numberOfConnFail to 0;

[0413] 2> Clear the contents contained in VarConnEstFailReport, except numberOfConnFail (if it exists);

[0414] 2>Store the following connection recovery failure information in VarConnEstFailReport by setting its fields as follows:

[0415] 3> Set plmn-Identity to the PLMN selected by the upper layer from the PLMNs in the plmn-IdentityInfoList contained in SIB1 (see TS 24.501

[23] );

[0416] 3> Based on the available SSB measurements collected until the UE detects the connection recovery failure, measResultFailedCell is set to include the global cell identity of the failed cell, tracking area code, cell-level and SS / PBCH block-level RSRP and RSRQ, and SS / PBCH block index;

[0417] 3> If available, set measResultNeighCells to include neighbor cell measurements for up to the following number of neighbor cells in descending order of the criteria used for cell reselection: 6 intra-frequency and 3 inter-frequency neighbors per frequency, and 3 inter-RAT neighbors per frequency / per group of frequencies per RAT, and according to the following:

[0418] 4> For each included neighboring cell, include the available optional fields;

[0419] NOTE: The UE contains the latest results of available measurements used for cell reselection evaluation, which are performed according to the performance requirements as specified in TS 38.133

[14] .

[0420] 3>If available, set locationInfo as described in 5.3.3.7;

[0421] 3> perRAInfoList is set to indicate the information related to the random access procedure performed as specified in 5.7.10.5;

[0422] 3> If numberOfConnFail is less than 8:

[0423] 4>Increment numberOfConnFail by 1;

[0424] 2> Perform actions after transitioning to RRC_IDLE, as specified in 5.3.11, where the release cause is 'RRC recovery failure'.

[0425] 1> Otherwise, if an integrity check failure indication is received from a lower layer while T319 or T319a is in operation:

[0426] 2> Perform actions after transitioning to RRC_IDLE, as specified in 5.3.11, where the release cause is 'RRC recovery failure'.

[0427] 1> else if an indication that the maximum number of retransmissions has been reached is received from the MCG RLC while T319a is in progress; or

[0428] 1> If a Random Access Problem Indication is received from the MCG MAC while T319a is in operation; or

[0429] 1> if the lower layers indicate that the cg-SDT-TimeAlignmentTimer expires before receiving the network response for the UL CG-SDT transmission with CCCH message while T319a is running; or

[0430] 1> If T319a expires:

[0431] 2> Perform actions after transitioning to RRC_IDLE, as specified in 5.3.11, where the release cause is 'RRC recovery failure'.

[0432] *********************************END OF QUOTE***************************

[0433] In New Radio (NR), Small Data Transfer (SDT) is introduced to transmit and / or receive user data (e.g., small data) in RRC_INACTIVE state without establishing (or resuming) a Radio Resource Control (RRC) connection, and is subsequently introduced in Release [1] RP-193252 "New Work Items on NR Small Data Transfer in Inactive State", which can save power consumption and signaling overhead. In the current 3GPP meeting, Mobile Originated (MO) SDT has been discussed in NR Release 17. For (MO)-SDT, in response to uplink (UL) data (e.g., small data) available for transmission while a User Equipment (UE) is in RRC_INACTIVE state, the UE may initiate an RRC Connection Recovery procedure, which triggers a Random Access (RA) procedure (e.g., RA-SDT) and / or a transmission on a pre-configured Physical Uplink Shared Channel (PUSCH) resource (e.g., configured grant-based SDT (CG-SDT)). The UE will be configured with CG-SDT resources (e.g., CG type 1 resources) in an RRC release message (e.g., RRCRelease) from the network (NW) in the RRC_CONNECTED state. The UE may use the CG-SDT resources (in CG-SDT) to send an RRC request message (e.g., RRCResumeRequest) and small data in Msg3 (in RA-SDT), message A (MSGA) (in RA-SDT) and / or a protocol data unit (PDU) to be transmitted. If there is more data that cannot be transmitted within the first (or initial) small data transmission (e.g., in Msg3, MSGA and / or the first PDU using CG-SDT resources), then subsequent small data transmissions and RRC state transition decisions will be under the control of the NW. Subsequent small data may be transmitted using (pre-) configured (CG-SDT) PUSCH resources and / or dynamic grants provided by the NW. There may be one or more subsequent small data transmissions after the first (or initial) small data transmission. If there is no more subsequent small data in the UE (e.g., indicated by a buffer status report (BSR)) and / or if the NW decides to complete the (MO-)SDT procedure, the NW may send an RRC release message (e.g., RRCRelease) (e.g., with suspendConfig) to the UE. If the NW decides to transition the UE to the RRC_CONNECTED state (and transmit uplink / downlink (UL / DL) data in the RRC_CONNECTED state), the NW may send an RRC resume message (e.g., RRCResume) to the UE.

[0434] For example, if Figure 13As shown in , the NW may configure and / or provide a type 1 configured (UL) grant in a first RRC release message (e.g., RRCRelease). In response to receiving the first RRC release message (e.g., RRCRelease), the UE may transition to the RRC_INACTIVE state. The UE may initiate an SDT procedure in the RRC_INACTIVE state and use the configured UL grant to transmit multiple small data (e.g., a first / initial small data transmission and subsequent small data transmissions). When a second RRC release message (e.g., RRCRelease) is received at the end of the SDT procedure, the UE may reset the media access control (MAC) and clear the configured UL grant.

[0435] For example, if Figure 14 As shown in , the NW may restore the UE to RRC_CONNECTED to transmit non-SDT. When non-SDT data arrives during the SDT procedure, the UE may inform the NW through UE Assistance Information (UAI). The NW may transmit an RRC resume message (e.g., RRCResume) to the UE. In response to receiving the RRC resume message (e.g., RRCResume), the UE may enter the RRC_CONNECTED state and clear the configured UL grant by considering the timing advance (TA) timer for CG-SDT (e.g., cg-SDT-TimeAlignmentTimer) as expired. In response to receiving the RRC resume message (e.g., RRCResume), the UE may terminate the SDT procedure.

[0436] On the other hand, the UE may perform MO-EDT and / or MT-EDT (mobile terminated EDT) in the RRC_IDLE state in LTE. The UE may initiate a MO-EDT procedure for one UL data transmission. The NW may instruct the UE to initiate an MT-EDT procedure for a single DL data transmission ([3] 3GPP TS 36.300 V16.7.0, “E-UTRA, General Description”). When the NW has DL data to transmit, the NW may send a paging containing an MT-EDT indication (e.g., mt-EDT set to true) to the UE. In response to the paging, the UE may select a RA preamble that is not configured for EDT and trigger a RA procedure. The RA procedure is a normal RA procedure (e.g., a RA procedure with no UL data in Msg3, a RA procedure using RA resources not used for EDT). The UE may send an RRC resume request message (e.g., RRCConnectionResumeRequest) in Msg3 in the RA procedure, where the resume cause is mt-EDT. The NW may then send an RRC release message (eg, RRCRelease) and DL data in Msg4 to complete the RA and MT-EDT procedures.

[0437] Further enhancements and / or additional features may be introduced in NR Release 18 for SDT, for example, for latency reduction and power saving ([2] RP-212726, “WI on MT-SDT”). For example, mobile terminated MT-SDT will be introduced to support the case where DL data arrives in the RRC_INACTIVE state. The UE may receive a paging that triggers the MT-SDT procedure and respond to the NW via RA-SDT and / or CG-SDT. For example, the UE may receive a paging that includes an MT-SDT indication. In response to receiving the paging, the UE may initiate a 2-step RA-SDT, a 4-step RA-SDT and / or a CG-SDT. The UE may transmit an initial / first UL (data) transmission as a UL response. The UE may transmit an UL response (and / or an initial / first UL (data) transmission) in an MSGA, Msg3 and / or PDU to be transmitted using CG-SDT resources. The UL response may be an RRC message (e.g., RRCResumeRequest). The UE may receive the (initial / first) DL (data) transmission after transmitting the UL response. The UE may receive one or more (subsequent) DL (data) transmissions after receiving the (initial / first) DL (data) transmission. The UE may transmit one or more (subsequent) UL (data) transmissions after receiving the (initial / first) DL (data) transmission.

[0438] There may be differences between MT-SDT in NR and MT-EDT in LTE. The UE receives DL data in a RA procedure for MT-EDT in LTE, while the UE may receive DL data in a RA procedure (e.g., RA-SDT) and / or via CG resources in NR (e.g., CG-SDT). There is one DL transmission in the MT-EDT procedure, while there may be multiple DL (data) transmissions during / in the MT-SDT procedure. The UE may receive (subsequent) DL data / transmissions in a dynamic DL assignment provided by the NW. The UE may receive (subsequent) DL data / transmissions in a (pre-)configured physical downlink shared channel (PDSCH) resources (e.g., through DL semi-persistent scheduling (SPS)). DLSPS may be applied in the RRC_INACTIVE state.

[0439] In response to DL data (e.g., small data) available for transmission while the UE is in the RRC_INACTIVE state, the NW may instruct the UE (e.g., via paging) to initiate an MT-SDT procedure. In order to perform MT-SDT in NR, the NW may send a paging containing an MT-SDT indication to the UE. In response to the reception of the paging indicating MT-SDT, the UE may initiate / trigger the MT-SDT procedure. The UE may need to send an RRC message to the NW before receiving the DL data. The UE may receive DL data directly after receiving the paging. The UE will monitor the Physical Downlink Control Channel (PDCCH) in the paging occasion. The UE will start monitoring the PDCCH in response to receiving the paging. The UE will continue to monitor the PDCCH from the receipt of the paging indicating MT-SDT to the completion of the MT-SDT (e.g., termination of the MT-SDT procedure).

[0440] The UE will initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit an RRC recovery request message (e.g., RRCResumeRequest) in an RA procedure. The UE may transmit an RRC recovery request message (e.g., RRCResumeRequest) using RA resources and / or pre-configured PUSCH resources. The RA procedure may be normal RA and / or RA-SDT. The pre-configured PUSCH resources may be CG-SDT resources. The UE may transmit an RRC recovery request message (e.g., RRCResumeRequest) in a Msg3, message B (MSGB), and / or PDU to be transmitted using CG-SDT resources. The UE may receive DL (data) transmission in response to the transmission of the RRC recovery request message (e.g., RRCResumeRequest). The UE may receive DL (data) transmission in dynamically granted and / or pre-configured PDSCH resources. The UE may receive DL (data) transmission using DL SPS.

[0441] When the NW has DL data to transmit, the NW may send a paging message to instruct the UE (e.g., in the RRC_INACTIVE state) to perform MT-SDT. The UE may receive the paging message indicating MT-SDT. The UE may receive a paging message (e.g., a paging message) with a parameter (e.g., a true MT-SDT) indicating MT-SDT. The UE may receive downlink control information (DCI) and / or PDCCH indicating MT-SDT.

[0442] There may be multiple DL (data) transmissions during / in the MT-SDT procedure. DL (data) transmissions during / in the MT-SDT procedure may be small and infrequent packets. For example, Figure 15As shown in , the NW can configure and / or provide type 1 configured (UL) grant (e.g., CG-SDT resources) in a first RRC release message (e.g., RRCRelease). In response to receiving the first RRC release message (e.g., RRCRelease), the UE can transition to the RRC_INACTIVE state. For example, when there is DL small data to be transmitted, the NW can transmit paging (e.g., a paging message) to indicate MT-SDT. In response to receiving a paging indicating MT-SDT, the UE can use the configured UL grant to transmit an RRC recovery request message (e.g., RRCResumeRequest). After receiving the RRC recovery request message (e.g., RRCResumeRequest), the NW can send multiple PDCCHs to schedule each PDSCH transmission for multiple DL (small data) transmissions. When a second RRC release message (e.g., RRCRelease) is received at the end of the SDT procedure, the UE can reset the MAC and clear the configured UL grant.

[0443] It would be beneficial for the UE to use dedicated resources and / or pre-configured PDSCH resources (e.g., DL SPS resources) to receive DL data in the RRC_INACTIVE state. The UE may activate and / or (re)initialize DL SPS for DL ​​transmission in MT-SDT. When the UE activates DL SPS, the UE stores the DL assignment (for the serving cell) and the associated hybrid automatic repeat request (HARQ) information as a configured DL assignment, and (re)initializes the configured DL assignment to start in the associated PDSCH duration. After activating and / or (re)initializing DL SPS, the UE will consider the configured / stored DL assignment to recur and / or occur based on predefined rules (e.g., in a time slot according to TS 38.321 ([4] 3GPP TS 38.321 V16.7.0, “NR, Medium Access Control (MAC) Protocol Specification”, clause 5.8.1)). When the UE activates DL SPS, the UE may resume DL transmission reception based on the DL SPS configuration. When the UE activates and / or initiates DL SPS, the UE may receive DL transmissions using DL SPS resources. When the UE deactivates DL SPS, the UE may suspend DL transmission reception based on the DL SPS configuration.

[0444] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive a first DL (data) transmission using dynamic assignments and / or DL ​​SPS. After receiving the first DL (data) transmission, the UE may receive subsequent DL (data) transmissions using DL SPS. The UE may be configured with DL SPS when in the RRC_CONNECTED state and / or the RRC_INACTIVE state. The UE may receive a DL SPS configuration, configured DL assignments, and / or DL ​​SPS resources. The UE may receive one or more DL SPS configurations (e.g., on a bandwidth part (BWP)). The DL SPS configuration may include configured DL assignments and / or DL ​​SPS resources. The configured DL assignment may be referred to as a DL SPS resource. A UE may be activated to (start) receiving DL (data) transmissions using DL SPS. A UE may be deactivated to stop receiving DL (data) transmissions using DL SPS.

[0445] For example, if Figure 16 As shown in , the NW can configure and / or provide type 1 configured (UL) grant (e.g., CG-SDT resources) in a first RRC release message (e.g., RRCRelease). In response to receiving the first RRC release message (e.g., RRCRelease), the UE can transition to the RRC_INACTIVE state. For example, when there is DL small data to be transmitted, the NW can transmit paging (e.g., a paging message) to indicate MT-SDT. In response to receiving a paging indicating MT-SDT, the UE can use the configured UL grant to transmit an RRC resume request message (e.g., RRCResumeRequest). After receiving the RRC resume request message (e.g., RRCResumeRequest), the NW can send a PDCCH to configure, activate, indicate and / or provide a DL SPS (e.g., configured DL assignment) for multiple DL (small data) transmissions. When a second RRC release message (e.g., RRCRelease) is received at the end of the SDT procedure, the UE can reset the MAC and clear the configured UL grant and the configured DL assignment.

[0446] The UE may receive one or more DL SPS configurations and / or DL ​​SPS resources in an RRC message (e.g., RRCRelease when transitioning the UE from the RRC_CONNECTED state to the RRC_INACTIVE state, RRCReconfiguration in the RRC_CONNECTED state). The UE may receive the DL SPS configuration and / or DL ​​SPS resources in system information (e.g., a system information block (SIB) in the RRC_INACTIVE state). The UE may receive the DL SPS configuration and / or DL ​​SPS resources in paging (e.g., in the RRC_INACTIVE state). The UE may receive the DL SPS configuration and / or DL ​​SPS resources in Msg4 and / or MSGB (e.g., in an RA procedure triggered for MT-SDT).

[0447] The UE may receive an indication of activation of the DL SPS on the PDCCH. The activation (indication) of the DL SPS may be indicated in the PDCCH content with the DL assignment. The activation (indication) of the DL SPS may be received on the PDCCH opportunity. The activation (indication) of the DL SPS may have a new data indicator (NDI) as 0. The downlink assignment may be addressed to a configured scheduling-radio network temporary identifier (CS-RNTI), an RNTI used in the RRC_INACTIVE state, and / or an RNTI used for MT-SDT. The UE may receive the DL assignment on the PDCCH. The UE may receive the DL assignment in an RRC message (e.g., RRCRelease when the UE is transitioned from the RRC_CONNECTED state to the RRC_INACTIVE state). The UE may receive the DL assignment in system information (e.g., SIB in the RRC_INACTIVE state). The UE may receive the DL assignment in paging (e.g., in the RRC_INACTIVE state). The UE may receive a DL assignment in Msg4 and / or MSG1 (e.g., in an RA procedure triggered for MT-SDT). Throughout this disclosure, a "DL assignment" may be (part of) the information of a DL assignment received on a PDCCH. Throughout this disclosure, a DL assignment may indicate a transmission on a DL-SCH and / or provide related HARQ information. Throughout this disclosure, a "DL assignment" may indicate and / or refer to a PDSCH resource (e.g., for DL ​​SPS, for MT-SDT), and / or a configured DL assignment (e.g., for DL ​​SPS, in RRC_INACTIVE state).

[0448] The UE may receive an indication of deactivation of the DL SPS on the PDCCH. The deactivation (indication) of the DL SPS may be indicated in the PDCCH content. The deactivation (indication) of the DL SPS may be received on a PDCCH opportunity. The deactivation (indication) of the DL SPS may have an NDI of 0. If the PDCCH content indicates SPS deactivation, the UE may clear the configured DL assignment. However, the PDCCH indication of deactivation of the DL SPS may not always be received by the UE during / in the MT-SDT procedure. The NW may not transmit the deactivation (indication) of the DL SPS at the end of the MT-SDT procedure. The UE may need to handle failures in the MT-SDT procedure. The UE may terminate the MT-SDT procedure without an NW indication. Therefore, the UE will need to determine when to terminate the MT-SDT procedure and / or deactivate the DL SPS.

[0449] When non-SDT data arrives during the MT-SDT procedure, the UE may inform the NW via UE Assistance Information (UAI). The NW may transmit an RRC resume message (e.g., RRCResume) to the UE. In response to receiving the RRC resume message (e.g., RRCResume), the UE may enter the RRC_CONNECTED state and clear the configured UL grant by considering the TA timer for CG-SDT (e.g., cg-SDT-TimeAlignmentTimer) as expired. However, the UE will need to determine whether to clear the configured DL assignment in response to receiving the RRC resume message (e.g., RRCResume).

[0450] The UE may terminate the MT-SDT procedure and / or deactivate / release DL SPS in response to one or more of (at least) the following conditions:

[0451] - An indication is received on the PDCCH (e.g., an indication of DL SPS deactivation is received on the PDCCH);

[0452] -Receive an RRC message (e.g., RRCRelease, RRCResume, RRC message terminating the MT-SDT procedure);

[0453] - Another paging is received (e.g., a paging not indicating MT-SDT, a Radio Access Network (RAN) paging, a paging indicating the arrival of non-SDT DL data);

[0454] - Timer expiration (e.g., expiration of a failure detection timer, a PDCCH monitoring timer, and / or a TA timer);

[0455] - (all) DL Synchronization Signal Blocks (SSBs) (e.g., used for / associated with DL SPS, used for / associated with DL transmission during / in an MT-SDT procedure) fail / become ineligible;

[0456] -Cell reselection;

[0457] - Initiate the RRC recovery procedure from another cell;

[0458] - Reception failure (eg, via DL SPS resources) until a configured time (eg, failure to decode received data until a configured time); and / or

[0459] - Non-SDT UL data arrives (eg, and / or UAI is transmitted to indicate NW).

[0460] In response to terminating the MT-SDT procedure and / or deactivating / releasing DL SPS, the UE may perform one or more of (at least) the following actions:

[0461] - Release DLSPS resources;

[0462] - Clear the soft buffer for DL ​​HARQ process;

[0463] - Clear configured DL assignments;

[0464] - Maintain the DLSPS configuration (e.g., do not release the DLSPS configuration);

[0465] - Stop monitoring PDCCH;

[0466] - transmitting an indication (e.g., uplink control information (UCI), UAI, MAC control element (CE), RRC message) to the NW, e.g., to notify the above conditions or failure of MT-SDT and / or DL ​​SPS;

[0467] -Initiate traditional RA procedures;

[0468] - Initiate MO-SDT procedures (e.g., RA-SDT, CG-SDT); and / or

[0469] - Transition to RRC_IDLE state.

[0470] The UE may deactivate / release the DL SPS and / or terminate the MT-SDT procedure in response to receiving an indication (e.g., DL SPS deactivation) on the PDCCH. The indication may be DL SPS deactivation. DL SPS deactivation may be received / indicated on the PDCCH. The indication may be a dynamic DL assignment. The dynamic DL assignment may replace or overwrite the DL SPS.

[0471] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to transmitting the first / initial UL (data) transmission / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may receive a dynamic DL assignment (e.g., to replace or overwrite the DL SPS). The UE may receive a PDCCH indicating deactivation of the DL SPS (e.g., when the NW has no DL data to transmit).

[0472] In response to receiving an indication on the PDCCH (e.g., DL SPS deactivation), the UE may or may not perform one or more of the following actions. The UE may terminate the MT-SDT procedure. The UE may deactivate the DL SPS. The UE may stop receiving DL (data) transmissions using the DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffers used for the DL HARQ process. The UE may not clear the soft buffers used for the DL HARQ process. The UE may clear the configured DL assignments for the DL SPS. The UE may not clear the configured DL assignments for the DL SPS. The UE may release one or more DL SPS configurations. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may release the DL SPS configuration indicated by the indication on the PDCCH (e.g., DL SPS deactivation). The UE may not release the DL SPS configuration indicated by the indication on the PDCCH (e.g., DL SPS deactivation). The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response.

[0473] The UE may deactivate / release the DL SPS and / or terminate the MT-SDT procedure in response to receiving an RRC message (eg, RRCRelease, RRCResume, an RRC message terminating the MT-SDT procedure).

[0474] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC resumption procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may receive an RRC message at (the end of) the MT-SDT procedure. The RRC message may be a release message (e.g., RRCRelease), a resumption message (e.g., RRCResume), and / or an RRC message terminating the MT-SDT procedure.

[0475] In response to receiving the RRC message, the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop using DL SPS to receive DL (data) transmissions. The UE may release DL SPS resources. The UE may not release DL SPS resources. If the RRC message indicates to release DL SPS resources, the UE may release DL SPS resources. If the RRC message indicates an RRC state transition, the UE may release DL SPS resources. If the RRC message indicates not to release DL SPS resources, the UE may not release DL SPS resources. If the RRC message indicates that the UE remains in the RRC_INACTIVE state (e.g., via RRCRelease with suspendConfig), the UE may not release DL SPS resources. The UE may clear the soft buffer for the DL HARQ process. The UE may not clear the soft buffer for the DL HARQ process. The UE may clear the configured DL assignment for DL ​​SPS. The UE may not clear the configured DL assignment for DL ​​SPS. Not clearing the configured DL assignment for DL ​​SPS may mean maintaining (using) the configured DL assignment for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. If the RRC message indicates the release of the DL SPS configuration, the UE may release one or more DL SPS configurations. If the RRC message indicates an RRC state transition, the UE may release the DL SPS configuration. If the RRC message indicates not to release the DL SPS configuration, the UE may not release one or more DL SPS configurations. If the RRC message indicates that the UE remains in the RRC_INACTIVE state (e.g., RRCRelease with suspendConfig), the UE may not release the DL SPS configuration. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. If the RRC message is an RRC release message (e.g., RRCRelease) with a suspend configuration (e.g., suspendConfig), the UE may remain in the RRC_INACTIVE state. If the RRC message is an RRC release message (e.g., RRCRelease) without a suspend configuration (e.g., suspendConfig), the UE may transition to the RRC_IDLE state. If the RRC message is an RRC resume message (e.g., RRCResume), the UE may transition to the RRC_CONNECTED state. In response to receiving the RRC resume message (e.g., RRCResume), the UE may transition to the RRC_CONNECTED state and clear the configured DL assignment for DL ​​SPS.In response to receiving the RRC resume message (e.g., RRCResume), the UE may transition to the RRC_CONNECTED state without clearing the configured DL assignment for DL ​​SPS (e.g., maintaining the use of the configured DL assignment for DL ​​SPS when the UE is in the RRC_CONNECTED state). In response to receiving the RRC resume message (e.g., RRCResume), the UE may consider the TA timer (e.g., the legacy TA timer, the TA timer for CG-SDT) to have expired.

[0476] The UE may deactivate / release DL SPS and / or terminate the MT-SDT procedure in response to receiving another paging (e.g., except a paging initiating the MT-SDT procedure, a paging not indicating MT-SDT, a RAN paging, or a paging indicating the arrival of non-SDT DL data).

[0477] For example, the UE may initiate an MT-SDT procedure in response to receiving a first paging. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may receive a second paging during the MT-SDT procedure. The second fill may be a paging that does not indicate MT-SDT, a RAN paging, a paging that indicates the arrival of non-SDT DL data, and / or a paging that initiates another RRC recovery procedure.

[0478] In response to receiving the second paging, the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop receiving DL (data) transmissions using DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffer for the DL HARQ process. The UE may not clear the soft buffer for the DL HARQ process. The UE may clear the configured DL assignment for DL ​​SPS. The UE may not clear the configured DL assignment for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may terminate the RRC recovery procedure and / or initiate another RRC recovery procedure. The UE may initiate a legacy RA. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response. The UE may perform an RRC state transition in response to receiving a second paging call and / or initiating a legacy RA.

[0479] The UE may deactivate / release the DL SPS and / or terminate the MT-SDT procedure in response to expiration of a timer (eg, expiration of a failure detection timer, expiration of a PDCCH monitoring timer, and / or expiration of a TA timer).

[0480] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using a DL SPS. The UE may start a timer during / in the MT-SDT procedure.

[0481] It can be a failure detection timer. The failure detection timer can be a timer used to handle the failure of the RRC recovery procedure, MO-SDT procedure and / or MT-SDT procedure. The failure detection timer can be started immediately after the transmission of the first RRC message (e.g., RRCResumeRequest, RRCResumeRequest1). The failure detection timer can be stopped immediately after receiving the second RRC message (e.g., RRCResume, RRCSetup, RRCRelease, RRCReject). When the failure detection timer expires, the UE can consider the failure of the RRC recovery and / or MT-SDT procedure.

[0482] The timer may be a PDCCH monitoring timer. The PDCCH monitoring timer may be a timer used to control PDCCH monitoring of the UE. When the PDCCH monitoring timer is running, the UE may monitor the PDCCH.

[0483] The timer may be a TA timer (e.g., a legacy TA timer, a TA timer for CG-SDT, or a TA timer for MT-SDT). The TA timer may be a timer that controls how long the UE considers the serving cell, UL transmission for CG-SDT, and / or UL transmission for MT-SDT to be UL time-aligned. When the TA timer is running, the UE may consider the TA to be valid.

[0484] In response to the expiration of the timer, the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop using DL SPS to receive DL (data) transmissions. The UE may release DL SPS resources. The UE may not release DL SPS resources. If the timer is a failure detection timer (and / or if the failure detection timer expires), the UE may release DL SPS resources. If the timer is a TA timer (and / or if the TA timer expires), the UE may release DL SPS resources. If the timer is a TA timer (and / or if the TA timer expires), the UE may not release DL SPS resources. If the timer is a PDCCH monitoring timer (and / or if the PDCCH monitoring timer expires), the UE may not release DL SPS resources. The UE may clear the configured DL assignment for DL ​​SPS. The UE may not clear the configured DL assignment for DL ​​SPS. Not clearing the configured DL assignment for DL ​​SPS may mean maintaining (using) the configured DL assignment for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may release the DL SPS configuration corresponding to a timer (e.g., PDCCH monitoring timer, TA timer). The UE may not release the DL SPS configuration that does not correspond to a timer (e.g., PDCCH monitoring timer, TA timer). The UE may clear the soft buffer for the DL HARQ process. The UE may not clear the soft buffer for the DL HARQ process. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may not terminate the MT-SDT procedure. The UE may transmit an indication to the NW, for example, to notify the expiration of a timer or the failure of MT-SDT and / or DL ​​SPS. The UE may initiate a legacy RA procedure (to indicate the NW). The UE may indicate to the NW that the TA is not valid. The UE may indicate to the NW to recover the TA. The UE may indicate to the NW that the MT-SDT failed. The indication may be UCI, UAI, and / or MAC CE. The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response. The UE may perform an RRC state transition in response to expiration of a timer. In response to expiration of the timer, the UE may clear the configured DL assignment for DL ​​SPS. In response to expiration of the timer, the UE may not clear the configured DL assignment for DL ​​SPS.

[0485] The UE may deactivate / release the DL SPS and / or terminate the MT-SDT procedure in response to one (or all) DL SSBs (e.g., associated with the DL SPS) becoming ineligible (e.g., the reference symbol received power (RSRP) of the DL SSB becomes below an RSRP threshold). The NW may configure the DL SSBs for each DL SPS resource. An SSB may refer to a beam. The UE may select any DL SSB among the configured DL SSBs to receive DL (data) transmission using the DL SPS. The UE may select a DL SSB among the configured DL SSBs having a radio condition (e.g., RSRP, channel state information reference signal (CSI-RS)) that is higher than and / or equal to a first threshold to receive DL (data) using the DL SPS. The UE may use the indicated DL SSB among the configured DL SSBs to receive DL (data) transmission using the DL SPS. The UE may evaluate / re-evaluate the radio conditions of the DL SSBs used to receive DL (data) transmission during the MT-SDT procedure. The UE may compare the radio conditions (e.g., RSRP, CSI-RS) for receiving the DL SSB for DL ​​(data) transmission with a second threshold value during the MT-SDT procedure. The first threshold value and the second threshold value may be RSRP or CSI-RS threshold values. The first threshold value and the second threshold value may be the same threshold value. The first threshold value and the second threshold value may be different threshold values.

[0486] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may evaluate the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB immediately after receiving the paging call and / or initiating / triggering the MT-SDT procedure. The UE may evaluate the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB in response to transmitting the first / initial UL (data) transmission. The UE may evaluate the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB before receiving the first DL (data) transmission. The UE may evaluate the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB before receiving subsequent DL (data) transmissions. The UE may evaluate the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB before using the DL SPS (resources). The DL SSB (e.g., for DL ​​SPS) may be and / or become ineligible during the MT-SDT procedure. The radio conditions (e.g., RSRP, CSI-RS) of the DL SSB (e.g., for DL ​​SPS) may be and / or become lower than and / or equal to a threshold during the MT-SDT procedure. The DL SSB may be ineligible when the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB are lower than and / or equal to a threshold. The DL SSB may be ineligible when the radio conditions (e.g., RSRP, CSI-RS) of the DL SSB are not higher than a threshold.

[0487] In response to one or all DL SSBs (e.g., for DL ​​SPS) being ineligible, the UE may or may not perform one or more of the following actions: The UE may deactivate the DL SPS. The UE may stop receiving DL (data) transmissions using the DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffers used for the DL HARQ process. The UE may not clear the soft buffers used for the DL HARQ process. The UE may clear the configured DL assignments for the DL SPS. The UE may not clear the configured DL assignments for the DL SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may retain the DL SPS configuration. The UE may release the DL SPS configuration corresponding to the ineligible DL SSB. The UE may not release the DL SPS configuration that does not correspond to the ineligible DL SSB. If all DL SSBs configured for the DL SPS configuration are ineligible, the UE may release the DL SPS configuration. If one of the DL SSBs configured for the DL SPS configuration is ineligible, the UE may release the DL SPS configuration. If all DL SSBs configured for DL ​​SPS configuration fail, the UE may release the DL SPS configuration. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may not terminate the MT-SDT procedure. The UE may transmit an indication to the NW, for example, to notify SSB failure or failure of MT-SDT and / or DL ​​SPS. The UE may initiate a traditional RA procedure (to indicate the NW). The UE may initiate a RA-SDT and / or CG-SDT procedure (to indicate the NW). The UE may indicate MT-SDT failure to the NW. The UE may indicate beam failure to the NW. The UE may request beam recovery from the NW. The indication may be UCI, UAI and / or MAC CE. The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response. The UE may perform an RRC state transition in response to one or all DL SSBs (e.g., for DL ​​SPS) becoming ineligible.

[0488] The UE may deactivate / release DL SPS and / or terminate the MT-SDT procedure in response to moving and / or linking to another cell (e.g., changing its serving cell, cell reselection). The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to initiating an RRC recovery procedure from another cell. The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to moving to a cell different from the cell in which the UE received the DL SPS configuration (and / or initiating the RRC recovery procedure from it). The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to moving to a cell different from the cell in which the UE transitioned from the RRC_CONNECTED state to the RRC_INACTIVE state (and / or initiating the RRC recovery procedure from it). The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to moving to a cell different from the cell in which the UE initiated / triggered the MT-SDT procedure (and / or initiating the RRC recovery procedure from it). The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to performing cell reselection.

[0489] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging in a first cell. The UE may initiate / trigger a first RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may move to a second cell during the MT-SDT procedure. The UE may perform cell reselection. The UE may initiate / trigger a second RRC recovery procedure in the second cell.

[0490] In response to moving to the second cell (e.g., and / or linking to the second cell, performing cell reselection to the second cell, initiating / triggering a second RRC recovery procedure in the second cell), the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop receiving DL (data) transmissions using DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear soft buffers for DL ​​HARQ processes. The UE may not clear soft buffers for DL ​​HARQ processes. The UE may clear configured DL assignments for DL ​​SPS. The UE may not clear configured DL assignments for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may stop monitoring PDCCH. The UE may not stop monitoring PDCCH. The UE may terminate the MT-SDT procedure. The UE may initiate / trigger another MT-SDT procedure in the second cell. The UE may initiate a legacy RA procedure. The UE may initiate a second RRC recovery procedure. The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with a NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without a NW response. The UE may perform an RRC state transition in response to moving to a second cell, linking to the second cell, performing cell reselection to the second cell, and / or initiating / triggering a second RRC recovery procedure in the second cell.

[0491] The UE may deactivate / release DL SPS and / or terminate the MT-SDT procedure in response to repeated transmission failures (e.g., failure to decode received DL data (e.g., via DL SPS resources, MAC PDUs, Radio Link Control (RLC) PDUs)) until a configured time.

[0492] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The UE may fail to decode one or more received DL data during / in the MT-SDT procedure.

[0493] In response to repeated transmission failures (e.g., failure to decode received DL data (e.g., MAC PDU, RLC PDU) until a configured time (e.g., a configured threshold)), the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop receiving DL (data) transmissions using DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffers for the DL HARQ process. The UE may not clear the soft buffers for the DL HARQ process. The UE may clear the configured DL assignments for DL ​​SPS. The UE may not clear the configured DL assignments for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may release the DL SPS configuration corresponding to the DL HARQ process in which the repeated transmission failure occurred. The UE may not release the DL SPS configuration that does not correspond to the DL HARQ process in which the repeated transmission failure occurred. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may not terminate the MT-SDT procedure. The UE may transmit an indication to the NW, for example, to notify a reception failure, or a failure of MT-SDT and / or DL ​​SPS. The UE may initiate a traditional RA procedure (to indicate the NW). The UE may initiate a RA-SDT and / or CG-SDT procedure (to indicate the NW). The UE may indicate an MT-SDT failure to the NW. The UE may indicate a beam failure to the NW. The UE may request beam recovery from the NW. The indication may be UCI, UAI and / or MAC CE. The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response. The UE may perform an RRC state transition in response to failing to decode the received DL data until a configured time.

[0494] The UE may deactivate / release DL SPS and / or terminate the MT-SDT procedure in response to the arrival of non-SDT UL data. The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to transmitting UAI to indicate the arrival of non-SDT UL data.

[0495] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using a DL SPS. Non-SDT UL data may arrive at the UE during the MT-SDT procedure. Non-SDT UL data may be data belonging to a logical channel (LCH) that is not allowed to be transmitted by the SDT procedure (e.g., configured by the NW). Non-SDT UL data may be data belonging to a data radio bearer (DRB) and / or a signaling radio bearer (SRB) that is not configured for SDT. SDT UL data may be data belonging to a logical channel (LCH) that is allowed to be transmitted by the SDT procedure (e.g., configured by the NW). The SDT UL data may be data belonging to a DRB and / or SRB configured for SDT.

[0496] In response to the arrival of non-SDT UL data during the MT-SDT procedure, the UE may inform the NW, for example, by transmitting a UAI. The UAI may or may not include a resumption cause (e.g., ResumeCause). In response to the arrival of non-SDT UL data and / or the transmission of the UAI, the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop receiving DL (data) transmissions using DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffer for the DL HARQ process. The UE may not clear the soft buffer for the DL HARQ process. The UE may clear the configured DL assignment for DL ​​SPS. The UE may not clear the configured DL assignment for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may initiate a legacy RA procedure (to indicate the NW). The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with an NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without an NW response. The UE may perform an RRC state transition in response to the arrival of non-SDT UL data.

[0497] The UE may deactivate DL SPS and / or terminate the MT-SDT procedure in response to the MT-SDT failure.

[0498] For example, the UE may initiate an MT-SDT procedure in response to receiving a paging call. The UE may initiate / trigger an RRC recovery procedure for the MT-SDT procedure. The UE may transmit a first / initial UL (data) transmission (e.g., with an RRCResumeRequest) using RA-SDT / CG-SDT resources during / in the MT-SDT procedure. In response to / after transmitting the first / initial UL (data) transmission, the UE may receive one or more DL (data) transmissions using DL SPS. The MT-SDT procedure may be deemed to have failed in response to one or more of (at least) the following conditions:

[0499] - Another paging is received (e.g., a paging different from a paging indicating MT-SDT, a RAN paging, a paging indicating the arrival of non-SDT DL data);

[0500] - Timer expiration (e.g. expiration of a failure detection timer and / or a TA timer);

[0501] - DL SSB (e.g., used for DL ​​SPS, for DL ​​transmission during / in MT-SDT procedure) is / becomes ineligible (e.g., radio conditions for DL ​​SSB are below or equal to the RSRP threshold);

[0502] -Cell reselection;

[0503] - initiating an RRC recovery procedure from another cell (e.g. a different cell from the cell in which the UE initiated the MT-SDT procedure), e.g. to change the serving cell; and / or

[0504] - Repeated transmission failures (eg, failure to decode received data until a configured time).

[0505] In response to MT-SDT failure, the UE may or may not perform one or more of the following actions. The UE may deactivate DL SPS. The UE may stop receiving DL (data) transmissions using DL SPS. The UE may release DL SPS resources. The UE may not release DL SPS resources. The UE may clear the soft buffer for the DL HARQ process. The UE may not clear the soft buffer for the DL HARQ process. The UE may clear the configured DL assignment for DL ​​SPS. The UE may not clear the configured DL assignment for DL ​​SPS. The UE may release the DL SPS configuration. The UE may not release the DL SPS configuration. The UE may maintain the DL SPS configuration. The UE may stop monitoring the PDCCH. The UE may not stop monitoring the PDCCH. The UE may terminate the MT-SDT procedure. The UE may transmit an indication to the NW, for example, to notify of a reception failure, or a failure of MT-SDT and / or DL ​​SPS. The UE may initiate a legacy RA procedure (to indicate the NW). The UE may remain in the RRC_INACTIVE state. The UE may transition to the RRC_IDLE state. The UE may transition to the RRC_CONNECTED state. The UE may perform an RRC state transition with a NW response (e.g., RRCRelease, RRCResume). The UE may perform an RRC state transition without a NW response. The UE may perform an RRC state transition in response to an MT-SDT failure.

[0506] Combinations of examples herein in this disclosure are possible for the various embodiments and concepts disclosed herein.

[0507] Throughout this disclosure, "paging" may refer to a paging message (e.g., paging) and / or (DCI on) a PDCCH addressed to a specific UE RNTI (e.g., cell RNTI (C-RNTI), CS-RNTI, paging RNTI (P-RNTI), RNTI used in the RRC_INACTIVE state, RNTI used for MT-SDT). The specific UE RNTI may be an RNTI provided by the NW in the RRC_CONNECTED state and / or the RRC_INACTIVE state.

[0508] Throughout this disclosure, an RA-SDT procedure may be an RA procedure with UL data, an RA procedure using RA resources used for MO-SDT. Legacy RA and / or normal RA may be an RA procedure without transmitting user data, an RA procedure using RA resources not used for MO-SDT, and / or an RA procedure using RA resources not used for one or more (Release 17) features, such as (MO-)SDT, RedCap, slicing, and coverage enhancement. Throughout this disclosure, "RRC recovery procedure" may be referred to as "RRC connection recovery procedure" and / or be replaced by it. DL SPS may be referred to as SPS. "DL data transmission" may be "DL transmission." "UL data transmission" may be "UL transmission."

[0509] Throughout this disclosure, "SDT" may be, may be referred to as, may be replaced by, and / or may be supplemented with "MO-SDT" and / or "MT-SDT." MO-SDT may be an SDT procedure triggered by an upper layer when small UL data arrives. MT-SDT may be an SDT procedure triggered by a paging message when small DL data arrives. The UE may transmit and / or receive small data in the RRC_INACTIVE state during the SDT procedure.

[0510] In the RRC recovery procedure forming the RRC_INACTIVE state, the UE will transmit an RRC recovery request message (e.g., RRCResumeRequest / RRCResumeRequest1) to the NW. In response to receiving the RRC recovery request message, the NW may transmit an RRC recovery message (e.g., RRCResume) to the UE. In response to receiving the RRC recovery message (e.g., RRCResume), the UE will transmit an RRC recovery completion message (e.g., RRCresumeComplete) and transition to the RRC_CONNECTED state. In response to receiving the RRC recovery request message, the NW may transmit an RRC release message (e.g., RRCRelease) with a suspend configuration (e.g., suspendConfig) to the UE. In response to receiving the RRC release message (e.g., RRCRelease) with a suspend configuration (e.g., suspendConfig), the UE will remain in the RRC_INACTIVE state. In response to receiving the RRC recovery request message, the NW may transmit an RRC release message (e.g., RRCRelease) without a suspend configuration (e.g., suspendConfig) to the UE. In response to receiving an RRC release message (e.g., RRCRelease) without a suspension configuration (e.g., suspendConfig), the UE will transition to the RRC_IDLE state. The RRC resumption procedure may be triggered / initiated in response to paging and / or initiation of MT-SDT / MO-SDT procedures.

[0511] The UE may receive (and / or apply) some configurations related to MO-SDT (e.g., CG-SDT / RA-SDT resources) and / or MT-SDT from the NW. The UE may receive (and / or apply) some configurations related to DL SPS from the NW. The above configuration may be received in the RRC_CONNECTED state. The configuration may be received in the RRC_INACTIVE state. The configuration may be received in an RRC message (e.g., RRCReconfiguration, RRCRelease). The UE may receive and / or be configured with a DL assignment (indicating PDSCH resources) for DL ​​SPS. The UE may receive the DL assignment in / together with the above configuration. The UE may receive the DL assignment in an RRC message, system information, paging and / or Msg3 / MSGB. The DL assignment may indicate the activation of the DL SPS. The DL assignment may not indicate the activation of the DL SPS. The DL assignment may be stored and / or (re)used for DL ​​transmission for DL ​​SPS. The UE may consider a (configured / stored) DL assignment (e.g., PDSCH resource) to be recurring and / or reused based on a predefined rule / formula for DL ​​SPS. The starting time slot of the (configured / stored) DL assignment (e.g., PDSCH resource) may be the time slot in which the first transmission of the PDSCH for the DL assignment is (re)initialized. The starting time slot of the (configured / stored) DL assignment (e.g., PDSCH resource) may be the time slot in which the DL assignment is received. The starting time slot of the (configured / stored) DL assignment (e.g., PDSCH resource) may be the time slot in which the DL SPS configuration is received. The starting time slot of the (configured / stored) DL assignment (e.g., PDSCH resource) may be the time slot indicated in the DL SPS configuration.

[0512] A UE may be referred to as a UE, a MAC entity of a UE, and / or an RRC entity of a UE. A UE may be an NR device. A UE may be an NR Lite device. A UE may be a device with insufficient capabilities. A UE may be a mobile phone. A UE may be a wearable device. A UE may be a sensor. A UE may be a fixed device.

[0513] The NW may be a network node. The NW may be a base station. The NW may be an access point. The NW may be an evolved Node B (eNB). The NW may be an NR Node B (gNB).

[0514] See Figure 17, with respect to this and other concepts, systems and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: receiving a first paging indicating MT-SDT from a NW (step 1002), initiating / triggering an MT-SDT procedure in response to receiving the first paging, and initiating a first RRC connection recovery procedure (step 1004), transmitting UL data including at least an RRC recovery request message (e.g., RRCResumeRequest) (step 1006), initializing a DL SPS to receive one or more DL transmissions after transmitting the UL data (step 1008), and terminating the MT-SDT procedure and / or deactivating the DL SPS based on and / or in response to at least one or more conditions (step 1010).

[0515] In various embodiments, the paging is a paging message and / or PDCCH reception.

[0516] In various embodiments, the UE transmits UL data in a RA procedure and / or using pre-configured PUSCH resources.

[0517] In various embodiments, the DL SPS is configured and activated by the NW.

[0518] In various embodiments, the condition is that the UE receives an indication on the PDCCH.

[0519] In various embodiments, the condition is that the UE receives an RRC message.

[0520] In various embodiments, the condition is that the UE receives the second page.

[0521] In various embodiments, the condition is expiration of a timer (eg, failure detection timer, PDCCH monitoring timer, TA timer).

[0522] In various embodiments, the condition is that (all) DL SSBs associated with the DL SPS are / become ineligible.

[0523] In various embodiments, the condition is that the UE performs cell reselection.

[0524] In various embodiments, the condition is that the UE initiates a second RRC connection resumption procedure.

[0525] In various embodiments, the condition is a failure of reception until a configured time.

[0526] In various embodiments, the condition is the arrival of non-SDT UL data.

[0527] Return Reference Figure 3 and Figure 4In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive a first paging indicating MT-SDT from the NW; (ii) initiate / trigger an MT-SDT procedure and initiate a first RRC connection recovery procedure in response to receiving the first paging; (iii) transmit UL data including at least an RRC recovery request message (e.g., RRCResumeRequest); (iv) initialize a DL SPS to receive one or more DL transmissions after transmitting the UL data; and (v) terminate the MT-SDT procedure and / or deactivate the DL SPS based on and / or in response to at least one or more conditions. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0528] Return to reference again Figure 3 and Figure 4 In one or more embodiments from the perspective of the NW, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) transmit a first paging indicating MT-SDT to the UE; (ii) initiate / trigger an MT-SDT procedure at the UE in response to receiving the first paging, and initiate a first RRC connection recovery procedure at the UE; (iii) receive UL data including at least an RRC recovery request message (e.g., RRCResumeRequest); (iv) initialize a DL SPS at the UE to receive one or more DL transmissions after the UL data is transmitted; and (v) terminate the MT-SDT procedure and / or deactivate the DL SPS at the UE based on and / or in response to at least one or more conditions. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0529] See Figure 18, with respect to this and other concepts, systems and methods of the present invention, a method 1020 for a UE in a wireless communication system includes: receiving one or more configurations for a DL SPS in an RRC_INACTIVE state (step 1022), initiating / triggering an MT-SDT procedure in response to receiving a paging indicating MT-SDT (step 1024), receiving one or more DL transmissions using the configured DL assignments for the DL SPS during / in the MT-SDT procedure in the RRC_INACTIVE state (step 1026), and maintaining the one or more configurations of the DL SPS and entering an RRC_CONNECTED state in response to receiving an RRC resume message during / in the MT-SDT procedure (step 1028).

[0530] In various embodiments, the method further includes transmitting an RRC resume request message (eg, RRCResumeRequest) using resources used for RA-SDT or CG-SDT in response to initiating / triggering the MT-SDT procedure.

[0531] In various embodiments, the UE clears one or more configurations for CG-SDT and resources for CG-SDT in response to receiving the RRC resume message.

[0532] In various embodiments, the configured DL assignment is provided by the PDCCH for activation of DL SPS or by an RRC release message (eg, RRCRelease).

[0533] In various embodiments, the one or more configurations of the DL SPS are received in an RRC release message (eg, RRCRelease).

[0534] In various embodiments, the UE does not clear the configured DL assignments in response to receiving an RRC resume message (eg, RRC Resume).

[0535] In various embodiments, the UE clears the configured DL assignments in response to receiving an RRC resume message (eg, RRCResume).

[0536] In various embodiments, the UE considers a timing advance (TA) timer expired in response to receiving an RRC resume message (eg, RRC Resume).

[0537] For various embodiments, the UE may receive, for example, one or more configurations for DL ​​SPS in the RRC_INACTIVE state in an RRC release message (e.g., RRCRelease). The UE may receive one or more configurations for CG-SDT and resources for CG-SDT in an RRC release message (e.g., RRCRelease). The NW may transmit paging (e.g., a paging message) to indicate an MT-SDT procedure in the RRC_INACTIVE state. In response to receiving a paging (e.g., a paging message) indicating MT-SDT, the UE may initiate / trigger an (MT-)SDT procedure. In response to initiating / triggering the (MT-)SDT procedure, the UE may transmit an RRC resume request message (e.g., RRCResumeRequest) using resources for RA-SDT or CG-SDT. During / in the (MT-)SDT procedure, the UE may receive one or more DL transmissions using the configured DL assignments for DL ​​SPS. The configured DL assignment may be provided by the PDCCH for activation of the DL SPS or by an RRC release message (e.g., RRCRelease). The NW may transmit an RRC message to end the (MT-)SDT procedure. The NW may transmit an RRC resume message (e.g., RRCResume) to the UE. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may clear one or more configurations for CG-SDT and resources for CG-SDT. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may maintain the one or more configurations of the DL SPS. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may not clear the configured DL assignment. In response to receiving an RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may consider the TA timer to have expired. In response to receiving an RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may enter the RRC_CONNECTED state.

[0538] Return Reference Figure 3 and Figure 4In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive one or more configurations for DL ​​SPS in the RRC_INACTIVE state; (ii) initiate / trigger an MT-SDT procedure in response to receiving a paging indicating MT-SDT; (iii) receive one or more DL transmissions using the configured DL assignments for DL ​​SPS during / in the MT-SDT procedure in the RRC_INACTIVE state; and (iv) maintain the one or more configurations for DL ​​SPS and enter the RRC_CONNECTED state in response to receiving an RRC resume message during / in the MT-SDT procedure. In addition, the CPU 308 can execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0539] See Figure 19 , with respect to this and other concepts, systems and methods of the present invention, a method 1030 for a UE in a wireless communication system includes: receiving one or more configurations for a DL SPS in an RRC_INACTIVE state (step 1032), initiating / triggering an MT-SDT procedure in response to receiving a paging indicating MT-SDT (step 1034), receiving one or more DL transmissions using the configured DL assignments for the DL SPS during / in the MT-SDT procedure in the RRC_INACTIVE state (step 1036), and releasing the one or more configurations of the DL SPS, clearing the configured DL assignments and entering the RRC_CONNECTED state in response to receiving an RRC resume message during / in the MT-SDT procedure (step 1038).

[0540] In various embodiments, the further includes transmitting an RRC resume request message (eg, RRCResumeRequest) using resources used for RA-SDT or CG-SDT in response to initiating / triggering the MT-SDT procedure.

[0541] In various embodiments, the UE clears one or more configurations for CG-SDT and resources for CG-SDT in response to receiving the RRC resume message.

[0542] In various embodiments, the configured DL assignment is provided by the PDCCH for activation of DL SPS or by an RRC release message (eg, RRCRelease).

[0543] In various embodiments, the one or more configurations of the DL SPS are received in an RRC release message (eg, RRCRelease).

[0544] For various embodiments, the UE may receive, for example, one or more configurations for DL ​​SPS in the RRC_INACTIVE state in an RRC release message (e.g., RRCRelease). The UE may receive one or more configurations for CG-SDT and resources for CG-SDT in an RRC release message (e.g., RRCRelease). The NW may transmit paging (e.g., a paging message) to indicate an MT-SDT procedure in the RRC_INACTIVE state. In response to receiving a paging (e.g., a paging message) indicating MT-SDT, the UE may initiate / trigger an (MT-)SDT procedure. In response to initiating / triggering the (MT-)SDT procedure, the UE may transmit an RRC resume request message (e.g., RRCResumeRequest) using resources for RA-SDT or CG-SDT. During / in the (MT-)SDT procedure, the UE may receive one or more DL transmissions using the configured DL assignments for DL ​​SPS. The configured DL assignment may be provided by the PDCCH for activation of the DL SPS or by an RRC release message (e.g., RRCRelease). The NW may transmit an RRC message to end the (MT-)SDT procedure. The NW may transmit an RRC resume message (e.g., RRCResume) to the UE. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may clear one or more configurations for CG-SDT and resources for CG-SDT. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may release the one or more configurations of the DL SPS and / or clear the configured DL assignment. In response to receiving the RRC resume message (e.g., RRCResume) during / in the (MT-)SDT procedure, the UE may enter the RRC_CONNECTED state.

[0545] Return Reference Figure 3 and Figure 4In one or more embodiments from the perspective of the UE, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive one or more configurations for DL ​​SPS in the RRC_INACTIVE state; (ii) initiate / trigger an MT-SDT procedure in response to receiving a paging indicating MT-SDT; (iii) receive one or more DL transmissions using the configured DL assignments for DL ​​SPS during / in the MT-SDT procedure in the RRC_INACTIVE state; and (iv) release the one or more configurations for DL ​​SPS, clear the configured DL assignments, and enter the state in response to receiving an RRC resume message during / in the MT-SDT procedure. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0546] Any combination of the above concepts or teachings can be combined or formed into new embodiments. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

[0547] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0548] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, functionality, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of any other aspects, and that two or more of these aspects can be combined in various ways. For example, a device or method can be implemented using any number of the aspects described herein. Furthermore, the device or method can be implemented using other structures, functionality, or structures and functionality in addition to or different from one or more of the aspects described herein. As examples of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and time hopping sequences.

[0549] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0550] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or a combination of the two. To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those of skill in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0551] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, external to the IC, or both. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0552] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0553] The steps of the methods or algorithms described in conjunction with the various aspects disclosed herein can be implemented directly in hardware, in software modules executed by a processor, or in a combination of the two. Software modules (e.g., containing executable instructions and associated data) and other data can reside in a data storage device, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor") so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integrated with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and storage medium may reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium comprising code related to one or more of the various aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0554] Although the present invention has been described in conjunction with various aspects and examples, it will be understood that the invention is capable of further modification. This application is intended to cover any variations, uses, or adaptations of the invention that generally follow the principles of the invention and include such departures from the present disclosure as come within the scope of known and customary practice in the art to which the invention pertains.

Claims

1. A method for a user equipment, characterized in that: include: initiating a mobile terminated small data transfer procedure in response to receiving the paging, wherein the mobile terminated small data transfer procedure includes a first random access procedure; evaluating a first reference signal received power of a downlink synchronization signal block during the mobile terminated small data transfer procedure; as well as In response to the first reference signal received power of the downlink synchronization signal block being less than a first threshold, a second random access procedure is initiated during the mobile-terminated small data transfer procedure.

2. The method according to claim 1, characterized in that Also includes: A radio resource control resumption procedure for the mobile terminated small data transfer procedure is initiated.

3. The method according to claim 2, characterized in that Also includes: In response to the first reference signal received power of the downlink synchronization signal block being less than the first threshold, the mobile-terminated small data transfer procedure including the radio resource control recovery procedure is not terminated.

4. The method according to claim 2, characterized in that Also includes: The mobile terminated small data transfer procedure including the radio resource control resumption procedure is terminated in response to receiving a radio resource control release message.

5. The method according to claim 1, characterized in that The page includes an indication of a mobile terminated small data transfer.

6. The method according to claim 1, characterized in that The user equipment selects the downlink synchronization signal block having a second reference signal received power greater than or equal to a second threshold.

7. The method according to claim 6, characterized in that The first threshold is the second threshold.

8. The method according to claim 1, characterized in that The downlink synchronization signal block refers to a downlink beam used to receive downlink transmission during the mobile terminated small data transmission procedure.

9. The method according to claim 1, characterized in that The user equipment is in a radio resource control inactive state.

10. The method according to claim 1, characterized in that The user equipment indicates beam failure to a network or requests beam recovery from the network in response to the first reference signal received power of the downlink synchronization signal block being less than the first threshold.

11. A user equipment, characterized in that: include: a memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: initiating a mobile terminated small data transfer procedure in response to receiving the paging, wherein the mobile terminated small data transfer procedure includes a first random access procedure; evaluating a first reference signal received power of a downlink synchronization signal block during said mobile terminated small data transfer procedure; as well as In response to the first reference signal received power of the downlink synchronization signal block being less than a first threshold, a second random access procedure is initiated during the mobile-terminated small data transfer procedure.

12. The user equipment according to claim 11, wherein: The processor is further configured to execute the program code to initiate a radio resource control resumption procedure for the mobile terminated small data transfer procedure.

13. The user equipment according to claim 12, wherein: The processor is further configured to execute the program code to not terminate the mobile-terminated small data transfer procedure including the radio resource control recovery procedure in response to the first reference signal received power of the downlink synchronization signal block being less than the first threshold.

14. The user equipment according to claim 12, wherein: The processor is further configured to execute the program code to terminate the mobile terminated small data transfer procedure including the radio resource control recovery procedure in response to receiving a radio resource control release message.

15. The user equipment according to claim 11, wherein: The page includes an indication of a mobile terminated small data transfer.

16. The user equipment according to claim 11, wherein: The user equipment selects the downlink synchronization signal block having a second reference signal received power greater than or equal to a second threshold.

17. The user equipment according to claim 16, wherein: The first threshold is the second threshold.

18. The user equipment according to claim 11, wherein: The downlink synchronization signal block refers to a downlink beam used to receive downlink transmission during the mobile terminated small data transmission procedure.

19. The user equipment according to claim 11, wherein: The user equipment is in a radio resource control inactive state.

20. The user equipment according to claim 11, wherein: The user equipment indicates beam failure to a network or requests beam recovery from the network in response to the first reference signal received power of the downlink synchronization signal block being less than the first threshold.

Images