WO2022134027A1

WO2022134027A1 - Method and apparatus for information processing in a small data transmission procedure

Info

Publication number: WO2022134027A1
Application number: PCT/CN2020/139512
Authority: WO
Inventors: Jie Shi; Lianhai WU; Jing HAN; Ran YUE; Haiming Wang
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2020-12-25
Filing date: 2020-12-25
Publication date: 2022-06-30
Anticipated expiration: 2023-06-25

Abstract

Embodiments of the present application are directed to a method and apparatus for information processing in a small data transmission (SDT) procedure. In an embodiment of the present application, the method includes: multiplexing at least one of buffer information (BI) and a media access control (MAC) service data unit (SDU) for SDT data radio bearer (DRB) to generate a resulting MAC protocol data unit (PDU); and transmitting the resulting MAC PDU in a SDT procedure.

Description

METHOD AND APPARATUS FOR INFORMATION PROCESSING IN A SMALL DATA TRANSMISSION PROCEDURE

TECHNICAL FIELD

Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus for information processing in a small data transmission (SDT) procedure.

BACKGROUND

For a user equipment (UE) in RRC_INACTIVE state (also called an inactive mode UE) , it is possible to transmit uplink (UL) small data to a base station (BS) over pre-configured physical uplink shared channel (PUSCH) resources (configured grant type 1 resources) , or in an initial random access procedure, such as, 2-step random access channel (RACH) procedure or 4-step RACH procedure.

During a SDT procedure, when there is UL data to be transmitted, how to report buffer information (BI) of the UE to the BS needs to be discussed.

SUMMARY OF THE APPLICATION

Embodiments of the present application provide a method and apparatus for information processing in a SDT procedure.

Some embodiments of the present application provide a method performed by a user equipment (UE) . The method may include: multiplexing at least one of buffer information (BI) and a media access control (MAC) service data unit (SDU) for small data transmission (SDT) data radio bearer (DRB) to generate a resulting MAC protocol data unit (PDU) ; and transmitting the resulting MAC PDU in a SDT procedure.

In an embodiment of the present application, the BI is at least one of: a buffer status report (BSR) ; expected buffer size; or release assistant information.

In an embodiment of the present application, multiplexing at least one of BI including the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of a BSR for non-SDT and a BI for SDT, and the MAC SDU for SDT DRB with at least one of the following priority: the BSR for non-SDT has a lower priority than the BI for SDT in a SDT procedure; or the BSR for non-SDT has a higher priority than the BI for SDT in a SDT procedure; the BSR for non-SDT has a lower priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT in a SDT procedure if the BI for SDT a SDT procedure is the BSR for SDT; the BSR for non-SDT has a higher priority than the MAC CE of expected buffer size for SDT in a SDT procedure if the BI for SDT a SDT procedure is the expected buffer size; or the BSR for non-SDT has a higher priority than any other BSR in a SDT procedure.

The BI for SDT could be MAC CE for BSR, with exception of BSR included for padding. The BI for non SDT could be MAC CE for BSR for non SDT, with exception of BSR included for padding. BSR included for padding could be the padding BSR for SDT and or non-SDT.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of a BSR for non-SDT and a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority: the BSR for non-SDT has a higher priority than the BSR for SDT if a priority of a logical channel (LCH) of the BSR for non-SDT is higher than that of a LCH of the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCH s associated with the BSR of non-SDT is higher than a highest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a lowest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority; or the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority: the BSR for non-SDT has a lower priority than the BSR for SDT if a priority of a LCH of the BSR for non-SDT is lower than that of a LCH of the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a highest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a lowest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority; or the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority: the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT; the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in one shot of uplink (UL) data transmission for SDT, or without a subsequent data transmission in SDT procedure; the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB; the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB at least in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT; the BSR for non-SDT has a higher priority than the MAC SDU for SDT in a SDT subsequent data transmission procedure; or the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB.

In an embodiment of the present application, the method may further include: in the case that, in a SDT initial transmission, if a BSR for non-SDT is triggered and the UE fails to receive a response message to the initial transmission, stopping the SDT procedure, and triggering a legacy random access procedure (RACH) for radio resource control (RRC) resume procedure.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB, wherein the BSR for non-SDT is at least one of a short BSR, a BSR for LCH or logical channel group (LCG) for non-SDT, or a new MAC CE; or wherein in the case that a triggered BSR is a long BSR including both the BSR for SDT and the BSR for non-SDT, the BSR for non-SDT is segmented as a truncated long BSR or a truncated short BSR, and the BSR for SDT is segmented as another truncated long BSR or a truncated short BSR; or wherein the BSR for non-SDT is a short BSR or a long BSR with buffer size information for non-SDT logical channel and/or non-SDT logical channel group; or wherein the BSR for SDT is a short BSR or a long BSR with buffer size information for SDT logical channel and/or SDT logical channel group. The BSR for SDT could be with the MAC CE for legacy BSR.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB, the BSR for non-SDT is multiplexed with a lower priority than the priority of the MAC SDU for SDT DRB, wherein the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a highest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a lowest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB; the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a lowest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a highest priority of priorities of LCHs associated with the MAC SDU for SDT DRB.

In an embodiment of the present application, multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of a BSR for non-SDT and a BSR for SDT, and the MAC SDU for SDT DRB, wherein in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for non-SDT has a higher priority than the BSR for SDT in the truncated BSR; or in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for SDT has a higher priority than the BSR for non-SDT in the truncated BSR.

In an embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, and if there is more than one non-SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission, short truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission.

In another embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, if there is no non-SDT LCG has data available for transmission, and if there is more than one SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission, short truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission.

In another embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the Short BSR plus its subheader, if there is no non-SDT LCG has data available for transmission, and if there is more than one SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission, short truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, and short truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission.

In another embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the Short BSR plus its subheader, and if there is more than one non-SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission, short truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission.

In another embodiment, the method may further include: if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is larger than the size of the Short BSR plus its subheader, reporting long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.

In another embodiment, the method may further include: if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if one LCG has data available for transmission when the BSR is to be built, reporting the short BSR

In another embodiment, the method may further include: if the number of padding bits is equal to or larger than the size of the long BSR plus its subheader, reporting the long BSR for all LCGs which have data available for transmission.

In an embodiment of the present application, the method may further include: receiving configuration information on a DRB or a LCH for non-SDT, and multiplexing at least one of the MAC SDU for a specific configured DRB or a specific configured LCH for non-SDT and the BSR for a specific configured DRB or a specific configured LCH for non-SDT in the MAC PDU in a SDT procedure based on the configuration information.

In an embodiment of the present application, for the specific configured DRB for non-SDT: the specific configured DRB for non-SDT is indicated per DRB; or the specific configured DRB for non-SDT is a DRB with a logical channel priority equal to or larger than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT DRB is a DRB with a logical channel priority equal to or lower than a configured LCP value.

In another embodiment of the present application, for the specific configured LCH for non-SDT: the specific configured LCH for non-SDT is indicated per LCH; or the specific configured LCH for non-SDT is a LCH with a logical channel priority equal to or larger than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT LCH is a LCH with a logical channel priority equal to or lower than a configured LCP value.

In another embodiment of the present application, a priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is lower than a priority of the MAC SDU for SDT DRB, or a priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is higher than a priority of the MAC SDU for SDT DRB.

In an embodiment of the present application, the method may further include: receiving configuration information for configuring a DRB or SRB for SDT and a DRB or SRB for non-SDT in different logical channel group (LCG) ; and triggering the BSR for SDT DRB or SRB or the BSR for non-SDT DRB or SRB for non-SDT in a respective LCG based on the configuration information.

In an embodiment of the present application, a regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT, or none of the logical channels which belong to an LCG for SDT contains any available UL data.

In an embodiment of the present application, a regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT, or none of the logical channels which belong to an LCG contains any available UL data.

In an embodiment of the present application, a regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG, or none of the logical channels which belong to an LCG contains any available UL data.

In an embodiment of the present application, a regular BSR for non-SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT; or none of the logical channels which belong to an LCG for non-SDT contains any available UL data.

In an embodiment of the present application, a regular BSR for non-SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, or none of the logical channels which belong to an LCG contains any available UL data.

In an embodiment of the present application, a regular BSR for non-SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG, or none of the logical channels which belong to an LCG contains any available UL data.

In an embodiment of the present application, a regular BSR for non-SDT on the DRB for non-SDT is triggered if no regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, and no data available for any logical channel for SDT; or none of the logical channels which belong to an LCG for non-SDT contains any available UL data and none of the logical channels which belong to an LCG for SDT contains any available UL data.

In an embodiment of the present application, the method may further include: receiving a radio resource control (RRC) release/reconfiguration message including a logical channel ID for DRB or SRB for SDT and a logical channel ID for DRB or SRB for non-SDT used in SDT procedure; and storing logical channel ID mappings for SDT procedure.

In an embodiment of the present application, the BSR for non-SDT on the DRB and/or SRB for non-SDT has a higher priority than the BSR for SDT on the DRB and/or SRB for SDT, or the BSR for non-SDT on the DRB and/or SRB for non-SDT has a lower priority than the BSR for SDT on the DRB and/or SRB for SDT.

In an embodiment of the present application, if the UE determines to trigger a RRC resume for SDT, the logical channel ID mappings for each DRB or SRB for SDT in a SDT procedure will be applied, or if the UE determines to trigger a RRC resume procedure for non-SDT or for moving to a connected mode, the logical channel ID mappings for each DRB or SRB for non-SDT in non-SDT procedure or in last connected mode procedure will be applied. The connected mode could be RRC connected mode.

Some embodiments of the present application provide a method performed by a base station (BS) , the method may include: receiving a media access control (MAC) protocol data unit (PDU) in a SDT procedure, wherein the MAC PDU is multiplexed with at least one of buffer information (BI) and a MAC service data unit (SDU) for small data transmission (SDT) data radio bearer (DRB) .

In an embodiment of the present application, at least one of BI including a BSR for non-SDT and a BI for SDT, and the MAC SDU for SDT DRB are multiplexed with at least one of the following priority: the BSR for non-SDT has a lower priority than the BI for SDT in a SDT procedure; the BSR for non-SDT has a higher priority than the BI for SDT in a SDT procedure; the BSR for non-SDT has a lower priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT; the BSR for non-SDT has a higher priority than MAC CE of expected buffer size for SDT in a SDT procedure if the BI for SDT a SDT procedure is the expected buffer size; or the BSR for non-SDT has a higher priority than any other BSR in a SDT procedure.

In an embodiment of the present application, at least one of BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB are multiplexed with at least one of the following priority: the BSR for non-SDT has a higher priority than the BSR for SDT if a priority of a logical channel (LCH) of the BSR for non-SDT is higher than that of a LCH of the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a highest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a lowest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority; or the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority.

In an embodiment of the present application, at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB are multiplexed with at least one of the following priority: the BSR for non-SDT has a lower priority than the BSR for SDT if a priority of a LCH of the BSR for non-SDT is lower than that of a LCH of the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a highest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a lowest priority of priorities of LCHs associated with the BSR for SDT; the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority; or the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority.

In an embodiment of the present application, at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB are multiplexed with at least one of the following priority: the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT; the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in one shot of uplink (UL) data transmission for SDT, or without a subsequent data transmission in SDT procedure; the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB; the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB at least in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT; the BSR for non-SDT has a higher priority than the MAC SDU for SDT in a SDT subsequent data transmission procedure; or the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB.

In an embodiment of the present application, at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB are multiplexed, wherein the BSR for non-SDT is at least one of a short BSR, a BSR for LCH or logical channel group (LCG) for non-SDT, or a new MAC CE; or wherein in the case that a triggered BSR is a long BSR including both the BSR for SDT and the BSR for non-SDT, the BSR for non-SDT is segmented as a truncated long BSR or a truncated short BSR, and the BSR for SDT is segmented as another truncated long BSR or a truncated short BSR; or wherein the BSR for non-SDT is a short BSR or a long BSR with buffer size information for non-SDT logical channel and/or non-SDT logical channel group; or wherein the BSR for SDT is a short BSR or a long BSR with buffer size information for SDT logical channel and/or SDT logical channel group.

In an embodiment of the present application, at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB multiplexed and the BSR for non-SDT is multiplexed with a lower priority than the priority of the MAC SDU for SDT DRB, wherein the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a highest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a lowest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB; or the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB.

In an embodiment of the present application, at least one of a BSR for non-SDT and a BSR for SDT, and the MAC SDU for SDT DRB are multiplexed, wherein in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for non-SDT has a higher priority than the BSR for SDT in the truncated BSR; or in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for SDT has a higher priority than the BSR for non-SDT in the truncated BSR.

In an embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, and if there is more than one non-SDT LCG has data available for transmission, receiving at least one of short truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission, short truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission.

In an embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, if there is no non-SDT LCG has data available for transmission, and if there is more than one SDT LCG has data available for transmission, receiving at least one of short truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission, short truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission.

In another embodiment, the method may further include: for the padding BSR, if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is larger than the size of the Short BSR plus its subheader, receiving long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.

In another embodiment, the method may further include: if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is not equal to the size of the Short BSR plus its subheader, receiving long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.

In an embodiment of the present application, the method may further include: transmitting configuration information on a DRB or a LCH for non-SDT, wherein at least one of the MAC SDU for a specific configured DRB or a specific configured LCH for non-SDT and the BSR for a specific configured DRB or a specific configured LCH for non-SDT are multiplexed in the MAC PDU in a SDT procedure based on the configuration information.

In an embodiment of the present application, for the specific configured DRB for non-SDT: the specific configured DRB for non-SDT is indicated per DRB, or the specific configured DRB for non-SDT is a DRB with a logical channel priority equal to or larger than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT DRB is a DRB with a logical channel priority equal to or lower than a configured LCP value.

In another embodiment of the present application, for the specific configured LCH for non-SDT: the specific configured LCH for non-SDT is indicated per LCH, or the specific configured LCH for non-SDT is a LCH with a logical channel priority equal to or larger than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT LCH is a LCH with a logical channel priority equal to or lower than a configured LCP value.

In an embodiment of the present application, a priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is lower than a priority of the MAC SDU for SDT DRB, or a priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is higher than a priority of the MAC SDU for SDT DRB.

In an embodiment of the present application, the method may further include: transmitting configuration information for configuring a DRB or SRB for SDT and a DRB or SRB for non-SDT in different logical channel group (LCG) , wherein the BSR for SDT DRB or SRB or the BSR for non-SDT DRB or SRB for non-SDT in a respective LCG is triggered based on the configuration information.

In an embodiment of the present application, a regular BSR for non-SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, or none of the logical channels which belong to an LCG for non-SDT contains any available UL data.

In an embodiment of the present application, a regular BSR for non-SDT is triggered if no regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, and no data available for any logical channel for SDT, or none of the logical channels which belong to an LCG for non-SDT contains any available UL data and none of the logical channels which belong to an LCG for SDT contains any available UL data.

In an embodiment of the present application, the method may further include: transmitting a radio resource control (RRC) release/reconfiguration message including a logical channel ID for DRB or SRB for SDT and a logical channel ID for DRB or SRB for non-SDT used in SDT procedure.

In an embodiment of the present application, if the UE determines to trigger a RRC resume for SDT, the logical channel ID mappings for each DRB or SRB for SDT in a SDT procedure will be applied, or if the UE determines to trigger a RRC resume procedure for non-SDT or for moving to a connected mode, the logical channel ID mappings for each DRB or SRB for non-SDT in non-SDT procedure or in last connected mode procedure will be applied.

Some other embodiments of the present application provide a method, performed by a user equipment (UE) , the method may include: transmitting a message including assistant information on configured grant (CG) resource; and receiving a response with respect to the message including the assistant information.

In an embodiment of the present application, the assistant information on the CG resource is transmitted in at least one of Msg. A of 2-step random access channel (RACH) procedure or Msg. 3 of 4-step RACH procedure, or in a small data transmission (SDT) procedure where the UE is in inactive mode or idle mode, or in a procedure where the UE is in a connected mode.

In an embodiment of the present application, the assistant information on the CG resource comprises at least one of: a measurement result on CG resource; or a CG resource configuration request.

In an embodiment of the present application, the measurement result on CG resource comprises at least one of: reference signal received power (RSRP) or reference signal receiving quality (RSRQ) value information on synchronization signal block (SSB) associated with the CG resource, dedicated bandwidth part (BWP) , or a serving cell; indication to indicate that the RSRP value information on SSB associated with the CG resource, the dedicated BWP, or the serving cell is higher than a first threshold; and indication to indicate that the RSRQ value information on SSB associated with the CG resource or the dedicated BWP, or the serving cell is higher than a second threshold.

In an embodiment of the present application, the CG resource configuration request comprises at least one of: an index of the CG resource; and an index of the CG resource associated with a beam.

Some other embodiments of the present application provide a method, performed by a base station (BS) , the method may include: receiving a message including assistant information on configured grant (CG) resource; and transmitting a response with respect to the message including the assistant information.

Some other embodiments of the present application provide an apparatus. The apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter. The computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.

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 wireless communication system according to some embodiments of the present application;

FIG. 2 illustrates a flow chart of a method for information processing in a SDT procedure according to some embodiments of the present application;

FIG. 3 illustrates an apparatus according to some embodiments of the present application; and

FIG. 4 illustrates another apparatus according to some other embodiments of the present application.

DETAILED DESCRIPTION

The detailed descriptions of the appended drawings are intended as descriptions of preferred embodiments of the present application and are 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.

FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.

As shown in FIG. 1, the wireless communication system can include at least one base station (BS) 102, at least one UE 101, and a core network (CN) node 103. Although a specific number of BSs and UEs, e.g., a BS (e.g., BS 102) and a UE (UE 101) are depicted in FIG. 1, one skilled in the art will recognize that any number of BSs and UEs may be included in the wireless communication system. As shown in FIG. 1, the BS 102 may be distributed over a geographic region and may communicate with the CN node 103 via an interface.

The UE 101 may be a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., a television connected to the Internet) , a set-top box, a game console, a security system (including security cameras) , a vehicle on-board computer, a network device (e.g., router, switch, and modem) , or the like. According to an embodiment of the present application, the UE 101 may be 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, 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 be a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, 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 BS 102 may communicate with a CN node 103 via an interface. In some 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) .

In an example, the CN node 103 can be a mobility management entity (MME) or a serving gateway (S-GW) . In another embodiment of the present application, the CN node 103 may include a mobility management function (AMF) or a user plane function (UPF) .

The wireless communication system may be compatible with any type of network that is capable of sending and receiving wireless communication signals. For example, the wireless communication system can be 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 3rd generation partnership project (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 can be compatible with 5G new radio of the 3GPP protocol, wherein BS 102 transmits data using an OFDM modulation scheme on the downlink (DL) and 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 may implement some other open or proprietary communication protocols, for example, WiMAX, WiFi, among other protocols.

In some embodiments of the present application, the 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 BS 102 may communicate over licensed spectrums, whereas in other embodiments the BS 102 may communicate over unlicensed spectrums. Embodiments of the present application are not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In yet some embodiments of the present application, the BS 102 may communicate with UE 101 using 3GPP 5G protocols.

In an example, the UE 101 is not in RRC_CONNECTED state, for example, the UE 101 could be in a RRC_IDLE state or in a RRC_INACTIVE state. When performing small data transmission, the UE 101 transmits packets to the BS 102, and the BS 102 transmits the small data to the CN node 103 via the interface.

Herein, the data transmission or small data transmission (SDT) may mean that a UE in an inactive state/mode or an idle state/mode could transmit the data to the network side (or network) , or receive the data from the network side. The details could be as follows:

An inactive UE may have a CN connection in a cell (e.g., cell A) associated with its last serving BS (also referred to as "anchor BS" ) . However, in some scenarios, the inactive UE may perform data transmission via another cell (cell B) . The data transmission may include at least one of an uplink data transmission and downlink data transmission. For example, the inactive UE may initiate an uplink data transmission via cell B, establish a RAN connection with cell B, enter the connected mode, and then perform the data transmission. Or, the inactive UE may initiate an uplink data transmission via cell B and still stay in inactive mode in the data transmission procedure. An idle UE may act similarly.

After the completion of the data transmission, the inactive or idle UE may receive a suspend message or release message from cell B and then go back to the inactive or idle mode. Or, after the completion of the data transmission, the inactive or idle UE may receive a suspend message or release message from cell B and the UE still stay in inactive or idle mode in the data transmission procedure. In some embodiments of the present disclosure, the suspend message or release message can be an RRC message. In some embodiments of the present disclosure, the data size in such data transmission may be no greater than the maximum transport block (TB) size that can be applied in one transmission, as defined in standard protocols. Small data transmission is one of such scenarios.

Currently, a UE in inactive mode could perform a small data transmission over configured grant type 1 resources, Msg. A for 2-step RACH, or Msg. 3 in normal RACH from INACTIVE state. And a work item description (WID) on small data transmission (SDT) in a RRC_INACTIVE state is as follows:

- For the RRC_INACTIVE state:

○ UL small data transmissions for RACH-based schemes (i.e. 2-step and 4-step RACH) :

■ General procedure to enable UP data transmission for small data packets from INACTIVE state (e.g. using MSGA or MSG. 3) [RAN2]

■ Enable flexible payload sizes larger than the Rel-16 CCCH message size that is possible currently for INACTIVE state for MSGA and MSG. 3 to support UP data transmission in UL (actual payload size can be up to network configuration) [RAN2]

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

Note 1: The security aspects of the above solutions should be checked with SA3 (Services &Systems Aspects 3)

○ Transmission of UL data on pre-configured PUSCH resources (i.e. reusing the configured grant type 1) –when TA (timing advance) is valid

■ General procedure for small data transmission over configured grant type 1 resources from INACTIVE state [RAN2]

■ Configuration of the configured grant type1 resources for small data transmission in UL for INACTIVE state [RAN2]

No new RRC state should be introduced in this WID. Transmission of small data in UL, subsequent transmission of small data in UL and DL and the state transition decisions should be under network control. Focus of the WID should be on licensed carriers and the solutions can be reused for NR-U if applicable.

Note 2: Any associated specification work in RAN1 that is needed to support the above set of objectives should be initiated by RAN2 via an LS.

Currently, a buffer status report (BSR) on SDT will be transmitted to gNB to let the network allocate the UL grant for data of UE in inactive mode. However, if there is data available for non-SDT during the SDT procedure, whether to report a BSR for non-SDT in a SDT procedure needs to be considered. The BSR for non-SDT is used to let network know that the UE has data available for non-SDT data radio bearer (DRB) , and the network needs to determine whether the UE needs to be moved into a connected mode. If the BSR reporting for non-SDT is agreed, how to specify the priority between the BSR for non-SDT, and other media access control (MAC) control element (CE) or MAC service data unit (SDU) for data needs to be considered and will be discussed in the following description of the present application.

In addition, in the current SDT procedure, the data from SDT DRB will be permitted to be transmitted in inactive mode. If the non-SDT data is available and the MAC PDU has some room to be used excepting the SDT data or related MAC CE for SDT, how to deal with the room with the available non-SDT data needs to be considered and will be discussed in the following description of the present application.

Furthermore, the term "BSR" is usually used to indicate the buffer status for a logical channel group (LCG) , and the BSR is triggered to report the buffer size per LCG. Now, another concept including a BSR for non-SDT or a BSR for SDT is introduced in a SDT procedure, how to define the BSR triggering procedure based on logical channel on SDT or non-SDT needs to be considered and will be discussed in the following description of the present application.

FIG. 2 illustrates a flow chart of a method for information processing in a SDT procedure according to some embodiments of the present application. The method in FIG. 2 is performed between a BS (e.g., BS 102 in FIG. 1) and a UE (e.g., UE 101 in FIG. 1) .

As shown in FIG. 2, in operation 210, the UE may multiplex at least one of buffer information (BI) and a MAC SDU for SDT DRB to generate a resulting MAC protocol data unit (PDU) . And then in operation 220, the UE may transmit the resulting MAC PDU to the BS.

In some embodiments of the present application, the UE may multiplex the BI and the MAC SDU for SDT DRB. In some other embodiments of the present application, the UE may multiplex the BI and the related MAC CE for SDT without the MAC SDU for SDT DRB.

In an embodiment of the present application, the MAC SDU for SDT DRB could be a MAC SDU from SDT DRB and/or signaling radio bearer (SRB) . In another embodiment of the present application, the MAC SDU for SDT DRB could be data from any logical channel in a SDT procedure, except data from UL-common control channel (CCCH) . In another embodiment of the present application, the MAC SDU for SDT DRB could be data from any logical channel configured for SDT transmission, except data from UL-common control channel (CCCH) .

In some embodiments of the present application, the BI may be at least one of a buffer status report (BSR) , expected buffer size, or release assistant information. For example, the expected buffer size may be the information about the amount of the data expected to arrive at UE. The release assistant information is used to let the network know that there is one shot of UL transmission or multiple shots of UL transmission and/or one shot of DL transmission or multiple shots of DL transmission, and or there is no UL transmission or DL transmission.

For example, the BI for SDT may indicate BSR for SDT, expected buffer size for SDT, or release assistant information for SDT. The BI for non-SDT may indicate BSR for non-SDT, expected buffer size for non-SDT, or release assistant information for non-SDT.

In some cases, the BSR for non-SDT and the BI for SDT could be multiplexed separately in a MAC PDU.

In some embodiments of the present application, the UE may multiplex a BSR for non-SDT, and a BI for SDT, and the MAC SDU for SDT DRB with a priority. The BI for SDT may be the BSR for SDT, the expected buffer size for SDT or the release assistant information for SDT.

In an embodiment, the BSR for non-SDT (always) has a lower priority than the BI for SDT in a SDT procedure.

In another embodiment, the BSR for non-SDT (always) has a higher priority than the BI for SDT in a SDT procedure. For example, the BSR for non-SDT has a higher priority than the BI for SDT in a SDT procedure in the subsequent data transmission procedure, or not in the initial (first) data transmission. In another example, the BSR for non-SDT has a higher priority than the legacy BSR used in a SDT procedure.

In another embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT in a SDT procedure if the BI for SDT a SDT procedure is the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the MAC CE of expected buffer size for SDT in a SDT procedure if the BI for SDT a SDT procedure is the expected buffer size. The expected buffer size indicates the information about the amount of the data expected to arrive at UE.

In another embodiment, the BSR for non-SDT has a higher priority than any other BSR in a SDT procedure.

In some embodiments, the BI for SDT could be MAC CE for BSR, with exception of BSR included for padding. The BI for non SDT could be MAC CE for BSR for non SDT, with exception of BSR included for padding. The BSR included for padding could be the padding BSR for SDT and or non-SDT.

In some embodiments of the present application, the BSR for non-SDT has a higher priority than the BSR for SDT in some cases:

In an embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a priority of a logical channel of the BSR for non-SDT is higher than that of a logical channel of the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a highest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a lowest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a lowest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a highest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a fixed or configured priority.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is higher than a fixed or configured priority.

In some other embodiments of the present application, the BSR for non-SDT has a lower priority than the BSR for SDT in some cases:

In an embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT if a priority of a logical channel of the BSR for non-SDT is lower than that of a logical channel of the BSR for SDT.

In another embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a highest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a lowest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a lowest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a highest priority of priorities of logical channels associated with the BSR for SDT.

In another embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a fixed or configured priority.

In another embodiment, the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of logical channels associated with the BSR of non-SDT is lower than a fixed or configured priority.

In another embodiment, the BSR for non-SDT is with new MAC CE, the BSR for non-SDT could be a short BSR or a long BSR with buffer size information for non-SDT logical channel and/or non-SDT logical channel group.

In another embodiment, the BSR for SDT is with the MAC CE for legacy BSR, the BSR for SDT could be a short BSR or a long BSR with buffer size information for SDT logical channel and/or SDT logical channel group.

In another embodiment, the BSR for non-SDT will be transmitted in subsequent transmission procedure in SDT procedure. This means that the BSR for non-SDT will not be transmitted in initial transmission procedure in SDT procedure. The initial transmission could the initial (first) data or TB transmission.

In the case that, in a SDT initial transmission, if a BSR for non-SDT is triggered and the UE fails to receive a response message to the initial transmission, stopping the SDT procedure, and triggering a random access procedure for radio resource control (RRC) resume procedure. In this procedure, the random access procedure will apply the legacy RACH. The legacy RACH could be not the RACH for SDT. The radio resource control (RRC) resume procedure is used to make UE resume the DRB/SRB for non-SDT or all DRB/SRB, or move UE to connected mode. The UE fails to receive a response message to the initial transmission include the following cases: the UE has not received the response message after UE sends the initial TB or data in SDT procedure, or the UE has not received the response message after UE sends the initial TB or data in SDT procedure in a Timer. The random access procedure could be 4-step RACH or 2-step RACH.

In some embodiments of the present application, the BSR for non-SDT has a lower priority than MAC SDU of DRB for SDT in some cases.

In an embodiment, the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT.

In another embodiment, the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in one shot of uplink (UL) data transmission for SDT, or without a subsequent data transmission in SDT procedure.

In some embodiments, the BSR for non-SDT has a higher priority than MAC SDU for SDT DRB in some cases.

In another embodiment, the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB.

In another embodiment, the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB at least in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT.

In another embodiment, the BSR for non-SDT has a higher priority than the MAC SDU for SDT in a SDT subsequent data transmission procedure.

In another embodiment, the BSR for non-SDT (always) has a higher priority than the MAC SDU for SDT DRB.

In the above embodiments of the present application, the BSR for non-SDT could be a new MAC CE. This MAC CE will only include the buffer size information for non-SDT logical channel or non-SDT logical channel group.

In the method as shown in FIG. 2, in a SDT initial transmission, if a BSR for non-SDT is triggered and the UE fails to receive a response message to the initial transmission, the UE may stop the SDT procedure, and trigger the legacy RACH based radio resource control (RRC) resume procedure.

In an embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, the BSR for non-SDT may be at least one of a short BSR for non-SDT, a BSR for logical channel or logical channel group (LCG) for non-SDT, or a new MAC CE.

In another embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, in the case that a triggered BSR is a long BSR including both the BSR for SDT and the BSR for non-SDT, the BSR for non-SDT is segmented as a truncated long BSR or a truncated short BSR, and the BSR for SDT is segmented as another truncated long BSR or a truncated short BSR. The non-SDT BSR is in an independent LCG from the BSR for SDT.

If the BSR for non-SDT and SDT in the same LCG, the BSR is defined as SDT or non-SDT based on the logical channel type in which the data becomes available and trigger the BSR.

In another embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, the BSR for non-SDT is a short BSR or a long BSR with buffer size information for non-SDT logical channel and/or non-SDT logical channel group.

In another embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, the BSR for SDT is a short BSR or a long BSR with buffer size information for SDT logical channel and/or SDT logical channel group. For example, the BSR for SDT could be with the MAC CE for legacy BSR.

If the BSR for non-SDT and the BSR for SDT in the same LCG, the BSR is defined as SDT or non-SDT based on the logical channel type in which the data becomes available and trigger the BSR.

In another embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, the BSR for non-SDT is multiplexed with a lower priority than the priority of the MAC SDU for SDT DRB, where:

the BSR for non-SDT is with a highest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a threshold; or

the BSR for non-SDT is with a lowest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a threshold; or

the BSR for non-SDT is with a highest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a highest priority of priorities of logical channels associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a lowest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a lowest priority of priorities of logical channels associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a lowest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a highest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a highest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a priority of a logical channel of a followed MAC SDU for SDT DRB; or

the BSR for non-SDT is with a lowest priority of priorities of logical channels associated with the BSR for non-SDT that is lower than a priority of a logical channel of a followed MAC SDU for SDT DRB.

In another embodiment, in the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, in the case that the triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for non-SDT has a higher priority than the BSR for SDT in the truncated BSR. And if the truncated BSR is a truncated short BSR, and the LCG with a logical channel for non-SDT has a higher priority than the LCG with a logical channel for SDT. That is, the truncated BSR will firstly include the BSR for LCG with non-SDT information, then it will include the BSR for LCG with SDT information. For example, the details could be as follows:

For Padding BSR, the MAC entity shall:

1> if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

2> if more than one LCG has data available for transmission when the BSR is to be built:

3> if the number of padding bits is equal to the size of the Short BSR plus its subheader:

4> if there is more than one non-SDT LCG has data available for transmission

5> report Short Truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission. (Or, report Short Truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, report Short Truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission )

4> else if there is more than one SDT LCG has data available for transmission

5> report Short Truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission. (Or, report Short Truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, report Short Truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission)

3> else:

4> report Long Truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID.

2> else:

3> report Short BSR.

1> else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader:

2> report Long BSR for all LCGs which have data available for transmission.

Here, logical channels for SDT could be the logical channels for SDT DRB and/or SDT SRB. Logical channels for non-SDT could be the logical channels for non-SDT DRB and/or non-SDT DRB. The logical channel group for SDT could be the logical channel group including the logical channel for SDT or only including the logical channel for SDT.

The logical channel group for non-SDT could be the logical channel group including the logical channel for non-SDT or only including the logical channel for non-SDT. This means that the logical channel group for non-SDT which coud be the logical channel group including the logical channel for non-SDT may have the logical channel for SDT.

The logical channel group for SDT could be the logical channel group including the logical channel for SDT or only including the logical channel for SDT. This means that the logical channel group for SDT which coud be the logical channel group including the logical channel for SDT may have the logical channel for non-SDT.

In the multiplexing of at least one of the BSR for non-SDT and the BSR for SDT, and the MAC SDU for SDT DRB, in another embodiment, in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for SDT has a higher priority than the BSR for non-SDT in the truncated BSR. And if the truncated BSR is a truncated short BSR, and the LCG with a logical channel for SDT has a higher priority than the LCG with a logical channel for non-SDT. That is, the truncated BSR will firstly include the BSR for LCG with SDT information, then it will include the BSR for LCG with non-SDT information. For example, the details could be as follows:

For Padding BSR, the MAC entity shall:

4> if there is more than one SDT LCG has data available for transmission

5> report Short Truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission (Or, report Short Truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, or, report Short Truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission) .

4>else if there is more than one non-SDT LCG has data available for transmission

5> report Short Truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission. (Or, report Short Truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or report Short Truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission )

3> else:

4> report Long Truncated BSR of the LCG (s) with the logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID.

2> else:

3> report Short BSR.

2> report Long BSR for all LCGs which have data available for transmission.

In another embodiment, for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, and if there is more than one non-SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission, short truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission.

In another embodiment, for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, if there is no non-SDT LCG has data available for transmission, and if there is more than one SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission, short truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission.

In another embodiment, for the padding BSR, if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is larger than the size of the Short BSR plus its subheader, reporting long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.

In another embodiment, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is not equal to the size of the Short BSR plus its subheader, reporting long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.

In another embodiment, logical channels shall be prioritised in accordance with the following order (highest priority listed first) :

- C-RNTI MAC CE or data from UL-CCCH;

- Configured Grant Confirmation MAC CE or BFR MAC CE or Multiple Entry Configured Grant Confirmation MAC CE;

- Sidelink Configured Grant Confirmation MAC CE;

- LBT failure MAC CE;

- MAC CE for SL-BSR prioritized according to clause 5.22.1.6;

- MAC CE for BSR including the buffer size information for non-SDT, with exception of BSR included for padding;

- MAC CE for BSR, with exception of BSR included for padding;

- Single Entry PHR MAC CE or Multiple Entry PHR MAC CE;

- MAC CE for the number of Desired Guard Symbols;

- MAC CE for Pre-emptive BSR;

- MAC CE for SL-BSR, with exception of SL-BSR prioritized according to clause 5.22.1.6 and SL-BSR included for padding;

- data from any Logical Channel, except data from UL-CCCH;

- MAC CE for Recommended bit rate query;

- MAC CE for BSR included for padding;

- MAC CE for SL-BSR included for padding.

NOTE 2: Prioritization among Configured Grant Confirmation MAC CE, Multiple Entry Configured Grant Confirmation MAC CE, and BFR MAC CE is up to UE implementation.

In the current SDT procedure, the SDT data will be transmitted in inactive mode. If there are non-SDT data available and the MAC PDU has some room to be used excepting the SDT data or related MAC CE for SDT, how to deal with the room with the available non-SDT data will be discussed in the following.

The network (the BS) may configure the UE whether to apply the non-SDT data from some dedicated DRB with a higher logical channel priority or per UE in the MAC PDU for SDT procedure. This will reduce the delay of non-SDT data transmission.

For example, before operation 210 in FIG. 2, the UE may receive configuration information on a DRB or a logical channel (LCH) for non-SDT from the BS. And then in operation 210, the UE may multiplex at least one of the MAC SDU for a specific configured DRB or a specific configured LCH for non-SDT and the BSR for a specific configured DRB or a specific configured LCH for non-SDT in the MAC PDU for SDT in a SDT procedure based on the configuration information.

In particular, the specific configured DRB for non-SDT could be configured as follows, the specific configured DRB for non-SDT will be configured to transmit the UL data in SDT procedure. In particular, for the specific configured DRB for non-SDT: the specific configured DRB for non-SDT is indicated per DRB; or the specific configured DRB for non-SDT is a DRB with a logical channel priority equal to or greater than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT DRB is a DRB with a logical channel priority equal to or lower than a configured LCP value.

The specific configured LCH could be configured as follows, the specific configured LCH (its DRB is non-SDT) will be configured to transmit the UL data in SDT procedure. In particular, for the specific configured LCH for non-SDT: the specific configured LCH for non-SDT is indicated per LCH; or the specific configured LCH for non-SDT is a LCH with a logical channel priority equal to or larger than a configured logical channel prioritization (LCP) value; or the specific configured non-SDT LCH is a LCH with a logical channel priority equal to or lower than a configured LCP value.

In the embodiments of the present application, the UE may multiplex the MAC SDU or the BSR for the specific configured DRB or a specific configured LCH for non-SDT with or without the MAC SDU for SDT DRB in a SDT procedure.

In an embodiment, the priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is lower than the priority of the MAC SDU for SDT DRB.

In another embodiment, the priority of the MAC SDU for the specific configured DRB or the specific configured LCH for non-SDT is higher than the priority of the MAC SDU for SDT DRB.

Therefore, when the UE has a UL grant in SDT procedure, it could transmit the data or BSR of the non-SDT DRB or non-SDT DRB with LCH configured with permission to transmit data in UL grant in SDT procedure. In an embodiment, the BSR for non-SDT may have a higher priority than MAC SDU for non-SDT DRB in MAC entity.

Currently, the term “BSR” is usually used to indicate the BSR for a LCG, the BSR is triggered to report the buffer size per LCG. In the present application, another concept including BSR for non-SDT or BSR for SDT is introduced in SDT procedure, how to redefine the BSR reporting procedure based on logical channel on SDT or non-SDT will be discussed in the following.

In the embodiments of the present application, the network may configure the DRB or SRB for SDT and DRB or SRB for non-SDT in different LCG.

For example, before operation 210 in FIG. 2, the UE may receive configuration information for configuring a DRB or SRB for SDT and a DRB or SRB for non-SDT in different or separate LCG. And then the UE may trigger the BSR for SDT DRB or SRB or the BSR for non-SDT DRB or SRB in a respective LCG based on the configuration information.

A regular BSR for SDT or a regular BSR for non-SDT may be triggered separately based on the divided LCG for SDT or non-SDT.

In an embodiment, the BSR for non-SDT on the DRB for non-SDT has a higher priority than the BSR for SDT on the DRB for SDT.

In another embodiment, the BSR for non-SDT on the DRB for non-SDT has a lower priority than the BSR for SDT on the DRB for SDT.

For example, a regular BSR for SDT may be triggered: in the case that UL data for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT, or none of the logical channels which belong to an LCG for SDT contains any available UL data.

For another example, a regular BSR for SDT may be triggered: in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT; or none of the logical channels which belong to an LCG contains any available UL data.

"Uplink (UL) data, for a logical channel for SDT" means that the data from this logical channel could be transmitted in SDT procedure, or the logical channel is for SDT DRB and or SDT SRB.

For another example, a regular BSR for SDT may be triggered: in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or none of the logical channels which belong to an LCG contains any available UL data.

In above procedure, any logical channel containing available UL data could be the logical channel for SDT. The logical channel in “none of the logical channels” could be the logical channel for SDT. Maybe, any logical channel containing available UL data could be the logical channel for SDT and or non-SDT. The logical channel in “none of the logical channels” could be the logical channel for SDT and or non-SDT.

The UL data for a logical channel for SDT means that the data from this logical channel could be transmitted in SDT procedure, or that the logical channel is for SDT DRB and or SDT SRB.

In an embodiment, a regular BSR for non-SDT may be triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT; or none of the logical channels which belong to an LCG for non-SDT contains any available UL data.

In another embodiment, a regular BSR for non-SDT may be triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT; or none of the logical channels which belong to an LCG contains any available UL data.

In another embodiment, a regular BSR for non-SDT may be triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either: this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or none of the logical channels which belong to an LCG contains any available UL data.

In above procedure, any logical channel containing available UL data could be the logical channel for non-SDT. The logical channel in “none of the logical channels” could be the logical channel for non-SDT. Maybe, the any logical channel containing available UL data could be the logical channel for SDT and or non-SDT. The logical channel in “none of the logical channels” could be the logical channel for SDT and or non-SDT.

The BSR for non-SDT will be configured with its retxBSR-Timer and/or periodicBSR-Timer. Its retxBSR-Timer could reuse the retxBSR-Timer in inactive mode. Its periodicBSR-Timer could reuse the periodicBSR-Timer in inactive mode.

A regular BSR for non-SDT on the DRB for non-SDT is triggered if no regular BSR for SDT is triggered: in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity; and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, and no data available for any logical channel for SDT; or none of the logical channels which belong to an LCG for non-SDT contains any available UL data and none of the logical channels which belong to an LCG for SDT contains any available UL data.

In an embodiment of the present application, before operation 210 in FIG. 2, the UE may receive a radio resource control (RRC) release/reconfiguration message including a logical channel ID for DRB or SRB for SDT and a logical channel ID for DRB or SRB for non-SDT used in SDT procedure, from the BS. And then the UE may store logical channel ID mappings for SDT procedure. The storing of the logical channel ID mappings for SDT procedure is storing logical channel ID mappings used in SDT procedure.

Furthermore, the UE may store logical channel ID mappings for non-SDT procedure. The storing of the logical channel ID mappings for non-SDT procedure means storing logical channel ID mappings used in UE connected mode.

For example, when a UE receives the RRC release message with suspend information, it will store two logical channel ID mappings for each DRB or SRB, one is for SDT procedure, and another is for non-SDT procedure. The UE will apply the logical channel ID mapping for each DRB or SRB based on the specific data transmission procedure.

In an embodiment, if the UE determines to trigger the RRC resume for SDT, the logical channel ID mappings for each DRB or SRB in SDT procedure will be applied.

In another embodiment, if the UE determines to trigger the RRC resume procedure for non-SDT or for moving to a connected mode, the logical channel ID mappings for each DRB or SRB in non-SDT procedure or in last connected mode procedure will be applied. The connected mode could be RRC connected mode.

In particular, in the case that the logical channel ID for DRB or SRB for SDT and the logical channel ID for DRB or SRB for non-SDT belong to the same LCG, a BSR for the LCG is transmitted when the UE is in a connected mode.

In the case that the logical channel ID for DRB or SRB for SDT and the logical channel ID for DRB or SRB for non-SDT belong to the same LCG, a BSR for the LCG is transmitted in a SDT procedure when the UE in an inactive mode or idle mode.

In an embodiment, the SRB for SDT will have a higher priority than any other DRB for SDT and or DRB (even for SRB) for non-SDT, if UE determines to trigger the SDT procedure or the UE is in SDT procedure.

In an embodiment, the SRB for non-SDT will have a higher priority than any other DRB for non-SDT and or DRB (even for SRB) for SDT, if the UE determines to trigger the non-SDT procedure or the UE is in SDT procedure. The non-SDT procedure could be RRC Resume procedure to move the UE in connected mode. In an embodiment, radio link control (RLC) service data unit (SDU) for SDT DRB is the radio link control (RLC) service data unit (SDU) from SDT SRB and or SDT DRB.

According to some embodiments of the present application, a method for reporting CG resource for SDT is provided.

The UE may perform an initial small data transmission (SDT) over a preconfigured resource, i.e., a CG resource. For example, the UE may transmit UL small data to a BS over the CG resource when the UE is in inactive mode or idle mode.

However, the initial SDT transmission over the CG resource may be failed. After the failed initial SDT transmission over the CG resource happens, the UE may transmit a message including assistant information on the CG resource.

In an embodiment, the UE may transmit the assistant information on the CG resource in a SDT procedure where the UE is in inactive mode or idle mode.

In another embodiment, the UE may transmit the assistant information on the CG resource in a random access channel (RACH) procedure, such as, in Msg. A of 2-step RACH procedure or in Msg. 3 of 4-step RACH procedure. In this embodiment, the UE may transmit the assistant information on the CG resource in a SDT procedure or in a non-SDT procedure. Msg. A of 2-step RACH procedure or Msg. 3 of 4-step RACH procedure could be with or without the data from DRB.

In another embodiment, the UE may transmit the assistant information on the CG resource in a procedure where the UE is in connected mode.

In addition, the assistant information on the CG resource may include at least one of: a measurement result on CG resource or a CG resource configuration request.

In an embodiment, the measurement result on CG resource may include reference signal received power (RSRP) or reference signal receiving quality (RSRQ) value information on synchronization signal block (SSB) associated with the CG resource, or dedicated bandwidth part (BWP) , or the serving cell. The SSB associated with the CG resource or the dedicated BWP or the serving cell could be beam specific CG resource, beam specific BWP, or beam specific serving cell. The SSB is associated with the CG resource, the CG resource occasion associated with a beam, or the dedicated BWP, or the serving cell.

In another embodiment, the measurement result on CG resource may include indication to indicate that the RSRP value information on SSB associated with the CG resource, or dedicated BWP or the serving cell is higher than a threshold. The threshold may be configured by the network or preconfigured (or predefined) .

In another embodiment, the measurement result on CG resource may include indication to indicate that the RSRQ value information on SSB associated with the CG resource, dedicated BWP or the serving cell is higher than a threshold. The threshold may be configured by the network or preconfigured (or predefined) .

The CG resource configuration request may be a CG resource updating request, a CG resource releasing request, or a CG resource configuration (reconfiguration) request.

The CG resource configuration request may include at least one of: an index of the CG resource; and an index of the CG resource associated with a beam. For example, the CG resource could also be indicated to CG resource occasion. The CG resource could also be indicated to CG resource occasion associated with a beam. For example, the CG resource configuration request may include at least one of: an index of the CG resource occasion (i.e., the failed CG resource index) associated with a beam; the number of the failed initial transmissions or consecutive failed initial transmissions on the CG resource occasion associated with a beam; the failed initial transmission on CG resource occasion associated with a beam; and indication to request the network to update the CG resource occasion associated with a beam, release the CG resource occasion associated with a beam, or reconfigure to another CG resource occasion associated with a beam. For example, the UE could send a CG resource releasing request to a CG resource occasion (s) associated with a beam. For example, the UE could reconfigure to another CG resource occasion associated with a dedicated beam.

After receiving the message including the assistant information on CG resource from the UE, the BS may transmit a response with respect to the message including the assistant information. For example, in the response, the BS may indicate the UE to transit to connected mode or to reconfigure to another CG resource. Or, the BS may indicate the UE to release the CG resource of the UE, such as, in Msg. B of 2-step RACH procedure or Msg. 4 of 4-step RACH procedure in order to avoid the resource consumption.

In this document, the SDT is small data transmission, it means the UE transmits or receives the data in IDLE mode or inactive mode. SDT DRB means the DRB could be transmitted in UE IDLE mode or inactive mode. The non-SDT logical channel is the logical channel at least for non-SDT DRB and or non-SDT SRB. The non-SDT logical channel group is the logical channel group at least including the logical channel for non-SDT DRB and or non-SDT SRB. The SDT logical channel is the logical channel at least for SDT DRB and or SDT SRB. The SDT logical channel group is the logical channel group at least including the logical channel for SDT DRB and or SDT SRB.

FIG. 3 illustrates an apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 300 may be the UE 101 as illustrated in FIG. 1 or other embodiments of the present application.

As shown in FIG. 3, the apparatus 300 may include a receiver 301, a transmitter 303, a processer 305, and a non-transitory computer-readable medium 307. The non-transitory computer-readable medium 307 has computer executable instructions stored therein. The processer 305 is configured to be coupled to the non-transitory computer readable medium 307, the receiver 301, and the transmitter 303. It can be contemplated that the apparatus 300 may include more computer-readable mediums, receiver, transmitters and processors in some other embodiments of the present application according to practical requirements. In some embodiments of the present application, the receiver 301 and the transmitter 303 can be integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 300 may further include an input device, a memory, and/or other components.

In some embodiments of the present application, the non-transitory computer-readable medium 307 may have stored thereon computer-executable instructions to cause the apparatus 300 to implement the method according to embodiments of the present application.

FIG. 4 illustrates another apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 400 may be the BS 102 as illustrated in FIG. 1 or other embodiments of the present application.

As shown in FIG. 4, the apparatus 400 may include a receiver 401, a transmitter 403, a processer 405, and a non-transitory computer-readable medium 407. The non-transitory computer-readable medium 407 has computer executable instructions stored therein. The processer 405 is configured to be coupled to the non-transitory computer readable medium 407, the receiver 401, and the transmitter 403. It is contemplated that the apparatus 400 may include more computer-readable mediums, receiver, transmitters and processors in some other embodiments of the present application according to practical requirements. In some embodiments of the present application, the receiver 401 and the transmitter 403 can be integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 400 may further include an input device, a memory, and/or other components.

In some embodiments of the present application, the non-transitory computer-readable medium 407 may have stored thereon computer-executable instructions to cause the apparatus 400 to implement the method according to embodiments of the present application.

Persons skilled in the art should understand that as the technology develops and advances, the terminologies described in the present application may change, and should not affect or limit the principle and spirit of the present application.

Those having ordinary skill in the art would understand that the steps 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 "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, performed by a user equipment (UE) , comprising:

multiplexing at least one of buffer information (BI) and a media access control (MAC) service data unit (SDU) for small data transmission (SDT) data radio bearer (DRB) to generate a resulting MAC protocol data unit (PDU) ; and

transmitting the resulting MAC PDU in a SDT procedure.
The method of Claim 1, wherein the BI is at least one of:

a buffer status report (BSR) ;

expected buffer size; or

release assistant information.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises:

multiplexing at least one of BI including a BSR for non-SDT and/or a BI for SDT, and the MAC SDU for SDT DRB with at least one of the following priority:

the BSR for non-SDT has a lower priority than the BI for SDT in a SDT procedure;

the BSR for non-SDT has a higher priority than the BI for SDT in a SDT procedure;

the BSR for non-SDT has a lower priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT;

the BSR for non-SDT has a higher priority than the BSR for SDT in a SDT procedure if the BI for SDT in a SDT procedure is the BSR for SDT;

the BSR for non-SDT has a higher priority than MAC CE of expected buffer size for SDT in a SDT procedure if the BI for SDT a SDT procedure is the expected buffer size; or

the BSR for non-SDT has a higher priority than any other BSR in a SDT procedure.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority:

the BSR for non-SDT has a higher priority than the BSR for SDT if a priority of a logical channel (LCH) of the BSR for non-SDT is higher than that of a LCH of the BSR for SDT;

the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCH s associated with the BSR of non-SDT is higher than a highest priority of priorities of LCHs associated with the BSR for SDT;

the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a lowest priority of priorities of LCHs associated with the BSR for SDT;

the BSR for non-SDT has a higher priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority; or

the BSR for non-SDT has a higher priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is higher than a fixed or configured priority.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority:

the BSR for non-SDT has a lower priority than the BSR for SDT if a priority of a LCH of the BSR for non-SDT is lower than that of a LCH of the BSR for SDT;

the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a highest priority of priorities of LCHs associated with the BSR for SDT;

the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a lowest priority of priorities of LCHs associated with the BSR for SDT;

the BSR for non-SDT has a lower priority than the BSR for SDT if a highest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority; or

the BSR for non-SDT has a lower priority than the BSR for SDT if a lowest priority of priorities of LCHs associated with the BSR of non-SDT is lower than a fixed or configured priority.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB with at least one of the following priority:

the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT;

the BSR for non-SDT has a lower priority than the MAC SDU for SDT DRB in one shot of uplink (UL) data transmission for SDT, or without a subsequent data transmission in SDT procedure;

the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB;

the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB only if after logical channel prioritization including the MAC SDU with the BSR for non-SDT in the resulting MAC PDU does not require segmenting radio link control (RLC) service data unit (SDU) for SDT DRB at least in Msg. A of 2-step random access channel (RACH) procedure, Msg. 3 of 4-step RACH procedure, or in initial transmission on CG based SDT;

the BSR for non-SDT has a higher priority than the MAC SDU for SDT in a SDT subsequent data transmission procedure; or

the BSR for non-SDT has a higher priority than the MAC SDU for SDT DRB.
The method of Claim 1, further comprising: in the case that, in a SDT initial transmission, if a BSR for non-SDT is triggered and the UE fails to receive a response message to the initial transmission, stopping the SDT procedure, and triggering a legacy random access procedure (RACH) for radio resource control (RRC) resume procedure.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of the BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB,

wherein the BSR for non-SDT is at least one of a short BSR, a BSR for LCH or logical channel group (LCG) for non-SDT, or a new MAC CE; or

wherein in the case that a triggered BSR is a long BSR including both the BSR for SDT and the BSR for non-SDT, the BSR for non-SDT is segmented as a truncated long BSR or a truncated short BSR, and the BSR for SDT is segmented as another truncated long BSR or a truncated short BSR; or

wherein the BSR for non-SDT is a short BSR or a long BSR with buffer size information for non-SDT logical channel and/or non-SDT logical channel group; or

wherein the BSR for SDT is a short BSR or a long BSR with buffer size information for SDT logical channel and/or SDT logical channel group.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of BI including a BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB, the BSR for non-SDT is multiplexed with a lower priority than the priority of the MAC SDU for SDT DRB, wherein

the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or

the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a threshold; or

the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a highest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a lowest priority of priorities of LCHs associated with the MAC SDU for SDT DRB; or

the BSR for non-SDT is with a highest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB; or

the BSR for non-SDT is with a lowest priority of priorities of LCHs associated with the BSR for non-SDT that is lower than a priority of a LCH of a followed MAC SDU for SDT DRB.
The method of Claim 1, wherein multiplexing at least one of the BI and the MAC SDU for SDT DRB comprises: multiplexing at least one of BI including BSR for non-SDT and/or a BSR for SDT, and the MAC SDU for SDT DRB, wherein

in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for non-SDT has a higher priority than the BSR for SDT in the truncated BSR; or

in the case that a triggered BSR is a padding BSR and the padding BSR is to be truncated, the BSR for SDT has a higher priority than the BSR for non-SDT in the truncated BSR.
The method of Claim 10, further comprising:

for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, and if there is more than one non-SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for non-SDT with data available for transmission, short truncated BSR of the non-SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the non-SDT LCG with the highest priority logical channel for non-SDT with data available for transmission; or

for the padding BSR, if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, if the number of padding bits is equal to the size of the short BSR plus its subheader, if there is no non-SDT LCG has data available for transmission, and if there is more than one SDT LCG has data available for transmission, reporting at least one of short truncated BSR of the LCG with the highest priority logical channel for SDT with data available for transmission, short truncated BSR of the SDT LCG with the highest priority logical channel with data available for transmission, or short truncated BSR of the SDT LCG with the highest priority logical channel for SDT with data available for transmission.
The method of Claim 10, further comprising:

for the padding BSR,

if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is larger than the size of the Short BSR plus its subheader, reporting long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID; or

if the number of padding bits is equal to or larger than the size of the short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader, if more than one LCG has data available for transmission when the BSR is to be built, and if the number of padding bits is not equal to the size of the Short BSR plus its subheader, reporting long truncated BSR of the LCG (s) with the logical channels for non-SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCGID, and decreasingly order with logical channels for SDT having data available for transmission following a decreasing order of the highest priority logical channel with or without data available for transmission in each of these LCG (s) , and in case of equal priority, in increasing order of LCG ID.
The method of Claim 1, further comprising:

receiving configuration information on a DRB or a LCH for non-SDT, and

multiplexing at least one of the MAC SDU for a specific configured DRB or a specific configured LCH for non-SDT and the BSR for a specific configured DRB or a specific configured LCH for non-SDT in the MAC PDU in a SDT procedure based on the configuration information.
The method of Claim 1, wherein a regular BSR for SDT is triggered:

in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT, or none of the logical channels which belong to an LCG for SDT contains any available UL data; or

in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for SDT, or none of the logical channels which belong to an LCG contains any available UL data; or

in the case that uplink (UL) data, for a logical channel for SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG, or none of the logical channels which belong to an LCG contains any available UL data.
The method of Claim 1, wherein a regular BSR for non-SDT is triggered:

in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, or none of the logical channels which belong to an LCG for non-SDT contains any available UL data; or

in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG for non-SDT, or none of the logical channels which belong to an LCG contains any available UL data; or

in the case that uplink (UL) data, for a logical channel for non-SDT which belongs to an LCG, becomes available to the MAC entity, and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG, or none of the logical channels which belong to an LCG contains any available UL data.