Qos flow mapping for multiplexed media streams

Abstract

This disclosure relates to an apparatus, UE, and method for supporting QoS stream mapping for multiplexed media streams. In one aspect, a first apparatus acquires a protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection. The protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream. The first apparatus then determines QoS stream identifiers (QFIs) for the QoS streams, wherein each QFI is associated with a media stream within the media stream. Furthermore, the first apparatus provides a second apparatus or UE with second information regarding the QFIs, the multiplexing identification information, and the mapping between the plurality of QoS parameter sets.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to apparatus and methods for quality of service (QoS) stream mapping for multiplexed media streams. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] There are instances where multiple different media streams for extended reality (XR) services can be multiplexed over a single transport layer connection that shares the same Internet Protocol (IP) 5-tuple with the transport protocol, and each media stream can have its own Quality of Service (QoS) requirements. The transport protocol multiplexes different data streams from the application to use the same IP 5-tuple. For example, virtual reality (VR) or augmented reality (AR) applications may use multiple streams within a single session for their different service profiles and purposes: one stream for signaling, one for control, one for audio, and one or more for video. These streams share the same connection while having different QoS requirements or parameters.

[0004] However, for the current 5GS QoS framework, when a service data stream is mapped to a QoS stream, there is only one set of QoS parameters, and it does not support differentiated QoS processing within a QoS stream. Summary of the Invention

[0005] This disclosure relates to apparatus, UE, and method for supporting QoS stream mapping for multiplexed media streams. Through this apparatus, UE, and method, a second apparatus or UE can identify multiplexed media streams with different QoS requirements within a single transport layer connection. The second apparatus or UE can then perform QoS stream mapping for the media streams with different QoS requirements.

[0006] Some implementations of the first apparatus described herein may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the first apparatus to: acquire protocol description and multiplexing identification information associated with a plurality of Quality of Service (QoS) parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream; determine QoS Stream Identifiers (QFIs) for the QoS streams, wherein each QFI is associated with a media stream in the media stream; and provide a second apparatus or User Equipment (UE) with second information regarding the QFIs, the multiplexing identification information, and the mapping between the plurality of QoS parameter sets.

[0007] In some implementations, the multiplexing identification information includes at least one of the following: the identifier of the transport layer connection, or the identifier of the media stream.

[0008] In some implementations, at least one processor is also configured to cause the first device to provide the second device with: a protocol description and a first instruction indicating that the second device obtains multiplexing identification information from data packets.

[0009] In some implementations, a single transport layer connection includes a connection based on the Fast User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description also includes third-party information about the QUIC protocol.

[0010] In some implementations, at least one processor is also configured to cause the first device to provide a second indication to a radio access network (RAN) node, the second indication indicating that a QoS flow is associated with a single transport layer connection.

[0011] In some implementations, at least one processor is further configured to cause the first means to: acquire QoS parameters of a set of alternative Protocol Data Units (PDUs) for a media stream; and provide at least one alternative QoS profile to a Radio Access Network (RAN) node, wherein each of the at least one alternative QoS profile includes at least the QoS parameters of the set of alternative PDUs.

[0012] In some implementations, at least one alternative QoS profile includes at least one dedicated alternative QoS profile.

[0013] In some implementations, at least one dedicated alternative QoS profile includes: a first dedicated alternative QoS profile for uplink (UL) and a second dedicated alternative QoS profile for downlink (DL). In some implementations, the first dedicated alternative QoS profile for UL includes at least one of the following: UL PDU set delay budget (PSDB), UL PDU set error rate (PSER), or UL PDU set integrated processing information (PSIHI). In some implementations, the second dedicated alternative QoS profile for DL ​​includes at least one of the following: DL PSDB, DL PSER, or DL ​​PSIHI.

[0014] In some implementations, the first dedicated alternative QoS profile for UL also includes UL Guaranteed Stream Bit Rate (GFBR), and the second dedicated alternative QoS profile for DL ​​also includes DL GFBR.

[0015] In some implementations, each of the at least one dedicated alternative QoS profiles includes at least one of the following: PDU error rate (PER), PDU delay budget (PDB), UL guaranteed stream bit rate (GFBR), DL GFBR, average window, maximum data burst volume (MDBV), ULPDU set delay budget (PSDB), UL PDU set error rate (PSER), ULPDU set integrated processing information (PSIHI), DL PSDB, DL PSER, or DL ​​PSIHI.

[0016] In some implementations, at least one processor is also configured to enable the first device to provide the RAN node with a priority list of at least one alternative QoS profile.

[0017] In some implementations, at least one processor is further configured to cause the first device to: provide a third indication to the RAN node, wherein the third indication indicates that: if the QoS profile is not satisfied, the RAN node provides the first device with fourth information regarding at least one QoS parameter of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0018] In some implementations, at least one processor is further configured to cause the first device to obtain from the RAN node at least one of the following: a fourth indication indicating that the QoS profile is not satisfied; a sixth indication indicating that the QoS parameters of the PDU set included in the QoS profile are not satisfied; or fourth information regarding at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0019] In some implementations, the fourth information regarding at least one of the candidate PDU set QoS parameters among the satisfied candidate PDU set QoS parameters includes at least one of the following: an index of a candidate QoS profile that includes at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters, or a fifth indication of at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters.

[0020] In some implementations, at least one processor is further configured to cause the first device to provide the third device with at least one of the following: a fourth indication indicating that the QoS profile is not satisfied, or fourth information regarding at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0021] Some implementations of the second apparatus described herein may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured such that the second apparatus: obtains from the first apparatus: a protocol description, wherein the protocol description includes first information regarding the location of obtaining multiplexing identification information from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection; second information regarding the mapping between QFI, the multiplexing identification information, and a plurality of QoS parameter sets for the media stream; and a first indication indicating that the second apparatus obtains the multiplexing identification information from the data packets; obtains the multiplexing identification information from the data packets based on the protocol description and the first indication; and maps the media stream to a QoS stream identified by the QFI based on the multiplexing identification information and the second information regarding the mapping.

[0022] In some implementations, the multiplexing identification information includes at least one of the following: the identifier of the transport layer connection, or the identifier of the media stream.

[0023] In some implementations, a single transport layer connection includes a connection based on the Fast User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description also includes third-party information about the QUIC protocol.

[0024] In some implementations, at least one processor is configured such that the second device obtains multiplexing identification information from the data packet by: obtaining multiplexing identification information from one of the following: the plaintext portion of the data packet based on the Fast User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) header of the data packet, or an RTP header extension for the data packet based on the Real-Time Transport Protocol (RTP) protocol.

[0025] Some implementations of the UE described herein may include a processor and a transceiver coupled to the processor. The processor is configured to: via the transceiver, acquire: second information regarding a QFI for a QoS stream, multiplexing identification information for identifying media streams, and a mapping between multiple sets of QoS parameters, wherein each QFI is associated with a media stream carried in uplink data packets and multiplexed over a single transport layer connection; and map the media streams to QoS streams based on the second information regarding the mapping.

[0026] In some implementations, the processor is further configured to: obtain a protocol description from a first device, wherein the protocol description includes first information regarding the location of obtaining multiplexing identification information from uplink data packets. In such an implementation, the processor is configured to: map a media stream to a QoS stream based on the protocol description and second information regarding the mapping.

[0027] In some implementations, the multiplexing identification information includes at least one of the following: the identifier of the transport layer connection, or the identifier of the media stream.

[0028] In some implementations, a single transport layer connection includes a connection based on the Fast User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description also includes third-party information about the QUIC protocol.

[0029] Some implementations of the third device described herein may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured such that the third device: provides a first device with protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream.

[0030] In some implementations, at least one processor is also configured to enable a third device to provide the first device with alternative Protocol Data Unit (PDU) set Quality of Service (QoS) parameters.

[0031] In some implementations, at least one processor is further configured to cause a third device to: provide a third instruction to the first device, wherein the third instruction indicates that: if the QoS profile is not satisfied, the radio access network (RAN) node provides the first device with fourth information regarding at least one QoS parameter of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0032] In some implementations, at least one processor is further configured to cause a third device to obtain from the first device at least one of the following: a fourth indication indicating that a QoS profile is not satisfied, or fourth information regarding at least one of the QoS parameters of a set of candidate PDUs that is satisfied.

[0033] In some implementations, the fourth information regarding at least one of the candidate PDU set QoS parameters among the satisfied candidate PDU set QoS parameters includes at least one of the following: an index of a candidate QoS profile that includes at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters, or a fifth indication of at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters.

[0034] In some implementations, at least one processor is further configured to cause the third device to provide the fourth device with at least one of the following: a fourth indication indicating that the QoS profile is not satisfied, or fourth information regarding at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0035] Some implementations of the RAN node described herein may include a processor and a transceiver coupled to the processor. The processor is configured to: obtain at least one alternative QoS profile from a first device via the transceiver, wherein each of the at least one alternative QoS profile includes at least: a set of alternative Protocol Data Units (PDUs) QoS parameters for a media stream.

[0036] In some implementations, at least one alternative QoS profile includes at least one dedicated alternative QoS profile, which includes at least a set of PDU QoS parameters.

[0037] In some implementations, at least one dedicated alternative QoS profile includes: a first dedicated alternative QoS profile for uplink (UL) and a second dedicated alternative QoS profile for downlink (DL).

[0038] In some implementations, the first dedicated alternative QoS profile for UL includes at least one of the following: UL PDU set delay budget (PSDB), UL PDU set error rate (PSER), or UL PDU set integrated processing information (PSIHI).

[0039] In some implementations, the second dedicated alternative QoS profile for DL ​​includes at least one of the following: DL PSDB, DL PSER, or DL ​​PSIHI.

[0040] In some implementations, the first dedicated alternative QoS profile for UL also includes UL Guaranteed Stream Bit Rate (GFBR), and the second dedicated alternative QoS profile for DL ​​also includes DL GFBR.

[0041] In some implementations, each of the at least one dedicated alternative QoS profiles includes at least one of the following: PDU error rate (PER), PDU delay budget (PDB), UL guaranteed stream bit rate (GFBR), DL GFBR, average window, maximum data burst volume (MDBV), ULPDU set delay budget (PSDB), UL PDU set error rate (PSER), ULPDU set integrated processing information (PSIHI), DL PSDB, DL PSER, or DL ​​PSIHI.

[0042] In some implementations, at least one processor is also configured to obtain a priority list of at least one alternative QoS profile from the first device.

[0043] In some implementations, at least one processor is further configured to: obtain a third indication from the first device via a transceiver, wherein the third indication indicates that: if the QoS profile is not satisfied, the RAN node provides the first device with fourth information regarding at least one QoS parameter of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0044] In some implementations, at least one processor is further configured to provide the first device with at least one of the following: a fourth indication indicating that a QoS profile is not satisfied; a sixth indication indicating that a QoS parameter of a PDU set included in a QoS profile is not satisfied; or fourth information regarding at least one of the satisfied QoS parameters of a PDU set.

[0045] In some implementations, at least one processor is also configured to provide the source RAN node with at least one of the following: a fourth indication indicating that the QoS profile is not satisfied, or fourth information regarding at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0046] In some implementations, the fourth information regarding at least one of the satisfied PDU set QoS parameters includes at least one of the following: an index of a candidate QoS profile, which includes at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters, or a fifth indication of at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters.

[0047] Some implementations of the method described herein may include: acquiring protocol description and multiplexing identification information associated with multiple sets of QoS parameters for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream; determining QFIs for the QoS stream, wherein each QFI is associated with a media stream in the media stream; and providing a second device or UE with second information about the QFIs, the multiplexing identification information, and the mapping between the multiple sets of QoS parameters.

[0048] Some implementations of the method described herein may include: obtaining from a first device the following: a protocol description, wherein the protocol description includes first information regarding the location of obtaining multiplexing identification information from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection; second information regarding the mapping between QFI, the multiplexing identification information, and a plurality of QoS parameter sets for the media stream; and a first indication indicating that the second device obtains the multiplexing identification information from the data packets; obtaining the multiplexing identification information from the data packets based on the protocol description and the first indication; and mapping the media stream to a QoS stream identified by the QFI based on the multiplexing identification information and the second information regarding the mapping.

[0049] Some implementations of the method described herein may include: obtaining: second information regarding the QFI for a QoS stream, multiplexing identification information for identifying media streams, and mappings between multiple sets of QoS parameters, wherein each QFI is associated with a media stream carried in uplink data packets and multiplexed over a single transport layer connection; and mapping the media streams to QoS streams based on the second information regarding the mappings.

[0050] Some implementations of the method described herein may include providing a first device with a protocol description and multiplexing identification information associated with a plurality of Quality of Service (QoS) parameters for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream.

[0051] Some implementations of the method described herein may include: obtaining at least one alternative QoS profile from a first device, wherein each alternative QoS profile in the at least one alternative QoS profile includes at least: QoS parameters for an alternative set of PDUs for a media stream.

[0052] It should be understood that the summary portion of this invention is not intended to identify key or essential features of the implementation of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0053] Figure 1A and Figure 1B Examples of wireless communication systems supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure are shown respectively;

[0054] Figure 2 and Figure 3 Signaling diagrams illustrating example procedures for supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure are shown respectively;

[0055] Figure 4 A signaling diagram illustrating an example process for supporting enhanced alternative QoS profiles according to aspects of this disclosure is shown;

[0056] Figure 5 Examples of devices supporting QoS stream mapping or enhanced alternative QoS profiles for multiplexed media streams are shown, according to some aspects of this disclosure.

[0057] Figure 6 Examples of processors that support QoS stream mapping or enhanced alternative QoS profiles for multiplexed media streams, according to other aspects of this disclosure, are shown.

[0058] Figure 7 , 8 Figures 9, 10, and 11 respectively illustrate flowcharts of methods supporting QoS stream mapping for multiplexed media streams according to other aspects of this disclosure. Detailed Implementation

[0059] The principles of this disclosure will now be described with reference to some implementations. It should be understood that these implementations are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0060] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0061] References to “an implementation,” “example implementation,” “implementation,” “some implementations,” etc., in this disclosure indicate that the implementation(s) described may include a particular feature, structure, or characteristic, but not every implementation is necessarily required to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same implementation(s). Moreover, when a particular feature, structure, or characteristic is described in conjunction with an implementation, those skilled in the art will consider that, in conjunction with other implementations (whether explicitly described or not), such feature, structure, or characteristic may affect such feature, structure, or characteristic within the scope of their knowledge.

[0062] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0063] The terminology used herein is for the purpose of describing a particular implementation only and is not intended to limit the example implementation. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” as used herein specify the presence of the stated feature, element, and / or component, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0064] As mentioned above, for the current 5GS QoS framework, when a service data stream is mapped to a QoS stream, there is only one set of QoS parameters, and differentiated QoS processing within a QoS stream is not supported. Therefore, for multiple media streams multiplexed on a single transport layer connection that share the same IP 5-tuple and have different QoS requirements or parameters, it is important to first distinguish and identify each media stream in the media stream, and then apply the QoS stream mapping to each stream with different QoS requirements or parameters.

[0065] In view of the above, the present disclosure provides a solution supporting QoS stream mapping for multiplexed media streams. In one aspect of this solution, a first device acquires protocol description and multiplexing identification information associated with multiple sets of QoS parameters for a media stream carried in data packets and multiplexed over a single transport layer connection. The protocol description includes first information about the location where the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream. The first device then determines a QoS stream identifier (QFI) for the QoS stream, wherein each QFI is associated with a media stream within the media stream. Furthermore, the first device provides a second device or UE with the following: second information regarding the QFIs, the multiplexing identification information, and the mapping between the multiple sets of QoS parameters. Through this solution, the second device or UE can identify multiplexed media streams with different QoS requirements within a single transport layer connection.

[0066] The aspects of this disclosure are described in the context of wireless communication systems.

[0067] Figure 1A An example of a wireless communication system 100A supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. The wireless communication system 100A may include one or more network entities 102 (also referred to as network devices (NEs)), one or more terminal devices or UEs 104, a core network 106, and a data network (DN) 108. The wireless communication system 100A may support various radio access technologies. In some implementations, the wireless communication system 100A may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100A may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100A may support radio access technologies other than 5G. In addition, the wireless communication system 100A can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0068] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100A. One or more network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. In the following, some implementations of this disclosure will be described by using RAN nodes as examples of network entities 102. Therefore, network entity 102 may be used interchangeably with RAN node 102. For example, RAN node 102 may include RAN node 102-1 and RAN node 102-2.

[0069] Network entity 102 and UE 104 can communicate via communication link 110, which can be a wireless connection or a wired connection. For example, network entity 102 and UE 104 can perform wireless communication (e.g., receive signaling, send signaling) through the Uu interface.

[0070] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0071] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100A. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100A. In some other implementations, UE 104 may be mobile within the wireless communication system 100A.

[0072] One or more UEs 104 can be devices of different forms or with different capabilities. Examples of some UEs 104 are shown in Figure 1. As shown in Figure 1, UE 104 can be able to communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UEs 104, which can act as relays in the wireless communication system 100A.

[0073] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0074] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0075] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0076] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0077] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0078] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, and RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0079] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, which are supported by corresponding network entities 102 communicating via such communication links.

[0080] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), and may include one or more core network elements 103. Core network elements 103 may be control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)), and user plane entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0081] Core network 106 can communicate with data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0082] In the wireless communication system 100A, network entity 102 and UE 104 can use the resources of the wireless communication system 100A (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0083] The wireless communication system 100A may support one or more digital technologies, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0084] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0085] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100A. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ=4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that for the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0086] In the wireless communication system 100A, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100A can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0087] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ=2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0088] Figure 1B An example of a wireless communication system 100B supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Specifically, Figure 1B As shown Figure 1A The network entities or network functions (NFs) in the core network 106 shown.

[0089] like Figure 1B As shown, the core network 106 may include at least: Session Management Function (SMF) 120, User Plane Function (UPF) 130, Policy Control Function (PCF) 140, Network Open Function (NEF) 150, Application Function (AF) 160, and Access and Mobility Management Function (AMF) 170.

[0090] In some implementations, the AMF 170 can communicate with RAN node 102 and SMF 120 via the N2 interface and the N11 interface, respectively.

[0091] In some implementations, the SMF 120 can communicate with the UPF 130 and PCF 140 via the N4 and N7 interfaces, respectively.

[0092] In some implementations, UPF 130 can communicate with RAN node 102 and DN 108 via the N3 interface and N6 interface, respectively. In some implementations, UPF 130 may include a PDU Session Anchor Point (PSA) UPF.

[0093] In some implementations, the core network 106 may include more than one UPF. In such an implementation, one UPF can communicate with another UPF via the N9 interface.

[0094] In some implementations, the NEF 150 can communicate with the PCF 140 and AF 160 via the N30 and N33 interfaces, respectively.

[0095] Figure 2 A signaling diagram illustrating an example process 200 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Process 200 may involve Figure 1A Or RAN node 102 in 1B Figure 1B The NEF 150, AF 160, and DN 108 are mentioned. Process 200 may also involve a first device, a second device, and a third device. In some implementations, the first device can perform... Figure 1BThe SMF 120 in the middle. Alternatively, the first device can perform, in addition to Figure 1B In addition to the SMF 120, other network functions are included. In some implementations, the second device can perform... Figure 1B UPF 130. Alternatively, the second device can perform other functions besides... Figure 1B In addition to the UPF 130, other network functions are included. In some implementations, a third device can perform... Figure 1B The PCF140 in the middle. Alternatively, a third device can perform, in addition to... Figure 1B Other network functions besides PCF 140. For discussion purposes, references will be made to... Figure 1B Describe process 200. Process 200 may involve... Figure 1B The RAN nodes are 102, UPF 130, SMF 120, PCF 140, NEF 150, AF 160, and DN 108.

[0096] like Figure 2 As shown, the AF 160 can provide the NEF 150 with 210 protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters for a media stream. The media stream is carried in data packets and multiplexed over a single transport layer connection. The protocol description includes initial information about where the multiplexing identification information is obtained from the data packets. The multiplexing identification information is used to identify the media stream.

[0097] In some implementations, a single transport layer connection may include a connection based on the Fast User Datagram Protocol (UDP) Internet Connection (QUIC) protocol. In such implementations, the protocol description may indicate that multiplexing identification information is obtained from the plaintext portion of a QUIC-based data packet or from the General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) header of the data packet.

[0098] In some implementations, a single transport layer connection may include a connection based on the Real-Time Transport Protocol (RTP). In such implementations, the protocol description may indicate that multiplexing identification information is obtained from the RTP header extension for RTP-based data packets.

[0099] In some implementations, the protocol description may also indicate the transport protocol used by the business data stream or media stream (e.g., RTP, Secure Real-Time Transport Protocol (SRTP)), transport protocol header extensions (e.g., the RTP header extension for PDU set marking as defined in TS 26.522), payload type and format (e.g., H.264 or H.265), and format parameters (e.g., H.264 profile level and packetization mode).

[0100] In some implementations, the multiplexing identification information may include at least one of the following: the identifier (ID) of the transport layer connection, or the ID of the media stream. For example, if a single transport layer connection may include a QUIC-based connection, the ID of the transport layer connection may include a connection ID, and the ID of the media stream may include a stream ID.

[0101] In some implementations, a connection ID is typically used to identify a QUIC connection between communication endpoints. For the encrypted data portion, when the frame type is set to stream, it means that application data is sent via the QUIC connection. A stream refers to a unidirectional or bidirectional channel within a QUIC connection used for sequential bytes. A QUIC connection can carry multiple media streams simultaneously.

[0102] In some implementations, a stream ID can be used to distinguish multiple streams within the same QUIC connection (with the same connection ID). When a stream ID is generated, it is guaranteed to be unique and exclusive within that QUIC connection. That is, the stream ID is unique across all streams within the connection and can be used accordingly to detect and identify different multiplexed media streams. For the QUIC protocol, connection IDs and stream IDs can be combined or used individually to uniquely identify media streams within a multiplexed media stream.

[0103] In the following sections, some examples of this disclosure will be described using connection ID and stream ID as examples of multiplexing identification information. It should be understood that multiplexing identification information may include any appropriate information used to identify media streams based on the transport layer protocol applied to this disclosure.

[0104] In some implementations, AF 160 can provide multiplexing identification information associated with multiple QoS parameter sets. In other words, AF 160 can provide a mapping between multiplexing identification information and multiple QoS parameter sets.

[0105] For example, the mapping between reused identification information and multiple QoS parameter sets can include: connection ID#X1 + flow ID#Y1 >>> QoS parameter set #1, connection ID#X2 + flow ID#Y2 >>> QoS parameter set #2.

[0106] For example, the mapping between reused identification information and multiple QoS parameter sets can include: Flow ID#X1>>>QoS parameter set #1, Flow ID#X2>>>QoS parameter set #2.

[0107] In some implementations, the AF 160 can also provide the NEF 150 with a flow description of the AF session and multiplexing identification information associated with multiple sets of QoS parameters. In such implementations, the flow description can be a set of packet filters that includes direction, source and destination IP addresses, protocol, source and destination port numbers, etc. For example, the packet filter set can be an IP packet filter set or an Ethernet packet filter set. Alternatively, the flow description can be an application identifier (i.e., AppID).

[0108] In some implementations, different media streams can have different forward error correction (FEC) ratios associated with PDU set importance (PSI) values ​​to facilitate potential PDU set drop at RAN node 102. Therefore, in addition to the mapping between multiplexing identification information and multiple QoS parameter sets, AF 160 can also provide NEF 150 with a mapping between multiplexing identification information and FEC ratios. For example, the mapping between multiplexing identification information, FEC ratios, and PDU set QoS parameters could include: Connection ID#X1 + Stream ID#Y1 >>> PSI value #1 >> FEC ratio X%.

[0109] In some implementations, different media streams can have different PDU set QoS parameters. Therefore, in addition to the mapping between multiplexing identification information and multiple QoS parameter sets, the AF 160 can also provide the NEF 150 with a mapping between multiplexing identification information and PDU set QoS parameters. For example, the mapping between multiplexing identification information and PDU set QoS parameters can include: Connection ID#X1 + Stream ID#Y1 >>> PDU set QoS parameter #1.

[0110] It should be noted that for FEC ratios associated with PSI values, the PDU set importance list can be associated with the same FEC ratio X%, or the PDU set importance list can be associated with different FEC ratios. For example, PSI value #1 is associated with FEC ratio > X%, PSI value #2 is associated with FEC ratio Y%, PSI value #3 is associated with FEC ratio Z%, and so on.

[0111] In some implementations, the AF 160 can send an Nnef_AFsessionWithQoS_Create message to the NEF 150. The Nnef_AFsessionWithQoS_Create message may include protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters.

[0112] In some implementations, the Nnef_AFsessionWithQoS_Create message may also include other information or parameters as described above.

[0113] Upon receiving the Nnef_AFsessionWithQoS_Create message, NEF 150 grants AF requests for AF sessions with the required QoS parameters and can apply policies to control the total amount of QoS granted to AF 160. If the grant is not granted, NEF 150 replies to AF 160 with a Result value indicating grant failure. Alternatively, in the case of a trusted AF, AF 160 can directly provide these parameters to PCF 140 without the involvement of NEF 150.

[0114] After successful authorization, the NEF 150 can provide the PCF 140 with 220 protocol descriptions and multiplexing identification information associated with multiple QoS parameter sets.

[0115] In some implementations, the NEF 150 can also provide flow descriptions to the PCF 140.

[0116] In some implementations, the NEF 150 can also provide the PCF 140 with a mapping between multiplexing identification information and FEC ratio.

[0117] In some implementations, the NEF 150 can also provide the PCF 140 with a mapping between multiplexing identification information and PDU set QoS parameters.

[0118] In some implementations, the NEF 150 can send an Npcf_PolicyAuthorization_Create message to the PCF 140. The Npcf_PolicyAuthorization_Create message can include protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters.

[0119] In some implementations, the Npcf_PolicyAuthorization_Create message may also include other information or parameters as described above.

[0120] Alternatively, the PCF 140 can obtain the above information or parameters based on the operator's local configuration.

[0121] Then, PCF 140 can provide SMF 120 with 225 protocol descriptions and multiplexing identification information associated with multiple QoS parameter sets.

[0122] In some implementations, the PCF 140 can also provide a flow description to the SMF 120.

[0123] In some implementations, PCF 140 can also provide SMF 120 with a mapping between multiplexing identification information and FEC ratio.

[0124] In some implementations, the PCF 140 can also provide the SMF 120 with a mapping between multiplexing identification information and PDU set QoS parameters.

[0125] In some implementations, the PCF 140 can generate Policy and Charging Control (PCC) rules and send these rules to the SMF 120. The PCC rules may include protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters.

[0126] In some implementations, PCC rules may also include other information or parameters as described above.

[0127] Alternatively, the SMF 120 can be pre-configured with protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters.

[0128] In some implementations, the SMF 120 may also be pre-configured with other information or parameters as described above.

[0129] Furthermore, SMF 120 determines 230 QFIs for QoS streams. Each QFI is associated with a media stream within the media stream.

[0130] In some implementations, the SMF 120 can perform PCC rule binding to a QoS flow based on multiple sets of QoS parameters, according to the PCC rules from the PCF 140. The SMF 120 can assign a QFI to a new QoS flow and derive its QoS profile, corresponding UPF directives (including packet detection rules), and at least one QoS rule from at least one PCC rule bound to that QoS flow and other information provided by the PCF 140.

[0131] Then, SMF 120 provides UPF 130 with the following items: a protocol description; second information regarding QFI, multiplexing identification information, and mappings between multiple QoS parameter sets; and a first indication that specifies that UPF 130 obtains multiplexing identification information from data packets.

[0132] In some implementations, the second information regarding the mapping between QFI, multiplexing identification information, and multiple QoS parameter sets may include the following: QFI#1 --- Connection ID #X1 + Stream ID #Y1 --- QoS parameter set #1, and QFI#2---Connection ID #X2+Stream ID#Y2---QoS parameter set #2.

[0133] In some implementations, the SMF 120 can send a PDR to the UPF 130. The PDR may include a first indication and second information about the mapping. The PDR may include the DL and UL portions of the Service Data Flow (SDF) template.

[0134] In some implementations, the SMF 120 can also send an indication to the UPF 130 in the QoS Enforcement Rule (QER) to indicate the multiplexing information identifier to the UPF 130. Upon receiving the indication and protocol description, the UPF 130 will know when and how to obtain the multiplexing identifier information from the DL data packets and will perform the following QFI specification for the QoS flow.

[0135] In some implementations, the SMF 120 may optionally provide a second indication 240 to the RAN node 102, which indicates that a QoS stream is associated with a single transport layer connection. For example, the SMF 120 may provide the second indication in an N2 SM message via the AMF 170. If necessary, the second indication may be used by the RAN node 102 for possible sequential processing among multiple media streams.

[0136] In some implementations, the SMF 120 can also provide the RAN node 102 with a QFI and QoS profile, which includes 5QI, Address Resolution Protocol (ARP), multiple QoS parameter sets, PDU set QoS parameters, and a PSI-FEC ratio mapping list. The RAN node 102 can determine the FEC ratio by examining the GTP-U header of DL packets from the UPF 130 to obtain the PSI and performing packet dropping. The RAN node 102 can perform PDU set-based processing based on the PDU set QoS parameters.

[0137] After receiving 245 DL data packets from application server 118 in DN 108, UPF 130 retrieves 250 multiplexing identification information from the data packets based on the protocol description and first indication.

[0138] In some implementations, the UPF 130 can obtain multiplexing identification information from the plaintext portion of a data packet, from the QUIC header, or from other parts of an unencrypted data packet based on the QUIC protocol.

[0139] Alternatively, in some implementations, the UPF 130 can obtain multiplexing identification information from the GTP-U header of the data packet.

[0140] Alternatively, in some implementations, the UPF 130 can obtain multiplexing identification information from the RTP header extension for data packets, based on the RTP protocol.

[0141] UPF 130 maps the media stream 255 to the QoS stream identified by the QFI based on the multiplexing identification information and a second information about the mapping between the QFI, the multiplexing identification information and multiple sets of QoS parameters.

[0142] After acquiring the multiplexing identification information, the UPF 130 will be able to identify each media stream in the media stream using the unique identification information. Then, by examining the corresponding list of QFIs and multiplexing identification information associated with QoS parameters received from the SMF 120, the UPF 130 can map the multiplexed media streams in the service data stream to the corresponding QoS streams marked by QFIs with different QoS parameters based on the service data stream template and the multiplexing identification information.

[0143] After receiving the DL data packet from UPF 130, RAN node 102 maps the QoS flow to the air interface resource (i.e., DRB in the case of 3GPP RAN) and sends the data packet to UE 104.

[0144] Through process 200, UPF 130 can identify multiplexed media streams with different QoS requirements within a single transport layer connection. UPF 130 can then perform QoS stream mapping for these media streams with different QoS requirements.

[0145] Figure 3 A signaling diagram illustrating an example process 300 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Process 300 may involve... Figure 1A Or UE 104 in 1B Figure 1B NEF 150 and AF 160 in the example. Process 300 may also involve a first device and a third device. In some implementations, the first device may perform... Figure 1B The SMF 120 in the middle. Alternatively, the first device can perform, in addition to Figure 1B In addition to the SMF 120, other network functions are included. In some implementations, a third device can perform... Figure 1B PCF 140 in the middle. Alternatively, a third device can perform, in addition to Figure 1B Other network functions besides PCF 140. For discussion purposes, references will be made to... Figure 1B Describe process 300. Process 300 may involve Figure 1B The UE104, SMF 120, PCF 140, NEF 150, and AF 160 are among them.

[0146] Actions 210, 215, 220, 225, and 230 in process 300 are the same as those in process 200. For the sake of brevity, the details of these actions have been omitted.

[0147] The difference between process 300 and process 200 lies in actions 335, 340, 345, and 350.

[0148] Specifically, SMF 120 provides UE 104 with the following items: second information regarding QFI, multiplexing identification information, and mappings between multiple QoS parameter sets.

[0149] In some implementations, the second information regarding QFI, multiplexing identifier information, and the mapping between multiple QoS parameter sets may include the following: QFI#1 --- Connection ID #X1 + Stream ID #Y1 --- QoS parameter set #1, and QFI#2---Connection ID #X2+Stream ID#Y2---QoS parameter set #2.

[0150] In some implementations, the SMF 120 can generate explicit signaling QoS rules based on the PCC rules from the PCF 140 and provide them to the UE 104. The QoS rules may include secondary information about the mapping.

[0151] In some implementations, QoS rules may also include a set of grouped filters generated from UL SDF filters.

[0152] In some implementations, the SMF 120 can also provide protocol descriptions to the UE 104 to assist the UE 104 in obtaining multiplexing identification information. For example, the SMF 120 can provide protocol descriptions and QoS rules to the UE 104.

[0153] After receiving the 340 UL data packet from the application, UE 104 obtains the 345 multiplexing identification information from the data packet based on the protocol description.

[0154] In some implementations, SMF 120 may also provide a first indication to UE 104, which specifies that UE 104 obtains multiplexing identification information from data packets. In such an implementation, UE 104 can obtain multiplexing identification information from data packets based on the protocol description and the first indication.

[0155] Alternatively, in some implementations, SMF 120 may not provide the first indication to UE 104. UE 104 may or may not use the protocol description to obtain multiplexing identification information from UL data packets based on UE 104's implementation.

[0156] In some implementations, UE 104 can obtain multiplexing identification information from the plaintext portion of a data packet, from the QUIC header, or from other portions of an unencrypted data packet based on the QUIC protocol.

[0157] Alternatively, in some implementations, UE 104 can obtain multiplexing identification information from the GTP-U header of the data packet.

[0158] Alternatively, in some implementations, UE 104 can obtain multiplexing identification information from the RTP header extension for data packets based on the RTP protocol.

[0159] UE 104 maps the media stream 350 to the QoS stream identified by the QFI based on the multiplexing identification information and second information about the mapping between QFI, multiplexing identification information and multiple sets of QoS parameters.

[0160] In some implementations, UE 104 can utilize QFI to mark the UL PDU.

[0161] Then, UE 104 can send UL PDUs using the corresponding access-specific resources for the QoS flow, based on the mapping provided by RAN node 102. RAN node 102 sends the PDU, including the QFI in the encapsulation header of the UL PDU, to UPF 130 via the N3 tunnel.

[0162] After acquiring the multiplexing identification information, UE 104 will be able to identify each media stream in the media stream using the unique identification information. Then, by checking the correspondence list of QFI and multiplexing identification information associated with QoS parameters received from SMF 120, UE 104 can map the multiplexed media streams in the service data stream to the corresponding QoS streams marked by QFI with different QoS parameters based on the service data stream template and the multiplexing identification information.

[0163] After receiving the UL data packet from UE 104, RAN node 102 maps the QoS flow to the air interface resource (i.e., DRB in the case of 3GPP RAN) and sends the data packet to UPF 130.

[0164] Through process 300, UE 104 can identify multiplexed media streams with different QoS requirements within a single transport layer connection. UE 104 can then perform QoS stream mapping for the media streams with different QoS requirements.

[0165] In the following text, reference will be made to Figure 4 This describes some implementations used to enhance alternative QoS profiles.

[0166] In some implementations, PDU set QoS parameters are used to support PDU set-based QoS processing in RAN node 102. At least one PDU set QoS parameter should be sent to RAN node 102 to enable PDU set-based QoS processing.

[0167] Currently, traditional alternative QoS profiles include: PDU error rate (PER), PDU delay budget (PDB), guaranteed stream bit rate (GFBR), average window, and optional maximum data burst size (MDBV). However, PDU set QoS parameters are not included in traditional alternative QoS profiles. Therefore, it is necessary to utilize PDU set QoS parameters to enhance traditional alternative QoS profiles.

[0168] Figure 4 A signaling diagram illustrating an example process 400 supporting enhanced alternative QoS profiles according to aspects of this disclosure is shown. Process 400 may involve Figure 1A Or RAN node 102-1 in 1B Figure 1B NEF 150 and AF 160 in the example. Process 400 may also involve a first device, a second device, and a third device. In some implementations, the first device may perform... Figure 1B The SMF 120 in the middle. Alternatively, the first device can perform, in addition to Figure 1B In addition to the SMF 120, other network functions are included. In some implementations, a third device can perform... Figure 1B PCF 140 in the middle. Alternatively, a third device can perform, in addition to Figure 1B Other network functions besides the PCF140. For discussion purposes, references will be made to... Figure 1B Describe process 400. Process 400 may involve... Figure 1B The RAN nodes are 102-1, SMF 120, PCF 140, NEF 150, and AF 160.

[0169] like Figure 4 As shown, the AF 160 can provide the NEF 150 with 410 alternative PDU sets of QoS parameters for media streams.

[0170] In some implementations, the QoS parameters for the candidate PDU set may include QoS parameters for the candidate UL PDU set and QoS parameters for the candidate DL PDU set for the QoS flow. The QoS parameters for the candidate UL PDU set for the QoS flow may be the same as or different from the QoS parameters for the candidate DL PDU set for the QoS flow.

[0171] In some implementations, alternative UL PDU set QoS parameters may include at least one of the following: UL PDU set delay budget (PSDB), UL PDU set error rate (PSER), or UL PDU set integrated processing information (PSIHI).

[0172] In some implementations, the QoS parameters for the alternative DL PDU set may include at least one of the following: DL PSDB, DL PSER, or DL ​​PSIHI.

[0173] In some implementations, the AF 160 can provide the NEF 150 with multiple alternative PDU set QoS parameter sets. Each of the multiple alternative PDU set QoS parameter sets can include alternative UL PDU set QoS parameters.

[0174] In some implementations, each of the multiple candidate PDU set QoS parameter sets can be assigned a priority. The AF 160 can provide multiple candidate PDU set QoS parameter sets to the NEF 150 in priority order. In other words, the AF 160 can provide multiple candidate PDU set QoS parameter sets to the NEF 150 in priority order.

[0175] In some implementations, the AF 160 can provide alternative service requests to the NEF 150. Alternative service requests may include alternative QoS parameter sets and alternative PDU set QoS parameter sets.

[0176] In some implementations, the AF 160 can also provide QoS parameters and PDU set QoS parameters to the NEF 150.

[0177] In some implementations, the AF 160 can also provide the NEF 150 with a flow description of the AF session and QoS parameters for an alternative PDU set. In such implementations, the flow description can be a packet filter set that includes direction, source and destination IP addresses, protocol, source and destination port numbers, etc. For example, the packet filter set can be an IP packet filter set or an Ethernet packet filter set. Alternatively, the flow description can be an application identifier (i.e., AppID).

[0178] In some implementations, the AF 160 can send an Nnef_AFsessionWithQoS_Create message to the NEF 150. The Nnef_AFsessionWithQoS_Create message can include QoS parameters for the alternative PDU set.

[0179] In some implementations, the Nnef_AFsessionWithQoS_Create message may also include at least one of the following: a flow description, QoS parameters, a PDU set of QoS parameters, or a set of alternative QoS parameters.

[0180] Upon receiving the Nnef_AFsessionWithQoS_Create message, NEF 150 grants AF requests for AF sessions with the required QoS parameters (415) and can apply policies to control the total amount of QoS granted to AF 160. If the grant is not granted, NEF 150 replies to AF 160 with a Result value indicating grant failure. Alternatively, in the case of a trusted AF, AF 160 can directly provide these parameters to PCF 140 without the involvement of NEF 150.

[0181] After successful authorization, the NEF 150 can provide the PCF 140 with QoS parameters for a set of 420 alternative PDUs.

[0182] In some implementations, the NEF 150 can provide the PCF 140 with multiple sets of alternative PDU sets of QoS parameters. Each of these sets can include alternative UL PDU set QoS parameters. For example, the NEF 150 can provide the PCF 140 with multiple sets of alternative PDU sets of QoS parameters in priority order.

[0183] In some implementations, the NEF 150 can also provide alternative service requirements to the PCF 140. Alternative service requirements can include a combination of alternative QoS parameter sets and alternative PDU set QoS parameters.

[0184] In some implementations, the NEF 150 can also provide QoS parameters and PDU set QoS parameters to the PCF 140.

[0185] In some implementations, the NEF 150 can also provide flow descriptions to the PCF 140.

[0186] In some implementations, the NEF 150 can send an Npcf_PolicyAuthorization_Create message to the PCF 140. The Npcf_PolicyAuthorization_Create message can include QoS parameters for the candidate PDU set.

[0187] In some implementations, the Npcf_PolicyAuthorization_Create message may also include at least one of the following: a flow description, QoS parameters, a set of PDU QoS parameters, or a set of alternative QoS parameters.

[0188] Alternatively, the PCF 140 can obtain the above information or parameters based on the operator's local configuration.

[0189] Then, the PCF 140 can provide the SMF 120 with QoS parameters for a set of 425 alternative PDUs.

[0190] In some implementations, the PCF 140 can also provide the SMF 120 with alternative QoS parameters, QoS parameters, and PDU set QoS parameters.

[0191] In some implementations, the PCF 140 can also provide a flow description to the SMF 120.

[0192] In some implementations, PCF 140 can also provide a third instruction to SMF 120.

[0193] In some implementations, the third indication may indicate that if the QoS profile is not satisfied, RAN node 102-1 provides SMF 120 with fourth information about at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set.

[0194] In some implementations, the fourth information regarding at least one of the candidate PDU set QoS parameters among the satisfied candidate PDU set QoS parameters may include at least one of the following: an index of a candidate QoS profile that includes at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters, or a fifth indication of at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters.

[0195] Alternatively, in some implementations, the third instruction may instruct: if the QoS profile is not satisfied, RAN node 102-1 provides SMF 120 with information about at least one of the satisfied alternative UL PDU set QoS parameters, and instruct: if the QoS profile is not satisfied, RAN node 102-1 provides SMF 120 with information about at least one of the satisfied alternative UL PDU set QoS parameters.

[0196] In some implementations, information regarding at least one of the satisfied alternative UL PDU set QoS parameters may include at least one of the following: a first index for a first alternative QoS profile for the UL, the first alternative QoS profile for the UL including at least one of the satisfied alternative UL PDU set QoS parameters, or a seventh indication of at least one of the satisfied alternative UL PDU set QoS parameters.

[0197] In some implementations, information regarding at least one of the satisfied alternative DL PDU set QoS parameters may include at least one of the following: a second index for a second alternative QoS profile for the DL, the second alternative QoS profile for the DL including at least one of the satisfied alternative DL PDU set QoS parameters, or an eighth indication of at least one of the satisfied alternative DL PDU set QoS parameters.

[0198] In some implementations, the PCF 140 can also provide a QoS Notification Control (QNC) indication to the SMF 120. The QNC indication specifies whether to request notification from RAN node 102-1 during the lifecycle of a QoS flow when the GFBR may no longer (or may again) guarantee the QoS flow. The GFBR is included in the legacy alternative QoS profile.

[0199] In some implementations, PCF 140 can generate PCC rules and send them to SMF 120. These PCC rules may include QoS parameters for a set of alternative PDUs.

[0200] In some implementations, PCC rules may also include at least one of the following: flow description, QoS parameters, alternative QoS parameters, PDU set QoS parameters, QNC indication, or third indication.

[0201] Upon receiving the QoS parameters for the candidate PDU set, the SMF 120 generates at least one of 430 candidate QoS profiles. Each candidate QoS profile in the at least one candidate QoS profile includes at least the QoS parameters for the candidate PDU set.

[0202] In some implementations, at least one alternative QoS profile may include at least one dedicated alternative QoS profile.

[0203] In some implementations, at least one dedicated alternative QoS profile may include at least one dedicated alternative QoS profile for UL and at least one dedicated alternative QoS profile for DL. Hereinafter, the dedicated alternative QoS profile for UL is also referred to as the “Alternate UL PDU Set QoS Profile”, and the dedicated alternative QoS profile for DL ​​is also referred to as the “Alternate DL PDU Set QoS Profile”.

[0204] In some implementations, the alternative UL PDU set QoS profile may include at least one of the following: UL PSDB, ULPSER, or UL PSIHI.

[0205] In some implementations, the alternative DL PDU set QoS profile may include at least one of the following: DL PSDB, DLPSER, or DL ​​PSIHI.

[0206] In some implementations, the alternative UL PDU set QoS profile may also include a UL GFBR, and the alternative DL PDU set QoS profile may also include a DL GFBR.

[0207] In some implementations, the SMF 120 can also generate a QoS profile, which can include QoS parameters and PDU set QoS parameters.

[0208] In some implementations, the SMF 120 can also generate at least one legacy alternative QoS profile. Each legacy alternative QoS profile in the at least one legacy alternative QoS profile may include one alternative QoS parameter set from the alternative QoS parameter set. Each alternative QoS parameter set in the alternative QoS parameter set may include at least one of the following: PER, PDB, GFBR, average window, and optionally MDBV.

[0209] In some implementations, the SMF 120 can add QoS parameters from a set of alternative PDUs to a legacy alternative QoS profile to obtain an upgraded alternative QoS profile. In such an implementation, the upgraded alternative QoS profile may include at least one of the following: PER, PDB, UL GFBR, DL GFBR, average window, MDBV, UL PSDB, UL PSER, UL PSIHI, DLPSDB, DL PSER, or DLPSIHI. In other words, each alternative QoS profile in at least one alternative QoS profile may include at least one of the following: PER, PDB, UL GFBR, DL GFBR, average window, MDBV, UL PSDB, UL PSER, ULPSIHI, DL PSDB, DL PSER, or DLPSIHI.

[0210] Then, SMF 120 provides at least one alternative QoS profile to RAN node 102-1. For example, SMF 120 can provide at least one alternative QoS profile to RAN node 102-1 via NAS signaling through AMF 170.

[0211] In some implementations, the SMF 120 can provide RAN node 102-1 with at least one set of 435 alternative UL PDU QoS profiles.

[0212] In some implementations, each of the at least one alternative UL PDU set QoS profiles can be assigned a priority. The SMF 120 can provide at least one alternative UL PDU set QoS profile to the RAN node 102-1 in priority order for the at least one alternative UL PDU set QoS profile. In other words, the SMF 120 can provide at least one alternative UL PDU set QoS profile to the RAN node 102-1 in priority order.

[0213] Alternatively or otherwise, in some implementations, the SMF 120 may provide at least one alternative DL PDU set QoS profile to the RAN node 102-1.

[0214] In some implementations, each of the at least one alternative DL PDU set QoS profiles can be assigned a priority. The SMF 120 can provide at least one alternative DL PDU set QoS profile to the RAN node 102-1 in priority order for the at least one alternative DL PDU set QoS profile. In other words, the SMF 120 can provide at least one alternative DL PDU set QoS profile to the RAN node 102-1 in priority order.

[0215] In some implementations, the SMF 120 can also provide a third instruction to RAN node 102-1.

[0216] In some implementations, the third indication may indicate that if the QoS profile is not satisfied, RAN node 102-1 provides SMF 120 with fourth information about at least one of the QoS parameters of the candidate PDU set among the satisfied candidate PDU set.

[0217] Alternatively, in some implementations, the third instruction may instruct: if the QoS profile is not satisfied, RAN node 102-1 to provide SMF 120 with information about at least one of the satisfied alternative UL PDU set QoS parameters, and instruct: if the QoS profile is not satisfied, RAN node 102-1 to provide SMF 120 with information about at least one of the satisfied alternative DL PDU set QoS parameters.

[0218] In some implementations, the SMF 120 may also provide RAN node 102-1 with at least one of the following: a QoS profile or a QNC indication.

[0219] In some implementations, the SMF 120 can also provide at least one traditional alternative QoS profile to RAN node 102-1.

[0220] In some implementations, each of the at least one legacy alternative QoS profiles can be assigned a priority. The SMF 120 can provide at least one legacy alternative QoS profile to the RAN node 102-1 in priority order for the at least one legacy alternative QoS profile. In other words, the SMF 120 can provide at least one legacy alternative QoS profile to the RAN node 102-1 in priority order.

[0221] Upon receiving a QoS profile, RAN node 102-1 can determine whether the QoS parameters in the 440 QoS profile can be satisfied. If at least one QoS parameter in the QoS profile cannot be satisfied, and RAN node 102-1 supports PDU set-based processing, then RAN node 102-1 can also determine whether the QoS parameters of the PDU set in the QoS profile can be satisfied.

[0222] If at least one PDU set QoS parameter in the PDU set of the QoS profile cannot be satisfied, RAN node 102-1 can also determine whether the QoS parameters of the alternative PDU set in at least one alternative QoS profile can be satisfied. For example, RAN node 102-1 can determine whether the QoS parameters of the alternative PDU set in at least one alternative QoS profile can be satisfied in descending order for at least one alternative QoS profile.

[0223] In some implementations, RAN node 102-1 can determine whether at least one of the candidate UL PDU set QoS parameters in the candidate UL PDU set QoS profile can be satisfied. Alternatively or additionally, RAN node 102-1 can also determine whether at least one of the candidate DL PDU set QoS parameters in the candidate DL PDU set QoS profile can be satisfied.

[0224] In some implementations, if the QoS profile cannot be satisfied, RAN node 102-1 can provide a fourth indication to SMF 120, indicating that the QoS profile is not satisfied. For example, if at least one QoS parameter in the QoS profile cannot be satisfied, RAN node 102-1 can provide a fourth indication to SMF 120. For example, the fourth indication could indicate that "GFBR can no longer be guaranteed".

[0225] Alternatively or additionally, in some implementations, if at least one of the PDU set QoS parameters in the QoS profile cannot be satisfied, RAN node 102-1 may provide a sixth indication to SMF 120. This sixth indication indicates that the PDU set QoS parameters included in the QoS profile have not been satisfied.

[0226] Alternatively or otherwise, in some implementations, if the QoS profile cannot be satisfied, RAN node 102-1 may provide SMF 120 with fourth information about at least one of the QoS parameters of the satisfied alternative PDU set.

[0227] In some implementations, the fourth information regarding at least one of the candidate PDU set QoS parameters among the satisfied candidate PDU set QoS parameters may include at least one of the following: an index of a candidate QoS profile that includes at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters, or a fifth indication of at least one candidate PDU set QoS parameter among the satisfied candidate PDU set QoS parameters.

[0228] As described above, in some implementations, at least one alternative QoS profile may include at least one dedicated alternative QoS profile. In such an implementation, the fourth information may include an index of an alternative QoS profile, which includes at least one alternative PDU set QoS parameter from a set of alternative PDUs that are satisfied.

[0229] Alternatively, as described above, in some implementations, the SMF 120 can add alternative PDU set QoS parameters to a legacy alternative QoS profile to obtain an upgraded alternative QoS profile. In such an implementation, the fourth information may include an index to the alternative QoS profile, which includes at least one alternative PDU set QoS parameter from the satisfied alternative PDU set QoS parameters, and a fifth indication of at least one alternative PDU set QoS parameter from the satisfied alternative PDU set QoS parameters. Alternatively, in such an implementation, the fourth information may include a fifth indication of at least one alternative PDU set QoS parameter from the satisfied alternative PDU set QoS parameters.

[0230] Alternatively, in some implementations, if a QoS profile cannot be satisfied, RAN node 102-1 may provide SMF 120 with information about at least one of the satisfied alternative UL PDU set QoS parameters. The information about at least one of the satisfied alternative UL PDU set QoS parameters may include at least one of the following: a first index to a first alternative QoS profile for the UL, which includes at least one of the satisfied alternative UL PDU set QoS parameters, or a seventh indication of at least one of the satisfied alternative UL PDU set QoS parameters.

[0231] Alternatively or additionally, in some implementations, if a QoS profile cannot be satisfied, RAN node 102-1 may provide SMF 120 with information about at least one of the satisfied alternative DL PDU set QoS parameters. The information about at least one of the satisfied alternative DL PDU set QoS parameters may include at least one of the following: a second index of a second alternative QoS profile for the DL, which includes at least one of the satisfied alternative DL PDU set QoS parameters, or an eighth indication of at least one of the satisfied alternative DL PDU set QoS parameters.

[0232] In some implementations, if at least one PDU set QoS parameter in the PDU set QoS parameters of the QoS profile cannot be satisfied, RAN node 102-1 can also determine whether at least one alternative QoS parameter in the alternative QoS profile can be satisfied.

[0233] Upon receiving a fourth indication (450) indicating that the QoS profile is not satisfied, a sixth indication indicating that the QoS parameters of the PDU set included in the QoS profile are not satisfied, or fourth information regarding at least one of the satisfied alternative PDU set QoS parameters, the SMF 120 may provide the PCF 140 with at least one of the following: a fourth indication indicating that the QoS profile is not satisfied, or fourth information regarding at least one of the satisfied alternative PDU set QoS parameters.

[0234] In some implementations, SMF 120 can provide a fourth instruction and a fourth message to PCF 140 via a policy control request.

[0235] Furthermore, PCF 140 can provide AF 160 with 460 fourth instructions and fourth information.

[0236] In some implementations, PCF 140 can provide AF 160 with a fourth instruction and a fourth information via event reporting.

[0237] In some implementations, for handover scenarios, RAN node 102-1 can act as the target RAN node, and RAN node 102-2 can act as the source RAN node. In such an implementation, RAN node 102-1 can provide RAN node 120-2 with at least one of the following: a fourth indication that the QoS profile is not satisfied, or fourth information regarding at least one QoS parameter of the candidate PDU set among the satisfied candidate PDU set QoS parameters.

[0238] In some implementations, for Xn handover, RAN node 102-1 can provide fourth information to SMF120 in the N2 path handover request message.

[0239] In some implementations, for N2 handover, the fourth piece of information may be included in the handover request ACK message that is sent from RAN node 102-1 (i.e., the target RAN node) to the target AMF and subsequently to SMF 120.

[0240] In some implementations, process 400 can be executed in combination with either process 200 or 300.

[0241] Figure 5 An example of a device 500 supporting QoS stream mapping for multiplexed media streams according to some aspects of this disclosure is shown. Device 500 may be an example of a first device, a second device, or a UE 104 as described herein. Device 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as a processor 502, a memory 504, a transceiver 506, and optionally an I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., a bus).

[0242] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0243] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 504 by processor 502).

[0244] For example, processor 502 may support wireless communication at device 500 according to examples disclosed herein. Processor 502 may be configured to operate to support components for: acquiring protocol descriptions and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream; determining QFIs for the QoS stream, wherein each QFI is associated with a media stream in the media stream; and providing a second device or UE with second information about the QFIs, the multiplexing identification information, and the mapping between the plurality of QoS parameter sets.

[0245] Alternatively, in some implementations, processor 502 may be configured to support components for performing the following: obtaining from a first means: a protocol description, wherein the protocol description includes first information regarding the location of obtaining multiplexing identification information from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection; second information regarding the mapping between QFI, the multiplexing identification information, and a plurality of QoS parameter sets for the media stream; and a first indication indicating that the second means obtains the multiplexing identification information from the data packets; obtaining the multiplexing identification information from the data packets based on the protocol description and the first indication; and mapping the media stream to a QoS stream identified by the QFI based on the multiplexing identification information and the second information regarding the mapping.

[0246] Alternatively, in some implementations, processor 502 may be configured to support components for performing the following: obtaining: second information regarding QFIs for QoS streams, multiplexing identification information for identifying media streams, and mappings between multiple sets of QoS parameters, wherein each QFI is associated with a media stream carried in uplink data packets and multiplexed over a single transport layer connection; and mapping the media streams to QoS streams based on the second information regarding the mappings.

[0247] Alternatively, in some implementations, processor 502 may be configured to support components for performing the following: providing a first device with protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream.

[0248] Alternatively, in some implementations, processor 502 may be configured to support components for performing the following: acquiring at least one alternative QoS profile from a first device via a transceiver, wherein each of the at least one alternative QoS profile includes at least: QoS parameters for an alternative PDU set for a media stream.

[0249] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0250] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0251] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device 500. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor, such as processor 502. In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0252] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 510 for transmission, and demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0253] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.

[0254] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0255] Figure 6 An example of a processor 600 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0256] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., processor chipset-local or included memory (e.g., processor 600)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0257] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0258] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, such that processor 600 supports various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600, such that processor 600 supports various operations according to the examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0259] Memory 604 may include one or more caches (e.g., memory local to processor 600 or included in processor 600) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., locally to processor 600). In some other implementations, memory 604 may reside outside the processor chipset (e.g., remotely from processor 600).

[0260] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions (e.g., functions or tasks supporting transmit power priority). For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0261] One or more ALU 606s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 606s may reside within or on the processor chipset (e.g., processor 600). In some other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU606s to handle conditional operations, comparisons, and bitwise operations.

[0262] Processor 600 may support wireless communication according to examples disclosed herein. Processor 600 may be configured to operate to support components for: acquiring protocol descriptions and multiplexing identification information associated with multiple sets of QoS parameters for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream; determining QFIs for the QoS stream, wherein each QFI is associated with a media stream in the media stream; and providing a second device or UE with second information about the QFIs, the multiplexing identification information, and the mapping between the multiple sets of QoS parameters.

[0263] Alternatively, in some implementations, processor 600 may be configured to support components for performing the following: obtaining from a first means: a protocol description, wherein the protocol description includes first information about the location of obtaining multiplexing identification information from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection; second information about the mapping between QFI, the multiplexing identification information, and a plurality of QoS parameter sets for the media stream; and a first indication indicating that the second means obtains the multiplexing identification information from the data packets; obtaining the multiplexing identification information from the data packets based on the protocol description and the first indication; and mapping the media stream to a QoS stream identified by the QFI based on the multiplexing identification information and the second information about the mapping.

[0264] Alternatively, in some implementations, processor 600 may be configured to support components for performing the following: obtaining: second information regarding QFIs for QoS streams, multiplexing identification information for identifying media streams, and mappings between multiple sets of QoS parameters, wherein each QFI is associated with a media stream carried in uplink data packets and multiplexed over a single transport layer connection; and mapping the media streams to QoS streams based on the second information regarding the mappings.

[0265] Alternatively, in some implementations, processor 600 may be configured to support components for performing the following: providing a first device with protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream.

[0266] Alternatively, in some implementations, processor 600 may be configured to support components for performing the following: acquiring at least one alternative QoS profile from a first device via a transceiver, wherein each of the at least one alternative QoS profile includes at least: QoS parameters for an alternative PDU set for a media stream.

[0267] Figure 7 A flowchart of a method 700 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Operation of method 700 can be implemented by a device or its components, as described herein. For example, operation of method 700 can be performed by a first means, as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the function.

[0268] At 710, the method may include: acquiring protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection. The protocol description includes first information about the location from which the multiplexing identification information is acquired from the data packets, and the multiplexing identification information is used to identify the media stream. The operation of 710 can be performed according to examples as described herein. In some implementations, aspects of the operation of 710 may be performed by a device, as referenced... Figure 1B As stated above.

[0269] At 720, the method may include: determining QFIs for a QoS stream, wherein each QFI is associated with a media stream in the media stream. The operation at 720 can be performed according to examples as described herein. In some implementations, aspects of the operation at 720 may be performed by a device, as referenced... Figure 1B As stated above.

[0270] At 730, the method may include providing a second device or UE with second information regarding QFI, multiplexing identification information, and a mapping between multiple sets of QoS parameters. The operation at 730 can be performed according to examples as described herein. In some implementations, aspects of the operation at 730 can be performed by a device, as referenced... Figure 1B As stated above.

[0271] Figure 8A flowchart of a method 800 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Operation of method 800 may be implemented by a device or its components, as described herein. For example, operation of method 800 may be performed by a first means, as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device may use dedicated hardware to perform aspects of the function.

[0272] At 810, the method may include: obtaining from a first means the following: a protocol description, wherein the protocol description includes first information regarding the location of obtaining multiplexing identification information from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection; second information regarding the mapping between QFI, the multiplexing identification information, and multiple sets of QoS parameters for the media stream; and a first indication indicating that a second means obtains multiplexing identification information from data packets. Operation of 810 may be performed according to examples as described herein. In some implementations, aspects of operation of 810 may be performed by a device, as referenced in [reference]. Figure 1B As stated above.

[0273] At 820, the method may include: obtaining multiplexing identification information from the data packet based on the protocol description and a first indication. The operation at 820 can be performed according to the examples described herein. In some implementations, aspects of the operation at 820 may be performed by a device, as referenced... Figure 1B As stated above.

[0274] At 830, the method may include mapping a media stream to a QoS stream identified by a QFI based on multiplexing identification information and second information about the mapping. The operation at 830 can be performed according to examples as described herein. In some implementations, aspects of the operation at 830 can be performed by a device, as referenced... Figure 1B As stated above.

[0275] Figure 9 A flowchart of a method 900 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Operation of method 900 can be implemented by a device or its components, as described herein. For example, operation of method 900 can be performed by a first means, as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the function.

[0276] At 910, the method may include: obtaining second information regarding the QFI for a QoS stream, multiplexing identification information for identifying media streams, and a mapping between multiple sets of QoS parameters, wherein each QFI is associated with a media stream carried in uplink data packets and multiplexed over a single transport layer connection. The operation of 910 can be performed according to examples as described herein. In some implementations, aspects of the operation of 910 can be performed by a device, as referenced... Figure 1B As stated above.

[0277] At 920, the method may include mapping the media stream to a QoS stream based on second information about the mapping. The operation at 920 can be performed according to examples as described herein. In some implementations, aspects of the operation at 920 may be performed by a device, as referenced... Figure 1B As stated above.

[0278] Figure 10 A flowchart of a method 1000 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Operation of method 1000 can be implemented by a device or its components, as described herein. For example, operation of method 1000 can be performed by a first means, as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the function.

[0279] At 1010, the method may include: providing a first device with a protocol description and multiplexing identification information associated with a plurality of QoS parameter sets for a media stream carried in data packets and multiplexed over a single transport layer connection. The protocol description includes first information regarding the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream. The operation of 1010 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1010 may be performed by a device, as referenced... Figure 1B As stated above.

[0280] Figure 11 A flowchart of a method 1100 supporting QoS stream mapping for multiplexed media streams according to aspects of this disclosure is shown. Operation of method 1100 can be implemented by a device or components thereof, as described herein. For example, operation of method 1100 can be performed by a first means, as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the function.

[0281] At 1110, the method may include: obtaining at least one alternative QoS profile from a first device. Each alternative QoS profile in the at least one alternative QoS profile includes at least: QoS parameters for a set of alternative PDUs for a media stream. The operation at 1110 can be performed according to examples as described herein. In some implementations, aspects of the operation at 1110 may be performed by a device, as referenced in [reference]. Figure 1B As stated above.

[0282] It should be noted that Figures 1 to 14 have been referenced. Figure 4 The implementations of this disclosure described herein are also applicable to device 500, processor 600, and methods 700, 800, 900, 1000, and 1100.

[0283] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0284] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0285] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0286] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0287] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0288] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first device: Acquire protocol description and multiplexing identification information associated with a set of multiple Quality of Service (QoS) parameters for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained, and the multiplexing identification information is used to identify the media stream; Determine a QoS Stream Identifier (QFI) for each QoS stream, wherein each QFI is associated with a media stream in the media stream; as well as The following items are provided to the second device or user equipment (UE): Second information regarding the mapping between the QFI, the multiplexing identifier information, and the multiple QoS parameter sets.

2. The first device according to claim 1, wherein the reuse identification information includes at least one of the following: The identifier of the transport layer connection, or The identifier of the media stream.

3. The first apparatus of claim 1, wherein the at least one processor is further configured to cause the first apparatus to provide the second apparatus with: The protocol description, and A first instruction indicates that the second device obtains the multiplexing identification information from the data packet.

4. The first apparatus of claim 1, wherein the at least one processor is further configured to cause the first apparatus to: Obtain the QoS parameters of the alternative Protocol Data Unit (PDU) set for the media stream; and Provide at least one alternative QoS profile to the radio access network (RAN) node, wherein each alternative QoS profile in the at least one alternative QoS profile includes at least the QoS parameters of the alternative PDU set.

5. The first apparatus according to claim 4, wherein the at least one alternative QoS profile includes at least one dedicated alternative QoS profile.

6. The first apparatus according to claim 5, wherein the at least one dedicated alternative QoS profile comprises: A first dedicated alternative QoS profile for uplink UL and a second dedicated alternative QoS profile for downlink DL; The first dedicated alternative QoS profile used for UL includes at least one of the following: UL PDU set delay budget PSDB, UL PDU set error rate PSER, or UL PDU integrates and processes PSIHI information; and The second dedicated alternative QoS profile used for DL ​​includes at least one of the following: DL PSDB, DL PSER, or DL PSIHI.

7. The first apparatus of claim 6, wherein the first dedicated alternative QoS profile for UL further includes a UL guaranteed stream bit rate GFBR, and the second dedicated alternative QoS profile for DL ​​further includes a DL GFBR.

8. The first apparatus of claim 4, wherein each of the at least one dedicated alternative QoS profiles comprises at least one of the following: PDU error rate PER, PDU Delay Budget (PDB) UL guarantees stream bit rate GFBR, DL GFBR, Average window, Maximum Data Burst Volume (MDBV) ULPDU set delay budget PSDB, UL PDU set error rate PSER, UL PDU integrates and processes information PSIHI. DL PSDB, DL PSER, or DL PSIHI.

9. The first apparatus of claim 4, wherein the at least one processor is further configured to cause the first apparatus to: The RAN node is provided with a third indication, wherein the third indication indicates that if the QoS profile is not satisfied, the RAN node provides the first device with fourth information regarding at least one of the QoS parameters of the satisfied candidate PDU set.

10. The first apparatus of claim 9, wherein the at least one processor is further configured to cause the first apparatus to: Obtain at least one of the following from the RAN node: The fourth indication indicates that the QoS profile was not satisfied. The sixth indication indicates that the QoS parameters of the PDU set included in the QoS profile are not satisfied, or The fourth information regarding at least one of the QoS parameters of the candidate PDU set that is satisfied.

11. The first apparatus according to claim 9 or 10, wherein the fourth information regarding the at least one QoS parameter of the candidate PDU set among the satisfied candidate PDU set QoS parameters includes at least one of the following: An index of alternative QoS profiles, the alternative QoS profiles including at least one of the alternative PDU set QoS parameters that are satisfied, or The fifth indication of at least one of the candidate PDU set QoS parameters among the candidate PDU set QoS parameters that are satisfied.

12. A second device, comprising At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the second device: The following items are obtained from the first device: The protocol description includes first information regarding the location where multiplexing identification information is obtained from data packets, and the multiplexing identification information is used to identify media streams in data packets multiplexed over a single transport layer connection. The second information pertains to the Quality of Service (QoS) Stream Identifier (QFI), the multiplexing identification information, and the mapping between multiple QoS parameter sets for the media stream. A first instruction indicates that the second device obtains the multiplexing identification information from the data packet; Based on the protocol description and the first instruction, the multiplexing identification information is obtained from the data packet; as well as Based on the multiplexing identification information and the second information about the mapping, the media stream is mapped to a QoS stream identified by the QFI.

13. The second apparatus of claim 2, wherein the at least one processor is configured such that the second apparatus obtains the multiplexing identification information from the data packet by: The reuse identification information can be obtained from one of the following: The plaintext portion of the data packets based on the Fast User Datagram Protocol (UDP) Internet connection QUIC protocol, The data packet contains the General Packet Radio Service (GPRS) Tunneling Protocol User Plane GTP-U header, or The RTP header extension for the data packets based on the Real-time Transport Protocol (RTP).

14. A user equipment (UE), comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The following items are obtained from the first device via the transceiver: The second information pertains to the QoS Flow Identifier (QFI) for a Quality of Service (QoS) flow, multiplexing identification information for identifying media flows, and a mapping between multiple sets of QoS parameters, wherein each QFI is associated with a media flow carried in uplink data packets and multiplexed over a single transport layer connection. as well as Based on the second information regarding the mapping, the media stream is mapped to the QoS stream.

15. The UE of claim 14, wherein the processor is further configured to: A protocol description is obtained from a first device, wherein the protocol description includes first information regarding the location of obtaining the multiplexing identification information from the uplink data packets; and The processor is configured to map the media stream to the QoS stream based on the protocol description and the second information about the mapping.

16. A third device, comprising At least one memory; and At least one processor, coupled to the at least one memory, and configured such that the third device: A first device is provided with protocol description and multiplexing identification information associated with a set of multiple Quality of Service (QoS) parameters for a media stream carried in data packets and multiplexed over a single transport layer connection, wherein the protocol description includes first information about the location from which the multiplexing identification information is obtained from the data packets, and the multiplexing identification information is used to identify the media stream.

17. The third apparatus of claim 16, wherein the at least one processor is further configured to cause the third apparatus to: Provide the first device with alternative Protocol Data Unit (PDU) set Quality of Service (QoS) parameters.

18. The third apparatus of claim 16, wherein the at least one processor is further configured to cause the third apparatus to: A third instruction is provided to the first device, wherein the third instruction indicates that if the QoS profile is not satisfied, the radio access network RAN ​​node provides the first device with fourth information regarding at least one of the QoS parameters of the candidate PDU set that has been satisfied.

19. A radio access network (RAN) node, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: At least one alternative Quality of Service (QoS) profile is obtained from the first device via the transceiver, wherein each of the at least one alternative QoS profile includes at least: alternative Protocol Data Unit (PDU) set QoS parameters for the media stream.

20. The RAN node of claim 19, wherein the at least one processor is further configured to: The first device is provided with at least one of the following: The fourth indication indicates that the QoS profile was not satisfied. The sixth indication indicates that the QoS parameters of the PDU set included in the QoS profile are not satisfied, or The fourth information regarding at least one of the QoS parameters of the candidate PDU set that is satisfied.

Images