Non-SDT DRB processing

Abstract

The present disclosure relates to non-SDT DRB processing, and in particular to apparatuses, systems, and methods for non-small data transmission (non-SDT) dedicated radio bearer (DRB) processing while in a radio resource control (RRC) inactive state. The wireless device may determine, when operating in the RRC inactive state, that non-SDT data is available for transmission on the non-SDT DRB, and determine, based on one or more conditions, to transmit non-SDT data arrival information to the base station during the SDT procedure. The one or more conditions may be associated with a time of arrival of the non-SDT data and / or an amount of non-SDT data to be transmitted. The time of arrival may be relative to arrival of the SDT data, initiation of the SDT process, and / or initiation of a subsequent transmission cycle of the SDT process.

Description

[0001] This application is a divisional application of invention patent application 202180091340.8, filed on January 14, 2021, and entitled “Non-SDT DRB Processing”. Technical Field

[0002] The present disclosure relates to wireless communications, including apparatus, systems, and methods for performing non-SDT DRB processing during an SDT procedure (e.g., in 5G NR systems and beyond). Background Art

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these functions.

[0004] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators around the world, providing mobile broadband data and high-speed Internet access to their user base. LTE was first proposed in 2004 and first standardized in 2008. Since then, as the use of wireless communication systems has grown exponentially, the demand on wireless network operators has risen to support higher capacity for a higher density of mobile broadband users. As a result, research on new radio access technologies began in 2015, and in 2017, the first version of the fifth generation new radio (5G NR) was standardized.

[0005] 5G-NR (also referred to as NR) provides higher capacity for a higher density of mobile broadband users compared to LTE, while also supporting ultra-reliable and massive machine-type communications from device to device, as well as lower latency and / or lower battery consumption. In addition, NR may allow for more flexible UE scheduling compared to current LTE. Therefore, efforts are being made to take advantage of the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Summary of the invention

[0006] Aspects relate to wireless communications, and more particularly to apparatus, systems, and methods for performing non-SDT DRB processing during an SDT process (e.g., in 5G NR systems and beyond).

[0007] For example, in some aspects, a user equipment device (UE) (such as UE 106) may be configured to perform a method for non-SDT dedicated radio bearer (DRB) processing while in a radio resource control (RRC) inactive state. The method may include the UE determining that non-SDT data is available for transmission on a non-SDT DRB when operating in the RRC inactive state, and determining to transmit non-SDT data arrival information to a base station during an SDT process based on one or more conditions. The one or more conditions may be associated with an arrival time of the non-SDT data and / or an amount of non-SDT data to be transmitted. The arrival time may be relative to the arrival of the SDT data, the initiation of the SDT process, and / or the initiation of a subsequent transmission period of the SDT process.

[0008] As another example, a base station (such as base station 102) may be configured to perform a method for non-SDT DRB processing. The method may include the base station receiving non-SDT data arrival information from a UE (such as UE 106) operating in an RRC inactive state during an SDT process, determining at least in part based on the amount of non-SDT data being less than a threshold to trigger the UE to transmit the non-SDT data via the SDT process, and transmitting to the UE an instruction to restore the non-SDT DRB for the SDT process. The instruction may be transmitted via a MAC CE. The threshold may be predefined (e.g., via a 3GPP standard), configured by the base station (e.g., by the network), and / or carrier-specific.

[0009] The techniques described herein may be implemented in and / or used with a plurality of different types of devices, including, but not limited to, any of unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), UTM servers, base stations, access points, cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.

[0010] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects, and advantages of the topics described herein will become apparent through the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A better understanding of the present subject matter may be obtained when the following detailed description of various aspects is considered in conjunction with the following drawings, in which:

[0012] Figure 1A

[0013] An example wireless communication system in accordance with some aspects is shown.

[0013] Figure 1B

[0013] Examples of base stations and access points in communication with user equipment (UE) devices are shown in accordance with some aspects.

[0014] Figure 2 An exemplary block diagram of a base station according to some aspects is shown.

[0015] Figure 3 An exemplary block diagram of a server according to some aspects is shown.

[0016] Figure 4 An exemplary block diagram of a UE according to some aspects is shown.

[0017] Figure 5 An exemplary block diagram of cellular communication circuitry according to some aspects is shown.

[0018] Fig. 6A An example of a 5G network architecture in accordance with some aspects is shown that combines both 3GPP (e.g., cellular) access and non-3GPP (e.g., non-cellular) access to the 5G CN.

[0019] Figure 6B An example of a 5G network architecture in accordance with some aspects is shown that combines both dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access.

[0020] Figure 7 An example of a baseband processor architecture for a UE according to some aspects is shown.

[0021] Fig. 8A An example of delay of small data transmission when the UE is required to perform an RRC recovery procedure is shown.

[0022] Figure 8B An example of small data transmission when the UE is not required to perform the RRC recovery procedure is shown.

[0023] Fig.9A , Fig. 9B and Fig. 9C Various scenarios of non-SDT procedures during an SDT procedure are shown in accordance with some aspects.

[0024] Fig. 10A and Fig. 10B

[0043] An example of network behavior upon receiving non-SDT data arrival information is shown in accordance with some aspects.

[0025] FIG. 11A to FIG. 11E

[0046] An example of UE behavior upon arrival of non-SDT data prior to initiating an SDT process in accordance with some aspects is shown.

[0026] FIG. 12A to FIG. 12D

[0046] An example of UE behavior upon arrival of non-SDT data after initiation of an SDT process in accordance with some aspects is shown.

[0027] Fig.13 An example of UE behavior when non-SDT data arrives during a subsequent SDT procedure is shown.

[0028] Fig.14 A block diagram illustrating an example of a method for non-small data transfer (SDT) dedicated radio bearer (DRB) processing while in a radio resource control (RRC) inactive state in accordance with some aspects.

[0029] Fig.15 A block diagram illustrating an example of a method for non-small data transfer (SDT) dedicated radio bearer (DRB) processing in accordance with some aspects.

[0030] Although the features described herein are susceptible to various modifications and alternative forms, specific aspects thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, the purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0031] Acronyms

[0032] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms used that may appear throughout this disclosure are as follows:

[0033] 3GPP: Third Generation Partnership Project

[0034] UE: User Equipment

[0035] RF: Radio Frequency

[0036] BS: Base Station

[0037] DL: Downlink

[0038] UL: Uplink

[0039] LTE: Long Term Evolution

[0040] NR: New Radio

[0041] 5GS: 5G system

[0042] 5GMM: 5GS Mobility Management

[0043] 5GC / 5GCN: 5G core network

[0044] IE: Information Element

[0045] CE: Control Element

[0046] MAC: Media Access Control

[0047] SSB: Synchronous Signal Block

[0048] CSI-RS: Channel State Information Reference Signal

[0049] PDCCH: Physical Downlink Control Channel

[0050] PDSCH: Physical Downlink Shared Channel

[0051] RRC: Radio Resource Control

[0052] RRM: Radio Resource Management

[0053] CORESET: Control resource set

[0054] TCI: Transmission Configuration Indicator

[0055] DCI: Downlink Control Indicator

[0056] the term

[0057] The following is a glossary of terms used in this disclosure:

[0058] Memory medium - any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROM, floppy disk or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drive or optical storage device; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or a combination thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., in the form of a computer program) that may be executed by one or more processors.

[0059] Carrier Media—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0060] Programmable hardware element - includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGA (field programmable gate array), PLD (programmable logic device), FPOA (field programmable object array), and CPLD (complex PLD). Programmable function blocks can vary from fine-grained (combinational logic unit or lookup table) to coarse-grained (arithmetic logic unit or processor core). Programmable hardware elements may also be referred to as "configurable logic units".

[0061] Computer system (or computer)—any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0062] User Equipment (UE) (or "UE device") - any of various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smart phones, portable gaming devices, laptop computers, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic, computing, and / or telecommunication device (or combination of devices) that is easily transportable by a user and capable of wireless communication.

[0063] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0064] Processing element (or processor) - refers to various elements or combinations of elements that are capable of performing functions in a device such as user equipment or cellular network equipment. Processing elements may include, for example, processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any of the above various combinations.

[0065] Channel - a medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" used in the present invention may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4MHz to 20MHz. In contrast, a WLAN channel may be 22MHz wide, while a Bluetooth channel may be 1Mhz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0066] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0067] Wi-Fi—The term "Wi-Fi" (or WiFi) has the full scope of its usual meaning and includes at least wireless communication networks or RATs that are served by wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi". Wi-Fi (WLAN) networks are distinct from cellular networks.

[0068] 3GPP access—refers to access (e.g., radio access technology) specified by the 3GPP standards. These accesses include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.

[0069] Non-3GPP access - refers to any access (e.g., radio access technology) not specified by the 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP accesses can be divided into two categories, "trusted" and "untrusted": trusted non-3GPP accesses can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP interoperates with the EPC / 5GC via network entities (such as Evolved Packet Data Gateways and / or 5GNR Gateways). In general, non-3GPP access refers to various types of non-cellular access technologies.

[0070] Automatic—refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the action or operation being directly specified or performed by a user input. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by a user, where the user provides input to directly perform the operation. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.

[0071] About - refers to a value that is close to a correct or exact value. For example, about can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold (or tolerance) may depend on the application. For example, in some aspects, "about" may mean within 0.1% of some specified or desired value, while in various other aspects, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the desires or requirements of a particular application.

[0072] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism", where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0073] Various components may be described as being "configured to" perform one or more tasks. In such environments, "configured to" is a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently performing the task, the component can be configured to perform the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently turned on, the component can be configured to perform the task. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0074] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0075] Figure 1A and Figure 1B :Communication System

[0076] Figure 1A A simplified exemplary wireless communication system according to some aspects is shown. Note that Figure 1A The system is merely one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems, as desired.

[0077] As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B to user equipment 106N, etc. through a transmission medium. Each user equipment may be referred to as a "user equipment" (UE) in this article. Therefore, user equipment 106 is referred to as UE or UE device.

[0078] The base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with the UEs 106A through 106N.

[0079] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0080] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. In particular, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0081] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping service to UE 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0082] Thus, while base station 102A may serve as a "serving cell" for UEs 106A-N as shown in FIG. 1 , each UE 106 may also be able to receive signals from (and possibly be within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity that provide service area sizes. For example, base stations 102A to 102B shown in FIG. 1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0083] In some aspects, base station 102A can be a next generation base station, such as a 5G New Radio (5G NR) base station or "gNB". In some aspects, a gNB can be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. In addition, a gNB cell can include one or more transition and reception points (TRPs). In addition, a UE capable of operating in accordance with 5G NR can connect to one or more TRPs within one or more gNBs.

[0084] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interface), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0085] Figure 1B A user equipment 106 (e.g., one of device 106A through device 106N) is shown in accordance with some aspects in communication with base station 102 and access point 112. UE 106 may be a device having cellular communication capabilities and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet computer, or virtually any type of wireless device.

[0086] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method aspects described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as an FPGA (field programmable gate array) configured to perform any of the method aspects described herein or any portion of any of the method aspects described herein.

[0087] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some aspects, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio component and / or GSM, LTE, LTE-Advanced, or 5G NR using a single shared radio component. The shared radio component may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio component may include any combination of a baseband processor, an analog radio frequency (RF) signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication technologies such as those discussed above.

[0088] In some aspects, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0089] Figure 2 :Block diagram of base station

[0090] Figure 2 1 shows an exemplary block diagram of a base station 102 according to some aspects. Note that Figure 3 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 204 that may execute program instructions for the base station 102. The processor 204 may also be coupled to a memory management unit (MMU) 240 or other circuit or device, which may be configured to receive addresses from the processor 204 and convert those addresses to locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0091] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide access to multiple devices (such as the UE device 106) as described above in FIG. Figure 2 Access to the telephone network as described in.

[0092] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 270 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0093] In some aspects, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB". In such aspects, base station 102 may be connected to a legacy Evolved Packet Core (EPC) network and / or to an NR Core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0094] The base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio component 230. The antenna 234 communicates with the radio component 230 via a communication chain 232. The communication chain 232 may be a receive chain, a transmit chain, or both. The radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0095] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5GNR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5GNR base station. As another possibility, the base station 102 may include a multimode radio component that can perform communications according to any one of a plurality of wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0096] As further described later herein, BS102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 204 of the base station 102 may be configured to implement or support implementing part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition thereto), in combination with one or more of the other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of the BS102 may be configured to implement or support implementing part or all of the features described herein.

[0097] Furthermore, as described herein, processor 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 204. Thus, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0098] Additionally, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) configured to perform the functions of radio 230. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 230.

[0099] Figure 3 :Block diagram of the server

[0100] Figure 3 An exemplary block diagram of a server 104 according to some aspects is shown. Note that Figure 3 The server 104 is just one example of a possible server. As shown, the server 104 may include a processor 344 that can execute program instructions for the server 104. The processor 344 may also be coupled to a memory management unit (MMU) 374, which may be configured to receive addresses from the processor 344 and convert these addresses to locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuits or devices.

[0101] Server 104 may be configured to provide access to network functionality to a plurality of devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.

[0102] In some aspects, server 104 can be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some aspects, server 104 can be connected to a legacy Evolved Packet Core (EPC) network and / or to a NR Core (NRC) network.

[0103] As further described later herein, the server 104 may include hardware and software components for implementing or supporting the features described herein. The processor 344 of the server 104 may be configured to implement or support implementing part or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, the processor 344 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition thereto), in combination with one or more of the other components 354, 364, and / or 374, the processor 344 of the server 104 may be configured to implement or support implementing part or all of the features described herein.

[0104] In addition, as described herein, processor 344 may be composed of one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0105] Figure 4 :UE block diagram

[0106] Figure 41 shows an exemplary simplified block diagram of a communication device 106 according to some aspects. Note that Figure 4 The block diagram of the communication device is only an example of a possible communication device. According to aspects, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices and other devices. As shown, the communication device 106 may include a group of components 400 configured to perform core functions. For example, the group of components may be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 400 may be implemented as a separate component or group of components for various purposes. This group of components 400 may be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0107] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as a connector I / F 420 (e.g., for connecting to a computer system; a docking station; a charging station; an input device such as a microphone, a camera, a keyboard; an output device such as a speaker; etc.), a display 460 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuits 430 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuits 429 (e.g., Bluetooth TM In some aspects, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0108] Cellular communication circuitry 430 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 435 and 436 as shown. Short-range to medium-range wireless communication circuitry 429 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, short-range to medium-range wireless communication circuitry 429 may be (e.g., communicatively; directly or indirectly) coupled to antennas 435 and 436 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 437 and 438. Short-range to medium-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

[0109] In some aspects, as further described below, the cellular communication circuitry 430 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). In addition, in some aspects, the cellular communication circuitry 430 can include a single transmit chain that can switch between radio components dedicated to specific RATs. For example, a first radio component can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio component, such as a second radio component that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with the dedicated receive chain and the shared transmit chain.

[0110] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include various elements such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0111] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 445. Note that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some aspects, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or implement SIM functionality in other ways. Thus, each SIM may be a single smart card that may be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Thus, the SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or the SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some aspects (such as when the SIM includes an eUICC), one or more of the SIMs may implement embedded SIM (eSIM) functionality; in such aspects, a single SIM of the SIM may execute multiple SIM applications. Each SIM may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some aspects, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality) as needed. For example, the UE 106 may include a combination of two embedded SIMs, two removable SIMs, or one embedded SIM and one removable SIM. Various other SIM configurations are also contemplated.

[0112] As described above, in some aspects, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 may allow UE 106 to support two different phone numbers, and may allow UE 106 to communicate on corresponding two or more corresponding networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM 410 may support a second RAT such as 5G NR. Of course, other implementations and RATs are also possible. In some aspects, when UE 106 includes two SIMs, UE 106 may support dual card dual communication (DSDA) functionality. The DSDA functionality may allow UE 106 to be connected to two networks (and use two different RATs) at the same time, or allow two connections supported by two different SIMs using the same or different RATs to be maintained on the same or different networks at the same time. The DSDA functionality may also allow UE 106 to receive voice calls or data traffic on any phone number at the same time. In some aspects, voice calls may be packet-switched communications. In other words, voice calls may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some aspects, the UE 106 may support dual SIM dual standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to standby for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some aspects, the DSDx functionality (DSDA or DSDS functionality) may be implemented using a single SIM (e.g., eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0113] As shown, SOC 400 may include a processor 402 that may execute program instructions for communication device 106 and a display circuit 404 that may perform graphics processing and provide display signals to display 460. Processor 402 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from processor 402 and convert those addresses to locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or to other circuits or devices (such as display circuit 404, short-range to medium-range wireless communication circuit 429, cellular communication circuit 430, connector I / F 420, and / or display 460). MMU 440 may be configured to perform memory protection and page table translation or setup. In some aspects, MMU 440 may be included as part of processor 402.

[0114] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuits. The communication device 106 may be configured to perform a method for performing non-SDT DRB processing during an SDT process as further described herein (e.g., in 5G NR systems and higher).

[0115] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to send a scheduling profile for power saving to the network. The processor 402 of the communication device 106 may be configured to implement part or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 402 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, the processor 402 of the communication device 106 may be configured to implement part or all of the features described herein.

[0116] In addition, as described in the present invention, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0117] Further, as described herein, the cellular communication circuit 430 and the short-range to medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-range to medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-range to medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-range to medium-range wireless communication circuit 429. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range to medium-range wireless communication circuit 429.

[0118] Figure 5 : Block diagram of a cellular communication circuit

[0119] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some aspects is shown. Note that Figure 5 The block diagram of the cellular communication circuit of is only one example of possible cellular communication circuits. According to aspects, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0120] Cellular communication circuitry 530 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 4 435a-435b and 436 shown in FIG. 436. In some aspects, the cellular communication circuit 530 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5GNR).

[0121] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for transmitting and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some aspects, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0122] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may be in communication with the RF front end 540. The RF front end 540 may include circuits for transmitting and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some aspects, the receiving circuit 542 may be in communication with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0123] In some aspects, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 530 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the modem 510, the switch 570 may be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 530 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the modem 520, the switch 570 may be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0124] In some aspects, the cellular communication circuit 530 may be configured to perform methods for non-SDT DRB processing during an SDT process as further described herein (e.g., in 5G NR systems and beyond).

[0125] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the feature parts described herein.

[0126] In addition, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0127] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a scheduling profile for power saving to a network, as well as various other techniques described herein. The processor 522 may be configured to implement part or all of the feature parts described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement part or all of the feature parts described herein.

[0128] In addition, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0129] Fig. 6A , Figure 6B and Figure 7 : 5G core network architecture—interworking with Wi-Fi

[0130] In some aspects, the 5G core network (CN) may be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Fig. 6AAn example of a 5G network architecture according to some aspects is shown, which combines both 3GPP (e.g., cellular) access and non-3GPP (e.g., non-cellular) access to a 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN through both a radio access network (RAN, such as gNB 604, which can be a base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP interworking function (N3IWF) 603 network entity. N3IWF may include a connection to a core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 may include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Thus, the 5G CN may support unified authentication on both connections and allow simultaneous registration of UE 106 access via both the gNB 604 and the AP 612. As shown, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., a network slice selection function (NSSF) 620, a short message service function (SMSF) 622, an application function (AF) 624, a unified data management (UDM) 626, a policy control function (PCF) 628, and / or an authentication server function (AUSF) 630). Note that these functional entities may also be supported by the session management function (SMF) 606a and SMF 606b of the 5G CN. The AMF 605 may be connected to (or communicate with) the SMF 606a. In addition, the gNB 604 may communicate with (or be connected to) a user plane function (UPF) 608a, which may also communicate with the SMF 606a. Similarly, N3IWF 603 can communicate with UPF 608b, which can also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.

[0131] Figure 6BAn example of a 5G network architecture according to some aspects is shown, which combines both dual 3GPP (e.g., LTE and 5G NR) access to 5G CN and non-3GPP access. As shown, a user equipment device (e.g., such as UE 106) can access 5G CN through both a radio access network (RAN, such as gNB 604 or eNB 602, which can be a base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to AMF 605 of 5G CN. AMF 605 may include an instance of a 5G MM function associated with UE 106. In addition, RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, 5G CN may support unified authentication on both connections and allow simultaneous registration of UE 106 access via both gNB 604 and AP 612. In addition, the 5G CN may support dual registration of UEs on both the legacy network (e.g., LTE via eNB 602) and the 5G network (e.g., via gNB 604). As shown, the eNB 602 may have connections to a mobility management entity (MME) 642 and a serving gateway (SGW) 644. The MME 642 may have connections to both the SGW 644 and the AMF 605. In addition, the SGW 644 may have connections to both the SMF 606a and the UPF 608a. As shown, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). It should be noted that the UDM 626 may also include a home subscriber server (HSS) function, and the PCF may also include a policy and charging rules function (PCRF). It should also be noted that these functional entities can also be supported by SMF 606a and SMF 606b of 5G CN. AMF 606 can be connected to (or communicate with) SMF 606a. In addition, gNB 604 can communicate with (or be connected to) UPF 608a, which can also communicate with SMF 606a. Similarly, N3IWF 603 can communicate with UPF 608b, which can also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the IMS core network 610.

[0132] Note that in various aspects, one or more of the above-described network entities may be configured to perform methods for improving security checks in 5G NR networks, including, for example, mechanisms for performing non-SDT DRB processing during an SDT process as further described herein (e.g., in 5G NR systems and higher).

[0133] Figure 7 An example of a baseband processor architecture for a UE (eg, such as UE 106) in accordance with some aspects is shown. Figure 7 The baseband processor architecture 700 described in the figure may be implemented on one or more radio components (e.g., the radio components 429 and / or 430 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access layer (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include a communication connection with a traditional access layer (AS) 770. The 5G NAS 720 may include a communication connection with a 5G AS 740 and a non-3GPP AS 730 and a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with two access layers. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as a short message service (SMS) entity 752, an evolved packet system (EPS) session management (ESM) entity 754, a session management (SM) entity 756, an EPS mobility management (EMM) entity 758, and a mobility management (MM) / GPRS mobility management (GMM) entity 760. In addition, the traditional AS 770 may include functional entities such as an LTE AS 772, a UMTS AS 774, and / or a GSM / GPRS AS 776.

[0134] Thus, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, the 5G MM can maintain a separate connection management and registration management state machine for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. In addition, a device can be in a connected state in one access and in an idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0135] It should be noted that in various aspects, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform, for example, methods for performing non-SDT DRB processing during an SDT process as further described herein (e.g., in 5G NR systems and higher).

[0136] Non-SDT DRB Handling During SDT Process

[0137] In some current implementations of cellular communication networks, the transmission of data packets (e.g., small data transmission (SDT)) may require a radio resource control (RRC) connection established between a wireless device such as a UE and a base station. Therefore, when in the RRC inactive state, in the control plane, the UE may have a network access stratum (NAS) connection to the core network (CN), but may not have dedicated access stratum (AS) resources for the RRC connection. In addition, in the user plane, the UE may not perform any dedicated transmission and / or reception. Therefore, if the UE has dedicated transmission and / or reception, the UE may be required to enter the RRC connected (RRC_CONNECTED) state. As an example, for downlink (DL) data transmission, the base station may page the UE via a radio access network (RAN) paging mechanism to trigger the UE to enter the RRC connected state. Similarly, for uplink (UL) transmission, the UE may trigger a random access channel (RACH) process to enter the RRC connected state. In addition, when in the RRC inactive state, the UE may move within the RAN notification area (RNA) without notifying the RAN.

[0138] Note that when the UE transitions from the RRC connected state to the RRC inactive state, the UE may send an RRC release and suspension information message to the base station. In addition, when the UE transitions from the RRC inactive state to the RRC connected state, the UE may perform an RRC recovery procedure with the base station. Finally, when the UE transitions from the RRC inactive state to the RRC idle state, the UE may send an RRC release message. This may also occur if and / or when the UE cannot find a cell for camping.

[0139] Therefore, if Fig. 8A As shown, some current implementations (e.g., pre-3GPP Release 17 implementations) may require a UE in an RRC inactive state to perform an RRC recovery connection procedure upon detecting data arrival for transmission to the network. Fig. 8A It can be seen that such a procedure results in a delay in data transmission as well as resource consumption at the UE to perform the RRC recovery connection procedure.

[0140] To address the above issues, a specific implementation of 3GPP Release 17 may include support for small data transfer (SDT) when the UE is in the RRC inactive state, for example, without transitioning to the RRC connected state. Figure 8B As shown, a UE in an RRC inactive state can perform data output / reception for transmission to the network when data arrival is detected, without performing an RRC recovery connection procedure. Figure 8B It can be seen that, for example, Fig. 8A Such a process reduces the delay of data transmission and reduces resource consumption at the UE compared to the process described in .

[0141] Note that for both RACH and cell group (CG) based solutions, specific implementations may require that when initiating a recovery procedure for SDT initiation (e.g., for the first SDT transmission), the UE is required to re-establish at least the SDT Packet Data Convergence Protocol (PDCP) entity and recover the SDT Data Radio Bearer (DRB) configured for SDT and Signaling Radio Bearer 1 (SRB1). Figure 8B It can be seen that in the case of UL data arrival, the UE operation for SDT DRB is clear. Specifically, the UE may re-establish the PDCP entity, apply the newly derived security key, resume transmission, and trigger the SDT process. In some examples, the buffer status report (BSR) MAC CE may reflect the amount of data of the SDT DRB. However, the UE operation for non-SDT DRBs remains unclear. Therefore, if the UE always triggers the traditional RRC recovery process during the SDT process, optimizations regarding delay, signaling overhead, and / or power consumption may be available.

[0142] Aspects described herein provide systems, methods, and mechanisms for performing non-small data transfer (non-SDT) dedicated radio bearer (DRB) processing while in a radio resource control (RRC) inactive state. When operating in an RRC inactive state, a UE (such as UE 106) may determine that non-SDT data is available for transmission on a non-SDT DRB. The UE may then determine to transmit non-SDT data arrival information to a base station during an SDT process based on one or more conditions. The one or more conditions may be associated with an arrival time of the non-SDT data and / or an amount of non-SDT data to be transmitted. The arrival time may be relative to the arrival of the SDT data, the initiation of the SDT process, and / or the initiation of a subsequent transmission cycle of the SDT process.

[0143] For example, in some aspects, in the event of non-SDT data arrival, the UE (such as UE 106) may not trigger a conventional RRC recovery procedure; instead, non-SDT data arrival information may be carried via UL data transmission during the SDT procedure. In some aspects, upon receiving the non-SDT data arrival information, the network may notify the UE to resume non-SDT data transmission. It is noted that aspects described herein may provide for resuming the non-SDT data transmission before initiating the SDT procedure (e.g., Fig.9A Scenario 1 shown), after initiating the SDT process but before entering the SDT subsequent transmission cycle (for example, Fig. 9B Scenario 2 shown in FIG. 1 ) and / or during a subsequent transmission period of SDT (e.g., Fig. 9C In some aspects, upon receiving non-SDT data arrival information, the network may send an RRC message to trigger the UE to transition to an RRC connected state and / or notify the UE to transmit non-SDT data via an SDT process.

[0144] In some aspects, non-SDT data arrival information may be provided to the network via a single bit included in the UL data transmission. For example, the UL data transmission may include an additional bit for indicating the non-SDT data arrival information. As another example, the UL data transmission may include an additional bit for indicating a request to transition to an RRC connected state. In some aspects, the non-SDT data arrival information may be provided to the network via a buffer status of the non-SDT DRB included in the BSRMAC CE.

[0145] In some aspects, non-SDT data arrival information may be signaled via Layer 1 (L1) signaling, L2 signaling, and / or L3 signaling. For example, for L1 signaling, the non-SDT data arrival information may be carried in uplink control information (UCI) on a physical uplink control channel (PUCCH). As another example, for L2 signaling, the non-SDT data arrival information may be carried in a dedicated MAC CE and / or in a BSR MAC CE. As another example, for L3 signaling, the non-SDT data arrival information may be carried in a first RRCResumeRequest message (e.g., if and / or when the arrival of non-SDT data occurs before the initiation of the SDT process) and / or the non-SDT data arrival information may be carried in a RRCResumeRequest message and / or a unified air interface (UAI) such as an RRC message to report UE information (e.g., if and / or when the arrival of non-SDT data occurs during a subsequent transmission period of the SDT).

[0146] Fig.9A , Fig. 9B and Fig. 9CVarious scenarios of non-SDT procedures during an SDT procedure according to some aspects are shown. As discussed above, when possible, the UE may not trigger a traditional RRC recovery procedure upon arrival of non-SDT data for transmission, e.g., when in an RRC inactive state. In some aspects, non-SDT data arrival information may be carried via UL data transmission during an SDT procedure (e.g., as described herein). From a network perspective, upon receiving the non-SDT data arrival information, the network may determine whether the UE should resume non-SDT data transmission or initiate an RRC recovery procedure. Fig.9A As shown, in the first scenario, non-SDT DRB data may arrive before the initiation of the SDT process. Therefore, as shown, when the UE determines at 910 that there is non-SDT data to be transmitted to the network (such as network 100), the UE (such as UE 106) may be in an RRC inactive state. In some aspects, based on the arrival time of the SDT data compared to the non-SDT data, the UE may include non-SDT data arrival information as part of the data transmission 912 and / or initiate an RRC recovery process, for example, as described in reference to FIG. 11A to FIG. 11E Further described. Fig. 9B As shown, in the second scenario, non-SDT DRB data may arrive after the initiation of the SDT process. Therefore, as shown, when the UE determines at 910 that there is non-SDT data to transmit to the network, the UE may be in an RRC inactive state. In some aspects, based on the arrival time of the SDT data compared to the non-SDT data, the UE may include non-SDT data arrival information as part of subsequent data transmission and / or initiate an RRC recovery process, for example, as described in reference to FIG. 12A to FIG. 12D Further described. Fig. 9C As shown, in the third scenario, non-SDT DRB data may arrive during a subsequent SDT process 902. In some aspects, based on the arrival time of the SDT data compared to the non-SDT data, the UE may include non-SDT data arrival information as part of a subsequent data transmission and / or initiate an RRC recovery process, e.g., as described in reference to Fig.13 Further described.

[0147] As described, from the network's perspective, upon receiving non-SDT data arrival information from a UE, the network (e.g., a base station of the network, such as base station 102) may determine whether the UE resumes non-SDT data transmission or initiates an RRC recovery procedure. Fig. 10A As shown, the network may send an RRC message to the UE to trigger the UE to transition to the RRC connected state. As another example, Fig. 10BAs shown, the network may instruct the UE to transmit non-SDT data via the SDT process. In at least some aspects, the network may determine whether the UE resumes non-SDT data transmission or initiates an RRC recovery process based at least in part on the size and / or amount of the UE's non-SDT data (e.g., as indicated by the non-SDT data arrival information). From the UE's perspective, the UE will perform non-SDT data transmission when entering the CONNECTED state or when receiving a network instruction (e.g., a command) to transmit non-SDT data via the SDT process.

[0148] Specifically, Fig. 10A As shown, at 1010, a UE (such as UE 106) may be in an RRC inactive state upon arrival of non-SDT data. Note that at 1010, non-SDT DRBs may be suspended and SDT DRBs may be resumed. Based on the arrival of non-SDT data, the UE may send a MAC PDU 1012 to a base station of the network (such as base station 102). The MAC PDU 1012 may include an RRC recovery request, SDT data, and non-SDT data arrival information. At 1014, based at least in part on the size and / or amount of the UE's non-SDT data (e.g., as indicated by the non-SDT data arrival information), the base station may determine to trigger the UE to transition to an RRC connected state. Therefore, the base station may transmit an RRC recovery message 1016 indicating a transition to an RRC connected state. In response to receiving the RRC recovery message 1016, the UE may transition the non-SDT DRB to a recovery state and to an RRC connected state at 1018. The UE may send an RRC recovery complete message 1020 to the base station to indicate a successful transition to the RRC connected state.Then, at 1022, the UE may transmit all DRBs.

[0149] In addition, if Fig. 10BAs shown, at 1020, a UE (such as UE 106) may be in an RRC inactive state upon arrival of non-SDT data. Note that at 1020, non-SDT DRBs may be suspended, while SDT DRBs may be resumed. Based on the arrival of non-SDT data, the UE may send a MAC PDU 1032 to a base station of the network (such as base station 102). The MAC PDU 1032 may include an RRC resume request, SDT data, and non-SDT data arrival information. At 1034, based at least in part on the size and / or amount of the UE's non-SDT data (e.g., as indicated by the non-SDT data arrival information), the base station may determine to instruct (and / or command) the UE to transmit the non-SDT data via an SDT process. Therefore, the base station may transmit a MAC CE 1036 indicating resumption of non-SDT transmission. In response to receiving the MAC CE 1036, at 1038, the UE may transition the non-SDT DRB to a resume state. Then, at 1040, the UE may transmit non-SDT DRB data, for example, during a subsequent SDT transmission.

[0150] FIG. 11A to FIG. 11E An example of UE behavior when non-SDT data arrives before initiating an SDT process according to some aspects is shown. For example, Fig.11A An example of UE behavior when SDT and non-SDT data arrive at the UE simultaneously (and / or substantially simultaneously) is shown. In some aspects, if both SDT and non-SDT data arrive simultaneously, the UE may trigger an SDT process and indicate non-SDT data arrival information to the base station during the SDT process. As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of non-SDT DRBs and SDT DRBs 1110. Thus, the UE may initiate an SDT process 1100 with a base station (such as base station 102) and transmit non-SDT arrival information at 1112 along with the SDT data.

[0151] As another example, Fig. 11B An example of UE behavior is shown when non-SDT data arrives after SDT data but before initiation of an SDT process. In some aspects, before the UE assembles a MAC PDU for a first SDT transmission, if non-SDT data has arrived, the UE may carry non-SDT data arrival information in the MAC PDU of the first SDT transmission. As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of non-SDT DRB 1122 and SDT DRB 1120. Thus, the UE may initiate an SDT process 1100 with a base station (such as base station 102) and transmit non-SDT arrival information together with SDT data at 1124, for example, based at least in part on the arrival of non-SDT DRB 1122 prior to initiation of the SDT process 1100.

[0152] As another example, Fig. 11C and Fig.11D An example of UE behavior when non-SDT data arrives before SDT data is shown. In some aspects, when the UE is in an RRC inactive state, the UE may initiate a timer upon the arrival of non-SDT data, for example, to delay the RRC recovery procedure. Then, if SDT data arrives before the timer expires, the UE may trigger the SDT procedure, stop the timer, and report non-SDT data arrival information during the SDT procedure. Alternatively, when the timer expires, the UE may trigger the RRC recovery procedure, for example, if SDT data does not arrive before the timer expires. Note that the timer may be defined (e.g., via a 3GGP specification) and / or configured by the base station (e.g., by the network). As Fig. 11C As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of a non-SDT DRB 1130 and initiate a timer. Then, before expiration of the timer, an SDT DRB 1132 may arrive. Thus, the UE may initiate an SDT process 1100 with a base station (such as base station 102) and transmit non-SDT arrival information together with SDT data at 1134, for example, based at least in part on the arrival of the SDT DRB 1132 before expiration of the timer. Alternatively, as Fig.11D As shown, a UE (such as UE 106) may be in an RRC inactive state and initiate a timer upon arrival of a non-SDT DRB 1130. Then, upon expiration of the timer without arrival of an SDT DRB, the UE may initiate an RRC recovery procedure 1101 with a base station (such as base station 102) and transmit an RRC recovery request message 1136. Upon completion of the RRC recovery procedure 1101, the UE may then transmit the non-SDT DRB 1130.

[0153] As another example, Fig.11E Another example of non-SDT data arriving before SDT data is shown. In some aspects, the UE may trigger an SDT process and report non-SDT data arrival information to the network. As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of a non-SDT DRB 1140. Thus, the UE may initiate an SDT process 1100 with a base station (such as base station 102) and transmit non-SDT arrival information at 1142 along with the SDT data.

[0154] FIG. 12A to FIG. 12DAn example of UE behavior upon arrival of non-SDT data after initiating an SDT process according to some aspects is shown. In some aspects, the UE may delay initial access and wait for a network response. For example, if the network instructs the UE to enter an SDT subsequent transmission period, the UE may deliver non-SDT data arrival information during that period. Fig. 12A As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of an SDT DRB 1210. The UE may initiate an SDT process 1200a with a base station (such as base station 102) and transmit SDT data 1214. The UE may also receive an SDT retransmission indication 1216 from the base station during the SDT process 1200a. In addition, during this process, the UE may detect the arrival of a non-SDT DRB 1212. Then, if the network instructs the UE to enter an SDT subsequent transmission period (such as SDT process 1200b), the UE may deliver non-SDT data arrival information 1218 during the SDT process 1200b.

[0155] As another example, if the network instructs the UE to transition to the RRC connected state, the UE may trigger the RRC recovery procedure. Fig. 12B As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of an SDT DRB 1220. The UE may initiate an SDT process 1200a with a base station (such as base station 102) and transmit SDT data 1224. The UE may also receive an SDT retransmission indication 1226 from the base station during the SDT process 1200a. In addition, during this process, the UE may detect the arrival of a non-SDT DRB 1222. Then, if the network instructs the UE to transition to an RRC connected state, the UE may trigger an RRC recovery process 1201 and transmit an RRC recovery request 1228. Once the UE has transitioned to the RRC connected state, the UE may transmit a non-SDT DRM 1222.

[0156] In some aspects, if a RACH procedure (e.g., RRC recovery procedure) for SDT access has not been successfully completed, the UE may terminate the previous RACH procedure and trigger a new SDT RACH procedure and carry non-SDT data arrival information in an SDT transmission. Fig. 12CAs shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of an SDT DRB 1230. The UE may initiate an SDT process 1200a with a base station (such as base station 102) and transmit SDT data 1234. In addition, during this process, the UE may detect the arrival of a non-SDT DRB 1222. Then, if a RACH process (e.g., an RRC recovery process) for SDT access has not been successfully completed, the UE may terminate the previous RACH process and trigger a new SDT RACH process (e.g., SDT process 1200b) and carry non-SDT data arrival information 1236 in the SDT transmission.

[0157] In some aspects, the UE may directly trigger the conventional recovery process and discard the previous SDT process. Fig.12D As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of an SDT DRB 1240. The UE may initiate an SDT process 1200a with a base station (such as base station 102) and transmit SDT data 1244. In addition, during this process, the UE may detect the arrival of a non-SDT DRB 1242. The UE may then trigger a conventional recovery process (such as RRC recovery process 1201) and discard the SDT process 1200a. During the RRC recovery process 1201, the UE may transmit an RRC recovery request 1246. Once the UE has transitioned to an RRC connected state, the UE may transmit a non-SDT DRM 1242.

[0158] Fig.13 An example of UE behavior upon arrival of non-SDT data during a subsequent SDT process is shown. In some aspects, the UE may report non-SDT data arrival information to the network via a dedicated scheduling and transmission process. Note that if no dedicated UL grant is available and the Scheduling Request (SR) functionality is supported, the UE may trigger an SR to request an UL grant for the transmission. The UE may transmit a legacy RRCResumeRequest message via a dedicated UL grant, and upon receipt of the message, the network may determine that the UE has non-SDT data for transmission. Fig.13As shown, a UE (such as UE 106) may be in an RRC inactive state upon arrival of an SDT DRB 1310. The UE may initiate an SDT process 1300a with a base station (such as base station 102) and transmit SDT data 1314. The UE may also receive an SDT retransmission indication 1316 from the base station during the SDT process 1200a. The UE may then initiate a subsequent SDT process 1300b and detect the arrival of a non-SDT DRB 1318 during the subsequent SDT process 1300b. The UE may then transmit a scheduling request 1320 to the base station, followed by a UE-specific scheduling message 1322. The UE may then transmit the SDT data and non-SDT arrival information to the base station 102 during the subsequent SDT process 1300b.

[0159] Fig.14 A block diagram illustrating an example of a method for non-small data transfer (SDT) dedicated radio bearer (DRB) processing when in a radio resource control (RRC) inactive state according to some aspects. Among other devices, Fig.14 The method shown in the figure can also be used with any of the systems, methods or devices shown in the figure. In various aspects, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0160] At 1402, a UE, such as UE 106, may determine that non-SDT data is available for transmission, such as on a non-SDT DRB, for example, while operating in an RRC inactive state.

[0161] At 1404, the UE may determine to transmit non-SDT data arrival information during the SDT process based on at least one condition and / or based on one or more conditions.

[0162] For example, when non-SDT data arrives before initiating the SDT process, at least one condition (and / or one or more conditions) may include any one, any combination, and / or all of the following: when SDT data and non-SDT data arrive approximately simultaneously (e.g., at the same time and / or within a negligible time period between arrival), the UE determines that SDT data is available for transmission on the SDT DRB; when SDT data arrives before non-SDT data and when non-SDT data arrives before assembly of the SDT MAC PDU, the UE determines that SDT data is available for transmission on the SDT DRB; when SDT data arrives within a time period after the arrival of non-SDT data (e.g., the user may monitor the time period via the initiation of a timer upon the arrival of non-SDT data), the UE determines that SDT data is available for transmission on the SDT DRB; and / or upon the arrival of non-SDT data, the UE receives a configuration from the base station to trigger the SDT process. Note that the time period may be defined by a specification (e.g., a 3GPP standard), configured by the base station, and / or carrier-specific. In some aspects, the UE may initiate an RRC recovery procedure based on not determining the arrival of SDT data during the time period, and transmit non-SDT DRBs upon entering the RRC connected state.

[0163] As another example, when non-SDT data arrives during the initial transmission period of the SDT process, at least one condition (and / or one or more conditions) may include any one, any combination, and / or all of the following: the UE receives an instruction from the base station to enter a subsequent transmission period of the SDT process (e.g., the UE may delay the RRC recovery process upon the arrival of non-SDT data), or the UE terminates the RACH process associated with the initiation of the SDT process and triggers a new RACH process to initiate a new SDT process. Note that the non-SDT data arrival information may be transmitted via a new SDT process, and the UE may determine that the RACH process for the SDT process is not completed upon the arrival of non-SDT data. In some aspects, the UE may receive an instruction from the base station to return to the RRC inactive state and not enter a subsequent transmission period of the SDT process. In response, the UE may initiate an RRC recovery process and transmit a non-SDT DRB when entering an RRC connected state. In some aspects, the UE may terminate the SDT process, initiate an RRC recovery process, and transmit a non-SDT DRB when entering an RRC connected state.

[0164] As another example, when non-SDT data arrives during a subsequent transmission period of the SDT process, at least one condition (and / or one or more conditions) may include any one, any combination, and / or all of the following: the UE reports the non-SDT data arrival information to the base station via dedicated scheduling and transmission during the subsequent transmission period, or the UE transmits an RRC recovery request message via a dedicated uplink grant of the SDT process. In some aspects, when a dedicated uplink grant is not available, the UE may report the non-SDT data arrival information by triggering a scheduling request (SR) to request an uplink grant for transmission during the subsequent transmission period.

[0165] In some aspects, the non-SDT data arrival information may include a bit indicating that non-SDT data is available and / or a bit indicating a request for the UE to transition to an RRC connected state. In some aspects, the non-SDT data arrival information may include a buffer status of a non-SDT DRB. The buffer status of the non-SDT DRB may be included in a buffer status report (BSR) medium access control (MAC) control element (CE). In some aspects, the non-SDT data arrival information may be signaled via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, for L1 signaling, the non-SDT data arrival information may be carried in uplink control information (UCI) on a physical uplink control channel (PUCCH). As another example, for L2 signaling, the non-SDT data arrival information may be carried in a dedicated medium access control (MAC) control element (CE) or in a buffer status report (BSR) MAC CE. As another example, for L3 signaling, when the arrival of non-SDT data occurs before the initiation of the SDT process, the non-SDT data arrival information may be carried in the first RRC recovery request message of the SDT process, or when the arrival of non-SDT data occurs during a subsequent transmission cycle of the SDT, the non-SDT data arrival information may be carried in one of the RRC recovery request message or the unified air interface (UAI) message to report UE information.

[0166] In some aspects, the non-SDT data arrival information may indicate the amount of non-SDT data to be transmitted. In such aspects, whether the UE initiates the RRC recovery process may depend on the amount of non-SDT data to be transmitted. For example, the UE may receive an RRC message from a base station indicating a transition to an RRC connected state. The indication may be based at least in part on the amount of non-SDT data indicated by the non-SDT data arrival information exceeding a threshold. The UE may then initiate an RRC recovery process and transmit a non-SDT DRB after completing the RRC recovery process. As another example, the UE may receive a network command from a base station to transmit non-SDT data via an SDT process. The command may be based at least in part on the amount of non-SDT data indicated by the non-SDT data arrival information not exceeding a threshold. The UE may then recover the non-SDT DRB, and transmit the non-SDT DRB after recovering the non-SDT DRB while remaining in an RRC inactive state. In some aspects, the command may be received via a MAC CE. It should be noted that the threshold may be predefined (e.g., via a 3GPP standard), configured by a base station (e.g., by a network) and / or carrier-specific.

[0167] Fig.15 A block diagram illustrating an example of a method for non-small data transfer (SDT) dedicated radio bearer (DRB) processing according to some aspects. Among other devices, Fig.15 The method shown in the figure can also be used with any of the systems, methods or devices shown in the figure. In various aspects, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0168] At 1502, a base station (such as base station 102) may receive non-SDT data arrival information from a UE (such as UE 106) during an SDT process. It should be noted that the UE may operate in an RRC inactive state. In some aspects, the non-SDT data arrival information may include a bit indicating that non-SDT data is available and / or a bit indicating a request for the UE to transition to an RRC connected state. In some aspects, the non-SDT data arrival information may include a buffer status of a non-SDT DRB. The buffer status of the non-SDT DRB may be included in a buffer status report (BSR) medium access control (MAC) control element (CE). In some aspects, the non-SDT data arrival information may be received via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, for L1 signaling, the non-SDT data arrival information may be carried in uplink control information (UCI) on a physical uplink control channel (PUCCH). As another example, for L2 signaling, the non-SDT data arrival information may be carried in a dedicated medium access control (MAC) control element (CE) or in a buffer status report (BSR) MAC CE. As another example, for L3 signaling, when the arrival of non-SDT data occurs before the initiation of the SDT process, the non-SDT data arrival information may be carried in the first RRC resume request message of the SDT process, or when the arrival of non-SDT data occurs during the SDT subsequent transmission period, the non-SDT data arrival information may be carried in one of the RRC resume request message or the unified air interface (UAI) message to report UE information.

[0169] At 1504, the base station may determine, at least in part, that the UE is triggered to transmit non-SDT data via an SDT process based on the amount of non-SDT data being less than a threshold, for example, while the UE remains in an RRC inactive state. In other words, the non-SDT data arrival information may indicate the amount of non-SDT data to be transmitted. Therefore, whether the UE initiates an RRC recovery process may depend on the amount of non-SDT data to be transmitted. For example, the base station may send an RRC message to the UE indicating a transition to an RRC connected state. The indication may be based at least in part on the amount (and / or quantity) of non-SDT data indicated by the non-SDT data arrival information exceeding a threshold. The UE may then initiate an RRC recovery process and transmit non-SDT DRBs after completing the RRC recovery process. Note that the threshold may be predefined (e.g., via a 3GPP standard), configured by the base station (e.g., by the network) and / or carrier-specific.

[0170] At 1506, the base station may transmit an instruction to the UE to restore the non-SDT DRBs for the SDT process. In some aspects, the instruction (and / or command) may be transmitted via a MAC CE.

[0171] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0172] Aspects of the present disclosure can be implemented in any of a variety of forms. For example, some aspects can be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other aspects can be implemented using one or more custom-designed hardware devices such as ASICs. Other aspects can be implemented using one or more programmable hardware elements such as FPGAs.

[0173] In some aspects, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any of the method aspects described herein, or any combination of the method aspects described herein, or any subset of any method aspects described herein, or any combination of such subsets.

[0174] In some aspects, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method aspects described herein (or any combination of the method aspects described herein, or any subset of any of the method aspects described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0175] By interpreting each message / signal X received by a user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any of the methods for operating a UE described herein may become the basis for the corresponding method for operating a base station.

[0176] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method for non-SDT DRB processing, wherein non-SDT refers to non-small data transmission, and DRB refers to a dedicated radio bearer, the method comprising: While operating in a radio resource control (RRC) inactive state, determining that non-SDT data is available for transmission on a non-SDTDRB; and Non-SDT data arrival information is sent to the transceiver for reporting to the base station via a dedicated uplink grant.

2. The method according to claim 1, in, The non-SDT data arrival information is sent to the transceiver for reporting during a subsequent transmission period via the dedicated uplink grant.

3. The method according to claim 2, in, The reporting is done via the RRC recovery request message.

4. The method according to claim 1, in, When the dedicated uplink grant is not available, sending the non-SDT data arrival information comprises: triggering the transceiver to transmit a scheduling request SR.

5. The method according to claim 4, in, The SR requests an uplink grant for transmission during the subsequent transmission period.

6. The method according to claim 1, in, The non-SDT data arrives during a subsequent transmission cycle of the SDT process.

7. The method according to claim 1, in, The non-SDT data arrival information is signaled via layer 3 L3 signaling.

8. The method according to claim 1, in, The non-SDT data arrival information is carried in a unified air interface UAI message to report UE information.

9. The method according to claim 8, in, The arrival of the non-SDT data occurs during the SDT subsequent transmission period.

10. The method according to claim 1, in, When the arrival of the non-SDT data occurs before the initiation of the SDT process, the non-SDT arrival information is carried in the first RRC resume request message of the SDT process.

11. The method according to claim 1, in, The non-SDT data arrival information includes one bit indicating that the non-SDT data is available.

12. The method according to claim 1, in, The non-SDT data arrival information includes a bit indicating a request for the UE to transition to an RRC connected state.

13. The method according to claim 1, in, The non-SDT data arrival information includes a buffer status of the non-SDT DRB.

14. The method according to claim 13, in, The buffer status of the non-SDT DRB is included in a buffer status report BSR medium access control element MAC CE.

15. The method according to claim 1, in, The non-SDT data arrival information indicates an amount of non-SDT data to be transmitted.

16. The method according to claim 15, further comprising: receiving, from the base station, an RRC message indicating a transition to an RRC connected state, wherein the indication is based at least in part on the amount of non-SDT data indicated by the non-SDT data arrival information exceeding a threshold; Initiate the RRC recovery process; as well as After completing the RRC recovery procedure and entering the RRC connected state, a non-SDT DRB is sent to the transceiver for transmission to the base station.

17. The method according to claim 15, further comprising: receiving, from the base station, a network command to transmit the non-SDT data via the SDT process, wherein the command is based at least in part on the amount of non-SDT data indicated by the non-SDT data arrival information not exceeding a threshold; Restoring the non-SDT DRB; as well as After recovering the non-SDT DRB, the non-SDT DRB is sent to the transceiver for transmission to the base station while remaining in an RRC inactive state.

18. The method according to claim 17, in, The command is received via a Medium Access Control Element MAC CE.

19. An apparatus comprising: Memory; and A baseband processor in communication with the memory and configured to perform the method according to any one of claims 1 to 18.

20. A computer program product comprising computer instructions which, when executed by a baseband processor, perform the method according to any one of claims 1 to 18.

Images