QoS flow mapping for multiplexed media flows

Abstract

Various aspects of the present disclosure relate to devices, UEs, and methods that support QoS flow mapping for multiplexed media flows. In one aspect, a first device obtains multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a data packet and multiplexed over a single transport layer connection. The protocol description includes first information regarding where to obtain the multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams. Next, the first device determines QoS flow identifiers (QFIs) for the QoS flows, and each of the QFIs is associated with one of the media streams. Subsequently, the first device provides a second device or UE with second information regarding mapping between the QFIs, the multiplexing identification information, and the plurality of sets of QoS parameters.

Description

Technology Field

[0001] The present disclosure relates to wireless communications, and more specifically to devices and methods for mapping Quality of Service (QoS) flows for multiplexed media flows. Background Technology

[0002] A wireless communication system may include one or more network communication devices, e.g., base stations, which may be known differently as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device, e.g., a base station, may support wireless communication with one or more user communication devices, which may be known differently as User Equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by using the resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including 3rd generation (3G) radio access technology, 4th generation (4G) radio access technology, and 5th generation (5G) radio access technology, among other suitable radio access technologies after 5G (e.g., 6th generation (6G)).

[0003] There is a scenario in which multiple different media streams of an Extended Reality (XR) service can be multiplexed over a single transport layer connection that shares the same Internet Protocol (IP) 5-tuple along with the transport protocol, and each of the media streams may have its own Quality of Service (QoS) requirements. The transport protocol multiplexes different data streams from the application and uses the same IP 5-tuple. For example, a Virtual Reality (VR) or Augmented Reality (AR) application may use multiple streams within a single session for its various traffic profiles and purposes, namely, one stream for signaling, one stream for control, one stream for audio, and one or more streams for video. These streams all share the same connection while having different QoS requirements or parameters.

[0004] However, for the current 5GS QoS framework, when a service data flow is mapped onto a QoS flow, it has only one set of QoS parameters and does not support differentiated QoS handling within a single QoS flow.

[0005] The present disclosure relates to devices, a UE, and methods that support QoS flow mapping for multiplexed media flows. Using the devices, the UE, and the methods, a second device or UE can identify multiplexed media flows having different QoS requirements within a single transport layer connection. Next, the second device or UE can perform QoS flow mapping for the media flows having different QoS requirements.

[0006] Some embodiments of the first device described herein may include at least one memory and at least one processor coupled with at least one memory. The at least one processor is configured to enable the first device to obtain a protocol description and multiplexing identification information associated with a plurality of sets of quality of service (QoS) parameters for media streams carried in a data packet and multiplexed over a single transport layer connection—the protocol description includes first information regarding where to obtain the multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams—; to determine QoS flow identifiers (QFIs) for QoS flows—each of which is associated with one of the media streams—; and to provide the second device or user equipment (UE) with second information regarding the mapping between the QFIs, the multiplexing identification information, and the plurality of sets of QoS parameters.

[0007] In some implementations, the multiplexing identification information includes at least one of the identity of a transport layer connection or the identities of media streams.

[0008] In some implementations, at least one processor is further configured to allow the first device to provide the second device with a first indication indicating to the second device to obtain multiplexing identification information from a protocol description and data packet.

[0009] In some implementations, a single transport layer connection includes a connection based on the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description additionally includes third information regarding the QUIC protocol.

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

[0011] In some implementations, at least one processor is additionally configured to cause the first device to: obtain alternative protocol data unit (PDU) set QoS parameters for media streams; and to provide at least one alternative QoS profile to a radio access network (RAN) node, each of which includes at least the alternative PDU set QoS parameters.

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

[0013] In some implementations, at least one dedicated alternate QoS profile includes a first dedicated alternate QoS profile for the uplink (UL) and a second dedicated alternate QoS profile for the downlink (DL). In some implementations, the first dedicated alternate QoS profile for the UL includes at least one of the UL PDU Set Delay Budget (PSDB), the UL PDU Set Error Rate (PSER), or the UL PDU Set Integrated Handling Information (PSIHI). In some implementations, the second dedicated alternate QoS profile for the DL includes at least one of the DL PSDB, the DL PSER, or the DL PSIHI.

[0014] In some implementations, a first dedicated alternate QoS profile for UL further includes a UL Guaranteed Flow Bit Rate (GFBR), and a second dedicated alternate QoS profile for DL ​​further includes a DL GFBR.

[0015] In some implementations, each of at least one dedicated alternate QoS profile includes at least one of the PDU Error Rate (PER), PDU Delay Budget (PDB), UL Guaranteed Flow Bit Rate (GFBR), DL GFBR, averaging window, Maximum Data Burst Volume (MDBV), ULPDU Set Delay Budget (PSDB), UL PDU Set Error Rate (PSER), UL PDU Set Integrated Handling Information (PSIHI), DL PSDB, DL PSER, or DL ​​PSIHI.

[0016] In some implementations, at least one processor is configured to cause the first device to provide at least one prioritized list of alternate QoS profiles to the RAN node.

[0017] In some implementations, at least one processor is additionally configured to cause the first device to provide a third indication to the RAN node, the third indication to provide the first device with fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among alternative PDU set QoS parameters when the QoS profile is not satisfied.

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

[0019] In some implementations, the fourth information regarding at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters includes an index of an alternate QoS profile containing at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters, or at least one of a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate 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 a fourth indication indicating that the QoS profile is not satisfied, or at least one of fourth information regarding at least one alternate PDU set QoS parameter that is satisfied among the alternate PDU set QoS parameters.

[0021] Some implementations of the second device described herein may include at least one memory and at least one processor coupled with at least one memory. The at least one processor is configured to enable the second device to obtain from the first device a protocol description—the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and the multiplexing identification information is used to identify media streams within a multiplexed data packet over a single transport layer connection—second information regarding mapping between QFIs for media streams, multiplexing identification information, and a plurality of sets of QoS parameters, and a first indication indicating to the second device to obtain multiplexing identification information from a data packet; to obtain multiplexing identification information from a data packet based on the protocol description and the first indication; and to map media streams to QoS streams identified by QFIs based on the multiplexing identification information and the second information regarding mapping.

[0022] In some implementations, the multiplexing identification information includes at least one of the identity of a transport layer connection or the identities of media streams.

[0023] In some implementations, a single transport layer connection includes a connection based on the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description additionally includes third information regarding the QUIC protocol.

[0024] In some implementations, at least one processor is configured to allow a second device to obtain multiplexing identification information from a data packet by obtaining multiplexing identification information from one of the plaintext part of a data packet based on the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, the General Packet Radio Service (GPRS) Tunnel Protocol-User Plane (GTP-U) header of a data packet, or the Real-time Transport Protocol (RTP) header extension for a data packet based on the RTP protocol.

[0025] Some implementations of the UE described herein may include a processor and a transceiver coupled to the processor. The processor obtains, through the transceiver, QFIs for QoS flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters—each QFI being associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection—and is configured to map the media streams to QoS flows based on the second information regarding mapping.

[0026] In some implementations, the processor is additionally configured to obtain a protocol description from a first device, and the protocol description includes first information regarding where to obtain multiplexing identification information from an uplink data packet. In such implementations, the processor is configured to map media streams to QoS flows based on the protocol description and second information regarding mapping.

[0027] In some implementations, the multiplexing identification information includes at least one of the identity of a transport layer connection or the identities of media streams.

[0028] In some implementations, a single transport layer connection includes a connection based on the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, and the protocol description additionally includes third information regarding the QUIC protocol.

[0029] Some embodiments of the third device described herein may include at least one memory and at least one processor coupled with at least one memory. The at least one processor is configured to enable the third device to provide the first device with multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a data packet and multiplexed over a single transport layer connection, the protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams.

[0030] In some implementations, at least one processor is additionally configured to allow a third device to provide alternative protocol data unit (PDU) set quality of service (QoS) parameters to the first device.

[0031] In some implementations, at least one processor is additionally configured to cause a third device to provide a third indication to the first device, and the third indication indicates to the radio access network (RAN) node to provide the first device with fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among alternative PDU set QoS parameters when the QoS profile is not satisfied.

[0032] In some implementations, at least one processor is further configured to allow a third device to obtain from the first device at least one of a fourth indication indicating that the QoS profile is not satisfied, or at least one of fourth information regarding at least one alternate PDU set QoS parameter that is satisfied among the alternate PDU set QoS parameters.

[0033] In some implementations, the fourth information regarding at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters includes an index of an alternate QoS profile containing at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters, or at least one of a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate 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 a fourth indication indicating that the QoS profile is not satisfied, or at least one of fourth information regarding at least one alternate PDU set QoS parameter that is satisfied among the alternate PDU set QoS parameters.

[0035] Some implementations of the RAN node described in this specification may include a processor and a transceiver coupled to the processor. The processor is configured to obtain at least one alternate QoS profile from a first device through the transceiver, and each of the at least one alternate QoS profile includes at least an alternate protocol data unit (PDU) set QoS parameters for media streams.

[0036] In some implementations, at least one alternate QoS profile includes at least one dedicated alternate QoS profile that includes at least one PDU set QoS parameter.

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

[0038] In some implementations, a first dedicated alternate QoS profile for the UL includes at least one of the UL PDU set delay budget (PSDB), UL PDU set error rate (PSER), or UL PDU set aggregation handling information (PSIHI).

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

[0040] In some implementations, a first dedicated alternate QoS profile for UL further includes a UL guaranteed flow bit rate (GFBR), and a second dedicated alternate QoS profile for DL ​​further includes a DL GFBR.

[0041] In some implementations, each of at least one dedicated alternate QoS profile includes at least one of a PDU error rate (PER), a PDU delay budget (PDB), a UL guaranteed flow bit rate (GFBR), a DL GFBR, an averaging window, a maximum data burst volume (MDBV), a ULPDU set delay budget (PSDB), a UL PDU set error rate (PSER), a UL PDU set aggregation handling information (PSIHI), a DL PSDB, a DL PSER, or a DL PSIHI.

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

[0043] In some implementations, at least one processor is additionally configured to obtain a third indication from a first device via a transceiver, and the third indication indicates to the RAN node to provide the first device with fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among alternative PDU set QoS parameters when the QoS profile is not satisfied.

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

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

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

[0047] Some implementations of the method described herein may include the steps of: obtaining multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a data packet and multiplexed over a single transport layer connection—the protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams—; determining QFIs for QoS streams—each of which is associated with one of the media streams—; and providing a second device or user equipment (UE) with second information regarding the mapping between the QFIs, multiplexing identification information, and a plurality of sets of QoS parameters.

[0048] Some implementations of the method described herein may include the step of obtaining from a first device a protocol description—the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and the multiplexing identification information is used to identify media streams within a multiplexed data packet over a single transport layer connection—second information regarding mapping between QFIs for media streams, multiplexing identification information, and a plurality of sets of QoS parameters, and a first indication indicating to a second device to obtain multiplexing identification information from a data packet; the step of obtaining multiplexing identification information from a data packet based on the protocol description and the first indication; and the step of mapping media streams to QoS streams identified by QFIs based on the multiplexing identification information and the second information regarding mapping.

[0049] Some implementations of the method described herein may include the step of obtaining QFIs for QoS flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters—each QFI being associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection—; and the step of mapping the media streams to QoS flows based on the second information regarding mapping.

[0050] Some implementations of the method described herein may include the step of providing a first device with multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a data packet and multiplexed over a single transport layer connection, wherein the protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams.

[0051] Some implementations of the method described herein may include the step of obtaining at least one alternate QoS profile from a first device through a transceiver, and each of the at least one alternate QoS profile includes at least an alternate PDU set QoS parameter for media streams.

[0052] It should be understood that the summary section is not intended to identify the essential or vital features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will be readily understood from the following description. Brief explanation of the drawing

[0053] FIGS. 1a and FIGS. 1b respectively illustrate examples of wireless communication systems that support QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. FIGS. 2 and FIGS. 3 each illustrate a signaling diagram illustrating an exemplary process that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. FIG. 4 illustrates a signaling diagram illustrating an exemplary process that supports improvements to alternative QoS profiles according to embodiments of the present disclosure. FIG. 5 illustrates an example of a device that supports improvements to QoS flow mapping or alternative QoS profiles for multiplexed media flows according to some embodiments of the present disclosure. FIG. 6 illustrates an example of a processor that supports improvements to QoS flow mapping or alternative QoS profiles for multiplexed media flows according to other embodiments of the present disclosure. FIGS. 7, FIGS. 8, FIGS. 9, FIGS. 10, and FIGS. 11 each illustrate flowcharts of a method for supporting QoS flow mapping for multiplexed media flows according to other embodiments of the present disclosure. Specific details for implementing the invention

[0054] Now, the principles of the present disclosure will be described with reference to some embodiments. These embodiments are described merely for illustrative purposes and are intended to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitation to the scope of the present disclosure. The disclosures described herein may be implemented in various ways other than those described below.

[0055] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as generally understood by a person skilled in the art to which this disclosure pertains.

[0056] References to “one embodiment,” “exemplary embodiment,” “embodiment,” “some embodiments,” and similar terms in this disclosure indicate that the described embodiment(s) may include a particular feature, structure, or characteristic, but not that all embodiments must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment(s). Moreover, where a particular feature, structure, or characteristic is described in relation to an embodiment, it is suggested that implementing such feature, structure, or characteristic in relation to other embodiments is within the knowledge of a person skilled in the art, whether or not explicitly described.

[0057] Additionally, it should be understood that while terms such as “first,” “second,” or similar terms are used in this specification to describe various elements, these elements are not limited by these terms. These terms are used merely to distinguish one element from another. For example, without going beyond the scope of the implementations, the first element may also be referred to as the second element, and likewise the second element may also be referred to as the first element. As used in this specification, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0058] The terms used herein are for the purpose of describing specific implementations only and are not intended to limit exemplary implementations. As used herein, the singular forms “a,” “an,” and “the” are intended to include plural forms unless the context clearly indicates otherwise. Furthermore, it will be further understood that as used herein, terms such as “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the mentioned features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0059] As described above, for the current 5GS QoS framework, when a service data stream is mapped onto a QoS stream, it has only a single set of QoS parameters and does not support differentiated QoS handling within a single QoS stream. Therefore, for multiplexed media streams on a single transport layer connection that share the same IP 5-tuple with different QoS requirements or parameters, it is essential to first distinguish and identify each of them, and then apply QoS stream mapping to each stream having different QoS requirements or parameters.

[0060] With the foregoing in mind, implementations of the present disclosure provide a solution that supports QoS flow mapping for multiplexed media flows. In one embodiment of the solution, a first device obtains multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a data packet and multiplexed over a single transport layer connection. The protocol description includes first information regarding where to obtain the multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams. Next, the first device determines QoS flow identifiers (QFIs) for the QoS flows, and each of the QFIs is associated with one of the media streams. Subsequently, the first device provides a second device or UE with second information regarding the mapping between the QFIs, the multiplexing identification information, and the plurality of sets of QoS parameters. Using this solution, the second device or UE can identify multiplexed media flows having different QoS requirements within a single transport layer connection. Next, the second device or UE can perform QoS flow mapping for media flows having different QoS requirements.

[0061] Aspects of the present disclosure are described in the context of a wireless communication system.

[0062] FIG. 1a illustrates an example of a wireless communication system (100A) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. The wireless communication system (100A) may include one or more network entities (102) (also referred to as network equipment (NE)), 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 LTE-Advanced (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 a 4G network and a 5G network, or other suitable radio access technology including IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system (100A) may support radio access technologies beyond 5G. Additionally, the wireless communication system (100A) may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0063] One or more network entities (102) may be distributed across a geographical area to form a wireless communication system (100A). One or more of the network entities (102) described herein may be network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms, may include or be referred to as such. In the following, some implementations of the disclosure will be described by taking a RAN node as an example of a network entity (102). Accordingly, a network entity (102) may be used interchangeably with a RAN node (102). For example, RAN nodes (102) may include a RAN node (102-1) and a RAN node (102-2).

[0064] Network entities (102) and UE (104) can communicate through a communication link (110) which may be a wireless or wired connection. For example, network entities (102) and UE (104) can perform wireless communication (e.g., receiving signaling, transmitting signaling) through a Uu interface.

[0065] A network entity (102) may provide a geographic coverage area (112), and the network entity (102) 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, the network entity (102) and the UE (104) may support wireless communication of signals related to the services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, the network entity (102) may be mobile and may be, 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 any of several different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification may be represented as voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0066] One or more UEs (104) may be distributed across the geographical area of ​​the wireless communication system (100A). The UE (104) may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or any other suitable term. In some implementations, the UE (104) may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, the UE (104) may be referred to as an Internet-of-things (IoT) device, Internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, the UE (104) may be fixed within the wireless communication system (100A). In some other implementations, the UE (104) may be mobile within the wireless communication system (100A).

[0067] One or more UEs (104) may be devices having different forms or different capabilities. Some examples of UEs (104) are illustrated in FIG. 1. As illustrated in FIG. 1, the UE (104) may communicate with various types of devices, such as network entities (102), other UEs (104), or network equipment (e.g., a core network (106), a data network (108), relay devices, integrated access and backhaul (IAB) nodes, or other network equipment). Additionally or alternatively, the UE (104) may support communication with other network entities (102) or UEs (104) that can act as relays within the wireless communication system (100A).

[0068] The UE (104) may also support direct wireless communication with other UEs (104) via a communication link (114). For example, the UE (104) may support direct wireless communication with other UEs (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, the communication link (114) may be referred to as a sidelink. For example, the UE (104) may support direct wireless communication with other UEs (104) via a PC5 interface.

[0069] A network entity (102) may support communication with a core network (106), other network entities (102), or both. For example, a network entity (102) may interface with the core network (106) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). Network entities (102) may communicate with each other through backhaul links (116) (e.g., through X2, Xn or other network interfaces). 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., through the core network (106)). In some implementations, one or more network entities (102) may include subcomponents such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs (104) through one or more other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0070] In some implementations, the network entity (102) may be configured as a disaggregated architecture, which may be configured to use protocol stacks that are physically or logically distributed between two or more network entities (102), such as an integrated access backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration overseen by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entity (102) may include one or more of 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.

[0071] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). One or more components of network entities (102) within a segregated RAN architecture may be co-located, or one or more components of network entities (102) may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities (102) of a segregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional partitioning between the CU, DU, and RU can be flexible and support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, functional partitioning of the protocol stack can be utilized between the CU and the DU, thereby allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host functions and signaling of higher protocol layers (e.g., Layer 3 (L3), Layer 2 (L2)) (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). A CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host the functionality and signaling of lower protocol layers, for example, Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each may be at least partially controlled by the CU (160).

[0073] Additionally or alternatively, functional partitioning of the protocol stack may be utilized between the DU and the RU, thereby allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., through one or more RUs). In some implementations, functional partitioning between the CU and the DU, or between the DU and the RU, may be performed within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by the other of the CU, DU, or RU).

[0074] The CU can be functionally further divided into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and 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 communication links or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of the protocol stack supported by their respective network entities (102) communicating through such communication links.

[0075] The core network (106) may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network (106) may be an evolved packet core (EPC) or a 5G core (5GC), and may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)), and a user plane entity that routes packets or interconnects them to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, a control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs (104) served by one or more network entities (102) associated with a core network (106).

[0076] The core network (106) may communicate with the data network (108) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). The data network (108) may include an application server (118). In some implementations, one or more UEs (104) may communicate with the application server (118). The UE (104) may establish a session with the core network (106) (e.g., a Protocol Data Unit (PDU) session or similar) through a network entity (102). The core network (106) may route traffic (e.g., control information, data, and similar) between the UE (104) and the application server (118) using the established session (e.g., an established PDU session). A PDU session may be an example of a logical connection between a UE (104) and a core network (106) (e.g., one or more network functions of the core network (106)).

[0077] In a wireless communication system (100A), network entities (102) and UEs (104) can perform various operations (e.g., wireless communications) using the resources of the wireless communication system (100A) (e.g., time resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)). In some implementations, network entities (102) and UEs (104) may support different resource structures. For example, network entities (102) and UEs (104) may support different frame structures. In some implementations, for example in 4G, network entities (102) and UEs (104) may support a single frame structure. In some other implementations, for example in 5G and among other suitable radio access technologies, network entities (102) and UEs (104) can support various frame structures (i.e., multiple frame structures). Network entities (102) and UEs (104) can support various frame structures based on one or more numerologies.

[0078] One or more numerologies may be supported in a wireless communication system (100A), and the numerologies may include subcarrier spacing and cyclic prefixes. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may use one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a general cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a general cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a general cyclic prefix.

[0079] The time intervals of a resource (e.g., a communication resource) can be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe within a frame may have the same duration.

[0080] Additionally or alternatively, the time intervals of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may contain a number (e.g., a large number) of slots. The number of slots within each subframe may also depend on one or more numerologies supported by the wireless communication system (100A). For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with their respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may each use a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe. Each slot may contain a number (e.g., a large number) of symbols (e.g., OFDM symbols). In some implementations, the number of slots per subframe (e.g., quantity) may depend on the numerology. For a standard cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the standard cyclic prefix and the extended cyclic prefix may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0081] In a wireless communication system (100A), the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system (100A) may support one or more operating frequency bands such as frequency range designations 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 entities (102) and UEs (104) may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by network entities (102) and UEs (104) among other equipment or devices for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by network entities (102) and UEs (104) among other equipment or devices for short-range, high data rate capabilities.

[0082] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology including 15 kHz subcarrier spacing (e.g., =0); a second numerology including 30 kHz subcarrier spacing (e.g., =1); and a third numerology including 60 kHz subcarrier spacing (e.g., =2). FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology including 60 kHz subcarrier spacing (e.g., =2); and a fourth numerology including 120 kHz subcarrier spacing (e.g., =3).

[0083] FIG. 1b illustrates an example of a wireless communication system (100B) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Specifically, FIG. 1b illustrates network entities or network functions (NFs) within a core network (106) as illustrated in FIG. 1a.

[0084] As illustrated in FIG. 1b, the core network (106) may include at least a session management function (SMF) (120), a user plane function (UPF) (130), a policy control function (PCF) (140), a network exposure function (NEF) (150), an application function (AF) (160), and an access and mobility management function (AMF) (170).

[0085] In some implementations, the AMF (170) can communicate with the RAN node (102) and the SMF (120) through the N2 interface and the N11 interface, respectively.

[0086] In some implementations, the SMF (120) can communicate with the UPF (130) and PCF (140) through the N4 interface and N7 interface, respectively.

[0087] In some implementations, the UPF (130) can communicate with the RAN node (102) and the DN (108) through the N3 interface and the N6 interface, respectively. In some implementations, the UPF (130) may include a PDU session anchor (PSA) UPF.

[0088] In some implementations, the core network (106) may include two or more UPFs. In such implementations, one UPF may communicate with another UPF through the N9 interface.

[0089] In some implementations, the NEF (150) can communicate with the PCF (140) and AF (160) through the N30 interface and N33 interface, respectively.

[0090] FIG. 2 illustrates a signaling diagram illustrating an exemplary process (200) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. The process (200) may involve a RAN node (102) of FIG. 1a or FIG. 1b, an NEF (150), an AF (160), and a DN (108) of FIG. 1b. The process (200) may also involve a first device, a second device, and a third device. In some implementations, the first device may perform the SMF (120) of FIG. 1b. Alternatively, the first device may perform other network functions other than the SMF (120) of FIG. 1b. In some implementations, the second device may perform the UPF (130) of FIG. 1b. Alternatively, the second device may perform other network functions other than the UPF (130) of FIG. 1b. In some implementations, the third device may perform the PCF (140) of FIG. 1b. Alternatively, the third device may perform other network functions other than the PCF (140) of FIG. 1b. For the purposes of discussion, the process (200) will be described with reference to FIG. 1b. The process (200) may involve the RAN node (102), UPF (130), SMF (120), PCF (140), NEF (150), AF (160), and DN (108) of FIG. 1b.

[0091] As illustrated in FIG. 2, AF (160) may provide NEF (150) with multiplexing identification information and protocol descriptions associated with multiple sets of QoS parameters for media streams (210). Media streams are carried in data packets and multiplexed over a single transport layer connection. The protocol description includes first information regarding where to obtain multiplexing identification information from the data packets. Multiplexing identification information is used to identify the media streams.

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

[0093] 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 obtaining multiplexing identification information from an RTP header extension for a data packet based on the RTP protocol.

[0094] In some implementations, the protocol description may additionally indicate the transport protocol used by the service data stream or media stream (e.g., RTP, Secure Real-time Transport Protocol (SRTP)), transport protocol header extensions (e.g., RTP header extensions for marking PDU sets 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).

[0095] In some implementations, the multiplexing identification information may include at least one of the identity (ID) of a transport layer connection or the IDs of media streams. For example, if a single transport layer connection may include a connection based on the QUIC protocol, the ID of the transport layer connection may include a connection ID, and the IDs of the media streams may include stream IDs.

[0096] 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 a stream type, this means that application data is transmitted over a QUIC connection. A stream refers to a unidirectional or bidirectional channel for sequential bytes in a QUIC connection. A QUIC connection can carry multiple media streams simultaneously.

[0097] In some implementations, a stream ID can be used to distinguish multiple streams within the same QUIC connection (having the same connection ID). When a stream ID is generated, it is guaranteed to be unique and distinct within this QUIC connection. That is, the stream ID is unique among all streams within the connection and can therefore be used to detect and identify different multiplexed media streams. In the case of the QUIC protocol, the connection ID and stream ID can be used individually or combined to uniquely identify a media stream among multiplexed media streams.

[0098] Hereinafter, some implementations of the present disclosure will be described by taking a connection ID and a stream ID as examples of multiplexing identification information. It will be understood that the multiplexing identification information may include any suitable information for identifying media streams based on the transport layer protocol applied to the present disclosure.

[0099] In some implementations, AF (160) may provide multiplexing identification information associated with multiple sets of QoS parameters. That is, AF (160) may provide a mapping between multiplexing identification information and multiple sets of QoS parameters.

[0100] For example, the mapping between multiple sets of multiplexing identification information and QoS parameters may include connection ID#X1+stream ID#Y1>>>QoS parameter set#1, connection ID#X2+stream ID#Y2>>>QoS parameter set#2.

[0101] As another example, the mapping between multiple sets of multiplexing identification information and QoS parameters may include stream ID#X1>>>QoS parameter set#1, stream ID#X2>>QoS parameter set#2.

[0102] In some implementations, AF (160) may additionally provide a flow description of the AF session to NEF (150) along with multiplexing identification information associated with a plurality of sets of QoS parameters. In such implementations, the flow description may be a packet filter set including direction, source and destination IP addresses, protocol, source and destination port numbers, etc. For example, the packet filter set may be an IP packet filter set or an Ethernet packet filter set. Alternatively, the flow description may be an application identifier (i.e., AppID).

[0103] In some implementations, different media streams may have different Forward Error Correction (FEC) rates associated with PDU Set Importance (PSI) values ​​for potential PDU set discarding at the RAN node (102). Thus, in addition to the mapping of multiple sets of multiplexing identification information and QoS parameters, AF (160) may additionally provide NEF (150) with a mapping between multiplexing identification information and FEC rates. For example, the mapping between multiplexing identification information, FEC rates, and PDU set QoS parameters may include Connection ID #X1 + Stream ID #Y1 >>> PSI Value #1 >> FEC Rate X%.

[0104] In some implementations, different media streams may have different PDU set QoS parameters. Therefore, in addition to mapping multiple sets of multiplexing identification information and QoS parameters, AF (160) may additionally provide NEF (150) with mapping between multiplexing identification information and PDU set QoS parameters. For example, mapping between multiplexing identification information and PDU set QoS parameters may include connection ID#X1+stream ID#Y1>>PDU set QoS parameters #1.

[0105] Regarding the FEC ratios associated with PSI values, it should be noted that the PDU set importance list may be associated with the same FEC ratio X%, or the PDU set importance list may be associated with different FEC ratios. For example, PSI value #1 may be associated with FEC ratio X%, PSI value #2 with FEC ratio Y%, PSI value #3 with FEC ratio Z%, and so on.

[0106] In some implementations, AF (160) may send an Nnef_AFsessionWithQoS_Create message to NEF (150). The Nnef_AFsessionWithQoS_Create message may include multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters.

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

[0108] When the Nnef_AFsessionWithQoS_Create message is received, the NEF (150) authorizes the AF request for the AF session having the requested QoS parameters (215) and can control the total amount of QoS authorized for the AF (160) by applying policies. If authorization is not granted, the NEF (150) responds to the AF (160) with a result value indicating that authorization failed. Alternatively, in the case of a trusted AF, the AF (160) can provide these parameters directly to the PCF (140) without the involvement of the NEF (150).

[0109] After successful authorization, the NEF (150) can provide the PCF (140) with multiplexing identification information and protocol descriptions associated with multiple sets of QoS parameters (220).

[0110] In some implementations, the NEF (150) may additionally provide a flow description to the PCF (140).

[0111] In some implementations, the NEF (150) may additionally provide the PCF (140) with a mapping between the multiplexing identification information and the FEC ratio.

[0112] In some implementations, the NEF (150) may additionally provide the PCF (140) with a mapping between the multiplexing identification information and the PDU set QoS parameters.

[0113] In some implementations, the NEF (150) may send an Npcf_PolicyAuthorization_Create message to the PCF (140). The Npcf_PolicyAuthorization_Create message may include multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters.

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

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

[0116] Next, PCF (140) can provide multiplexing identification information and protocol description associated with multiple sets of QoS parameters to SMF (120) (225).

[0117] In some implementations, the PCF (140) may additionally provide a flow description to the SMF (120).

[0118] In some implementations, the PCF (140) may additionally provide the SMF (120) with a mapping between the multiplexing identification information and the FEC ratio.

[0119] In some implementations, the PCF (140) may additionally provide the SMF (120) with a mapping between the multiplexing identification information and the PDU set QoS parameters.

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

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

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

[0123] In some implementations, the SMF (120) may be additionally preconfigured with other information or parameters as described above.

[0124] Ultimately, the SMF (120) determines the QFIs for the QoS streams (230). Each QFI is associated with one of the media streams.

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

[0126] Next, the SMF (120) provides the following to the UPF (130) (235): a protocol description; second information regarding the mapping between multiple sets of QFIs, multiplexing identification information and QoS parameters; and a first indication to the UPF (130) to obtain multiplexing identification information from a data packet.

[0127] In some implementations, second information regarding the mapping between multiple sets of QFIs, multiplexing identification information, and QoS parameters may include the following:

[0128] · QFI#1---Connection ID #X1+Stream ID#Y1---QoS Parameter Set #1, and

[0129] · QFI#2---Connection ID #X2+Stream ID#Y2---QoS Parameter Set #2.

[0130] In some implementations, the SMF (120) may transmit the PDR to the UPF (130). The PDR may include second information and a first indication regarding the mapping. The PDR may include both the DL portion and the UL portion of a Service Data Flow (SDF) template.

[0131] In some implementations, the SMF (120) may further transmit a mark from a QoS enforcement rule (QER) to the UPF (130) to indicate to the UPF (130) regarding multiplexing information identification. Upon receiving the mark and protocol description, the UPF (130) will know when and how to obtain multiplexing identification information from the DL data packet and will perform the following QFI decisions for the QoS flows.

[0132] In some implementations, optionally, the SMF (120) may provide a second indication to the RAN node (102) indicating that the QoS flows are associated with a single transport layer connection (240). For example, the SMF (120) may provide the second indication in an N2 SM message via the AMF (170). The second indication may be used by the RAN node (102) for potential sequential processing between multiple media streams, if necessary.

[0133] In some implementations, the SMF (120) may additionally provide the RAN node (102) with a QoS profile that includes QFIs, 5QIs, an Address Resolution Protocol (ARP), multiple sets of QoS parameters and PDU set QoS parameters, and a PSI-FEC ratio mapping list. The RAN node (102) may determine the FEC ratio by checking the GTP-U header of a DL packet from the UPF (130) to obtain the PSI and performing packet discarding. The RAN node (102) may perform PDU set-based handling based on the PDU set QoS parameters.

[0134] After receiving a DL data packet from an application server (118) within a DN (108) (245), the UPF (130) obtains multiplexing identification information from the data packet based on a protocol description and a first indication (250).

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

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

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

[0138] UPF (130) maps media streams to QoS streams identified by QFIs based on second information regarding mapping between multiplexing identification information and QFIs, multiplexing identification information and multiple sets of QoS parameters (255).

[0139] After obtaining multiplexing identification information, UPF (130) will be able to identify each of the media streams having unique identification information. Next, by checking the list of correspondences between the multiplexing identification information and QFIs associated with the QoS parameters received from SMF (120), UPF (130) can map the multiplexed media streams in the service data stream to corresponding QoS streams marked by QFIs having different QoS parameters based on the service data stream template and the multiplexing identification information.

[0140] After receiving a DL data packet from the UPF (130), the RAN node (102) maps the QoS flows to air interface resources (i.e., DRBs in the case of a 3GPP RAN) and sends the data packet to the UE (104).

[0141] In process (200), the UPF (130) can identify multiplexed media flows with different QoS requirements within a single transport layer connection. Next, the UPF (130) can perform QoS flow mapping for the media flows with different QoS requirements.

[0142] FIG. 3 illustrates a signaling diagram illustrating an exemplary process (300) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. The process (300) may involve a UE (104) of FIG. 1a or FIG. 1b, an NEF (150) and an AF (160) of FIG. 1b. The process (300) may also involve a first device and a third device. In some implementations, the first device may perform the SMF (120) of FIG. 1b. Alternatively, the first device may perform other network functions other than the SMF (120) of FIG. 1b. In some implementations, the third device may perform the PCF (140) of FIG. 1b. Alternatively, the third device may perform other network functions other than the PCF (140) of FIG. 1b. For the sake of discussion, the process (300) will be described with reference to FIG. 1b. The process (300) may involve the UE (104), SMF (120), PCF (140), NEF (150) and AF (160) of FIG. 1b.

[0143] The actions (210, 215, 220, 225, and 230) in process (300) are identical to the actions in process (200). Details of these actions are omitted for brevity.

[0144] Process (300) is different from process (200) in actions (335, 340, 345 and 350).

[0145] Specifically, the SMF (120) provides the UE (104) with second information regarding the mapping between multiple sets of QFIs, multiplexing identification information, and QoS parameters (335).

[0146] In some implementations, second information regarding the mapping between QFIs, multiplexing identification information, and multiple sets of QoS parameters may include the following:

[0147] ·QFI#1---Connection ID #X1+Stream ID#Y1---QoS Parameter Set #1, and

[0148] ·QFI#2---Connection ID #X2+Stream ID#Y2---QoS Parameter Set #2.

[0149] In some implementations, based on PCC rules from PCF (140), SMF (120) may generate an explicitly signaled QoS rule and provide it to UE (104). The QoS rule may include second information regarding mapping.

[0150] In some implementations, QoS rules may additionally include a set of packet filters generated from UL SDF filters.

[0151] In some implementations, the SMF (120) may additionally provide the UE (104) with a protocol description to help the UE (104) obtain multiplexing identification information. For example, the SMF (120) may provide the protocol description to the UE (104) along with QoS rules.

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

[0153] In some implementations, the SMF (120) may additionally provide the UE (104) with a first indication indicating that the UE (104) should obtain multiplexing identification information from a data packet. In these implementations, the UE (104) can obtain multiplexing identification information from a data packet based on the protocol description and the first indication.

[0154] Alternatively, in some implementations, the SMF (120) may not provide the first indication to the UE (104). The UE (104) may or may not use the protocol description to obtain multiplexing identification information from the UL data packet based on the implementation of the UE (104).

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

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

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

[0158] The UE (104) maps media streams to QoS streams identified by QFIs based on multiplexing identification information and second information regarding mapping between multiple sets of QFIs, multiplexing identification information and QoS parameters (350).

[0159] In some implementations, the UE (104) can mark the UL PDU with QFI.

[0160] Next, the UE (104) can transmit UL PDUs using the corresponding access-specific resources for the QoS flow based on the mapping provided by the RAN node (102). The RAN node (102) transmits the PDUs through the N3 tunnel toward the UPF (130), including the QFI within the encapsulation header of the UL PDU.

[0161] After obtaining multiplexing identification information, the UE (104) will be able to identify each of the media streams having unique identification information. Next, by checking the list of correspondences between the multiplexing identification information and QFIs associated with the QoS parameters received from the SMF (120), the UE (104) can map the multiplexed media streams in the service data stream to corresponding QoS streams marked by QFIs having different QoS parameters, based on the service data stream template and the multiplexing identification information.

[0162] After receiving a UL data packet from the UE (104), the RAN node (102) maps the QoS flows to air interface resources (i.e., DRBs in the case of a 3GPP RAN) and sends the data packet to the UPF (130).

[0163] In process (300), the UE (104) can identify multiplexed media flows having different QoS requirements within a single transport layer connection. Next, the UE (104) can perform QoS flow mapping for the media flows having different QoS requirements.

[0164] Below, some implementations for improvements to alternative QoS profiles will be described with reference to FIG. 4.

[0165] In some implementations, PDU set QoS parameters are used to support PDU set-based QoS handling at the RAN node (102). To enable PDU set-based QoS handling, at least one PDU set QoS parameter will be sent to the RAN node (102).

[0166] Currently, legacy alternative QoS profiles include PDU Error Rate (PER), PDU Delay Budget (PDB), Guaranteed Flow Bit Rate (GFBR), Averaging Window, and Arbitrarily Maximum Data Burst Volume (MDBV), but PDU Set QoS parameters are not included in legacy alternative QoS profiles. Therefore, it is necessary to improve legacy alternative QoS profiles with PDU Set QoS parameters.

[0167] FIG. 4 illustrates a signaling diagram illustrating an exemplary process (400) that supports improvements to alternative QoS profiles according to embodiments of the present disclosure. The process (400) may involve a RAN node (102-1) of FIG. 1a or FIG. 1b, an NEF (150) and an AF (160) of FIG. 1b. The process (400) may also involve a first device, a second device, and a third device. In some implementations, the first device may perform the SMF (120) of FIG. 1b. Alternatively, the first device may perform other network functions other than the SMF (120) of FIG. 1b. In some implementations, the third device may perform the PCF (140) of FIG. 1b. Alternatively, the third device may perform other network functions other than the PCF (140) of FIG. 1b. For the sake of discussion, the process (400) will be described with reference to FIG. 1b. The process (400) may include the RAN node (102-1), SMF (120), PCF (140), NEF (150), and AF (160) of FIG. 1b.

[0168] As illustrated in FIG. 4, AF (160) can provide alternative PDU set QoS parameters for media streams to NEF (150) (410).

[0169] In some implementations, alternate PDU set QoS parameters may include alternate UL PDU set QoS parameters for QoS flows and alternate DL PDU set QoS parameters for QoS flows. The alternate UL PDU set QoS parameters for QoS flows may be the same or different from the alternate DL PDU set QoS parameters for QoS flows.

[0170] In some implementations, alternative UL PDU set QoS parameters may include at least one of the UL PDU set delay budget (PSDB), UL PDU set error rate (PSER), or UL PDU set aggregation handling information (PSIHI).

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

[0172] In some implementations, AF (160) may provide a plurality of alternate PDU set QoS parameter sets to NEF (150). Each of the plurality of alternate PDU set QoS parameter sets may include alternate UL PDU set QoS parameters.

[0173] In some implementations, a priority may be assigned to each of the multiple alternate PDU set QoS parameter sets. AF (160) may provide the multiple alternate PDU set QoS parameter sets to NEF (150) in an order of priorities for the multiple alternate PDU set QoS parameter sets. That is, AF (160) may provide the multiple alternate PDU set QoS parameter sets to NEF (150) in a prioritized order.

[0174] In some implementations, AF (160) may provide alternative service requirements to NEF (150). The alternative service requirements may include alternative QoS parameter sets and alternative PDU set QoS parameter sets.

[0175] In some implementations, AF (160) may additionally provide QoS parameters and PDU set QoS parameters to NEF (150).

[0176] In some implementations, AF (160) may additionally provide a flow description of the AF session to NEF (150) along with alternate PDU set QoS parameters. In such implementations, the flow description may be a packet filter set including direction, source and destination IP addresses, protocol, source and destination port numbers, etc. For example, the packet filter set may be an IP packet filter set or an Ethernet packet filter set. Alternatively, the flow description may be an application identifier (i.e., AppID).

[0177] In some implementations, AF (160) may send an Nnef_AFsessionWithQoS_Create message to NEF (150). The Nnef_AFsessionWithQoS_Create message may include alternate PDU Set QoS parameters.

[0178] In some implementations, the Nnef_AFsessionWithQoS_Create message may additionally include at least one of a flow description, QoS parameters, a set of PDU QoS parameters, or an alternative set of QoS parameters.

[0179] When the Nnef_AFsessionWithQoS_Create message is received, the NEF (150) authorizes the AF request for the AF session with the requested QoS parameters (415) and can control the total amount of QoS authorized to the AF (160) by applying policies. If authorization is not granted, the NEF (150) responds to the AF (160) with a result value indicating that authorization failed. Alternatively, in the case of a trusted AF, the AF (160) may provide these parameters directly to the PCF (140) without the involvement of the NEF (150).

[0180] After successful authorization, NEF (150) can provide PCF (140) with alternative PDU set QoS parameters (420).

[0181] In some implementations, the NEF (150) may provide the PCF (140) with a number of alternate PDU set QoS parameter sets. Each of the number of alternate PDU set QoS parameter sets may include alternate UL PDU set QoS parameters. For example, the NEF (150) may provide the PCF (140) with a number of alternate PDU set QoS parameter sets in a prioritized order.

[0182] In some implementations, the NEF (150) may additionally provide alternative service requirements to the PCF (140). The alternative service requirements may include alternative QoS parameter sets and alternative PDU set QoS parameter sets.

[0183] In some implementations, the NEF (150) may additionally provide the PCF (140) with QoS parameters and PDU set QoS parameters.

[0184] In some implementations, the NEF (150) may additionally provide a flow description to the PCF (140).

[0185] In some implementations, the NEF (150) may send an Npcf_PolicyAuthorization_Create message to the PCF (140). The Npcf_PolicyAuthorization_Create message may include alternate PDU Set QoS parameters.

[0186] In some implementations, the Npcf_PolicyAuthorization_Create message may additionally include at least one of a flow description, QoS parameters, PDU set QoS parameters, or alternative sets of QoS parameters.

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

[0188] Next, PCF (140) can provide alternative PDU set QoS parameters to SMF (120) (425).

[0189] In some implementations, PCF (140) may additionally provide SMF (120) alternative QoS parameters, QoS parameters, and PDU set QoS parameters.

[0190] In some implementations, the PCF (140) may additionally provide a flow description to the SMF (120).

[0191] In some implementations, PCF (140) may additionally provide a third mark to SMF (120).

[0192] In some implementations, the third indication may indicate to the RAN node (102-1) that if the QoS profile is not satisfied, the SMF (120) should provide fourth information regarding at least one substitute PDU set QoS parameter that is satisfied among the substitute PDU set QoS parameters.

[0193] In some implementations, the fourth information regarding at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters may include an index of an alternate QoS profile containing at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters, or at least one of a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters.

[0194] Alternatively, in some implementations, the third indication may indicate to the RAN node (102-1) that if the QoS profile is not satisfied, information regarding at least one alternative UL PDU set QoS parameter among the alternative UL PDU set QoS parameters is satisfied be provided to the SMF (120), and to the RAN node (102-1) that if the QoS profile is not satisfied, information regarding at least one alternative UL PDU set QoS parameter among the alternative UL PDU set QoS parameters is satisfied be provided to the SMF (120).

[0195] In some implementations, information regarding at least one alternate UL PDU set QoS parameter satisfied among alternate UL PDU set QoS parameters may include at least one of a first index of a first alternate QoS profile for a UL containing at least one alternate UL PDU set QoS parameter satisfied among alternate UL PDU set QoS parameters, or a seventh indication of at least one alternate UL PDU set QoS parameter satisfied among alternate UL PDU set QoS parameters.

[0196] In some implementations, information regarding at least one alternate DL PDU set QoS parameter satisfied among alternate DL PDU set QoS parameters may include a second index of a second alternate QoS profile for a DL containing at least one alternate DL PDU set QoS parameter satisfied among the satisfied alternate DL PDU set QoS parameters, or at least one of an eighth indication of at least one alternate DL PDU set QoS parameter satisfied among the alternate DL PDU set QoS parameters.

[0197] In some implementations, the PCF (140) may additionally provide a QoS notification control (QNC) indication to the SMF (120). The QNC indication indicates whether notifications are requested from the RAN node (102-1) when the GFBR can no longer guarantee (or can again guarantee) for the QoS flow during the lifetime of the QoS flow. The GFBR is included in the legacy alternate QoS profile.

[0198] In some implementations, the PCF (140) can generate PCC rules and send the PCC rules to the SMF (120). The PCC rules may include alternate PDU set QoS parameters.

[0199] In some implementations, PCC rules may additionally include at least one of a flow description, QoS parameters, alternate QoS parameters, PDU set QoS parameters, QNC indication, or third indication.

[0200] When receiving alternate PDU set QoS parameters, the SMF (120) generates at least one alternate QoS profile (430). Each of the at least one alternate QoS profile includes at least the alternate PDU set QoS parameters.

[0201] In some implementations, at least one alternate QoS profile may include at least one dedicated alternate QoS profile.

[0202] In some implementations, at least one dedicated alternate QoS profile may include at least one dedicated alternate QoS profile for UL and at least one dedicated alternate QoS profile for DL. Hereinafter, the dedicated alternate QoS profile for UL is also referred to as the "alternative UL PDU set QoS profile," and the dedicated alternate QoS profile for DL ​​is also referred to as the "alternative DL PDU set QoS profile."

[0203] In some implementations, the alternative UL PDU set QoS profile may include at least one of UL PSDB, UL PSER, or UL PSIHI.

[0204] In some implementations, the alternate DL PDU set QoS profile may include at least one of DL PSDB, DL PSER, or DL ​​PSIHI.

[0205] In some implementations, the alternate UL PDU set QoS profile may additionally include UL GFBR, and the alternate DL PDU set QoS profile may additionally include DL GFBR.

[0206] In some implementations, the SMF (120) may additionally generate a QoS profile, and the QoS profile may include QoS parameters and PDU set QoS parameters.

[0207] In some implementations, the SMF (120) may additionally generate at least one legacy alternate QoS profile. Each of the at least one legacy alternate QoS profile may include one of the alternate QoS parameter sets. Each of the alternate QoS parameter sets may include at least one of PER, PDB, GFBR, averaging window, and optionally MDBV.

[0208] In some implementations, the SMF (120) may add alternate PDU set QoS parameters to the legacy alternate QoS profile to obtain an upgraded alternate QoS profile. In such implementations, the upgraded alternate QoS profile may include at least one of PER, PDB, UL GFBR, DL GFBR, average window, MDBV, UL PSDB, UL PSER, ULPSIHI, DL PSDB, DL PSER, or DL ​​PSIHI. That is, each of at least one alternate QoS profile may include at least one of PER, PDB, UL GFBR, DL GFBR, average window, MDBV, UL PSDB, UL PSER, ULPSIHI, DL PSDB, DL PSER, or DL ​​PSIHI.

[0209] Next, the SMF (120) provides at least one alternate QoS profile to the RAN node (102-1). For example, the SMF (120) can provide at least one alternate QoS profile to the RAN node (102-1) through the AMF (170) via NAS signaling.

[0210] In some implementations, the SMF (120) can provide at least one alternate UL PDU set QoS profile to the RAN node (102-1) (435).

[0211] In some implementations, a priority may be assigned to each of at least one alternate UL PDU set QoS profile. The SMF (120) may provide at least one alternate UL PDU set QoS profile to the RAN node (102-1) in an order of priorities for at least one alternate UL PDU set QoS profile. That is, the SMF (120) may provide at least one alternate UL PDU set QoS profile to the RAN node (102-1) in a prioritized order.

[0212] Alternatively or additionally, in some implementations, the SMF (120) may provide at least one alternate DL PDU set QoS profile to the RAN node (102-1).

[0213] In some implementations, a priority may be assigned to each of at least one alternate DL PDU set QoS profile. The SMF (120) may provide at least one alternate DL PDU set QoS profile to the RAN node (102-1) in an order of priorities for at least one alternate DL PDU set QoS profile. That is, the SMF (120) may provide at least one alternate DL PDU set QoS profile to the RAN node (102-1) in a prioritized order.

[0214] In some implementations, the SMF (120) may additionally provide a third mark to the RAN node (102-1).

[0215] In some implementations, the third indication may indicate to the RAN node (102-1) that if the QoS profile is not satisfied, the SMF (120) should provide fourth information regarding at least one substitute PDU set QoS parameter that is satisfied among the substitute PDU set QoS parameters.

[0216] Alternatively, in some implementations, the third indication may indicate to the RAN node (102-1) that if the QoS profile is not satisfied, information regarding at least one alternative UL PDU set QoS parameter among the alternative UL PDU set QoS parameters is satisfied be provided to the SMF (120), and to the RAN node (102-1) that if the QoS profile is not satisfied, information regarding at least one alternative DL PDU set QoS parameter among the alternative DL PDU set QoS parameters is satisfied be provided to the SMF (120).

[0217] In some implementations, the SMF (120) may additionally provide at least one of a QoS profile or a QNC indication to the RAN node (102-1).

[0218] In some implementations, the SMF (120) may additionally provide at least one legacy alternate QoS profile to the RAN node (102-1).

[0219] In some implementations, a priority may be assigned to each of at least one legacy replacement QoS profile. The SMF (120) may provide at least one legacy replacement QoS profile to the RAN node (102-1) in an order of priorities for at least one legacy replacement QoS profile. That is, the SMF (120) may provide at least one legacy replacement QoS profile to the RAN node (102-1) in a prioritized order.

[0220] When a QoS profile is received, the RAN node (102-1) can determine whether the QoS parameters within the QoS profile can be satisfied (440). If at least one of the QoS parameters within the QoS profile cannot be satisfied and the RAN node (102-1) supports PDU set-based handling, the RAN node (102-1) can further determine whether the PDU set QoS parameters within the QoS profile can be satisfied.

[0221] If at least one of the PDU set QoS parameters in the QoS profile cannot be satisfied, the RAN node (102-1) may further determine whether the alternative PDU set QoS parameters in at least one alternative QoS profile can be satisfied (445). For example, the RAN node (102-1) may determine whether the alternative PDU set QoS parameters in at least one alternative QoS profile can be satisfied in descending order of priorities for at least one alternative QoS profile.

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

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

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

[0225] Alternatively or additionally, in some implementations, the RAN node (102-1) may provide the SMF (120) with fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among the alternative PDU set QoS parameters when the QoS profile cannot be satisfied.

[0226] In some implementations, the fourth information regarding at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters may include an index of an alternate QoS profile containing at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters, or at least one of a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters.

[0227] As described above, in some implementations, at least one alternate QoS profile may include at least one dedicated alternate QoS profile. In such implementations, the fourth information may include an index of an alternate QoS profile that includes at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters.

[0228] Alternatively, as described above, in some implementations, the SMF (120) may add alternate PDU set QoS parameters to the legacy alternate QoS profile to obtain an upgraded alternate QoS profile. In such implementations, the fourth information may include an index of the alternate QoS profile containing at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters, as well as a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters. Alternatively, in such implementations, the fourth information may include a fifth indication of at least one alternate PDU set QoS parameter satisfied among the alternate PDU set QoS parameters.

[0229] Alternatively, in some implementations, if the QoS profile cannot be satisfied, the RAN node (102-1) may provide information to the SMF (120) regarding at least one alternate UL PDU set QoS parameter that is satisfied among the alternate UL PDU set QoS parameters. The information regarding at least one alternate UL PDU set QoS parameter that is satisfied among the alternate UL PDU set QoS parameters may include at least one of a first index of a first alternate QoS profile for a UL containing at least one alternate UL PDU set QoS parameter that is satisfied among the alternate UL PDU set QoS parameters, or a seventh indication of at least one alternate UL PDU set QoS parameter that is satisfied among the alternate UL PDU set QoS parameters.

[0230] Alternatively or additionally, in some implementations, if the QoS profile cannot be satisfied, the RAN node (102-1) may provide information to the SMF (120) regarding at least one alternate DL PDU set QoS parameter that is satisfied among the alternate DL PDU set QoS parameters. The information regarding at least one alternate DL PDU set QoS parameter that is satisfied among the alternate DL PDU set QoS parameters may include at least one of a second index of a second alternate QoS profile for a DL containing at least one alternate DL PDU set QoS parameter that is satisfied among the alternate DL PDU set QoS parameters, or at least one of an eighth indication of at least one alternate DL PDU set QoS parameter that is satisfied among the alternate DL PDU set QoS parameters.

[0231] In some implementations, if at least one of the PDU set QoS parameters in the QoS profile cannot be satisfied, the RAN node (102-1) may further determine whether at least one alternative QoS parameter in an alternative QoS profile can be satisfied (445).

[0232] When receiving a fourth indication indicating that the QoS profile is not satisfied, a sixth indication indicating that the PDU set QoS parameters included in the QoS profile are not satisfied, or a fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among the alternative PDU set QoS parameters (450), the SMF (120) may provide (455) to the PCF (140) at least one of the fourth indication indicating that the QoS profile is not satisfied, or the fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among the alternative PDU set QoS parameters.

[0233] In some implementations, the SMF (120) can provide the fourth indication and fourth information to the PCF (140) through a policy control request trigger.

[0234] Next, PCF (140) can provide a fourth indication and fourth information to AF (160) (460).

[0235] In some implementations, PCF (140) can provide a fourth indication and fourth information to AF (160) through event reporting.

[0236] In some implementations, in the case of a handover scenario, the RAN node (102-1) may act as the target RAN node, and the RAN node (102-2) may act as the source RAN node. In such implementations, the RAN node (102-1) may provide the RAN node (120-2) with at least one of a fourth indication indicating that the QoS profile is not satisfied, or at least one of fourth information regarding at least one alternate PDU set QoS parameter that is satisfied among the alternate PDU set QoS parameters.

[0237] In some implementations, for Xn handover, the RAN node (102-1) may provide fourth information to the SMF (120) within the N2 path switching request message.

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

[0239] In some implementations, the process (400) may be performed in combination with any of the processes (200 and 300).

[0240] FIG. 5 illustrates an example of a device (500) that supports QoS flow mapping for multiplexed media flows according to some aspects of the present disclosure. The device (500) may be an example of the first device, second device, or UE (104) described herein. The device (500) may support wireless communication with one or more network entities (102), UEs (104), or any combination thereof. The device (500) may include components for bidirectional communication, such as a processor (502), memory (504), transceiver (506), and optionally, an I / O controller (508), for transmitting and receiving communications. These components may communicate electronically through one or more interfaces (e.g., a bus) or be combined in other ways (e.g., operablely, communically, functionally, electronically, electrically).

[0241] A processor (502), memory (504), transceiver (506), or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the disclosure described herein. For example, a processor (502), memory (504), transceiver (506), or various combinations thereof or components thereof may support a method for carrying out one or more of the operations described herein.

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

[0243] For example, the processor (502) may support wireless communication in the device (500) according to the examples disclosed herein. The processor (502) may be configured to be operable to support means for performing the following: obtaining multiplexing identification information and protocol descriptions associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection—the protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams—; determining QFIs for QoS streams—each of which is associated with one of the media streams—; and providing second information regarding the mapping between the QFIs, multiplexing identification information and a plurality of sets of QoS parameters to a second device or UE.

[0244] Alternatively, in some implementations, the processor (502) may be configured to be operable to support means for performing the following: obtaining from a first device a protocol description—the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and the multiplexing identification information is used to identify media streams within a multiplexed data packet over a single transport layer connection—second information regarding mapping between QFIs for media streams, multiplexing identification information, and a plurality of sets of QoS parameters, and a first indication indicating to the second device to obtain multiplexing identification information from a data packet; obtaining multiplexing identification information from a data packet based on the protocol description and the first indication; and mapping media streams onto QoS streams identified by QFIs based on the multiplexing identification information and the second information regarding mapping.

[0245] Alternatively, in some implementations, the processor (502) may be configured to operate to support means for performing mapping of media streams to QoS flows based on the second information regarding mapping, which includes obtaining QFIs for QoS flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters—each QFI being associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection—and mapping media streams to QoS flows.

[0246] Alternatively, in some implementations, the processor (502) may be configured to be operable to support means for performing the provision of multiplexing identification information and protocol description associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection to a first device, the protocol description includes first information regarding where to obtain multiplexing identification information from the downlink data packet, and the multiplexing identification information is used to identify the media streams.

[0247] Alternatively, in some implementations, the processor (502) may be configured to be operable to support means for performing at least one alternate QoS profile from the first device through a transceiver, and each of the at least one alternate QoS profile includes at least an alternate PDU set QoS parameters for media streams.

[0248] The processor (502) may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor (502) may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor (502). The processor (502) may be configured to execute computer-readable instructions stored in memory (e.g., memory (504)) to enable the device (500) to perform various functions of the present disclosure.

[0249] Memory (504) may include random access memory (RAM) and read-only memory (ROM). Memory (504) may store computer-readable, computer-executable code containing instructions that enable the device (500) to perform the various functions described herein when executed by the processor (502). The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some implementations, the code may not be directly executable by the processor (502), but may enable the computer to perform the functions described herein (e.g., during compilation and execution). In some implementations, memory (504) may include a basic I / O system (BIOS) capable of controlling basic hardware or software operations, such as interactions with devices, among other things, peripheral components or others.

[0250] The I / O controller (508) can manage input and output signals for the device (500). The I / O controller (508) can also manage peripherals that are not integrated into the device (M02). In some implementations, the I / O controller (508) may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller (508) may use an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, the I / O controller (508) may be implemented as part of a processor such as the processor (506). In some implementations, a user may interact with the device (500) through the I / O controller (508) or through a hardware component controlled by the I / O controller (508).

[0251] In some implementations, the device (500) may include a single antenna (510). However, in some other implementations, the device (500) may have more than one antenna (510) (i.e., multiple antennas) comprising multiple antenna panels or antenna arrays, which can transmit or receive multiple wireless transmissions simultaneously. The transceiver (506) may communicate bidirectionally through one or more antennas (510), wired links, or wireless links as described herein. For example, the transceiver (506) may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver (506) may also include a modem for modulating packets, providing the modulated packets to one or more antennas (510) for transmission, and demodulating packets received from one or more antennas (510). The transceiver (506) may include one or more transmission chains, one or more reception chains, or a combination thereof.

[0252] A transmission chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator to modulate data onto a carrier signal to prepare the signal for transmission over a wireless medium. The 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 air or a wireless medium.

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

[0254] FIG. 6 illustrates an example of a processor (600) that supports QoS flow mapping for multiplexed media flows according to other aspects of the present disclosure. The processor (600) may be an example of a processor configured to perform various operations according to the examples described herein. The processor (600) may include a controller (602) configured to perform various operations according to the examples described herein. The processor (600) may optionally include at least one memory (604). Additionally or alternatively, the processor (600) may optionally include one or more arithmetic logic units (ALUs) (606). One or more of these components may communicate electronically through one or more interfaces (e.g., buses) or otherwise be coupled (e.g., operablely, communically, functionally, electronically, electrically).

[0255] The processor (600) may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or contained in the processor chipset (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.).

[0256] A controller (602) may be configured to manage and coordinate various operations of the processor (600) (e.g., signaling, receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) so that the processor (600) may support various operations according to the examples described herein. For example, the controller (602) may operate as a control unit of the processor (600) and generate control signals that manage the operations of various components of the processor (600). These control signals include the activation or deactivation of function units, the selection of data paths, the initiation of memory access, and the timing adjustment of operations.

[0257] The controller (602) may be configured to fetch instructions from memory (604) (e.g., acquire, retrieve, receive) and determine subsequent instruction(s) to be executed, thereby enabling the processor (600) to support various operations according to the examples described herein. The controller (602) may be configured to track the memory addresses of instructions associated with memory (604). The controller (602) may be configured to decode instructions to determine the operations to be performed and the accompanying operands. For example, the controller (602) may be configured to interpret instructions and determine control signals to be output to other components of the processor (600) to enable the processor (600) to support various operations according to the examples described herein. Additionally or alternatively, the controller (602) may be configured to manage data flow within the processor (600). The controller (602) may be configured to control data transfer between the registers, arithmetic logic units (ALU), and other functional units of the processor (600).

[0258] Memory (604) may include one or more caches (e.g., memory local to or contained in the processor (600)) or other memory, e.g., RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory (604) may be located within or on the processor chipset (e.g., local to the processor (600)). In some other implementations, memory (604) may be located outside the processor chipset (e.g., remote from the processor (600)).

[0259] Memory (604) may store computer-readable, computer-executable code containing instructions that, when executed by the processor (600), cause the processor (600) to perform the various functions described herein. The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. The controller (602) and / or the processor (600) may be configured to execute the computer-readable instructions stored in the memory (604) to cause the processor (600) to perform various functions (e.g., functions or tasks that support transmission power prioritization). For example, the processor (600) and / or the controller (602) may be coupled to or with the memory (604), and the processor (600), the controller (602), and the memory (604) may be configured to perform the various functions described herein. In some examples, the processor (600) may include multiple processors, and the memory (604) may include multiple memories. One or more of the multiple processors may be combined with one or more of the multiple memories, and they may be configured to perform the various functions of this specification individually or collectively.

[0260] One or more ALUs (606) may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs (606) may be located in or on a processor chipset (e.g., processor (600)). In some other implementations, one or more ALUs (606) may be located outside the processor chipset (e.g., processor (600)). One or more ALUs (606) may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs (606) may receive input operands and an operation code that determines the operation to be executed. One or more ALUs (606) may be composed of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs (606) may support logical operations such as AND, OR, exclusive OR (XOR), negative OR (NOR), and negative AND (NAND), thereby enabling one or more ALUs (606) to handle conditional operations, comparisons, and bitwise operations.

[0261] The processor (600) may support wireless communication according to examples as disclosed in this specification. The processor (600) may be configured to be operable to support means for performing the following: obtaining multiplexing identification information and protocol descriptions associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection—the protocol description includes first information regarding where to obtain multiplexing identification information from the downlink data packet, and the multiplexing identification information is used to identify the media streams—; determining QFIs for QoS streams—each QFI is associated with one of the media streams—; and providing a second device or user equipment (UE) with second information regarding the mapping between the QFIs, multiplexing identification information, and a plurality of sets of QoS parameters.

[0262] Alternatively, in some implementations, the processor (600) may be configured to be operable to support means for performing the following: obtaining from a first device a protocol description—the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and the multiplexing identification information is used to identify media streams within a multiplexed data packet over a single transport layer connection—second information regarding mapping between QFIs for media streams, multiplexing identification information, and a plurality of sets of QoS parameters, and a first indication indicating to a second device to obtain multiplexing identification information from a data packet; obtaining multiplexing identification information from a data packet based on the protocol description and the first indication; and mapping media streams onto QoS streams identified by QFIs based on the multiplexing identification information and the second information regarding mapping.

[0263] Alternatively, in some implementations, the processor (600) may be configured to operate to support means for performing mapping of media streams to QoS flows based on the second information regarding mapping, such that it obtains QFIs for QoS flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters—each QFI being associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection—and mapping media streams to QoS flows.

[0264] Alternatively, in some implementations, the processor (600) may be configured to be operable to support means for performing the provision of multiplexing identification information and protocol description associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection to a first device, the protocol description includes first information regarding where to obtain multiplexing identification information from the downlink data packet, and the multiplexing identification information is used to identify the media streams.

[0265] Alternatively, in some implementations, the processor (600) may be configured to be operable to support means for performing the acquisition of at least one alternate QoS profile from the first device through a transceiver, and each of the at least one alternate QoS profile includes at least an alternate PDU set QoS parameters for media streams.

[0266] FIG. 7 illustrates a flowchart of a method (700) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Operations of the method (700) may be implemented by a device or its components as described herein. For example, operations of the method (700) may be performed by a first device as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0267] In 710, the method may include the step of obtaining multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection. The protocol description includes first information regarding where to obtain the multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams. The operations of 710 may be performed according to examples as described herein. In some implementations, aspects of the operations of 710 may be performed by a device as described with reference to FIG. 1b.

[0268] In 720, the method may include the step of determining QFIs for QoS flows, each QFI being associated with one of the media streams. The operations of 720 may be performed according to examples as described herein. In some implementations, aspects of the operations of 720 may be performed by a device as described with reference to FIG. 1b.

[0269] In 730, the method may include the step of providing a second device or UE with a plurality of sets of second information regarding mapping between QFIs, multiplexing identification information, and QoS parameters. The operations of 730 may be performed according to examples as described herein. In some implementations, aspects of the operations of 730 may be performed by a device as described with reference to FIG. 1b.

[0270] FIG. 8 illustrates a flowchart of a method (800) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Operations of the method (800) may be implemented by a device or its components as described herein. For example, operations of the method (800) may be performed by a second device as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0271] In 810, the method may include the step of obtaining from a first device a protocol description—the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and the multiplexing identification information is used to identify media streams within a multiplexed data packet over a single transport layer connection—second information regarding mapping between QFIs for media streams, multiplexing identification information, and a plurality of sets of QoS parameters, and a first indication indicating to a second device to obtain multiplexing identification information from a data packet. The operations of 810 may be performed according to examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a device as described with reference to FIG. 1b.

[0272] In 820, the method may include the step of obtaining multiplexing identification information from a data packet based on a protocol description and a first indication. The operations of 820 may be performed according to examples as described herein. In some implementations, aspects of the operations of 820 may be performed by a device as described with reference to FIG. 1b.

[0273] In 830, the method may include the step of mapping media streams onto QoS flows identified by QFIs based on multiplexing identification information and second information regarding mapping. The operations of 830 may be performed according to examples as described herein. In some implementations, aspects of the operations of 830 may be performed by a device as described with reference to FIG. 1b.

[0274] FIG. 9 illustrates a flowchart of a method (900) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Operations of the method (900) may be implemented by a device or its components as described herein. For example, operations of the method (900) may be performed by a UE (104) as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0275] In 910, the method may include the step of obtaining QFIs for QoS flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters, each of which is associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection. The operations of 910 may be performed according to examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to FIG. 1a or FIG. 1b.

[0276] In 920, the method may include the step of mapping media streams to QoS flows based on second information regarding mapping. The operations of 920 may be performed according to examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a device as described with reference to FIG. 1a or FIG. 1b.

[0277] FIG. 10 illustrates a flowchart of a method (1000) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Operations of the method (1000) may be implemented by a device or its components as described herein. For example, operations of the method (1000) may be performed by a third device as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0278] In 1010, the method may include the step of providing a first device with multiplexing identification information and a protocol description associated with a plurality of sets of QoS parameters for media streams carried in a downlink data packet and multiplexed over a single transport layer connection. The protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams. The operations of 1010 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to FIG. 1b.

[0279] FIG. 11 illustrates a flowchart of a method (1100) that supports QoS flow mapping for multiplexed media flows according to embodiments of the present disclosure. Operations of the method (1100) may be implemented by a device or its components as described herein. For example, operations of the method (1100) may be performed by a RAN node (102) as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0280] In 1110, the method may include the step of obtaining at least one alternate QoS profile from the first device. Each of the at least one alternate QoS profile includes at least an alternate PDU set QoS parameter for media streams. The operations of 1110 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1a or FIG. 1b.

[0281] It should be understood that the implementations of the present disclosure described with reference to FIGS. 1 through 4 are also applicable to the device (500), the processor (600), as well as the methods (700, 800, 900, 1000, 1100).

[0282] Additionally, it should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or modified in other ways, and other implementations are possible. Furthermore, aspects from two or more of the methods may be combined.

[0283] The various exemplary blocks and components described in connection with the disclosure of this specification may be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this specification. A 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 by 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).

[0284] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or code forms on a computer-readable medium or transmitted therethrough. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be located in various physical locations, including distributed so that parts of the functions are implemented in different physical locations.

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

[0286] As used herein, including in the claims, the article "a" preceding an element is not restricted and is understood to mean "at least one" of the elements or "one or more" of the elements. The terms article ("a"), "at least one," "one or more," and "at least one of one or more" may be interchangeable. When used in this specification, including in claims, the word “or” used in a list of items (e.g., a list of items accompanied by phrases such as “at least one of,” or “one or more of,” or “one or both of) indicates a comprehensive list; thus, 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, B, and C). Furthermore, when used in this specification, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, when used in this specification, the phrase “based on” should be interpreted in the same way as the phrase “at least partially based.” Furthermore, when used in this specification, including in claims, the “set” may include one or more elements.

[0287] This description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure is not limited to the examples and designs described herein, but should be given the broadest scope conforming to the principles and novel features disclosed herein.

Claims

Claim 1 A first device comprising: at least one memory; and at least one processor coupled to said at least one memory, wherein the at least one processor causes said first device to: obtain multiplexing identification information and a protocol description associated with a plurality of sets of Quality of Service (QoS) parameters for media streams carried in a data packet and multiplexed over a single transport layer connection, wherein the protocol description includes first information regarding where to obtain said multiplexing identification information from said data packet, and said multiplexing identification information is used to identify said media streams; and determine QoS flow identifiers (QFIs) for said QoS flows, wherein each of said QFIs is associated with one of said media streams; and to a second device or user equipment (UE): A first device configured to provide second information regarding mapping between the above QFIs, the above multiplexing identification information, and a plurality of sets of the above QoS parameters. Claim 2 In claim 1, the multiplexing identification information comprises: at least one of the identity of the transport layer connection or the identities of the media streams, a first device. Claim 3 A first device according to claim 1, wherein the at least one processor further comprises: a first device configured to enable the first device to provide a first indication to the second device that the second device obtains the multiplexing identification information from the protocol description and the data packet. Claim 4 The first device according to claim 1, wherein the at least one processor further enables the first device to: acquire alternative protocol data unit (PDU) set QoS parameters for the media streams; 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 comprises at least the alternative PDU set QoS parameters. Claim 5 In paragraph 4, the first device wherein the at least one alternative QoS profile comprises at least one dedicated alternative QoS profile. Claim 6 In paragraph 5, the at least one dedicated alternative QoS profile comprises a first dedicated alternative QoS profile for an uplink (UL) and a second dedicated alternative QoS profile for a downlink (DL); the first dedicated alternative QoS profile for the UL comprises at least one of: a UL PDU set delay budget (PSDB), a UL PDU set error rate (PSER), or a UL PDU set aggregation handling information (PSIHI); and the second dedicated alternative QoS profile for the DL comprises at least one of: a DL PSDB, a DL PSER, or a DL PSIHI, a first device. Claim 7 A first device according to claim 6, wherein the first dedicated alternative QoS profile for the UL further comprises a UL guaranteed flow bit rate (GFBR), and the second dedicated alternative QoS profile for the DL further comprises a DL GFBR. Claim 8 In paragraph 4, each of the at least one dedicated alternative QoS profile comprises: a PDU error rate (PER), a PDU delay budget (PDB), a UL guaranteed flow bit rate (GFBR), a DL GFBR, an averaging window, a maximum data burst volume (MDBV), a UL PDU set delay budget (PSDB), a UL PDU set error rate (PSER), a UL PDU set aggregation handling information (PSIHI), a DL PSDB, a DL PSER, or a DL PSIHI, a first device. Claim 9 In paragraph 4, the 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 to the RAN node to provide fourth information regarding at least one alternative PDU set QoS parameter among the alternative PDU set QoS parameters that is satisfied when the QoS profile is not satisfied. Claim 10 In claim 9, the at least one processor further enables the first device: from the RAN node, A fourth indication indicating that the above QoS profile is not satisfied, A sixth indication indicating that the PDU set QoS parameters included in the above QoS profile are not satisfied, or A first device configured to obtain at least one of the fourth information regarding at least one alternative PDU set QoS parameter satisfied among the alternative PDU set QoS parameters. Claim 11 In claim 9 or 10, the fourth information regarding the at least one alternative PDU set QoS parameter satisfied among the alternative PDU set QoS parameters comprises: an index of an alternative QoS profile including the at least one alternative PDU set QoS parameter satisfied among the alternative PDU set QoS parameters, or at least one of a fifth indication of the at least one alternative PDU set QoS parameter satisfied among the alternative PDU set QoS parameters, a first device. Claim 12 A second device comprising at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor enables the second device: from the first device, Protocol description - the protocol description includes first information regarding where to obtain multiplexing identification information from a data packet, and said multiplexing identification information is used to identify media streams within said data packet multiplexed over a single transport layer connection -, Quality of Service (QoS) flow identifiers (QFIs) for the above media streams, the multiplexing identification information, and second information regarding mapping between a plurality of sets of QoS parameters, and A second device configured to obtain a first indication indicating to the second device to obtain the multiplexing identification information from the data packet; to obtain the multiplexing identification information from the data packet based on the protocol description and the first indication; and to map the media streams to QoS flows identified by the QFIs based on the multiplexing identification information and the second information regarding the mapping. Claim 13 In paragraph 12, the above at least one processor causes the above second device: The plaintext portion of a data packet based on the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, General Packet Radio Service (GPRS) Tunnel Protocol-User Plane (GTP-U) header of the above data packet, or A second device configured to obtain multiplexing identification information from a data packet by obtaining the multiplexing identification information from one of the RTP header extensions for the data packet based on the Real-time Transmission Protocol (RTP) protocol. Claim 14 As a user equipment (UE), it comprises: a processor; and a transceiver coupled to the processor, wherein the processor: from a first device through the transceiver, A UE configured to obtain QoS flow identifiers (QFIs) for Quality of Service (QoS) flows, multiplexing identification information for identifying media streams, and second information regarding mapping between a plurality of sets of QoS parameters—each of which QFIs is associated with one of the media streams carried in an uplink data packet and multiplexed over a single transport layer connection—; and to map the media streams to the QoS flows based on the second information regarding mapping. Claim 15 In paragraph 14, the processor is further configured to obtain a protocol description from a first device, said protocol description includes first information regarding where to obtain the multiplexing identification information from the uplink data packet, and said processor is configured to map the media streams to the QoS flows based on said protocol description and the second information regarding the mapping. Claim 16 A third device comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to cause the third device to: provide to the first device multiplexing identification information and a protocol description associated with a plurality of sets of quality of service (QoS) parameters for media streams carried in a data packet and multiplexed over a single transport layer connection, wherein the protocol description includes first information regarding where to obtain multiplexing identification information from the data packet, and the multiplexing identification information is used to identify the media streams. Claim 17 In paragraph 16, the at least one processor is further configured to cause the third device to provide the first device with alternative protocol data unit (PDU) set quality of service (QoS) parameters. Claim 18 In paragraph 16, the at least one processor is further configured to cause the third device to: provide a third indication to the first device, wherein the third indication indicates to a radio access network (RAN) node to provide the first device with fourth information regarding at least one alternative PDU set QoS parameter that is satisfied among the alternative PDU set QoS parameters when the QoS profile is not satisfied. Claim 19 A RAN node comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to obtain at least one alternate quality of service (QoS) profile from a first device through the transceiver, and each of the at least one alternate QoS profile comprises at least an alternate protocol data unit (PDU) set QoS parameters for media streams. Claim 20 In paragraph 19, the above at least one processor additionally: to the above first device, A fourth indication indicating that the above QoS profile is not satisfied, A sixth indication indicating that the PDU set QoS parameters included in the above QoS profile are not satisfied, or A RAN node configured to provide at least one of the fourth information regarding at least one alternative PDU set QoS parameter satisfied among the above alternative PDU set QoS parameters.

Images