Method and apparatus for transmitting quality of service information via user plane
By transmitting QoS information in the user plane, the issues of QoS information transmission delay and accuracy in 5G NR are resolved, enabling more efficient QoS information transmission and simplifying signaling processing.
Patent Information
- Application Number
- CN202280097439.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-24
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-06-24
AI Technical Summary
Traditional QoS information transmission mechanisms suffer from time delays and poor accuracy and reliability in 5G NR, especially the long and simple signaling process on the control plane.
By transmitting QoS information in the user plane, control plane procedures and signaling overhead are reduced, and a more flexible and dynamic QoS information delivery is achieved by using a user plane mechanism to transmit QoS information.
It improves the reliability and real-time performance of QoS information transmission, simplifies control plane processes, and reduces the signaling processing burden.
Smart Images

Figure CN119422406B_ABST
Abstract
Description
Technical Field
[0001] This disclosure is generally directed to wireless communications. In particular, this disclosure relates to methods and apparatus for transmitting Quality of Service (QoS) information over the user plane. Background Technology
[0002] A data transmission session in a communication network can include one or more data streams. These data streams within a session can be associated with Quality of Service (QoS) information. QoS information relates to the characteristics or requirements of the data streams and provides guarantees for communication service capabilities. The delivery of QoS information may involve various network nodes, elements, or entities within the communication network, as well as numerous signaling processes between these nodes, elements, or entities. Traditional QoS mechanisms may experience time delays and exhibit poor accuracy and reliability. Summary of the Invention
[0003] This document relates to methods, systems, and apparatuses for wireless communication, and more specifically, to methods, systems, and apparatuses for transmitting Quality of Service (QoS) information over a user plane. Various embodiments in this disclosure may be beneficial for improving the ability to transmit QoS information.
[0004] In one embodiment, this disclosure describes a method for wireless communication. The method includes: a first network element transmitting first Quality of Service (QoS) information to a second network element by the first network element transmitting a data packet via a user to the second network element, wherein the data packet includes the first QoS information.
[0005] In one embodiment, this disclosure describes a method for wireless communication. The method includes: a second network element receiving first Quality of Service (QoS) information from a first network element by the second network element receiving a data packet from the first network element via a user plane, wherein the data packet includes the first QoS information.
[0006] In some other embodiments, the apparatus for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the methods described above.
[0007] In some other embodiments, the device for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the methods described above.
[0008] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above.
[0009] The above and other aspects, and embodiments thereof, are described in more detail in the accompanying drawings, description, and claims. Attached Figure Description
[0010] Figure 1A An example of a wireless communication system including a wireless network node and one or more user devices is shown.
[0011] Figure 1B Schematic diagrams of various embodiments of the present disclosure are shown.
[0012] Figure 1C Another schematic diagram of various embodiments of the present disclosure is shown.
[0013] Figure 2 An example of a network node is shown.
[0014] Figure 3 An example of a user device is shown.
[0015] Figure 4A A flowchart of a method for wireless communication is shown.
[0016] Figure 4B A flowchart of another method for wireless communication is shown.
[0017] Figure 5 A schematic diagram of a non-limiting embodiment for wireless communication is shown.
[0018] Figure 6 A schematic diagram of a non-limiting embodiment for wireless communication is shown.
[0019] Figure 7 A schematic diagram of a non-limiting embodiment for wireless communication is shown.
[0020] Figure 8 A schematic diagram of a non-limiting embodiment for wireless communication is shown. Detailed Implementation
[0021] This disclosure will now be described in detail below with reference to the accompanying drawings, which form part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.
[0022] Throughout the specification and claims, terms may have subtle meanings suggested or implied in the context that go beyond their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. It is intended, for example, that the claimed subject matter includes all or part of exemplary embodiments or combinations of embodiments.
[0023] Generally, terms can be understood, at least in part, from their usage in context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend, at least in part, on the context in which such terms are used. Typically, “or,” if used with an associative list such as A, B, or C, is intended to mean A, B, and C, used here in an inclusive sense, and A, B, or C, used here in an exclusive sense. Additionally, terms such as “one or more” or “at least one” as used herein, depending at least in part on the context, can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can again be understood to convey a singular or plural usage, depending at least in part on the context. Furthermore, the terms “based on” or “determined by” can be understood to not necessarily convey an exclusive set of factors, and can, conversely, allow for the existence of additional factors that are not necessarily explicitly described, again, depending at least in part on the context.
[0024] This disclosure describes a method and apparatus for transmitting Quality of Service (QoS) information over a user plane (UP).
[0025] In a communication network, end-to-end communication can be established as a data communication session (or alternatively, a data session or communication session). Each data session can include the transmission of data of different types, characteristics, and transmission requirements. Therefore, a data session can be configured to contain multiple data streams (which may be referred to as QoS streams), each of which includes data with similar transmission characteristics and / or associated with similar transmission quality requirements. The transmission of each of these data streams can be controlled and configured based on its transmission characteristics / requirements. For example, the allocation of communication resources by the communication network to the data streams can be based on the transmission characteristics / requirements of the data streams. These transmission characteristics / requirements of the data streams can be used to determine a set of transmission parameters, collectively referred to as the QoS information of the data streams. The transmission configuration of the data streams (such as communication resource allocation) can then be based on this QoS information. The determination and transmission of QoS information can be performed by network elements in the communication network assigned to configure and manage the transmission of the data streams. A “network element” can include one or more network nodes, one or more network functions, and / or one or more network entities.
[0026] Data flows can be associated with QoS information. In a network, QoS information is typically used to provide service guarantees. QoS information relates to the characteristics or requirements of data flows. QoS information can include QoS parameters and QoS policies, such as QoS profiles, QoS rules, and / or policy control and charging (PCC) rules.
[0027] In traditional QoS mechanisms, QoS information is delivered through the control plane (CP). The delivery of QoS information may involve various network nodes, elements, or entities within the communication network, as well as numerous signaling processes between these nodes, elements, or entities. In 5G New Radio (NR), the core network (CN) maps user plane traffic to QoS flows, and the access network (AN) binds QoS flows to the data radio bearer (DRB). To accomplish this mapping process, multiple control plane processes are required for QoS information transmission, involving multiple control plane network functions (NFs), such as policy control function (PCF), session management function (SMF), and access and mobility management function (AMF). The transmission mechanism of QoS information through the control plane can be semi-static, long-chained, and / or single-means. Traditional methods of QoS information transmission may suffer from time delays, resulting in poor accuracy and reliability of QoS capabilities.
[0028] Figure 1A A wireless communication system 100 is illustrated, comprising a core network (CN) 110, a radio access network (RAN) 130, and one or more user equipment (UEs) (152, 154, and 156). RAN 130 may include a wireless network base station or an NG radio access network (NG-RAN) base station or node, which may include a node B (NB, e.g., gNB) in mobile telecommunications. In one embodiment, core network 110 may include a 5G core network (5GC), and interface 125 may include a new generation (NG) interface.
[0029] refer to Figure 1AThe first UE 152 can wirelessly receive one or more downlink communications 142 from RAN 130 and wirelessly transmit one or more uplink communications 141 to RAN 130. Similarly, the second UE 154 can wirelessly receive downlink communications 144 from RAN 130 and wirelessly transmit uplink communications 143 to RAN 130; and the third UE 156 can wirelessly receive downlink communications 146 from RAN 130 and wirelessly transmit uplink communications 145 to RAN 130. For example, but not limited to, the downlink communications may include a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and the uplink communications may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
[0030] In some implementations, the core network (CN) may include one or more core network functions related to QoS information, such as Figure 1B As shown, it is described below. The core network can communicate with UE 171, with RAN 172, and / or with UE via RAN.
[0031] A more detailed description Figure 1B Further description of the functions of various network nodes in a wireless communication network and network functions related to QoS information.
[0032] Regarding UPF (User Plane Function) 173, the UPF performs functions including, but not limited to, acting as an anchor point for mobility within / between radio access technologies (RATs), packet routing and forwarding, traffic usage reporting, user plane Quality of Service (QoS) processing, downlink packet buffering, and downlink data notification triggering. The UPF service area comprises an area consisting of one or more tracking areas within which communication sessions associated with the UPF can be initiated by RAN nodes through a direct interface between the RAN and the UPF (e.g., ...). Figure 1B The N3 interface shown provides service without requiring the addition or removal / reassignment of a new UPF. When the UE moves outside the UPF service area, an intermediate UPF (I-UPF) can be inserted / repositioned. An I-UPF can be used, for example... Figure 1BThe N3 tunnel, as indicated in the diagram, is used to connect to RAN 172, and can be used, for example, as... Figure 1B The N9 tunnel as indicated in the text.
[0033] Regarding AMF (Access and Mobility Management Function) 176, AMF performs functions including, but not limited to, registration management, connection management, reachability management, and mobility management for UE 171. AMF also performs access authentication and access authorization. AMF 176 has the function of securely terminating the non-access stratum (NAS) and relaying session management NAS messages between UE 171 and SMF 177. AMF 176 also performs SMF selection during the communication session establishment process and UE mobility process. AMF can forward QoS profiles from SMF to RAN (or AN) and QoS rules from SMF to UE.
[0034] Regarding SMF (Session Management Function) 177, the SMF performs functions including, but not limited to, establishing, modifying, and releasing communication sessions; allocating and managing UE IP addresses (including optional authorization functions); selecting and controlling UPF 173; and downlink data notification. Each SMF can control one or more UPFs and is associated with a service area that is the set of UPF service areas of all UPFs under its control. The SMF derives a QoS profile according to PCC rules, generates QoS flows, sends the QoS profile to the RAN, and sends packet detection rules (PDRs) to the UPFs. PCC rules are bound to QoS flows. In some implementations, the SMF also selects UPFs based on UE or session granularity and can assign IP addresses, collect charging data, connect to a charging center, and so on. I-SMFs (intermediate SMFs) are inserted, modified, or removed from the communication session as needed to control I-UPFs (intermediate UPFs), which cannot be controlled by the original SMF 177 selected for the communication session because they belong to different SMF service areas.
[0035] Regarding PCF (Policy Control Function) 184, PCF is responsible for a unified policy framework, providing policy rules for control plane functions, determining policy control and charging (PCC) rules, and authorizing Session Management Functions (SMFs) based on service data flows (SDFs). PCF enforcement functions include, but are not limited to, providing policy rules and controlling other network nodes to enforce those rules. Specifically, PCF provides access and mobility-related policies to AMF 176, enabling AMF 176 to enforce them during mobility procedures.
[0036] Regarding the Unified Data Repository (UDR) 181, the UDR can support the storage / retrieval of structured data for network access, application data (e.g., packet flow descriptions (PFDs) for application detection, application request information for multiple UEs, and application requests for data traffic routing impacts, as described above and in more detail below), and the storage / retrieval of network group IDs (e.g., external group IDs or internal group IDs) corresponding to subscriber identifiers. The UDR can reside in the same public-land mobile network (PLMN) as the network application service to which it provides application data storage. The 5G system architecture allows the UDM, PCF, and NEF to store data in the UDR, including subscription data and policy data of the UDM and PCF, and structured data and application data for access from the NEF (including packet flow descriptions (PFDs) for application detection and AF request information for multiple UEs).
[0037] Regarding UDM (Unified Data Management) 185, UDM is responsible for user identification, access authorization, and unified processing of user subscription data and authentication data.
[0038] Regarding NEF (Network Open Function) 182, these network nodes can use standardized interfaces (e.g., the Nudr interface) to store / retrieve information about structured data from the UDR. The NEF provides an AF with a secure way to provide various information to the core network, including but not limited to information about the impact of applications on data traffic routing. The NEF can authenticate, authorize, and assist in restricting requests from application functions (AFs). Access to the NEF can be through an open application programming interface (API) provided by the core network. A specific NEF instance can support one or more of these functions, and therefore a single NEF can support a subset of the APIs specified by the NEF. The NEF can be configured to access a UDR located in the same PLMN as the NEF.
[0039] Regarding AF (Application Function) 186, these network nodes can interact with the core network to provide services to applications. AFs can interact with applications at one end and with network functions in the core network via NEF at the other end. In some implementations, AFs considered trusted by the core network can bypass NEF and interact directly with other relevant network functions in the core network. AFs interact as the control plane of applications and transmit application QoS requirements / parameters.
[0040] Regarding AUSF (Authentication Server Functionality) 175, AUSF can handle authentication and access authentication, and can authenticate external applications and B2B.
[0041] Regarding the Network Function Repository Function (NRF)
[183] , the NRF can be responsible for the discovery and registration of network function services.
[0042] Regarding the data network (DN) 174, the DN can correspond to carrier services, internet access, or third-party services, etc. In some implementations, applications (Apps) can be deployed in the DN.
[0043] In the core network, AMF, SMF, PCF, AUSF, UDR, UDM, NRF, NEF, and AF can belong to the control plane; and UPF can belong to the user plane.
[0044] In 5G NR, QoS information transmission occurs through the control plane. Before applications transmit service data, service authentication and user service subscription queries may need to be performed via NRF, UDM, UDR, AUSF, etc. Then, the PCF determines QoS policies such as PCC rules based on the obtained service requirements and subscription information. PCC rules include QoS parameters and charging policies. For third-party applications, the AF also needs to perform security authentication, service requirement, and QoS information transmission via NEF. The SMF performs SDF-to-QoS flow binding based on QoS and service requirements. Upon receiving the PCC rules provided by the PCF, the SMF assigns a QFI to the new QoS flow and derives its QoS profile, corresponding UPF directives, and one or more QoS rules from the PCC rules and other information provided by the PCF. When a PDU session is established, the SMF transmits QoS information by configuring PDR for the UPF, QoS profiles for the RAN, and QoS rules for the UE. Based on the QoS information from the SMF, the UPF maps IP data flows to multiple QoS flows using the PDU session. The SMF provides QoS profiles to the access network (AN) via the AMF, thereby instructing the AN to perform data flow matching and radio bearer mapping. UE uplink transmissions match and map packets according to QoS rules, and these QoS rules are also sent to the UE by the SMF via the AMF in NAS messages. For GBR QoS flows, alternative QoS profiles can be transmitted by enabling notification control, and the AN can select an appropriate set of QoS parameters from multiple QoS profiles. QoS profiles can be used for an extended period in a PDU session until the RAN selects an alternative QoS profile and feeds it back to the CN. QoS information transmission via the control plane is in a semi-static mode.
[0045] In 5G NR, a QoS flow is associated with QoS requirements specified by one or more QoS parameters and QoS characteristics, such as those in the QoS information. Any QoS flow can be characterized by: a QoS profile provided by the SMF to the AN at the N2 reference point via the AMF, or a QoS profile pre-configured in the AN; one or more QoS rules and optional QoS flow-level QoS parameters associated with these QoS rules, which can be provided by the SMF to the UE at the N1 reference points via the AMF and / or derived by the UE through applied reflective QoS control; and / or one or more ULs and one or more DL PDRs provided by the SMF to the UPF. For each QoS flow, the QoS profile may include QoS parameters such as a 5G QoS identifier (5QI) and / or allocation and retention priority (ARP). Only for each non-GBR QoS flow, the QoS profile may also include QoS parameters such as a reflective QoS attribute (RQA). For each GBR QoS flow only, the QoS profile may also include QoS parameters, such as the guaranteed flow bit rate (GFBR) and / or the maximum flow bit rate (MFBR); in the case of GBR-only QoS flows, the QoS profile may also include one or more QoS parameters, such as notification control and maximum packet loss rate. In 5G NR, 5G QoS features as part of the QoS profile associated with 5QI may include at least one of the following: resource type (e.g., GBR, delay-critical GBR, or non-GBR), priority, packet delay budget (including core network packet delay budget), packet error rate, average window (only for GBR and / or delay-critical GBR resource types), and / or maximum data burst size (only for delay-critical GBR resource types). Standardized 5QI (e.g., non-dynamic 5QI) can indicate standardized QoS features to reduce signaling overhead. In the case of dynamic 5QI, 5G QoS features need to be included in the QoS profile, which can result in a large number of QoS parameters, leading to control plane overhead.
[0046] In 5G NR, QoS profiles can be sent from the SMF to the RAN via the AMF on the N2 interface; QoS rules can be sent from the SMF to the UE via the AMF on the N1 interface. The PDR can be considered a Service Data Flow (SDF) template, provided by the SMF to the UPF. The Reflective QoS Attribute (RQA) is an optional QoS parameter indicating that certain traffic carried on this QoS flow is affected by reflected QoS. The (R)AN enables the transmission of the Reflective QoS Indication (RQI) for the AN resource corresponding to the QoS flow only when the RQA is signaled for the QoS flow. The RQA can be signaled to the NG-RAN via the N2 reference point during UE context establishment and QoS flow establishment or modification in the NG-RAN. To complete the above mapping process, multiple control plane procedures are required, involving multiple control planes (NFs) in the core network, and QoS information is transmitted in the signaling.
[0047] Most importantly, the transmission mechanism of QoS information through the control plane can be semi-static, long-chain, and single-means. Traditional methods of QoS information transmission may be time-delayed, and their accuracy and reliability are poor.
[0048] The present invention provides a method and apparatus for transmitting QoS information on the user plane, which solves at least one of the difficulties / problems discussed above, reduces control plane signaling processing, and / or improves the ability to transmit QoS information.
[0049] Figure 2 An example of an electronic device 200 implementing one or more core network functions or one or more base stations is shown. The example electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include network interface circuitry 209 to enable communication between the base station and other base stations and / or the core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The electronic device 200 may optionally include an input / output (I / O) interface 206 for communication with operators, etc.
[0050] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured to perform functions of one or more network nodes in processor 124. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.
[0051] Figure 3 An example of an electronic device implementing terminal device 300 (e.g., user equipment (UE)) is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. UE 300 may include a communication interface 302, system circuitry 304, input / output interface (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of an implementation of any desired functionality in UE 300. In this regard, system circuitry 304 may include logic that, as an example, enables decoding and playback of music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, as an example, for internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface units. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.
[0052] refer to Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may follow any of various arrays of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and codes. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G standards, and / or 6G standards. However, the techniques described below are applicable to other wireless communication technologies, whether they originate from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.
[0053] refer to Figure 3 System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to implement the desired functions of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that UE 300 will send or has received via communication interface 302. In various embodiments, the system power of UE 300 may be supplied by power storage devices such as batteries or transformers.
[0054] This disclosure describes various embodiments for transmitting Quality of Service (QoS) information over the user plane, which may be partially or wholly described above. Figures 2 to 3The core network functions, access network, and / or user equipment described herein are implemented. Various embodiments in this disclosure enable the transmission of QoS information via the user plane, which can deliver more QoS information and / or dynamic real-time QoS information. Furthermore, the user plane transmission mechanism differs from the control plane transmission mechanism, which improves the reliability of QoS information transmission.
[0055] refer to Figure 4A This disclosure describes various embodiments of a method 400 for wireless communication. The method may include step 410: transmitting first quality of service (QoS) information from a first network element to a second network element by transmitting a data packet from the first network element to the second network element via a user, wherein the data packet includes the first QoS information.
[0056] refer to Figure 4B This disclosure describes various embodiments of a method 450 for wireless communication. The method may include step 460: receiving first Quality of Service (QoS) information from a first network element by a second network element receiving data packets from the first network element via a user plane, wherein the data packets include the first QoS information.
[0057] In some implementations, the first network element includes one of the following: core network (CN), user plane function (UPF), radio access network (RAN), serving data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, medium access control (MAC) layer, centralized unit (CU), distributed unit (DU), application server, edge node, base station, backhaul adaptation protocol (BAP) layer, integrated access backhaul (IAB) node, or user equipment (UE). The edge node can be a mobile edge computing (MEC) node or a multi-access edge computing (MEC) node.
[0058] In some implementations, the second network element includes one of the following: core network (CN), UPF, radio access network (RAN), Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, central unit (CU), distributed unit (DU), application client, edge node, base station (BS), backhaul adaptation protocol (BAP) layer, IAB node, or user equipment (UE). The edge node can be a mobile edge computing (MEC) node or a multi-access edge computing (MEC) node.
[0059] In some implementations, the first QoS information includes at least one of the following: one or more Packet Detection Rules (PDR), one or more Policy Control and Charging (PCC) Rules, one or more QoS Profiles, one or more QoS Rules, one or more QoS Parameters, one or more QoS Features, one or more Alternative QoS Profiles, one or more Alternative QoS Sets, one or more QoS Identifiers (IDs), one or more QoS Information Indices, one or more QoS Parameter Ranges, one or more 5G QoS Identifiers (5QIs), one or more indexed QoS Profiles, one or more indexed QoS Parameter Sets, one or more QoS Parameter Set Index Ranges, one or more QoS Types, or one or more QoS Groups.
[0060] In some implementations, the user plane includes at least one of the following: User Plane Function (UPF), user plane of the Service Data Adaptation Protocol (SDAP) layer, user plane of the Packet Data Convergence Protocol (PDCP) layer, user plane of the Radio Link Control (RLC) layer, user plane of the Media Access Control (MAC) layer, user plane of the Central Unit-Distributed Unit (CU-DU) interface (F1-U), CU-User Plane (CU-UP), DU-UP, General Packet Radio Service Tunneling Protocol User Plane (GTP-U), Next Generation User Plane (NG-U), Xn User Plane (Xn-U), user plane of QoS flow, user plane of CN-RAN interface, user plane of inter-BS interface, X2-U, user plane of the Backhaul Adaptation Protocol (BAP) layer, or user plane of the Integrated Access Backhaul (IAB) node.
[0061] In some implementations, a data packet including first QoS information may be located either in the packet header or in a predefined data area of the data packet. In some implementations, the first QoS information may be transmitted along with other data in a predefined data area of the data packet, or the first QoS information may be transmitted separately in a predefined data area of the data packet. In some implementations, the data area may be referred to as a data field. In some implementations, the data area may be referred to as a data domain.
[0062] In some implementations, the data packet including the first QoS information includes: the first QoS information being located in one of the following: PDU header, control PDU, data PDU or MAC control element (CE), PDU header field, and PDU data field.
[0063] In some implementations, method 400 or method 450 may further include: the first network element transmitting second QoS information to the second network element via control.
[0064] In some implementations, the content of the first QoS information and the attributes of the second QoS information are different or the same.
[0065] In some implementations, when the content of the first QoS information and the content of the second QoS information are different, one of the following can be performed: the first QoS information is mapped to a DRB, and the second QoS information is mapped to a signaling radio bearer (SRB); the first QoS information is transmitted via the user plane, and the second QoS information is transmitted via the control plane; the first QoS information is transmitted via a data stream, and the second QoS information is transmitted via a message; the first QoS information is transmitted via a data packet, and the second QoS information is transmitted via signaling; or the first QoS information is transmitted via a data packet, and the second QoS information is transmitted via an information element (IE).
[0066] In some implementations, when the content of the first QoS information and the content of the second QoS information are the same, one of the following can be performed: the first QoS information is mapped to a DRB and the second QoS information is mapped to a Signaling Radio Bearer (SRB); the first QoS information is transmitted via the user plane and the second QoS information is transmitted via the control plane; the first QoS information is transmitted via a data stream and the second QoS information is transmitted via a message; the first QoS information is transmitted via a data packet and the second QoS information is transmitted via signaling; or the first QoS information is transmitted via a data packet and the second QoS information is transmitted via an Information Element (IE).
[0067] In some implementations, the step of transmitting the first QoS information to the second network element may include at least one of the following: transmitting the first QoS information to the second network element in each packet; transmitting the first QoS information to the second network element in the first packet; transmitting the first QoS information as an independent data packet to the second network element; transmitting the first QoS information to the second network element in a periodic manner in packets; transmitting the first QoS information to the second network element in a non-periodic manner in packets; transmitting the first QoS information to the second network element in a global-sub-QoS manner; transmitting the first QoS information to the second network element in a differential QoS manner; transmitting the first QoS information to the second network element in a primary-secondary QoS manner; or transmitting the first QoS information to the second network element in one or more QoS lists.
[0068] In some implementations, the step of transmitting the first QoS information to the second network element may include some or all of the following: the first network element maps the first QoS information into data of a data stream; and / or transmits the first QoS information as a data stream to the second network element.
[0069] In some implementations, the data stream is a shared data stream used for QoS information data and service data; or the data stream is a dedicated data stream used for QoS information.
[0070] In some implementations, the first QoS information corresponds to an entity, wherein the entity includes at least one of the following: a Service Data Adaptation Protocol (SDAP) entity, a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, a Media Access Control (MAC) entity, a QoS-related entity, a Backhaul Adaptation Protocol (BAP) entity, or an Integrated Access Backhaul (IAB) entity.
[0071] In some implementations, the mapping method for the first QoS information includes at least one of the following: mapping the first QoS information together with service data to a shared data radio bearer (DRB); mapping the first QoS information to a dedicated DRB without service data; mapping the first QoS information to a dedicated QoS radio bearer; mapping the first QoS information together with service data to a shared logical channel; mapping the first QoS information to a dedicated logical channel without service data; mapping the first QoS information together with service data to a shared logical channel group; mapping the first QoS information together with service data to a dedicated logical channel group; mapping the first QoS information together with service data to a shared data channel; or mapping the first QoS information to a dedicated data channel without service data.
[0072] In some implementations, the first QoS information is mapped to a data channel and transmitted to the second network element via the data channel.
[0073] In some implementations, method 400 and / or method 450 may further include: the first network element performing the retransmission of a data packet including first QoS information to the second network element via the user plane, wherein the retransmission includes one of the following: an automatic repeat request (ARQ) retransmission mechanism, or a hybrid automatic repeat request (HARQ) retransmission mechanism.
[0074] In some implementations, the first QoS information is transmitted to the second network element via the user plane at a granular level, wherein the granular level includes at least one of the following: based on each flow, based on each PDU, based on each PDU set, based on each frame, based on each packet, or based on each time slot.
[0075] In some implementations, the first QoS information includes at least one of the following: overall QoS information, sub-QoS information, hierarchical QoS information, QoS information with different priorities, or QoS information in a tree structure.
[0076] In some implementations, the first QoS information is generated by a third network element, and / or the first network element is connected to the third network element to obtain the first QoS information.
[0077] In some implementations, the third network element includes one of the following: a QoS information generation unit, an application server, a PCF, a QoS controller, a CN, a RAN, or a UE.
[0078] This disclosure describes below a number of various non-limiting embodiments and / or examples for transmitting Quality of Service (QoS) information over the user plane. These embodiments and / or examples are described as some of the many possible implementations of this disclosure and do not impose any limitation on this disclosure.
[0079] Example 1
[0080] This disclosure describes embodiments for transmitting Quality of Service (QoS) information over the user plane, wherein the core network determines the QoS information and transmits it to the access network via the user plane. An advantage is that when transmitting a large number of QoS parameters, control plane procedures and signaling overhead can be reduced, and a lightweight control plane can be achieved. In some implementations, the network (e.g., the core network and / or access network) can directly address customized and application-level QoS information.
[0081] In some implementations, multiple QoS parameters can be passed from the UPF to the user plane of the access network, or to other UPFs. In 5G NR, the transmission of QoS information requires the SMF to provide QoS profiles to the access network via the AMF, and the SMF needs to send the QoS profiles along with NAS messages to the UE via the AMF. In some implementations, to better match the needs of the access network, an alternative QoS mechanism can be introduced in 5G NR. When the PCF enables notification control, the core network transmits multiple sets of QoS profiles through the control plane. When the access network finds that QoS requirements cannot be guaranteed / met, it selects a set of appropriate QoS parameters from the multiple sets of QoS profiles for the alternative QoS. To avoid adding too much overhead to the control plane, the alternative QoS method can transmit only a limited number of indices of the QoS profiles and can avoid transmitting a large amount of QoS information for specific QoS parameters. Transmitting QoS information on the user plane can flexibly expand the index range of the QoS profiles and transmit more specific QoS parameters. Transmitting QoS information on the user plane also simplifies the control plane process, reduces signaling transmission on the control plane, and / or reduces the processing burden on the control plane, and can transmit more real-time and dynamic QoS information.
[0082] In a non-limiting example of transmitting QoS information on the user plane, the core network determines QoS information (such as QoS profiles, QoS profile index ranges, specific QoS parameters, specific QoS characteristics, and QoS rules) through the PCF, and the PCF sends them to the SMF. The SMF transmits them to the UPF, and the UPF transmits them to the access network. In some implementations, the UPF can use, for example, a communication interface (e.g., the N3 interface) to transmit QoS information as QoS stream data to the access network. In some other implementations, different systems can use different interfaces other than the N3 interface. For example, a 6G system can use interfaces other than the N3 interface, such as a service-based architecture (SBA) interface, to perform the above and some other operations. Unlike the PCF->SMF->AMF->RAN route, QoS information is transmitted on the user plane in the PCF->SMF->UPF->RAN route. Furthermore, the amount of QoS information on the user plane can be larger than that on the control plane.
[0083] For another non-limiting example, due to the high-speed movement of the UE or base station (BS), service data may need to be migrated from one UPF to another. In some implementations, one or more UPFs can be deployed locally, and one or more AMFs, SMFs, and PCFs can be deployed on a larger scale (e.g., at the national or provincial level). Furthermore, when the UE and / or base station move across regions, an intermediate SMF (I-SMF) can be used to assist SMF control forwarding when the original SMF cannot provide service to the UE. For high-mobility scenarios, the QoS transmission chain of 5G NR may be long and may not meet the requirements of high-speed mobility. Through the various embodiments and / or examples described in this disclosure for transmitting QoS on the user plane, QoS information can be directly forwarded from one UPF to another via a communication interface (e.g., the N9 interface) without the need for the process of controlling NFs (such as PCF, SMF, AMF), which can shorten QoS transmission time, enhance service continuity, and / or enhance the user / service experience.
[0084] In some implementations, QoS information migration can be performed using UPF handover during the migration process. A UPF can be triggered to transmit QoS information to another UPF when certain conditions are met or a specific message is received. For example, when an I-UPF is inserted by an SMF, QoS information is transferred from the old UPF to the new I-UPF.
[0085] Figure 5 A schematic diagram illustrating the transmission of user plane QoS information in a mobile scenario is shown, which may include some or all of the following: AMF 501, SMF 512, I-SMF 514, UPF1 522, UPF2 524, and / or UPF3 526. I-SMF can be used to control UPF3. In some implementations, QoS information can be directly forwarded from UPF2 to UPF3 via a communication interface (e.g., the N9 interface).
[0086] In some implementations, new QoS nodes / units (e.g., QoS network functions) can be used to directly connect to the RAN. The new QoS nodes / units provide QoS information to the RAN and / or UE for QoS information transmission on the user plane. The new QoS nodes / units can generate and / or manage QoS information.
[0087] For another non-limiting example, in a business-to-business (toB) scenario, users have group characteristics, and therefore the network elements of the control plane can be further simplified. For example, in industrial areas or automated factories, there are no-fee policies, low mobility, and high customization. Therefore, in a toB scenario, the application server can directly customize QoS information and pass it to the access network on the user plane (e.g., from UPF to RAN or directly from the application server to the RAN user plane). In some implementations, QoS information is transmitted in the data stream. In some implementations, intent-driven applications generate QoS information for QoS customization. In some other implementations, the control plane can be a lightweight implementation, whereby the control plane performs only basic and simple processing, such as session establishment, and may not perform QoS information transmission. In some implementations, the amount of QoS information transmitted on the control plane is small, while the amount of QoS information transmitted on the user plane is large. In some implementations, the QoS information transmitted on the control plane is not real-time, while the QoS information transmitted on the user plane is real-time. In some implementations, the QoS information transmitted on the control plane is semi-static, while the QoS information transmitted on the user plane is dynamic. In some implementations, the QoS information transmitted on the control plane is simple and coarse, while the QoS information transmitted on the user plane is detailed and explicit.
[0088] Figure 6 A schematic diagram of customized QoS transmitted over the user plane is shown, which may include some or all of the following: UE601, RAN603, UPF605, and / or application server607. The application server can directly customize QoS parameters, QoS requirements, and / or other QoS information; and the application server can transmit them to the access network (e.g., from UPF to SDAP layer) on the user plane.
[0089] Example 2
[0090] This disclosure describes another embodiment for transmitting Quality of Service (QoS) information over the user plane, wherein the user plane can transmit QoS information in data packets, such as, but not limited to, in PDU headers, control PDUs, data PDUs, and / or MAC CEs. Based on dynamic QoS information in the data packets, the access network can flexibly map data flows to bearers. This embodiment solves at least one of the challenges / problems associated with transmitting QoS information, achieving advantages and improvements in the field of telecommunications technology, such as the ability to perform real-time and dynamic resource adjustments based on data packet demand, and / or the ability to achieve finer-grained QoS granularity, such as on a per-data-packet basis.
[0091] For a non-limiting example, QoS information may include one or more specific QoS parameters, such as, but not limited to, 5QI, ARP, RQA, GFBR, MFBR, notification control, maximum packet loss rate, resource type, priority level, packet delay budget, packet error rate, average window, maximum data burst size, etc. In some implementations, QoS information may also include one or more specific QoS index values, such as 5QI, QoS profile index, QoS parameter set index, QoS dataset index range, etc.
[0092] In some implementations, QoS information in data packets is transmitted on the user plane, thus enabling dynamic control of data packets. For example, there are 20 packets from the UPF to the SDAP layer. The first packet carries QoS0, and the eleventh packet carries QoS1. QoS0 is the QoS information for packets from the first to the tenth packet, and QoS1 is the QoS information for packets from the eleventh to the twentieth packet. Based on QoS0 and QoS1, the SDAP layer maps the first ten packets to one DRB and the last ten packets to another DRB.
[0093] In some implementations, QoS information can be transmitted in one or more of the following ways: QoS information is transmitted in each packet, QoS information is transmitted periodically in packets, and / or QoS information is transmitted aperiodically in packets. For each packet's QoS information, each packet has its own QoS control. For example, application frames correspond to packets, and each application frame has its own QoS requirements, such as different levels of importance. The RAN detects the QoS information of a packet and allocates resources based on that packet's QoS information. Packets with higher priority can be allocated to better resources. Resources can be radio bearers (RBs), logical channels (LCs), logical channel groups (LCGs), time resources, frequency resources, or power resources. For periodic patterns, QoS information can be transmitted every m packets or every n time intervals, where m and n are numbers. In Internet of Things (IoT) scenarios, it is beneficial to periodically transmit important QoS information to ensure successful reception of important QoS information. For aperiodic patterns, dynamic QoS control can be performed by inserting QoS information in real time. For example, the first packet carries QoS information, and this QoS information is used for QoS control of subsequent packets until a packet carrying new QoS information appears.
[0094] In some implementations, within the core network, the core network directly maps and transmits QoS information as service data to achieve QoS information transmission on the user plane. For example, but not limited to, mapping QoS information and service data to the same data stream (e.g., a QoS stream), meaning that QoS information and service data are mapped together to one data stream (e.g., QoS stream 1). For example, but not limited to, mapping QoS information and service data to different data streams (e.g., QoS streams), meaning that QoS information is mapped separately to one data stream (e.g., QoS stream 1 or a dedicated QoS information stream), and service data is mapped to another data stream (e.g., QoS stream 2).
[0095] In some implementations, QoS information can be transmitted in the packet header, extended header, or data area of the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U), such as the GTP-UPDU header, GTP-U PDU field, or GTP extended header. For example, the GTP extended header could be the GTP version 1 User Plane (GTPv1-U) extended header. Interfaces used to transmit QoS information on the user plane can include, but are not limited to: the user plane interface from the core network user plane UPF to the RAN, the user plane interface Xn-U between 5G NR base stations, the user plane interface X2-U between 4G base stations, and / or the CU-DU user plane interface F1-U.
[0096] In some implementations, the transmission of QoS information can be mapped onto the user plane at each layer of the access network, such as SDAP, PDCP, RLC, and MAC. Specifically, QoS information can be mapped to PDU data headers, PDU data fields, control units (CEs), control PDUs, data PDUs, etc. In some implementations, QoS information can be carried in packet headers, such as SDAP PDU headers, PDCP PDU data headers, RLC PDU headers, and MAC PDU headers. In some implementations, QoS information can be carried in data PDUs, such as SDAP PDUs, PDCP PDU data, RLC PDUs, MAC PDUs, and the like. In some implementations, QoS information can be carried in control PDUs, such as RLC control PDUs and PDCP control PDUs. In some implementations, QoS information can be mapped into PDU header fields, PDU data fields, control unit (CE) fields, etc.
[0097] Figure 7An exemplary schematic diagram is shown illustrating the inclusion of QoS information in the SDAP PDU data field for transmission. The SDAP PDU header may include at least one of the following indications: QoS flow indication (QFI), reflective QoS flow to DRB mapping indication (RDI), and reflective QoS indication (RQI). In this case, the QoS information does not include QFI, RDI, and / or RQI. The QoS information is treated as service data (which may be referred to as QoS parameter information data) and mapped to a data field. In some implementations, the data field may be a data field.
[0098] Figure 8 Another exemplary diagram illustrates how QoS information is included in the RLC PDU header for transmission. In 5G NR, the RLC PDU header may include at least one of the following: a data / control (D / C) field, a polling bit (P) field, a sequence number (SN) field, a segmentation info (SI) field, a segment offset (SO) field, and / or a segment offset (SO) field. A new field (which may be referred to as QoS parameter information) is added to the RLCPDU header to provide QoS information.
[0099] In some implementations, QoS information can be carried in packet transmissions, indicating the quality requirements of the associated traffic. For example, QoS information can be transmitted in the first packet, indicating the QoS requirements, QoS parameter profiles, and / or QoS policies for subsequent consecutive data packets. When QoS information needs to be updated, new packets can carry new QoS information to indicate subsequent packets. This implementation avoids repeatedly sending the same QoS information, reduces the demand on the control plane, and / or reduces the transmission burden on the user plane. In some implementations, differential QoS information can be transmitted in packet transmissions. For example, basic QoS information can be transmitted in the first packet, and differential QoS information can be transmitted in the second packet. The complete QoS information of the second packet is obtained by aggregating the basic QoS information and the differential QoS information.
[0100] In some implementations, QoS information is transmitted as a separate data packet, and this special packet is called a QoS packet. A QoS packet contains only QoS information. In some implementations, a QoS packet has a special QoS packet header. By analyzing and inspecting QoS packets, network efficiency can be improved based on the QoS information.
[0101] In some implementations, QoS transmission in the user plane can be delivered in a structured manner. In some implementations, specific structuring methods include, but are not limited to, overall-substructure, master-slave structure, superclass and subclass structure, and / or tree structure. QoS information with an overall-substructure can include the entire QoS information description as well as a portion of specific QoS parameters and / or specific QoS policies. QoS information with a master-slave structure can include high-level QoS information, low-level QoS information, etc. QoS information with a master-slave structure can include superclass QoS information and subclass QoS information, etc. QoS information with a master-slave structure can include multi-level QoS information. QoS information with one or more QoS list structures can include some or all of the following: QoS parameter sets, QoS policy sets, QoS feature sets, QoS requirement sets, and the like. QoS information with one or more QoS list structures can be a tree structure.
[0102] In some implementations, QoS information may correspond to entities such as SDAP entities, PDCP entities, RLC entities, MAC entities, and / or QoS-related entities.
[0103] In some implementations, the QoS information mapping method may include, but is not limited to, at least one of the following: mapping to a DRB along with service data; mapping to a DRB without service data; mapping to a logical channel along with service data; mapping to a logical channel without service data; mapping to a data channel along with service data; and / or mapping to a data channel without service data. In some implementations, QoS information may be mapped to a dedicated data stream. In some implementations, QoS information may be mapped to a dedicated radio bearer. In some implementations, QoS information may be mapped to a dedicated physical channel. In some implementations, QoS information may be mapped to a dedicated logical channel. In some implementations, QoS information may be mapped to a dedicated logical channel group (LCG).
[0104] In some implementations, the QoS information mapping method can perform dynamic mapping of radio bearers, including but not limited to at least one of the following: a portion of the QoS information can be mapped to an SRB, and / or another portion of the QoS information can be mapped to a DRB.
[0105] In some implementations, QoS information can be mapped to a data transmission channel (DCH) and / or can be sent to the UE in the data channel.
[0106] In 5G NR, QoS rules are sent to the access network in NAS messages, and the access network encapsulates the QoS rules into RRC signaling and maps them to signaling bearers (SRBs). Retransmission mechanisms are not applicable to SRBs. In some implementations, QoS information transmitted over the user plane can be reliably transmitted using retransmission mechanisms such as ARQ and HARQ. In some implementations, QoS information such as QoS rules sent to the UE is transmitted as user service data on the user plane of the access network (AN), and the QoS information is mapped to a data radio bearer (DRB). In some implementations, QoS information can be transmitted over the user plane using user plane retransmission mechanisms to improve transmission success rates. For example, ARQ is used for retransmissions at the RLC layer, and HARQ can be used for retransmissions of QoS information at the physical layer. For example, QoS information can be transmitted on the user plane of the access network, and QoS information can be transmitted as transport blocks (TBs) for scheduling and resource allocation. TBs carrying QoS information can be retransmitted using HARQ.
[0107] Example 3
[0108] This disclosure describes another embodiment for transmitting Quality of Service (QoS) information over the user plane, wherein the QoS information can be transmitted over the control plane and simultaneously over the user plane to achieve a QoS system-level dual-connectivity effect. Advantages / benefits of this embodiment may include that the method can meet / achieve industry-wide high availability or reliability requirements, and / or provide reliability guarantees and redundancy. QoS information over the user plane and QoS information over the control plane are two different mechanisms. Both mechanisms provide availability / reliability similar to system-level dual-connectivity.
[0109] In some implementations, B2B has high availability requirements. For example, high availability / reliability in aviation is achieved through diversity of different technologies and systems, where equipment and services from different companies, technologies, and systems are used simultaneously. To ensure the reliability of B2B services, there can also be two sets of QoS mechanisms: (1) QoS information is transmitted and controlled on the control plane; and / or (2) QoS information is transmitted and controlled on the user plane. Using two sets of QoS mechanisms simultaneously can provide system-level diversity gain and achieve system-level dual connectivity and high reliability. For example, QoS information transmission is carried out using the control plane of manufacturer A, and simultaneously using the user plane of manufacturer B. If the QoS transmission of manufacturer A fails, manufacturer B can provide supplementary QoS information.
[0110] In some implementations, two sets of QoS mechanisms can be used to implement QoS transmission and control at different granularities. For example, semi-static QoS information is transmitted through the control plane, and dynamic real-time QoS information is transmitted through the user plane. In some implementations, coarse-grained QoS information is transmitted through the control plane, and QoS information refined based on the coarse-grained QoS information is transmitted through the user plane. In some implementations, a transmission QoS parameter set with a larger set index range is transmitted through the control plane, and a QoS parameter set with a smaller set index range is transmitted through the user plane.
[0111] In some implementations, the granularity of QoS information transmitted in the user plane can be diverse, including but not limited to at least one of the following: stream-based, PDU-based, PDU set-based, frame-based, slot-based, and packet-based. For example, for XR services, service frames of different importance correspond to different PDU sets, and PDU set-based QoS information can accurately reflect the QoS requirements of different service frames.
[0112] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure addresses the problem of configuring and / or transmitting QoS information via the user plane. The methods, apparatus, and computer-readable media described in this disclosure can improve the performance of wireless communication by configuring and / or transmitting QoS information via the user plane, thereby improving efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.
[0113] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this solution should be included or included in any single implementation thereof. Rather, references to features and advantages are to be understood as meaning that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, throughout this specification, discussions of features and advantages, and similar language, may, but do not necessarily, refer to the same embodiments.
[0114] Furthermore, the features, advantages, and characteristics described in this solution can be combined in any suitable manner in one or more embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in some embodiments, and they may not be present in all embodiments of this solution.
Claims
1. A method for wireless communication, comprising: The first network element transmits the first Quality of Service (QoS) information to the second network element in the following manner: The first network element transmits data packets to the second network element through the user, wherein the data packets include the first QoS information. The first QoS information does not include the QoS Flow Indicator (QFI), the Reflected QoS Flow to Data Radio Bearer (DRB) Mapping Indicator (RDI), and the Reflected QoS Indicator (RQI). Wherein, the first QoS information is at least one of the following: one or more Packet Detection Rules (PDR), one or more Policy Control and Charging (PCC) rules, one or more QoS profiles, one or more QoS rules, one or more QoS parameters, one or more QoS features, one or more alternative QoS profiles, one or more alternative QoS sets, one or more QoS information indices, one or more QoS parameter ranges, one or more 5G QoS identifiers (5QI), one or more QoS profile indices, one or more QoS parameter set indices, one or more QoS parameter set index ranges, one or more QoS types, or one or more QoS groups. The method further includes: the first network element transmitting second QoS information to the second network element via control.
2. The method according to claim 1, wherein: The first network element includes one of the following: core network (CN), user plane function (UPF), radio access network (RAN), service data adaptation protocol (SDAP) layer, packet data aggregation protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, central unit (CU), distributed unit (DU), application server, edge node, base station, backhaul adaptation protocol (BAP) layer, integrated access backhaul (IAB) node, or user equipment (UE).
3. The method according to claim 1, wherein: The second network element includes one of the following: core network (CN), user plane function (UPF), radio access network (RAN), service data adaptation protocol (SDAP) layer, packet data aggregation protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, central unit (CU), distributed unit (DU), application client, edge node, base station, backhaul adaptation protocol (BAP) layer, IAB node, or user equipment (UE).
4. The method according to claim 1, wherein: The user plane includes at least one of the following: User Plane Function (UPF), User Plane of Service Data Adaptation Protocol (SDAP) layer, User Plane of Packet Data Convergence Protocol (PDCP) layer, User Plane of Radio Link Control (RLC) layer, User Plane of Media Access Control (MAC) layer, User Plane of Central Unit-Distributed Unit (CU-DU) interface (F1-U), CU-User Plane (CU-UP), DU-UP, General Packet Radio Service Tunneling Protocol (GTP-U), Next Generation User Plane (NG-U), Xn User Plane (Xn-U), User Plane of QoS Flow, User Plane of CN-RAN interface, User Plane of Base Station (BS) inter-base station (BS) interface, X2-U, User Plane of Backhaul Adaptation Protocol (BAP) layer, or User Plane of Integrated Access Backhaul (IAB) node.
5. The method according to claim 1, wherein, The data packet including the first QoS information includes: The first QoS information is located in the header of the data packet; or The first QoS information is located in a predefined data area of the data packet, wherein: The first QoS information, along with other data, is transmitted in a predefined data area of the data packet, or The first QoS information is transmitted separately in the predefined data area of the data packet.
6. The method according to claim 1, wherein, The data packet including the first QoS information includes: The first QoS information is located in one of the following: PDU header, control PDU, data PDU, MAC control unit CE, PDU header field, or PDU data field.
7. The method according to claim 1, wherein: The content of the first QoS information may be different from or the same as the content of the second QoS information.
8. The method of claim 7, further comprising at least one of the following: The first QoS information is mapped to the DRB, and the second QoS information is mapped to the signaling radio bearer SRB; The first QoS information is transmitted through the user plane, and the second QoS information is transmitted through the control plane; The first QoS information is transmitted via a data stream, and the second QoS information is transmitted via a message; The first QoS information is transmitted via the data packet, and the second QoS information is transmitted via signaling; or The first QoS information is transmitted via the data packet, and the second QoS information is transmitted via the information element (IE).
9. The method according to claim 1, wherein, Transmitting the first QoS information to the second network element includes at least one of the following: The first QoS information is transmitted to the second network element in each packet; The first QoS information is transmitted to the second network element in the first packet; The first QoS information is transmitted as an independent data packet to the second network element; The first QoS information is transmitted to the second network element in a periodic manner within the packet; The first QoS information is transmitted to the second network element in a non-periodic manner within the packet; The first QoS information is transmitted to the second network element in an overall-sub-QoS manner; The first QoS information is transmitted to the second network element in a differential QoS manner; The first QoS information is transmitted to the second network element in a primary-secondary QoS manner; or The first QoS information is transmitted to the second network element in the form of one or more QoS lists.
10. The method according to claim 1, wherein, Transmitting the first QoS information to the second network element includes: The first network element maps the first QoS information into data stream data; and The first QoS information is transmitted to the second network element as the data stream.
11. The method of claim 10, wherein: The data stream is a shared data stream used for QoS information and service data; or The data stream is a dedicated data stream used for QoS information.
12. The method according to claim 1, wherein: The first QoS information corresponds to an entity, wherein the entity includes at least one of the following: Service Data Adaptation Protocol (SDAP) entity, Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, QoS-related entity, Backhaul Adaptation Protocol (BAP) entity, or Integrated Access Backhaul (IAB) entity.
13. The method according to claim 1, wherein: The mapping method for the first QoS information includes at least one of the following: The first QoS information is mapped together with the service data to a shared data radio bearer (DRB); Map the first QoS information to a dedicated DRB that does not contain service data; Map the first QoS information to a dedicated QoS radio bearer; The first QoS information is mapped together with the service data to a shared logical channel (LC). The first QoS information is mapped to a dedicated logical channel (LC) that does not contain service data. The first QoS information is mapped together with the service data to a shared logical channel group (LCG); The first QoS information is mapped to a dedicated logical channel group (LCG) that does not contain service data. The first QoS information is mapped together with the service data to a shared data channel; or The first QoS information is mapped to a dedicated data channel that does not contain service data.
14. The method according to claim 1, wherein: The first QoS information is mapped to a data channel and transmitted to the second network element through the data channel.
15. The method according to claim 1, further comprising: The first network element performs the retransmission of the data packet including the first QoS information to the second network element through the user, wherein the retransmission includes one of the following: Automatic Repeat Request (ARQ) retransmission mechanism or Hybrid Automatic Repeat Request (HARQ) retransmission mechanism.
16. The method according to claim 1, wherein: The first QoS information is transmitted to the second network element through the user plane at a granular level, wherein the granular level includes at least one of the following: based on each flow, based on each PDU, based on each PDU set, based on each frame, based on each packet, based on each TB, based on each DRB, based on each LC, based on each LCG, based on each physical channel, and based on each time slot.
17. The method according to claim 1, wherein: The first QoS information includes at least one of the following: overall QoS information, sub-QoS information, hierarchical QoS information, QoS information with different priorities, or QoS information in a tree structure.
18. The method according to claim 1, wherein: The first QoS information is generated by the third network element, and The first network element is connected to the third network element to obtain the first QoS information.
19. The method of claim 18, wherein: The third network element includes one of the following: QoS information generation unit, application server, PCF, QoS controller, CN, RAN, or UE.
20. A method for wireless communication, comprising: The second network element receives the first Quality of Service (QoS) information from the first network element in the following manner: The second network element receives data packets from the first network element through the user plane, wherein the data packets include the first QoS information. The first QoS information does not include the QoS Flow Indicator (QFI), the Reflected QoS Flow to Data Radio Bearer (DRB) Mapping Indicator (RDI), and the Reflected QoS Indicator (RQI). Wherein, the first QoS information is at least one of the following: one or more Packet Detection Rules (PDR), one or more Policy Control and Charging (PCC) rules, one or more QoS profiles, one or more QoS rules, one or more QoS parameters, one or more QoS features, one or more alternative QoS profiles, one or more alternative QoS sets, one or more QoS information indices, one or more QoS parameter ranges, one or more 5G QoS identifiers (5QI), one or more QoS profile indices, one or more QoS parameter set indices, one or more QoS parameter set index ranges, one or more QoS types, or one or more QoS groups. The method further includes: the second network element receiving second QoS information from the first network element through the control plane.
21. The method of claim 20, wherein: The first network element includes one of the following: core network (CN), user plane function (UPF), radio access network (RAN), service data adaptation protocol (SDAP) layer, packet data aggregation protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, central unit (CU), distributed unit (DU), application server, edge node, base station, backhaul adaptation protocol (BAP) layer, integrated access backhaul (IAB) node, or user equipment (UE).
22. The method of claim 20, wherein: The second network element includes one of the following: core network (CN), user plane function (UPF), radio access network (RAN), service data adaptation protocol (SDAP) layer, packet data aggregation protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, central unit (CU), distributed unit (DU), application client, edge node, base station, backhaul adaptation protocol (BAP) layer, IAB node, or user equipment (UE).
23. The method of claim 20, wherein: The user plane includes at least one of the following: User Plane Function (UPF), User Plane of Service Data Adaptation Protocol (SDAP) layer, User Plane of Packet Data Convergence Protocol (PDCP) layer, User Plane of Radio Link Control (RLC) layer, User Plane of Media Access Control (MAC) layer, User Plane of Central Unit-Distributed Unit (CU-DU) interface (F1-U), CU-User Plane (CU-UP), DU-UP, General Packet Radio Service Tunneling Protocol (GTP-U), Next Generation User Plane (NG-U), Xn User Plane (Xn-U), User Plane of QoS Flow, User Plane of CN-RAN interface, User Plane of Base Station (BS) inter-base station (BS) interface, X2-U, User Plane of Backhaul Adaptation Protocol (BAP) layer, or User Plane of Integrated Access Backhaul (IAB) node.
24. The method of claim 20, wherein, The data packet including the first QoS information includes: The first QoS information is located in the header of the data packet; or The first QoS information is located in a predefined data area of the data packet, wherein: The first QoS information, along with other data, is transmitted in a predefined data area of the data packet, or The first QoS information is transmitted separately in the predefined data area of the data packet.
25. The method according to claim 20, wherein, The data packet including the first QoS information includes: The first QoS information is located in one of the following: PDU header, control PDU, data PDU, MAC control unit CE, PDU header field, or PDU data field.
26. The method of claim 20, wherein: The content of the first QoS information may be different from or the same as the content of the second QoS information.
27. The method of claim 26, further comprising at least one of the following: The first QoS information is mapped to the DRB, and the second QoS information is mapped to the signaling radio bearer SRB; The first QoS information is transmitted through the user plane, and the second QoS information is transmitted through the control plane; The first QoS information is transmitted via a data stream, and the second QoS information is transmitted via a message; The first QoS information is transmitted via the data packet, and the second QoS information is transmitted via signaling; or The first QoS information is transmitted via the data packet, and the second QoS information is transmitted via the information element (IE).
28. The method according to claim 20, wherein, Transmitting the first QoS information to the second network element includes at least one of the following: The first QoS information is transmitted to the second network element in each packet; The first QoS information is transmitted to the second network element in the first packet; The first QoS information is transmitted as an independent data packet to the second network element; The first QoS information is transmitted to the second network element in a periodic manner within the packet; The first QoS information is transmitted to the second network element in a non-periodic manner within the packet; The first QoS information is transmitted to the second network element in an overall-sub-QoS manner; The first QoS information is transmitted to the second network element in a differential QoS manner; The first QoS information is transmitted to the second network element in a primary-secondary QoS manner; or The first QoS information is transmitted to the second network element in the form of one or more QoS lists.
29. The method according to claim 20, wherein, Transmitting the first QoS information to the second network element includes: The first network element maps the first QoS information into data stream data; and The first QoS information is transmitted to the second network element as the data stream.
30. The method according to claim 29, wherein: The data stream is a shared data stream used for QoS information and service data; or The data stream is a dedicated data stream used for QoS information.
31. The method of claim 20, wherein: The first QoS information corresponds to an entity, wherein the entity includes at least one of the following: Service Data Adaptation Protocol (SDAP) entity, Packet Data Convergence Protocol (PDCP) entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, QoS-related entity, Backhaul Adaptation Protocol (BAP) entity, or Integrated Access Backhaul (IAB) entity.
32. The method of claim 20, wherein: The mapping method for the first QoS information includes at least one of the following: The first QoS information is mapped together with the service data to a shared data radio bearer (DRB); Map the first QoS information to a dedicated DRB that does not contain service data; Map the first QoS information to a dedicated QoS radio bearer; The first QoS information is mapped together with the service data to a shared logical channel (LC). The first QoS information is mapped to a dedicated logical channel (LC) that does not contain service data. The first QoS information is mapped together with the service data to a shared logical channel group (LCG); The first QoS information is mapped to a dedicated logical channel group (LCG) that does not contain service data. The first QoS information is mapped together with the service data to a shared data channel; or The first QoS information is mapped to a dedicated data channel that does not contain service data.
33. The method of claim 20, wherein: The first QoS information is mapped to a data channel and transmitted to the second network element through the data channel.
34. The method of claim 20, further comprising: The first network element performs the retransmission of the data packet including the first QoS information to the second network element through the user, wherein the retransmission includes one of the following: Automatic Repeat Request (ARQ) retransmission mechanism or Hybrid Automatic Repeat Request (HARQ) retransmission mechanism.
35. The method of claim 20, wherein: The first QoS information is transmitted to the second network element through the user plane at a granular level, wherein the granular level includes at least one of the following: based on each flow, based on each PDU, based on each PDU set, based on each frame, based on each packet, based on each TB, based on each DRB, based on each LC, based on each LCG, based on each physical channel, and based on each time slot.
36. The method of claim 20, wherein: The first QoS information includes at least one of the following: overall QoS information, sub-QoS information, hierarchical QoS information, QoS information with different priorities, or QoS information in a tree structure.
37. The method of claim 20, wherein: The first QoS information is generated by the third network element, and The first network element is connected to the third network element to obtain the first QoS information.
38. The method of claim 37, wherein: The third network element includes one of the following: QoS information generation unit, application server, PCF, QoS controller, CN, RAN, or UE.
39. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any one of claims 1 to 38.
40. A computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code causing the processor to perform the method of any one of claims 1 to 38 when executed by a processor.
Citation Information
Patent Citations
Data transmission method and apparatus
US20190327635A1
