Method and device for small data transmission

Abstract

The present application relates to a user equipment, a base station, and a method for small data transmission. The base station transmits configuration information for small data transmission to the user equipment. The user equipment receives the configuration information for small data transmission from the base station. The user equipment and the base station perform small data transmission based on the configuration information.

Description

Technical Field

[0001] The present disclosure relates generally to data transmission, and more particularly to small data transmission. Background Art

[0002] In conventional networks, different services (e.g., different applications) between a base station and user equipment can be performed using different types of data transmission. Specifically, some services can be performed using normal data transmission, while others can be performed using small data transmission. However, the specific details of how a base station and user equipment distinguish whether a service can be performed using small data transmission have not been discussed, and several issues remain to be addressed. Summary of the Invention

[0003] One embodiment of the present disclosure provides a method for user equipment, which includes: receiving configuration information of small data transmission from a base station; and performing at least one small data transmission using the base station according to the configuration information of small data transmission.

[0004] Another embodiment of the present disclosure provides a method of a base station, which includes: transmitting configuration information of small data transmission to a user equipment; and executing at least one small data transmission with the user equipment according to the configuration information of small data transmission.

[0005] Yet another embodiment of the present disclosure provides an apparatus. According to an embodiment of the present disclosure, the apparatus includes: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; at least one receiving circuit system; at least one transmitting circuit system; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuit system, and the at least one transmitting circuit system, wherein the at least one non-transitory computer-readable medium and the computer-executable instructions are configured to cause the apparatus to perform a method according to an embodiment of the present disclosure using the at least one processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the present disclosure illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present disclosure and therefore should not be considered limiting of its scope.

[0007] Figure 1 A wireless communication system according to an embodiment of the present disclosure is described.

[0008] Figure 2 Data transmission in a wireless communication system according to an embodiment of the present disclosure is described.

[0009] Figures 3A to 3Cis a schematic diagram of message transmission between wireless communication systems according to an embodiment of the present disclosure.

[0010] Figures 4A to 4C is a schematic diagram of message transmission between wireless communication systems according to an embodiment of the present disclosure.

[0011] Figures 5A to 5C is a schematic diagram of message transmission between wireless communication systems according to an embodiment of the present disclosure.

[0012] Figures 6A to 6C is a schematic diagram of message transmission between wireless communication systems according to an embodiment of the present disclosure.

[0013] Figure 7 A flow chart illustrating a method for wireless communication according to an embodiment of the present disclosure.

[0014] Figures 8A to 8C A flow chart illustrating a method for wireless communication according to an embodiment of the present disclosure.

[0015] Figure 9 A flow chart illustrating a method for wireless communication according to an embodiment of the present disclosure.

[0016] Figure 10 An example block diagram illustrating an apparatus according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0017] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure can be practiced. It should be understood that the same or equivalent functions can be achieved by different embodiments that are intended to be encompassed by the spirit and scope of the present disclosure.

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

[0019] CN 103 may include a core access and mobility management function (AMF) entity. BS 102, which may communicate with CN 103, may operate or work under the control of the AMF entity. CN 103 may further include a user plane function (UPF) entity, which may be communicatively coupled with the AMF entity.

[0020] BSs 102 may be distributed over a geographic area. In certain embodiments of the present application, BSs 102 may also be referred to as access points, access terminals, base stations, base units, macrocells, Node-Bs, evolved Node-Bs (eNBs), gNBs, Home Node-Bs, relay nodes, or devices, or other terms used in the art. BSs 102 are typically part of a radio access network that may include one or more controllers communicatively coupled to one or more corresponding BSs.

[0021] UE 101 may include, for example, but not limited to, a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), an Internet of Things (IoT) device, or the like.

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

[0023] In some embodiments of the present application, UE 101 may include, for example, but not limited to, a wearable device such as a smartwatch, a fitness band, an optical head-mounted display, or the like. Furthermore, UE 101 may be referred to as a subscriber unit, a mobile device, 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 other terms used in the art to describe the UE. UE 101 may communicate directly with BS 102 via uplink communication signals.

[0024] The wireless communication system 100 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, time division multiple access (TDMA)-based networks, code division multiple access (CDMA)-based networks, orthogonal frequency division multiple access (OFDMA)-based networks, long term evolution (LTE) networks, 3GPP-based networks, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.

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

[0026] In some embodiments of the present application, BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Furthermore, in some embodiments of the present application, BS 102 may communicate via licensed spectrum, while in other embodiments, BS 102 may communicate via unlicensed spectrum. The present application is not intended to be limited to any particular wireless communication system architecture or protocol implementation. In still other embodiments of the present application, BS 102 may communicate with UE 101 using 3GPP 5G protocols.

[0027] In some existing protocols, small data transmission may be introduced in wireless communication system 100 to improve the efficiency of data transmission between UE 101 and BS 102. However, the specific details of whether base stations and user equipment can perform differentiated services (e.g., applications) with small data transmission have not been discussed, and some issues still need to be addressed.

[0028] In some embodiments, because a data radio bearer (DRB) may correspond to a service (e.g., an application), configuring different DRB transmission data as different data transmissions (i.e., small data transmission or normal data transmission) can be used to distinguish different data transmissions (i.e., small data transmission or normal data transmission) for the corresponding service. Specifically, when the DRB between UE 101 and BS 102 is configured to allow small data transmission (i.e., small data transmission is allowed to be performed by the DRB), the service corresponding to the DRB can be performed using the small data transmission. In some embodiments, because a logical channel (LCH) may correspond to a DRB, configuring different LCH transmission data as different data transmissions can be used to distinguish different data transmissions for the corresponding DRB and further distinguish different data transmissions for the corresponding service.

[0029] Therefore, in order to distinguish whether a service (e.g., an application) can be performed using small data transmission, BS 102 may determine configuration information 102C for small data transmission, and configuration information 102C may be used to configure at least one DRB / LCH for at least one small data transmission between UE 101 and BS 102. In other words, configuration information 102C may indicate to UE 101 which CRB / LCH(s) between UE 101 and BS 102 are allowed to perform small data transmission in a pre-configured uplink resource (e.g., a physical uplink shared channel (PUSCH)).

[0030] Additionally, in some embodiments, BS 102 may determine configuration information 102C for small data transmission, and configuration information 102C may be used to configure to resume use of at least one DRB / LCH for at least one small data transmission between UE 101 and BS 102. In other words, configuration information 102C may indicate to UE 101 which CRB / LCH(s) between UE 101 and BS 102 are allowed to resume small data transmission in pre-configured uplink resources.

[0031] refer to Figure 2 After determining the configuration information 102C, the BS 102 may transmit the configuration information 102C to the UE 101. Subsequently, the UE 101 may receive the configuration information from the BS 102. The UE 101 may then store the configuration information 102C for later use.

[0032] In some embodiments, small data transmission may be performed when UE 101 is in a non-active state. Thus, when UE 101 enters a non-active state (e.g., from a connected state), UE 101 may apply configuration information 102C to configure which DRB / LCH(s) between UE 101 and BS 102 are allowed to perform small data transmission in pre-configured uplink resources.

[0033] Therefore, when UE 101 is in an inactive state and data on the DRB / LCH arrives (i.e., the data is ready to be further processed), UE 101 can determine whether the DRB / LCH is configured (i.e., allowed) for small data transmission. If the DRB / LCH is configured (i.e., allowed) for small data transmission, UE 101 can perform small data transmission to transmit the data to BS 102 via the DRB / LCH. In other words, UE 101 can transmit the data to BS 102 as small data transmission via the DRB / LCH.

[0034] If the DRB / LCH is not configured (i.e., not allowed) for small data transmission, the UE 101 may not perform small data transmission to transmit data to the BS 102 through the DRB / LCH. Furthermore, in some implementations, when the DRB / LCH is not configured (i.e., not allowed) for small data transmission, the UE 101 may enter a connected state and perform normal data transmission to transmit data to the BS 102 through the DRB / LCH.

[0035] In some embodiments, configuration information 102C may be transmitted between UE 101 and BS 102 during a radio resource control (RRC) procedure. More specifically, configuration information 102C may be transmitted from BS 102 to UE 101 along with an RRC message during a corresponding RRC procedure.

[0036] In some embodiments, the configuration information 102C may be transmitted from the BS 102 to the UE 101 together with an RRC release message during the RRC release procedure. Figure 3A In detail, when UE 101 is in a connected state through an RRC connection, UE 101 may transmit a request 101Q to BS 102. Request 101Q may be used to request configuration information 102C for small data transmission when UE 101 is in an inactive state. After receiving request 101Q, BS 102 may determine configuration information 102C according to request 101Q.

[0037] Then, when the RRC connection between UE 101 and BS 102 needs to be released, BS 102 may transmit an RRC message 102R1 (e.g., RRCConnectionRelease) to UE 101. Configuration information 102C may be included in RRC message 102R1. Then, after receiving RRC message 102R1, UE 101 may retrieve configuration information 102C from RRC message 102R1 and store configuration information 102C. Furthermore, once UE 101 enters an inactive state, UE 101 may apply configuration information 102C. In some implementations, UE 101 may store configuration information 102C as a UE access stratum (AS) context.

[0038] Therefore, when UE 101 is in an inactive state and data D1 arrives on the DRB / LCH, UE 101 can determine whether the DRB / LCH is configured (i.e., allowed) for small data transmission. If the DRB / LCH is configured (i.e., allowed) for small data transmission, UE 101 can perform a small data transmission to transmit data D1 to BS 102 via the DRB / LCH. In other words, UE 101 can transmit data D1 as a small data transmission to BS 102 via the DRB / LCH. In some implementations, UE 101 can first recover the DRB / LCH and then perform a small data transmission to transmit data D1 to BS 102 via the DRB / LCH.

[0039] Please refer to Figure 3B If the DRB / LCH is not configured (ie, not allowed) for small data transmission, the UE 101 may not perform the small data transmission (as depicted by the dashed line) of transmitting the data D1 to the BS 102 via the DRB / LCH. Figure 3C In some embodiments, when DRB / LCH is not configured (i.e., not allowed) for small data transmission, UE 101 may transmit an RRC message 101R1 (e.g., RRCConnectionResumeRequest or RRCConnectionRequest) to enter a connected state and perform normal data transmission to transmit data D1 to BS 102 via DRB / LCH in the connected state.

[0040] In some embodiments, the configuration information 102C may be transmitted from the BS 102 to the UE 101 together with an RRC configuration message in the RRC connected state. Figure 4A In detail, when UE 101 is in a connected state through an RRC connection, UE 101 may transmit a request 101Q to BS 102. Request 101Q may be used to request configuration information 102C for small data transmission when UE 101 is in an inactive state. After receiving request 101Q, BS 102 may determine configuration information 102C according to request 101Q.

[0041] BS 102 may then transmit an RRC message 102R2 (e.g., RRCConfiguration) to UE 101 in the RRC Connected state. Configuration information 102C may be included in RRC message 102R2. Upon receiving RRC message 102R2, UE 101 may retrieve configuration information 102C from RRC message 102R2 and store configuration information 102C. Furthermore, once UE 101 enters the Inactive state, UE 101 may apply configuration information 102C. In some implementations, UE 101 may store configuration information 102C as a UE AS context.

[0042] Therefore, when UE 101 is in an inactive state and data D2 arrives on the DRB / LCH, UE 101 can determine whether the DRB / LCH is configured (i.e., allowed) for small data transmission. If the DRB / LCH is configured (i.e., allowed) for small data transmission, UE 101 can perform a small data transmission to transmit data D2 to BS 102 via the DRB / LCH. In other words, UE 101 can transmit data D2 as a small data transmission to BS 102 via the DRB / LCH. In some implementations, UE 101 can first recover the DRB / LCH and then perform a small data transmission to transmit data D2 to BS 102 via the DRB / LCH.

[0043] Please refer to Figure 4B If the DRB / LCH is not configured (ie, not allowed) for small data transmission, the UE 101 may not perform the small data transmission of the data D2 to the BS 102 via the DRB / LCH (as depicted by the dotted line). Figure 4C In some implementations, when DRB / LCH is not configured (i.e., not allowed) for small data transmission, UE 101 may transmit an RRC message 101R1 (e.g., RRCConnectionResumeRequest or RRCConnectionRequest) to enter a connected state and perform normal data transmission to transmit data D2 to BS 102 via DRB / LCH in the connected state.

[0044] In some embodiments, the configuration information 102C may be transmitted from the BS 102 to the UE 101 together with the RRC release message during the RRC release procedure and the data for small data transmission may be transmitted to the CN 103 via the BS 102 according to the mapping relationship between the flow (e.g., QoS flow) and the DRB / LCH. Figure 5AIn detail, when UE 101 is in a connected state through an RRC connection, UE 101 may transmit a request 101Q to BS 102. Request 101Q may be used to request configuration information 102C for small data transmission when UE 101 is in an inactive state. After receiving request 101Q, BS 102 may determine configuration information 102C according to request 101Q.

[0045] Then, when the RRC connection between UE 101 and BS 102 needs to be released, BS 102 may transmit an RRC message 102R1 (e.g., RRCConnectionRelease) to UE 101. Configuration information 102C may be included in RRC message 102R1. Then, after receiving RRC message 102R1, UE 101 may retrieve configuration information 102C from RRC message 102R1 and store configuration information 102C. Furthermore, once UE 101 enters an inactive state, UE 101 may apply configuration information 102C. In some implementations, UE 101 may store configuration information 102C as a UE AS context.

[0046] In some embodiments, after applying the configuration information 102C, the UE 101 may identify a mapping relationship between the flow(s) and the configured (e.g., allowed) DRB / LCH. Then, based on the mapping relationship, the lower layer (e.g., AS layer) of the UE 101 may indicate to the higher layer (e.g., non-access stratum, NAS layer) of the UE 101 that the flow(s) corresponding to the configured (i.e., allowed) DRB / LCH are available for small data transmission.

[0047] In some implementations, a mapping relationship may indicate which DRB / LCH a stream corresponds to. More specifically, a DRB / LCH may include one or more streams, and a mapping relationship may record the corresponding DRB / LCH for each stream. For example, when DRB / LCH "X" includes one stream "x" (i.e., stream "x" corresponds to DRB / LCH "X"), the mapping relationship may indicate that stream "x" corresponds to DRB / LCH "X". For another example, when DRB / LCH "A" includes two streams "a" and "b" (i.e., two streams "a" and "b" correspond to DRB / LCH "A"), the mapping relationship may indicate that stream "a" corresponds to DRB / LCH "A" and stream "b" corresponds to DRB / LCH "A".

[0048] Therefore, when UE 101 is in an inactive state and data D3 on a flow arrives, UE 101 can determine whether the flow is mapped to a configured DRB / LCH based on the mapping relationship. If the flow is mapped to a configured (i.e., allowed) DRB / LCH for small data transmission, UE 101 can perform small data transmission to transmit data D3 together with RRC message 101R2 or a higher layer (e.g., NAS layer) message (not shown) to CN 103 via BS 102. In other words, UE 101 can transmit data D3 as a small data transmission together with RRC message 101R2 or a higher layer message to CN 103 via BS 102 via RRC message 101R2.

[0049] Please refer to Figure 5B If the flow corresponds to a DRB / LCH that is not configured (ie, not allowed) for small data transmission, the UE 101 may not perform the small data transmission of the data D3 to the CN 103. Figure 5C In some embodiments, when a flow corresponds to a DRB / LCH that is not configured (i.e., not allowed) for small data transmission, UE 101 may transmit an RRC message 101R1 (e.g., RRCConnectionResumeRequest or RRCConnectionRequest) to enter a connected state and perform normal data transmission to transmit data D3 to CN 103 via BS 102 through the flow within the corresponding DRB / LCH in the connected state.

[0050] In some embodiments, the configuration information 102C may be transmitted from the BS 102 to the UE 101 together with the RRC configuration message in the RRC connected state, and the data for small data transmission may be transmitted to the CN 103 via the BS 102 according to the mapping relationship between the flow (e.g., QoS flow) and the DRB / LCH. Figure 6A In detail, when UE 101 is in a connected state through an RRC connection, UE 101 may transmit a request 101Q to BS 102. Request 101Q may be used to request configuration information 102C for small data transmission when UE 101 is in an inactive state. After receiving request 101Q, BS 102 may determine configuration information 102C according to request 101Q.

[0051] BS 102 may then transmit an RRC message 102R2 (e.g., RRCConfiguration) to UE 101 in the RRC Connected state. Configuration information 102C may be included in RRC message 102R2. Upon receiving RRC message 102R2, UE 101 may retrieve configuration information 102C from RRC message 102R2 and store configuration information 102C. Furthermore, once UE 101 enters the Inactive state, UE 101 may apply configuration information 102C. In some implementations, UE 101 may store configuration information 102C as a UE AS context.

[0052] In some embodiments, after applying the configuration information 102C, the UE 101 may identify a mapping relationship between the flow(s) and the configured (e.g., allowed) DRB / LCH. Then, based on the mapping relationship, the lower layer (e.g., AS layer) of the UE 101 may indicate to the higher layer (e.g., non-access stratum, NAS layer) of the UE 101 that the flow(s) corresponding to the configured (i.e., allowed) DRB / LCH are available for small data transmission.

[0053] Therefore, when UE 101 is in an inactive state and data D4 on a flow arrives, UE 101 can determine whether the flow is mapped to a configured DRB / LCH based on the mapping relationship. If the flow is mapped to a configured (i.e., allowed) DRB / LCH for small data transmission, UE 101 can perform small data transmission to transmit data D4 together with RRC message 101R2 or a higher layer (e.g., NAS layer) message (not shown) to CN 103 via BS 102. In other words, UE 101 can transmit data D4 as a small data transmission together with RRC message 101R2 or a higher layer message to CN 103 via BS 102 via RRC message 101R2.

[0054] Please refer to Figure 6B If the data D4 on the flow f corresponds to a DRB / LCH that is not configured (ie, not allowed) for small data transmission, the UE 101 may not perform the small data transmission of the data D4 to the CN 103. Figure 6C In some implementations, when a flow corresponds to a DRB / LCH that is not configured (i.e., not allowed) for small data transmission, UE 101 may transmit an RRC message 101R1 (e.g., RRCConnectionResumeRequest or RRCConnectionRequest) to enter a connected state and perform normal data transmission to transmit data D4 to CN 103 via BS 102 through the flow within the corresponding DRB / LCH in the connected state.

[0055] In some embodiments, conditions may be further applied to UE 101 to determine whether small data transmission can be performed. Specifically, if the conditions are met, small data transmission can be performed. If the conditions are not met, small data transmission may not be performed even if the corresponding DRB / LCH is configured (i.e., allowed) for small data transmission.

[0056] In some embodiments, the condition may be related to the size of a medium access control (MAC) protocol data unit (PDU). Specifically, when there is a configured (i.e., allowed) DRB / LCH for small data transmission and the data to be transmitted by the configured DRB / LCH is generated in a MAC PDU, the UE 101 may determine whether the size of the MAC PDU is greater than a threshold value "T1".

[0057] If the MAC PDU is greater than the threshold value "T1", UE 101 may not perform small data transmission for data on the preconfigured uplink resources. In other words, UE 101 may not transmit data on the preconfigured uplink resources as small data transmission. If the MAC PDU is not greater than the threshold value "T1", UE 101 may perform small data transmission for data on the preconfigured uplink resources. In other words, UE 101 may transmit data on the preconfigured uplink resources as small data transmission.

[0058] In some embodiments, when it is determined that the MAC PDU is larger than the threshold "T1", UE 101 may regenerate a new MAC PDU for data to be transmitted by the configured DRB / LCH and adjust parameters so that the size of the new MAC PDU is not larger than the threshold "T1".

[0059] In some implementations, the condition may be related to the buffered data size of a Radio Link Control (RLC) or Packet Data Convergence Protocol (PDCP) transport entity. Specifically, for each RLC / PDCP transport entity corresponding to one of the configured (i.e., allowed) DRBs / LCHs, UE 101 may determine whether the current buffered data size of the RLC / PDCP transport entity is greater than a threshold value "T2".

[0060] If the current buffered data size of the RLC / PDCP transmission entity is greater than the threshold value "T2", the UE 101 may not perform small data transmission on the data on the preconfigured uplink resources through the corresponding DRB / LCH. In other words, the UE 101 may not transmit the data on the preconfigured uplink resources as small data transmission through the corresponding DRB / LCH. If the current buffered data size of the RLC / PDCP transmission entity is not greater than the threshold value "T2", the UE 101 may perform small data transmission on the data on the preconfigured uplink resources through the corresponding DRB / LCH. In other words, the UE 101 may transmit the data on the preconfigured uplink resources as small data transmission through the corresponding DRB / LCH.

[0061] It should be noted that an LCH with a higher priority may be used before an LCH with a lower priority. Therefore, in some embodiments, the condition may be related to the priority of the LCH. In detail, UE 101 may determine whether the priority of the selected LCH is greater than a priority threshold. If the priority of the selected LCH is higher than the priority threshold, UE 101 may perform a small data transmission for the data on the pre-configured uplink resources through the corresponding DRB / LCH. In other words, UE 101 may transmit data as a small data transmission on the pre-configured uplink resources through the corresponding DRB / LCH. If the priority of the selected LCH is not higher than the priority threshold, UE 101 may not perform a small data transmission through the corresponding DRB / LCH.

[0062] In some embodiments, a hybrid automatic repeat request (HARQ) process may be applied to the data of the small data transmission between UE 101 and BS 102 to check the correctness of the transmission. If UE 101 determines, based on the HARQ process, that the data of the small data transmission is not successfully transmitted to BS 102 on the PUSCH and the autonomous retransmission function is enabled, UE 101 may autonomously retransmit the data of the small data transmission to BS 102 on the PUSCH.

[0063] In some embodiments, the configuration information 102C may indicate a restriction on selecting an LCH for each preconfigured uplink resource for small data transmission. Thus, after receiving the configuration information 102C, the UE 101 may add a restriction on selecting an LCH for each preconfigured uplink resource for small data transmission. The UE 101 may then determine whether the LCH(s) are configured to be allowed to transmit data as small data transmission via the preconfigured uplink resource.

[0064] According to the restriction, if UE 101 determines that an LCH is available for transmitting data as a small data transmission via pre-configured uplink resources, then UE 101 may transmit the data as a small data transmission on the LCH. According to the restriction, if UE 101 determines that an LCH is not allowed to transmit data as a small data transmission via pre-configured uplink resources, then the UE may not transmit the data as a small data transmission on the LCH. In some embodiments, the restriction may be configured as a logical channel priority (LCP) restriction.

[0065] For example, according to 3GPP specification #38.321, LCP restrictions can be described as follows:

[0066] 1> For each UL grant, select a logical channel that meets all of the following conditions:

[0067] 2> the set of allowed subcarrier spacing index values ​​in allowedSCS-List (if configured) contains the subcarrier spacing index associated with the UL grant; and

[0068] 2> maxPUSCH-Duration (if configured) is greater than or equal to the PUSCH transmission duration associated with the UL grant; and

[0069] 2> In case the UL grant is configured grant type 1, configuredGrantType1Allowed (if configured) is set to true; and

[0070] 2> allowedServingCells (if configured) contains cell information associated with UL grants. Does not apply to logical channels associated with DRBs configured with PDCP duplication (ie CA duplication) within the same MAC entity for which PDCP duplication is deactivated.

[0071] In some implementations of the restriction of selecting an LCH per preconfigured uplink resource for small data transmission, the following new restrictions may be introduced:

[0072] 2> In case the UL grant is a configured grant for small data transmission, smallDataAllowed (if configured) is set to true.

[0073] It should be noted that "smallDataAllowed" may be a term used to represent a parameter for enabling / disabling small data transmission. For example, when the value of "smallDataAllowed" is "0", this means that small data transmission is disabled (i.e., not allowed). When the value of "smallDataAllowed" is "1", this means that small data transmission is enabled (i.e., allowed). For another example, when the string of "smallDataAllowed" is "no", this means that small data transmission is disabled (i.e., not allowed). When the string of "smallDataAllowed" is "yes", this means that small data transmission is enabled (i.e., allowed). In some embodiments, the term used to represent the parameter for enabling / disabling small data transmission can be customized by the operator. For example, the operator can use the term "AAAA" or "BBBB" to represent the parameter.

[0074] Figure 7 A flowchart illustrating a method for wireless communication according to some embodiments of the present application is provided. Figure 7 In some embodiments of the present application, method 700 is performed by a UE (eg, UE 101) and a BS (eg, BS 102).

[0075] Operation S701 is performed to transmit configuration information of small data transmission to a UE by a BS. Operation S702 is performed to receive configuration information from the BS by the UE. Operation S703 is performed to perform at least one small data transmission by the UE according to the configuration information of small data transmission.

[0076] Figures 8A to 8C A flowchart illustrating a method for wireless communication according to some embodiments of the present application is provided. Figures 8A to 8C In some embodiments of the present application, method 800 is performed by a UE (eg, UE 101) and a BS (eg, BS 102).

[0077] Operation S801 is performed to transmit, by a UE, a request to a base station for configuration information for small data transmission in an inactive state. Operation S802 is performed to receive, by the base station, the request from the UE. Operation S803 is performed to transmit, by the base station, configuration information to the UE in accordance with the request. In some embodiments, the configuration information may indicate DRB(s) / LCH(s) for small data transmission. In some embodiments, the configuration information may further be used to restore DRB(s) / LCH(s) and indicate the restored DRB(s) / LCH(s) for small data transmission.

[0078] Operation S804 is performed to receive configuration information from the BS by the UE. Operation S805 is performed to store the configuration information by the UE. In some embodiments, when the UE enters an inactive state, operation S806 is performed by the UE to apply the configuration information.

[0079] Please refer to Figure 8B . From the perspective of the user plane, in some embodiments, operation S807 is performed to determine, by the UE, whether data on the DRB / LCH has arrived and whether the DRB / LCH is indicated (e.g., allowed) for small data transmission. If the DRB / LCH is not configured (e.g., not allowed) for small data transmission, then operation S808 is performed to transmit the arrived data to the BS by the UE after the UE enters the connected state. If data on the DRB / LCH has arrived and the DRB / LCH is configured (e.g., allowed) for small data transmission, then operation S809 is performed to transmit the data as small data transmission to the BS via the allowed DRB / LCH by the UE. Operation S810 is performed to receive the arrived data from the UE as small data transmission by the BS.

[0080] Please refer to Figure 8C From the perspective of the control plane, in some embodiments, operation S811 is performed to identify, by the UE, a mapping relationship between (several) flows and (several) DRBs indicated (e.g., allowed) for small data transmission. Operation S812 is performed to indicate, by a lower layer (e.g., an AS layer) of the UE, to a higher layer (e.g., a NAS layer) of the UE, the (several) flows for small data transmission.

[0081] Operation S813 is performed to determine, by the UE, based on the mapping relationship, whether data on the flow has arrived and whether the flow is mapped to the configured DRB / LCH. If not, operation S814 is performed to transmit the data to the BS after the UE enters the connected state. If yes, operation S815 is performed to transmit the data to the BS as a small data transmission by the UE along with another RRC message or a higher layer (e.g., NAS layer) message.

[0082] In some embodiments, small data transmission may be performed when a condition is met. Specifically, the UE may determine whether the size of the MAC PDU for the DRB(s) indicated for small data transmission is greater than a threshold. If the MAC PDU is greater than the threshold, the UE may not perform small data transmission. If the MAC PDU is not greater than the threshold, the UE may perform small data transmission via the allowed DRB(s).

[0083] Figure 9 A flowchart illustrating a method for wireless communication according to some embodiments of the present application is provided. Figure 9In some embodiments of the present application, method 900 is performed by a UE (eg, UE 101) and a BS (eg, BS 102).

[0084] Operation S901 is performed to transmit configuration information of small data transmission to UE by BS. In some embodiments, the configuration information may indicate a restriction on selecting LCH for each pre-configured uplink resource for small data transmission. Operation S902 is performed to receive configuration information from BS by UE.

[0085] Operation S903 is performed to determine, by the UE, whether the LCH is configured to allow transmission of data as a small data transmission on the pre-configured uplink resources. If so, operation S904 is performed to transmit data as a small data transmission on the pre-configured uplink resources via the LCH by the UE. Operation S905 is performed to receive data as a small data transmission on the pre-configured uplink resources via the LCH by the BS. In some embodiments, the restriction may be configured as an LCP restriction.

[0086] In some embodiments, a HARQ process may be introduced into the previous method. Specifically, the UE may determine whether the data of the small data transmission is successfully transmitted to the BS on the pre-configured uplink resources based on the HARQ process. If not, the UE may autonomously retransmit the data of the small data transmission to the BS on the pre-configured uplink resources.

[0087] Figure 10 An example block diagram illustrating apparatus 1 according to an embodiment of the present disclosure.

[0088] like Figure 10 As shown in FIG, apparatus 1 may include at least one non-transitory computer-readable medium ( Figure 10 Not illustrated), receiving circuit system 11, transmitting circuit system 13 and coupled to the non-transitory computer readable medium ( Figure 10 ), a processor 15 of the receiving circuit system 11 and the transmitting circuit system 13. The device 1 may be a user equipment or a base station.

[0089] Although elements such as processor 15, transmit circuitry 13, and receive circuitry 11 are described in the singular in this figure, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present disclosure, receive circuitry 11 and transmit circuitry 13 are combined into a single device, such as a transceiver. In certain embodiments of the present disclosure, apparatus 1 may further include an input device, memory, and / or other components.

[0090] In some embodiments of the present disclosure, a non-transitory computer-readable medium may store thereon computer-executable instructions that cause a processor to implement the method for the base station described above. For example, when the computer-executable instructions are executed, the processor 15 interacts with the receiving circuit system 11 and the transmitting circuit system 13 to perform the method for the base station described above. Figures 1 to 6C The operation of the BS is depicted in FIG.

[0091] In some embodiments of the present disclosure, a non-transitory computer-readable medium may store thereon computer-executable instructions that cause a processor to implement the method for the user equipment described above. For example, when the computer-executable instructions are executed, the processor 1 interacts with the receiving circuit system 11 and the transmitting circuit system 13 to perform the method for transmitting the user equipment described above. Figures 1 to 6C The operation of the UE is depicted in FIG.

[0092] Those skilled in the art will appreciate that the operations of the methods described in conjunction 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. The 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 the methods 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.

[0093] Although the present disclosure has been described with reference to specific embodiments thereof, it is apparent that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, the various components of an embodiment may be interchanged, added, or replaced in other embodiments. Moreover, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, a person skilled in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure set forth herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0094] In this file, the term "includes / including" or any other variation thereof is intended to encompass non-exclusive inclusion, such that the process, method, article, or apparatus comprising a list of elements includes not only those elements but may also include other elements that are not explicitly listed or inherent to the process, method, article, or apparatus. An element beginning with "a / an" or the like (without further constraints) does not exclude the presence of additional identical elements in the process, method, article, or apparatus comprising the element. Moreover, the term "another" is defined as at least a second or more. As used herein, the term "having" and the like are defined as "comprising."

Claims

1. A user equipment comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receiving configuration information for small data transmission from a base station, wherein the configuration information indicates a restriction on selecting a logical channel for each preconfigured uplink resource for at least one small data transmission; determining whether at least one logical channel is configured to transmit data as a small data transmission via preconfigured uplink resources; and The at least one small data transmission is performed using the base station according to the configuration information of the small data transmission.

2. The UE of claim 1 , wherein the at least one processor is further configured to cause the UE to: A request for the configuration information for at least one small data transmission in an inactive state is transmitted to the base station. 3 . The UE according to claim 1 , wherein the configuration information indicates at least one data radio bearer (DRB) for the at least one small data transmission.

4. The UE of claim 3, wherein the configuration information further indicates to the user equipment that the at least one DRB is restored and used for the at least one small data transmission.

5. The UE of claim 3, wherein the at least one processor is further configured to cause the UE to: storing the configuration information as a user equipment access stratum context; and The configuration information is applied when the user equipment enters an inactive mode.

6. The UE of claim 5 , wherein the configuration information for the small data transmission is received together with a radio resource control (RRC) message, and performing the at least one small data transmission further comprises: determining whether the at least one DRB for transmitting data is configured for small data transmission; and The data is transmitted to the base station as at least one small data transmission when the at least one DRB for transmitting the data is configured for small data transmission.

7. The UE of claim 5 , wherein the configuration information for the small data transmission is received together with a radio resource control (RRC) message, and performing the at least one small data transmission further comprises: Identifying a mapping relationship between one of the at least one DRB and at least one flow; and The at least one flow for the at least one small data transmission is indicated to a higher layer of the user equipment.

8. The UE of claim 7, wherein the at least one processor is further configured to cause the UE to: determining whether data is configured for transmission via the at least one stream; and The data is transmitted to the base station as the at least one small data transmission according to the step of indicating the at least one flow for the at least one small data transmission to the higher layer of the user equipment together with another RRC message or with a higher layer message.

9. The UE of claim 3 , wherein to perform the at least one small data transmission, the at least one processor is further configured to cause the UE to: determining whether a condition is satisfied; and The at least one small data transmission is performed via the at least one DRB when the condition is met.

10. The UE of claim 9, wherein to determine whether the condition is satisfied, the at least one processor is further configured to cause the UE to: It is determined whether a size of a medium access control (MAC) protocol data unit (PDU) for the at least one DRB for the at least one small data transmission is greater than a threshold.

11. The UE of claim 1, wherein the restriction is configured as a Logical Channel Priority (LCP) restriction.

12. The UE of claim 1 , wherein the at least one processor is further configured to cause the UE to: determining, according to a hybrid automatic repeat request (HARQ) process, that data of the at least one small data transmission was not successfully transmitted to the base station on pre-configured uplink resources; and The data of the at least one small data transmission is autonomously retransmitted to the base station on the pre-configured uplink resources.

13. A base station, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmitting configuration information for small data transmission to a user equipment, wherein the configuration information indicates a restriction on selecting a logical channel for each preconfigured uplink resource for at least one small data transmission; determining whether at least one logical channel is configured to receive data as a small data transmission via preconfigured uplink resources; and The at least one small data transmission is performed with the user equipment according to the configuration information for small data transmission.

14. The base station of claim 13, wherein the at least one processor is further configured to cause the base station to: A request is received from the user equipment, wherein the request is for requesting the configuration information for the at least one small data transmission in an inactive state. 15 . The base station of claim 13 , wherein the configuration information indicates at least one data radio bearer (DRB) for the at least one small data transmission.

16. The base station of claim 15, wherein the configuration information further indicates to the user equipment that the at least one DRB is restored and used for the at least one small data transmission.

17. The base station of claim 16 , wherein the configuration information for small data transmission is transmitted together with a radio resource control (RRC) message, and to perform the at least one small data transmission, the at least one processor is further configured to cause the base station to: Data is received from the user equipment via the at least one DRB as the at least one small data transmission.

18. The base station of claim 15, wherein to perform the at least one small data transmission, the at least one processor is further configured to cause the base station to: The at least one small data transmission is performed via the at least one DRB when a condition is met.

19. The base station of claim 18, wherein the condition indicates whether a size of a medium access control (MAC) protocol data unit (PDU) used for the at least one DRB for the at least one small data transmission is equal to or smaller than a threshold.

20. The base station of claim 13, wherein the restriction is configured as a Logical Channel Priority (LCP) restriction.

21. The base station of claim 13, wherein the at least one processor is further configured to cause the base station to: determining, according to a hybrid automatic repeat request (HARQ) process, that data of the at least one small data transmission was not successfully received from the user equipment on pre-configured uplink resources; and The data of the at least one small data transmission is re-received from the user equipment on the pre-configured uplink resources.

22. A method of user equipment, comprising: receiving configuration information for small data transmission from a base station, wherein the configuration information indicates a restriction on selecting a logical channel for each preconfigured uplink resource for at least one small data transmission; determining whether at least one logical channel is configured to transmit data as a small data transmission via preconfigured uplink resources; and The at least one small data transmission is performed using the base station according to the configuration information of the small data transmission.

23. A method of a base station, comprising: transmitting configuration information for small data transmission to a user equipment, wherein the configuration information indicates a restriction on selecting a logical channel for each preconfigured uplink resource for at least one small data transmission; determining whether at least one logical channel is configured to receive data as a small data transmission via preconfigured uplink resources; and The at least one small data transmission is performed with the user equipment according to the configuration information for small data transmission.

Images