Method and apparatus for selecting a subsequent transmission bandwidth portion in a preconfigured small data transmission

Abstract

The present invention discloses a method and apparatus for selecting a subsequent transmission bandwidth portion in a preconfigured small data transmission. In an example from the perspective of a user equipment, the user equipment receives a first radio resource control message from a network node, wherein the first radio resource control message indicates a first uplink bandwidth portion of a cell. In response to initiation of a procedure for using configured granted resources in a radio resource control inactive state, the user equipment performs a bandwidth portion switch from a second uplink bandwidth portion of the cell to a first uplink bandwidth portion of the cell. The user equipment performs a first uplink transmission on the first uplink bandwidth portion using the configured granted resources. In response to completion of the procedure, the user equipment performs a bandwidth portion switch from the first uplink bandwidth portion of the cell to the second uplink bandwidth portion of the cell.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to a method and apparatus for selecting a bandwidth part (BWP) for subsequent transmissions in a small data transmission (SDT) based on preconfigured resources in a wireless communication system. Background Art

[0002] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks with Internet Protocol (IP) data packet communications, which can provide IP-bearing voice, multimedia, multicast and on-demand communication services to users of mobile communication devices.

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

[0004] According to the present disclosure, one or more apparatuses and / or methods are provided. In an example from the perspective of a user equipment (UE), the UE receives a first radio resource control (RRC) message from a network node, wherein the first RRC message indicates a first uplink (UL) bandwidth part (BWP) of a cell. In response to initiation of a procedure using configured grant (CG) resources in an RRC inactive state, the UE performs a BWP switch from a second UL BWP of the cell to a first UL BWP of the cell. The UE performs a first UL transmission using the CG resources on the first UL BWP. In response to completion of the procedure, the UE performs a BWP switch from the first UL BWP of the cell to the second UL BWP of the cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A diagram of a wireless communication system is shown according to an exemplary embodiment.

[0006] 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 exemplary embodiment.

[0007] Figure 3 is a functional block diagram of a communication system according to an exemplary embodiment.

[0008] Figure 4 According to an exemplary embodiment Figure 3 Functional block diagram of the program code.

[0009] Figure 5 is a diagram of transitioning from RRC_INACTIVE to RRC_CONNECTED according to an exemplary embodiment.

[0010] Figure 6 is a diagram of transitioning from RRC_INACTIVE to RRC_CONNECTED according to an exemplary embodiment.

[0011] Figure 7 is a diagram illustrating an exemplary scenario in which a UE receives a rejection from a network according to an exemplary embodiment.

[0012] Figure 8 is a diagram of a UE state machine and / or state transitions according to an exemplary embodiment.

[0013] Fig. 9 is a diagram of a radio resource control (RRC) connection recovery according to an exemplary embodiment.

[0014] Fig.10 is a diagram of RRC connection recovery according to an exemplary embodiment.

[0015] Fig.11 is a diagram of RRC connection recovery according to an exemplary embodiment.

[0016] Fig.12 is a diagram of RRC connection recovery according to an exemplary embodiment.

[0017] Fig.13 is a diagram of RRC connection recovery according to an exemplary embodiment.

[0018] Fig.14 is a diagram of an RRC connection release according to an exemplary embodiment.

[0019] Fig.15 is a diagram of bandwidth adaptation according to an exemplary embodiment.

[0020] Fig.16 is a diagram illustrating an exemplary situation in which a small data transfer (SDT) is performed in an RRC_INACTIVE state according to an exemplary embodiment.

[0021] Fig.17 is a diagram illustrating an exemplary situation in which SDT is performed in the RRC_INACTIVE state according to an exemplary embodiment.

[0022] Fig.18 is a diagram illustrating an exemplary situation in which SDT is performed in the RRC_INACTIVE state according to an exemplary embodiment.

[0023] Fig.19 is a diagram illustrating an exemplary scenario associated with the execution of an SDT procedure by a UE according to an exemplary embodiment.

[0024] Fig. 20 is a diagram illustrating an exemplary scenario associated with the execution of an SDT procedure by a UE according to an exemplary embodiment.

[0025] Fig.21 is a flow chart according to an exemplary embodiment.

[0026] Fig. 22 is a flow chart according to an exemplary embodiment. DETAILED DESCRIPTION

[0027] The exemplary wireless communication systems and devices described below adopt 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 (code division multiple access, CDMA), time division multiple access (time division multiple access, TDMA), orthogonal frequency division multiple access (orthogonal frequency division multiple access, OFDMA), third generation partnership project (3GPP) long term evolution (Long Term Evolution, LTE) radio access, 3GPP long term evolution advanced (Long Term Evolution Advanced, LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (Ultra Mobile Broadband, UMB), WiMax, 3GPP New Radio (New Radio, NR) radio access for 5G, or some other modulation technology.

[0028] Specifically, the exemplary wireless communication system apparatus described below may be designed to support one or more standards, such as standards provided by an association named “3rd Generation Partnership Project” (referred to herein as 3GPP), including: 3GPP TS 38.300 V16.0.0, “NR: NR and NG-RAN overall description, Stage 2”; 3GPP TS 38.321 V16.0.0, “NR: MAC protocol specification”; 3GPP TS 38.331 V16.0.0, “NR: RRC protocol specification”; RP-193252, “New Work Item on NR small data transmissions in INACTIVE state”. The standards and documents listed above are expressly incorporated herein by reference in their entirety.

[0029] Figure 1 A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. An access network 100 (AN) includes multiple antenna groups, one antenna group includes 104 and 106, another antenna group includes 108 and 110, and another antenna group includes 112 and 114. Figure 1 , only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access terminal 116 (AT) 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 access terminal 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 a frequency-division duplexing (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 the frequency used by reverse link 118.

[0030] Each antenna group 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 can each be designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0031] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Also, an access network that uses beamforming to transmit to access terminals that are randomly dispersed throughout the coverage area of ​​the access network will generally cause less interference to access terminals in neighboring cells than an access network that transmits to its access terminals via a single antenna.

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

[0033] Figure 2 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)) are presented in a multiple-input and multiple-output (MIMO) system 200. At the transmitter system 210, traffic data for a number of data streams may be provided from a data source 212 to a transmit (TX) data processor 214.

[0034] In one embodiment, each data stream is transmitted via 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.

[0035] The coded data for each data stream may be multiplexed with pilot data using orthogonal frequency-division multiplexing (OFDM) techniques. The pilot data may typically be 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 may then be modulated (i.e., symbol mapped) based on a particular modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM)) to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230.

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

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

[0038] 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 may be provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 may condition (e.g., filter, amplify, and downconvert) a respective received signal, digitize the conditioned signal to provide samples, and / or further process the samples to provide a corresponding “received” symbol stream.

[0039] RX data processor 260 then extracts the N R The receiver 254 receives and / or processes N R receive symbol streams to provide N T The RX data processor 260 may then demodulate, deinterleave, and / or decode each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 may be complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0040] Processor 270 may periodically determine which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

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

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

[0043] Figure 3 An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown in FIG. , the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in or Figure 1The base station (AN) 100 in the wireless communication system may be an LTE system or 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 may receive a signal input by a user through the input device 302 (for example, a keyboard or a keypad), and may output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to pass the received signal to the control circuit 306 and wirelessly output the signal generated by the control circuit 306. The communication device 300 in the wireless communication system may also be used to implement Figure 1 AN 100 in.

[0044] Figure 4 According to one embodiment of the disclosed subject matter Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 may perform radio resource control. Layer 2 portion 404 may perform link control. Layer 1 portion 406 may perform and / or implement physical connectivity.

[0045] The following quotes the text related to the RRC_INACTIVE state from 3GPP TS 38.300 V16.0.0. It is worth noting that the text in section 9.2.2.4.1 of 3GPP TS 38.300 V16.0.0 entitled "UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED (UE context retrieval successful)" Fig. 9 .2.2.4.1-1 is reproduced in this article as Figure 5 3GPP TS 38.300 V16.0.0, section 9.2.2.4.1 entitled "UE triggered transition from RRC_INACTIVE to RRC_CONNECTED (UE context retrieval failure)" Fig. 9 .2.2.4.1-2 is reproduced in this article as Figure 6 3GPP TS 38.300 V16.0.0, section 9.2.2.4.1, titled "Reject from the network, UE attempts to resume a connection" Fig. 9 .2.2.4.1-3 is reproduced in this article as Figure 7 .

[0046] 9 Mobility and State Migration

[0047] 9.2.2 Mobility in RRC_INACTIVE

[0048] 9.2.2.4 State Migration

[0049] 9.2.2.4.1 UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED

[0050] The following figure describes the UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED in case of successful UE context retrieval:

[0051] Fig. 9 .2.2.4.1-1: UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED

[0052] (UE context retrieval successful)

[0053] 1. The UE recovers from RRC_INACTIVE providing the I-RNTI allocated by the last serving gNB.

[0054] 2. If the gNB identity contained in the I-RNTI can be resolved, the gNB requests the last serving gNB to provide UE context data.

[0055] 3. The last serving gNB provides UE context data.

[0056] 4 / 5.gNB and UE complete the recovery of the RRC connection.

[0057] NOTE: User data may also be sent in step 5 if permission is granted.

[0058] 6. If the loss of DL user data buffered in the last serving gNB is to be prevented, the gNB provides a forwarding address.

[0059] 7 / 8.gNB performs path switching.

[0060] 9. The gNB triggers the release of UE resources at the last serving gNB.

[0061] After step 1 above, when the gNB decides to reject the resume request and keep the UE in RRC_INACTIVE without any reconfiguration (e.g. as described in the two examples below), or when the gNB decides to establish a new RRC connection, SRB0 (without security) may be used. SRB1 (with at least integrity protection) shall be used when the gNB decides to reconfigure the UE (e.g. with a new DRX cycle or RNA) or when the gNB decides to push the UE to RRC_IDLE.

[0062] Note: SRB1 can only be used after the UE context has been retrieved, i.e. after step 3.

[0063] The following diagram describes the UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED in the event of a UE context retrieval failure:

[0064] Fig. 9 .2.2.4.1-2: UE-triggered transition from RRC_INACTIVE to RRC_CONNECTED

[0065] (UE context retrieval failed)

[0066] 1. The UE recovers from RRC_INACTIVE providing the I-RNTI allocated by the last serving gNB.

[0067] 2. If the gNB identity contained in the I-RNTI can be resolved, the gNB requests the last serving gNB to provide UE context data.

[0068] 3. The last serving gNB is unable to retrieve or verify UE context data.

[0069] 4. The last serving gNB indicates the failure to the gNB.

[0070] 5. The gNB performs fallback to establish a new RRC connection by sending RRCSetup.

[0071] 6. Establish a new connection as described in Section 9.2.1.3.1.

[0072] The following diagram illustrates the rejection from the network when the UE attempts to resume the connection from RRC_INACTIVE:

[0073] Fig. 9 .2.2.4.1-3: Rejection from the network: UE attempts to restore the connection

[0074] 1. The UE attempts to recover the connection from RRC_INACTIVE.

[0075] 2. The gNB is unable to process the procedure, e.g. due to congestion.

[0076] 3. The gNB sends RRCReject (with waiting time) to keep the UE in RRC_INACTIVE.

[0077] The following text is quoted from 3GPP TS 38.331 V16.0.0 related to the RRC_INACTIVE state in NR. It is worth noting that in section 4.2.1 of 3GPP TS 38.331 V16.0.0, titled "UE state machine and state transition in NR" Figure 4 .2.1-1 is reproduced in this article as Figure 8 3GPP TS 38.331 V16.0.0, section 5.3.13.1, titled "RRC Connection Recovery: Success" Figure 5 .3.13.1-1 is reproduced in this article as Fig. 9 3GPP TS 38.331 V16.0.0, section 5.3.13.1 entitled "RRC Connection Recovery Fallback to RRC Connection Establishment: Success" Figure 5 .3.13.1-2 is reproduced in this article as Fig.10 3GPP TS 38.331 V16.0.0, section 5.3.13.1 entitled "RRC Connection Resumption followed by Network Release: Success" Figure 5 .3.13.1-3 is reproduced in this article as Fig.11 3GPP TS 38.331 V16.0.0, section 5.3.13.1 entitled "RRC Connection Resumption followed by Network Suspend: Success" Figure 5 .3.13.1-4 is reproduced in this article as Fig.12 3GPP TS 38.331 V16.0.0, section 5.3.13.1 entitled "RRC Connection Recovery: Network Rejection" Figure 5 .3.13.1-5 is reproduced in this article as Fig.13 .

[0078] 4.2.1 UE state and state migration between RATs

[0079] When an RRC connection has been established, the UE is in the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, i.e. no RRC connection has been established, the UE is in the RRC_IDLE state. The RRC state can be further characterized as follows:

[0080] -RRC_IDLE:

[0081] -UE-specific DRX can be configured by upper layers;

[0082] -UE controls mobility based on network configuration;

[0083] -UE:

[0084] - monitor short messages sent via DCI using P-RNTI (see section 6.5);

[0085] -Monitor the paging channel for CN paging using 5G-S-TMSI;

[0086] -Perform neighbor cell measurements and cell selection (reselection);

[0087] - Get system information and may send SI request (if configured).

[0088] - Logging of available measurements is performed along with the location and time of the UE configured via the logged measurements.

[0089] -RRC_INACTIVE:

[0090] -UE-specific DRX can be configured by upper layers or RRC layer;

[0091] -UE controls mobility based on network configuration;

[0092] -UE stores UE inactive AS context;

[0093] -RAN-based notification area is configured by the RRC layer;

[0094] UE:

[0095] - monitor short messages sent via DCI using P-RNTI (see section 6.5);

[0096] -Monitor the paging channel for CN paging using 5G-S-TMSI and RAN paging using fullI-RNTI;

[0097] -Perform neighbor cell measurements and cell selection (reselection);

[0098] -Perform RAN-based notification area updates periodically and upon moving out of a configured RAN-based notification area;

[0099] - Get system information and may send SI request (if configured).

[0100] - Logging of available measurements is performed along with the location and time of the UE configured via the logged measurements.

[0101] -RRC_CONNECTED:

[0102] -UE stores the AS context;

[0103] - Delivery of unicast data to / from UE;

[0104] - At lower layers, the UE may be configured to use UE-specific DRX;

[0105] -For UEs supporting CA, use one or more SCells aggregated with SpCell to increase bandwidth;

[0106] -For UEs supporting DC, use one SCG aggregated with the MCG to increase bandwidth;

[0107] - Network controlled mobility within NR and to / from E-UTRA;

[0108] -UE:

[0109] - If configured, listen to short messages sent via DCI using P-RNTI (see section 6.5);

[0110] - listening to a control channel associated with a shared data channel to determine whether data is scheduled for it;

[0111] -Provide channel quality and feedback information;

[0112] -Perform neighbor cell measurements and measurement reporting;

[0113] -Get system information.

[0114] Figure 4 .2.1-1 shows an overview of the UE RRC state machine and state transitions in NR. A UE has only one RRC state at a time in NR.

[0115] Figure 4 .2.1-1: UE state machine and state transition in NR

[0116] 5.3 Connection Control

[0117] 5.3.13RRC Connection Recovery

[0118] 5.3.13.1 Overview

[0119] Figure 5 .3.13.1-1: RRC connection recovery: Success

[0120] Figure 5 .3.13.1-2: RRC connection recovery fallback to RRC connection establishment: Success

[0121] Figure 5 .3.13.1-3: RRC connection recovery followed by network release: Success

[0122] Figure 5 .3.13.1-4: RRC connection recovery followed by network suspension: Success

[0123] Figure 5 .3.13.1-5: RRC Connection Recovery: Network Rejection

[0124] The purpose of this procedure is to resume a suspended RRC connection, including resuming SRBs and DRBs or performing RNA updates.

[0125] 5.3.13.2 Initiation

[0126] The UE initiates this procedure when upper layers or the AS (in response to RAN paging or after triggering RNA update when the UE is in RRC_INACTIVE) request to resume a suspended RRC connection.

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

[0128] After initiating the described procedure, the UE shall:

[0129] […]

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

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

[0132] 3> Use the access category and access identifier provided by the upper layer to implement the unified access control procedures specified in 5.3.14;

[0133] 4> If the access attempt is prohibited, the procedure ends;

[0134] 2> Set resumeCause based on the information received from the upper layer;

[0135] […]

[0136] 1> If the UE is in NE-DC or NR-DC:

[0137] 2> If the UE does not support maintaining the SCG configuration after the connection is restored:

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

[0139] 1> If the UE does not support maintaining the MCG SCell configuration after connection restoration: 2> If stored, release the MR-DC related configuration from the UE inactive AS context;

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

[0141] 1> Apply the preset SRB1 configuration as specified in 9.2.1;

[0142] 1> As specified in 9.2.2, the preset MAC cell group configuration is applied;

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

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

[0145] 1> if stored, release overheatingAssistanceConfig from the UE inactive AS context;

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

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

[0148] 1> If stored, release the drx-PreferenceConfig from the UE inactive AS context;

[0149] 1> Stop timer T346a (if it is running);

[0150] 1> If stored, release maxBW-PreferenceConfig from the UE inactive AS context;

[0151] 1> Stop timer T346b (if it is running);

[0152] 1> If stored, release maxCC-PreferenceConfig from the UE inactive AS context;

[0153] 1> Stop timer T346c (if it is running);

[0154] 1> If stored, release maxMIMO-LayerPreferenceConfig from the UE inactive AS context;

[0155] 1> Stop timer T346d (if it is running);

[0156] 1> If stored, release minSchedulingOffsetPreferenceConfig from the UE inactive AS context;

[0157] 1> Stop timer T346e (if it is running);

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

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

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

[0161] 1> Apply timeAlignmentTimerCommon contained in SIB1;

[0162] 1>Start timer T319;

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

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

[0165] 5.3.13.3 Actions related to the transmission of RRCResumeRequest or RRCResumeRequest1 message

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

[0167] 1> If the field useFullResumeID is transmitted in SIB1:

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

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

[0170] 1> Otherwise:

[0171] 2>Select RRCResumeRequest as the message to be used;

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

[0173] 1> Restore RRC configuration, RoHC status, stored QoS flow to DRB mapping rules and K from the stored UE inactive AS contextgNB and K RRCint Keys, except as follows;

[0174] -masterCellGroup;

[0175] -mrdc-SecondaryCellGroup (if stored); and

[0176] -pdcp-Config;

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

[0178] 2> via ASN.1 encoding as VarResumeMAC-Input according to section 8 (i.e., a multiple of 8 bits);

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

[0180] 2> All input bits of COUNT, BEARER, and DIRECTION are set to binary 1;

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

[11] ;

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

[0183] 1>Immediately use the configured algorithm and K derived in this section 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;

[0184] Note 1: Only DRBs that were previously configured with UP integrity protection will have integrity protection restored.

[0185] 1> Configure lower layers to apply encryption to all radio bearers except SRB0 and apply the configured encryption algorithm derived in this section, 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;

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

[0187] 1>Restore SRB1;

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

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

[0190] If the lower layer indicates that the integrity check has failed while T319 is in operation, then the actions specified in 5.3.13.5 are performed.

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

[0192] 5.3.13.4UE Reception of RRCResume

[0193] UE will:

[0194] 1> Stop timer T319;

[0195] 1> Stop timer T380 (if it is running);

[0196] 1> If T331 is running:

[0197] 2> Stop timer T331;

[0198] 2> Execute the actions specified in 5.7.8.3;

[0199] 1> If RRCResume contains fullConfig:

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

[0201] 1> Otherwise:

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

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

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

[0205] 3> If the UE is in NE-DC or NR-DC:

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

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

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

[0209] 1>Discard the UE inactive AS context;

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

[0211] 1>If RRCResume contains masterCellGroup:

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

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

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

[0215] 3> According to 5.3.5.3, perform RRC reconfiguration for the RRCReconfiguration message contained in nr-SCG;

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

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

[10] section 5.3.5.3;

[0218] 1> If RRCResume contains radioBearerConfig:

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

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

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

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

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

[0224] 1>Restore SRB2, SRB2 (if configured) and all DRBs;

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

[0226] 1> Stop timer T320 (if it is running);

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

[0228] 2>Execute the measurement configuration procedure as specified in 5.5.2;

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

[0230] 1> If the T390 is in operation:

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

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

[0233] 1> If T302 is in operation:

[0234] 2> Stop timer T302;

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

[0236] 1>Enter RRC_CONNECTED;

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

[0238] 1> Stop the cell reselection procedure;

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

[0240] […]

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

[0242] 1>The program ends.

[0243] 5.3.13.7 UE receives RRCSetup

[0244] UE will:

[0245] 1> Perform the RRC connection setup procedure as specified in 5.3.3.4.

[0246] 5.3.13.9 UE Reception of RRCRelease

[0247] UE will:

[0248] 1>Execute the actions specified in 5.3.8.

[0249] 5.3.13.10 UE Reception of RRCReject

[0250] UE will:

[0251] 1>Execute the actions specified in 5.3.15.

[0252] 6.2.2 Message Definition

[0253] -RRCResume

[0254] The RRCResume message is used to resume a suspended RRC connection.

[0255] Signaling Radio Bearer: SRB1

[0256] RLC-SAP:AM

[0257] Logical channel: DCCH

[0258] Direction: Network to UE

[0259] RRCResume message

[0260]

[0261]

[0262] The following text is quoted from 3GPP TS 38.331 V16.0.0 related to RRC connection release in NR. It is worth noting that in section 5.3.8.1 of 3GPP TS 38.331 V16.0.0, the section titled "RRC connection release: success" Figure 5 .3.8.1-1 is reproduced in this article as Fig.14 .

[0263] 5.3.8RRC Connection Release

[0264] 5.3.8.1 Overview

[0265] Figure 5 .3.8.1-1: RRC connection release: Success

[0266] The purpose of this program is to:

[0267] - Release the RRC connection, which includes the release of established radio bearers and all radio resources; or

[0268] - The RRC connection is suspended only when SRB2 and at least one DRB are set up, which includes suspending the established radio bearers.

[0269] 5.3.8.2 Initiation

[0270] The network initiates the RRC connection release procedure to migrate the UE from the RRC_CONNECTED state to the RRC_IDLE state; or to migrate the UE from the RRC_CONNECTED state to the RRC_INACTIVE state only when SRB2 and at least one DRB are set under RRC_CONNECTED; or to migrate the UE from the RRC_INACTIVE state back to the RRC_INACTIVE state when the UE attempts to recover; or to migrate the UE from the RRC_INACTIVE state to the RRC_IDLE state when the UE attempts to recover. This procedure can also be used to release and redirect the UE to another frequency.

[0271] 5.3.8.3UE Reception of RRCRelease

[0272] UE will:

[0273] 1> Delay the following actions defined in this subsection by 60 milliseconds from the moment the RRCRelease message is received or, optionally, when the lower layer indicates that the receipt of the RRCRelease message has been successfully confirmed (the earlier of the two cases);

[0274] 1> Stop timer T380 (if it is running);

[0275] 1> Stop timer T320 (if it is running);

[0276] 1> Stop timer T316 (if it is running);

[0277] 1> If AS security is not activated:

[0278] 2> Ignore any fields except waitTime contained in the RRCRelease message;

[0279] 2> Perform actions after going to RRC_IDLE as specified in 5.3.11, and the release reason is "other", after which the procedure ends;

[0280] 1> If the RRCRelease message contains redirectedCarrierInfo indicating redirection to eutra:

[0281] 2> If cnType is included:

[0282] 3> After cell selection, indicate the available CN types and received cnType to the upper layer;

[0283] NOTE 1: The handling of the situation where the E-UTRA cell selected after redirection does not support the core network type specified by cnType is UE implementation dependent.

[0284] 2> If voiceFallbackIndication is included:

[0285] 3> Treat RRC connection release as EPS fallback for IMS voice (see TS 23.502

[43] );

[0286] 1> If the RRCRelease message contains cellReselectionPriorities:

[0287] 2>Store the cell reselection priority information provided by cellReselectionPriorities;

[0288] 2> If t320 is included:

[0289] 3>Start timer T320, where the timer value is set according to the value of t320;

[0290] 1> Otherwise:

[0291] 2> Apply the cell reselection priority information broadcast in the system information;

[0292] 1> If deprioritisationReq is included:

[0293] 2> Start or restart timer T325, where the timer value is set to the deprioritisationTimer represented by the signal;

[0294] 2>Store deprioritisationReq until T325 expires;

[0295] 1> If RRCRelease contains measIdleConfig:

[0296] 2> If T331 is running:

[0297] 3> Stop timer T331;

[0298] 3> Execute the actions specified in 5.7.8.3;

[0299] 2>If measIdleConfig is set to settings:

[0300] 3>Store the received measIdleDuration in VarMeasIdleConfig;

[0301] 3>Start timer T331 with value measIdleDuration;

[0302] 3>If measIdleConfig contains measIdleCarrierListNR:

[0303] 4>Store the received measIdleCarrierListNR in VarMeasIdleConfig;

[0304] 3>If measIdleConfig contains measIdleCarrierListEUTRA:

[0305] 4>Store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;

[0306] 3>If measIdleConfig contains validityAreaList:

[0307] 4>Store the received validityAreaList in VarMeasIdleConfig;

[0308] 3> Start executing the idle / inactivity measurements specified in 5.7.8;

[0309] 1> If RRCRelease contains suspendConfig:

[0310] 2>Apply the received suspendConfig;

[0311] 2> Remove all entries in VarConditionalConfig (if they exist);

[0312] 2>For each measId, if the associated reportConfig has reportType set to condTriggerConfig:

[0313] 3>For the associated reportConfigId:

[0314] 4> Remove the entry with matching reportConfigId from reportConfigList in VarMeasConfig;

[0315] 3> If the associated measObjectId is only associated with a reportConfig that has a reportType set to condTriggerConfig:

[0316] 4> Remove the entry with matching measObjectId from measObjectList in VarMeasConfig;

[0317] 3> Remove entries with matching measId from measIdList in VarMeasConfig

[0318] 2> Reset MAC and release the preset MAC cell group configuration (if any);

[0319] 2> Re-establish the RLC entity for SRB1;

[0320] 2> If a RRCRelease message with suspendConfig is received in response to RRCResumeRequest or RRCResumeRequest1:

[0321] 3> Stop timer T319 (if it is running);

[0322] 3> In the stored UE inactive AS context:

[0323] 4>Use the current K gNB and K RRCint Key replacement K gNB and K RRCint Key;

[0324] 4> Replace the C-RNTI with the temporary C-RNTI in the cell where the UE has received the RRCRelease message;

[0325] 4> Replace cellIdentity with the cellIdentity of the cell in which the UE has received the RRCRelease message;

[0326] 4> Replace the physical cell identifier with the physical cell identifier of the cell in which the UE has received the RRCRelease message;

[0327] 2> Otherwise:

[0328] 3>Store the current K in the UE inactive AS context gNB and K RRCint Keys, ROHC state, stored QoS flow to DRB mapping rules, C-RNTI for source PCell, cellIdentity and physical cell identity of source PCell and all other configured parameters except those in ReconfigurationWithSync and servingCellConfigCommonSIB;

[0329] NOTE 2: When the UE enters RRC_INACTIVE, the NR sidelink communication related configuration is not stored as UE inactive AS context.

[0330] 2>Suspend all SRBs and DRBs except SRB0;

[0331] 2> Instruct the lower layers of all DRBs to suspend PDCP;

[0332] 2> If t380 is included:

[0333] 3>Start timer T380, where the timer value is set to t380:

[0334] 2> If the RRCRelease message contains waitTime:

[0335] 3>Start timer T302, where the value is set to waitTime;

[0336] 3> Notify upper layers that access barring is applicable to all access categories except categories "0" and "2".

[0337] 2> If the T390 is in operation:

[0338] 3> For all access categories, stop timer T390;

[0339] 3> Execute the actions specified in 5.3.14.4;

[0340] 2> Indicate to the upper layer the suspension of the RRC connection;

[0341] 2> Enter RRC_INACTIVE and perform cell selection as specified in TS 38.304

[20] ;

[0342] Editor's Note: Whether IAB nodes support inactive mode and, if so, whether they need to release / suspend the BAP entity when migrating to inactive mode is for further study.

[0343] 1> Otherwise

[0344] 2> Perform actions after going to RRC_IDLE as specified in 5.3.11, and the release reason is "other".

[0345] 6.2RRC Message

[0346] -RRCRelease

[0347] The RRCRelease message is used to command the release of the RRC connection or the suspension of the RRC connection.

[0348] Signaling Radio Bearer: SRB1

[0349] RLC-SAP:AM

[0350] Logical channel: DCCH

[0351] Direction: Network to UE

[0352] RRCRelease message

[0353]

[0354]

[0355]

[0356]

[0357]

[0358] The text from RP-193252 related to NR small data transfer in the INACTIVE state is quoted below.

[0359] 3 valid reasons

[0360] NR supports the RRC_INACTIVE state, and UEs with infrequent (periodic and / or aperiodic) data transfers are typically kept in the RRC_INACTIVE state by the network. Prior to Rel-16, the RRC_INACTIVE state did not support data transfers. Therefore, the UE had to restore the connection (i.e., move to the RRC_CONNECTED state) for any DL (MT) and UL (MO) data. Connection establishment and subsequent release to the INACTIVE state occurs for every data transfer, regardless of the size and frequency of the data packets. This results in unnecessary power consumption and signaling overhead.

[0361] Specific examples of smaller and infrequent data traffic include the following use cases:

[0362] -Smartphone App:

[0363] ○Instant messaging service traffic (WhatsApp, QQ, WeChat, etc.)

[0364] ○ Heartbeat / keep-alive traffic from IM / email clients and other applications

[0365] ○Push notifications from various apps

[0366] - Non-smartphone applications:

[0367] ○Traffic from wearable devices (periodic positioning information, etc.)

[0368] ○ Sensors (industrial wireless sensor networks transmit temperature, pressure readings periodically or in an event-triggered manner, etc.)

[0369] ○Smart meters and smart meter networks that send periodic meter readings

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

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

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

[0373] - Overall reduction in signaling overhead

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

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

[0376] 4. Goals

[0377] 4.1 Objectives of SI or core WI or test WI

[0378] This work item enables small data transfer in the RRC_INACTIVE state as follows:

[0379] -For RRC_INACTIVE state:

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

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

[0382] ■ 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]

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

[0384] Note 1: The security aspects of the above solution should be checked using SA3

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

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

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

[0388] No new RRC state should be introduced in this WID. Small data transmission in UL, subsequent small data transmission in UL and DL, and state migration decisions should all be under network control.

[0389] The focus of WID should be on licensed operators and these solutions can be repurposed for NR-U if applicable.

[0390] NOTE 2: Any relevant specification work required in RAN1 to support the above set of objectives should be initiated by RAN2 via LS.

[0391] The following text is quoted from 3GPP TS 38.300 V16.0.0 related to Bandwidth Part (BWP) in NR. It is worth noting that the section 6.10 of 3GPP TS 38.300 V16.0.0 entitled "BA Instance" Figure 6 .10-1 is reproduced in this article as Fig.15 .

[0392] 6.10 Bandwidth Adaptation

[0393] With bandwidth adaptation (BA), the receive and transmit bandwidth of the UE does not have to be as large as the bandwidth of the cell, and can be adjusted: the bandwidth can be commanded to change (e.g., reduced during low activity periods to save power); the location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP), and BA is achieved by configuring the UE with a BWP and telling the UE which of the configured BWPs is the currently active BWP.

[0394] under Figure 6 .10-1 describes the configuration of 3 different BWPs:

[0395] -BWP 1 With 40MHz bandwidth and 15kHz subcarrier spacing;

[0396] -BWP 2 With 10MHz bandwidth and 15kHz subcarrier spacing;

[0397] -BWP 3 It has a 20MHz bandwidth and 60kHz subcarrier spacing.

[0398] Figure 6 .10-1: BA Example

[0399] 7.8 Bandwidth Adaptation

[0400] To enable BA on PCell, the gNB configures the UE with UL and DL BWPs. To enable BA on SCell in case of CA, the gNB configures the UE with at least the DL BWP (i.e., it may not be present in UL). For PCell, the initial BWP is the BWP used for initial access. For SCell, the initial BWP is the BWP that the UE is configured to operate first upon SCell activation.

[0401] In paired spectrum, DL and UL can switch BWPs independently. In unpaired spectrum, DL and UL switch BWPs simultaneously. Switching between configured BWPs is performed by means of RRC signaling, DCI, inactivity timer or after initiating random access. When the inactivity timer is configured for a serving cell, the expiration of the inactivity timer associated with the cell switches the active BWP to the default BWP configured by the network. There can be at most one active BWP per cell, unless the serving cell is configured with SUL, in which case there can be at most one active BWP per UL carrier.

[0402] The text related to Bandwidth Part (BWP) in NR is quoted below from 3GPP TS 38.321 V16.0.0.

[0403] 5.15 Bandwidth Part (BWP) Operation

[0404] 5.15.1 Downlink and Uplink

[0405] In addition to section 12 of TS 38.213 [6], this section also specifies requirements for BWP operation.

[0406] A serving cell can be configured with one or more BWPs, and the maximum number of BWPs per serving cell is specified in TS 38.213 [6].

[0407] In an example, BWP switching for a serving cell is used to simultaneously activate an inactive BWP and deactivate an active BWP. BWP switching may be controlled by a PDCCH indicating a downlink assignment or uplink grant, by a bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself after a random access procedure is initiated or after a consistent LBT failure is detected on the SpCell. After RRC (re)configuration of firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id for the SpCell or activation of the SCell, the DL BWP and / or UL BWP indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively (as specified in TS 38.331 [5]) are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP of a serving cell is indicated by RRC or PDCCH (as specified in TS 38.213 [6]). For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL.

[0408] Entering or leaving the sleep BWP is done by BWP switching. It is controlled by PDCCH per SCell or per sleep SCell group (as specified in TS 38.212 [9]). The sleep SCell group configuration indicated by dormancySCellGroups and the sleep BWP configuration for one SCell indicated by dormantDownlinkBWP-Id are configured by RRC signaling as described in TS38.331 [5]. After receiving a PDCCH indicating leaving the sleep BWP from the SpCell outside the active time, the DL BWP indicated by firstOutsideActiveTimeBWP-Id (as specified in TS 38.331 [5]) is activated. After receiving a PDCCH indicating leaving the sleep BWP from the SpCell within the active time, the DL BWP indicated by firstWithinActiveTimeBWP-Id (as specified in TS38.331 [5]) is activated. Upon receiving a PDCCH indicating entry into a sleep BWP, the DL BWP indicated by dormantDownlinkBWP-Id (as specified in TS 38.331 [5]) is activated. Sleep BWP configuration for SpCell or PUCCH SCell is not supported.

[0409] For each activated serving cell configured with a BWP, the MAC entity shall:

[0410] 1> If the BWP is activated and it is not a sleeping BWP, then:

[0411] 2>Transmitted on UL-SCH on BWP;

[0412] 2> If PRACH opportunity is configured, then transmit on RACH on BWP;

[0413] 2>Monitor PDCCH on BWP;

[0414] 2> Transmit PUCCH on BWP (if configured);

[0415] 2> Report CSI for BWP;

[0416] 2> Transmit SRS on BWP (if configured);

[0417] 2> Receive DL-SCH on BWP;

[0418] 2> (re)initialize any suspended configured uplink grants of configured grant type 1 on the active BWP according to the stored configuration (if any), and starting from symbol 1 according to the rules in section 5.8.2;

[0419] 2> If consistent LBT failover is configured, then:

[0420] 3>Stop lbt-FailureDetectionTimer (if it is running);

[0421] 3> Set LBT_COUNTER to 0;

[0422] 3> Listen for LBT fault indications from lower layers as specified in Section 5.21.2.

[0423] […]

[0424] 1> If BWP is disabled, then:

[0425] 2> Not transmitted on UL-SCH on BWP;

[0426] 2> Not transmitted on RACH on BWP;

[0427] 2>Do not monitor PDCCH on BWP;

[0428] 2> PUCCH is not transmitted on BWP;

[0429] 2> No CSI is reported for BWP;

[0430] 2> Do not transmit SRS on BWP;

[0431] 2> Do not receive DL-SCH on BWP;

[0432] 2> Clear any configured downlink assignments and configured uplink grants of configured grant type 2 on the BWP;

[0433] 2> Suspend any configured uplink grants of configured grant type 1 on inactive BWPs.

[0434] Upon initiating a random access procedure on a serving cell, after selecting a carrier for performing the random access procedure as specified in section 5.1.1, the MAC entity shall, for the selected carrier of this serving cell:

[0435] 1> If the PRACH opportunity is not configured for active UL BWP, then:

[0436] 2> Switch the active UL BWP to the BWP not indicated by initialUplinkBWP;

[0437] 2> If the serving cell is SpCell, then:

[0438] 3> Switch the active DL BWP to the BWP indicated by initialDownlinkBWP.

[0439] 1> Otherwise:

[0440] 2> If the serving cell is SpCell, then:

[0441] 3> If the active DL BWP does not have the same bwp-Id as the active UL BWP, then:

[0442] 4> Switch the active DL BWP to a DL BWP with the same bwp-Id as the active UL BWP.

[0443] 1> Stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell (if running).

[0444] 1> If the serving cell is SCell, then:

[0445] 2> Stop the bwp-InactivityTimer associated with the active DL BWP of SpCell (if running).

[0446] 1> Perform a random access procedure on the active DL BWP of the SpCell and the active UL BWP of this serving cell.

[0447] If the MAC entity receives a PDCCH for BWP switching of a serving cell, the MAC entity shall:

[0448] 1> if there is no ongoing random access procedure associated with this serving cell; or

[0449] 1> If an ongoing random access procedure associated with this serving cell (as specified in sections 5.1.4, 5.1.4a and 5.1.5) is successfully completed after receiving this PDCCH addressed to the C-RNTI, then:

[0450] 2> If it exists, cancel the triggered consistent LBT fault of this serving cell;

[0451] 2> Perform BWP switching to the BWP indicated by PDCCH.

[0452] If the MAC entity receives a PDCCH for BWP switching of a serving cell or a dormant SCell group while a random access procedure associated with the serving cell is ongoing in the MAC entity, it is up to the UE to implement whether to switch the BWP or ignore the PDCCH for BWP switching, except for PDCCH reception for BWP switching addressed to the C-RNTI to successfully complete the random access procedure (as specified in sections 5.1.4, 5.1.4a and 5.1.5), in which case the UE will perform a BWP switch to the BWP indicated by the PDCCH. After receiving a PDCCH for BWP switching other than a successful contention resolution, if the MAC entity decides to perform a BWP switch, the MAC entity shall stop the ongoing random access procedure and initiate the random access procedure after performing the BWP switch; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue the ongoing random access procedure on the serving cell.

[0453] […]

[0454] For each activated serving cell configured with bwp-InactivityTimer, the MAC entity shall:

[0455] 1> if defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id (if configured); or

[0456] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not the BWP indicated by initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id (if configured), then:

[0457] 2> if a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received on an active BWP; or

[0458] 2> If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received for an active BWP; or

[0459] 2> If a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment, then:

[0460] 3> if there is no ongoing random access procedure associated with this serving cell; or

[0461] 3> If an ongoing random access procedure associated with this serving cell (as specified in sections 5.1.4, 5.1.4a and 5.1.5) is successfully completed after receiving this PDCCH addressed to the C-RNTI, then:

[0462] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0463] 2> If the bwp-InactivityTimer associated with the active DL BWP expires, then:

[0464] 3> If defaultDownlinkBWP-Id is configured, then:

[0465] 4> Perform BWP switching to the BWP indicated by defaultDownlinkBWP-Id.

[0466] 3> Otherwise:

[0467] 4>Execute BWP to switch to initialDownlinkBWP.

[0468] Note: If a random access procedure is initiated on an SCell, both the SCell and the SpCell are associated with the random access procedure.

[0469] 1> If PDCCH for BWP switching is received and the MAC entity switches the active DL BWP, then:

[0470] 2> if defaultDownlinkBWP-Id is configured, and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and not indicated by dormantDownlinkBWP-Id (if configured); or

[0471] 2> If defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP that is not indicated by initialDownlinkBWP and not indicated by dormantDownlinkBWP-Id (if configured), then:

[0472] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0473] The text related to Bandwidth Part (BWP) in NR is quoted below from 3GPP TS 38.331 V16.0.0.

[0474] 6.3.2 Radio Resource Control Information Elements

[0475] -CellGroupConfig

[0476] CellGroupConfig is used to configure a Master Cell Group (MCG) or a Secondary Cell Group (SCG). A cell group includes a MAC entity, a set of logical channels with an associated RLC entity, a primary cell (SpCell), and one or more secondary cells (SCells).

[0477] CellGroupConfig Information Element

[0478]

[0479]

[0480] IEServingCellConfig is used to configure (add or modify) a UE with a serving cell, which can be a SpCell or an SCell of an MCG or SCG. Most of the parameters in this document are UE-specific, but some are also cell-specific (e.g., in an additionally configured bandwidth portion). Reconfiguration between PUCCH and PUCCH-free SCells is supported only using SCell release and addition.

[0481] ServingCellConfig Information Elements

[0482]

[0483]

[0484] IEServingCellConfigCommonSIB is used to configure cell-specific parameters of the UE's serving cell in SIB1.

[0485] ServingCellConfigCommonSIB Information Element

[0486]

[0487] IEDownlinkConfigCommonSIB provides common downlink parameters for the cell.

[0488] DownlinkConfigCommonSIB Information Element

[0489]

[0490]

[0491] IE UplinkConfigCommonSIB provides common uplink parameters for the cell.

[0492] UplinkConfigCommonSIB Information Element

[0493]

[0494] The IEBWP is used to configure the common parameters of the bandwidth part as defined in section 4.5 of TS 38.211

[16] and section 12 of TS 38.213

[13] .

[0495] For each serving cell, the network configures at least an initial downlink bandwidth portion and one (if the serving cell is configured with uplink) or two (if supplementary uplink (SUL) is used) initial uplink bandwidth portions. In addition, the network may configure additional uplink and downlink bandwidth portions for the serving cell.

[0496] Uplink and downlink bandwidth portion configuration is divided into common and dedicated parameters.

[0497] BWP Information Elements

[0498]

[0499]

[0500] -BWP-Downlink

[0501] IEBWP-Downlink is used to configure an additional downlink bandwidth portion (not used for the initial BWP).

[0502] BWP-Downlink Information Element

[0503]

[0504]

[0505]

[0506]

[0507] -BWP-DownlinkCommon

[0508] IE BWP-DownlinkCommon is used to configure the common parameters of the downlink BWP. They are "cell-specific" and the network ensures the required alignment with the corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides common parameters via dedicated signaling.

[0509] BWP-DownlinkCommon Information Element

[0510]

[0511]

[0512] IE BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters of the downlink BWP.

[0513] BWP-DownlinkDedicated Information Element

[0514]

[0515] IEBWP-Uplink is used to configure an additional uplink bandwidth portion (not used for the initial BWP).

[0516] BWP-Uplink Information Element

[0517]

[0518]

[0519]

[0520]

[0521] -BWP-UplinkCommon

[0522] IEBWP-UplinkCommon is used to configure the common parameters of the uplink BWP. They are "cell specific" and the network ensures the required alignment with the corresponding parameters of other UEs. Common parameters for the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides common parameters via dedicated signaling.

[0523] BWP-UplinkCommon Information Element

[0524]

[0525]

[0526]

[0527]

[0528] -BWP-UplinkDedicated

[0529] IE BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters of uplink BWP.

[0530] BWP-UplinkDedicated Information Element

[0531]

[0532] For UEs with infrequent data transmission, an RRC_INACTIVE state is introduced. When there is no data transmission, the UE may be in the RRC_INACTIVE state to reduce power consumption (e.g., the radio resource control (RRC) connection associated with the UE may be suspended). When the UE is in the RRC_INACTIVE state, the first gNB (e.g., the current serving gNB, such as the serving gNB currently serving the UE) may store (and / or maintain) the UE context of the UE (e.g., one or more configurations and / or one or more identities of the UE). After data arrives, the UE may resume the RRC connection from the RRC_INACTIVE state, which may be faster than establishing a new RRC connection from the RRC_IDLE state. After resuming the RRC connection (e.g., after successfully completing the random access (RA) procedure to resume the RRC connection), the UE is able to transmit data (e.g., data from the UE's application layer) in the RRC_CONNECTED state. Alternatively and / or in addition, the UE may be able to resume the RRC connection on a second gNB (e.g., a new gNB) that is different from the initial gNB (e.g., the old gNB) in which the RRC connection was suspended (e.g., the initial gNB may be the first gNB). In the event that the UE resumes RRC on the second gNB, the second gNB may attempt to retrieve the UE context from the initial gNB. If the second gNB fails to retrieve the UE context, it may fall back to the RRC connection setup procedure (e.g., establishing a new RRC connection). Further details associated with the RRC_INACTIVE state have been cited above and may be found in 3GPP TS 38.300 V16.0.0 and 3GPP TS 38.331 V16.0.0.

[0533] Although the RRC_INACTIVE state may bring benefits (such as described above), currently the UE may not be able to transmit data (e.g., user plane data) in the RRC_INACTIVE state. That is, the UE may need to enter the RRC_CONNECTED state before transmitting the data. After transmitting the data, the UE may be in the RRC_INACTIVE state again. The above steps (e.g., entering the RRC_CONNECTED state, transmitting data, and / or being in the RRC_INACTIVE state) may be performed for each data transmission, regardless of the amount of data and the frequency of data arrival, which may result in an increase in power consumption and / or signaling overhead.

[0534] To alleviate the problem, a small data transfer (SDT) in the RRC_INACTIVE state may be introduced (e.g., as discussed in RP-193252). The SDT may be intended to enable the UE to transmit data in the RRC_INACTIVE state without entering the RRC_CONNECTED state (and / or to be able to transmit data in the RRC_INACTIVE state before entering the RRC_CONNECTED state). Possible solutions (e.g., enabling the UE to transmit data in the RRC_INACTIVE state without entering the RRC_CONNECTED state and / or before) may be based on a 2-step RA, a 4-step random access channel (RACH), and / or a pre-configured physical uplink shared channel (PUSCH) resource (e.g., similar to a type 1 configured grant in NR and / or a configured grant type 1). The SDT in the RRC_INACTIVE state may be referred to as "SDT in the RRC_INACTIVE state", "SDT procedure", and / or "SDT" (e.g., an RRC connection recovery procedure). For example, when the UE performs a RACH-based 2-step SDT procedure (e.g., a procedure for transmitting data, etc. using a 2-step RACH) in a cell, the UE may include uplink (UL) data and an RRCResumeRequest message in MsgA (e.g., MsgA of the RACH-based 2-step SDT procedure). Alternatively and / or in addition, when the UE performs a RACH-based 4-step SDT procedure (e.g., a procedure for transmitting data, etc. using a 4-step RACH) in a cell, the UE may include UL data and an RRCResumeRequest message in Msg3 (e.g., MsgA of the RACH-based 4-step SDT procedure). For example, when the UE performs a pre-configured PUSCH resource-based SDT procedure (e.g., a procedure for transmitting data, etc. using a pre-configured PUSCH resource) in a cell, the UE may include UL data and an RRCResumeRequest message in a PDU to be transmitted using the pre-configured PUSCH resources. It is possible to introduce a different RRC message (eg, a new RRC message) for the SDT procedure (eg, replacing the RRCResumeRequest message as mentioned above).

[0535] Fig.16An example scenario 1600 is shown in which an SDT is performed in an RRC_INACTIVE state. In the example scenario 1600, data 1606 (e.g., UL data) may arrive after the UE enters 1604 the RRC_INACTIVE state. The UE may perform an SDT procedure. For example, the UE may transmit a transmission 1608 to the gNB including an RRC message (e.g., an RRCResumeRequest message) and / or at least some of the data 1606. Alternatively and / or in addition, the UE may receive a transmission 1612 from the gNB including an RRC message (e.g., an RRCRelease message) and / or downlink (DL) data. The UE may remain 1610 in the RRC_INACTIVE state after performing the SDT procedure (e.g., because no more data is expected to be transmitted).

[0536] Fig.17 An example scenario 1700 is shown in which SDT is performed in the RRC_INACTIVE state. In the example scenario 1700, data 1706 (e.g., UL data) may arrive after the UE enters 1704 the RRC_INACTIVE state. The UE may perform the SDT procedure. For example, the UE may transmit a transmission 1708 including an RRC message (e.g., an RRCResumeRequest message) and / or at least some of the data 1706 to the gNB. Alternatively and / or in addition, the UE may receive a transmission 1712 including an RRC message (e.g., an RRCResume message) and / or DL ​​data from the gNB. For example, the SDT procedure may fall back to RRCResume, e.g., because data (e.g., more data) is expected to be transmitted, and / or the UE may enter 1710 the RRC_CONNECTED state.

[0537] Fig.18 An example scenario 1800 is shown in which an SDT is performed in an RRC_INACTIVE state. In the example scenario 1800, data 1806 (e.g., UL data) may arrive after the UE enters 1804 the RRC_INACTIVE state. The UE may perform an SDT procedure. For example, the UE may transmit a transmission 1808 to the gNB including an RRC message (e.g., an RRCResumeRequest message) and / or at least some of the data 1806. Alternatively and / or in addition, the UE may receive a transmission 1812 from the gNB including an RRC message (e.g., an RRCSetup message). For example, the SDT procedure may fall back to RRCSetup, e.g., because the gNB fails to retrieve a UE context for the UE to perform the SDT procedure, and / or the UE may enter 1810 the RRC_CONNECTED state.

[0538] In some systems, the data transmission of the SDT procedure includes a first UL transmission, followed by a first DL transmission. If there is data that cannot be transmitted and / or received within the first UL transmission and / or the first DL transmission, the network may migrate (e.g., transition) the UE to the RRC_CONNECTED state to transmit and / or receive data. One or more subsequent transmissions may be performed while the UE is still in the RRC_INACTIVE state. In an example, the second UL transmission may be after the first DL transmission, and the UE may remain in RRC_INACTIVE after performing (e.g., transmitting) the second UL transmission (and / or receiving an "ACK" response associated with the second UL transmission from the network). In an example, the second DL transmission may be after the second UL transmission, and the UE may remain in RRC_INACTIVE after performing (e.g., receiving) the second DL transmission (and / or transmitting an "ACK" response associated with the second DL transmission to the network). In some examples, "completion of the SDT procedure" may refer to the last transmission of the one or more subsequent transmissions (e.g., a second UL transmission, a second DL transmission, or another transmission). In some examples, in the case where the second DL transmission is performed, the RRCRelease message may be included in the first DL transmission (rather than, for example, the second DL transmission). Alternatively and / or additionally, in the case where the second DL transmission is performed (e.g., where the second DL transmission may be the last DL transmission in the SDT procedure), the RRCRelease message may be included in the second DL transmission (rather than, for example, the first DL transmission). The one or more subsequent transmissions may be considered part of the SDT procedure.

[0539] In some instances, when the RRC connection of the UE is suspended (e.g., due to receiving an RRCRelease message), the UE may store at least a portion of the current RRC configuration of the UE in a UE inactive access stratum (AS) context, and the UE may switch to an initial bandwidth part (BWP) (e.g., an initial DL BWP and / or an initial UL BWP). In an instance, the initial UL BWP may be a UL BWP used by the UE for initial access (e.g., with a cell). Alternatively and / or in addition, the initial UL BWP may be a UL BWP used by the UE to activate a cell. In an instance, the initial DL BWP may be a DLBWP used by the UE for initial access (e.g., with a cell). Alternatively and / or in addition, the initial DL BWP may be a DL BWP used by the UE to activate a cell. In some instances, after the UE initiates an RRC recovery procedure on a cell (where the cell may be considered a special cell (SpCell) after the RRC connection is successfully recovered) and before the UE transmits an RRCResumeRequest message, the UE may recover a portion of the stored RRC configuration (e.g., the configured current RRC) from the UE inactive AS context, such as specified in section 5.3.13.3 of 3GPP TS 38.331 V16.0.0. An RRC configuration (e.g., one RRC configuration) that may not be recovered before transmitting the RRCResumeRequest message is a "masterCellGroup" that includes the SpCellConfig. Because the dedicated BWP configuration of the SpCell is included in the SpCellConfig, the UE may not be able to transmit an RRCResumeRequest message on a UL BWP other than the initial UL BWP of the cell (e.g., even if the cell is the same as the previous SpCell). In some instances, the previous SpCell may be the UE's most recent SpCell before the UE's RRC connection was suspended and / or before initiating the RRC recovery procedure on the cell. If an RRCResume message is received in response to transmitting an RRCResumeRequest message, the cell may become a SpCell and the UE may recover the masterCellGroup from the UE inactive AS context, as specified in section 5.3.13.4 of 3GPP TS 38.331 V16.0.0. If the current SpCell is the same as the previous SpCell (e.g., the previously stored masterCellGroup may still be employed), the UE may be able to perform the one or more subsequent transmissions on a UL BWP other than the initial UL BWP of the cell.If the current SpCell is different from the previous SpCell (and / or if the network decides to reconfigure the BWP configuration), the network may provide a new masterCellGroup in the RRCResume message, and the UE may be able to perform the one or more subsequent transmissions on an UL BWP other than the initial UL BWP of the cell. Prior to transmitting the RRCResumeRequest message, the UE may not be able to restore the masterCellGroup from the UE Inactive AS Context because the cell on which the UE is resuming (e.g., resuming the RRC Connection) may be different from the previous SpCell (and therefore, the previously stored SpCellConfig may not be applicable to the cell).

[0540] For an SDT procedure based on preconfigured PUSCH resources (e.g., in at least some of the following descriptions, such as in the description of the first concept, the second concept, the third concept, and / or the fourth concept, also referred to as SDT and / or SDT procedure), because the UE can transmit UL data and the RRCResumeRequest message on the initial UL BWP of the cell, the initial UL BWP of the cell may become congested (e.g., if more than a threshold number of UEs are configured to use the SDT procedure based on preconfigured PUSCH resources). For example, the network may not have enough (e.g., sufficient) UL resources to allocate preconfigured PUSCH resources to some UEs, which may cause the UE to have more power consumption (e.g., the UE may need to initiate a RA procedure to transmit UL data). It may also affect other UEs that are performing PUSCH transmission on the initial UL BWP of the cell (e.g., Msg3 transmission and / or MsgA transmission during the RA procedure). Increasing the frequency bandwidth of the initial UL BWP of the cell may not be a preferred solution because not all UEs can support a large UL bandwidth, and / or because a large UL bandwidth may also generate more power consumption.

[0541] One or more techniques are provided herein to address one or more of the aforementioned issues (eg, at least one of the following: the initial UL BWP of the cell becomes congested, there are not enough UL resources for the network to allocate pre-configured PUSCH resources to the UE, the UE has more power consumption, etc.).

[0542] In a first concept, additional UL BWP (eg, in addition to the initial UL BWP) may be used for the SDT procedure.

[0543] In some examples, in order to separate UEs performing SDT from UEs not performing SDT, a UL BWP for SDT may be configured (eg, additionally configured) for a cell.

[0544] The UL BWP of the SDT may have a frequency bandwidth different from the initial UL BWP of the cell. The UL BWP of the SDT may have a frequency position different from the initial UL BWP of the cell (e.g., a different center frequency). Alternatively and / or in addition, the ULBWP of the SDT may have the same frequency position as the initial UL BWP of the cell and / or the same center frequency as the initial UL BWP of the cell. The UL BWP of the SDT may have different basic parameters from the initial UL BWP of the cell. Alternatively and / or in addition, the ULBWP of the SDT may have the same basic parameters as the initial UL BWP of the cell.

[0545] In an example, when (and / or after and / or before) providing the configuration of the preconfigured PUSCH resources, the network may provide (e.g., additionally provide) the configuration of the UL BWP for the SDT. For example, the configuration of the preconfigured PUSCH resources may include the configuration of the UL BWP to be used for the SDT. In some examples, the UE may determine (e.g., calculate) the resource location of the preconfigured PUSCH resources based on the frequency location and / or bandwidth of the UL BWP for the SDT (e.g., rather than determining and / or calculating the resource location based on the frequency location and / or bandwidth of the initial UL BWP).

[0546] In an example, after initiating the SDT procedure based on the pre-configured PUSCH resources (and / or in response to the initiation), the UE may determine (e.g., the UE may check) whether the UL BWP of the SDT is configured for the cell. If the UL BWP of the SDT is configured for the cell, the UE may perform the SDT procedure based on the pre-configured PUSCH resources on the UL BWP of the SDT. If the UL BWP of the SDT is not configured for the cell, the UE may perform the SDT procedure based on the pre-configured PUSCH resources on the initial UL BWP of the cell.

[0547] Alternatively and / or in addition, the SDT procedure based on the pre-configured PUSCH resources may be allowed on the UL BWP of the SDT (e.g., the SDT procedure based on the pre-configured PUSCH resources may be allowed to be performed on the UL BWP of the SDT), and may not be allowed on the initial UL BWP of the cell (e.g., the SDT procedure based on the pre-configured PUSCH resources may not be allowed to be performed on the initial UL BWP of the cell). Therefore, if the UL BWP of the SDT is not configured for the cell, the UE may not be able to perform the SDT procedure.

[0548] In some instances, the UL BWP of the SDT may be configured in the system information of the cell. For example, the UL BWP of the SDT may be configured in a system information block (SIB) (e.g., SIB1), SIB2, and / or another SIB designed for and / or usable for the SDT (e.g., a new SIB). Alternatively and / or in addition, the UL BWP of the SDT may be configured in a dedicated RRC message (e.g., an RRCRelease message) to the UE and stored in the UE inactive AS context. For example, the UE may be configured (to use) the UL BWP of the SDT via a dedicated RRC message received by the UE, and / or the UE may store the UL BWP of the SDT (and / or the configuration of the UL BWP of the SDT) in the UE inactive AS context (e.g., after receiving the dedicated RRC message). The configuration of the UL BWP of the SDT may be applicable to the cell that received the configuration (e.g., the cell that received the dedicated RRC message). The configuration of the UL BWP of the SDT may not be applicable to cells other than the cell that received the configuration.

[0549] Alternatively and / or in addition, the network may provide the configuration of the UL BWP for the SDT for the cell list in a dedicated RRC message to the UE (e.g., in an RRCRelease message). For example, the configuration of the UL BWP for the SDT for the cell list may be used for the cells in the cell list. Thus, the UE is able to use the UL BWP for the SDT (and / or the configuration of the UL BWP for the SDT) when initiating the SDT on a cell (e.g., any one cell) in the cell list. For example, the network may include 3 UL BWPs for the SDT in the configuration and / or there may be 3 cells in the cell list, wherein each UL BWP of the SDT in the configuration (of the 3 UL BWPs for the SDT) corresponds to a cell in the cell list. In an example, a first UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a first cell in a cell list (e.g., the UE may use the first UL BWP of SDT to perform an SDT procedure based on preconfigured PUSCH resources on the first cell), a second UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a second cell in the cell list (e.g., the UE may use the second UL BWP of SDT to perform an SDT procedure based on preconfigured PUSCH resources on the second cell), and / or a third UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a third cell in the cell list (e.g., the UE may use the third UL BWP of SDT to perform an SDT procedure based on preconfigured PUSCH resources on the third cell). The cell list may indicate and / or may include cells belonging to a first RAN notification area (RNA) (e.g., the cell list may indicate and / or may include all cells belonging to the first RNA or some cells belonging to the first RNA). Alternatively and / or in addition, the cell list may include one or more cells belonging to the second RNA. Alternatively and / or in addition, the cell list may not include cells belonging to the second RNA (e.g., the cell list may not include any cells belonging to the second RNA). In some instances, the UE is configured to use the first RNA when the RRC connection is suspended. In some instances, in response to moving outside of the first RNA (e.g., when residing in a cell that does not belong to the first RNA), the UE initiates the RNA update procedure.

[0550] In some instances, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the UL BWP of the SDT is configured in the system information of the cell, then the UE (e.g., the RRC layer of the UE) may consider the UL BWP of the SDT to be configured. Alternatively and / or in addition, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the UL BWP of the SDT is not configured in the system information of the cell, and if the stored UE-inactive AS context includes a configuration of the UL BWP of the SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may restore the configuration of the UL BWP of the SDT from the UE-inactive AS context, and may consider the UL BWP of the SDT to be configured. Alternatively and / or additionally, after initiating the SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the UL BWP for SDT is configured in the system information of the cell, and if the stored UE inactive AS context contains the configuration of the UL BWP for SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the UL BWP for SDT from the UE inactive AS context (e.g., instead of using the configuration configured in the system information of the cell), and the UL BWP for SDT may be considered to be configured. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers that the UL BWP for SDT is not configured, then the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure, and may initiate a conventional RRC recovery procedure.

[0551] The RRC layer of the UE may indicate to a lower layer (e.g., a medium access control (MAC) layer) (e.g., of the UE) that the SDT procedure is to be performed on the UL BWP of the SDT (e.g., if the UL BWP of the SDT is configured in the RRC, such as the UL BWP of the SDT is configured in the RRC layer of the UE). The RRC layer of the UE may configure a lower layer (e.g., a MAC layer) (e.g., of the UE) to use the UL BWP of the SDT (e.g., if the UL BWP of the SDT is configured in the RRC, such as the UL BWP of the SDT is configured in the RRC layer of the UE).

[0552] In some instances, in response to successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) through the RRCRelease message (e.g., at the time of and / or after the last of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after other subsequent transmissions of the SDT procedure that the UE considers to be non-existent, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the UL BWP of the SDT. Alternatively and / or in addition, in response to successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) through the RRCRelease message (e.g., at the time of and / or after the last of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after other subsequent transmissions of the SDT procedure that the UE considers to be non-existent, etc.), if the network provides and / or includes a new configuration of the UL BWP of the SDT in the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may replace the configuration of the UL BWP of the SDT contained in the UE inactive AS context with the new configuration of the UL BWP of the SDT (received via the RRCRelease message). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network does not provide and / or include a new configuration of the ULBWP of the SDT (e.g., in the RRCRelease message) and / or if the network indicates (and / or instructs) to release the configuration of the UL BWP of the SDT via the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the UL BWP of the SDT contained in the UE's inactive AS context.

[0553] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the UL BWP for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the UL BWP for the SDT).

[0554] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP of the SDT.

[0555] After initiating the SDT procedure based on the preconfigured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the UL BWP of the SDT. For example, if the (e.g., UE's) upper layer (e.g., the UE's RRC layer) indicates that the SDT procedure will be performed on the UL BWP of the SDT, then after initiating the SDT procedure based on the preconfigured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the UL BWP of the SDT. Alternatively and / or in addition, if the (e.g., UE's) upper layer (e.g., the UE's RRC layer) configures the MAC (e.g., the MAC layer of the UE) to use the UL BWP of the SDT, then after initiating the SDT procedure based on the preconfigured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the UL BWP of the SDT. Throughout the present disclosure, switching the active UL BWP from a first UL BWP (e.g., an initial UL BWP of a cell) to a second UL BWP (e.g., a UL BWP of an SDT) may correspond to switching from the first UL BWP activity to the second UL BWP activity. For example, before switching the active UL BWP from the first UL BWP to the second UL BWP, the first UL BWP may be the active UL BWP of the UE. After switching the active UL BWP from the first UL BWP to the second UL BWP, the second UL BWP may be the active UL BWP of the UE.

[0556] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) (and / or after successful completion) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell).

[0557] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the UL BWP of the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the ULBWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the MAC layer of the UE) may switch the active ULBWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0558] In a case where the UL BWP of the SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may select (e.g., randomly select) a UL BWP (e.g., one UL BWP) between the UL BWP of the SDT and the initial UL BWP (e.g., the UE may select, e.g., randomly select, the UL BWP of the SDT or the initial UL BWP). In a case where the UL BWP of the SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may prioritize the UL BWP of the SDT over the initial UL BWP (e.g., based on prioritizing the UL BWP of the SDT over the initial UL BWP, the UE may select the UL BWP of the SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the UL BWP of the SDT (e.g., based on prioritizing the initial UL BWP over the UL BWP of the SDT, the UE may select the initial UL BWP instead of the UL BWP of the SDT). In some examples, the prioritization (e.g., the prioritization of the UL BWP of SDT over the initial UL BWP or the prioritization of the initial UL BWP over the UL BWP of SDT) may be based on the UE category of the UE and / or the UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the UL BWP of SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the UL BWP of SDT. In the case where the UL BWP of SDT is configured for a cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may prioritize the initial UL BWP over the UL BWP of SDT (e.g., if the initial UL BWP of the cell is available for the SDT procedure, the UE may select the initial UL BWP). Alternatively and / or additionally, if the initial UL BWP of the cell is not available for the SDT procedure, the UE may select the UL BWP of SDT. In a situation where the UL BWP of SDT is configured for a cell and the initial UL BWP of the cell can also be used for the SDT procedure (for example, where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may select the UL BWP of SDT and the UL BWP (for example, one UL BWP) among the initial UL BWP (for example, the UE may select the UL BWP of SDT or the initial UL BWP based on an indication (for example, the network may instruct and / or instruct the UE to perform the SDT procedure using the UL BWP of SDT or the initial UL BWP) (for example, the UE may select the UL BWP of SDT or the initial UL BWP based on the indication).For example, if the indication indicates that the SDT procedure is performed using the UL BWP of the SDT, the UE may select the UL BWP of the SDT. Alternatively and / or additionally, if the indication indicates that the SDT procedure is performed using the initial UL BWP, the UE may select the initial UL BWP. The indication may be included in a dedicated RRC message transmitted to the UE (e.g., the indication may be included in an RRCRelease message). If the UE selects the UL BWP of the SDT, the UE may perform the SDT procedure using the UL BWP of the SDT. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0559] Fig.19 An example scenario associated with the UE's execution of an SDT procedure is shown. The UE may receive a first RRCRelease message 1900 indicating a BWP for the SDT. The UE may use an initial BWP (e.g., a BWP different from the SDT) between the receipt of the first RRCRelease message 1900 and the initiation 1910 of an SDT procedure (e.g., an SDT procedure based on preconfigured PUSCH resources, such as a configured grant SDT (CG-SDT) procedure). The UE may use the BWP for the SDT between the initiation 1910 of the SDT procedure and the completion of the SDT procedure (e.g., the SDT procedure may be completed by receiving a second RRCRelease message 1906). In some instances, the UE may perform (e.g., transmit and / or receive) a first transmission 1902 and / or one or more subsequent transmissions 1904 during the SDT procedure.

[0560] In the second concept, a set of UL BWPs may be used for the SDT procedure.

[0561] In some instances, in order to separate UEs performing SDT (e.g., to divide the UEs into multiple groups), a set of UL BWPs for SDT may be configured for a cell. The set of UL BWPs for SDT may include the UL BWP of the SDT (e.g., at least one UL BWP of the SDT). If more than one UL BWP of the SDT is configured (e.g., if the set of UL BWPs configured for SDT for the cell includes more than one UL BWP of the SDT), the UE may perform selection of a UL BWP (e.g., one UL BWP) from the set of UL BWPs for SDT. Alternatively and / or additionally, if only one UL BWP of the SDT is configured (e.g., if the set of BWPs configured for SDT for the cell includes only one UL BWP of the SDT), the UE may perform selection of the one UL BWP of the SDT.

[0562] In some examples, the UL BWP of the SDT in the set of UL BWPs of the SDT may have a frequency bandwidth different from the initial UL BWP of the cell. Alternatively and / or additionally, the UL BWP of the SDT may have a frequency location different from the initial UL BWP of the cell (e.g., a different center frequency). Alternatively and / or additionally, the UL BWP of the SDT may have a basic parameter different from the initial UL BWP of the cell.

[0563] In an example, when (and / or after and / or before) providing the configuration of the preconfigured PUSCH resources, the network may provide (e.g., additionally provide) the configuration of the set of UL BWPs for the SDT. For example, the configuration of the preconfigured PUSCH resources may include the configuration of the set of UL BWPs to be used for the SDT. In some examples, the UE may determine (e.g., calculate) the resource location of the preconfigured PUSCH resources based on the frequency location and / or bandwidth of the UL BWP of the SDT in the set of UL BWPs for the SDT (e.g., instead of determining and / or calculating the resource location based on the frequency location and / or bandwidth of the initial UL BWP).

[0564] In an example, after initiating the SDT procedure based on the pre-configured PUSCH resources (and / or in response to the initiation), the UE may determine (e.g., the UE may check) whether the set of UL BWPs for the SDT is configured for the cell. If the set of UL BWPs for the SDT is configured for the cell, the UE may perform the SDT procedure based on the pre-configured PUSCH resources on the selected UL BWP for the SDT (e.g., after performing the selection of the selected UL BWP from the set of UL BWPs for the SDT). If the set of UL BWPs for the SDT is not configured for the cell, the UE may perform the SDT procedure based on the pre-configured PUSCH resources on the initial UL BWP for the cell.

[0565] Alternatively and / or in addition, the SDT procedure based on the preconfigured PUSCH resources may be allowed on the set of UL BWPs for SDT (e.g., the SDT procedure based on the preconfigured PUSCH resources may be allowed to be performed on a UL BWP in the set of UL BWPs for SDT), and may not be allowed on the initial UL BWP of the cell (e.g., the SDT procedure based on the preconfigured PUSCH resources may not be allowed to be performed on the initial UL BWP of the cell). Therefore, if the set of UL BWPs for SDT is not configured for the cell, the UE may not be able to perform the SDT procedure.

[0566] In some instances, the set of UL BWPs for the SDT may be configured in the system information of the cell. For example, the set of UL BWPs for the SDT may be configured in SIB1, SIB2, and / or another SIB designed for and / or available for the SDT (e.g., a new SIB). Alternatively and / or in addition, the set of UL BWPs for the SDT may be configured in a dedicated RRC message (e.g., an RRCRelease message) to the UE and stored in the UE inactive AS context. For example, the UE may be configured (to use) the set of UL BWPs for the SDT via a dedicated RRC message received by the UE, and / or the UE may store the set of UL BWPs for the SDT (and / or the configuration of the set of UL BWPs for the SDT) in the UE inactive AS context (e.g., after receiving the dedicated RRC message). The configuration of the set of UL BWPs for the SDT may be used for the cell that received the configuration (e.g., the cell that received the dedicated RRC message). The configuration of the set of UL BWPs for the SDT may not be applicable to cells other than the cell that received the configuration.

[0567] Alternatively and / or in addition, the network may provide the configuration of the set of UL BWPs for the SDT for the cell list in a dedicated RRC message to the UE (e.g., in an RRCRelease message). For example, the configuration of the UL BWPs for the SDT for the cell list may be used for the cells in the cell list. Thus, the UE is able to use the UL BWPs among the set of UL BWPs for the SDT when initiating the SDT on a cell (e.g., any one cell) among the cell list. In an example, the network may include 5 UL BWPs for the SDT in the configuration and / or there may be 3 cells in the cell list, wherein the first UL BWP and the second UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the first cell in the cell list, wherein the third UL BWP and the fourth UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the second cell in the cell list, and wherein the fifth UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the third cell in the cell list. The cell list may indicate and / or may include cells belonging to the first RNA (e.g., the cell list may indicate and / or may include all cells belonging to the first RNA or some cells belonging to the first RNA). Alternatively and / or in addition, the cell list may include one or more cells belonging to the second RNA. Alternatively and / or in addition, the cell list may not include cells belonging to the second RNA (e.g., the cell list may not include any cells belonging to the second RNA). In some instances, the UE is configured to use the first RNA when the RRC connection is suspended. In some instances, in response to moving outside the first RNA (e.g., when residing in a cell that does not belong to the first RNA), the UE initiates an RNA update procedure.

[0568] In some instances, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the set of UL BWPs for the SDT is configured in the system information of the cell, then the UE (e.g., the RRC layer of the UE) may consider the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) to be configured. Alternatively and / or in addition, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the set of UL BWPs for the SDT is not configured in the system information of the cell, and if the stored UE-inactive AS context includes a configuration of the set of UL BWPs for the SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may restore the configuration of the set of UL BWPs for the SDT from the UE-inactive AS context, and may consider the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) to be configured. Alternatively and / or additionally, after initiating the SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the set of UL BWPs for SDT is configured in the system information of the cell, and if the stored UE inactive AS context contains the configuration of the set of UL BWPs for SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the set of UL BWPs for SDT from the UE inactive AS context (e.g., instead of using the configuration configured in the system information of the cell), and may consider the UL BWP for SDT (and / or the set of UL BWPs for SDT) to be configured. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers the ULBWP for SDT (and / or the set of UL BWPs for SDT) to be not configured, then the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure, and may initiate a conventional RRC recovery procedure.

[0569] The UE may perform selecting a UL BWP (eg, one UL BWP) from the set of UL BWPs for the SDT on the cell using one or more selection techniques (eg, in a case where the set of UL BWPs for the SDT includes more than one UL BWP for the SDT).

[0570] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on random selection.

[0571] In an example, when the UE initiates SDT on the cell (and / or after initiating SDT on the cell and / or in response to the initiation), the UE may randomly select a UL BWP from the set of UL BWPs for the SDT. For example, each time the UE initiates SDT on the cell, the UE randomly selects a UL BWP from the set of UL BWPs for the SDT (e.g., when the UE initiates SDT on the cell and / or after initiating SDT on the cell and / or in response to the initiation, the UE may randomly select a UL BWP).

[0572] In an example where the UE selects a UL BWP from the set of UL BWPs of the SDT based on random selection, the probability of selecting each UL BWP in the set of UL BWPs may be the same. For example, if there are two UL BWPs in the set of UL BWPs of the SDT, the probability of selecting a first UL BWP of the two UL BWPs may be 50%, and the probability of selecting a second UL BWP of the two UL BWPs may be 50%.

[0573] Alternatively and / or additionally, in an example where the UE selects a UL BWP from the set of UL BWPs of the SDT based on random selection, the probability of selecting the UL BWP from the set of UL BWPs may be configurable. For example, the network may configure the probability (with which the UE is configured) in the configuration of the set of UL BWPs (e.g., the probability may be included in the configuration). The UE may perform the selection based on the probability (used to configure the UE). In an example, the probability of selecting a first UL BWP from the set of UL BWPs may be a first configured probability, the probability of selecting a second UL BWP from the set of UL BWPs may be a second configured probability, and so on.

[0574] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on a UE identification of the UE.

[0575] In an example, when the UE initiates SDT on the cell (and / or after initiating SDT on the cell and / or in response to the initiation), the UE may select the UL BWP from the set of UL BWPs for the SDT based on the UE identity and / or a formula. For example, each time the UE initiates SDT on the cell, the UE may select the UL BWP from the set of UL BWPs for the SDT based on the UE identity and / or a formula (for example, when the UE initiates SDT on the cell and / or after initiating SDT on the cell and / or in response to the initiation, the UE may randomly select the UL BWP).

[0576] In an example, the UE may perform one or more operations (e.g., mathematical operations) to select a UL BWP from the set of UL BWPs of the SDT using the UE identity (e.g., the one or more operations may be performed according to a formula). In an example, the formula may be XmodY, where X is the UE identity, mod is a modulo operation, and / or Y is the number of UL BWPs in the set of UL BWPs of the SDT. The UE may determine a result of the formula, and / or the UE may select a UL BWP from the set of UL BWPs of the SDT based on the result. In an example, a result of 0 may correspond to a first UL BWP in the set of UL BWPs, a result of 1 may correspond to a second UL BWP in the set of UL BWPs, a result of 2 may correspond to a third UL BWP in the set of UL BWPs, and so on. In an example where the UE identity of the UE is 10 and the number of UL BWPs in the set of UL BWPs of the SDT is 3, the UE may determine that the result is 10mod3=1, and / or may select the second UL BWP from the set of UL BWPs of the SDT based on the result being 1.

[0577] The UE identifier may be an inactive-radio network temporary identifier (I-RNTI) assigned to the UE in the RRCRelease message. Alternatively and / or in addition, the UE identifier may be a different identifier other than the I-RNTI, such as an identifier designed and / or usable for the SDT procedure, wherein the different identifier may be assigned to the UE in the RRCRelease message.

[0578] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on an indication (eg, an indication from the network).

[0579] In an example, the network may indicate a UL BWP among the set of UL BWPs for SDT that should be provided to the UE for SDT (eg, the network may indicate which UL BWP among the set of UL BWPs for SDT should be provided to the UE for use).

[0580] For example, the network may provide an indication (e.g., a value, such as an integer) in a dedicated RRC message to the UE (e.g., in an RRCRelease message). The UE may perform an SDT procedure on the UL BWP of the cell based on the indication (e.g., the indication may indicate the UL BWP). The indication may be per cell (e.g., the network may provide multiple indications for a cell list, wherein each of the multiple indications indicates the UL BWP of a cell in the cell list). Alternatively and / or in addition, the indication may be common to multiple cells (e.g., the network may provide a single indication for a cell list).

[0581] In some instances, the SDT procedure may be triggered by the network via paging (e.g., due to the arrival of DL data at the network side). For example, the network may transmit a paging message (associated with triggering the SDT procedure) to the UE. The paging message transmitted to the UE may include a first indication (e.g., a flag) indicating the initiation of the SDT procedure. The paging message transmitted to the UE may include a second indication (e.g., a value, such as an integer) indicating which UL BWP (e.g., of the set of UL BWPs) the UE should use for SDT. The first indication and the second indication may be the same indication (e.g., the presence of the indication may indicate the initiation of the SDT procedure and / or the value of the indication may indicate the UL BWP to be used). In response to receiving the paging message on the cell, the UE performs the SDT procedure on the indicated UL BWP of the cell based on the first indication and / or the second indication.

[0582] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on radio conditions and / or channel conditions of the UL BWP.

[0583] For example, each UL BWP in the set of UL BWPs of the SDT may be associated with one or more DL reference signals (e.g., the one or more DL reference signals may be received in a DL BWP paired with the UL BWP). For example, a first UL BWP in the set of UL BWPs of the SDT may be associated with one or more first DL reference signals, a second UL BWP in the set of UL BWPs of the SDT may be associated with one or more second DL reference signals, and so on, and the UE may select the UL BWP in the set of UL BWPs of the SDT based on measurements of the DL reference signals associated with the set of UL BWPs of the SDT. For example, the UE may select the UL BWP in the set of UL BWPs of the SDT based on determining that the UL BWP has the best reference signal quality among the set of UL BWPs (e.g., determining that the UL BWP has the best reference signal quality among the set of UL BWPs may be based on measurements of the DL reference signals associated with the set of UL BWPs of the SDT).

[0584] Alternatively and / or additionally, the UE may perform "listen before talk" on each UL BWP among the set of UL BWPs of the SDT. The UE may not select an occupied UL BWP (e.g., occupied due to another UE using the UL BWP and / or due to strong interference in the UL BWP), wherein whether the UL BWP is occupied may be determined by performing "listen before talk" on the UL BWP. The UE may select an unoccupied UL BWP, wherein whether the UL BWP is occupied may be determined by performing "listen before talk" on the UL BWP. Alternatively and / or additionally, the UE may select the UL BWP with the lowest noise and / or lowest interference among the set of UL BWPs, wherein the UE may determine that the UL BWP has the lowest noise and / or lowest interference among the set of UL BWPs by performing "listen before talk" on each UL BWP among the set of UL BWPs of the SDT.

[0585] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on the UL data size (eg, the amount of UL data to be transmitted via the SDT procedure).

[0586] For example, each UL BWP in the set of UL BWPs of the SDT may be associated with a transport block size (TBS) (e.g., the transport block size may be configurable). In an example, a first UL BWP in the set of UL BWPs of the SDT may be associated with a first transport block size, a second UL BWP in the set of UL BWPs of the SDT may be associated with a second transport block size, and so on. The UE may select the UL BWP based on the UL data size (e.g., the amount of UL data to be transmitted). Alternatively and / or additionally, the UE may select the UL BWP based on the total data amount (e.g., the total data amount may correspond to the data size of the UL data size plus the size of the RRC message and / or MAC subheader). In an instance where the total amount of data is 100 kilobytes (KB), a first UL BWP among the set of UL BWPs of the SDT is associated with a transport block size of 70KB, and a second UL BWP among the set of UL BWPs of the SDT is associated with a transport block size of 120KB, the UE may select the second UL BWP based on determining that the second UL BWP is capable of transmitting all UL data without introducing a threshold number of padding bits (and / or the UE may select the second UL BWP based on determining that the transport block size of the second UL BWP exceeds the total amount of data and / or the difference between the transport block size of the second UL BWP and the total amount of data is less than a threshold).

[0587] The RRC layer of the UE may indicate to the lower layer (e.g., the MAC layer) (e.g., the UE) that the SDT procedure will be performed on the UL BWP of the SDT (e.g., the selected UL BWP of the SDT) in the set of UL BWPs of the SDT (e.g., if the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC, such as the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC layer of the UE). The RRC layer of the UE may configure the lower layer (e.g., the MAC layer) (e.g., the UE) to use the UL BWP of the SDT (e.g., if the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC, such as the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC layer of the UE).

[0588] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via an RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT. Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network provides and / or includes a new configuration of the set of UL BWPs for the SDT in the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may replace the configuration of the set of UL BWPs for the SDT contained in the UE's inactive AS context with the new configuration of the set of UL BWPs for the SDT (received via the RRCRelease message). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network does not provide and / or include a new configuration of the set of UL BWPs for the SDT (e.g., in the RRCRelease message) and / or if the network indicates (and / or instructs) to release the configuration of the set of UL BWPs for the SDT via the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the set of UL BWPs for the SDT contained in the UE's inactive AS context.

[0589] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, and / or after that, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the set of UL BWPs for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the set of UL BWPs for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in the masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the set of UL BWPs for the SDT).Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the set of UL BWPs for the SDT).

[0590] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for SDT. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for SDT.

[0591] After initiating the SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the UE's active UL BWP (e.g., from the initial UL BWP) to the selected UL BWP of the SDT (e.g., the UL BWP is selected from the set of UL BWPs of the SDT). For example, if an upper layer (e.g., an RRC layer of the UE) indicates that the SDT procedure is to be performed on the selected UL BWP of the SDT, then after initiating the SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the UE's active UL BWP to the selected UL BWP of the SDT. Alternatively and / or in addition, if an upper layer (e.g., the UE's) (e.g., the UE's RRC layer) configures the MAC (e.g., the UE's MAC layer) to use a selected UL BWP for SDT, then after initiating an SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the UE's MAC layer) may switch the UE's active UL BWP (e.g., from an initial UL BWP) to the selected UL BWP for SDT.

[0592] In some instances, after successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (and / or in response to the successful completion) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell).

[0593] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the selected UL BWP of the SDT (e.g., if a new BWP configuration is not provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the selected UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message, the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0594] In the case where the set of UL BWPs for SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources for the SDT are configured on the initial UL BWP), the UE may perform a selection (e.g., selecting a UL BWP from a second set of UL BWPs) using one or more of the techniques discussed herein for selecting a UL BWP from the set of UL BWPs for SDT (e.g., based on random selection, UE identity of the UE, indication from the network, radio conditions, channel conditions, listen-before-talk, and / or UL data size), wherein the initial UL BWP may be considered (e.g., by the UE) to be included in the second set of UL BWPs from which the selected UL BWP is selected (e.g., the initial UL BWP may be considered to be a UL BWP included in the second set of UL BWPs). For example, the second set of UL BWPs may include the set of UL BWPs for SDT and the initial UL BWP. In an example, the initial UL BWP may be considered to be the first UL BWP in the second set of UL BWPs (e.g., subsequent to the first UL BWP). In a situation where the set of UL BWPs for SDT is configured for a cell and an initial UL BWP of the cell may also be used for the SDT procedure (e.g., where the preconfigured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may prioritize the set of UL BWPs for SDT over the initial UL BWP (e.g., based on prioritizing the set of UL BWPs for SDT over the initial UL BWP, the UE may select a UL BWP in the set of UL BWPs for SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT (e.g., based on prioritizing the initial UL BWP over the set of UL BWPs for SDT, the UE may select the initial UL BWP instead of the UL BWP in the set of UL BWPs for SDT). In some instances, the priority ranking (e.g., the priority ranking of the set of UL BWPs for SDT over the initial UL BWP or the priority ranking of the initial UL BWP over the set of UL BWPs for SDT) may be based on a UE category of the UE and / or a UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the set of UL BWPs for SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT.In the case where the set of UL BWPs for SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT (e.g., if the initial UL BWP of the cell is available for the SDT procedure, the UE may select the initial UL BWP). Alternatively and / or additionally, if the initial UL BWP of the cell is not available for the SDT procedure, the UE may select the UL BWP from the set of UL BWPs for SDT. If the UE selects the UL BWP of the SDT from the set of UL BWPs for SDT, the UE may perform the SDT procedure using the UL BWP of the SDT. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0595] In the third concept, one or more dedicated UL BWPs in RRC_CONNECTED may be used for the SDT procedure.

[0596] In some instances, when the UE is in the RRC_CONNECTED state, the network configures the UE with a UL BWP (e.g., referred to as a dedicated UL BWP) for use in the RRC_CONNECTED state. For example, the network may configure the UE to use the dedicated UL BWP by providing the UE with a configuration of the dedicated UL BWP. In some instances, the configuration of the dedicated UL BWP includes pre-configured PUSCH resources for SDT. After initiating the SDT procedure (and / or in response to the initiation), if the dedicated UL BWP is available for the cell (e.g., the cell may be the same as the previous SpCell), the UE may restore the configuration of the dedicated UL BWP from the UE inactive AS context, and the UE may perform the SDT procedure using the dedicated UL BWP (e.g., if the dedicated UL BWP is available for the cell).

[0597] In some instances, when the UE is in the RRC_CONNECTED state, the network configures a set of dedicated UL BWPs for use in the RRC_CONNECTED state to the UE. For example, the network may configure the UE to use the set of dedicated UL BWPs by providing one or more configurations of the set of dedicated UL BWPs to the UE. In some instances, the configuration (e.g., of the one or more configurations) of each dedicated UL BWP in the set of dedicated UL BWPs includes pre-configured PUSCH resources for the SDT. For example, a first configuration of a first dedicated UL BWP in the set of dedicated UL BWPs may include a first pre-configured PUSCH resource for the SDT, a second configuration of a second dedicated UL BWP in the set of dedicated UL BWPs may include a second pre-configured PUSCH resource for the SDT, and so on. After initiating the SDT procedure (and / or in response to the initiation), if the set of dedicated UL BWPs is available for the cell (e.g., the cell may be the same as the previous SpCell), the UE may recover each of the one or more configurations (e.g., the configuration of each dedicated UL BWP among the set of dedicated UL BWPs) from the UE inactive AS context, and the UE may select a dedicated UL BWP (e.g., one dedicated UL BWP) from the set of dedicated UL BWPs to perform the SDT procedure (e.g., if the set of dedicated UL BWPs is available for the cell).

[0598] In some instances, when the UE is in the RRC_CONNECTED state, the network configures the UE with a dedicated UL BWP (and / or a set of dedicated UL BWPs) for use in the RRC_CONNECTED state (e.g., when the UE is in the RRC_CONNECTED state, the network configures the UE with a dedicated UL BWP (and / or the set of dedicated UL BWPs) for use in the RRC_CONNECTED state). Alternatively and / or in addition, before or after the UE enters the RRC_INACTIVE state (and / or in response to the entry), the network indicates (e.g., to the UE) the dedicated UL BWP that the UE should use to perform the SDT procedure (e.g., the network may instruct the UE to perform the SDT procedure using the dedicated UL BWP). In an instance, the indication of the dedicated UL BWP may be included in the configuration of the pre-configured PUSCH resources (e.g., the UE may be configured to use the pre-configured PUSCH resources via configuration). Alternatively and / or in addition, the indication of the dedicated UL BWP may be included in a RRCRelease message transmitted to the UE or in a different transmission transmitted to the UE.

[0599] In at least some of the descriptions below, "dedicated UL BWP" may be a UL BWP that is used in the RRC_CONNECTED state (e.g., for a UE) and that can be used for SDT in the RRC_INACTIVE state (e.g., the pre-configured PUSCH resources for SDT are configured for the dedicated UL BWP and / or the pre-configured PUSCH resources for SDT can be used on the dedicated UL BWP).

[0600] For example, the UE may be configured to use one or more dedicated UL BWPs (e.g., when the UE is in RRC_CONNECTED state) and / or the UE may use the one or more dedicated UL BWPs in the RRC_CONNECTED state, wherein the one or more dedicated UL BWPs may be used for SDT in the RRC_INACTIVE state (e.g., by the UE) (e.g., one or more preconfigured PUSCH resources for SDT may be configured for use with the one or more dedicated UL BWPs and / or one or more preconfigured PUSCH resources for SDT may be used on the one or more dedicated UL BWPs).

[0601] In some instances, the UE may prioritize the one or more dedicated UL BWPs used in the RRC_CONNECTED state over the UL BWP for SDT (and / or a set of UL BWPs for SDT) configured in the system information. For example, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the UL BWP for SDT (and / or the set of UL BWPs for SDT) is configured in the system information of the cell, and if the stored UE inactive AS context includes the configuration of the one or more dedicated UL BWPs that can be used for the cell, then the UE (e.g., the RRC layer of the UE) may restore the configuration of the one or more dedicated UL BWPs from the UE inactive AS context, and the UL BWP for SDT (and / or the set of UL BWPs for SDT) may be considered to be configured.

[0602] In some instances, the UE may prioritize the UL BWP for the SDT (and / or a set of UL BWPs for the SDT) received in the RRCRelease message over the one or more dedicated UL BWPs used in the RRC_CONNECTED state. For example, after initiating an SDT procedure based on pre-configured PUSCH resources (and / or in response to the initiation), if the stored UE inactive AS context includes a configuration of the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) that can be used for a cell (e.g., the cell can be the same as the previous SpCell and / or the cell can be in the cell list, such as discussed above), and if the stored UE inactive AS context includes a configuration of the one or more dedicated UL BWPs that can be used for the cell, then the UE (e.g., the RRC layer of the UE) may restore the configuration of the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) from the UE inactive AS context (e.g., instead of restoring the configuration of the one or more dedicated UL BWPs), and the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) may be considered to be configured. Alternatively and / or additionally, the UE may consider the one or more dedicated UL BWPs used in the RRC_CONNECTED state as part of the set of UL BWPs for SDT. For example, if there is one dedicated UL BWP and two UL BWPs for SDT in the stored UE inactive AS context, the UE may consider that there are three UL BWPs in the set of UL BWPs for SDT. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers that the UL BWP for SDT (and / or the set of UL BWPs for SDT) is not configured, the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure and may initiate a conventional RRC recovery procedure.

[0603] In some instances, if multiple UL BWPs for the SDT are configured (e.g., if the UE is configured to use more than one UL BWP for the SDT), for example, counting one or more dedicated UL BWPs for the SDT used in the RRC_CONNECTED state and / or counting the UL BWPs (and / or a set of UL BWPs) for the SDT configured in the system information and / or received in the RRCRelease message, then the UE may select the ULBWP for the SDT on the cell from the multiple UL BWPs (and / or from the set of UL BWPs for the SDT) (e.g., the UL BWP may be selected using one or more of the techniques discussed herein for selecting a UL BWP from a set of UL BWPs for the SDT, such as based on random selection, a UE identity of the UE, an indication from the network, radio conditions, channel conditions, listen-before-talk, and / or UL data size).

[0604] In some instances, the UE may be configured to use one or more dedicated UL BWPs (e.g., when the UE is in an RRC_CONNECTED state) and / or the UE may use the one or more dedicated UL BWPs in the RRC_CONNECTED state, wherein the one or more dedicated UL BWPs may be used for SDT in the RRC_INACTIVE state (e.g., by the UE) (e.g., one or more preconfigured PUSCH resources for SDT may be configured for use with the one or more dedicated UL BWPs and / or one or more preconfigured PUSCH resources for SDT may be used on the one or more dedicated UL BWPs).

[0605] The RRC layer of the UE may indicate to the lower layers (e.g., the MAC layer) (e.g., the UE) that the SDT procedure is to be performed on the one or more dedicated UL BWPs of the SDT. For example, if the one or more dedicated UL BWPs are configured in the RRC (e.g., if the one or more dedicated UL BWPs are configured in the RRC layer of the UE), then the RRC layer of the UE may indicate to the lower layers that the SDT procedure is to be performed on the one or more dedicated UL BWPs. The RRC layer of the UE may configure the lower layers (e.g., the MAC layer) (e.g., the UE) to use the one or more dedicated UL BWPs (e.g., if the one or more dedicated UL BWPs are configured in the RRC, such as the one or more dedicated UL BWPs are configured in the RRC layer of the UE).

[0606] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via an RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs of the SDT.

[0607] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the one or more dedicated UL BWPs). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the one or more dedicated UL BWPs). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the one or more dedicated UL BWPs for the SDT).Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the one or more dedicated UL BWPs for the SDT).

[0608] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs.

[0609] After initiating the SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the UE's active UL BWP (e.g., from the initial UL BWP) to the dedicated UL BWP for SDT (e.g., the dedicated UL BWP for SDT among the one or more dedicated UL BWPs for SDT). For example, if an upper layer (e.g., an RRC layer of the UE) indicates that the SDT procedure is to be performed on the dedicated UL BWP for SDT, then after initiating the SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the UE's active UL BWP to the dedicated UL BWP for SDT. Alternatively and / or in addition, if an upper layer (e.g., the UE's) (e.g., the UE's RRC layer) configures the MAC (e.g., the UE's MAC layer) to use a dedicated UL BWP for SDT, then after initiating an SDT procedure based on pre-configured PUSCH resources on the cell (and / or in response to the initiation), the UE (e.g., the UE's MAC layer) may switch the UE's active UL BWP (e.g., from an initial UL BWP) to a dedicated UL BWP for SDT.

[0610] In some instances, after successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (and / or in response to the successful completion) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the dedicated UL BWP of the SDT to the initial active UL BWP of the cell).

[0611] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the dedicated UL BWP for SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the dedicated UL BWP for SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the dedicated UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message, the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from a dedicated UL BWP for SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0612] In a scenario where the one or more dedicated UL BWPs of SDT are configured for a cell and the initial UL BWP of the cell can also be used for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may select (e.g., randomly select) a UL BWP (e.g., one UL BWP) among the one or more dedicated UL BWPs and the initial UL BWP (e.g., the UE may select, e.g., randomly select, a dedicated UL BWP or the initial UL BWP among the one or more dedicated UL BWPs). In the case where the one or more dedicated UL BWPs of the SDT are configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the pre-configured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may prioritize the one or more dedicated UL BWPs of the SDT over the initial UL BWP (e.g., based on prioritizing the one or more dedicated UL BWPs of the SDT over the initial UL BWP, the UE may select a dedicated UL BWP from among the one or more dedicated UL BWPs of the SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the one or more dedicated UL BWPs of the SDT (e.g., based on prioritizing the initial UL BWP over the one or more dedicated UL BWPs of the SDT, the UE may select the initial UL BWP instead of the dedicated UL BWP from among the one or more dedicated UL BWPs of the SDT). In some instances, the priority ranking (e.g., the priority ranking of the one or more dedicated UL BWPs of the SDT over the initial UL BWP or the priority ranking of the initial UL BWP over the one or more dedicated UL BWPs of the SDT) may be based on a UE category of the UE and / or a UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the one or more dedicated UL BWPs of the SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the one or more dedicated UL BWPs of the SDT. In a case where the one or more dedicated UL BWPs of the SDT are configured for a cell and the initial UL BWP of the cell may also be used for the SDT procedure (e.g., where the preconfigured PUSCH resources of the SDT are configured on the initial UL BWP), the UE may select a UL BWP (e.g., one UL BWP) from among the one or more dedicated UL BWPs of the SDT and the initial UL BWP based on an indication (e.g., the network may instruct and / or instruct the UE to perform the SDT procedure using the one or more dedicated UL BWPs of the SDT or the initial UL BWP) (e.g., the UE may select the dedicated UL BWP or the initial UL BWP from among the one or more dedicated UL BWPs of the SDT based on the indication).For example, if the indication indicates that the SDT procedure is performed using the one or more dedicated UL BWPs of the SDT (and / or if the indication indicates that the SDT procedure is performed using a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT), the UE may select a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT. Alternatively and / or additionally, if the indication indicates that the SDT procedure is performed using an initial UL BWP, the UE may select the initial UL BWP. The indication may be included in a dedicated RRC message transmitted to the UE (e.g., the indication may be included in an RRCRelease message). If the UE selects a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT, the UE may perform the SDT procedure using the dedicated UL BWP. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0613] In a fourth concept, the UE may perform UL transmission using one or more pre-configured PUSCH resources outside the initial UL BWP of the cell.

[0614] In some systems, it may not be expected that the UE performs transmission and / or reception outside the UE's currently active UL BWP and / or the UE's currently active DL BWP. The UE's currently active UL BWP may correspond to the UL BWP currently active for the UE. The currently active DL BWP may correspond to the DL BWP currently active for the UE. In order to address one or more of the aforementioned problems (e.g., insufficient PUSCH resources in the initial UL BWP of the cell), the UE may be allowed (and / or configured to) perform an SDT procedure based on pre-configured PUSCH resources outside the initial UL BWP of the cell. In some instances, the frequency range of the initial UL BWP may be within (and / or narrower than) the bandwidth of the cell (e.g., the entire cell) (e.g., the entire cell bandwidth). The network may configure the UE to use pre-configured PUSCH resources at a frequency outside the frequency range of the initial ULBWP and / or within the bandwidth of the cell (e.g., the entire cell) (e.g., the entire cell bandwidth). In an example where the frequency range of the initial UL BWP is 2545 MHz to 2555 MHz and the bandwidth of the cell (e.g., the entire cell) (e.g., the entire cell bandwidth) is 2500 MHz to 2600 MHz, the network may configure the UE to use the preconfigured PUSCH resources at 2580 MHz, which is outside the frequency range of the initial UL BWP of the cell. The UE may adjust (and / or re-tune) (e.g., temporarily adjust and / or re-tune) a transmit unit of the UE to perform (and / or be able to perform) transmission outside the initial UL BWP (e.g., even if no additional UL BWP is configured for the UE). For example, by adjusting and / or re-tuning the transmit unit (e.g., temporarily adjusting and / or re-tuning the transmit unit), the UE may enable transmission outside the initial UL BWP (e.g., even if no additional UL BWP is configured for the UE). The UE may receive the configuration of the pre-configured PUSCH resources in dedicated signaling (e.g., an RRCRelease message). The UE may determine (e.g., calculate) the resource location of the preconfigured PUSCH resources based on the frequency location and / or bandwidth (e.g., the entire cell bandwidth) of the cell (e.g., the entire cell) (e.g., instead of determining the resource location of the preconfigured PUSCH resources based on the frequency location and / or bandwidth of the initial UL BWP). Alternatively and / or in addition, the resource location of the preconfigured PUSCH resources may be within the bandwidth (e.g., the entire cell bandwidth) of the cell (e.g., the entire cell). Alternatively and / or in addition, the resource location of the preconfigured PUSCH resources may or may not be outside the initial UL BWP (and / or the resource location of the preconfigured PUSCH resources may or may not be within the frequency range and / or bandwidth of the initial UL BWP).

[0615] Alternatively and / or in addition, the UE may be configured to receive a network response (e.g., at least one of a physical downlink control channel (PDCCH) scheduling a physical downlink shared channel (PDSCH) transmission, a PDCCH scheduling a PUSCH retransmission, a PDCCH indicating a successful or unsuccessful transmission, a PDSCH transmission, etc.) outside of the initial DL BWP of the cell, where the network response is transmitted by the network in response to a transmission performed using preconfigured PUSCH resources (e.g., by the UE).

[0616] The UE may determine whether transmission using the preconfigured PUSCH resources will be performed outside the initial UL BWP based on the configuration of the preconfigured PUSCH resources. Alternatively and / or additionally, the UE may determine whether reception of the network response will be outside the initial DL BWP based on a search space configuration of a PDCCH (e.g., at least one of a PDCCH associated with a network response, a PDCCH scheduling a PDSCH transmission, a PDCCH scheduling a PUSCH retransmission, a PDCCH scheduling a PUSCH transmission, a PDCCH indicating a successful or unsuccessful transmission, etc.). Alternatively and / or additionally, the UE may determine whether to listen and / or receive a network response outside the initial DL BWP based on the search space configuration.

[0617] In some instances (e.g., instances of one or more embodiments discussed herein, e.g., one or more embodiments described with respect to the first concept, the second concept, the third concept, and / or the fourth concept), a release mechanism (e.g., an implicit release mechanism) of preconfigured PUSCH resources may be applied for each UL BWP. For example, a first release mechanism (e.g., a first implicit release mechanism) of preconfigured PUSCH resources may be applied to a first UL BWP of an SDT, a second release mechanism (e.g., a second implicit release mechanism) of preconfigured PUSCH resources may be applied to a second UL BWP of an SDT, and so on. In some instances, a counter for counting the occurrence rate of transmission opportunities in which a UE skips an SDT may be maintained for each UL BWP. For example, a first counter (e.g., associated with a first release mechanism) for counting the occurrence rate of transmission opportunities in which a UE skips an SDT may be maintained for a first UL BWP of an SDT, a second counter (e.g., associated with a second release mechanism) for counting the occurrence rate of transmission opportunities in which a UE skips an SDT may be maintained for a second UL BWP of an SDT, and so on. In some instances, if the first counter of the first UL BWP for SDT reaches and / or exceeds a threshold (e.g., a configured threshold, such as the threshold that the UE is configured to use), then the UE may release the configuration of the first UL BWP for SDT (e.g., the configuration may be configured to (e.g., additionally configured to) be used for a cell such as the first cell). Alternatively and / or in addition, if the first counter of the first UL BWP for SDT reaches and / or exceeds a threshold (e.g., a configured threshold, such as the threshold that the UE is configured to use), then the UE may release the pre-configured PUSCH resources configured for the first UL BWP for SDT (e.g., with or without releasing the configuration of the first UL BWP for SDT, the UE may release the pre-configured PUSCH resources configured for the first UL BWP for SDT).

[0618] Alternatively and / or in addition, a release mechanism (e.g., an implicit release mechanism) of preconfigured PUSCH resources may be applied for each cell. For example, a first release mechanism (e.g., a first implicit release mechanism) of preconfigured PUSCH resources may be applied to a first cell, a second release mechanism (e.g., a second implicit release mechanism) of preconfigured PUSCH resources may be applied to a second cell, and so on. In some instances, a counter for counting the occurrence rate of transmission opportunities in which the UE skips the SDT may be maintained for each cell, for example, for a UL BWP of SDT on the cell (e.g., all UL BWPs of SDT). For example, a first counter (e.g., associated with a first release mechanism) for counting the occurrence rate of transmission opportunities in which the UE skips the SDT may be maintained for a UL BWP of SDT on a first cell (e.g., all UL BWPs of SDT), a second counter (e.g., associated with a second release mechanism) for counting the occurrence rate of transmission opportunities in which the UE skips the SDT may be maintained for a UL BWP of SDT on a second cell (e.g., all UL BWPs of SDT), and so on. In some instances, if the UE performs the SDT using the UL BWP of the SDT on the first cell (e.g., any UL BWP of the SDT in the UL BWP of the SDT on the first cell), the UE may reset the first counter to zero. In some instances, if the first counter of the cell reaches and / or exceeds a threshold (e.g., a configured threshold, such as the threshold that the UE is configured to use), the UE may release the configuration of the UL BWP of the SDT on the first cell (e.g., all UL BWPs of the SDT), such as the UL BWP of the SDT configured (e.g., additionally configured) on the first cell (e.g., all UL BWPs of the SDT). Alternatively and / or additionally, if the first counter of the cell reaches and / or exceeds a threshold (e.g., a configured threshold, such as the threshold that the UE is configured to use), the UE may release the preconfigured PUSCH resources (e.g., all preconfigured PUSCH resources) configured for the first cell (e.g., with or without releasing the configuration of the UL BWP of the SDT (e.g., all UL BWPs of the SDT) configured on the first cell).

[0619] In some instances (e.g., instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, and / or the fourth concept), after the UE selects a UL BWP to be used (e.g., in an SDT procedure), the UE may perform the SDT procedure using the selected UL BWP (and / or the UE may use the selected UL BWP until the SDT procedure is completed). Alternatively and / or in addition, after the UE selects the UL BWP to be used, the UE may perform a (subsequent) selection of the UL BWP in response to an event. In some instances, the event may correspond to an unsuccessful UL transmission (e.g., the event may include an unsuccessful UL transmission in which an SDT procedure occurs). Alternatively and / or in addition, the event corresponds to an UL transmission being performed unsuccessfully multiple times, for example, more than a threshold number of times. Alternatively and / or in addition, the event may correspond to an unsuccessful contention resolution occurring, for example, in a scenario where a preconfigured PUSCH resource (e.g., of an SDT procedure) is shared. Alternatively and / or additionally, the event may correspond to contention resolution being unsuccessfully performed multiple times, eg more than a threshold number of times (eg in the case of a shared (eg SDT procedure) pre-configured PUSCH resource).

[0620] In some instances (e.g., instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, and / or the fourth concept), a timer may be used (and / or introduced) for an SDT procedure on a UL BWP of an SDT. In an instance, the UE may be configured to use a timer. In some instances, the UE may start a timer in response to the initiation of the SDT procedure (and / or after the initiation). Alternatively and / or in addition, the UE may start a timer in response to selecting a UL BWP other than the initial UL BWP (e.g., the UL BWP of the SDT) (and / or after the selection). The UE may stop the timer in response to the successful completion (and / or after the successful completion) of the SDT procedure (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at and / or after the time when the UE considers that there are no other subsequent transmissions of the SDT procedure, etc.). In some instances, the UE may consider that the SDT procedure has not been successfully completed in response to the expiration of the timer (and / or after the expiration). The UE may switch the UE's active UL BWP to the initial UL BWP (and / or may switch the UE's active DL BWP to the initial DL BWP) in response to (and / or after) the expiration of the timer. The UE may fall back to (and / or initiate and / or perform) an RRC recovery procedure (e.g., a legacy RRC recovery procedure) on the initial UL BWP (and / or initial DL BWP) in response to (and / or after) the expiration of the timer.

[0621] For RACH-based, for example, 2-step and / or 4-step RA_SDT procedures (e.g., also referred to as SDT and / or SDT procedures in at least some of the descriptions below, such as in the descriptions of the fifth concept, the sixth concept, and / or the seventh concept), because the UE can transmit UL data as well as the RRCResumeRequest message on the initial UL BWP of the cell, the initial UL BWP of the cell may become congested (e.g., if more than a threshold number of UEs perform the SDT procedure in parallel). For example, there may not be enough (e.g., sufficient) UL resources for the network to schedule the transmission of MsgA / Msg3 of the RACH-based SDT procedure, which may cause the UE to have a longer delay. It may also affect other UEs that are performing an RRC establishment procedure (e.g., a traditional RRC establishment procedure) and / or an RRC recovery procedure (e.g., a traditional RRC recovery procedure) on the cell. Increasing the frequency bandwidth of the initial UL BWP of the cell may not be a preferred solution because not all UEs can support a large UL bandwidth, and / or because a large UL bandwidth may also generate more power consumption.

[0622] One or more techniques are provided herein to address one or more of the aforementioned issues (e.g., at least one of the following: the initial UL BWP of the cell becomes congested, there are insufficient UL resources for the network to schedule MsgA / Msg3 transmissions for RACH-based SDT procedures, UE has longer delays, etc.).

[0623] In a fifth concept, additional UL BWP (eg, in addition to the initial UL BWP) may be used for the SDT procedure.

[0624] In some examples, in order to separate UEs performing SDT from UEs not performing SDT, a UL BWP for SDT may be configured (eg, additionally configured) for a cell.

[0625] The UL BWP of the SDT may have a frequency bandwidth different from the initial UL BWP of the cell. The UL BWP of the SDT may have a frequency position different from the initial UL BWP of the cell (eg, a different center frequency). The UL BWP of the SDT may have basic parameters different from the initial UL BWP of the cell.

[0626] In an example, after initiating a RACH-based SDT procedure (and / or in response to the initiation), the UE may determine (e.g., the UE may check) whether the UL BWP for SDT is configured for the cell. If the UL BWP for SDT is configured for the cell, the UE may perform the RACH-based SDT procedure on the UL BWP for SDT. If the UL BWP for SDT is not configured for the cell, the UE may perform the RACH-based SDT procedure on the initial UL BWP for the cell.

[0627] Alternatively and / or additionally, the RACH-based SDT procedure may be allowed on the UL BWP for SDT (e.g., the RACH-based SDT procedure may be allowed to be performed on the UL BWP for SDT), and may not be allowed on the initial UL BWP for the cell (e.g., the RACH-based SDT procedure may not be allowed to be performed on the initial UL BWP for the cell). Therefore, if the ULBWP for SDT is not configured for the cell, the UE may not be able to perform the SDT procedure.

[0628] In some instances, the UL BWP of the SDT may be configured in the system information of the cell. For example, the UL BWP of the SDT may be configured in SIB1, SIB2, and / or another SIB (e.g., a new SIB) designed for and / or usable for SDT. Alternatively and / or in addition, the UL BWP of the SDT may be configured in a dedicated RRC message (e.g., an RRCRelease message) to the UE and stored in the UE inactive AS context. For example, the UE may be configured (to use) the UL BWP of the SDT via a dedicated RRC message received by the UE, and / or the UE may store the UL BWP of the SDT (and / or the configuration of the UL BWP of the SDT) in the UE inactive AS context (e.g., after receiving the dedicated RRC message). The configuration of the UL BWP of the SDT may be used for the cell that received the configuration (e.g., the cell that received the dedicated RRC message). The configuration of the UL BWP of the SDT may not be applicable to cells other than the cell that received the configuration.

[0629] Alternatively and / or in addition, the network may provide the configuration of the UL BWP for the SDT for the cell list in a dedicated RRC message to the UE (e.g., in an RRCRelease message). For example, the configuration of the UL BWP for the SDT for the cell list may be used for the cells in the cell list. Thus, the UE is able to use the UL BWP for the SDT (and / or the configuration of the UL BWP for the SDT) when initiating the SDT on a cell (e.g., any one cell) in the cell list. For example, the network may include 3 UL BWPs for the SDT in the configuration and / or there may be 3 cells in the cell list, wherein each UL BWP of the SDT in the configuration (of the 3 UL BWPs for the SDT) corresponds to a cell in the cell list. In an example, a first UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a first cell in a cell list (e.g., the UE may use the first UL BWP of SDT to perform a RACH-based SDT procedure on the first cell), a second UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a second cell in the cell list (e.g., the UE may use the second UL BWP of SDT to perform a RACH-based SDT procedure on the second cell), and / or a third UL BWP for SDT among the three UL BWPs of SDT may correspond to (e.g., may be used for) a third cell in the cell list (e.g., the UE may use the third UL BWP of SDT to perform a RACH-based SDT procedure on the third cell). The cell list may indicate and / or may include cells belonging to a first RAN notification area (RNA) (e.g., the cell list may indicate and / or may include all cells belonging to the first RNA or some cells belonging to the first RNA). Alternatively and / or in addition, the cell list may include one or more cells belonging to the second RNA. Alternatively and / or in addition, the cell list may not include cells belonging to the second RNA (e.g., the cell list may not include any cells belonging to the second RNA). In some instances, the UE is configured to use the first RNA when the RRC connection is suspended. In some instances, in response to moving outside of the first RNA (e.g., when residing in a cell that does not belong to the first RNA), the UE initiates the RNA update procedure.

[0630] In some instances, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the UL BWP for the SDT is configured in the system information of the cell, then the UE (e.g., the RRC layer of the UE) may consider the UL BWP for the SDT to be configured. Alternatively and / or in addition, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the UL BWP for the SDT is not configured in the system information of the cell, and if the stored UE-inactive AS context includes a configuration of the UL BWP for the SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the UL BWP for the SDT from the UE-inactive AS context, and may consider the UL BWP for the SDT to be configured. Alternatively and / or additionally, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the UL BWP for SDT is configured in the system information of the cell, and if the stored UE inactive AS context includes a configuration of the UL BWP for SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the UL BWP for SDT from the UE inactive AS context (e.g., instead of using the configuration configured in the system information of the cell), and the UL BWP for SDT may be considered to be configured. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers that the UL BWP for SDT is not configured, then the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure, and may initiate a conventional RRC recovery procedure.

[0631] The RRC layer of the UE may indicate to a lower layer (e.g., a MAC layer) (e.g., of the UE) that the SDT procedure is to be performed on the UL BWP of the SDT (e.g., if the UL BWP of the SDT is configured in the RRC, such as the UL BWP of the SDT is configured in the RRC layer of the UE). The RRC layer of the UE may configure a lower layer (e.g., a MAC layer) (e.g., of the UE) to use the UL BWP of the SDT (e.g., if the UL BWP of the SDT is configured in the RRC, such as the UL BWP of the SDT is configured in the RRC layer of the UE).

[0632] In some instances, in response to successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) through the RRCRelease message (e.g., at the time of and / or after the last of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after other subsequent transmissions of the SDT procedure that the UE considers to be non-existent, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the UL BWP of the SDT. Alternatively and / or in addition, in response to successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) through the RRCRelease message (e.g., at the time of and / or after the last of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after other subsequent transmissions of the SDT procedure that the UE considers to be non-existent, etc.), if the network provides and / or includes a new configuration of the UL BWP of the SDT in the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may replace the configuration of the UL BWP of the SDT contained in the UE inactive AS context with the new configuration of the UL BWP of the SDT (received via the RRCRelease message). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network does not provide and / or include a new configuration of the ULBWP of the SDT (e.g., in the RRCRelease message) and / or if the network indicates (and / or instructs) to release the configuration of the UL BWP of the SDT via the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the UL BWP of the SDT contained in the UE's inactive AS context.

[0633] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the UL BWP for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the UL BWP for the SDT).

[0634] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the UL BWP of the SDT. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the UL BWP of the SDT.

[0635] After initiating the SDT procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the UL BWP of the SDT. For example, if the upper layer (e.g., the RRC layer of the UE) indicates that the SDT procedure is to be performed on the UL BWP of the SDT, then after initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the UL BWP of the SDT. Alternatively and / or in addition, if the upper layer (e.g., the RRC layer of the UE) configures the MAC (e.g., the MAC layer of the UE) to use the UL BWP of the SDT, then after initiating the RACH-based SDT procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the UL BWP of the SDT.

[0636] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) (and / or after successful completion) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell).

[0637] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the UL BWP of the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the ULBWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the MAC layer of the UE) may switch the active ULBWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the UL BWP of the SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0638] In a case where the UL BWP of the SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may select (e.g., randomly select) a UL BWP (e.g., one UL BWP) between the UL BWP of the SDT and the initial UL BWP (e.g., the UE may select, e.g., randomly select, the UL BWP of the SDT or the initial UL BWP). In a case where the UL BWP of the SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may prioritize the UL BWP of the SDT over the initial UL BWP (e.g., based on prioritizing the UL BWP of the SDT over the initial UL BWP, the UE may select the UL BWP of the SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the UL BWP of the SDT (e.g., based on prioritizing the initial UL BWP over the UL BWP of the SDT, the UE may select the initial UL BWP instead of the UL BWP of the SDT). In some examples, the prioritization (e.g., the prioritization of the UL BWP of SDT over the initial UL BWP or the prioritization of the initial UL BWP over the UL BWP of SDT) may be based on the UE category of the UE and / or the UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the UL BWP of SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the UL BWP of SDT. In a situation where the UL BWP of SDT is configured for a cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may prioritize the initial UL BWP over the UL BWP of SDT (e.g., if the initial UL BWP of the cell is available for the SDT procedure, the UE may select the initial UL BWP). Alternatively and / or additionally, if the initial UL BWP of the cell is not available for the SDT procedure, the UE may select the UL BWP of SDT. In a situation where the UL BWP for SDT is configured for a cell and the initial UL BWP of the cell can also be used for the SDT procedure (e.g., where the RA resources for the SDT are configured on the initial UL BWP), the UE may select a UL BWP (e.g., one UL BWP) between the UL BWP for SDT and the initial UL BWP based on an indication (e.g., the network may instruct and / or instruct the UE to perform the SDT procedure using the UL BWP for SDT or the initial UL BWP) (e.g., the UE may select the UL BWP for SDT or the initial UL BWP based on the indication).For example, if the indication indicates that the SDT procedure is performed using the UL BWP of the SDT, the UE may select the UL BWP of the SDT. Alternatively and / or additionally, if the indication indicates that the SDT procedure is performed using the initial UL BWP, the UE may select the initial UL BWP. The indication may be included in a dedicated RRC message transmitted to the UE (e.g., the indication may be included in an RRCRelease message). If the UE selects the UL BWP of the SDT, the UE may perform the SDT procedure using the UL BWP of the SDT. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0639] Fig. 20 An example scenario associated with the UE's execution of an SDT procedure is shown. The UE may receive a first RRCRelease message 2000 indicating a BWP for the SDT. The UE may use an initial BWP (e.g., a BWP different from the SDT's) between the reception of the first RRCRelease message 2000 and the initiation 2010 of an SDT procedure (e.g., a RACH-based SDT procedure, such as a random access SDT (RA-SDT) procedure). The UE may use the BWP for the SDT during a time period between the initiation 2010 of the SDT procedure and the completion of the SDT procedure (e.g., the SDT procedure may be completed by the reception of a second RRCRelease message 2006). In some instances, the time period between the initiation 2010 of the SDT procedure and the completion of the SDT procedure may include a time period 2012 during which an RA procedure is performed and a time period 2014 after the RA procedure. In some instances, the UE may perform (e.g., transmit and / or receive) a first transmission 2002 (e.g., a Msg3 transmission and / or a MsgA transmission) during time period 2012, and / or perform (e.g., transmit and / or receive) one or more subsequent transmissions 2004 during time period 2014.

[0640] In the sixth concept, a set of UL BWPs may be used for the SDT procedure.

[0641] In some instances, in order to separate UEs performing SDT (e.g., to divide the UEs into multiple groups), a set of UL BWPs for SDT may be configured for a cell. The set of UL BWPs for SDT may include the UL BWP of the SDT (e.g., at least one UL BWP of the SDT). If more than one UL BWP of the SDT is configured (e.g., if the set of UL BWPs configured for SDT for the cell includes more than one UL BWP of the SDT), the UE may perform selection of a UL BWP (e.g., one UL BWP) from the set of UL BWPs for SDT. Alternatively and / or additionally, if only one UL BWP of the SDT is configured (e.g., if the set of BWPs configured for SDT for the cell includes only one UL BWP of the SDT), the UE may perform selection of the one UL BWP of the SDT.

[0642] In some examples, the UL BWP of the SDT in the set of UL BWPs of the SDT may have a frequency bandwidth different from the initial UL BWP of the cell. Alternatively and / or additionally, the UL BWP of the SDT may have a frequency location different from the initial UL BWP of the cell (e.g., a different center frequency). Alternatively and / or additionally, the UL BWP of the SDT may have a basic parameter different from the initial UL BWP of the cell.

[0643] In an example, after initiating a RACH-based SDT procedure (and / or in response to the initiation), the UE may determine (e.g., the UE may check) whether the set of UL BWPs for the SDT is configured for the cell. If the set of UL BWPs for the SDT is configured for the cell, the UE may perform the RACH-based SDT procedure on the selected UL BWP for the SDT (e.g., after performing a selection of the selected UL BWP from the set of UL BWPs for the SDT). If the set of UL BWPs for the SDT is not configured for the cell, the UE may perform the RACH-based SDT procedure on the initial UL BWP for the cell.

[0644] Alternatively and / or in addition, the RACH-based SDT procedure may be allowed on the set of UL BWPs for SDT (e.g., the RACH-based SDT procedure may be allowed to be performed on a UL BWP in the set of UL BWPs for SDT), and may not be allowed on the initial UL BWP of the cell (e.g., the RACH-based SDT procedure may not be allowed to be performed on the initial UL BWP of the cell). Therefore, if the set of UL BWPs for SDT is not configured for the cell, the UE may not be able to perform the SDT procedure.

[0645] In some instances, the set of UL BWPs for the SDT may be configured in the system information of the cell. For example, the set of UL BWPs for the SDT may be configured in SIB1, SIB2, and / or another SIB designed for and / or available for the SDT (e.g., a new SIB). Alternatively and / or in addition, the set of UL BWPs for the SDT may be configured in a dedicated RRC message (e.g., an RRCRelease message) to the UE and stored in the UE inactive AS context. For example, the UE may be configured (to use) the set of UL BWPs for the SDT via a dedicated RRC message received by the UE, and / or the UE may store the set of UL BWPs for the SDT (and / or the configuration of the set of UL BWPs for the SDT) in the UE inactive AS context (e.g., after receiving the dedicated RRC message). The configuration of the set of UL BWPs for the SDT may be used for the cell that received the configuration (e.g., the cell that received the dedicated RRC message). The configuration of the set of UL BWPs for the SDT may not be applicable to cells other than the cell that received the configuration.

[0646] Alternatively and / or in addition, the network may provide the configuration of the set of UL BWPs for the SDT for the cell list in a dedicated RRC message to the UE (e.g., in an RRCRelease message). For example, the configuration of the UL BWPs for the SDT for the cell list may be used for the cells in the cell list. Thus, the UE is able to use the UL BWPs among the set of UL BWPs for the SDT when initiating the SDT on a cell (e.g., any one cell) among the cell list. In an example, the network may include 5 UL BWPs for the SDT in the configuration and / or there may be 3 cells in the cell list, wherein the first UL BWP and the second UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the first cell in the cell list, wherein the third UL BWP and the fourth UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the second cell in the cell list, and wherein the fifth UL BWP of the 5 UL BWPs for the SDT may correspond to (e.g., may be used for) the third cell in the cell list. The cell list may indicate and / or may include cells belonging to a first RAN notification area (RNA) (e.g., the cell list may indicate and / or may include all cells belonging to the first RNA or some cells belonging to the first RNA). Alternatively and / or in addition, the cell list may include one or more cells belonging to a second RNA. Alternatively and / or in addition, the cell list may not include cells belonging to the second RNA (e.g., the cell list may not include any cells belonging to the second RNA). In some instances, the UE is configured to use the first RNA when the RRC connection is suspended. In some instances, in response to moving outside the first RNA (e.g., when residing in a cell that does not belong to the first RNA), the UE initiates an RNA update procedure.

[0647] In some instances, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the set of UL BWPs for the SDT is configured in the system information of the cell, then the UE (e.g., the RRC layer of the UE) may consider the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) to be configured. Alternatively and / or in addition, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the set of UL BWPs for the SDT is not configured in the system information of the cell, and if the stored UE-inactive AS context includes a configuration of the set of UL BWPs for the SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the set of UL BWPs for the SDT from the UE-inactive AS context, and may consider the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) to be configured. Alternatively and / or additionally, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the set of UL BWPs for SDT is configured in the system information of the cell, and if the stored UE inactive AS context contains the configuration of the set of UL BWPs for SDT that can be used for the cell (e.g., the cell may be the same as the previous SpCell and / or the cell may be in the cell list, such as discussed above), then the UE (e.g., the RRC layer of the UE) may recover the configuration of the set of UL BWPs for SDT from the UE inactive AS context (e.g., instead of using the configuration configured in the system information of the cell), and may consider the UL BWP for SDT (and / or the set of UL BWPs for SDT) to be configured. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers the UL BWP for SDT (and / or the set of UL BWPs for SDT) to be not configured, then the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure, and may initiate a conventional RRC recovery procedure.

[0648] The UE may perform selecting a UL BWP (eg, one UL BWP) from the set of UL BWPs for the SDT on the cell using one or more selection techniques (eg, in a case where the set of UL BWPs for the SDT includes more than one UL BWP for the SDT).

[0649] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on random selection.

[0650] In an example, when the UE initiates SDT on the cell (and / or after initiating SDT on the cell and / or in response to the initiation), the UE may randomly select a UL BWP from the set of UL BWPs for the SDT. For example, each time the UE initiates SDT on the cell, the UE randomly selects a UL BWP from the set of UL BWPs for the SDT (e.g., when the UE initiates SDT on the cell and / or after initiating SDT on the cell and / or in response to the initiation, the UE may randomly select a UL BWP).

[0651] In an example where the UE selects a UL BWP from the set of UL BWPs of the SDT based on random selection, the probability of selecting each UL BWP in the set of UL BWPs may be the same. For example, if there are two UL BWPs in the set of UL BWPs of the SDT, the probability of selecting a first UL BWP of the two UL BWPs may be 50%, and the probability of selecting a second UL BWP of the two UL BWPs may be 50%.

[0652] Alternatively and / or additionally, in an example where the UE selects a UL BWP from the set of UL BWPs of the SDT based on random selection, the probability of selecting the UL BWP from the set of UL BWPs may be configurable. For example, the network may configure the probability (with which the UE is configured) in the configuration of the set of UL BWPs (e.g., the probability may be included in the configuration). The UE may perform the selection based on the probability (used to configure the UE). In an example, the probability of selecting a first UL BWP from the set of UL BWPs may be a first configured probability, the probability of selecting a second UL BWP from the set of UL BWPs may be a second configured probability, and so on.

[0653] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on a UE identification of the UE.

[0654] In an example, when the UE initiates SDT on the cell (and / or after initiating SDT on the cell and / or in response to the initiation), the UE may select the UL BWP from the set of UL BWPs for the SDT based on the UE identity and / or a formula. For example, each time the UE initiates SDT on the cell, the UE may select the UL BWP from the set of UL BWPs for the SDT based on the UE identity and / or a formula (for example, when the UE initiates SDT on the cell and / or after initiating SDT on the cell and / or in response to the initiation, the UE may randomly select the UL BWP).

[0655] In an example, the UE may perform one or more operations (e.g., mathematical operations) to select a UL BWP from the set of UL BWPs of the SDT using the UE identity (e.g., the one or more operations may be performed according to a formula). In an example, the formula may be XmodY, where X is the UE identity, mod is a modulo operation, and / or Y is the number of UL BWPs in the set of UL BWPs of the SDT. The UE may determine a result of the formula, and / or the UE may select a UL BWP from the set of UL BWPs of the SDT based on the result. In an example, a result of 0 may correspond to a first UL BWP in the set of UL BWPs, a result of 1 may correspond to a second UL BWP in the set of UL BWPs, a result of 2 may correspond to a third UL BWP in the set of UL BWPs, and so on. In an example where the UE identity of the UE is 10 and the number of UL BWPs in the set of UL BWPs of the SDT is 3, the UE may determine that the result is 10mod3=1, and / or may select the second UL BWP from the set of UL BWPs of the SDT based on the result being 1.

[0656] The UE identifier may be the I-RNTI assigned to the UE in the RRCRelease message. Alternatively and / or in addition, the UE identifier may be a different identifier other than the I-RNTI, such as an identifier designed and / or usable for the SDT procedure, wherein the different identifier may be assigned to the UE in the RRCRelease message.

[0657] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on an indication (eg, an indication from the network).

[0658] In an example, the network may indicate a UL BWP among the set of UL BWPs for SDT that should be provided to the UE for SDT (eg, the network may indicate which UL BWP among the set of UL BWPs for SDT should be provided to the UE for use).

[0659] For example, the network may provide an indication (e.g., a value, such as an integer) in a dedicated RRC message to the UE (e.g., in an RRCRelease message). The UE may perform an SDT procedure on the UL BWP of the cell based on the indication (e.g., the indication may indicate the UL BWP). The indication may be per cell (e.g., the network may provide multiple indications for a cell list, wherein each of the multiple indications indicates the UL BWP of a cell in the cell list). Alternatively and / or in addition, the indication may be common to multiple cells (e.g., the network may provide a single indication for a cell list).

[0660] In some instances, the SDT procedure may be triggered by the network via paging (e.g., due to the arrival of DL data at the network side). For example, the network may transmit a paging message (associated with triggering the SDT procedure) to the UE. The paging message transmitted to the UE may include a first indication (e.g., a flag) indicating the initiation of the SDT procedure. The paging message transmitted to the UE may include a second indication (e.g., a value, such as an integer) indicating which UL BWP (e.g., of the set of UL BWPs) the UE should use for SDT. The first indication and the second indication may be the same indication (e.g., the presence of the indication may indicate the initiation of the SDT procedure and / or the value of the indication may indicate the UL BWP to be used). In response to receiving the paging message on the cell, the UE performs the SDT procedure on the indicated UL BWP of the cell based on the first indication and / or the second indication.

[0661] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on radio conditions and / or channel conditions of the UL BWP.

[0662] For example, each UL BWP in the set of UL BWPs of the SDT may be associated with one or more DL reference signals (e.g., the one or more DL reference signals may be received in a DL BWP paired with the UL BWP). For example, a first UL BWP in the set of UL BWPs of the SDT may be associated with one or more first DL reference signals, a second UL BWP in the set of UL BWPs of the SDT may be associated with one or more second DL reference signals, and so on, and the UE may select the UL BWP in the set of UL BWPs of the SDT based on measurements of the DL reference signals associated with the set of UL BWPs of the SDT. For example, the UE may select the UL BWP in the set of UL BWPs of the SDT based on determining that the UL BWP has the best reference signal quality among the set of UL BWPs (e.g., determining that the UL BWP has the best reference signal quality among the set of UL BWPs may be based on measurements of the DL reference signals associated with the set of UL BWPs of the SDT).

[0663] Alternatively and / or additionally, the UE may perform "listen before talk" on each UL BWP among the set of UL BWPs of the SDT. The UE may not select an occupied UL BWP (e.g., occupied due to another UE using the UL BWP and / or due to strong interference in the UL BWP), wherein whether the UL BWP is occupied may be determined by performing "listen before talk" on the UL BWP. The UE may select an unoccupied UL BWP, wherein whether the UL BWP is occupied may be determined by performing "listen before talk" on the UL BWP. Alternatively and / or additionally, the UE may select the UL BWP with the lowest noise and / or lowest interference among the set of UL BWPs, wherein the UE may determine that the UL BWP has the lowest noise and / or lowest interference among the set of UL BWPs by performing "listen before talk" on each UL BWP among the set of UL BWPs of the SDT.

[0664] In some examples, the UE may select a UL BWP from the set of UL BWPs for the SDT based on the UL data size (eg, the amount of UL data to be transmitted via the SDT procedure).

[0665] For example, each UL BWP in the set of UL BWPs of the SDT may be associated with a transport block size (TBS) (e.g., the transport block size may be configurable). In an example, a first UL BWP in the set of UL BWPs of the SDT may be associated with a first transport block size, a second UL BWP in the set of UL BWPs of the SDT may be associated with a second transport block size, and so on. The UE may select the UL BWP based on the UL data size (e.g., the amount of UL data to be transmitted). Alternatively and / or additionally, the UE may select the UL BWP based on the total data amount (e.g., the total data amount may correspond to the data size of the UL data size plus the size of the RRC message and / or MAC subheader). In an instance where the total amount of data is 100 kilobytes (KB), a first UL BWP among the set of UL BWPs of the SDT is associated with a transport block size of 70KB, and a second UL BWP among the set of UL BWPs of the SDT is associated with a transport block size of 120KB, the UE may select the second UL BWP based on determining that the second UL BWP is capable of transmitting all UL data without introducing a threshold number of padding bits (and / or the UE may select the second UL BWP based on determining that the transport block size of the second UL BWP exceeds the total amount of data and / or the difference between the transport block size of the second UL BWP and the total amount of data is less than a threshold).

[0666] The RRC layer of the UE may indicate to the lower layer (e.g., the MAC layer) (e.g., the UE) that the SDT procedure will be performed on the UL BWP of the SDT (e.g., the selected UL BWP of the SDT) in the set of UL BWPs of the SDT (e.g., if the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC, such as the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC layer of the UE). The RRC layer of the UE may configure the lower layer (e.g., the MAC layer) (e.g., the UE) to use the UL BWP of the SDT (e.g., if the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC, such as the UL BWP of the SDT and / or the set of UL BWPs of the SDT are configured in the RRC layer of the UE).

[0667] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via an RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT. Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network provides and / or includes a new configuration of the set of UL BWPs for the SDT in the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may replace the configuration of the set of UL BWPs for the SDT contained in the UE's inactive AS context with the new configuration of the set of UL BWPs for the SDT (received via the RRCRelease message). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time of and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), if the network does not provide and / or include a new configuration of the set of UL BWPs for the SDT (e.g., in the RRCRelease message) and / or if the network indicates (and / or instructs) to release the configuration of the set of UL BWPs for the SDT via the RRCRelease message, then the UE (e.g., the RRC layer of the UE) may release (and / or discard) the configuration of the set of UL BWPs for the SDT contained in the UE's inactive AS context.

[0668] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, and / or after that, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the set of UL BWPs for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the set of UL BWPs for the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in the masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the set of UL BWPs for the SDT).Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the set of UL BWPs for the SDT).

[0669] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the set of UL BWPs for SDT. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the set of UL BWPs for SDT.

[0670] After initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the selected UL BWP of the SDT (e.g., the UL BWP is selected from the set of UL BWPs of the SDT). For example, if the upper layer (e.g., the RRC layer of the UE) indicates that the SDT procedure is to be performed on the selected UL BWP of the SDT, then after initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the selected UL BWP of the SDT. Alternatively and / or in addition, if the upper layer (e.g., the RRC layer of the UE) configures the MAC (e.g., the MAC layer of the UE) to use the selected UL BWP of the SDT, then after initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the selected UL BWP of the SDT.

[0671] In some instances, after successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (and / or in response to the successful completion) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell).

[0672] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the selected UL BWP of the SDT (e.g., if a new BWP configuration is not provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the selected UL BWP of the SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message, the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the selected UL BWP of the SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0673] In the case where the set of UL BWPs for SDT is configured for the cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may perform a selection (e.g., selecting a UL BWP from a second set of UL BWPs) using one or more of the techniques discussed herein for selecting a UL BWP from the set of UL BWPs for SDT (e.g., based on random selection, UE identity of the UE, indication from the network, radio conditions, channel conditions, listen-before-talk, and / or UL data size), wherein the initial UL BWP may be considered (e.g., by the UE) to be included in the second set of UL BWPs from which the selected UL BWP is selected (e.g., the initial UL BWP may be considered to be a UL BWP included in the second set of UL BWPs). For example, the second set of UL BWPs may include the set of UL BWPs for SDT and the initial UL BWP. In an example, the initial UL BWP may be considered to be the first UL BWP in the second set of UL BWPs (e.g., consecutive to the first UL BWP). In a situation where the set of UL BWPs for SDT is configured for a cell and an initial UL BWP of the cell may also be used for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may prioritize the set of UL BWPs for SDT over the initial UL BWP (e.g., based on prioritizing the set of UL BWPs for SDT over the initial UL BWP, the UE may select a UL BWP in the set of UL BWPs for SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT (e.g., based on prioritizing the initial UL BWP over the set of UL BWPs for SDT, the UE may select the initial UL BWP instead of the UL BWP in the set of UL BWPs for SDT). In some examples, the priority ranking (e.g., the priority ranking of the set of UL BWPs for SDT over the initial UL BWP or the priority ranking of the initial UL BWP over the set of UL BWPs for SDT) may be based on a UE category of the UE and / or a UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the set of UL BWPs for SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT. In a situation where the set of UL BWPs for SDT is configured for a cell and the initial UL BWP of the cell is also available for the SDT procedure (e.g., where the RA resources for the SDT are configured on the initial UL BWP), the UE may prioritize the initial UL BWP over the set of UL BWPs for SDT (e.g., if the initial UL BWP of the cell is available for the SDT procedure, the UE may select the initial UL BWP).Alternatively and / or additionally, if the initial UL BWP of the cell is not available for the SDT procedure, the UE may select a UL BWP from the set of UL BWPs for the SDT. If the UE selects the UL BWP of the SDT from the set of UL BWPs for the SDT, the UE may perform the SDT procedure using the UL BWP of the SDT. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0674] In the seventh concept, one or more dedicated UL BWPs in RRC_CONNECTED may be used for the SDT procedure.

[0675] In some instances, when the UE is in the RRC_CONNECTED state, the network configures the UE with a UL BWP (e.g., referred to as a dedicated UL BWP) for use in the RRC_CONNECTED state. For example, the network may configure the UE to use the dedicated UL BWP by providing the UE with a configuration of the dedicated UL BWP. In some instances, the configuration of the dedicated UL BWP includes a physical random access channel (PRACH) resource for SDT. After initiating the SDT procedure (and / or in response to the initiation), if the dedicated UL BWP is available for the cell (e.g., the cell may be the same as the previous SpCell), the UE may restore the configuration of the dedicated UL BWP from the UE inactive AS context, and the UE may perform the SDT procedure using the dedicated UL BWP (e.g., if the dedicated UL BWP is available for the cell).

[0676] In some instances, when the UE is in the RRC_CONNECTED state, the network configures a set of dedicated UL BWPs for use in the RRC_CONNECTED state to the UE. For example, the network may configure the UE to use the set of dedicated UL BWPs by providing one or more configurations of the set of dedicated UL BWPs to the UE. In some instances, the configuration (e.g., of the one or more configurations) of each dedicated UL BWP in the set of dedicated UL BWPs includes a PRACH resource for an SDT. For example, a first configuration of a first dedicated UL BWP in the set of dedicated UL BWPs may include a first PRACH resource for an SDT, a second configuration of a second dedicated UL BWP in the set of dedicated UL BWPs may include a second PRACH resource for an SDT, and so on. After initiating the SDT procedure (and / or in response to the initiation), if the set of dedicated UL BWPs is available for the cell (e.g., the cell may be the same as the previous SpCell), the UE may recover each of the one or more configurations (e.g., the configuration of each dedicated UL BWP among the set of dedicated UL BWPs) from the UE inactive AS context, and the UE may select a dedicated UL BWP (e.g., one dedicated UL BWP) from the set of dedicated UL BWPs to perform the SDT procedure (e.g., if the set of dedicated UL BWPs is available for the cell).

[0677] In some instances, when the UE is in the RRC_CONNECTED state, the network configures the UE with a dedicated UL BWP (and / or a set of dedicated UL BWPs) for use in the RRC_CONNECTED state (e.g., when the UE is in the RRC_CONNECTED state, the network configures the UE with a dedicated UL BWP (and / or the set of dedicated UL BWPs) for use in the RRC_CONNECTED state). Alternatively and / or in addition, before or after the UE enters the RRC_INACTIVE state (and / or in response to the entry), the network indicates (e.g., to the UE) a dedicated UL BWP that the UE should use to perform the SDT procedure (e.g., the network may instruct the UE to perform the SDT procedure using the dedicated UL BWP). In an instance, the indication of the dedicated UL BWP may be included in an RRCRelease message transmitted to the UE.

[0678] In at least some descriptions below, "dedicated UL BWP" may be a UL BWP used in RRC_CONNECTED state (eg, for a UE) and may be used for SDT in RRC_INACTIVE state (eg, PRACH resources of SDT are configured for the dedicated UL BWP).

[0679] For example, the UE may be configured to use one or more dedicated UL BWPs (e.g., when the UE is in RRC_CONNECTED state) and / or the UE may use the one or more dedicated UL BWPs in the RRC_CONNECTED state, wherein the one or more dedicated UL BWPs may be used for SDT in the RRC_INACTIVE state (e.g., by the UE) (e.g., one or more PRACH resources of the SDT may be configured to be used for the one or more dedicated UL BWPs).

[0680] In some instances, the UE may prioritize the one or more dedicated UL BWPs used in the RRC_CONNECTED state over the UL BWP for SDT (and / or a set of UL BWPs for SDT) configured in the system information. For example, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the UL BWP for SDT (and / or the set of UL BWPs for SDT) is configured in the system information of the cell, and if the stored UE inactive AS context includes the configuration of the one or more dedicated UL BWPs that can be used for the cell, then the UE (e.g., the RRC layer of the UE) may restore the configuration of the one or more dedicated UL BWPs from the UE inactive AS context, and the UL BWP for SDT (and / or the set of UL BWPs for SDT) may be considered to be configured.

[0681] In some instances, the UE may prioritize the UL BWP for the SDT (and / or a set of UL BWPs for the SDT) received in the RRCRelease message over the one or more dedicated UL BWPs used in the RRC_CONNECTED state. For example, after initiating a RACH-based SDT procedure (and / or in response to the initiation), if the stored UE inactive AS context includes a configuration of the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) that can be used for a cell (e.g., the cell can be the same as the previous SpCell and / or the cell can be in the cell list, such as discussed above), and if the stored UE inactive AS context includes a configuration of the one or more dedicated UL BWPs that can be used for the cell, then the UE (e.g., the RRC layer of the UE) may restore the configuration of the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) from the UE inactive AS context (e.g., instead of restoring the configuration of the one or more dedicated UL BWPs), and the UL BWP for the SDT (and / or the set of UL BWPs for the SDT) may be considered to be configured. Alternatively and / or additionally, the UE may consider the one or more dedicated UL BWPs used in the RRC_CONNECTED state as part of the set of UL BWPs for SDT. For example, if there is one dedicated UL BWP and two UL BWPs for SDT in the stored UE inactive AS context, the UE may consider that there are three UL BWPs in the set of UL BWPs for SDT. Alternatively and / or additionally, if the UE (e.g., the RRC layer of the UE) considers that the UL BWP for SDT (and / or the set of UL BWPs for SDT) is not configured, the UE (e.g., the RRC layer of the UE) may cancel (and / or may not initiate) the SDT procedure and may initiate a conventional RRC recovery procedure.

[0682] In some instances, if multiple UL BWPs for the SDT are configured (e.g., if the UE is configured to use more than one UL BWP for the SDT), for example, counting one or more dedicated UL BWPs for the SDT used in the RRC_CONNECTED state and / or counting the UL BWPs (and / or a set of UL BWPs) for the SDT configured in the system information and / or received in the RRCRelease message, then the UE may select the ULBWP for the SDT on the cell from the multiple UL BWPs (and / or from the set of UL BWPs for the SDT) (e.g., the UL BWP may be selected using one or more of the techniques discussed herein for selecting a UL BWP from a set of UL BWPs for the SDT, such as based on random selection, a UE identity of the UE, an indication from the network, radio conditions, channel conditions, listen-before-talk, and / or UL data size).

[0683] In some instances, the UE may be configured to use one or more dedicated UL BWPs (e.g., when the UE is in an RRC_CONNECTED state) and / or the UE may use the one or more dedicated UL BWPs in the RRC_CONNECTED state, wherein the one or more dedicated UL BWPs may be used for SDT in an RRC_INACTIVE state (e.g., by the UE) (e.g., one or more PRACH resources of the SDT may be configured to be used for the one or more dedicated UL BWPs).

[0684] The RRC layer of the UE may indicate to the lower layers (e.g., the MAC layer) (e.g., the UE) that the SDT procedure is to be performed on the one or more dedicated UL BWPs of the SDT. For example, if the one or more dedicated UL BWPs are configured in the RRC (e.g., if the one or more dedicated UL BWPs are configured in the RRC layer of the UE), then the RRC layer of the UE may indicate to the lower layers that the SDT procedure is to be performed on the one or more dedicated UL BWPs. The RRC layer of the UE may configure the lower layers (e.g., the MAC layer) (e.g., the UE) to use the one or more dedicated UL BWPs (e.g., if the one or more dedicated UL BWPs are configured in the RRC, such as the one or more dedicated UL BWPs are configured in the RRC layer of the UE).

[0685] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via an RRCRelease message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs of the SDT.

[0686] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the one or more dedicated UL BWPs). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may release and / or abandon the configuration of the one or more dedicated UL BWPs). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs for the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the one or more dedicated UL BWPs for the SDT).Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs for the SDT (e.g., if a new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the UE and / or the RRC layer of the UE may maintain the configuration of the one or more dedicated UL BWPs for the SDT).

[0687] In response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may release (and / or abandon) the configuration of the one or more dedicated UL BWPs. Alternatively and / or additionally, in response to the unsuccessful completion of the SDT procedure through the RRCSetup message (e.g., unsuccessful completion of the SDT procedure), the UE (e.g., the RRC layer of the UE) may maintain the configuration of the one or more dedicated UL BWPs.

[0688] After initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the dedicated UL BWP of the SDT (e.g., the dedicated UL BWP of the SDT among the one or more dedicated UL BWPs of the SDT). For example, if the upper layer (e.g., the RRC layer of the UE) indicates that the SDT procedure is to be performed on the dedicated UL BWP of the SDT, then after initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE to the dedicated UL BWP of the SDT. Alternatively and / or in addition, if the upper layer (e.g., the RRC layer of the UE) configures the MAC (e.g., the MAC layer of the UE) to use the dedicated UL BWP of the SDT, then after initiating the RA procedure on the cell (and / or in response to the initiation), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP of the UE (e.g., from the initial UL BWP) to the dedicated UL BWP of the SDT.

[0689] In some instances, after successfully completing the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCRelease message (and / or in response to the successful completion) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the UE may switch the active UL BWP from the dedicated UL BWP of the SDT to the initial active UL BWP of the cell).

[0690] In some instances, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may maintain use (e.g., continue to use) the dedicated UL BWP for SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in a masterCellGroup, then the MAC layer of the UE may maintain use of the dedicated UL BWP for SDT). Alternatively and / or in addition, in response to successful completion of the SDT procedure (e.g., successful completion of the SDT procedure) via the RRCResume message (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time and / or after the UE believes that there are no other subsequent transmissions of the SDT procedure, etc.), the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from the dedicated UL BWP of the SDT to the initial active UL BWP of the cell), for example, when no new BWP configuration, such as a new BWP configuration in the masterCellGroup, is provided in the RRCResume message. Alternatively and / or in addition, in response to unsuccessful completion of the SDT procedure via the RRCSetup message, the UE (e.g., the MAC layer of the UE) may switch the active UL BWP back to the initial UL BWP of the cell (e.g., the MAC layer of the UE may switch the active UL BWP from a dedicated UL BWP for SDT to the initial active UL BWP of the cell), for example when a new BWP configuration, such as a new BWP configuration in a masterCellGroup, is not provided in the RRCSetup message.

[0691] In a situation where the one or more dedicated UL BWPs of SDT are configured for a cell and the initial UL BWP of the cell can also be used for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may select (e.g., randomly select) a UL BWP (e.g., one UL BWP) among the one or more dedicated UL BWPs and the initial UL BWP (e.g., the UE may select, e.g., randomly select, a dedicated UL BWP or the initial UL BWP among the one or more dedicated UL BWPs). In the case where the one or more dedicated UL BWPs of the SDT are configured for the cell and the initial UL BWP of the cell can also be used for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may prioritize the one or more dedicated UL BWPs of the SDT over the initial UL BWP (e.g., based on prioritizing the one or more dedicated UL BWPs of the SDT over the initial UL BWP, the UE may select the dedicated UL BWP of the one or more dedicated UL BWPs of the SDT instead of the initial UL BWP), or the UE may prioritize the initial UL BWP over the one or more dedicated UL BWPs of the SDT (e.g., based on prioritizing the initial UL BWP over the one or more dedicated UL BWPs of the SDT, the UE may select the initial UL BWP instead of the dedicated UL BWP of the one or more dedicated UL BWPs of the SDT). In some examples, the priority ranking (e.g., the priority ranking of the one or more dedicated UL BWPs of the SDT over the initial UL BWP or the priority ranking of the initial UL BWP over the one or more dedicated UL BWPs of the SDT) may be based on the UE category of the UE and / or the UE type of the UE. For example, if the UE is a first type of UE, the UE may prioritize the one or more dedicated UL BWPs of the SDT over the initial UL BWP, and / or if the UE is a second type of UE, the UE may prioritize the initial UL BWP over the one or more dedicated UL BWPs of the SDT. In a case where the one or more dedicated UL BWPs of the SDT are configured for a cell and the initial UL BWP of the cell may also be used for the SDT procedure (e.g., where the RA resources of the SDT are configured on the initial UL BWP), the UE may select a UL BWP (e.g., one UL BWP) from among the one or more dedicated UL BWPs of the SDT and the initial UL BWP based on an indication (e.g., the network may instruct and / or instruct the UE to perform the SDT procedure using the one or more dedicated UL BWPs of the SDT or the initial UL BWP) (e.g., the UE may select the dedicated UL BWP or the initial UL BWP from among the one or more dedicated UL BWPs of the SDT based on the indication).For example, if the indication indicates that the SDT procedure is performed using the one or more dedicated UL BWPs of the SDT (and / or if the indication indicates that the SDT procedure is performed using a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT), the UE may select a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT. Alternatively and / or additionally, if the indication indicates that the SDT procedure is performed using an initial UL BWP, the UE may select the initial UL BWP. The indication may be included in a dedicated RRC message transmitted to the UE (e.g., the indication may be included in an RRCRelease message). If the UE selects a dedicated UL BWP in the one or more dedicated UL BWPs of the SDT, the UE may perform the SDT procedure using the dedicated UL BWP. Alternatively and / or additionally, if the UE selects the initial UL BWP, the UE may perform the SDT procedure using the initial UL BWP.

[0692] In some instances, for example, in addition to the initial UL BWP becoming congested, the initial DL BWP of the cell may also become congested (for example, if there are more than a threshold number of UEs performing SDT procedures at the same time). In some instances (for example, instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept), in order to solve the problem (for example, the initial DL BWP becomes congested), the DL BWP of SDT may be used, for example, by using one or more techniques discussed herein with respect to using the UL BWP of SDT (and / or by using one or more techniques similar to the one or more techniques discussed herein with respect to using the UL BWP of SDT). In some instances, the DL BWP of SDT (for example, one DL BWP of SDT) may be paired with the UL BWP of SDT (for example, one UL BWP of SDT), wherein the configuration of the DL BWP of SDT and the configuration of the UL BWP of SDT may be provided together (for example, the configuration of the DL BWP of SDT and the configuration of the UL BWP of SDT may be provided together to the UE). Alternatively and / or in addition, the DL BWP of the SDT (e.g., one DL BWP of the SDT) may be paired with a set of UL BWPs of the SDT, wherein the configuration of the DL BWP of the SDT and the configuration of the set of UL BWPs of the SDT may be provided together (e.g., the configuration of the DL BWP of the SDT and the configuration of the set of UL BWPs of the SDT may be provided to the UE together). In some examples, the UE may determine to use the DL BWP of the SDT based on determining that the DL BWP of the SDT is paired with the UL BWP of the SDT. For example, the UE may determine to use the UL BWP of the SDT (e.g., for the SDT procedure), and / or the UE may determine to use the DL BWP of the SDT (e.g., for the SDT procedure) after (and / or in response to) determining to use the UL BWP of the SDT. The UE may switch the active DL BWP (e.g., from an initial DL BWP) to the DL BWP of the SDT paired with the UL BWP of the SDT. For example, the UE may switch the active DL BWP (eg, from the initial DL BWP) to the DL BWP of the SDT after (and / or while) switching the active UL BWP (eg, from the initial UL BWP) to the UL BWP of the SDT.In some instances, in response to successfully completing the SDT procedure through the RRCRelease message (and / or after successful completion) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE may switch the active DL BWP (e.g., from the DL BWP of the SDT) back to the initial DL BWP of the cell (e.g., the initial active DL BWP). Alternatively and / or in addition, in response to successfully completing the SDT procedure through the RRCResume message (e.g., successful completion of the SDT procedure) (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at the time when the UE believes that there are no other subsequent transmissions of the SDT procedure and / or after that, etc.), the UE may maintain use (e.g., continue to use) the DL BWP of the SDT (e.g., if no new BWP configuration is provided in the RRCResume message, such as a new BWP configuration in the masterCellGroup, then the UE may maintain use of the DL BWP of the SDT). Alternatively and / or additionally, if the DL BWP of SDT is not configured for the cell and if the UL BWP of SDT is configured for the cell, the UE performs the SDT procedure on the cell using the initial DL BWP and the UL BWP of SDT. Alternatively and / or additionally, if both the DL BWP of SDT and the UL BWP of SDT are configured for the cell, the UE performs the SDT procedure on the cell using the DL BWP of SDT and the UL BWP of SDT.

[0693] In some instances (e.g., instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the fifth concept, the sixth concept, and / or the seventh concept), after the UE selects a UL BWP to be used (e.g., in an SDT procedure), the UE may perform the SDT procedure using the selected UL BWP (and / or the UE may use the selected UL BWP until the SDT procedure is completed). Alternatively and / or in addition, after the UE selects the UL BWP to be used, the UE may perform a (subsequent) selection of the UL BWP in response to an event. In some instances, the event may correspond to an unsuccessful preamble transmission (e.g., the event may include the occurrence of an unsuccessful preamble transmission, such as an unsuccessful transmission of Msg1 and / or MsgA). Alternatively and / or in addition, the event corresponds to a preamble transmission (e.g., the transmission of Msg1 and / or MsgA) being performed multiple times without success, such as more than a threshold number of times. Alternatively and / or in addition, the event may correspond to the occurrence of an unsuccessful contention resolution. Alternatively and / or additionally, the event may correspond to contention resolution being unsuccessfully performed a number of times, such as more than a threshold number of times.

[0694] In some instances (e.g., instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the fifth concept, the sixth concept, and / or the seventh concept), a timer may be used (and / or introduced) for an SDT procedure on a UL BWP of an SDT. In an instance, the UE may be configured to use a timer. In some instances, the UE may start a timer in response to the initiation of the SDT procedure (and / or after the initiation). Alternatively and / or in addition, the UE may start a timer in response to selecting a UL BWP other than the initial UL BWP (e.g., the UL BWP of the SDT) (and / or after the selection). The UE may stop the timer in response to the successful completion (and / or after the successful completion) of the SDT procedure (e.g., at the time of and / or after the last transmission of one or more subsequent transmissions of the SDT procedure, and / or at and / or after the time when the UE considers that there are no other subsequent transmissions of the SDT procedure, etc.). In some instances, the UE may consider that the SDT procedure has not been successfully completed in response to the expiration of the timer (and / or after the expiration). The UE may fall back to (and / or initiate and / or perform) an RRC resumption procedure (eg, a legacy RRC resumption procedure) on the initial UL BWP (and / or initial DL BWP) in response to (and / or after) expiration of the timer.

[0695] In some examples (e.g., examples of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept), the UE may perform (e.g., transmit) one or more subsequent UL transmissions (e.g., the second UL transmission) of the SDT procedure using the first UL BWP for the first UL transmission for performing the SDT procedure (e.g., the UE may continue to use the first UL BWP to perform the one or more subsequent UL transmissions of the SDT procedure). Alternatively and / or in addition, the UE may perform the one or more subsequent UL transmissions (e.g., the second UL transmission) of the SDT procedure using the second UL BWP (e.g., different from the first UL BWP for performing the first UL transmission). For example, the network may indicate and / or instruct the UE to use the second UL BWP (e.g., for performing the one or more subsequent UL transmissions) (e.g., via the first DL transmission of the SDT procedure after the first UL transmission). Alternatively and / or in addition, the network may indicate in an RRC message (e.g., without reconfiguring the BWP configuration of the UE) the UL BWP to be used to perform the one or more subsequent UL transmissions. If the network does not indicate in the RRC message the UL BWP to be used to perform the one or more subsequent UL transmissions, the UE may continue to use the first UL BWP (e.g., for the first UL transmission) to perform the one or more subsequent UL transmissions (e.g., the UE may not perform a BWP switch between the first UL transmission and the one or more subsequent UL transmissions). Alternatively and / or in addition, the UE may perform the one or more subsequent UL transmissions using the initial UL BWP. In the case where the UL BWP for the one or more subsequent UL transmissions is different from the first UL BWP for the first UL transmission, the UE may perform a BWP switch. The RRC message may be an RRCRelease message. Alternatively and / or in addition, the RRC message may be an RRC message different from the RRCRelease message.

[0696] In some examples (e.g., examples of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept), the UE may perform (e.g., receive) one or more subsequent DL transmissions (e.g., the second DL transmission) of the SDT procedure using the first DL BWP for the first UL transmission for performing the SDT procedure (e.g., the UE may continue to perform the one or more subsequent DL transmissions of the SDT procedure using the first DL BWP). Alternatively and / or in addition, the UE may perform the one or more subsequent DL transmissions (e.g., the second DL transmission) of the SDT procedure using a second DL BWP (e.g., different from the first DL BWP for performing the first DL transmission). For example, the network may indicate and / or instruct the UE to use the second DL BWP (e.g., for performing the one or more subsequent DL transmissions) (e.g., via the first DL transmission of the SDT procedure after the first UL transmission). Alternatively and / or in addition, the network may indicate in an RRC message (e.g., without reconfiguring the BWP configuration of the UE) which DL BWP will be used to perform the one or more subsequent DL transmissions. If the network does not indicate the DL BWP to be used to perform the one or more subsequent DL transmissions in the RRC message, the UE may continue to use the first UL BWP (e.g., used for the first DL transmission) to perform the one or more subsequent DL transmissions (e.g., the UE may not perform a BWP switch between the first DL transmission and the one or more subsequent DL transmissions). Alternatively and / or additionally, the UE may perform the one or more subsequent DL transmissions using the initial DL BWP. Alternatively and / or additionally, the UE may perform the one or more subsequent DL transmissions (e.g., the second DL transmission) using a DL BWP paired with the UL BWP used by the UE to perform the one or more subsequent UL transmissions. In the case where the DL BWP used for the one or more subsequent DL transmissions is different from the first DL BWP used for the first DL transmission, the UE may perform a BWP switch. The RRC message may be an RRCRelease message. Alternatively and / or additionally, the RRC message may be an RRC message different from the RRCRelease message.

[0697] In some instances (e.g., instances of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept), a timer may be introduced to control the completion of the SDT procedure and / or the one or more subsequent transmissions of the SDT procedure (e.g., including the one or more subsequent UL transmissions of the SDT procedure and / or the one or more subsequent DL transmissions of the SDT procedure). For example, the UE may start and / or restart the timer in response to performing the first subsequent UL transmission (and / or after the execution). In some instances, if the first subsequent UL transmission is “ACKed” (e.g., if the UE receives an ACK indication associated with the first subsequent UL transmission), and if no other subsequent DL transmissions are received before the timer expires, the UE may deem that there are no other subsequent transmissions (of the SDT procedure), and the SDT procedure may be considered to be completed (e.g., the UE may determine that the SDT procedure is completed after the timer expires). Alternatively and / or in addition, the UE may start and / or restart the timer in response to receiving the first subsequent DL transmission (and / or after the reception). In some instances, if no other UL data arrives (e.g., arrives at the UE) after the first subsequent DL transmission and before the expiration of the timer, the UE may consider that there are no other subsequent transmissions (of the SDT procedure) and may consider the SDT procedure to be completed (e.g., the UE may determine that the SDT procedure is completed after the expiration of the timer).

[0698] In some examples (e.g., examples of one or more embodiments discussed herein, such as one or more embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept), the network may indicate to the UE whether there are one or more other subsequent transmissions (e.g., of the SDT procedure). For example, after the UE performs a first subsequent UL transmission, the network may indicate to the UE (e.g., via a message transmitted to the UE, such as via downlink control information (DCI), a MAC control element (CE), or an RRC message) that there are no other subsequent transmissions (e.g., of the SDT procedure). Alternatively and / or in addition, after the UE receives the first subsequent DL transmission (and / or after the UE receives it), the network may indicate to the UE (e.g., via a message transmitted to the UE, such as via a DCI, a MAC CE, or an RRC message) that there are no other subsequent transmissions (e.g., of the SDT procedure). In response to receiving an indication indicating that there are no other subsequent transmissions (e.g., of the SDT procedure), the UE may deem that there are no other subsequent transmissions (e.g., of the SDT procedure), and may deem that the SDT procedure is completed. Alternatively and / or additionally, if the UE does not receive an indication (e.g., the indication is not present in the DL transmission), the UE may consider that there are one or more other subsequent transmissions (e.g., of the SDT procedure). Alternatively and / or additionally, if the UE does not receive an indication (e.g., the indication is not present in the DL transmission), the UE may consider that there are no other subsequent transmissions (e.g., of the SDT procedure) and may consider the SDT procedure to be completed.

[0699] One or more techniques and / or systems of the present disclosure may be applicable to (and / or implemented using and / or supported by) a reduced-capability NR device (and / or NR_Light device). One or more techniques and / or systems of the present disclosure may be applicable to (and / or implemented using and / or supported by) a NR device (and / or NR_Light device) other than a reduced-capability NR device and / or NR_Light device (e.g., a normal NR device).

[0700] The UE may initiate the SDT procedure on a serving cell other than the last serving cell in the RRC_CONNECTED state (e.g., the primary serving cell), such as the most recently used serving cell in the RRC_CONNECTED state (e.g., the primary serving cell). Alternatively and / or in addition, the UE may initiate the SDT procedure on the same serving cell as the last serving cell in the RRC_CONNECTED state.

[0701] In some instances, the pre-configured PUSCH resources discussed with respect to one or more embodiments of the present disclosure may be a configured grant (e.g., a type 1 configured grant), such as a configured grant in NR (e.g., a type 1 configured grant).

[0702] One, some and / or all of the above-mentioned techniques and / or embodiments may be formed into new embodiments.

[0703] In some examples, the embodiments disclosed herein may be implemented independently and / or individually, such as the embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and the seventh concept. Alternatively and / or in addition, a combination of the embodiments described herein may be implemented, such as a combination of the embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept. Alternatively and / or in addition, a combination of the embodiments described herein may be implemented in parallel and / or simultaneously, such as a combination of the embodiments described with respect to the first concept, the second concept, the third concept, the fourth concept, the fifth concept, the sixth concept, and / or the seventh concept.

[0704] The various techniques of the present disclosure may be performed independently and / or separately from each other. Alternatively and / or in addition, the various techniques of the present disclosure may be combined and / or implemented using a single system. Alternatively and / or in addition, the various techniques of the present disclosure may be implemented in parallel and / or simultaneously.

[0705] Fig.21 2100 is a flowchart according to an exemplary embodiment from the perspective of a UE. In step 2105, the UE receives an RRCRelease message from a network node indicating a suspension of an RRC connection (e.g., an RRC connection between the UE and the network node). In step 2110, the UE enters the RRC_INACTIVE state in response to receiving the RRCRelease message. In step 2115, the UE initiates an SDT procedure in the RRC_INACTIVE state. In step 2120, in response to initiating the SDT procedure, the UE selects a first UL BWP to be used for the SDT procedure. In step 2125, during the SDT procedure, the UE transmits first UL data and a first RRC message to the network node on the first UL BWP. In step 2130, after transmitting the first UL data and the first RRC message, the UE selects a second UL BWP to be used for the SDT procedure. In step 2135, during the SDT procedure, the UE transmits second UL data to the network node on the second UL BWP.

[0706] In one embodiment, the SDT procedure is an SDT procedure based on pre-configured PUSCH resources.

[0707] In one embodiment, the SDT procedure is a RACH-based SDT procedure.

[0708] In one embodiment, in response to transmitting the first UL data and / or the first RRC message, the UE receives a first indication from the network node on the first DL BWP.

[0709] In one embodiment, in response to transmitting the second UL data and the second RRC message, the UE receives a second indication from the network node on the second DL BWP.

[0710] In one embodiment, the first indication and / or the second indication indicates whether there are one or more subsequent UL transmissions to be performed (e.g., the first indication and / or the second indication indicates whether there are one or more subsequent UL transmissions to be transmitted for the SDT procedure and / or to be transmitted during the SDT procedure).

[0711] In one embodiment, the first indication and / or the second indication indicates whether there are one or more subsequent DL transmissions to be performed (e.g., the first indication and / or the second indication indicates whether there are one or more subsequent DL transmissions to be received for the SDT procedure and / or to be received during the SDT procedure).

[0712] In one embodiment, the first indication is a DCI, a MAC CE or an RRC message.

[0713] In one embodiment, the second indication is a DCI, a MAC CE or an RRC message.

[0714] In one embodiment, the UE receives the second RRC message and the first indication on the first DL BWP.

[0715] In one embodiment, the UE receives the second RRC message and the second indication on the second DL BWP.

[0716] In one embodiment, the first UL BWP is configured in (and / or by) the RRCRelease message. For example, the UE may be configured to use the first UL BWP via the RRCRelease message.

[0717] In one embodiment, the first UL BWP is configured in (and / or by) system information. For example, the UE may be configured to use the first UL BWP via system information.

[0718] In one embodiment, the first UL BWP is not an initial UL BWP (eg, the first UL BWP is not an initial UL BWP for the UE).

[0719] In one embodiment, the UE selects a first UL BWP from a plurality of UL BWPs for the SDT procedure.

[0720] In one embodiment, the first DL BWP is configured in (and / or by) the RRCRelease message. For example, the UE may be configured to use the first DL BWP via the RRCRelease message.

[0721] In one embodiment, the first DL BWP is configured in system information. For example, the UE may be configured to use the first DL BWP via system information.

[0722] In one embodiment, the first DL BWP is paired with the first UL BWP.

[0723] In one embodiment, the first DL BWP is not an initial DL BWP (eg, the first DL BWP is not an initial DL BWP for the UE).

[0724] In one embodiment, the second UL BWP is configured in (and / or by) the RRCRelease message. For example, the UE may be configured to use the second UL BWP via the RRCRelease message.

[0725] In one embodiment, the second UL BWP is configured in (and / or by) system information. For example, the UE may be configured to use the second UL BWP via system information.

[0726] In one embodiment, the second UL BWP is the same as the first UL BWP (and / or the UE selects the second UL BWP by selecting the same UL BWP as the first UL BWP).

[0727] In one embodiment, the second UL BWP is the initial UL BWP (and / or the UE selects the second UL BWP by selecting the initial UL BWP).

[0728] In one embodiment, the second DL BWP is configured in (and / or by) the RRCRelease message. For example, the UE may be configured to use the second DL BWP via the RRCRelease message.

[0729] In one embodiment, the second DL BWP is configured in (and / or by) system information. For example, the UE may be configured to use the second DL BWP via system information.

[0730] In one embodiment, the second DL BWP is paired with the second UL BWP.

[0731] In one embodiment, in response to selecting the first UL BWP, the UE switches the UE's active UL BWP from an initial UL BWP to the first UL BWP before transmitting on the first UL BWP.

[0732] In one embodiment, in response to selecting the first UL BWP, the UE switches the UE's active DL BWP from an initial DL BWP to the first DL BWP before transmitting on the first UL BWP.

[0733] In one embodiment (eg, where the second UL BWP is different than the first UL BWP), in response to selecting the second UL BWP, the UE switches the UE's active UL BWP from the first UL BWP to the second UL BWP before transmitting on the second UL BWP.

[0734] In one embodiment (eg, where the second UL BWP is different than the first UL BWP), in response to selecting the second UL BWP, the UE switches the UE's active DL BWP from the first DL BWP to the second DL BWP before transmitting on the second UL BWP.

[0735] In one embodiment, the first RRC message is a RRCResumeRequest message.

[0736] In one embodiment, the second RRC message is an RRCRelease message (eg, a second RRCRelease message), and the UE remains in the RRC_INACTIVE state in response to receiving the second RRC message.

[0737] In one embodiment, the second RRC message is an RRC Resume message, and the UE enters the RRC_CONNECTED state in response to receiving the second RRC message.

[0738] In one embodiment, the UE switches the active UL BWP of the UE from the first UL BWP to the initial UL BWP in response to receiving the second RRC message.

[0739] In one embodiment, the UE does not switch the UE's active UL BWP from the first UL BWP to the initial UL BWP in response to receiving the second RRC message.

[0740] In one embodiment (eg, where the SDT procedure is an SDT procedure based on pre-configured PUSCH resources), the UE transmits first UL data and a first RRC message on a first UL BWP using the pre-configured PUSCH resources.

[0741] In one embodiment (e.g., where the SDT procedure is a RACH-based SDT procedure), the UE transmits the first UL data and the first RRC message after (and / or in response to and / or after) transmitting a random access preamble on a first UL BWP using PRACH resources.

[0742] In one embodiment, based on the second RRC message, the UE regards the SDT procedure as completed (eg, in response to and / or after receiving the second RRC message, the UE regards the SDT procedure as completed).

[0743] In one embodiment, based on an indication (e.g., a first indication or a second indication) indicating that there is neither a subsequent UL transmission (e.g., for the SDT procedure) nor a subsequent DL transmission (e.g., for the SDT procedure), the UE considers the SDT procedure to be completed. For example, the UE may consider the SDT procedure to be completed in response to and / or after receiving the indication.

[0744] Return to reference Figure 3 and 4 In an exemplary embodiment of the UE, the apparatus 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to: (i) receive an RRCRelease message indicating a suspension of the RRC connection from the network node, (ii) enter the RRC_INACTIVE state in response to receiving the RRCRelease message, (iii) initiate an SDT procedure (e.g., an SDT procedure based on preconfigured PUSCH resources or an SDT procedure based on RACH) in the RRC_INACTIVE state, (iv) select a first UL BWP to be used for the SDT procedure in response to initiating the SDT procedure, (v) transmit first UL data and a first RRC message to the network node on the first UL BWP during the SDT procedure, (vi) select a second UL BWP to be used for the SDT procedure after transmitting the first UL data and the first RRC message, and (vii) transmit second UL data to the network node on the second UL BWP during the SDT procedure. Furthermore, CPU 308 may execute program code 312 to perform one, some, and / or all of the actions and steps described above and / or other actions and steps described herein.

[0745] Fig. 222200 is a flowchart according to an exemplary embodiment from the perspective of a UE. In step 2205, the UE receives a first RRC message from a network node, wherein the first RRC message indicates a first UL BWP of a cell. In step 2210, in response to initiation of a procedure using configured grant (CG) resources in an RRC inactive state (e.g., RRC_INACTIVE state), the UE performs a BWP switch from a second UL BWP of the cell to a first UL BWP of the cell (e.g., the UE may switch the active UL BWP from the second UL BWP of the cell to the first UL BWP of the cell). In step 2215, the UE performs a first UL transmission on the first UL BWP using the CG resources. In step 2220, in response to completion of the procedure, the UE performs a BWP switch from the first UL BWP of the cell to the second UL BWP of the cell (e.g., the UE may switch the active UL BWP from the first UL BWP of the cell to the second UL BWP of the cell).

[0746] In one embodiment, the program is a SDT program.

[0747] In one embodiment, the second UL BWP is an initial UL BWP. In an example, the initial UL BWP may be a UL BWP used by the UE for initial access (eg, with a cell). Alternatively and / or additionally, the initial UL BWP may be a UL BWP used by the UE to activate a cell.

[0748] In one embodiment, the first UL BWP is configured by a first RRC message (eg, the UE is configured to use the first UL BWP through the first RRC message).

[0749] In one embodiment, the first UL BWP is a UL BWP (e.g., one UL BWP) among one or more BWPs used by the UE when the UE is in an RRC connected state (e.g., RRC_CONNECTED state). For example, the UE uses the one or more UL BWPs including the first UL BWP before the procedure is initiated in the RRC connected state. For example, the one or more UL BWPs may be used to perform one or more UL transmissions in the RRC connected state.

[0750] In one embodiment, the UE enters the RRC inactive state in response to receiving a first RRC message, wherein the first RRC message is an RRC Release message.

[0751] In one embodiment, the UE receives a second RRC message, wherein based on the second RRC message, the UE considers the procedure to be completed. For example, in response to (and / or after) receiving the second RRC message, the UE may consider the procedure to be completed.

[0752] In one embodiment, the UE remains in the RRC inactive state in response to receiving a second RRC message, wherein the second RRC message is a RRC Release message.

[0753] In one embodiment, the first RRC message indicates a first DL BWP of the cell, and the UE performs a BWP switch from a second DL BWP of the cell to the first DL BWP of the cell in response to the initiation of the procedure (e.g., the UE may switch the active UL BWP from the second DL BWP of the cell to the first DL BWP of the cell). The second DL BWP may be an initial DL BWP. In an example, the initial DL BWP may be a DL BWP used by the UE for initial access (e.g., with the cell). Alternatively and / or in addition, the initial DL BWP may be a DL BWP used by the UE to activate the cell.

[0754] In one embodiment, the first RRC message indicates a first DL BWP of the cell, and the UE performs a BWP switch from the first DL BWP of the cell to a second DL BWP of the cell in response to completion of the procedure (e.g., the UE may switch the active UL BWP from the first DL BWP of the cell to the second DL BWP of the cell). The second DL BWP may be an initial DL BWP. In an example, the initial DL BWP may be a DL BWP used by the UE for initial access (e.g., with the cell). Alternatively and / or in addition, the initial DL BWP may be a DL BWP used by the UE to activate the cell.

[0755] In one embodiment, the UE performs a second UL transmission using CG resources on the first UL BWP during the procedure.

[0756] In one embodiment, the UE starts a timer in response to the initiation of the procedure. The UE performs (and / or falls back to) an RRC recovery procedure on the second UL BWP in response to expiration of the timer.

[0757] In one embodiment, the first RRC message indicates a CG resource.

[0758] Return to reference Figure 3 and 4In an exemplary embodiment of the UE, the apparatus 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to: (i) receive a first RRC message from a network node, wherein the first RRC message indicates a first UL BWP of a cell, (ii) in response to initiation of a procedure using CG resources in an RRC inactive state (e.g., RRC_INACTIVE state), perform a BWP switch from a second UL BWP of the cell to a first UL BWP of the cell, (iii) perform a first UL transmission using CG resources on the first UL BWP, and (iv) in response to completion of the procedure, perform a BWP switch from the first UL BWP of the cell to a second UL BWP of the cell. In addition, the CPU 308 can execute the program code 312 to perform one, some and / or all of the above actions and steps and / or other actions and steps described herein.

[0759] A communication device (e.g., UE, base station, network node, etc.) may be provided, wherein the communication device may include a control circuit, a processor installed in the control circuit, and / or a memory installed in the control circuit and coupled to the processor. The processor may be configured to execute a program code stored in the memory to perform Figure 21-22 In addition, the processor may execute program code to perform one, some and / or all of the above actions and steps and / or other actions and steps described herein.

[0760] A computer readable medium may be provided. The computer readable medium may be a non-transitory computer readable medium. The computer readable medium may include a flash memory device, a hard drive, a disk (e.g., a magnetic disk and / or an optical disk, such as at least one of a digital versatile disk (DVD), a compact disk (CD), etc.), and / or a memory semiconductor, such as at least one of a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), etc. The computer readable medium may include processor executable instructions that, when executed, cause the processor to execute a program that performs a program execution. Figure 21-22 One, some and / or all of the method steps shown in and / or one, some and / or all of the actions and steps described above and / or other actions and steps described herein are performed.

[0761] It should be appreciated that applying one or more of the techniques presented herein may result in one or more benefits, including but not limited to improved communication efficiency between devices (e.g., UEs and / or network nodes). The efficiency improvement may be due to a reduced load on the initial UL BWP of a cell supporting SDT (which may reduce power consumption of one or more UEs and / or faster communication between a network node and one or more UEs, etc.).

[0762] Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example 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.

[0763] 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 voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0764] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction 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 may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled 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.

[0765] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. An 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, outside 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, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0766] 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 an exemplary order, but are not meant to be limited to the specific order or hierarchy presented.

[0767] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., including executable instructions and related data) and other data may reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium may be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to as a "processor" in this article) 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 may be integrated with a processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and the storage medium may reside in a user device as discrete components. Alternatively or additionally, in some aspects, any suitable computer program product may include a computer-readable medium, which includes a code related to one or more aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0768] Although the disclosed subject matter has been described in conjunction with various aspects, it will be understood that the disclosed subject matter is capable of further modification. This application is intended to cover any changes, uses, or adaptations of the disclosed subject matter that generally follow the principles of the disclosed subject matter and include such deviations from the present disclosure as come within the scope of known and customary practice in the art to which the disclosed subject matter belongs.

[0769] CROSS-REFERENCE TO RELATED APPLICATIONS

[0770] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 052,195, filed on July 15, 2020, the entire disclosure of which is incorporated herein by reference in its entirety. This application also claims the benefit of U.S. Provisional Patent Application No. 63 / 052,217, filed on July 15, 2020, the entire disclosure of which is incorporated herein by reference in its entirety.

Claims

1. A method of a user device, It is characterized in that The method comprises: receiving system information from a network node, wherein the system information indicates an initial uplink bandwidth portion of a cell and an initial downlink bandwidth portion of the cell; If the system information configures a first uplink bandwidth part different from the initial uplink bandwidth part, performing a random access procedure in the first uplink bandwidth part in a radio resource control inactive state; If the system information does not configure the first uplink bandwidth part, performing the random access procedure in the initial uplink bandwidth part in the radio resource control inactive state; If the system information configures a first downlink bandwidth part different from the initial downlink bandwidth part, performing the random access procedure in the first downlink bandwidth part in the radio resource control inactive state; and If the system information does not configure the first downlink bandwidth part, the random access procedure is performed on the initial downlink bandwidth part in the radio resource control inactive state.

2. The method according to claim 1, It is characterized in that The frequency bandwidth of the first uplink bandwidth portion is different from the frequency bandwidth of the initial uplink bandwidth portion.

3. The method according to claim 1, It is characterized in that The system information is SIB1 of the cell.

4. The method according to claim 1, It is characterized in that The center frequency of the first uplink bandwidth portion is different from the center frequency of the initial uplink bandwidth portion.

5. The method according to claim 1, It is characterized in that The center frequency of the first uplink bandwidth portion is the same as the center frequency of the initial uplink bandwidth portion.

6. The method according to claim 1, It is characterized in that include: The radio resource control inactive state is entered in response to receiving a first radio resource control message, wherein the first radio resource control message is a RRCRelease message.

7. The method according to claim 1, It is characterized in that The random access procedure is used for small data transmission.

8. A user device, It is characterized in that include: Control circuit; a processor installed in the control circuit; as well as a memory installed in the control circuit and operably coupled to the processor, wherein the processor is configured to execute program code stored in the memory to perform operations, the operations comprising: receiving system information from a network node, wherein the system information indicates an initial uplink bandwidth portion of a cell and an initial downlink bandwidth portion of the cell; If the system information configures a first uplink bandwidth part different from the initial uplink bandwidth part, performing a random access procedure in the first uplink bandwidth part in a radio resource control inactive state; If the system information does not configure the first uplink bandwidth part, performing the random access procedure in the initial uplink bandwidth part in the radio resource control inactive state; If the system information configures a first downlink bandwidth part different from the initial downlink bandwidth part, performing the random access procedure in the first downlink bandwidth part in the radio resource control inactive state; and If the system information does not configure the first downlink bandwidth part, the random access procedure is performed on the initial downlink bandwidth part in the radio resource control inactive state.

9. The user equipment according to claim 8, It is characterized in that The frequency bandwidth of the first uplink bandwidth portion is different from the frequency bandwidth of the initial uplink bandwidth portion.

10. The user equipment according to claim 8, It is characterized in that The system information is SIB1 of the cell.

11. The user equipment according to claim 8, It is characterized in that The center frequency of the first uplink bandwidth portion is different from the center frequency of the initial uplink bandwidth portion.

12. The user equipment according to claim 8, It is characterized in that The center frequency of the first uplink bandwidth portion is the same as the center frequency of the initial uplink bandwidth portion.

13. The user equipment according to claim 8, It is characterized in that The operations include: The radio resource control inactive state is entered in response to receiving a first radio resource control message, wherein the first radio resource control message is a RRCRelease message.

14. The user equipment according to claim 8, It is characterized in that The random access procedure is used for small data transmission.

15. A method of a user device, It is characterized in that The method comprises: receiving system information from a network node, wherein the system information indicates an initial uplink bandwidth portion of a cell and an initial downlink bandwidth portion of the cell; If the system information has configured a first uplink bandwidth portion different from the initial uplink bandwidth portion, performing a first procedure for small data transmission in the first uplink bandwidth portion using the configured granted resources in a radio resource control inactive state; If the system information does not configure the first uplink bandwidth portion, performing the first procedure for small data transmission in the initial uplink bandwidth portion using the configured granted resources in the radio resource control inactive state; If the system information configures a first downlink bandwidth portion different from the initial downlink bandwidth portion, performing the first procedure for small data transmission using the configured granted resources in the first downlink bandwidth portion in the radio resource control inactive state; and If the first downlink bandwidth portion is not configured by the system information, the first procedure for small data transmission is performed in the initial downlink bandwidth portion using the configured granted resources in the radio resource control inactive state.

16. The method according to claim 15, It is characterized in that The frequency bandwidth of the first uplink bandwidth portion is different from the frequency bandwidth of the initial uplink bandwidth portion.

17. The method according to claim 15, It is characterized in that The system information is SIB1 of the cell.

18. The method according to claim 15, It is characterized in that include: The center frequency of the first uplink bandwidth portion is different from or the same as the center frequency of the initial uplink bandwidth portion.

19. The method according to claim 15, It is characterized in that include: The radio resource control inactive state is entered in response to receiving a first radio resource control message, wherein the first radio resource control message is a RRCRelease message.

20. The method according to claim 19, It is characterized in that include: The first radio resource control message indicates the configured grant resources.

Images