Method and apparatus for small data transmission or reception

Abstract

The present disclosure relates to a method and apparatus for small data transmission or reception. One embodiment of the present disclosure provides a method performed by a user equipment (UE), comprising: transmitting uplink data in an inactive mode or an idle mode; and receiving a response message indicating information associated with data to be transmitted or received in the inactive mode or the idle mode.

Description

Technical Field

[0001] This disclosure relates to wireless communication technology, and more particularly to a method and apparatus for transmitting or receiving small data. Background Technology

[0002] When a user equipment (UE) has multiple subsequent downlink (DL) or uplink (UL) transmissions in inactive mode, a legacy RRC release message will switch the UE to inactive mode, and a legacy RRC recovery request message can switch the UE to connected mode later if needed.

[0003] The goal is to enable the UE to perform DL or UL data transmission via configured authorized (CG) resources in inactive mode. Summary of the Invention

[0004] One embodiment of this disclosure provides a method performed by a user equipment (UE), comprising: transmitting uplink data in an inactive mode or an idle mode; and receiving a response message indicating information associated with data to be transmitted or received in the inactive mode or the idle mode.

[0005] In one embodiment of this disclosure, the uplink data is transmitted via Msg.A in a two-step random access channel (RACH) procedure, via Msg.3 in a four-step RACH procedure, or via configured authorized (CG) resources.

[0006] In one embodiment of this disclosure, the information includes one or more resources for monitoring the Physical Downlink Control Channel (PDCCH).

[0007] In one embodiment of this disclosure, the one or more resources are associated with at least one of one or more data radio bearers (DRBs), UE service modes, or one or more CG resources.

[0008] In one embodiment of this disclosure, the one or more resources include control resource set (CORESET) information for PDCCH and / or search space information for PDCCH, wherein the search space information includes UE-specific search space (USS) and / or common search space (CSS).

[0009] In one embodiment of this disclosure, the one or more resources used for PDCCH monitoring are associated with at least one of the following: an initial bandwidth portion (BWP) for small data transmission, a BWP for initializing the small data transmission, a default BWP, and / or a BWP different from the initial BWP for the small data transmission.

[0010] In one embodiment of this disclosure, when the UE transitions from the connected mode to the inactive mode, the UE transitions from the connected mode to the idle mode, or the UE is in the inactive mode or the idle mode, information containing one or more resources for PDCCH monitoring is received in a Radio Resource Control (RRC) release message or a new RRC message; and wherein the RRC release message or the new RRC message enables the UE in the inactive mode or the idle mode to transmit or receive data, or to transmit or receive data in a Configurable Authorized (CG) resource.

[0011] In one embodiment of this disclosure, the response message includes an index of resources for PDCCH monitoring.

[0012] In one embodiment of this disclosure, the UE further transmits a first indicator for suggesting a resource set for PDCCH monitoring.

[0013] In one embodiment of this disclosure, the first indicator is transmitted in a Radio Resource Control (RRC) Resumption Request message, in a Media Access Control (MAC) control element (MAC CE) in a Random Access Channel (RACH) procedure, or in a Configured Grant (CG) resource for small data transmission in the inactive mode or the idle mode.

[0014] In one embodiment of this disclosure, the UE further receives first timer information indicating the start time of PDCCH monitoring when the first timer expires.

[0015] In one embodiment of this disclosure, the UE further receives second timer information indicating the end time of PDCCH monitoring when the second timer expires.

[0016] In one embodiment of this disclosure, the UE further receives a second indicator for small data transmission in the active mode or the idle mode, wherein the second indicator is used for UE contention resolution in a random access (RA) procedure or for decoding UL or DL ​​scheduling information, wherein the second indicator includes X-Radio Network Temporary Identifier (RNTI) and / or UE identification information.

[0017] In one embodiment of this disclosure, when the UE transitions from connected mode to inactive mode, or when the UE transitions from connected mode to idle mode, or when the UE is in inactive mode or idle mode, the second indicator is received in an RRC release message or a new RRC message, or in Msg.B of a two-step RACH procedure or Msg.4 of a four-step RACH procedure, wherein the RRC release message or the new RRC message enables the UE in inactive mode or idle mode to transmit or receive data, or to transmit or receive data in CG resources.

[0018] In one embodiment of this disclosure, the UE further transmits a second indicator for small data transmission in the inactive mode or the idle mode, wherein the second indicator is used for UE contention resolution in the RA procedure or for decoding UL or DL ​​scheduling information, wherein the second indicator includes X-RNTI and / or UE identification information.

[0019] In one embodiment of this disclosure, the second indicator is transmitted in Msg.A in a two-step random access channel (RACH) procedure, or Msg.3 in a four-step RACH procedure, or an RRC recovery request message on a CG resource, or a MAC CE on a CG resource.

[0020] In one embodiment of this disclosure, the response message includes uplink (UL) authorization information.

[0021] In one embodiment of this disclosure, a third indicator in the subheader of a successful random access response (RAR) indicates the availability of the UL authorization information, wherein the UL authorization information is a MAC control element (CE) following the successful RAR, or the UL authorization information is included in the payload of the successful RAR.

[0022] In one embodiment of this disclosure, a third indicator in the payload of a successful RAR indicates the availability of the UL authorization information, wherein the UL authorization information is a MAC CE following the successful RAR, or the UL authorization information is included in the payload of the successful RAR.

[0023] In one embodiment of this disclosure, the UL authorization information is used for a single UL data transmission, a first-time UL data transmission, a UL data transmission exceeding the first-time number, or for UL data transmission within a duration or in a short data transmission procedure.

[0024] In one embodiment of this disclosure, the response message includes downlink (DL) assignment information.

[0025] In one embodiment of this disclosure, a fourth indicator in the subheader of a successful RAR indicates the availability of the DL assignment information, wherein the DL assignment information is a MAC control element (CE) following the successful RAR, or the DL assignment information is included in the payload of the successful RAR.

[0026] In one embodiment of this disclosure, a fourth indicator in the payload of a successful RAR indicates the availability of the DL assignment information, wherein the DL assignment information is a MAC control element (CE) following the successful RAR, or the DL assignment information is included in the payload of the successful RAR.

[0027] In one embodiment of this disclosure, the DL assignment information is used for a single DL data transmission, a second DL data transmission, more than the second DL data transmission, or for DL ​​data transmission within a duration or in a short data transmission procedure.

[0028] In one embodiment of this disclosure, the UE further transmits an estimated or anticipated uplink buffer state report (BSR), which is based on a logical channel group (LCG) for small data transmission or associated with one or more DRBs for small data transmission.

[0029] In one embodiment of this disclosure, the UE further transmits an estimated or anticipated DL data size, which is based on a Logical Channel Group (LCG) for small data transmission or associated with one or more DRBs for small data transmission.

[0030] In one embodiment of this disclosure, the UE further indicates an expected or estimated UL buffer state report (BSR) to the access layer (AS) layer through the upper layer of the UE, or indicates an estimated or expected DL data size to the AS layer.

[0031] In one embodiment of this disclosure, the UE further indicates the number of UL small data transmissions and / or the number of DL small data transmissions via Msg.A in a two-step Random Access Channel (RACH) procedure, via Msg.3 in a four-step RACH procedure, or via a Configurable Grant (CG) resource.

[0032] In one embodiment of this disclosure, the number of times for UL small data transmission includes a value from 0, 1 to the first number or greater than the first number; and wherein the number of times for DL ​​small data transmission includes a value from 0, 1 to the second number or greater than the second number.

[0033] Another embodiment of this disclosure provides a method performed by a base station (BS), comprising: receiving uplink data from a user equipment (UE) in an inactive mode or an idle mode; and transmitting a response message indicating information associated with data to be transmitted or received in the inactive mode or the idle mode.

[0034] In one embodiment of this disclosure, the uplink data is received via Msg.A in a two-step random access channel (RACH) procedure, via Msg.3 in a four-step RACH procedure, or via configured authorized (CG) resources.

[0035] In one embodiment of this disclosure, the information includes one or more resources for monitoring the Physical Downlink Control Channel (PDCCH).

[0036] In one embodiment of this disclosure, the one or more resources are associated with at least one of one or more data radio bearers (DRBs), UE service modes, or one or more CG resources.

[0037] In one embodiment of this disclosure, the one or more resources include control resource set (CORESET) information for PDCCH and / or search space information for PDCCH, wherein the search space information includes UE-specific search space (USS) and / or common search space (CSS).

[0038] In one embodiment of this disclosure, the one or more resources used for PDCCH monitoring are associated with at least one of the following: an initial bandwidth portion (BWP) for small data transmission, a BWP for initializing the small data transmission, a default BWP, and / or a BWP different from the initial BWP for the small data transmission.

[0039] In one embodiment of this disclosure, when the UE transitions from the connected mode to the inactive mode, the UE transitions from the connected mode to the idle mode, or the UE is in the inactive mode or the idle mode, information containing one or more resources for PDCCH monitoring is transmitted in a Radio Resource Control (RRC) release message or a new RRC message; and wherein the RRC release message or the new RRC message enables the UE in the inactive mode or the idle mode to transmit or receive data, or to transmit or receive data in a Configurable Grant (CG) resource.

[0040] In one embodiment of this disclosure, the response message includes an index of resources for PDCCH monitoring.

[0041] In one embodiment of this disclosure, the BS further receives a first indicator for suggesting a set of resources for PDCCH monitoring.

[0042] In one embodiment of this disclosure, the first indicator is transmitted in a Radio Resource Control (RRC) Resumption Request message, in a Media Access Control (MAC) control element (MAC CE) in a Random Access Channel (RACH) procedure, or in a Configured Grant (CG) resource for small data transmission in the inactive mode or the idle mode.

[0043] In one embodiment of this disclosure, the BS further transmits first timer information indicating the start time of PDCCH monitoring when the first timer expires.

[0044] In one embodiment of this disclosure, the BS further transmits second timer information indicating the end time of PDCCH monitoring when the second timer expires.

[0045] In one embodiment of this disclosure, the BS further transmits a second indicator for small data transmission in the active mode or the idle mode, wherein the second indicator is used for UE contention resolution in a random access (RA) procedure or for decoding UL or DL ​​scheduling information, wherein the second indicator includes X-Radio Network Temporary Identification (RNTI) and / or UE identification information.

[0046] In one embodiment of this disclosure, when the UE transitions from connected mode to inactive mode, or when the UE transitions from connected mode to idle mode, or when the UE is in inactive mode or idle mode, the second indicator is transmitted in an RRC release message or a new RRC message, or in Msg.B of a two-step RACH procedure or Msg.4 of a four-step RACH procedure, wherein the RRC release message or the new RRC message enables the UE in inactive mode or idle mode to transmit or receive data, or to transmit or receive data in CG resources.

[0047] In one embodiment of this disclosure, the BS further receives a second indicator for small data transmission in the inactive mode or the idle mode, wherein the second indicator is used for UE contention resolution in the RA procedure or for decoding UL or DL ​​scheduling information, wherein the second indicator contains X-RNTI and / or UE identification information.

[0048] In one embodiment of this disclosure, the second indicator is received in Msg.A of a two-step random access channel (RACH) procedure, or Msg.3 of a four-step RACH procedure, or an RRC recovery request message on a CG resource, or a MAC CE on a CG resource.

[0049] In one embodiment of this disclosure, the response message includes uplink (UL) authorization information.

[0050] In one embodiment of this disclosure, a third indicator in the subheader of a successful random access response (RAR) indicates the availability of the UL authorization information, wherein the UL authorization information is a MAC control element (CE) following the successful RAR, or the UL authorization information is included in the payload of the successful RAR.

[0051] In one embodiment of this disclosure, a third indicator in the payload of a successful RAR indicates the availability of the UL authorization information, wherein the UL authorization information is a MAC CE following the successful RAR, or the UL authorization information is included in the payload of the successful RAR.

[0052] In one embodiment of this disclosure, the UL authorization information is used for a single UL data transmission, a first-time UL data transmission, a UL data transmission exceeding the first-time number, or for UL data transmission within a duration or in a short data transmission procedure.

[0053] In one embodiment of this disclosure, the response message includes downlink (DL) assignment information.

[0054] In one embodiment of this disclosure, a fourth indicator in the subheader of a successful RAR indicates the availability of the DL assignment information, wherein the DL assignment information is a MAC control element (CE) following the successful RAR, or the DL assignment information is included in the payload of the successful RAR.

[0055] In one embodiment of this disclosure, a fourth indicator in the payload of a successful RAR indicates the availability of the DL assignment information, wherein the DL assignment information is a MAC control element (CE) following the successful RAR, or the DL assignment information is included in the payload of the successful RAR.

[0056] In one embodiment of this disclosure, the DL assignment information is used for a single DL data transmission, a second DL data transmission, more than the second DL data transmission, or for DL ​​data transmission within a duration or in a short data transmission procedure.

[0057] In one embodiment of this disclosure, the BS further receives an estimated or anticipated uplink buffer state report (BSR) based on a logical channel group (LCG) for small data transmission or associated with one or more DRBs for small data transmission.

[0058] In one embodiment of this disclosure, the BS further receives an estimated or anticipated DL data size, the DL data size being based on a Logical Channel Group (LCG) for small data transmission or associated with one or more DRBs for small data transmission.

[0059] In one embodiment of this disclosure, the BS further receives an expected or estimated UL buffer state report (BSR) from the upper layer of the UE to the access layer (AS), or receives an estimated or expected DL data size to the AS layer.

[0060] In one embodiment of this disclosure, the BS further receives information on the number of UL small data transmissions and / or the number of DL small data transmissions via Msg.A in a two-step Random Access Channel (RACH) procedure, Msg.3 in a four-step RACH procedure, or via Configurable Grant (CG) resources.

[0061] In one embodiment of this disclosure, the number of times for UL small data transmission includes a value from 0, 1 to the first number or greater than the first number; and wherein the number of times for DL ​​small data transmission includes a value from 0, 1 to the second number or greater than the second number.

[0062] Another embodiment of this disclosure provides an apparatus comprising: a non-transitory computer-readable medium having computer-executable instructions stored thereon; receiving circuitry; transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform a method executed by a user equipment (UE), comprising: transmitting uplink data in an inactive mode or an idle mode; and receiving a response message indicating information associated with data to be transmitted or received in the inactive mode or the idle mode.

[0063] Another embodiment of this disclosure provides an apparatus comprising: a non-transitory computer-readable medium having computer-executable instructions stored thereon; receiving circuitry; transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform a method executed by a base station (BS), comprising: receiving uplink data from a user equipment (UE) in an inactive mode or an idle mode; and transmitting a response message indicating information associated with data to be transmitted or received in the inactive mode or the idle mode. Attached Figure Description

[0064] Figure 1 This invention describes a wireless communication system according to some embodiments of the present disclosure.

[0065] Figure 2 This describes another wireless communication system according to some embodiments of the present disclosure.

[0066] Figure 3 A flowchart illustrating small data transmission according to some embodiments of this disclosure.

[0067] Figure 4A The structure of a Successful Random Access Response (RAR) Media Access Control (MAC) subheader with an indicator for UL authorization information is described according to some embodiments of this disclosure.

[0068] Figure 4B This describes the structure of a successful RAR with UL authorization information according to some embodiments of this disclosure.

[0069] Figure 4C This describes another structure for a successful RAR with UL authorization information according to some embodiments of this disclosure.

[0070] Figure 5A The structure of a successful RARMAC subheader with an indicator for DL ​​assignment information is described according to some embodiments of this disclosure.

[0071] Figure 5B This describes the structure of a successful RAR with DL assignment information according to some embodiments of the present disclosure.

[0072] Figure 5C This describes another structure for a successful RAR with DL assignment information according to some embodiments of the present disclosure.

[0073] Figure 6 This invention describes methods for transmitting or receiving small data according to some embodiments of the present disclosure.

[0074] Figure 7 A block diagram illustrating a UE according to an embodiment of the present disclosure.

[0075] Figure 8 A block diagram illustrating a BS according to an embodiment of the present disclosure. Detailed Implementation

[0076] The detailed description of the accompanying drawings is intended to illustrate the presently preferred embodiments of the invention and is not intended to represent the only form in which the invention may be practiced. It should be understood that the same or equivalent functionality may be achieved through different embodiments, which are intended to be encompassed within the spirit and scope of the invention.

[0077] Figure 1 This invention describes a wireless communication system according to some embodiments of the present disclosure.

[0078] like Figure 1 As shown, a wireless communication system can include at least one BS, at least one UE, and a CN node. Although in Figure 1 The description depicts a specific number of BS and UE, such as one BS (e.g., BS 102) and one UE (UE 101), but those skilled in the art will recognize that any number of BS and UE can be included in a wireless communication system.

[0079] like Figure 1 As shown, BS 102 can be distributed across a geographical area and can communicate with CN node 103 via interface S1. In this example, UE 101 can be an LTE UE, BS 102 can be an eNB, and CN node 103 can be a Mobility Management Entity (MME) or Serving Gateway (S-GW). In this example, UE 101 is in idle mode. When performing small data transmission, UE 101 connects to BS 102, and BS 102 transmits the small data to CN node 103 via interface S1.

[0080] Figure 2 This describes another wireless communication system according to some embodiments of the present disclosure.

[0081] like Figure 2 As shown, a wireless communication system can include at least one BS, at least one UE, and a CN node. Although in Figure 2 The text describes a specific number of BSs and UEs, such as two BSs (e.g., BS 202a and BS 202b) and one UE (UE 201), but those skilled in the art will recognize that any number of BSs and UEs can be included in a wireless communication system.

[0082] BS 202a and BS 202b may be distributed across a geographical area and may communicate with each other via interface Xn. BS 202a and BS 202b may communicate with CN node 203 via interface NG. In embodiments of this disclosure, CN node 203 may include a Mobility Management Function (AMF) or a User Plane Function (UPF). In some embodiments of this disclosure, BS 202a or BS 202b may also be referred to as an access point, access terminal, base station, base station element, macro cell, node B, evolved Node B (eNB), gNB, home node B, relay node, or device, or described using other terms used in this art. BS 202a or BS 202b is typically part of a radio access network that may include one or more controllers communicatively coupled to one or more corresponding BSs.

[0083] UE 201 may be a computing device, such as a desktop computer, laptop computer, personal digital assistant (PDA), tablet computer, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, and modem), or the like. According to embodiments of this disclosure, UE 201 may be a portable wireless communication device, smartphone, cellular phone, flip phone, device with a subscriber identification module, personal computer, selective call receiver, or any other device capable of transmitting and receiving communication signals on a wireless network. In some embodiments of this disclosure, UE 201 may be a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, UE 201 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in this art.

[0084] In this example, UE 201 is in the RRC_INACTIVE state (or inactive mode). BS 202a and BS 202b are two gNBs. The RRC_INACTIVE state is a state in which the UE remains connected under Management (CM) and can move within an area configured by the Next Generation Radio Access Network (NG-RAN) (i.e., the RAN Notification Area (RNA)) without notifying the NG-RAN. Figure 2As shown, UE 201 can move within RNA 222. BS 202b is the last serving BS of UE 201, and UE 201 is currently in a cell covered by BS 202a. For UE 201 in RRC_INACTIVE state, BS 202b maintains the context of UE 201 and its associated NG connections with CN node 203 (e.g., serving AMF and UPF). UE 201 in inactive mode can transmit uplink data. For example, UE 201 can perform small data transmission. In this example, when performing small data transmission, BS 202a can transmit data from UE 201 to BS 202b via interface Xn, and then BS 202b transmits the data to CN node 203. In another instance, when performing small data transfer, BS 202a knows that there is data from UE 201 to be transferred. BS 202a first obtains the context of UE 201 from BS 202b, and then transfers the data from UE 201 to CN node 203.

[0085] Currently, uplink (UL) or downlink (DL) transmissions following UL Small Data Transmission (SDT) are supported without transitioning to the RRC_CONNECTED state. When an RRC connection exists between the UE and the BS, the UE is in the RRC_CONNECTED state. When the UE is in the RRC_INACTIVE state, it can send multiple UL and DL packets as part of the same SDT mechanism without transitioning to RRC_CONNECTED on dedicated licenses.

[0086] Generally, if a UE has multiple subsequent DL or UL transmissions in inactive mode, a legacy RRC release message will put the UE into inactive mode, and a legacy RRC recovery request message can later return the UE to connected mode if needed.

[0087] Therefore, it is desirable to provide the UE with a solution for performing DL or UL transmissions in inactive mode.

[0088] This disclosure proposes a new message or new information indicator in a new message or traditional message. After the UE receives this new message or new information indicator, the UE will perform DL or UL transmissions via CG resources or dedicated resources in inactive mode or idle mode. It should be noted that inactive mode and idle mode refer to the state of the UE. The new message or new information indicator may be included in Msg.4 in a four-step Random Access Channel (RACH) procedure or Msg.B in a two-step RACH procedure.

[0089] Figure 3 A flowchart illustrating small data transmission according to some embodiments of this disclosure.

[0090] In step 301, the BS may transmit an RRC release message to the UE. The RRC release message is transmitted to the UE when the UE changes from connected mode to inactive mode. The RRC release message may contain a set of configuration information for the UE in inactive or idle mode; for example, the configuration information set may be a set of resources used for PDCCH monitoring. The size of the set may range from zero to a predefined number.

[0091] The resource set used for PDCCH monitoring can be UE-specific time or frequency resources applied to UEs in inactive or idle modes for PDCCH monitoring. The resource set used for PDCCH monitoring can be associated with one or more specific data radio bearers (DRBs), as small data transmission is performed according to DRBs. The resource set used for PDCCH monitoring can also be control resource set (CORSET) information, which may contain physical resource sets and parameter sets for carrying PDCCH or DCI. The resource set used for PDCCH monitoring may contain PDCCH search space information. The search space can be a UE-specific search space (USS) or a common search space (CSS).

[0092] The resource set used for PDCCH monitoring can be associated with a bandwidth portion (BWP) used for small data transfer. For example, the resource set can be associated with the initial BWP, the BWP that initiates small data transfer, and the default BWP. In another instance, the resource set can be associated with a different BWP than the initial BWP.

[0093] In addition, the RRC release message may also include one or more timers configured for the UE to avoid continuous PDCCH monitoring, thereby saving UE power. The timers can be used in scenarios where only one subsequent DL or UL data transmission occurs besides the first UL small data transmission.

[0094] One or more timers may include: a start timer, which indicates the start time for monitoring DL or UL data scheduling for PDCCH. When the start timer expires, the UE can start PDCCH monitoring. An end timer, which indicates the end time for PDCCH monitoring, when the end timer expires, the UE can stop PDCCH monitoring. PDCCH monitoring refers to monitoring the PDCCH to obtain DCI information to schedule subsequent UL or DL ​​data.

[0095] One or more timers may be pre-configured, for example, in the specification or by the network. The timer may be pre-configured but not activated initially, and then activated by the network, or it may be activated once the UE receives the associated message.

[0096] In addition, an X-Radio Network Temporary Identifier (RNTI) for small data transmissions in inactive or idle modes can be configured in the RRC release message. This X-RNTI can be an SDT-RNTI. The X-RNTI is used for UE contention resolution in random access (RA) procedures or for decoding UL or DL ​​scheduling information.

[0097] In step 302, the UE can transmit uplink data via Msg.A in a two-step RACH procedure, Msg.3 in a four-step RACH procedure, or via CG resources. The UE can also transmit one or more suggested resources for PDCCH monitoring to the BS in the RRC recovery request message, the MAC layer of the RACH procedure, or the CG-based small data transmission procedure. The one or more suggested resources for PDCCH can be an index of multiple resources for PDCCH monitoring used for UE small data transmission in inactive or idle modes.

[0098] Furthermore, for UE contention resolution purposes, the X-RNTI, serving as the MAC CE, can be included in Msg.3 or Msg.A, or the X-RNTI can be used to decode UL or DL ​​scheduling information. Through this X-RNTI, the UE and BS can implicitly know that the UE needs to perform UL or DL ​​data transmission in inactive or idle mode. Additionally, for UE contention resolution purposes, the UE's identification information can also be included in Msg.3 or Msg.A.

[0099] In step 303, the BS can transmit a configured resource response message for PDCCH monitoring with potential downlink data. The response message can be transmitted via CG resources. The message can be Msg.B or Msg.4, or a response message to an RRC recovery request message. The message may contain resources for PDCCH monitoring, which are used by the UE in inactive or idle mode. X-RNTI can be applied to Msg.B or Msg.4 and subsequent UL or DL ​​data transmission to monitor the PDCCH, for UE contention resolution in the RA procedure, or for decoding UL or DL ​​scheduling information. Additionally, for UE contention resolution purposes, UE identification information may also be included in Msg.B or Msg.4.

[0100] One or more timers included in the RRC release message may also be included in the response message. Similarly, one or more timers may be pre-configured, or pre-configured and activated later by the network, or activated once the UE receives the associated message.

[0101] In step 303, the BS may also receive suggested resources for PDCCH monitoring from the UE, and may select one or more resources for PDCCH monitoring, and indicate the index of the resource for PDCCH monitoring to the UE. When the UE does not suggest any resources, or the suggested resources are unavailable, the BS may indicate the index of the resource for PDCCH monitoring to the UE, regardless of the suggested resources. This indication may be transmitted in a first message in the Radio Resource Control (RRC) layer or by the MAC Control Element (CE). This means that the MAC CE may indicate which PDCCH resource is configured for the UE, or whether a timer is used to indicate the start or end time of PDCCH monitoring.

[0102] In step 304, the UE may transmit an acknowledgment (ACK) or a non-acknowledgment (NACK) to the BS on the PUCCH.

[0103] In this way, the UE can perform DL or UL data transmission via configured authorized (CG) resources in inactive or idle modes.

[0104] Different scenarios exist for small data transmissions. For example, within a given time period, the UE may have:

[0105] i. Single UL data and no DL data;

[0106] ii. No UL data and only one DL data;

[0107] iii. Multiple UL data entries but no DL data;

[0108] iv. No UL data and multiple DL data;

[0109] v. Single UL data and multiple DL data;

[0110] vi. Multiple UL data and a single DL data;

[0111] vii. Multiple UL data and a single DL data; and

[0112] viii. Multiple UL data and multiple DL data.

[0113] It should be noted that the above circumstances are intended to be illustrative, and this disclosure also applies to other situations.

[0114] It can be seen that the first and second scenarios involve only a single UL data transmission or a single DL data transmission, respectively. That is, after the first UL data transmission in the RA or CG resource, there is only one additional UL data transmission or only one additional DL data transmission. In this situation, Figure 3 The method described is complex and it is unnecessary to configure so many parameters for a single DL or UL small data transfer.

[0115] Therefore, in Figures 4A to 5C The paper proposes other solutions for small data transfers in inactive or idle modes.

[0116] Figure 4A The structure of a successful RARMAC subheader with an indicator for UL authorization information, according to some embodiments of this disclosure, is described. The subheader consists of eight header fields: E, T1, T2, S, R, R, R, and R.

[0117] Field "E" is an extended field. The extended field indicates whether the MAC subprotocol data unit (PDU) containing this MAC subheading is the last MAC subPDU or not in a MAC PDU. Field "T1" indicates whether the MAC subheading contains a random access preamble ID or a T2 flag. Field "T2" indicates whether the MAC subheading contains a backoff indicator (BI) or a MAC service data unit (SDU) indicator. Field "S" indicates whether the 'MAC subPDU of the MAC SDU' follows the MAC subPDU containing this MAC subheading.

[0118] The field "R" is a reserved bit, and it is set to "0". Figure 4A In the dashed box, the first field "R" indicates whether UL authorization information exists.

[0119] After the UE reports its subsequent UL data transmission buffer status report (BSR) or UL data assistant information, the BS can configure UL authorization information based on small data transmission in Msg.B, in Msg.4, or in the response message of the CG.

[0120] For small data transfers based on a two-step RACH, in Msg.B, the UL authorization information can be a standalone MAC CE following the MAC sub-PDU of a successful RAR. The first field "R" in the sub-header of the successful RAR will indicate whether this MAC CE is available. For example, in Figure 4A In the dashed box, the first field "R" is set to a value of "1", which indicates that the MAC CE follows the child PDU of the successful RAR.

[0121] exist Figure 4A When the first field "R" in the dashed box is set to "1", in Figure 4B In the process, a MAC CE for UL authorization information exists after the successfully RARed sub-PDU. If Figure 4A If the first field "R" in the dashed box is set to a value of "0", then it indicates that no MAC CE exists after a successful RAR subPDU.

[0122] Alternatively, UL authorization information may be included in the successful RAR sub-PDU in Msg.B. Figure 4C This describes the structure of a successful RAR with UL authorization information according to some embodiments of this disclosure.

[0123] The first field "R" in the subheader of a successful RAR will indicate whether UL authorization information is available in the successful RAR payload. Figure 4A When the first field "R" in the dashed box is set to "1", in Figure 4C In the dashed box, the two 8-bit segments (i.e., UL Authorization Oct 12 (the 12th 8-bit) and UL Authorization Oct 13 (the 13th 8-bit) in the successful RAR payload) are used to indicate UL authorization information. If Figure 4A If the first field “R” in the dashed box is set to a value of “0”, it indicates that there is no UL authorization information in the successful RAR payload.

[0124] Instead of using an indicator in the successful RAR MAC subheader, another indicator can be included in the payload of the successful RAR to indicate the availability of UL authorization information. For example, in Figure 4C In Oct 7 (the 7th 8-bit), the field “R” can be used to indicate the availability of UL authorization information.

[0125] When the indicator in the payload of a successful RAR is set to a value of "1", it indicates that the UL authorization information is either a MAC CE following a successful RAR, or that the UL authorization information is included in the successful RAR. When the indicator is set to a value of "0", it indicates that there is no UL authorization information.

[0126] For the four-step RACH procedure and CG-based small data transmissions, the response message for Msg.4 and CG-based small data transmissions may include a MAC CE for UL authorization information. The UL authorization information may be followed by a MAC CE for UE contention resolution.

[0127] Figure 5A This description illustrates the structure of a successful RARMAC subheader with an indicator for DL ​​assignment information according to some embodiments of this disclosure, specifically for situations where the UE has only a single DL data transmission and no UL data transmission following a response message for Msg.B, Msg.4, or a small data transmission based on CG. The subheader consists of eight header fields: E, T1, T2, S, R, R, R, and R. The second field "R" within the dashed box indicates the presence of DL assignment information.

[0128] For small data transfers based on a two-step RACH, in Msg.B, the DL assignment information can be a standalone MAC CE following the MAC sub-PDU of a successful RAR. The second field "R" in the sub-header of the successful RAR will indicate whether this MAC CE is available. For example, in Figure 5A In the dashed box, the second field "R" is set to a value of "1", which indicates that the MAC CE follows the child PDU of the successful RAR.

[0129] exist Figure 5A When the second field "R" in the dashed box is set to "1", in Figure 5B In the process, a MAC CE for DL ​​assignment information exists after the successfully RARed sub-PDU. If Figure 5A If the second field "R" bit in the dashed box is set to a value of "0", then it indicates that there is no MAC CE after a successful RAR subPDU.

[0130] Alternatively, DL assignment information can be included in the successful RAR subPDU in Msg.B. Figure 5C This describes the structure of a successful RAR with DL assignment information according to some embodiments of the present disclosure.

[0131] The second field in the subheader of a successful RAR will indicate whether the DL assignment information is available in the successful RAR payload. Figure 5A When the second field "R" in the dashed box is set to "1", in Figure 5C In the dashed box, the two 8-bit values ​​(i.e., DL assignment Oct 12 (the 12th 8-bit) and DL assignment Oct 13 (the 13th 8-bit) in the successful RAR payload are used to indicate DL assignment information. If Figure 5A If the second field "R" in the dashed box is set to a value of "0", then it indicates that there is no DL assignment information in the successful RAR payload.

[0132] Instead of using an indicator in the successful RAR MAC subheader, another indicator can be included in the successful RAR payload to indicate the availability of DL assignment information. For example, in Figure 5C In the 7th octet, the field "R" in Oct 7 (the 7th octet) can be used to indicate the availability of DL assignment information. When the indicator is set to a value of "1", it indicates that the DL assignment information is a MAC CE following a successful RAR, or that the DL assignment information is included in a successful RAR. When the indicator is set to a value of "0", it indicates that there is no DL assignment information.

[0133] For four-step RACH procedures and CG-based small data transmissions, the response message for Msg.4 and CG-based small data transmissions may include a MAC CE for DL ​​assignment information. The DL assignment information may be followed by a MAC CE for UE contention resolution.

[0134] In some embodiments, UL authorization information and DL assignment information can be indicated simultaneously, i.e. Figure 4A Both the first and second fields "R" in the RAR are set to "1". In this case, there is a MAC CE for UL authorization and a MAC CE for DL ​​assignment, and the MAC CE for UL authorization may follow the MAC CE for DL ​​assignment, or the MAC CE for UL authorization may precede the MAC CE for DL ​​assignment. Alternatively, they may be positioned close to each other. Similarly, the UL authorization bit in the payload of a successful RAR may follow the DL assignment bit in the successful RAR, or vice versa. Alternatively, they may be positioned close to each other in the payload of a successful RAR.

[0135] Generally, the size of a UL license can be 27 bits, and the size of a DL assignment can be greater than 20 bits. If a DL assignment exists in a successful RAR of Msg.B, then the UL PUCCH resource used for this DL assignment can reuse the PUCCH resource in Msg.B.

[0136] Generally, UL authorization information or DL ​​assignment information will also be included in the RRC message in Msg.B of the 2-step RACH or Msg.4 of the 4-step RACH.

[0137] UL authorization information can be indicated as transmitting UL data once, a configured number of times, or for a specified duration, or as transmitting UL data within a small data transmission procedure, or transmitting DL data until the small data transmission procedure ends. The configured number of times or duration can be indicated to the UE via the network or specified in the UE behavior.

[0138] DL assignment information can indicate whether to transmit DL data once, a configured number of times, or for a specified duration, or to transmit DL data within a small data transmission procedure, or to transmit DL data until the small data transmission procedure ends. The configured number of times or duration can be indicated to the UE via the network or specified in the UE behavior.

[0139] based on Figures 4A to 5C The solution reduces the number of PDCCH monitoring sessions required for DL ​​assignment or UL authorization by the UE. This is beneficial when there is only one subsequent UL or DL ​​data transmission, in which case the UE will receive the RRC release message after this UL or DL ​​data transmission. No additional scheduling information needs to be applied to the UE.

[0140] In one embodiment, the UE may transmit auxiliary information to the BS at the MAC layer. This auxiliary information indicates the UE's service mode, allowing the network to prepare scheduling information based on it. For example, the BS may determine subsequent operations based on the UE's service mode, such as directly switching the UE to connected mode, waiting for DL ​​data and transmitting it with an RRC release message, or transmitting an RRC response message and scheduling DL data in inactive mode.

[0141] The UE's auxiliary information may include the expected or estimated UL BSR or the expected or estimated DL data size.

[0142] The expected or estimated UL BSR indication is based on the expected or estimated UL BSR of the logical channel group (LCG) used for small data transmissions within duration T1. The upper layer of the UE can indicate the expected or estimated UL buffer size for duration T1 to the access layer (AS) layer (e.g., the MAC layer).

[0143] Similarly, the expected or estimated DL data size can indicate the expected DL data size based on the LCG used for small data transmissions within duration T2. ​​The upper layer indicates the expected or estimated DL data size for duration T2 to the AS layer (e.g., the MAC layer).

[0144] The expected or estimated UL BSR can indicate the expected or estimated UL BSR for duration T3. The upper layer of the UE can indicate the expected or estimated UL buffer size for duration T3 to the access layer (AS) layer (e.g., MAC layer).

[0145] Similarly, the expected or estimated DL data size can indicate the expected DL data size over duration T4. The upper layer indicates the expected or estimated DL data size for duration T4 to the AS layer (e.g., the MAC layer).

[0146] In MAC CE or RRC messages used for UE auxiliary information (e.g., Release Auxiliary Information (RAI)) reporting, the number of UL data transmissions can be 0, 1, 2, 2 to A or greater than A, where A is an integer. Alternatively, the number of UL data transmissions can be 1, 2, 2 to A or greater than A, where A is an integer. The number of DL data transmissions can be 0, 1, 2, 2 to B, or greater than B, where B is an integer. The values ​​of A or B can be pre-configured to the UE, or they can be broadcast in the network (e.g., in a system information block).

[0147] In one embodiment, the MAC CE or RRC message used for UE auxiliary information will indicate a combination of the number of UL data transmissions and the number of DL data transmissions. For example, a single UL data transmission with no DL data transmissions, or more than A UL data transmissions with no DL data transmissions.

[0148] In a MAC CE or RRC message used for UE Auxiliary Information A (e.g., RAI) reporting, the number of subsequent UL data transmissions can be 0, 1, 1 to C or greater than C, where C is an integer. Alternatively, the number of subsequent UL data transmissions can be 0, 1 to C or greater than C, where C is an integer. Similarly, in a MAC CE or RRC message, the number of subsequent DL data transmissions can be 0, 1, 1 to D or greater than D, where D is an integer. Alternatively, the number of subsequent DL data transmissions can be 0, 1 to D or greater than D, where D is an integer. The values ​​of C and D can be pre-configured to the UE, or they can be broadcast in the network (e.g., in a system information block).

[0149] In one embodiment, a MAC CE or RRC message for UE auxiliary information may indicate a combination of the number of subsequent UL data transmissions and the number of subsequent DL data transmissions. For example, a single subsequent UL data transmission with no subsequent DL data transmissions.

[0150] MAC CE or RRC messages used for UE Auxiliary Information B reports (e.g., RAI) may indicate that the time period for small data transmission will be greater than the duration Tx or less than Ty. The values ​​of Tx or Ty may be pre-configured to the UE, or they may be broadcast in the network (e.g., in a system information block).

[0151] In one embodiment, a MAC CE or RRC message for UE assistance information may indicate a combination of UE assistance information A and UE assistance information B.

[0152] In one embodiment, 2 bits are configured to describe the number of UL data transmissions, and 2 bits are configured to describe the number of DL data transmissions. Therefore, the 8 code points or 8 indices are configured by 4 bits in the MAC CE.

[0153] The following are two sample tables illustrating the relationship between code points or indices and frequency information:

[0154] Table 1

[0155] 00 Single UL data transmission 01 2-A UL data transmission 10 A+ UL data transmission 11 reserve

[0156] Table 2

[0157] 00 Single DL data transfer 01 2-B DL data transmission 10 B+ DL data transmission 11 reserve

[0158] It should be noted that the solutions in this disclosure also apply other mapping relationships between code points or indices and frequency information, and the table above is for illustrative purposes only and not for limitation.

[0159] These code points allow for more flexible indication of small data transmission service modes. The network can determine whether the UE will be in connected mode, inactive mode, or idle mode based on the likely number of transmissions of DL or UL data.

[0160] Figure 6 This invention describes methods for transmitting or receiving small data according to some embodiments of the present disclosure.

[0161] In step 601, the UE transmits uplink data in inactive or idle mode. Accordingly, in step 602, the BS receives uplink data from the UE, wherein the UE is in inactive or idle mode. In step 603, the UE receives a response message indicating information associated with data to be transmitted or received in inactive or idle mode, the response message being transmitted by the BS in step 604.

[0162] Uplink data can be transmitted via Msg.A in a two-step RACH procedure, Msg.3 in a four-step RACH procedure, or via CG resources. Correspondingly, the BS receives uplink data via Msg.A in a two-step RACH procedure, via Msg.3 in a four-step RACH procedure, or via CG resources. For example, in... Figure 3 In step 302, uplink data can be transmitted from the UE to the BS. The information may include one or more resources for PDCCH monitoring. The one or more resources for PDCCH monitoring may relate to DRB, UE service mode, or one or more CG resources. PDCCH monitoring may refer to monitoring the PDCCH to obtain DCI information to schedule subsequent UL or DL ​​data.

[0163] In addition, one or more resources used for PDCCH monitoring may contain CORESET information for PDCCH and / or search space information for PDCCH. The search space information may contain USS and / or CSS.

[0164] One or more resources used for PDCCH monitoring can also be associated with BWPs. For example, a resource can be associated with an initial BWP for small data transfer, a BWP that initializes small data transfer, a default BWP, and / or a BWP that is different from the initial BWP used for small data transfer.

[0165] The UE can receive information containing one or more resources for PDCCH monitoring at different times, such as when the UE transitions from connected mode to inactive mode, when the UE transitions from connected mode to idle mode, or when the UE is in inactive or idle mode. RRC release messages or new RRC messages enable the UE in inactive or idle mode to transmit or receive data, or to transmit or receive data in CG resources.

[0166] In some embodiments, the response message may contain one or more indexes of resources used for PDCCH monitoring. For example, by the BS in Figure 3 The message transmitted in step 303 may indicate to the UE one or more indices of resources for PDCCH monitoring.

[0167] The UE can suggest a set of resources for PDCCH monitoring, for example, in Figure 2 In step 302, the UE may transmit a first indicator for proposing a resource set for PDCCH monitoring. The first indicator may be transmitted in an RRC recovery request message, in a MACCE during a RACH procedure, or in CG resources used for small data transmissions in inactive or idle modes. The first indicator may be transmitted in Msg.A of a 2-step RACH procedure or Msg.3 of a 4-step RACH procedure. On the BS side, the BS receives the first indicator in Msg.A of a 2-step RACH procedure or Msg.3 of a 4-step RACH procedure.

[0168] In some embodiments, the UE may receive one or more timers from the BS for PDCCH monitoring. The timers include at least two timers: a first timer information indicating the start time of PDCCH monitoring when the first timer expires; that is, the UE may begin PDCCH monitoring when the first timer expires. A second timer information indicating the end time of PDCCH monitoring when the second timer expires; that is, the UE may stop PDCCH monitoring when the second timer expires. The timers may be pre-configured to the UE or configured by the network via broadcast information or dedicated RRC messages. The timers will be initiated by network indication or activated once the UE receives a response message for UL data transmission in UE inactive or idle mode, or activated once the UE transmits UL data in UE inactive or idle mode.

[0169] The UE may further receive an X-RNTI and / or UE identification from the BS, which is used for small data transmissions in inactive or idle modes and for UE contention resolution during the RA procedure, or for decoding UL or DL ​​scheduling information. For example, the X-RNTI may be an SDT-RNTI. The X-RNTI may be received in an RRC release message or a new RRC message at the following times: i) when the UE transitions from connected mode to inactive mode, ii) when the UE transitions from connected mode to idle mode, or iii) when the UE is in inactive or idle mode. The X-RNTI may be received in Msg.B of a two-step RACH procedure or Msg.4 of a four-step RACH procedure. For example, the X-RNTI may be received in Msg.B of a four-step RACH procedure. Figure 3 Received in step 303.

[0170] The UE can transmit X-RNTI and / or UE identification to the BS, which is also used for small data transmissions in inactive or idle modes, and is used for UE contention resolution in RA procedures, or for decoding UL or DL ​​scheduling information. XRNTI and / or UE identification can be transmitted in Msg.A in a two-step RACH procedure, or Msg.3 in a four-step RACH procedure, or in an RRC recovery request message on CG resources, or in a MAC CE on CG resources. For example, in Figure 3 In step 302, the UE may transmit X-RNTI and / or UE identification.

[0171] In some embodiments, Figure 3 The response message transmitted in step 303 contains UL authorization information or DL ​​assignment information. UL authorization information is used for a single UL data transmission, the first number of UL data transmissions, more than the first number of UL data transmissions, or for UL data transmissions within a duration or short data transmission procedure. Similarly, DL assignment information is used for a single DL data transmission, the second number of DL data transmissions, more than the second number of DL data transmissions, or for DL ​​data transmissions within a duration or short data transmission procedure.

[0172] Generally, UL authorization information or DL ​​assignment information will also be included in the RRC message in Msg.B of 2-step RACH or Msg.4 of 4-step RACH, which is transmitted from BS to UE.

[0173] UL authorization information can instruct the UE to transmit UL data once, a configured number of times, or for a specified duration, or to transmit UL data within a small data transmission procedure, or to transmit DL data until the small data transmission procedure ends. The configured number of times or duration can be indicated to the UE via the network or specified in the UE's behavior.

[0174] DL assignment information can instruct the UE to transmit DL data once, a configured number of times, or for a specified duration, or to transmit DL data within a small data transmission procedure, or to transmit DL data until the small data transmission procedure ends. The configured number of times or duration can be indicated to the UE via the network or specified in the UE's behavior.

[0175] In one embodiment, a third indicator in the subheader of a successful RAR may indicate the availability of UL authorization information, wherein the UL authorization information is either a MAC CE following a successful RAR, or the UL authorization information is included in the payload of the successful RAR. For example... Figure 4A The first field "R" in the successful RAR subheader indicates the UL authorization information. Figure 4B and Figure 4C Available. Alternatively, a third indicator in the payload of a successful RAR may indicate the availability of UL authorization information, wherein the UL authorization information is a MAC CE following a successful RAR, or the UL authorization information is included in the payload of a successful RAR.

[0176] In another embodiment, the fourth indicator in the subheader of the successful RAR indicates the availability of DL assignment information, wherein the DL assignment information is a MAC control element (CE) following the successful RAR, or the DL assignment information is included in the payload of the successful RAR. For example, Figure 5A The second field "R" in the subheader of a successful RAR indicates the UL authorization information. Figure 5B and Figure 5C Available. Alternatively, the fourth indicator in the payload of a successful RAR indicates the availability of DL assignment information, wherein the DL assignment information is a MAC CE following a successful RAR, or the DL assignment information is included in the payload of a successful RAR.

[0177] UL-authorized MAC CEs and DL-assigned MAC CEs can be placed close to each other; they will follow the payload of a successfully RAR. UL-authorized MAC CEs can follow DL-assigned MAC CEs or precede DL-assigned MAC CEs.

[0178] Reserved bits in a successful RAR payload can be used to indicate the availability of DL assignment information or UL authorization information.

[0179] In some embodiments, the UE may transmit auxiliary information to the BS, enabling the network to prepare scheduling information. Accordingly, the BS receives the auxiliary information and prepares scheduling information for the UE.

[0180] For example, the UE can transmit an estimated or anticipated uplink BSR based on the LCG used for small data transmission or associated with one or more DRBs used for small data transmission to the BS. The UE can also transmit an estimated or anticipated DL data size based on the LCG used for small data transmission or associated with one or more DRBs used for small data transmission or associated with a DRB to the BS. The UE's upper layers can further indicate the UL BSR to the DL data size to the AS layer (e.g., the MAC layer).

[0181] The auxiliary information may also include information on the number of small data transmissions and / or the number of DL small data transmissions. The UE can indicate the number of transmissions to the BS via Msg.A in a two-step RACH procedure, Msg.3 in a four-step RACH procedure, or through CG resources. For example, in Figure 3 In step 302, the UE can transmit number of times information. This number of times information relates to, for example, the range of UL small data transmissions, and may include zero UL small data transmissions, one to the first number of UL small data transmissions, or a number of UL small data transmissions greater than the first number. Similarly, for DL ​​small data transmissions, the number of times information may include zero DL small data transmissions, one to the second number of DL small data transmissions, or a number of DL small data transmissions greater than the second number. The solution disclosed herein is also applicable to other numbers of UL or DL ​​small data transmissions, and the above numbers are for illustrative purposes only and not for limitation.

[0182] The auxiliary information may also include a combination of the number of UL data transmissions and the number of DL data transmissions. For example, a single UL data transmission without DL data transmission, or more than A UL data transmissions without DL data transmission, or similar.

[0183] In a MAC CE or RRC message used to report UE auxiliary information A (e.g., RAI), the number of subsequent UL data transmissions can be 0, 1, 1 up to the third number, or more than the third number. Similarly, in a MAC CE or RRC message, the number of subsequent DL data transmissions can be 0, 1, 1 up to the fourth number, or more than the fourth number. The values ​​for the third or fourth number can be pre-configured to the UE, or they can be broadcast in the network (e.g., in a system information block).

[0184] The auxiliary information can also indicate a combination of the number of subsequent UL data transmissions and the number of subsequent DL data transmissions. For example, a single subsequent UL data transmission with no subsequent DL data transmissions, or similar.

[0185] MAC CE or RRC messages used to report UE auxiliary information B (e.g., RAI) can also indicate that the time period for small data transmission will be greater than the duration Tx or less than Ty. The values ​​of Tx or Ty can be pre-configured to the UE, or they can be broadcast in the network (e.g., in a system information block).

[0186] In one embodiment, a MAC CE or RRC message for UE assistance information may indicate a combination of UE assistance information A and UE assistance information B.

[0187] Figure 7 A block diagram illustrating a UE according to an embodiment of the present disclosure.

[0188] The BS may include receiving circuitry, a processor, and transmitting circuitry. In one embodiment, the UE may include: a non-transitory computer-readable medium storing computer-executable instructions thereon; receiving circuitry; transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, receiving circuitry, and transmitting circuitry. The computer-executable instructions may be programmed to implement methods using the receiving circuitry, transmitting circuitry, and processor (e.g., ...). Figure 6 (Methods in the text).

[0189] Figure 8 A block diagram illustrating a BS according to an embodiment of the present disclosure.

[0190] The BS may include receiving circuitry, a processor, and transmitting circuitry. In one embodiment, the UE may include: a non-transitory computer-readable medium storing computer-executable instructions thereon; receiving circuitry; transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, receiving circuitry, and transmitting circuitry. The computer-executable instructions may be programmed to implement methods using the receiving circuitry, transmitting circuitry, and processor (e.g., ...). Figure 6 (Methods in the text).

[0191] The methods disclosed herein can be implemented on a programmable processor. However, the controller, flowchart, and modules can also be implemented on a general-purpose or special-purpose computer, a programmable microprocessor or microcontroller and peripheral integrated circuit elements, integrated circuits, hardware electronics or logic circuits such as discrete element circuits, programmable logic devices, or the like. Generally, any device having a finite state machine capable of implementing the flowcharts shown in the figures can be used to implement the processing functions of this disclosure.

[0192] Although this disclosure has been described with reference to specific embodiments thereof, it will be apparent to those skilled in the art that many alternatives, modifications, and variations will be readily apparent. For example, various components of the embodiments may be interchanged, added to, or substituted in other embodiments. Furthermore, not all elements shown in each figure are essential to the operation of the disclosed embodiments. For example, those skilled in the art to which the disclosed embodiments pertain will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as set forth herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of this disclosure. In this disclosure, relational terms such as “first,” “second,” and the like may be used only to distinguish one entity or action from another, and do not necessarily require or imply any actual such relationship or order between these entities or actions. The terms “comprises” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements may include not only those elements but also other elements not expressly listed or inherent to the process, method, article, or apparatus. An element beginning with "a," "an," or the like does not, without further limitation, exclude the presence of additional identical elements in a process, method, article, or apparatus that includes said element. Furthermore, the term "another" is defined as at least a second or more. As used herein, the terms "comprising," "having," and the like are defined as "including."

Claims

1. A method performed by a user equipment (UE), the method comprising: Transmit uplink data in inactive or idle mode; Transmit auxiliary information associated with small data transmission, wherein the auxiliary information indicates the uplink buffer status report (BSR) and the downlink data size; and A response message is received indicating information associated with data to be transmitted or received in the inactive mode or the idle mode, wherein the information is based at least in part on the auxiliary information, which includes one or more resources for monitoring the physical downlink control channel (PDCCH).

2. The method according to claim 1, wherein the uplink data is transmitted via Msg.A in a two-step random access channel RACH procedure, via Msg.3 in a four-step RACH procedure, or via a configured authorized CG resource.

3. The method according to claim 1, wherein: The one or more resources are associated with at least one of one or more data radio bearers (DRBs), UE service modes, or one or more configured authorized CG resources; and The one or more resources include control resource set CORESET information for at least one of PDCCH or search space information for PDCCH, wherein the search space information includes at least one of UE-specific search space USS or common search space CSS.

4. The method according to claim 1, wherein: The one or more resources used for PDCCH monitoring are associated with at least one of the following: an initial bandwidth portion BWP for small data transmission, a BWP for initializing the small data transmission, a default BWP, or a BWP different from the initial BWP used for the small data transmission. When the UE transitions from connected mode to inactive mode, transitions from connected mode to idle mode, or is in at least one of the inactive mode or idle mode, the UE receives information containing the one or more resources for PDCCH monitoring in a Radio Resource Control (RRC) release message or a new RRC message; and The RRC release message or the new RRC message enables the UE in the inactive mode or the idle mode to transmit or receive the data, or to transmit or receive the data in a configured authorized CG resource.

5. The method of claim 1, wherein the response message contains an index of resources for PDCCH monitoring.

6. The method of claim 1, further comprising: The transmission indicates a first indicator for a resource set used for PDCCH monitoring, and transmits the first indicator in at least one of the Radio Resource Control (RRC) Recovery Request Message, the Media Access Control (MAC) Control Element (CE) in the Random Access Channel (RACH) procedure, or the Configured Authorized CG resource for small data transmission in the inactive mode or the idle mode.

7. The method of claim 1, further comprising: Receive the first timer information indicating the start time of PDCCH monitoring when the first timer expires; and Receive second timer information indicating the end time of PDCCH monitoring when the second timer expires.

8. The method of claim 1, further comprising: In the inactive mode or the idle mode, an indicator for small data transmission is received, wherein the indicator is used for UE contention resolution in the random access RA procedure or for decoding uplink UL or downlink DL scheduling information, and the indicator contains at least one of X-Radio Network Temporary Identifier (RNTI) or UE identification information.

9. The method of claim 1, further comprising: In the inactive mode or the idle mode, an indicator for small data transmission is transmitted, wherein the indicator is used for UE contention resolution in the random access RA procedure or for decoding uplink UL or downlink DL scheduling information, and the indicator contains X-Radio Network Temporary Identifier (X-RNTI) or UE identification information.

10. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor coupled to and operable to cause the UE to: Transmit uplink data in inactive or idle mode; Transmit auxiliary information associated with small data transmission, wherein the auxiliary information indicates the uplink buffer status report (BSR) and the downlink data size; and A response message is received indicating information associated with data to be transmitted or received in the inactive mode or the idle mode, wherein the information is based at least in part on the auxiliary information, which includes one or more resources for monitoring the physical downlink control channel (PDCCH).

11. The UE of claim 10, wherein the uplink data is transmitted via Msg.A in a two-step random access channel RACH procedure, via Msg.3 in a four-step RACH procedure, or via configured authorized CG resources.

12. The UE according to claim 10, wherein: The one or more resources are associated with at least one of one or more data radio bearers (DRBs), UE service modes, or one or more configured authorized CG resources; and The one or more resources include control resource set CORESET information for at least one of PDCCH or search space information for PDCCH, wherein the search space information includes at least one of UE-specific search space USS or common search space CSS.

13. The UE according to claim 10, wherein: The one or more resources used for PDCCH monitoring are associated with at least one of the following: an initial bandwidth portion BWP for small data transmission, a BWP for initializing the small data transmission, a default BWP, or a BWP different from the initial BWP used for the small data transmission. When the UE transitions from connected mode to inactive mode, transitions from connected mode to idle mode, or is in at least one of the inactive mode or idle mode, the UE receives information containing the one or more resources for PDCCH monitoring in a Radio Resource Control (RRC) release message or a new RRC message; and The RRC release message or the new RRC message enables the UE in the inactive mode or the idle mode to transmit or receive the data, or to transmit or receive the data in a configured authorized CG resource.

14. The UE of claim 10, wherein the response message includes an index of resources for PDCCH monitoring.

15. The UE of claim 10, wherein the at least one processor is configured such that the UE transmits a first indicator indicating a resource set for PDCCH monitoring, the first indicator being transmitted in at least one of a Radio Resource Control (RRC) Recovery Request message, a Media Access Control (MAC) Control Element (MAC CE) in a Random Access Channel (RACH) procedure, or a configured authorized CG resource for small data transmission in the inactive mode or the idle mode.

16. The UE of claim 10, wherein the at least one processor is configured such that the UE: Receive the first timer information indicating the start time of PDCCH monitoring when the first timer expires; and Receive second timer information indicating the end time of PDCCH monitoring when the second timer expires.

17. The UE of claim 10, wherein the at least one processor is configured such that the UE: In the inactive mode or the idle mode, at least one of receiving or transmitting an indicator for small data transmission is performed, wherein the indicator is used for UE contention resolution in the random access RA procedure or for decoding uplink UL or downlink DL scheduling information, and the indicator contains at least one of X-Radio Network Temporary Identifier (RNTI) or UE identification information.

18. A base station for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured such that the base station: Receive uplink data from a user equipment (UE) in inactive or idle mode; and Receive auxiliary information associated with small data transmission, wherein the auxiliary information indicates the uplink buffer status report (BSR) and the downlink data size; A transmission response message is transmitted, indicating information associated with data to be transmitted or received in the UE’s inactive mode or idle mode, wherein the information is based at least in part on the auxiliary information, which includes one or more resources for monitoring the physical downlink control channel (PDCCH).

Images