WO2022205344A1

WO2022205344A1 - Method and apparatus for handling arrival of non-small data transmission

Info

Publication number: WO2022205344A1
Application number: PCT/CN2021/085035
Authority: WO
Inventors: Jie Shi; Haiming Wang; Lianhai WU; Ran YUE; Jing HAN
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2021-04-01
Filing date: 2021-04-01
Publication date: 2022-10-06
Anticipated expiration: 2023-10-01

Abstract

The present application relates to a method and an apparatus for handling arrival of non-SDT data transmission. The method includes: determining that a non-SDT data is to be transmitted to a BS during a SDT procedure; and transmitting an RRC resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure.

Description

METHOD AND APPARATUS FOR HANDLING ARRIVAL OF NON-SMALL DATA TRANSMISSION

TECHNICAL FIELD

Embodiments of the present application generally relate to wireless communication technology, especially to a method and an apparatus for handling arrival of non-small data transmission (SDT) under 3GPP (3rd Generation Partnership Project) 5G New Radio (NR) .

BACKGROUND

In conventional network, different services (e.g., different applications) between base station and user equipment may be performed with different types of data transmissions. Some of the services may be performed with small data transmission (SDT) when the user equipment is under an inactive mode. During a SDT procedure, non-SDT data (e.g., data that could not be transmitted as SDT data) may be arrived. In other words, the non-SDT data may be ready to be transmitted to the base station during the SDT procedure. However, specific details of handling the arrival of non-SDT data during the SDT procedure have not been discussed yet and there are still some issues that need to be solved.

SUMMARY

Some embodiments of the present application provide a method for a user equipment (UE) . The method includes: determining that a non-small data transmission (SDT) data is to be transmitted to a base station (BS) during a SDT procedure; and transmitting a radio resource control (RRC) resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure, wherein the at least one stage includes: that a random access channel (RACH) preamble for SDT data is transmitted; that a random access response (RAR) message is monitored; receiving the RAR message from the BS; preparing an RRC resume request for initialing the SDT procedure; that the RRC resume request for initialing the SDT procedure is transmitted without receiving an RRC response message for the SDT procedure from the BS; being in an initial SDT procedure; being in a subsequence of the SDT procedure; or that no granted uplink resource of the SDT procedure is available.

Some embodiments of the present application provide an apparatus. The apparatus includes: a non-transitory computer-readable medium having stored thereon computer-executable instructions; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the abovementioned method for wireless communications.

The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which advantages and features of the application can be obtained, a description of the application is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only example embodiments of the application and are not therefore to be considered limiting of its scope.

FIG. 1 illustrates a schematic diagram of a wireless communication system in accordance with some embodiments of the present application.

FIG. 2 illustrates a schematic diagram of message transmissions in accordance with some embodiments of the present application.

FIG. 3A illustrates a schematic diagram of message transmissions in accordance with some embodiments of the present application.

FIG. 3B illustrates a schematic diagram of message transmissions in accordance with some embodiments of the present application.

FIG. 4 illustrates a flow chart of a method for wireless communications according to an embodiment of the present disclosure.

FIG. 5 illustrates a flow chart of a method for wireless communications according to an embodiment of the present disclosure.

FIG. 6 illustrates a flow chart of a method for wireless communications according to an embodiment of the present disclosure.

FIGS. 7A and 7B illustrate flow charts of a method for wireless communications according to an embodiment of the present disclosure.

FIGS. 9A and 9C illustrate flow charts of a method for wireless communications according to an embodiment of the present disclosure.

FIG. 10 illustrates a flow chart of a method for wireless communications according to an embodiment of the present disclosure.

FIG. 11 illustrates a block diagram of an exemplary apparatus in accordance with some embodiments of the present application.

DETAILED DESCRIPTION

The detailed description of the appended drawings is intended as a description of preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.

Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. Embodiments of the present application may be provided in a network architecture that adopts various service scenarios, for example but is not limited to, 3GPP 3G, long-term evolution (LTE) , LTE-Advanced (LTE-A) , 3GPP 4G, 3GPP 5G NR (new radio) , etc. It is contemplated that along with the 3GPP and related communication technology development, the terminologies recited in the present application may change, which should not affect the principle of the present application.

Referring to FIG. 1, a wireless communication system 100 may include a user equipment (UE) 101, a base station (BS) 102 and a core network (CN) 103. Although a specific number of the UE 101, the BS 102 and the CN 103 are depicted in FIG. 1, it is contemplated that any number of the UEs 101, the BSs 102 and the CNs 103 may be included in the wireless communication system 100.

The CN 103 may include a core Access and Mobility management Function (AMF) entity. The BS 102, which may communicate with the CN 103, may operate or work under the control of the AMF entity. The CN 103 may further include a User Plane Function (UPF) entity, which communicatively coupled with the AMF entity.

The BS 102 may be distributed over a geographic region. In certain embodiments of the present application, the BS 102 may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art. The BS 102 is generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BS (s) .

The UE 101 may include, for example, but is not limited to, computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , Internet of Thing (IoT) devices, or the like.

According to some embodiments of the present application, the UE 101 may include, for example, but is not limited to, a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, a wireless sensor, a monitoring device, or any other device that is capable of sending and receiving communication signals on a wireless network.

In some embodiments of the present application, the UE 101 may include, for example, but is not limited to, wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art. The UE 101 may communicate directly with the BS 102 via uplink communication signals.

The wireless communication system 100 may be compatible with any type of network that is capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a Time Division Multiple Access (TDMA) -based network, a Code Division Multiple Access (CDMA) -based network, an Orthogonal Frequency Division Multiple Access (OFDMA) -based network, a Long Term Evolution (LTE) network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.

In some embodiments of the present application, the wireless communication system 100 is compatible with the 5G New Radio (NR) of the 3GPP protocol or the 5G NR-light of the 3GPP protocol, wherein the BS 102 transmits data using an OFDM modulation scheme on the downlink (DL) and the UE 101 transmits data on the uplink (UL) using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocols, for example, WiMAX, among other protocols.

In some embodiments of the present application, the UE 101 and BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present application, the UE 101 and BS 102 may communicate over licensed spectrums, whereas in other embodiments, the UE 101 and BS 102 may communicate over unlicensed spectrums. The present application is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In yet some embodiments of present application, the BS 102 may communicate with the UE 101 using the 3GPP 5G protocols.

According to some existing agreements, small data transmission (SDT) may be used to transmit particular data when the UE 101 is under an inactive mode or an idle mode. During a SDT procedure, non-SDT data (e.g., data that cannot be transmitted as SDT data) may be arrived, i.e., the UE 101 may have the non-SDT data ready to be transmitted to the BS 102 during the SDT procedure. However, specific details of handling the arrival of non-SDT data during the SDT procedure have not been discussed yet and there are still some issues that need to be solved.

Accordingly, in the present disclosure, details of handling arrival of non-SDT data during the SDT procedure will be introduced. More details on embodiments of the present disclosure will be further described hereinafter.

Referring to FIG. 2, in some embodiments, the UE 101 may determine that non-SDT data is to be transmitted to the BS 102 during a SDT procedure, i.e., the UE 101 may determine that the non-SDT is arrived (e.g., arrived in a data transmission queue of the UE 101) . Then, in one or more stages of the SDT procedure, the UE 101 may then transmit a radio resource control (RRC) resume request 101A or an RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102. Particularly, the one or more stages of the SDT procedure that the UE 101 transmit the RRC resume request 101A or the RRC re-establishment request 101B therewithin may include:

(1) that a random access channel (RACH) preamble for SDT data is transmitted;

(2) that a random access response (RAR) message for the RACH preamble is monitored;

(3) receiving the RAR message from the BS;

(4) preparing an RRC resume request for initialing the SDT procedure;

(5) that the RRC resume request for initialing the SDT procedure is transmitted without receiving an RRC response message for the SDT procedure from the BS;

(6) being in an initial SDT procedure;

(7) being in a subsequent SDT procedure;

(8) that no granted uplink resource of the SDT procedure is available; or

(9) any logical combination of the mentioned stages of (1) to (8) .

It should be noted that the RRC resume request for arrival of the non-SDT data may be transmitted to the BS 102 in a SDT RACH resource or a configured-grant (CG) resource. The initial SDT procedure may mean means that the UE 101 is in the procedure of transmitting first uplink data and/or receiving first downlink data within the SDT procedure. For example, the initial SDT procedure may include: (1) as for CG based SDT, a period of a first uplink data transmission in a UE specific physical uplink shared channel (PUSCH) resource and a monitor of possible response message; (2) as for 4-step RACH based SDT, a period of an RA procedure for a first uplink data; or (3) as for 2-step RACH based SDT, a period of transmissions of message-A (i.e., MSG. A of 2-step RACH) and message-B (i.e., MSG. B of 4-step RACH) .

Moreover, the subsequent SDT procedure may mean that the UE 101 is in procedure of transmitting a subsequent or second uplink data or receiving a downlink data. The second uplink data may be a new data which is different from the first uplink data.

Further, in some implementations, the stage of “no granted uplink resource of the SDT procedure is available” may be determined by the UE 101 when: (1) a timer expires without receiving an RRC message in SDT procedure from the BS 102; or (2) the timer expires and/or an indication of the non-SDT data is not transmitted and/or not received by a network in the SDT procedure. In some implementations, the timer may start: (1) when an indication of arrival of the non-SDT data is generated; (2) when the non-SDT data is arrived; or (3) for each transmission and/or reception in the SDT procedure. It should be noted that each uplink transmission and/or downlink reception in the SDT procedure may be for the initial SDT transmission or the subsequent SDT transmission. The timer may be a timer for detecting a radio link failure (RLF) during the SDT procedure. The RLF during the SDT procedure happens while determining at an expiry of a timer and achieving of maximum number of retransmission in radio link control (RLC) .

In some embodiments, during the mentioned one or more stages of the SDT procedure (e.g., during the stage of: (1) that the UE 101 transmits the RRC resume request for initialing the SDT procedure to the BS 102 without receiving any RRC response message for the SDT procedure from the BS 102; or (2) that the UE 101 transmits the RACH preamble to the BS 102 without receiving any RAR message (i.e., message 2 of 4-step RACH procedure or message B of 2-step RACH procedure) ) , when the UE 101 determines that the non-SDT data is to be transmitted to the BS 102 (i.e., the non-SDT data is arrived) , the UE 101 may transmit the RRC resume request 101A or the RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102.

In some implementations, when the non-SDT data corresponds to a data radio bearer (DRB) or a signaling radio bearer (SRB) configured with a first priority (e.g., configured with strict delay requirement or high QoS requirement) and/or time information is limited, the UE 101 may stop the SDT procedure, and or transmit the RRC resume request 101A or the RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102. More particularly, the UE 101 may stop monitoring RRC response message, RAR message or message-B, and then may transmit the RRC resume request 101A or the RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102. UE may stop the timer to indicate the SDT failure.

It should be noted that the time information being limited could mean that the time for indicate the arrival of non-SDT data on SDT procedure is long or longer than a threshold, or the remaining time for the timer to indicate the SDT failure is long or longer than a threshold. The first priority may be high priority or low priority. The threshold may be configured by the network.

In some implementations, when the non-SDT data corresponds to a DRB configured or an SRB with a second priority (e.g., configured with loose delay requirement or low QoS requirement) and/or time information is not limited, the UE 101 may continue the SDT procedure. More particularly, the UE 101 may keep monitoring the RRC response message, the RAR message or message-B for the SDT procedure, or UE may transmit the indication of arrival of non-SDT data in SDT procedure. If the SDT procedure is determined failed (e.g., a timer for receiving response from the BS 102 expires) , the UE 101 may then transmit the RRC resume request 101A or the RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102.

It should be noted that the time information being not limited could mean that: (1) the time for indicate the arrival of non-SDT data on SDT procedure is not long or not longer than a threshold, or the remaining time for the timer to indicate the SDT failure is not long or not longer than a threshold; (2) the time for indicate the arrival of non-SDT data on SDT procedure is short or shorter than a threshold; or (3) the remaining time for the timer to indicate the SDT failure is short or shorter than a threshold. The second priority may be low priority or high priority. The threshold may be configured by the network.

The high priority means that the UE 101 is configured with strict delay requirement or high QoS requirement. The low priority means that the UE 101 is configured with loose delay requirement or low QoS requirement.

It should be noted that, in these implementations, the RRC resume request 101A for non-SDT data may reuse a resume message authentication code-integrity (MAC-I) in last RRC resume request for SDT procedure. During this process, a DRB for the SDT procedure may be suspended and resumed until receiving an RRC resume message from the BS 102. The same security key as the one used in the SDT procedure may be applied for this process.

Moreover, in theses implementations, the first priority of the DRB or the second priority of the DRB may be configured by a previous RRC release message transmitted from the BS 102. In some implementations, the first priority of the DRB or the second priority of the DRB may be directly configured by an upper layer of the UE 101. The upper layer may be non-access stratum (NAS) layer, RRC layer, Service Data Adaptation Protocol (SDAP) layer or packet data convergence protocol (PDCP) layer.

In some embodiments, during the mentioned one or more stages of the SDT procedure, one indication of physical (PHY) layer may be introduced to indicates to the BS 102 that the UE 101 determines to terminate the SDT procedure. For example, referring to FIG. 3A, during the stage of that the UE 101 is in the subsequence of the SDT procedure, the UE 101 transmits an indication 101C of PHY layer to the BS 102 to indicates to the BS 102 that the UE 101 determines to terminate the SDT procedure. Then, the UE 101 receives an RRC release message 102A for the SDT procedure from the BS 102, and transmit the RRC resume request 101A for the non-SDT data to the BS 102 according to the RRC release message 102A with next hop chaining counter (NCC) information. In some implementations, the NCC information may include value of NCC (e.g., nextHopChainCount defined in 3GPP specification) .

In some embodiments, during the mentioned one or more stages of the SDT procedure, another indication of PHY layer may be introduced to indicates to the BS 102 that the non-SDT data is to be transmitted by the UE 101 (i.e., the arrival of the non-SDT data in the UE 101) . For example, referring to FIG. 3B, during the stage of that the UE 101 is in the subsequence of the SDT procedure, the UE 101 transmits an indication 101D of PHY layer to the BS 102 to indicates to the BS 102 that the non-SDT data is to be transmitted by the UE 101. Then, the UE 101 receives an RRC resume message (or other RRC message) 102B from the BS 102, and the UE 101 switches to a connected mode according to the RRC resume message (or other RRC message) 102B.

It should be noted that, in these embodiments, the

indication

101C or 101D of PHY layer from the UE 101 to the BS 102 may be an uplink control information or a sequence in a scheduling request.

In some embodiments, during the mentioned one or more stages of the SDT procedure, the UE 101 may directly transmit the RRC resume request 101A for the non-SDT data to the BS 102 in a non-SDT RACH resource. In these embodiments, the RRC resume request 101A for the non-SDT data may include: (1) a resume message authentication code-integrity (MAC-I) and an inactive radio network temporary identity (I-RNTI) , wherein the resume MAC-I use another resume MAC-I in the RRC resume request for the SDT procedure; or (2) a resume MAC-I and an I-RNTI, wherein the resume MAC-I is generated based on a key (e.g., key of K_RRCint defined in 3GPP specification) , wherein the key is in UE inactive access stratum (AS) context and for integrity check of control signal.

It should be noted that the UE 101 may keep the key (e.g., key of K_RRCint defined in 3GPP specification) and security information to be stored in UE inactive context. The security information may include at least one of: another key corresponding to the BS 102 (e.g., key of KgNB defined in 3GPP specification) , a next hop (NH) value or a NCC in UE inactive AS context. The UE 101 may discard at least one of the key (e.g., key of K_RRCint defined in 3GPP specification) and the security information after receiving an RRC message with new security information or an RRC release message from the BS 102. Further, the UE 101 may transmit an indication to the BS 102 to indicate the BS 102: (1) the key (e.g., key of K_RRCint defined in 3GPP specification) in UE inactive AS context being applied for the SDT procedure; (2) the another key (e.g., key of KgNB defined in 3GPP specification) in UE inactive AS context being applied for the SDT procedure; and (3) a NCC in UE inactive AS context being applied for the SDT procedure, (4) at least one of the security information in UE inactive AS context and the key (e.g., key of K_RRCint defined in 3GPP specification) in UE inactive AS context being applied for the SDT procedure.

In some embodiments, during the mentioned one or more stages of the SDT procedure, the UE 101 may generate a resume MAC-I by using a key derived during the SDT procedure and transmit the RRC resume request 101A for the non-SDT data to the BS 102 in a non-SDT RACH resource. In these embodiments, the RRC resume request for the non-SDT data may include the resume MAC-I, and the key derived during the SDT procedure may be: (1) a key, which is derived based on one key (e.g., key of KgNB defined in 3GPP specification) used in SDT procedure, a physical cell identify (PCI) and downlink frequency information of a serving cell of the BS 102; (2) a key, which is derived based on one key (e.g., key of KgNB defined in 3GPP specification) stored in UE inactive AS context, the PCI and the downlink frequency information of the serving cell of the BS 102; or (3) the same as one key used in the SDT procedure.

Further, in these embodiments, if an I-RNTI is not updated, a security authentication may be transmitted to an anchor BS before the SDT procedure. The anchor BS may update its key according to the security authentication and discard a previous key when the SDT procedure is successful. Otherwise, the anchor BS may have a serving BS (used to perform the SDT procedure) to confirm security issue, i.e., the anchor BS may transfer the short MAC-I to a source BS (used to perform the SDT procedure) to perform the security authentication.

Further, in these embodiments, if the I-RNTI is updated, the security authentication may be transmitted to the serving BS (used to perform the SDT procedure) , and the source BS (used to perform the SDT procedure) may perform the security authentication based on the received short MAC-I.

In some embodiments, during the mentioned one or more stages of the SDT procedure, the UE 101 may generate a resume MAC-I by using a key derived during the SDT procedure and transmit the RRC resume request 101A for the non-SDT data to the BS 102 in a non-SDT RACH resource. In these embodiments, the RRC resume request for the non-SDT data may include the resume MAC-I, and the key derived during the SDT procedure may be a new key derived based on security configuration information in the SDT procedure.

It should be noted that the security configuration information in the SDT procedure may include the NCC information. For example, a NCC is received from a configuration in SDT procedure, and then the key of KgNB is derived based on: (1) the current KgNB in UE inactive AS context (or the KgNB used in SDT procedure) ; and/or (2) the information of the NH in UE inactive AS context (or the NH used in SDT procedure) and NCC. Then the key of K_RRCint may be derived based the derived KgNB..

In some embodiments, during the mentioned one or more stages of the SDT procedure, when the UE 101 transmits the RRC re-establishment request 101B for arrival of the non-SDT data to the BS 102, a cell-radio network temporary identifier (C-RNTI) in the RRC re-establishment request 101B may be a configured grant-radio network temporary identifier (CG-RNTI) or C-RNTI configured in an RRC release message for configured grant (CG) based SDT.

In some embodiments, during the mentioned one or more stages of the SDT procedure, the UE 101 may receive an I-RNTI during the SDT procedure before an end of the SDT procedure and/or at the end of the SDT procedure.

In some embodiments, during the mentioned one or more stages of the SDT procedure, the UE 101 may receive an I-RNTI during the SDT procedure when an anchor BS is updated or relocated. In detail, the UE 101 may receive the I-RNTI before the end of the SDT procedure and/or at the end of the SDT procedure if the anchor BS is updated or relocated. In some implementations, the UE 101 may receive the I-RNTI in the response message for the RRC resume request. In some implementations, the I-RNTI may be transmitted in an RRC message or in a media access control-control element (MAC-CE) .

In some embodiments, the I-RNTI may be included in the RRC resume request 101A triggered by the arrival of the non-SDT data or be included in the RRC re-establishment procedure triggered by the arrival of the non-SDT data 101B.

In some embodiments, the response message in the SDT procedure may be transmitted before an end of the SDT procedure, and may include: (1) an RRC message or MAC-CE in RRC message in SRB1/SRB2 in the SDT procedure; or (2) an RRC message or MAC-CE in RRC message in SRB1/SRB2 in the SDT procedure besides the RRC release message. The SRB1 and or SRB2 could be configured by network in the RRC Release message. If the data from SRB1 and/or SRB is transmitted in the SDT procedure, the data may use the same key as the key used for the DRB, or the following procedure may be performed:

If the UE 101 determines to transmit the data in the SDT procedure, the UE 101 may:

- derive the key of KgNB based on the current key of KgNB or the NH, by using the stored nextHopChainingCount value, as specified in 3GPP specification;

- derive the key of KRRCenc, the key of KRRCint key, the key of KUPint and the key KUPenc key, as specified in 3GPP specification;

- configure lower layers to apply integrity protection for all radio bearers except SRB0 using the configured algorithm and the key of KRRCint and the key of KUPint key derived in this subclause immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE 101, wherein only DRB (s) with previously configured user-plane integrity protection shall resume integrity protection;

- configure lower layers to apply ciphering for all radio bearers except SRB0 and to apply the configured ciphering algorithm, the key of KRRCenc and the key of KUPenc derived in this subclause, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE 101;

- re-establish PDCP entities for SRB1 and/or SRB2;

- resume SRB1 and or SRB2.

In some embodiments, the UE 101 may determine that an RLF happens in the SDT procedure. Then, the UE 101 may perform a procedure in response to the happening of the RLF in the SDT procedure. The RLF may be determined when: (1) expiry of a timer happens; (2) a random access problem happens; (3) maximum number of retransmission in radio link control (RLC) achieves; (4) a beam failure recovery failed; or (5) a listen before talk (LBT) failed.

It should be noted that the timer may be a timer for each SDT uplink transmission and/or downlink reception. Each uplink transmission and/or downlink reception may be for the initial SDT procedure or the subsequent SDT procedure. The timer may be a timer for SDT failure detection. The RLF may happen while determining at the expiry of the timer and achieving of maximum number of retransmission in RLC.

In some implementations, the procedure in response to the happening of the RLF in the SDT procedure may include at least one of: (1) switching to an idle status; (2) performing action upon switching to the idle status, wherein the action includes reset MA and/or discard of security key used in the SDT procedure; and (3) transmitting a release cause of at least one of RRC resume failure, failure for SDT procedure, RLF failure in SDT, or RRC Resume failure for SDT procedure.

In some implementations, the procedure in response to the happening of the RLF in the SDT procedure may include at least one of: (1) when the RLF happens in a CG based SDT procedure, performing the procedure includes triggering a RACH based SDT procedure, wherein the RACH based SDT procedure is a 2-step RACH based SDT procedure or a 4-step RACH based SDT procedure; (2) when the RLF happens in a 2-step RACH based SDT procedure, performing the procedure includes triggering a 4-step RACH based SDT procedure; (3) when the RLF happens in a 4-step RACH based SDT procedure, performing the procedure includes triggering an RRC resume procedure in a non-SDT RACH procedure or triggering an RRC reestablishment procedure in a non-SDT RACH procedure; (4) when the RLF happens in the SDT procedure, performing the procedure includes triggering an RRC resume procedure in a non-SDT RACH procedure or triggering an RRC reestablishment procedure in a non-SDT RACH procedure; or (5) when the RLF happens in the SDT procedure, performing the procedure includes performing fallback to following procedure in an order of priority of: a CG based SDT procedure, a 2-step RACH based SDT procedure, a 4-step RACH based SDT procedure, a 2-step RACH based procedure, a 4-setp RACH based procedure if the corresponding procedure is available to the UE 101.

FIG. 4 illustrates a flow chart of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIG. 4, method 400 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S401 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. Operation S402 is executed to transmit, by the UE, an RRC resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure. The at least one stage includes:

(1) that a random access channel (RACH) preamble for SDT data is transmitted;

(3) receiving the RAR message from the BS;

(4) preparing an RRC resume request for initialing the SDT procedure;

(6) being in an initial SDT procedure;

(7) being in a subsequent SDT procedure;

(8) no granted uplink resource of the SDT procedure is available; or

(9) any logical combination of the mentioned stages of (1) to (8) .

FIG. 5 illustrates a flow chart of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIG. 5, method 500 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S501 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. In some implementations, when the non-SDT data corresponds to a DRB configured with a first priority and/or time information is limited, operation S502A is executed to stop, by the UE, the SDT procedure. Then, operation S503A is executed to transmit, by the UE, the RRC resume request for the non-SDT data to the BS.

In some implementations, when the non-SDT data corresponds to a DRB configured with a second priority and/or time information is not limited, operation S502B is executed to continue, by the UE, the SDT procedure. Then, operation S503B is executed to transmit, by the UE, the RRC resume request for the non-SDT data to the BS when the SDT procedure is determined failed.

FIG. 6 illustrates a flow chart of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIG. 6, method 600 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S601 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. In some implementations, operation S602A is executed to transmit, by the UE, an indication of PHY layer to the BS. The indication indicates to the BS that the UE determines to terminate the SDT procedure. Operation S603A is executed to receive, by the UE, an RRC release message for the SDT procedure from the BS. Operation S604A is executed to transmit, by the UE, the RRC resume request for the non-SDT data to the BS according to the RRC release message with NCC information.

In some implementations, after operation S601, operation S602B is executed to transmit another indication of PHY layer to the BS. The another indication indicates to the BS that the arrival of the non-SDT data. Operation S603B is executed to receive an RRC resume message (or other RRC message) from the BS. Operation S604B is executed to switch, by the UE, to a connected mode according to the RRC resume message or other RRC message.

FIGS. 7A and 7B illustrate flow charts of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIGS. 7A and 7B, method 700 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S701 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. Operation S702 is executed to transmit an RRC resume request for arrival of the non-SDT data to the BS in a non-SDT RACH resource in at least one of stage of the SDT procedure. The RRC resume request for the non-SDT data includes a short MAC-I and an I-RNTI used in the RRC resume request for the SDT procedure.

In some embodiments, the method may optionally include the following steps. Operation S703 is executed to, keep, by the UE, a key corresponding to the BS and an RRC integrity to be stored in an inactive context. Operations S704 is executed to receive, by the UE, an RRC message from the BS with new key information. Operation S705 is executed to discard, by the UE, the key corresponding to the BS and the RRC integrity according to the RRC message. Operation S706 is executed to transmit, by the UE, an indication to the BS to indicates the BS: (1) the SDT procedure; (2) another key in UE inactive AS context being applied for the SDT procedure; and (3) a NCC in UE inactive AS context being applied for the SDT procedure.

FIG. 8 illustrates a flow chart of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIG. 8, method 800 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S801 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. Operation S802 is executed to generate, by the UE, a short MAC-I by using a key derived during the SDT procedure. Operation S803 is executed to transmit, by the UE, the RRC resume request for the non-SDT data to the BS in a non-SDT RACH resource. The RRC resume request for the non-SDT data includes the short MAC-I. In these embodiments, the key may be: (1) a key, which corresponds to the BS, with a PCI of the BS; (2) the same as a key used in the SDT procedure; or (3) a new key configured in the SDT procedure.

FIGS. 9A and 9C illustrate flow charts of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIGS. 9A to 9C, method 900 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S901 is executed to determine, by the UE, that a non-SDT data is to be transmitted to a BS during a SDT procedure. Operation S902 is executed to transmit, by the UE, an RRC resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure.

In some embodiments, the method may optionally include the following steps. Operation S903A is executed to receive, by the UE, an I-RNTI during the SDT procedure before an end of the SDT procedure and/or at the end of the SDT procedure. Operation S903B is executed to receive, by the UE, the I-RNTI during the SDT procedure when an anchor BS is updated or relocated.

FIG. 10 illustrates a flow chart of a method for wireless communications in accordance with some embodiments of the present application. Referring to FIG. 10, method 1000 is performed by a UE (e.g., the UE 101) in some embodiments of the present application.

In some embodiments, operation S1001 is executed to determine, by the UE, that an RLF happens in a SDT procedure. In some implementations, the RLF may be determined when: (1) expiry of a timer happens; (2) a random access problem happens; (3) maximum number of retransmission in radio link control (RLC) achieves; (4) a beam failure recovery failed; or (5) a listen before talk (LBT) failed.

Operation S1002 is executed to perform, by the UE, a procedure in response to the happening of the RLF in the SDT procedure. In some implementations, the procedure in response to the happening of the RLF in the SDT procedure may include at least one of: (1) switching to an idle status; (2) performing action upon switching to the idle status, wherein the action includes reset MA and/or discard of security key used in the SDT procedure; and (3) transmitting a release cause of at least one of RRC resume failure, failure for SDT procedure, RLF failure in SDT, or RRC Resume failure for SDT procedure.

FIG. 11 illustrates an example block diagram of an apparatus 10 according to an embodiment of the present disclosure.

As shown in FIG. 11, the apparatus 11 may include at least one non-transitory computer-readable medium (not illustrated in FIG. 11) , a receiving circuitry 1101, a transmitting circuitry 1103, and a processor 1105 coupled to the non-transitory computer-readable medium (not illustrated in FIG. 11) , the receiving circuitry 1101 and the transmitting circuitry 1103. The apparatus 11 may be a UE or a BS.

Although in this figure, elements such as processor 1105, transmitting circuitry 1103, and receiving circuitry 1101 are described in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present disclosure, the receiving circuitry 1101 and the transmitting circuitry 1103 are combined into a single device, such as a transceiver. In certain embodiments of the present disclosure, the apparatus 11 may further include an input device, a memory, and/or other components.

In some embodiments of the present disclosure, the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the user equipment as described above. For example, the computer-executable instructions, when executed, cause the processor 1105 interacting with receiving circuitry 1101 and transmitting circuitry 1103, so as to perform the operations with respect to UE or BS depicted in FIG. 1.

In some embodiments, the present disclosure provides a method of a UE, including: determining that a non-SDT data is to be transmitted to a BS during a SDT procedure; and transmitting an RRC resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure, wherein the at least one stage includes: that a RACH preamble for SDT data is transmitted; that an RAR message is monitored; receiving the RAR message from the BS; preparing an RRC resume request for initialing the SDT procedure; that the RRC resume request for initialing the SDT procedure is transmitted without receiving an RRC response message for the SDT procedure from the BS; being in an initial SDT procedure; being in a subsequent SDT procedure; or no granted uplink resource of the SDT procedure is available.

In some embodiments, when the non-SDT data corresponds to a DRB or a SRB configured with a first priority and/or time information is limited, the step of transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS includes: stopping the SDT procedure; and transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS.

In some embodiments, when the non-SDT data corresponds to a DRB or a SRB configured with a second priority and/or time information is not limited, the step of transmitting the RRC resume request for arrival of the non-SDT data to the BS includes: continuing the SDT procedure; and/or transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS when the SDT procedure is determined failed.

In some embodiments, the first priority of the DRB or the second priority of the DRB is configured by the BS and or by the UE.

In some embodiments, the step of transmitting the RRC resume request for arrival of the non-SDT data to the BS includes: transmitting an indication of PHY layer to the BS, wherein the indication indicates to the BS that the UE determines to terminate the SDT procedure.

In some embodiments, the step of transmitting the RRC resume request for the non-SDT data to the BS includes: transmitting an indication of PHY layer to the BS, wherein the indication indicates to the BS arrival of the non-SDT data.

In some embodiments, the step of transmitting the RRC resume request for the non-SDT data to the BS includes: transmitting the RRC resume request for arrival of the non-SDT data to the BS in a non-SDT RACH resource, wherein the RRC resume request for arrival of the non-SDT data includes: a resume MAC-I and an I-RNTI, the resume MAC-I uses another resume MAC-I in the RRC resume request for the SDT procedure; or a resume MAC-I and an I-RNTI, the resume MAC-I is generated based on a key, wherein the key is in UE inactive AS context and for integrity check of control signal.

In some embodiments, the method further includes: keeping the key in the UE inactive AS context and/or security information to be stored in an inactive context, wherein the security information includes at least one of another key, a next hop value or a next-hop chaining counter in the UE inactive AS context; receiving an RRC message from the BS with new security information or receiving an RRC Release message; and discarding the key in the UE inactive AS context and/or the security information according to the RRC message or the RRC release message.

In some embodiments, the method further includes: transmitting an indication to the BS to indicates the BS that at least one of the security information in UE inactive AS context and the key in UE inactive AS context has been applied for the SDT procedure.

In some embodiments, the step of transmitting the RRC resume request for arrival of the non-SDT data to the BS includes: generating a resume MAC-I by using a key; transmitting the RRC resume request for arrival of the non-SDT data to the BS in a non-SDT RACH resource, wherein the RRC resume request for the non-SDT data includes the resume MAC-I.

In some embodiments, the key is: a key, which is derived based on one key used in SDT procedure, a PCI and downlink frequency information of a serving cell of the BS; a key, which is derived based on one key stored in UE inactive AS context, the PCI and the downlink frequency information of the serving cell of the BS; the same as one key used in the SDT procedure; or a new key derived based on security configuration information in the SDT procedure.

In some embodiments, a NCC is configured in the SDT procedure.

In some embodiments, a C-RNTI in the RRC re-establishment request is a CG-RNTI or C-RNTI configured in an RRC release message for CG based SDT.

In some embodiments, no granted uplink resource of the SDT procedure being available is determined when a timer expires and or not receiving an RRC message in SDT procedure from the BS.

In some embodiments, the timer starts: when an indication of arrival of the non-SDT data is generated; when the non-SDT data is arrived; or for each transmission and/or reception in the SDT procedure.

In some embodiments, no granted uplink resource of the SDT procedure being available is determined when a timer expires and/or an indication of the non-SDT data is not transmitted and/or not received by a network in the SDT procedure.

In some embodiments, the timer starts: when the indication of the non-SDT data is generated; when the non-SDT data is arrived; or for each transmission and/or reception in the SDT procedure.

In some embodiments, the method further includes: receiving an I-RNTI during the SDT procedure before an end of the SDT procedure and/or at the end of the SDT procedure.

In some embodiments, the method further includes: receiving an I-RNTI during the SDT procedure when an anchor BS is updated or relocated.

In some embodiments, the I-RNTI is included in the RRC resume request triggered by the arrival of the non-SDT data, or included in an RRC re-establishment procedure triggered by the arrival of the non-SDT data.

In some embodiments, the present disclosure provides a method of a BS, includes: receiving an RRC resume request or an RRC re-establishment request for arrival of non-SDT data from the UE when the UE is in at least one of stage of a SDT procedure, wherein the at least one stage includes: that a RACH preamble for SDT data is transmitted; that an RAR message is monitored; receiving the RAR message from the BS; preparing an RRC resume request for initialing the SDT procedure; that the RRC resume request for initialing the SDT procedure is transmitted without receiving an RRC response message for the SDT procedure from the BS; being in an initial SDT procedure; being in a subsequent SDT procedure; or no granted uplink resource of the SDT procedure is available.

In some embodiments, when the non-SDT data corresponds to a DRB or a SRB configured with a first priority and/or time information is limited, the step of receiving the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data from the UE includes: stopping the SDT procedure; and receiving the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data from the UE.

In some embodiments, when the non-SDT data corresponds to a DRB or a SRB configured with a second priority and/or time information is not limited, the step of receiving the RRC resume request for arrival of the non-SDT data to the BS includes: continuing the SDT procedure; and/or receiving the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data from the UE when the SDT procedure is determined failed by the UE.

In some embodiments, the step of receiving the RRC resume request for arrival of the non-SDT data from the UE includes: receiving an indication of PHY layer from the UE, wherein the indication indicates to the BS that the UE determines to terminate the SDT procedure.

In some embodiments, the step of receiving the RRC resume request for arrival of the non-SDT data from the UE includes: receiving an indication of PHY layer from the UE, wherein the indication indicates to the BS arrival of the non-SDT data.

In some embodiments, the step of receiving the RRC resume request for arrival of the non-SDT data from the UE includes: receiving the RRC resume request for arrival of the non-SDT data from the UE in a non-SDT RACH resource, wherein the RRC resume request for arrival of the non-SDT data includes: a resume MAC-I and an I-RNTI, the resume MAC-I uses another resume MAC-I in the RRC resume request for the SDT procedure; or a resume MAC-I and an I-RNTI, the resume MAC-I is generated based on a key, wherein the key is in UE inactive AS context and for integrity check of control signal.

In some embodiments, the method further includes: keeping the key and/or security information to be stored in an inactive context, wherein the security information includes at least one of another key, a next hop value or a next-hop chaining counter; transmitting an RRC message to the UE with new security information or transmitting an RRC Release message; and discarding the key and/or the security information after transmitting the RRC message or the RRC release message.

In some embodiments, the method further includes: receiving an indication from the UE, wherein the indication is to indicate the BS that at least one of the security information in UE inactive AS context and the key in UE inactive AS context has been applied for the SDT procedure.

In some embodiments, the step of receiving the RRC resume request for arrival of the non-SDT data to the BS includes: generating a resume MAC-I by using a key; receiving the RRC resume request for arrival of the non-SDT data from the UE in a non-SDT RACH resource, wherein the RRC resume request for the non-SDT data includes a resume MAC-I generated by using a key.

In some embodiments, a NCC is configured in the SDT procedure.

In some embodiments, the method further includes: transmitting an I-RNTI during the SDT procedure before an end of the SDT procedure and/or at the end of the SDT procedure.

In some embodiments, the BS includes an anchor BS and the method further includes: transmitting an I-RNTI during the SDT procedure when being is updated or relocated.

In some embodiments, the present disclosure provides a method of a UE, including: determining that an RLF happens in a SDT procedure; and performing a procedure in response to the happening of the RLF in the SDT procedure.

In some embodiments, the step of determining that the RLF happens includes a determination of the following: expiry of a timer; a random access problem; achieving of maximum number of retransmission in RLC; a beam failure recovery failure; or a LBT failure.

In some embodiments, the step of performing the procedure includes at least one of: switching to an idle status; performing action upon switching to the idle status, wherein the action includes reset MA and/or discard of security key used in the SDT procedure; and transmitting a release cause of at least one of RRC resume failure, failure for SDT procedure, RLF failure in SDT, or RRC Resume failure for SDT procedure.

In some embodiments, the step of performing the procedure includes at least one of that: when the RLF happens in a CG based SDT procedure, performing the procedure includes triggering a RACH based SDT procedure, wherein the RACH based SDT procedure is a 2-step RACH based SDT procedure or a 4-step RACH based SDT procedure; when the RLF happens in a 2-step RACH based SDT procedure, performing the procedure includes triggering a 4-step RACH based SDT procedure; when the RLF happens in a 4-step RACH based SDT procedure, performing the procedure includes triggering an RRC resume procedure in a non-SDT RACH procedure or triggering an RRC reestablishment procedure in a non-SDT RACH procedure; when the RLF happens in the SDT procedure, performing the procedure includes triggering an RRC resume procedure in a non-SDT RACH procedure or triggering an RRC reestablishment procedure in a non-SDT RACH procedure; or when the RLF happens in the SDT procedure, performing the procedure includes performing fallback to following procedure in an order of priority of: a CG based SDT procedure, a 2-step RACH based SDT procedure, a 4-step RACH based SDT procedure, a 2-step RACH based procedure, a 4-setp RACH based procedure if the corresponding procedure is available to the UE.

the present disclosure provides an apparatus, including: a non-transitory computer-readable medium having stored thereon computer-executable instructions; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry; wherein the computer-executable instructions cause the processor to implement the above methods.

Those having ordinary skill in the art would understand that the operations of a method described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.

In this document, the terms "includes" , "including" , or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a" , "an" , or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term "another" is defined as at least a second or more. The term "having" and the like, as used herein, are defined as "including" .

In this document, the terms "comprises, " "comprising, " or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a, " "an, " or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Also, the term "another" is defined as at least a second or more. The terms "including, " "having, " and the like, as used herein, are defined as "comprising. "

Claims

A method of a user equipment (UE) , comprising:

determining that a non-small data transmission (SDT) data is to be transmitted to a base station (BS) during a SDT procedure; and

transmitting a radio resource control (RRC) resume request or an RRC re-establishment request for arrival of the non-SDT data to the BS in at least one of stage of the SDT procedure, wherein the at least one stage includes:

that a random access channel (RACH) preamble for SDT data is transmitted;

that a random access response (RAR) message is monitored;

receiving the RAR message from the BS;

preparing an RRC resume request for initialing the SDT procedure;

that the RRC resume request for initialing the SDT procedure is transmitted without receiving an RRC response message for the SDT procedure from the BS;

being in an initial SDT procedure;

being in a subsequent SDT procedure; or

no granted uplink resource of the SDT procedure is available.
The method of Claim 1, wherein when the non-SDT data corresponds to a data radio bearer (DRB) or a signaling radio bearer (SRB) configured with a first priority and/or time information is limited, the step of transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS comprises:

stopping the SDT procedure; and

transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS.
The method of Claim 1, wherein when the non-SDT data corresponds to a data radio bearer (DRB) or a signaling radio bearer (SRB) configured with a second priority and/or time information is not limited, the step of transmitting the RRC resume request for arrival of the non-SDT data to the BS comprises:

continuing the SDT procedure; and/or

transmitting the RRC resume request or the RRC re-establishment request for arrival of the non-SDT data to the BS when the SDT procedure is determined failed.
The method of Claim 2 or 3, wherein the first priority of the DRB or the second priority of the DRB is configured by the BS and or by the UE.
The method of Claim 1, wherein the step of transmitting the RRC resume request for the non-SDT data to the BS comprises:

transmitting the RRC resume request for arrival of the non-SDT data to the BS in a non-SDT random access channel (RACH) resource, wherein the RRC resume request for arrival of the non-SDT data includes:

a resume message authentication code-integrity (MAC-I) and an inactive radio network temporary identity (I-RNTI) , the resume MAC-I uses another resume MAC-I in the RRC resume request for the SDT procedure; or

a resume MAC-I and an inactive radio network temporary identity (I-RNTI) , the resume MAC-I is generated based on a key, wherein the key is in UE inactive access stratum (AS) context and for integrity check of control signal.
The method of Claim 5, further comprising:

keeping the key in the UE inactive AS context and/or security information to be stored in an inactive context, wherein the security information includes at least one of another key, a next hop value or a next-hop chaining counter in the UE inactive AS context;

receiving an RRC message from the BS with new security information or receiving an RRC Release message; and

discarding the key in the UE inactive AS context and/or the security information according to the RRC message or the RRC release message.
The method of Claim 1, wherein the step of transmitting the RRC resume request for arrival of the non-SDT data to the BS comprises:

generating a resume message authentication code-integrity (MAC-I) by using a key;

transmitting the RRC resume request for arrival of the non-SDT data to the BS in a non-SDT random access channel (RACH) resource, wherein the RRC resume request for the non-SDT data includes the resume MAC-I.
The method of Claim 7, wherein the key is:

a key, which is derived based on one key used in SDT procedure, a physical cell identify (PCI) and downlink frequency information of a serving cell of the BS;

a key, which is derived based on one key stored in UE inactive AS context, the PCI and the downlink frequency information of the serving cell of the BS;

the same as one key used in the SDT procedure; or

a new key derived based on security configuration information in the SDT procedure.
The method of Claim 1, wherein a next-hop chaining counter (NCC) is configured in the SDT procedure.
The method of Claim 1, wherein a cell-radio network temporary identifier (C-RNTI) in the RRC re-establishment request is a configured grant-radio network temporary identifier (CG-RNTI) or C-RNTI configured in an RRC release message for configured grant (CG) based SDT.
The method of Claim 1, wherein no granted uplink resource of the SDT procedure being available is determined when a timer expires and or not receiving an RRC message in SDT procedure from the BS.
The method of Claim 1, wherein no granted uplink resource of the SDT procedure being available is determined when a timer expires and/or an indication of the non-SDT data is not transmitted and/or not received by a network in the SDT procedure.
The method of Claim 1, further comprising:

receiving an I-RNTI during the SDT procedure before an end of the SDT procedure and/or at the end of the SDT procedure.
The method of Claim 1, further comprising:

receiving an I-RNTI during the SDT procedure when an anchor BS is updated or relocated.
The method of Claim 13 or 14, wherein the I-RNTI is included in the RRC resume request triggered by the arrival of the non-SDT data, or included in an RRC re-establishment procedure triggered by the arrival of the non-SDT data.