Communication coordination and reduced processing techniques for enhanced quality of service procedures
By dynamically adjusting data packet transmission and QoS rules at the base station, the challenges of signal accuracy and power requirements in wireless communication equipment are solved, achieving efficient communication optimization under multiple communication standards.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- APPLE INC
- Filing Date
- 2021-09-02
- Publication Date
- 2026-07-03
AI Technical Summary
In wireless communication devices, as functionality increases, there is a need to improve signal accuracy and reduce power and processing requirements while maintaining good communication capabilities. This is especially true in the context of supporting multiple communication standards and technologies such as 5G NR, where existing technologies struggle to effectively coordinate and optimize.
The base station dynamically adjusts the transmission process of data packets by receiving reflected Quality of Service (QoS) Indicator (RQI) tags and timer information, including or avoiding the inclusion of RQI tags, optimizing communication with User Equipment (UE), and coordinating the maintenance and updating of QoS rules using Protocol Data Unit (PDU) session timers and signaling mechanisms.
It improves the service quality of wireless communication systems, reduces the power and processing requirements of UE devices, enhances the accuracy and efficiency of signal transmission, and adapts to the needs of various communication standards and technologies.
Smart Images

Figure CN116076104B_ABST
Abstract
Description
Technical Field
[0001] This application relates to wireless devices, and more specifically to apparatus, systems, and methods for communication coordination and processing reduction techniques to enhance quality of service procedures. Background Technology
[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (LTE-Advanced), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and BLUETOOTH. TM wait.
[0003] The increasing number of features and functions introduced into wireless communication devices has created a continuous demand for improvements in both wireless communication and the devices themselves. Ensuring the accuracy of signals transmitted and received by user equipment (UEs) (e.g., via wireless devices such as cellular phones, base stations, and relay stations used in wireless cellular communications) is of paramount importance. Furthermore, adding functionality to UE devices can place significant strain on their battery life and processing or computing power. Therefore, it is equally crucial to reduce the power and processing or computing requirements in UE device design while allowing the UE to maintain good transmission and reception capabilities to improve communication.
[0004] To increase coverage and better serve the growing demand and scope for the intended uses of wireless communication, in addition to the aforementioned communication standards, new wireless communication technologies are under development, including fifth-generation (5G) New Radio (NR) communication. Therefore, there is a need to improve the areas supporting this development and design. Summary of the Invention
[0005] The implementation plan relates to apparatus, systems, and methods for coordinating communications and providing wireless communication systems with reduced processing techniques for enhancing quality of service procedures.
[0006] In some implementations, a base station (BS) may receive one or more data packets from a network node that include one or more Reflective Quality of Service (QoS) Indicator (RQI) tags. The base station may determine one or more active uplink (UL) QoS rules associated with a user equipment (UE) based on the values of the one or more RQI tags. Additionally or alternatively, the base station may further determine whether to include one or more RQI tags or avoid including one or more RQI tags in the transmission of one or more data packets to the UE based on at least one of one or more timers, one or more active UL QoS rules, and status information received from the UE. In response to determining that one or more RQI tags should be included, the base station may transmit one or more data packets to the UE, wherein the one or more packets include one or more RQI tags.
[0007] Alternatively or additionally, the base station may determine, based on at least one of one or more timers, one or more active UL QoS rules, and status information received from the UE, to avoid including one or more RQI tags in the transmission of one or more data packets to the UE. Therefore, in response to determining to avoid including one or more RQI tags in the transmission, the base station may transmit one or more packets to the UE, wherein the one or more packets do not include one or more RQI tags.
[0008] According to some implementations, the base station can be further configured to initiate and maintain a timer corresponding to a Protocol Data Unit (PDU) session at the UE. Furthermore, the base station can determine, based on the timer, that the UE may discard the current QoS rule based on an additional timer initiated and maintained by the UE. Therefore, according to some implementations, in response to determining that the UE will discard the current QoS rule, the base station can transmit a message instructing the UE to continue using the current QoS rule. In some implementations, this message is transmitted via Downlink Serving Data Adaptation Protocol (SDAP) control PDU signaling, and the timer may be provided by the 5G core network (5GCN) per PDU session as part of the Reflected QoS Attribute (RQA).
[0009] In some implementations, the base station may receive periodic reporting signaling from the UE indicating the status of a Reflection Quality of Service (RQ) timer. Furthermore, according to some implementations, the base station may be able to configure the periodicity of the reporting signaling, and the reporting signaling may include at least one of a QoS rule identifier, a 1-bit indication of whether the RQ timer is running or has expired, and an indication of the remaining time of the RQ timer's expiration.
[0010] Alternatively or concurrently, according to some implementations, the base station may be configured to initiate and maintain a timer corresponding to the QoS rules of the PDU session at the UE, and transmit signaling including an indication to the UE to delete the QoS rules when the timer expires. In some implementations, this message may be transmitted via downlink SDAP control PDU signaling or radio resource control (RRC) reconfiguration signaling.
[0011] According to another implementation, the base station may transmit to the UE signaling including a Quality of Service Flow Identifier (QFI) value of 0 to indicate that the payload of one or more data packets is a Service Data Adaptation Protocol (SDAP) Control Protocol Data Unit (PDU). Additionally or alternatively, the base station may configure the UE to transmit to the base station acknowledgment or response to at least one of the establishment of a new QoS rule and the expiration of an RQ timer.
[0012] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of cellular phones, tablets, wearable computing devices, portable media players and various other computing devices.
[0013] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description
[0014] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:
[0015] Figure 1 An exemplary wireless communication system according to some implementation schemes is shown;
[0016] Figure 2 This illustrates a base station (BS) communicating with a user equipment (UE) device according to some implementation schemes;
[0017] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown;
[0018] Figure 4 An exemplary block diagram of a BS according to some implementation schemes is shown;
[0019] Figure 5 An exemplary block diagram of a cellular communication circuit according to some embodiments is shown;
[0020] Figure 6 This is a flowchart illustrating an exemplary aspect of a method for a base station to maintain the QoS state of a UE, according to some implementation schemes;
[0021] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation
[0022] acronym
[0023] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:
[0024] 3GPP: Third Generation Partnership Project
[0025] TS: Technical Specification
[0026] RAN: Radio Access Network
[0027] • NG-RAN: RAN (E-UTRAN or NR) connected to the 5G core network
[0028] • RAT: Radio Access Technology
[0029] UE: User Equipment
[0030] RF: Radio Frequency
[0031] ·BS: Base Station
[0032] DL: Downlink
[0033] ·UL: Uplink
[0034] LTE: Long Term Evolution
[0035] NR: New Radio
[0036] ·5GS: 5G system
[0037] ·5GMM: 5GS Mobility Management
[0038] ·5GC: 5G Core Network
[0039] •RRC: Radio Resource Control
[0040] ·MAC-CE: Media Access Control—Control Element
[0041] • DCI: Downlink Control Information
[0042] ·PDCP: Protocol Data Convergence Protocol
[0043] • SDU: Service Data Unit
[0044] • PDU: Protocol Data Unit
[0045] SDAP: Service Data Adaptation Protocol
[0046] •SDF: Service Data Flow
[0047] • UPF: User Plane Function
[0048] QoS: Quality of Service
[0049] • QFI: Quality of Service Flow Identifier
[0050] • RQI: Reflection Quality of Service Indicator
[0051] • RDI: Reflection QoS Flow to DRB Mapping Indicator
[0052] • RQA: Reflection QoS attribute
[0053] TX: Transmission
[0054] ·RX: Receive
[0055] •DRB: Data Radio Bearer
[0056] •AS: Access Layer
[0057] NAS: Non-Access Layer
[0058] the term
[0059] The following is a glossary of terms used in this disclosure:
[0060] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic 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, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside 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 media" may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.
[0061] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).
[0062] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."
[0063] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. 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.
[0064] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on AndroidTM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM ), laptops, wearable devices (e.g., smartwatches, smart glasses), head-mounted displays, VR displays, XR devices, PDAs, portable internet devices, music players, data storage devices, or other handheld devices, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or combination of devices) that is portable to the user and capable of wireless communication.
[0065] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.
[0066] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.
[0067] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.
[0068] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.
[0069] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, 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.
[0070] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.
[0071] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.
[0072] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.
[0073] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).
[0074] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.
[0075] 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". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.
[0076] Figure 1 and Figure 2 —Communication System
[0077] Figure 1 A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1 The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.
[0078] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.
[0079] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”) and may include hardware for implementing wireless communication with UE 106A to UE 106N.
[0080] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".
[0081] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.
[0082] 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 services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.
[0083] Therefore, although base station 102A can act as such Figure 1The diagram shows the "serving cell" of UEs 106A-N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from 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 facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in Figure 1 Base stations 102A to 102B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.
[0084] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to a New Radio communication core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating under 5G NR may connect to one or more TRPs within one or more gNBs. For example, base station 102A and one or more other base stations 102 may support joint transmission, enabling UE 106 to receive transmissions from multiple base stations (and / or multiple TRPs provided by the same base station).
[0085] It should be noted that UE 106 can communicate 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 interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), 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, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., Advanced Television Systems Committee—Mobile / Handheld (ATSC-M / H)) and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.
[0086] Figure 2The illustration shows a user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 according to some embodiments. UE 106 can be a cellular communication-capable device, such as a mobile phone, handheld device, computer, laptop, tablet, smartwatch, or other wearable device, or virtually any type of wireless device.
[0087] UE 106 may include a processor (e.g., a processing element) configured to execute program instructions stored in memory. UE 106 may perform any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include any of the programmable hardware elements, such as any of the FPGA (Field Programmable Gate Array), integrated circuits, and / or various other possible hardware components configured to perform (e.g., individually or in combination) any of or any portion of any of the method embodiments described herein.
[0088] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, NR or LTE using at least some shared radio components. As an additional possibility, UE 106 may be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio components may include any combination of baseband processors, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio components 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 the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.
[0089] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include shared radio components for communicating using either LTE or 5G NR (or, in various possibilities, either LTE or 1xRTT, or either LTE or GSM), and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
[0090] Figure 3 —UE block diagram
[0091] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 3 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, among other devices, 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. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.
[0092] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card for Ethernet, for example.
[0093] The wireless communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as one or more antennas 335 as shown in the figure. The wireless communication circuit 330 may include cellular communication circuitry and / or medium-to-short-range wireless communication circuitry, and 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.
[0094] In some embodiments, as further described below, the cellular communication circuit 330 may include one or more receive chains of multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT (e.g., LTE) and can communicate with a dedicated receive chain and a transmit chain shared with a second radio component. A second radio component may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.
[0095] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.
[0096] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general purpose integrated circuit cards) 345.
[0097] As shown in the figure, the SOC 300 may include a processor 302 and display circuitry 304. The processor executes program instructions for the communication device 106, and the display circuitry performs graphics processing and provides display signals to the display 360. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as display circuitry 304, wireless communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.
[0098] As described above, communication device 106 may be configured to communicate using wireless and / or wired communication circuitry. As described herein, communication device 106 may include hardware and software components for implementing any of the various features and techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 302 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 conjunction with one or more of other components 300, 304, 306, 310, 320, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.
[0099] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.
[0100] Furthermore, as described herein, the wireless communication circuit 330 may include one or more processing elements. In other words, one or more processing elements may be included in the wireless communication circuit 330. Therefore, the wireless communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the wireless communication circuit 330. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the wireless communication circuit 330.
[0101] Figure 4 —Block diagram of a base station
[0102] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).
[0103] Base station 102 may include at least one network port 470. This network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106.
[0104] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).
[0105] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a “gNB”. In such implementations, 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 receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.
[0106] Base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 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.
[0107] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and LTE, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).
[0108] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. Processor 404 of base station 102 may be configured to implement or support some 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, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, and 470, processor 404 of base station 102 may be configured to implement or support some or all of the features described herein.
[0109] Furthermore, as described in this invention, one or more processors 404 may include one or more processing elements. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.
[0110] Furthermore, as described in this invention, the radio component 430 may include one or more processing elements. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.
[0111] Figure 5 —Block diagram of cellular communication circuit
[0112] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of possible cellular communication circuits; other circuits, such as those including or coupled to sufficient antennas for different RATs to perform uplink activities using independent antennas, or those including or coupled to fewer antennas, such as those that can be shared among multiple RATs, are also possible. According to some embodiments, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, 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.
[0113] Cellular communication circuitry 330 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-b and 336 as shown in the figure. In some embodiments, cellular communication circuitry 330 may include dedicated receive chains for multiple RATs (including and / or coupled (e.g., communicatively; directly or indirectly) to dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as Figure 5 As shown, the cellular communication circuit 330 may include a first modem 510 and a second modem 520. The first modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).
[0114] As shown, the first modem 510 may include one or more processors 512 and a memory 516 communicating with the processors 512. The modem 510 may communicate with a radio frequency (RF) front-end 530. The RF front-end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 530 may include a receiver circuit (RX) 532 and a transmitter circuit (TX) 534. In some embodiments, the receiver circuitry 532 may communicate with a downlink (DL) front-end 550, which may include circuitry for receiving radio signals via an antenna 335a.
[0115] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 communicating with the processors 522. The modem 520 may communicate with an RF front-end 540. The RF front-end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, the receiving circuitry 542 may communicate with a DL front-end 560, which may include circuitry for receiving radio signals via an antenna 335b.
[0116] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by a first modem 510), switch 570 may be switched to a first state allowing the first modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by a second modem 520), switch 570 may be switched to a second state allowing the second modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).
[0117] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, processors 512, 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processors 512, 522 may be configured as programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays) or as ASICs (Application-Specific Integrated Circuits). Alternatively (or in addition), processors 512, 522 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336.
[0118] Furthermore, as described herein, processors 512 and 522 may include one or more processing elements. Therefore, processors 512 and 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512 and 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processors 512 and 522.
[0119] In some implementations, the cellular communication circuit 330 may include only one transmit / receive chain. For example, the cellular communication circuit 330 may not include modem 520, RF front-end 540, DL front-end 560, and / or antenna 335b. As another example, the cellular communication circuit 330 may not include modem 510, RF front-end 530, DL front-end 550, and / or antenna 335a. In some implementations, the cellular communication circuit 330 may also not include switch 570, and RF front-end 530 or RF front-end 540 may communicate with UL front-end 572, for example, through direct communication.
[0120] Communication coordination and processing reduction techniques used to enhance service quality procedures
[0121] According to some embodiments described herein, some mobile device services may exhibit deterministic behavior due to defined Quality of Service (QoS) parameters. For example, some services may need to transmit and / or receive multiple data stream types corresponding to different QoS requirements. In other words, certain data streams or Service Data Streams (SDFs) may be associated with certain QoS parameters that effectively adapt the transmission and reception of the data streams based on the associated QoS parameters. For example, a data stream or SDF including video frames may correspond to a specific set of QoS parameters and QoS rules (e.g., one or more packet filters), while another data stream or SDF including audio information may correspond to a different set of QoS parameters and QoS rules (e.g., one or more packet filters). In some embodiments, the UE may be able to autonomously derive QoS rules. Additionally, the data payload may typically be transmitted and received periodically.
[0122] Furthermore, data services (e.g., transmit / receive between the UE and the network) may involve multiple QoS flows mapped to the same or different Data Radio Bearers (DRBs). For example, multiple QoS flows may exist associated with a single DRB (but other relationships are also envisioned). Additionally, each QoS flow may have its own QoS forwarding processing. Therefore, if each QoS flow in the air interface requires different QoS forwarding processing, the network can map the QoS flows to different DRBs. However, this may not always be possible given the large volume of traffic in some data transmissions. In other words, the network can be incentivized to map different QoS flows to different DRBs.
[0123] To facilitate the mapping of specific data to network resources, some networks may allocate certain QoS flows for information transmitted in data bursts to establish higher priority and / or protection for transmitted data, minimizing data loss and latency. For example, a QoS Flow ID (QFI) can be used to identify QoS flows in the network. In some implementations, QoS flows may require Guaranteed Stream Bit Rate (GBR) or may not require GBR (non-GBR). Additionally or alternatively, some QoS flows may be used for mission-critical GBRs (e.g., delay-critical QoS flows). These GBRs associated with QoS flows can allow for more efficient data transmission with higher priority, which can further lead to an enhanced user experience.
[0124] In previous wireless communication standards, QoS parameter mapping was characterized through a one-to-one relationship between the Evolved Packet Core (EPC) and the Data Radio Bearer (DRB). More specifically, the DRB, Evolved Packet System (EPS) bearer, S1 General Packet Radio System Tunneling Protocol User Plane (GTP-U), and S5-U interface tunnel were characterized through a one-to-one QoS mapping. In other words, the UE was explicitly instructed or configured to utilize certain Long-Term Service Data Streams (SDFs) and corresponding QoS rules based on the one-to-one mapping with the DRB.
[0125] However, in 5GC, the Single User Plane Function (UPF) can be used for data delivery between the NG-RAN and other devices or nodes (e.g., UEs). Therefore, a DRB on the air interface can have a one-to-many correspondence with a GTP-U tunnel on the UPF N3 interface. In other words, multiple QoS flows can be mapped to a single GTP-U tunnel. Thus, the NG-RAN can map individual QoS flows to one or more DRBs. Alternatively or additionally, a PDU session can include multiple DRBs and QoS flows corresponding to a single N3 GTP-U tunnel. Therefore, one DRB can deliver one or more (e.g., multiple) QoS flows. In some cases, the UE can adaptively derive QoS rules on a per-packet basis without receiving one or more explicit indications of QoS rules from the Session Management Function (SMF, e.g., the network).
[0126] Furthermore, 5GC can enable QoS at the QoS flow level, allowing each QoS flow packet to be classified and labeled using a QoS Flow Identifier (QFI). The QFI-identifiable flow can be carried in the extended header on the N3 interface in the GTP-U protocol. Therefore, in 5GC, multiple QoS flows can be mapped to the DRB in the Access Network (AN). Apparatus, systems, and methods for communication coordination and processing reduction techniques to enhance QoS procedures can improve UE operational efficiency by further reducing unnecessary transmission / reception or processing of QoS-related rules by shifting the maintenance of QoS states and rules to the network side. Therefore, the UE can experience reduced processing requirements due to these mappings.
[0127] Enhancements to reflection QoS and SDAP
[0128] In some implementations, the UE may support reflective QoS at the NAS layer. Reflective QoS can be characterized as such that, for each DRB, the UE can monitor the QoS flow ID of downlink packets and apply the same mapping to subsequent uplink transmissions. In other words, the UE can map its QoS flow to which it belongs and further correspond to the QoS flow ID observed in the downlink packets of the associated DRB and the uplink packets of the PDU session. Additionally or alternatively, the UE may indicate support for reflective QoS functionality for each PDU session via (NAS)PDU session establishment / modification messages.
[0129] In some implementations, the fifth-generation core network (5GC) can decide to use reflected QoS for specific QoS flows. For example, the 5GC can inform the random access network (RAN) by providing a reflected QoS attribute (RQA). Alternatively, the 5GC can apply a reflected QoS indication (RQI) tag to each packet sent from the User Plane Function (UPF) to the RAN. Furthermore, according to some implementations, the 5GC (via the RAN) can provide a reflected QoS timer (RQ timer) to the UE per PDU session. Additionally, when the UE receives an RQI on a DL packet, if the QoS rule does not already exist, the UE can create a new UE-derived QoS rule by "reflecting" the Internet Protocol (IP) 5-tuple. Alternatively, the RQ timer can then be started or restarted. According to some implementations, the UE can delete the corresponding QoS rule when the RQ timer expires. Because the packets contain RQI tags, intermediate nodes (e.g., I-UPF, gNB) do not need to maintain the state of the RQI tags; therefore, this reflected QoS mechanism can be considered stateless.
[0130] In some implementations, the UE may support reflection mapping at the AS layer. In other words, the AS layer may support its own reflection mechanism. For example, at the AS layer, the UE may utilize a reflection QoS mechanism to map QoS flows to DRBs. More specifically, DL packets may carry the reflected QoS flow to a DRB Mapping Indication (RDI) in the SDAP header. For example, when the UE receives an RDI on a DL packet, it may map the corresponding QoS flow to the corresponding UL DRB in the UL direction. In some implementations, timers (e.g., RQ timers) involved in this process may not be present.
[0131] The stateless nature of the reflection mechanism can be characterized by the fact that virtually every packet sent from the UPF to the UE is marked with a QFI. Furthermore, the SDAP layer can further notify the NAS layer whenever a packet with the RQI bit set is received. Therefore, this could cause the NAS layer to have to process QoS rules even if they already exist, potentially leading to a significant processing load. Additionally or alternatively, the UE may also have to track or maintain an RQ timer to refresh or discard QoS rules when the timer expires.
[0132] Therefore, due to the enhanced power and processing capabilities of next-generation random access networks (NG-RAN, e.g., gNB or base station), NG-RAN, rather than UE tracking and reflection QoS requirements, can be beneficial.
[0133] According to some implementations, a reflection QoS mapping can be torn down (e.g., disabled) through explicit RRC reconfiguration or a new reflection mapping. Therefore, the reflection QoS mechanism at the AS layer can be considered to be designed to be stateful. For example, when the RDI bit is set to 1, the UE can update the QoS flow to the DRB mapping. Alternatively, when the RDI bit is set to 0, the UE may not need to perform any processing. Therefore, the UE can experience some secondary effects, such as battery saving, by not having to utilize various computing resources and / or power to perform the aforementioned processing.
[0134] In some implementations, ensuring packets are delivered in the correct order is important for transport quality purposes when QoS flows are remapped to different bearers. In some implementations, this can be ensured using an end-of-line marker (SDAP) control PDU. For example, the UE can send an end-of-line marker when remapping a QoS flow (via RRC messages or by reflection). Therefore, if a default DRB exists, the end-of-line marker can be sent even if packets belonging to the QoS flow have not yet been sent. In some implementations, the network can buffer packets arriving on the new DRB until an end-of-line marker is received on the old DRB.
[0135] Figure 6 - The base station maintains the QoS status of the UE.
[0136] Figure 6 The flowchart illustrates exemplary aspects of methods for communication coordination and processing reduction techniques used to enhance service quality procedures, according to some implementation schemes. More specifically, Figure 6 This illustrates a method in which the NG-RAN can track each RQI tag of a packet received from the UPF via the NG-U (i.e., N3) interface and determine whether to forward the RQI tag to the UE based on one or more timers, one or more active ULQoS rules, and / or status information received from the UE.
[0137] Figure 6 Aspects of the method may be implemented by a wireless device such as UE 106, which communicates with one or more base stations (e.g., BS 102) as shown in the accompanying drawings and as described with respect to the drawings, or more generally, in conjunction with any of the computer systems or devices shown in the drawings, as well as other circuits, systems, devices, elements or components shown in the drawings, and other devices, as needed. For example, one or more processors (or processing elements) of the UE (e.g., processor 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) may cause the UE to perform some or all of the illustrated method elements. It should be noted that although at least some elements of the method have been described in a manner involving the use of communication technologies and / or features associated with 3GPP specification documents, this description is not intended to limit the present disclosure, and aspects of the method may be used in any suitable wireless communication system as needed. In various embodiments, some elements of the illustrated method may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.
[0138] In 602, the NG-RAN can receive one or more data packets from a network node (e.g., a User Plane Function (UPF)) that include one or more Reflection Quality of Service (QoS) Indicator (RQI) tags. Furthermore, the NG-RAN (e.g., gNB) can track each RQI tag of packets received from the UPF via a Next-Generation User Plane Interface (NG-U), such as the N3 interface. In some implementations, if an RQI tag or bit is not set (e.g., includes or equals a set value of 0), the NG-RAN can forward the RQI tag to the UE in the DL SDAP header. For example, according to some implementations, if the header is configured, the NG-RAN can convert an RQI field received via the N3 interface into an RQI field in the SDAP header.
[0139] In section 604, if an RQI tag is set (e.g., including or equal to a bit value such as 1), the NG-RAN can determine whether there are active uplink QoS rules for the corresponding QFI and SDF associated with the incoming packet. In other words, the NG-RAN can determine whether there are UL QoS rules associated with the incoming packet. This determination may require processing 5-tuples associated with packets in the received IP flow. Furthermore, if the NG-RAN determines that there are no active UL QoS rules associated with the incoming packet, the NG-RAN can forward the packet with the RQI tag to the UE. Additionally, according to some implementations, the NG-RAN can also create an RQI mapping corresponding to the UL QoS rules of the QoS flow.
[0140] In 606, NG-RAN can determine, based on at least one of one or more timers, one or more active UL QoS rules, and status information received from the UE, whether to include or avoid including RQI tags in transmissions of one or more data packets to the UE. For example, NG-RAN can determine that the UL QoS rules currently used by the UE are the same as those in the RQI tags received from the UPF. Therefore, NG-RAN can optionally choose not to send RQI tags in one or more packets transmitted to the UE because the UE has already utilized the appropriate QoS rules. Alternatively or additionally, NG-RAN can choose not to include RQI tags in subsequent transmissions to the UE based on one or more RQ timers maintained by NG-RAN or the UE. Since these RQ timers can indicate the point in time when the UE can discard the corresponding QoS rule, NG-RAN can also optionally allow the QoS rule to expire by excluding the RQI tag. In some implementations, NG-RAN may not maintain an RQ timer, but instead receive periodic status report signaling from the UE. This periodic status report signaling may include status information about the UE's RQ timer (e.g., the amount of time remaining before the timer expires and the dropping of current QoS rules). Therefore, NG-RAN may be able to reduce the processing burden on the UE by not sending redundant or non-useful RQI tags for which the UE would have to process IP 5-tuples.
[0141] In 608a, according to some implementations, the NG-RAN may provide the UE with an RQI tag based on the factors or parameters used in the determinations of 604 and 606. In some implementations, the NG-RAN may provide the UE with an RQI tag by “piggybacking” the RQI tag on the DL packet. For example, the NG-RAN may utilize the DL SDAP header to include the RQI tag with the data packets sent to the UE. Therefore, for this purpose, the DL packet should be available when the NG-RAN attempts to send the RQI tag.
[0142] In 608b, according to some implementations, NG-RAN can choose not to provide an RQI tag to the UE based on the factors or parameters used in the determinations in 604 and 606. For example, if an RQI tag is not provided to the UE, the UE's RQ timer may expire, and the UE may delete the QoS rule. According to some implementations, this can be beneficial if NG-RAN determines that the UE's current QoS rule should be discarded or deleted so that a new QoS rule can be implemented. Furthermore, NG-RAN may also be able to ensure that expired QoS rules at the UE (e.g., QoS rules that may have already been discarded after their RQ timers expire) do not send RQI tags.
[0143] Additional Information
[0144] In some implementations, both the UE and the NG-RAN (e.g., base stations such as gNB) can track the RQ timer used by the UE for each PDU session. For example, the 5GC can provide the RQ timer as part of the Reflective QoS Attribute (RQA) per PDU session. Furthermore, when the NG-RAN detects that the UE can delete a QoS rule, it can send an RQI tag to the UE to keep the QoS rule “alive” or active. Alternatively, for reliability purposes, the NG-RAN can transmit or send the RQI tag multiple times (corresponding to multiple packets). In some implementations, these “keep-alive” messages can be sent along with DL packets if they are available. Alternatively, “keep-alive” messages can be transmitted with new DL SDAP control PDUs. Therefore, the NG-RAN may need to run its own RQ timer. Consequently, the UE's RQ timer may not be synchronized with the NG-RAN's RQ timer, which could further lead to QoS rules with longer lifetimes than expected.
[0145] In some implementations, the UE may periodically indicate the status of the RQ timer to the NG-RAN. For example, the status indicator or indication may be in the form of a QoS rule identifier plus a 1-bit indication of whether the RQ timer is currently active or has expired. Alternatively, the status indicator or indication may include additional information, such as the remaining time of the RQ timer's expiration. Furthermore, according to some implementations, the periodicity of the UE's periodic indication of the RQ timer's status may be configurable by the NG-RAN. In some implementations, the status report may be sent using a new UL SDAP control PDU. For example, the NG-RAN may delete or discard active QoS rules for which its UE has indicated the RQ timer has expired. The NG-RAN can then use the status report to determine whether to send an RQI tag received in a subsequent DL packet. Therefore, the UE may need to send periodic reports to the NG-RAN. Furthermore, the status of the NG-RAN (QoS rules) may not be entirely consistent with that of the UE.
[0146] In some implementations, the NG-RAN (e.g., base station, gNB) instead of the UE may maintain the RQ timer. For example, when the NG-RAN's RQ timer expires, the NG-RAN may send an indication to the UE that the RQ timer has expired, which may further instruct the UE to discard its QoS rules associated with that RQ timer and PDU session. In some implementations, the NG-RAN may use a DL SDAP control PDU to send the indication to the UE. Alternatively or additionally, the NG-RAN may utilize RRC reconfiguration signaling to indicate to the UE that the RQ timer has expired and that the UE should discard or delete its QoS rules. One advantage of the NG-RAN instead of the UE maintaining the RQ timer is that there may be no discernible mismatch in the QoS states of the UE and NG-RAN. Furthermore, since the UE may not have to maintain the RQ timer due to the NG-RAN performing this task, the UE can benefit from reduced processing and power consumption. Additionally, according to some implementations, the NG-RAN may only need to send the RQI once during the duration of the QoS rule, which can further minimize UE processing requirements. Additionally or alternatively, and according to some implementations, for greater reliability, NG-RAN may transmit RQI multiple times. In some implementations, NG-RAN may use DL packets or DL SDAP control PDUs to transmit RQI. According to some implementations, for greater reliability, uplink SDAP control acknowledging the establishment of QoS rules and / or the expiration of RQ timers may be required. Therefore, NG-RAN may configure the UE to require the UE to transmit the acknowledgment response.
[0147] In some implementations, where no spare bits are available in the DL SDAP header to distinguish between data and control PDUs, NG-RAN may use the QFI value 0 to indicate that the payload is an SDAP control PDU. For example, a "keep-alive" SDAP control PDU may indicate the QFI and packet fields corresponding to a QoS rule. Alternatively, in some implementations, NG-RAN may also use an RQ timer-expired SDAP control PDU to indicate the QFI and packet fields corresponding to a QoS rule to the UE. Furthermore, in some implementations, the use of the QFI value 0 is not limited to these DL SDAP control PDUs. More specifically, the QFI value 0 may be used as a general mechanism for the transmission of control information or to provide such a general mechanism. For example, in some implementations, the QFI value 0 may be used as a DL SDAP control PDU to manage handover.
[0148] In some implementations, a spare bit may be present in the UL SDAP header, which can be used to characterize a new UL SDAP PDU or an extended header. Alternatively, according to some implementations, the UE may use an RQ timer status report SDAP control PDU to periodically indicate the status of the RQ timer to the NG-RAN. For example, the status may be indicated as a QoS rule identifier plus a 1-bit indication of whether the RQ timer is running or has expired.
[0149] In some implementations, the UE can provide a response to RQI received from the NG-RAN (e.g., a base station). For example, the UE can acknowledge that it has created a QoS rule using parameters (QFI plus packet filter information). Alternatively, according to some implementations, the UE can provide a response to the expiration of its RQI timer. For example, the UE can provide the NG-RAN with an acknowledgment message that the UE has deleted the corresponding QoS rule.
[0150] Exemplary Implementation
[0151] Another exemplary embodiment may include a device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.
[0152] Another exemplary implementation may include a method comprising: performing any or all of the foregoing examples by a device.
[0153] Another implementation may include a non-transitory computer-accessible memory medium that, when executed at the device, causes the device to perform any or all of the instructions of any of the foregoing examples.
[0154] Another exemplary embodiment may include a computer program that includes instructions for performing any or all of the portions of any of the examples described above.
[0155] Another exemplary embodiment may include an apparatus that includes means for performing any or all of the elements of any of the foregoing examples.
[0156] Another exemplary embodiment may include an apparatus comprising a processing element configured to cause a wireless device to perform any or all of the elements of any of the foregoing examples.
[0157] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.
[0158] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.
[0159] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.
[0160] In some implementations, the device (e.g., UE 106 or BS 102) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and wherein the processor is configured to read from the memory medium and execute the program instructions, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations of method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.
[0161] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.
Claims
1. An apparatus for wireless communication, the apparatus comprising: At least one processor, the at least one processor being configured to cause the base station to: Receive one or more data packets from a network node, wherein the one or more data packets include one or more Reflective Quality of Service (QoS) Indicator (RQI) tags; Receive periodic status report signaling from the user equipment (UE), the periodic status report signaling including status information associated with one or more active uplink UL QoS rules and one or more reflection quality of service (RQ) timers maintained by the UE; Based on at least one of the status information or the values of the one or more RQI tags, identify the one or more active UL QoS rules associated with the UE; Start and maintain at least one timer corresponding to the QoS rules of the Protocol Data Unit (PDU) session with the UE; Based on the at least one timer maintained by the base station, the one or more active UL QoS rules, and the status information received from the UE, it is determined that the one or more RQI tags are included in the transmission of the one or more data packets to the UE; as well as The one or more data packets are transmitted to the UE, wherein the one or more data packets include the one or more RQI tags.
2. The apparatus according to claim 1, wherein, The at least one processor is configured to cause the base station to: Based on the at least one timer maintained by the base station, it is determined that the UE will discard active UL QoS rules based on another timer initiated and maintained by the UE; and In response to determining that the UE will discard the active UL QoS rule, a message instructing the UE to continue using the active UL QoS rule is transmitted.
3. The apparatus according to claim 2, wherein, The message is transmitted via Downlink Service Data Adaptation Protocol (SDAP) control PDU signaling.
4. The apparatus according to claim 2, wherein, The at least one timer is provided by the 5GCN (5th Generation Core Network) per PDU session as part of the Reflective QoS Attribute (RQA).
5. The apparatus according to claim 1, wherein, The at least one processor is further configured to cause the base station to: Configure the periodicity of the reporting signaling.
6. The apparatus according to claim 1, wherein, The reporting signaling includes at least one of the following: a QoS rule identifier, a 1-bit indication of whether the one or more RQ timers are running or have expired, and an indication of the remaining time of the one or more RQ timers upon expiration.
7. The apparatus according to claim 1, wherein, At least one processor is further configured to cause the base station to: When the at least one timer expires, signaling is transmitted, which includes an indication to the UE to delete the QoS rule.
8. The apparatus according to claim 7, wherein, The instruction is transmitted using Downlink Service Data Adaptation Protocol (SDAP) Control PDU signaling or Radio Resource Control (RRC) Reconfiguration signaling.
9. The apparatus according to claim 1, wherein, The at least one processor is further configured to cause the base station to: The signaling is transmitted to the UE, the signaling including a Quality of Service Flow Identifier (QFI) value of 0 to indicate that the payload of the one or more data packets is a Service Data Adaptation Protocol (SDAP) Control Protocol Data Unit (PDU).
10. The apparatus according to claim 7, wherein, The at least one processor is further configured to cause the base station to: The UE is configured to transmit to the base station an acknowledgment or response to at least one of the establishment of a new QoS rule and the expiration of an RQ timer.
11. A method for wireless communication, the method comprising: From base station: Receive one or more data packets from a network node, wherein the one or more data packets include one or more Reflective Quality of Service (QoS) Indicator (RQI) tags; Receive periodic status report signaling from the user equipment (UE), the periodic status report signaling including status information associated with one or more active uplink UL QoS rules and one or more reflection quality of service (RQ) timers maintained by the UE; Based on at least one of the status information or the values of the one or more RQI tags, identify the one or more active UL QoS rules associated with the UE; Start and maintain at least one timer corresponding to the QoS rules of the Protocol Data Unit (PDU) session with the UE; Based on the at least one timer maintained by the base station, the one or more active UL QoS rules, and the status information received from the UE, it is determined to avoid including the one or more RQI tags in the transmission of the one or more data packets to the UE; The one or more data packets are transmitted to the UE, wherein the one or more data packets do not include the one or more RQI tags.
12. The method of claim 11, wherein the determination of the one or more active UL QoS rules is further based on processing a 5-tuple associated with the one or more data packets.
13. The method of claim 12, further comprising: Based on the values of the one or more RQI tags, it is determined that there are no one or more active UL QoS rules associated with the UE; In response to determining that there are no one or more active UL QoS rules associated with the UE, the one or more data packets are forwarded to the UE. The one or more data packets mentioned therein include the one or more RQI tags.
14. The method of claim 13, wherein one or more RQI tags are forwarded to the UE in a downlink Serving Data Adaptation Protocol (SDAP) header.
15. An apparatus for wireless communication, the apparatus comprising: At least one processor, the at least one processor being configured to equip the user with a UE: The UE receives configuration information for periodic status reporting signaling from the base station, wherein the configuration information can be used by the UE to configure the periodicity of the periodic status reporting signaling. The system transmits periodic status report signaling to the base station, wherein the report signaling includes status information associated with one or more active uplink UL quality of service (QoS) rules and one or more reflection quality of service (RQ) timers maintained by the UE. Receive one or more data packets including one or more Reflection QoS Indicator (RQI) tags, wherein the determination of the one or more data packets including the one or more RQI tags indicates that the RQI tags should be included in the one or more data packets is performed by the base station based on the one or more active UL QoS rules, the state information and at least one timer maintained by the base station.
16. The apparatus according to claim 15, wherein, The at least one processor is further configured such that the UE: The base station receives a message instructing the UE to continue using the active UL QoS rules.
17. The apparatus according to claim 16, wherein, The at least one processor is further configured such that the UE: The signaling received from the base station includes a Quality of Service Flow Identifier (QFI) value of 0 to indicate that the payload of the one or more data packets is a Service Data Adaptation Protocol (SDAP) Control Protocol Data Unit (PDU).
18. The apparatus according to claim 15, wherein, The at least one processor is further configured such that the UE: The base station is transmitted an acknowledgment or response message for at least one of the establishment of a new QoS rule and the expiration of an RQ timer.