Techniques for protocol data unit (PDU) set importance (PSI) field semantics and configuration of quality of service (QOS) provisioning

Abstract

Methods, systems, and devices for media session management are described. In some aspects, two or more of various devices or entities can support one or more signaling or configuration based mechanisms according to which such devices or entities can communicate information associated with an interpretation of a protocol data unit (PDU) set importance (PSI) field of a PDU header. In accordance with communicating information associated with an interpretation of a PSI field, a device or entity can communicate one or more PDUs according to the interpretation (or can otherwise perform communications associated with one or more PDUs, such as communications associated with providing, encapsulating, relaying, or configuring resource allocations for the one or more PDUs). The indicated interpretation can define, specify, or indicate how a device or entity is to handle, parse, allocate, or otherwise communicate (e.g., send or receive) PDU sets for conveying a given PSI field value.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 19 / 090,943, filed March 26, 2025, entitled “Technologies for Aconfigurative of Protocol Data Unit (PDU) Set Importance (PSI) Fields and Quality of Service (QOS) Provisioning,” which claims priority to U.S. Patent Application No. 19 / 090,943, filed April 1, 2024, entitled “Technologies for Aconfigurative of Protocol Data Unit (PDU) Set Importance (PSI) Fields and Quality of Service (QOS) Provisioning.” The benefit of U.S. Provisional Patent Application No. 63 / 572,894, entitled “Provisioning (Techniques for configuring Protocol Data Unit (PDU) Set Importance (PSI) field semantics and Quality of Service (QOS) provisioning),” is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following content relates to media session management, including techniques for configuring the semantics of Protocol Data Unit (PDU) set importance (PSI) fields and the provisioning of Quality of Service (QoS). Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The systems, methods, and apparatus disclosed herein each have some innovative aspects, and no single aspect is solely responsible for the desired properties disclosed herein.

[0006] A method for media session management by a first device is described. The method may include: establishing a Protocol Data Unit (PDU) session between the first device and a second device based on an application at the first device; a first communication that, in association with establishing the PDU session, conveys information associated with the interpretation of a PDU Set Importance (PSI) field in the PDU header; and a second communication that, based on the interpretation of the PSI field, conveys one or more PDUs from one or more PDU sets associated with the application.

[0007] A first device for media session management is described. The first device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to enable the first device to: establish a PDU session between the first device and a second device based on an application at the first device; first communication associated with establishing the PDU session, conveying information related to the interpretation of a PSI field in the PDU header; and second communication, based on the interpretation of the PSI field, conveying one or more PDUs from one or more sets of PDUs associated with the application.

[0008] Another first device for media session management is described. The first device may include: components for establishing a PDU session between the first device and a second device based on an application at the first device; components for first communication that, in association with establishing the PDU session, conveys information associated with the interpretation of the PSI field in the PDU header; and components for second communication that, based on the interpretation of the PSI field, conveys one or more PDUs from one or more sets of PDUs associated with the application.

[0009] A non-transitory computer-readable medium storing code for media session management is described. The code may include instructions executable by one or more processors to: establish a PDU session between a first device and a second device based on an application at a first device; a first communication associated with establishing the PDU session conveying information related to the interpretation of a PSI field in a PDU header; and a second communication based on the interpretation of the PSI field conveying information about one or more PDUs from one or more sets of PDUs associated with the application.

[0010] A method for media session management by a first device is described. The method may include: establishing a PDU session between the first device and a second device based on an application at the first device; selecting a set of communication parameters for one or more PDUs associated with the application based on a media type; and sending the one or more PDUs based on the set of communication parameters.

[0011] A first device for media session management is described. The first device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code to cause the first device to: establish a PDU session between the first device and a second device based on an application at the first device; select a set of communication parameters for the one or more PDUs based on a media type associated with the application; and transmit the one or more PDUs based on the set of communication parameters.

[0012] Another first device for media session management is described. The first device may include: components for establishing a PDU session between the first device and a second device based on an application at the first device; components for selecting a set of communication parameters for one or more PDUs associated with the application based on a media type; and components for transmitting the one or more PDUs based on the set of communication parameters.

[0013] A non-transitory computer-readable medium is described, storing code for media session management. The code may include instructions executable by one or more processors to: establish a PDU session between a first device and a second device based on an application at a first device; select a set of communication parameters for the one or more PDUs associated with the application based on a media type; and transmit the one or more PDUs based on the set of communication parameters.

[0014] A method for media session management by a first device is described. The method may include: establishing a PDU session between the first device and a second device based on an application at the first device; receiving, in association with establishing the PDU session, information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters; selecting, based on the mapping, a first set of communication parameters for a first PDU set associated with the application and a second set of communication parameters for a second PDU set associated with the application, wherein the first and second PDU sets are associated with the same Quality of Service (QoS) stream; transmitting the first PDU set based on the first set of communication parameters; and transmitting the second PDU set based on the second set of communication parameters.

[0015] A first device for media session management is described. The first device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may operate individually or jointly to execute code to cause the first device to: establish a PDU session between the first device and a second device according to an application at the first device; receive information associated with establishing the PDU session, in connection with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters; select, according to the mapping, a first set of communication parameters for a first PDU set associated with the application and a second set of communication parameters for a second PDU set associated with the application, wherein the first and second PDU sets are associated with the same QoS stream; transmit the first PDU set according to the first set of communication parameters; and transmit the second PDU set according to the second set of communication parameters.

[0016] Another first device for media session management is described. The first device may include: components for: establishing a PDU session between the first device and a second device based on an application at the first device; components for: receiving, in association with establishing the PDU session, information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters; components for: selecting, based on the mapping, a first set of communication parameters for a first PDU set associated with the application and a second set of communication parameters for a second PDU set associated with the application, wherein the first and second PDU sets are associated with the same QoS flow; components for: transmitting the first PDU set based on the first set of communication parameters; and components for: transmitting the second PDU set based on the second set of communication parameters.

[0017] A non-transitory computer-readable medium storing code for media session management is described. The code may include instructions executable by one or more processors to: establish a PDU session between a first device and a second device based on an application at a first device; receive, in association with establishing the PDU session, information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters; select, based on the mapping, a first set of communication parameters for a first PDU set associated with the application and a second set of communication parameters for a second PDU set associated with the application, wherein the first and second PDU sets are associated with the same QoS stream; transmit the first PDU set based on the first set of communication parameters; and transmit the second PDU set based on the second set of communication parameters.

[0018] A method for media session management by a network entity is described. The method may include: a first communication that, in association with the establishment of a PDU session between a first device and a second device, conveys information associated with the interpretation of a PSI field in the PDU header of a PDU transmitted between the first device and the second device; and a second communication that, based on the interpretation of the PSI field, conveys information associated with providing one or more PDUs from one or more PDU sets from the first device to the second device.

[0019] A network entity for media session management is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to enable the network entity to: communicate, in association with the establishment of a PDU session between a first device and a second device, information associated with the interpretation of the PSI field of the PDU header of a PDU transmitted between the first device and the second device; and communicate, based on the interpretation of the PSI field, information associated with providing one or more PDUs from one or more PDU sets from the first device to the second device.

[0020] Another network entity for media session management is described. This network entity may include: components for: first communication that, in association with the establishment of a PDU session between a first device and a second device, conveys information associated with the interpretation of the PSI field of the PDU header of the PDU transmitted between the first device and the second device; and components for: second communication that, based on the interpretation of the PSI field, conveys information associated with providing one or more PDUs from one or more PDU sets from the first device to the second device.

[0021] A non-transitory computer-readable medium storing code for media session management is described. The code may include instructions executable by one or more processors to: first communication associated with the establishment of a PDU session between a first device and a second device, conveying information related to the interpretation of a PSI field in the PDU header of a PDU transmitted between the first and second devices; and second communication, based on the interpretation of the PSI field, conveying information associated with providing one or more PDUs from a set of one or more PDUs from the first device to the second device.

[0022] A method for media session management by a network entity is described. The method may include: obtaining one or more PDUs in association with a PDU session between a first device and a second device; selecting a set of communication parameters for the one or more PDUs based on the media type associated with the associated one or more PDUs; and transmitting the one or more PDUs based on the set of communication parameters.

[0023] A network entity for media session management is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors may operate individually or jointly to execute code to enable the network entity to: acquire one or more PDUs in association with a PDU session between a first device and a second device; select a set of communication parameters for the one or more PDUs based on the media type associated with the associated PDUs; and transmit the one or more PDUs based on the set of communication parameters.

[0024] Another network entity for media session management is described. This network entity may include: components for: acquiring one or more PDUs in association with a PDU session between a first device and a second device; components for: selecting a set of communication parameters for the one or more PDUs based on the media type associated with the associated one or more PDUs; and components for: transmitting the one or more PDUs based on the set of communication parameters.

[0025] A non-transitory computer-readable medium is described, storing code for media session management. The code may include instructions executable by one or more processors to: acquire one or more PDUs in association with a PDU session between a first device and a second device; select a set of communication parameters for the one or more PDUs based on the media type associated with the associated one or more PDUs; and transmit the one or more PDUs based on the set of communication parameters.

[0026] A method for media session management by a network entity is described. The method may include: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets, in connection with the establishment of a PDU session between a first device and a second device; obtaining a first PDU set and a second PDU set based on the PDU session between the first device and the second device, wherein the first PDU set and the second PDU set are associated with the same QoS flow; transmitting the first PDU set based on a first communication parameter set mapped to the first PDU set; and transmitting the second PDU set based on a second communication parameter set mapped to the second PDU set.

[0027] A network entity for media session management is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the memories. The processors may operate individually or jointly to execute code to cause the network entity to: transmit information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets, in connection with the establishment of a PDU session between a first device and a second device; obtain a first PDU set and a second PDU set based on the PDU session between the first device and the second device, wherein the first PDU set and the second PDU set are associated with the same QoS flow; transmit the first PDU set based on a first communication parameter set mapped to the first PDU set; and transmit the second PDU set based on a second communication parameter set mapped to the second PDU set.

[0028] Another network entity for media session management is described. This network entity may include: components for transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets, in connection with the establishment of a PDU session between a first device and a second device; components for obtaining a first PDU set and a second PDU set based on the PDU session between the first device and the second device, wherein the first PDU set and the second PDU set are associated with the same QoS flow; components for transmitting the first PDU set based on a first communication parameter set mapped to the first PDU set; and components for transmitting the second PDU set based on a second communication parameter set mapped to the second PDU set.

[0029] A non-transitory computer-readable medium storing code for media session management is described. The code may include instructions executable by one or more processors to: transmit information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of a plurality of PDU sets, in connection with the establishment of a PDU session between a first device and a second device; obtain a first PDU set and a second PDU set based on the PDU session between the first device and the second device, wherein the first PDU set and the second PDU set are associated with the same QoS stream; transmit the first PDU set based on a first communication parameter set mapped to the first PDU set; and transmit the second PDU set based on a second communication parameter set mapped to the second PDU set.

[0030] Details of one or more specific embodiments of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and embodiments will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0031] Figure 1 An example of a wireless communication system is shown, which supports the configuration of Protocol Data Unit (PDU) Set Importance (PSI) field semantics and Quality of Service (QoS) provisioning according to one or more aspects of this disclosure.

[0032] Figure 2 An example of a network architecture is shown that supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0033] Figure 3 An example of a signaling diagram is shown that supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0034] Figure 4 and Figure 5 An example of a process flow is shown that supports the configuration of techniques for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0035] Figure 6 and Figure 7 A block diagram of an apparatus is shown that supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0036] Figure 8 A block diagram of a communication manager is shown, which supports the configuration of techniques for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0037] Figure 9 A diagram of a system including a device that supports configuration for PSI field semantics and QoS provisioning, according to one or more aspects of this disclosure, is shown.

[0038] Figure 10 and Figure 11 A block diagram of an apparatus is shown that supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0039] Figure 12 A block diagram of a communication manager is shown, which supports the configuration of techniques for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure.

[0040] Figure 13 A diagram of a system including a device that supports configuration for PSI field semantics and QoS provisioning, according to one or more aspects of this disclosure, is shown.

[0041] Figure 14 - Figure 19 A flowchart illustrating a method for configuring techniques for PSI field semantics and QoS provisioning, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0042] In some wireless communication systems, one or more devices (e.g., one or more User Equipment (UEs), one or more network entities, one or more nodes, or one or more of any other type of device capable of wired or wireless communication) may communicate (e.g., transmit or receive, or both) one or more Protocol Data Units (PDUs) sets. A PDU set may refer to or include one or more PDUs carrying a payload of an information unit generated at the application layer (e.g., a frame, video slice, etc., for Extended Reality (XR) services). In some systems, a PDU may include a PDU header, which may be understood as or include a Real-Time Transport Protocol (RTP) header. Some PDU headers may include RTP header extensions. The PDU header (e.g., an RTP header extension that can be used for PDU set marking) may include a PDU set importance (PSI) field. The PSI field may include 4 bits. The PSI field may indicate, for example, the priority of the PDU set (e.g., based on media type) or may indicate dependencies between PDU sets. A relatively low PSI field value may indicate a relatively high priority.

[0043] However, in some systems, various communication devices may lack a signaling mechanism for defining, configuring, adjusting, updating, setting, or otherwise synchronizing the meaning or interpretation of PSI field values. For example, some systems may support various options regarding how to use the PSI field, but such systems lack a signaling mechanism by which multiple communication devices can synchronize the use of the PSI field (e.g., its meaning or interpretation, such as semantics). Furthermore, such options supported by some systems may be based on or otherwise associated with existing video codecs and applications, and may lack the flexibility to adapt to other video codecs or application types that the communication devices may implement in the future.

[0044] According to some specific implementation examples, two or more devices or entities of various (wired or wireless) may support one or more signaling or configuration-based mechanisms, according to which such devices or entities may convey information associated with the interpretation (e.g., usage, meaning, or semantics) of the PSI field in the PDU header (e.g., configuration of the interpretation). Such communication of information associated with the interpretation of the PSI field may include communication (e.g., sending or receiving) of one or more messages (e.g., one or more Session Description Protocol (SDP) or Session Initiation Protocol (SIP) messages), one or more PDUs, one or more packets, one or more information elements, one or more Media Access Control (MAC) Control Elements (MAC-CE), one or more Downlink Control Messages (DCI), Uplink Control Messages (UCI), or Sidelink Control Messages (SCI), or any other wired or wireless signaling format. Based on the information conveyed in relation to the interpretation of the PSI field, a device or entity may, according to that interpretation, convey one or more PDUs associated with an application (or may otherwise perform communications associated with providing one or more PDUs, such as communications associated with encapsulating, relaying, or configuring resource allocation for the one or more PDUs). The interpretation of the indication may define, specify, or instruct how a device or entity will use, process, dispose of, parse, allocate resources for a set of PDUs, or otherwise convey (e.g., send or receive) a set of PDUs used to deliver a given PSI field value.

[0045] By communicating information associated with the interpretation of the PSI field, various devices or entities can achieve greater synchronization of the expected interpretation of the PSI field and have greater flexibility or control to change the interpretation of the PSI field over time. With this greater synchronization, devices or entities can appropriately (e.g., as desired) send (e.g., based on a selected set of communication parameters) or provide resources for one or more PDUs in one or more PDU sets, which can support more timely PDU set delivery, fewer PDU set delay budget failures, higher data rates, and higher spectral efficiency. Furthermore, with this greater flexibility and control, devices or entities can dynamically, semi-persistently, or periodically update the interpretation of the PSI field, making the interpretation of the PSI field suitable for the specific application, deployment scenario, or performance indicator associated with the device or entity. Therefore, devices or entities can provide a better user experience, reduced complexity, more efficient processing, and reduced power consumption associated with this reduced complexity and more efficient processing.

[0046] Additionally or alternatively, two or more of a variety of (wired or wireless) devices or entities may support one or more signaling or configuration-based mechanisms, according to which such devices or entities may select communication parameters based on a media type or PSI field value associated with one or more PDUs (in a PDU set). In other words, a device or entity may use a media type or PSI field value to select one or more communication parameters (e.g., one or more Quality of Service (QoS) parameters). In such an implementation, the device or entity may transmit the one or more PDUs based on a set of communication parameters. By making this selection of communication parameters for one or more PDUs based on a media type or PSI field value associated with the one or more PDUs (e.g., included or indicated via the header of the one or more PDUs), the device or entity can more dynamically select relatively more suitable communication parameters for a given set of one or more PDUs, thereby providing fewer communication errors, more timely PDU set delivery, fewer PDU set delay budget failures, higher data rates, and higher spectral efficiency.

[0047] Additionally or alternatively, two or more of various (wired or wireless) devices or entities may support one or more signaling or configuration-based mechanisms, according to which such devices or entities can convey information associated with a mapping between a set of PDUs and a set of communication parameters. For example, such information may indicate a mapping between each of a plurality of PDU sets and a corresponding set of communication parameters. Such communication parameters may include QoS parameters. In other words, as an alternative or supplement to indicating a mapping between a corresponding QoS flow and a corresponding set of communication parameters, the mapping may correspond to a corresponding set of PDUs and a corresponding set of communication parameters. In such an implementation, a device or entity may select a set of communication parameters for a set of PDUs based on the mapping and transmit the set of PDUs (e.g., the one or more PDUs in the set of PDUs) according to the selected set of communication parameters. Based on this mapping and this selection, devices or entities can more dynamically select relatively more suitable communication parameters for a given set of PDUs (because different sets of PDUs, even those associated with the same QoS flow, can be associated with different service types, such as different media types), thereby providing fewer communication errors, more timely PDU set delivery, fewer PDU set delay budget failures, higher data rates, and higher spectrum efficiency.

[0048] As used herein, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc. Furthermore, as used herein, phrases referring to "at least one of" or "one or more of" in a list of items refer to any combination of these items, including a single member. Additionally, as described herein, "network entity" can mean any one or more network components, network devices, network nodes, network functions (or equivalently, "functionalities"), or any combination thereof. For example, a network entity can or can mean a gNB, base station, application function (AF), policy control function (PCF), session management function (SMF), user plane function (UPF), server, or any one or more devices, components, or interfaces associated with any such entity. Network entities can support wired communication, wireless communication, or any combination thereof. Furthermore, as described herein, "device" can or can mean a UE, server, gNB, base station, or any other device that can be used as an RTP endpoint or associated with an RTP endpoint. Devices can support wired communication, wireless communication, or any combination thereof. Furthermore, as used in this article, “communication” can mean sending or receiving, or both.

[0049] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to techniques for configuring PSI field semantics and QoS provisioning. The aspects of this disclosure are further described in the context of various process flows relating to techniques for configuring PSI field semantics and QoS provisioning.

[0050] Figure 1 An example of a wireless communication system 100 is illustrated, which supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices (such as one or more network devices, e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0051] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0052] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0053] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In still other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0054] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0055] One or more network entities or network equipment in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home NodeB, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0056] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) communicating via such communication links.

[0058] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor network entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with a relay chain of the access network (e.g., downstream) or additional entities within the configuration (e.g., IAB node 104, UE 115). In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0059] For example, the access network (AN) or RAN may include an access node (e.g., an IAB donor), communication between IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0060] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0061] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0062] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0063] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0064] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown.

[0065] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “transmit,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the communication between network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU170) and another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0066] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0067] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0068] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0069] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0070] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0071] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0072] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0073] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0074] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE115 (e.g., one or more UEs) or a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0075] Network entity 105 may provide communication coverage via one or more cells (such as macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0076] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast to macro cells, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0077] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0078] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication for coverage area 110 (e.g., different coverage areas) using the same or different RATs.

[0079] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0080] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0081] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0082] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communications and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0083] In some examples, UE 115 may be configured to support direct communication with other UEs (one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in the group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0084] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0085] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or UPF) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0086] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0087] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0088] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0089] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0090] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0091] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0092] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0093] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0094] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0095] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0096] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer can map transport channels to physical channels.

[0097] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0098] The UE 115 and network entity 105 of the wireless communication system 100 may convey data in the form of one or more PDUs. In some scenarios, one or more devices in such a system may convey one or more PDUs as part of a PDU set. A PDU set may be defined or understood as one or more PDUs carrying a payload of an information unit generated at the application layer. For example, a PDU set may include one or more PDUs carrying or otherwise indicating one or more frames or video slices associated with an application, such as an XR application, a virtual reality (VR) application, a mixed reality (MR) application, or an augmented reality (AR) application, etc. A PDU set marked with an RTP header extension may include a PSI field, and in some systems, one or more devices may support guidelines regarding the use of the PSI field (e.g., based on at least one of media type or dependencies between PDU sets). However, in some systems, such guidelines may be based on existing video codecs and applications. In other words, such guidelines may lack the flexibility to support future codecs and applications. For example, in autonomous applications, there may be 16 types of data (including text, audio, video, telemetry, etc.), and the guidelines used by some systems may not be sufficient to support 16 types of data. Some systems may use other methods to label packets, such as the Differential Service Code Point (DSCP) in the IP packet header. However, DSCP labeling is based on the concept of IP packets rather than a set of PDUs. Furthermore, routers can modify DSCP values, potentially leading to inconsistent labeling or labeling mechanisms that are otherwise uncontrollable (e.g., unpredictable) in some scenarios.

[0099] According to some specific implementation examples, two or more of various (wired or wireless) devices or entities (e.g., one or more UE 115s or one or more network entities 105s or any combination thereof) may support one or more signaling or configuration-based mechanisms, according to which such devices or entities may convey information associated with the interpretation (e.g., semantics) (e.g., configuration of the interpretation) of the PSI field in the PDU header. Based on conveying the information associated with the interpretation of the PSI field, the device or entity may, according to that interpretation, convey one or more PDUs associated with an application (or may otherwise perform communications associated with providing one or more PDUs, such as communications associated with encapsulation, relaying, or configuring resource allocation for the one or more PDUs). The indicated interpretation may define, specify, or instruct how the device or entity will dispose of, parse, allocate, or otherwise convey (e.g., send or receive) a set of PDUs used to deliver a given PSI field value.

[0100] Additionally or alternatively, two or more of a variety of (wired or wireless) devices or entities may support one or more signaling or configuration-based mechanisms, according to which such devices or entities can select communication parameters based on a media type or PSI field value associated with one or more PDUs (in a PDU set). In other words, the device or entity can use a media type or PSI field value to select one or more communication parameters (e.g., one or more QoS parameters). In such an implementation, the device or entity can transmit the one or more PDUs according to a set of communication parameters.

[0101] Additionally or alternatively, two or more of various (wired or wireless) devices or entities may support one or more signaling or configuration-based mechanisms, according to which such devices or entities can convey information associated with a mapping between a set of PDUs and a set of communication parameters. For example, such information may indicate a mapping between each of a plurality of PDU sets and a corresponding set of communication parameters. Such communication parameters may include QoS parameters. In other words, as an alternative or supplement to indicating a mapping between a corresponding QoS flow and a corresponding set of communication parameters, the mapping may correspond to a corresponding set of PDUs and a corresponding set of communication parameters. In such an implementation, a device or entity may select a set of communication parameters for a set of PDUs based on the mapping and transmit the set of PDUs (e.g., the one or more PDUs in the set of PDUs) according to the selected set of communication parameters.

[0102] Figure 2An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0103] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0104] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0105] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0106] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0107] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0108] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) or machine learning (ML) workflows for model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CU 160-a, one or more DU 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0109] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0110] Figure 3 Signaling diagram 300 illustrates techniques supporting configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. For example, signaling diagram 300 illustrates communication between UE 115 and network entity 105, which may be examples of corresponding devices as described herein. UE 115 and network entity 105 may communicate via communication link 305, which may represent an uplink or a downlink or both.

[0111] In some implementations, UE 115, network entity 105, or another network device, node, or function may support a mechanism that allows selection of a corresponding set of communication parameters for conveying (e.g., sending or receiving) a given set of PDUs. In other words, UE 115 and network entity 105 may convey PDUs by selecting communication parameters at the PDU set level. For example, UE 115 and network entity 105 may convey a first PDU set 310-a and a second PDU set 310-b. The first PDU set 310-a may be associated with a first PSI field value 315-a or a first media type 320-a, or both. The second PDU set 310-b may be associated with a second PSI field value 315-b or a second media type 320-b, or both. In some examples, the first PDU set 310-a and the second PDU set 310-b may be associated with the same QoS flow 325.

[0112] Based on the selection of communication parameters at the PDU set level, a first PDU set 310-a may be associated with a first communication parameter set 330-a (e.g., a first QoS parameter set), and a second PDU set 310-b may be associated with a second communication parameter set 330-b (e.g., a second QoS parameter set). UE 115, network entity 105, or another network device, node, or function may select a first communication parameter set 330-a for conveying the first PDU set 310-a based on a first PSI field value 315-a or a first media type 320-a, or both, associated with the first PDU set 310-a. UE 115, network entity 105, or another network device, node, or function may select a second communication parameter set 330-b for conveying the second PDU set 310-b based on a second PSI field value 315-b or a second media type 320-b, or both, associated with the second PDU set 310-b.

[0113] The first PDU set 310-a and the second PDU set 310-b may be associated with an application. In some implementations, the application may signal (e.g., transmit or send) the semantics (e.g., interpret) of the PSI field. For example, an application on an RTP endpoint (e.g., UE115 or a server) may signal the configuration of the semantics of the PSI field. In some examples, signaling may be transmitted from one endpoint to another, such as in an SDP message, and the network (e.g., PCF) may obtain the mapping. For example, the Proxy Call Session Control Function (P-CSCF) may intercept the mapping in the case of IMS, or the Media Session Disposal Procedure (MSH) on UE115 may extract the mapping and transmit an indication of the mapping to the AF in the case of Web Real-Time Communication (WebRTC). Additionally or alternatively, in some examples, signaling may take the form of a request to the core network, such as by extending a PDU session modification request message to include semantics. In such examples, the request may be followed by a PDU session modification command or an acknowledgment (ACK).

[0114] In some examples, the signaling content may include or indicate a mapping between the service type (e.g., media type) of the PDU set and PSI field values. This mapping may indicate that each media type in the media type set corresponds to a corresponding PSI field value in the set of possible PSI field values. For example, the mapping may indicate that the media type "text" corresponds to a PSI field value equal to 15, the media type "telemetry (sensor data)" corresponds to a PSI field value equal to 2, the media type "audio" corresponds to a PSI field value equal to 3, the media type "video (I-frame)" corresponds to a PSI field value equal to 5, the media type "video (P-frame)" corresponds to a PSI field value equal to 7, or any combination thereof.

[0115] Additionally or alternatively, the signaling content may include or indicate relationships (e.g., dependencies) between PDU sets. Multiple dependencies may exist between PDU sets. Such relationships or dependencies may include audio dependencies. For example, in audio decoding (e.g., Immersive Speech and Audio Services (IVAS)), an audio encoder may generate both audio data and audio metadata (e.g., azimuth, elevation, radius, pitch, and yaw), and the audio data may depend on the audio metadata. A PDU set carrying audio data may be labeled with a PSI field value equal to 5, and a PDU set carrying audio metadata may be labeled with a PSI field value equal to 4. In such an example, the signaling may indicate that a PDU set with a PSI field value equal to 5 depends on a PDU set with a PSI field value equal to 4. As another example, another type of relationship or dependency may include video dependencies. For example, a P-frame may reference an I-frame, which can create a dependency between a PDU set carrying one or more P-frames and a PDU set carrying one or more I-frames. Signaling can indicate that a set of PDUs with a PSI field value equal to 7 (e.g., which may correspond to a set of PDUs carrying P-frames, such as according to an indicated or default mapping) depends on a set of PDUs with a PSI field value equal to 6 (e.g., which may correspond to a set of PDUs carrying I-frames, such as according to an indicated or default mapping, as a reference to the P-frames). In this example, a set of PDUs labeled with a PSI field value equal to 6 may not depend on a set of PDUs labeled with a PSI field value equal to 4, even though the former's PSI field value is greater than the latter's.

[0116] In some examples, the signaling content may include or indicate an association (e.g., a mapping between the two) between a set of QoS parameters for a PDU set and a PSI field value or a media type. This association or mapping may differ from a QoS flow-based PDU set QoS framework supported by some systems, because QoS parameters (or more generally, communication parameters) can be selected at the PDU set level granularity, rather than at the QoS flow level granularity. In such examples, the association may indicate (e.g., each) PSI field value or (e.g., each) media type corresponds to a corresponding set of communication parameters (e.g., a corresponding set of QoS parameters). For example, the association may indicate that a PSI field value equal to 3 or a first media type (such as the media type corresponding to PSI=3) corresponds to a first set of communication parameters, a PSI field value equal to 4 or a second media type (such as the media type corresponding to PSI=4) corresponds to a second set of communication parameters, and a PSI field value equal to 5 or a third media type (such as the media type corresponding to PSI=5) corresponds to a third set of communication parameters. For example, the first set of communication parameters may include a PDU set delay budget (PSDB) of 20 milliseconds and a PDU set error rate (PSER) of 0.01%. As another example, the second set of communication parameters may include a PSDB of 40 milliseconds and a PSER of 0.1%. As yet another example, the third set of communication parameters may include a PSDB of 50 milliseconds and a PSER of 1%.

[0117] Network entity 105 may adjust resource allocation based on received signaling. In some examples, the network (e.g., PCF) may reconfigure PDU set QoS parameters based on signaling. In some examples, for downlink traffic, the UPF may identify QoS flows based on PSI field values ​​(and / or media type) and one or more other attributes (e.g., IP 5-tuples). For uplink traffic, UE 115 may identify QoS flows based on PSI field values ​​(and / or media type) and one or more other attributes (e.g., IP 5-tuples). Additionally or alternatively, the network (e.g., PCF) may map media types (or equivalently, PSI field values) to a set of PDU set QoS parameters (e.g., PSDB, PSER, or PDU set integrated disposal information (PSIHI), etc.). PSIHI may indicate whether PDUs in the PDU set should be disposed of as a whole, such as whether all PDUs in the PDU set are expected to be delivered or otherwise discarded. In other words, PSIHI can indicate that one or more PDUs in a PDU set can be delivered, while one or more other PDUs in the PDU set are discarded, or all PDUs in the PDU set are delivered or all are discarded. In such examples, the network (e.g., PCF) can transmit mappings to one or more other network entities (such as one or more SMF, UPF, or RAN nodes). In some examples, the network can signal relationships to the SMF, UPF, or RAN nodes as input for resource allocation. In some examples, the network can accept or modify requests and configure the SMF, UPF, or RAN nodes for resource allocation based on the accepted or modified requests.

[0118] In some implementations, network entities may signal PSI configuration. For example, the network may signal the semantics (e.g., interpretation) of PSI fields. In some examples, the network may map or remap PSI field values ​​and service types (e.g., media types) and may signal the mapping to applications (e.g., via AF). In some examples, the network may signal the mapping to applications based on a request from a RAN node (e.g., in a PDU session modification request message) under one or more specific conditions (e.g., congestion or persistently high network load, such as above a threshold for congestion or above a threshold for network load), which may suggest a new mapping. For example, the gNB may observe a significant PSER (e.g., PSER above a PSER threshold) and may observe that the PSER for I-frames and P-frames are similar. In such examples, to improve Quality of Experience (QoE), the gNB may (in the request) suggest further prioritizing I-frames and further deprioritizing P-frames by decreasing the PSI field value for the PDU set associated with the I-frame and increasing the PSI field value for the PDU set associated with the P-frame. In some examples, the network may signal mappings to applications based on QoS or QoE metric reports (such as those transmitted from UE 115 or gNB to the Operation, Administration, and Maintenance (OAM) function). In such examples, and referring to those with significant PSERs, the gNB may not observe but instead report one or more QoS / QoE metrics to the OAM function, which may forward the reports to the PCF (upon request from the PCF), and the PCF may adjust the PSI field values ​​for the I-frame PDU set and the P-frame PDU set.

[0119] In some examples, the network may signal relationships (e.g., dependencies) to applications, UPFs, or RAN nodes. In other examples, the network may signal the association between a set of PDUs, a set of QoS parameters (or more generally, a set of communication parameters) and PSI field values ​​(and / or media types) to UPFs and RAN nodes. Applications may apply remapping to future services based on signaling received from the network.

[0120] In some examples, UE 115 and network entity 105 may support QoS flow definitions that take into account (e.g., consider or otherwise take into account) PSI. In some systems, QoS flows may be defined by packet filters that include IP 5-tuples, Type of Service (TOS), and source and destination MAC addresses, etc. IP packet filter sets may be defined: for IP PDU session types, the packet filter set may support packet filtering based on at least any combination of the following: source / destination IP address or IPv6 prefix, source / destination port number, protocol ID / next header type of the above-IP protocol, TOS (IPv4) / Class of Service (IPv6) and mask, flow label (IPv6), security parameter index, or packet filter direction. For example, an Ethernet packet filter set can be defined such that, for an Ethernet PDU session type, the packet filter set can support packet filtering based on at least any combination of the following: source / destination MAC address, Ethernet type as defined in IEEE 802.3, VID field of customer VLAN tag (C-TAG) and / or service VLAN tag (S-TAG) as defined in IEEE standard 802.IQ, PCP / DEI field of customer VLAN tag (C-TAG) and / or service VLAN tag (S-TAG) as defined in IEEE standard 802.IQ, IP packet filter set (where the Ethernet type indicates an IPv4 / IPv6 payload), or packet filter direction.

[0121] To support QoS flow definitions that take into account PSI field values ​​(and / or media type), in some examples, devices or entities can (e.g., based on rules) add PSI to an attribute list that can be used to define QoS flows for IP packet filters or Ethernet packet filters. For example, PSI and IP 5-tuples (e.g., source / destination IP address or IPv6 prefix, source / destination port number, protocol ID / next header type for IP above the standard protocol) can be used together (e.g., jointly or in combination) to define a QoS flow.

[0122] Furthermore, in some systems, PDU set QoS parameters can be selected (e.g., identified, determined, or used) at the flow level, such that all PDU sets within the same QoS flow (e.g., the same QoS flow 325) will have the same set of parameters (including PSI). For example, PDU set QoS parameters can be used to support PDU set-based QoS handling in NG-RAN. At least one PDU set QoS parameter can be transmitted to NG-RAN to implement PDU set-based QoS handling. As described herein, PDU set QoS parameters may include PSDB, PSER, and PSIHI. For a given QoS flow, the values ​​of PSDB, PSER, and PSIHI can be different for uplink and downlink. This selection of PDU set QoS parameters at the flow level may result in the network being unable to distinguish the handling of different application data units (e.g., I-frames and P-frames) multiplexed on the same QoS flow.

[0123] According to some specific implementation examples, UE 115 and network entity 105 may support PDU set QoS parameter configuration at the PDU set level. In some examples, PDU set QoS parameters (e.g., PSDB, PSER, and PSIHI) may be specified or defined for the PDU set (e.g., where PDU sets with the same PSI field value or the same media type are treated the same) rather than (or otherwise) for the QoS flow. For example, a first communication parameter set 330-a (e.g., a first QoS parameter set, such as "QoS parameter 1") corresponding to a first PSI field value 315-a or a first media type 320-a may include or indicate a PSDB equal to 5 milliseconds, a PSER equal to 0.001%, and a PSIHI equal to "true". As another example, a second set of communication parameters 330-b (e.g., a second set of QoS parameters, such as "QoS parameter 2") corresponding to a second PSI field value 315-b or a second media type 320-b may include or indicate a PSDB equal to 10 milliseconds, a PSER equal to 0.01%, and a PSIHI equal to "false". Depending on the defined or specified communication parameters for the PDU sets, UE 115 and network entity 105 may support the communication of [flow 1, PDU set 1, QoS parameter 1], [flow 1, PDU set 2, QoS parameter 2], and [flow 1, PDU set 3, QoS parameter 1]. For example, on the same QoS flow (e.g., flow 1), PDU sets 1 and 3 may represent I-frames, and PDU set 2 may represent P-frames.

[0124] Figure 4Process flow 400 is illustrated, which supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. Process flow 400 illustrates UE 115 (which may include RTP application 402 and MSH 404), network entity 105 (in Figure 4 The example is shown as communication between gNB, AF 406, PCF 408, SMF 410, UPF 412 and application server 414 (which may include RTP application 416, which may be the same as RTP application 402 or another version of that RTP application). Any or more of the devices, nodes, entities or functions of process flow 400 may implement one or more aspects of this disclosure.

[0125] According to process flow 400, two or more devices or entities of various types (wired or wireless) may support one or more signaling or configuration-based mechanisms, according to which such devices or entities may convey information associated with the interpretation (e.g., usage, meaning, or semantics) of the PSI field in the PDU header (e.g., configuration of the interpretation). Such communication of information associated with the interpretation of the PSI field may include communication (e.g., sending or receiving) of one or more messages, one or more PDUs, one or more packets, one or more information elements, one or more MAC-CEs, one or more DCI, UCI, or SCI messages, or any other wired or wireless signaling format.

[0126] Based on the information conveyed in relation to the interpretation of the PSI field, a device or entity may, according to that interpretation, convey one or more PDUs associated with an application (or may otherwise perform communications associated with providing one or more PDUs, such as communications associated with encapsulating, relaying, or configuring resource allocation for the one or more PDUs). The interpretation of the indication may define, specify, or instruct how a device or entity will use, process, dispose of, parse, allocate resources for a set of PDUs, or otherwise convey (e.g., send or receive) a set of PDUs used to deliver a given PSI field value.

[0127] In the following description of process flow 400, operations between various devices, nodes, entities, or functions may be performed in a different order than the example order shown. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may occur simultaneously.

[0128] At 418, UE 115 may send an SDP proposal to the RTP application 416 of application server 414. The SDP proposal may include or indicate a proposed or requested mapping between PSI field values ​​and media types.

[0129] At 420, the RTP application 416 of application server 414 may send an SDP response to at least one of the RTP application 402 or MSH 404 of UE 115. The SDP response may include or indicate an agreed-upon mapping between PSI field values ​​and media types.

[0130] At 422, UE 115's MSH 404 can extract the mapping between PSI field values ​​and media types. At 424, UE 115's MSH 404 can send an indication of the mapping between PSI field values ​​and media types to at least one of AF 406 or PCF 408. At 426, PCF 408 can send an indication of reconfiguration of PDU set QoS parameters (e.g., based on the mapping) to at least one of SMF 410 or UPF 412.

[0131] At 428, the RTP application 416 of application server 414 can transmit a PDU set to UPF 412. At 430, UPF 412 can encapsulate the PDUs in the PDU set into General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packets and copy the RTP header extension in the PDUs to the corresponding GTP-U packet header. At 432, UPF 412 can transmit GTP-U packets to network entity 105 (e.g., gNB or another RAN node). At 434, network entity 105 can provide resource allocation (e.g., time and frequency resources) for communicating the PDUs in the PDU set from network entity 105 to UE 115. At 436, network entity 105 can extract the PDUs in the PDU set and transmit them to UE 115, which can then provide them to UE 115's RTP application 402.

[0132] Figure 5 A process flow 500 is illustrated, which supports the configuration of PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. Process flow 500 illustrates UE 115, network entity 105 (in... Figure 5 The example is shown as communication between gNB, AF 502, PCF 504, SMF 506, UPF 508, OAM function 510, and application server 512. Any or more of the devices, nodes, entities, or functions of process flow 500 may implement one or more aspects of this disclosure.

[0133] According to process flow 500, two or more devices or entities of various types (wired or wireless) may support one or more signaling or configuration-based mechanisms, according to which such devices or entities may convey information associated with the interpretation (e.g., usage, meaning, or semantics) of the PSI field in the PDU header (e.g., configuration of the interpretation). Such communication of information associated with the interpretation of the PSI field may include communication (e.g., sending or receiving) of one or more messages, one or more PDUs, one or more packets, one or more information elements, one or more MAC-CEs, one or more DCI, UCI, or SCI messages, or any other wired or wireless signaling format.

[0134] Based on the information conveyed in relation to the interpretation of the PSI field, a device or entity may, according to that interpretation, convey one or more PDUs associated with an application (or may otherwise perform communications associated with providing one or more PDUs, such as communications associated with encapsulating, relaying, or configuring resource allocation for the one or more PDUs). The interpretation of the indication may define, specify, or instruct how a device or entity will use, process, dispose of, parse, allocate resources for a set of PDUs, or otherwise convey (e.g., send or receive) a set of PDUs used to deliver a given PSI field value.

[0135] In the following description of process flow 500, operations between various devices, nodes, entities, or functions may be performed in a different order than the example order shown. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may occur simultaneously.

[0136] At 514, UE 115 and application server 512 may participate in or otherwise perform session establishment. Such session establishment may include: sending an SDP proposal from UE 115 to application server 512, and sending an SDP response from application server 512 to UE 115. Session establishment may negotiate, coordinate, or indicate the mapping between PSI field values ​​and media types.

[0137] At 516, PCF 504 may send an indication to UE 115 of the mapping between PSI field values ​​and media types. At 518, UE 115 may send a QoE metric report to OAM function 510. At 520, OAM function 510 may send (e.g., forwarding or relaying) a QoE metric report to PCF 504. At 522, PCF 504 may change the mapping between PSI field values ​​and media types (e.g., based on the QoE metric report). At 524, PCF 504 may update the mapping to at least one of AF 502 or UE 115. For example, PCF 504 may send an indication of the updated mapping to at least one of AF 502 or UE 115.

[0138] At 526, UE 115 may send an SDP proposal to application server 512. The SDP proposal may include or indicate a new mapping (e.g., an updated mapping) (e.g., as indicated to UE 115 from PCF 504). At 528, application server 512 may send an SDP response to UE 115. The SDP response may include or indicate agreement to the new mapping (e.g., an updated mapping).

[0139] At 530, application server 512 can transmit the PDU set to UPF 508 according to the new mapping. At 532, UPF 508 can encapsulate the PDUs in the PDU set into GTP-U packets and copy the RTP header extension in the PDUs to the corresponding GTP-U packet header. At 534, UPF 508 can transmit GTP-U packets to network entity 105 (e.g., gNB or another RAN node). At 536, network entity 105 can provide resource allocation (e.g., time and frequency resources) for communicating the PDUs in the PDU set from network entity 105 to UE 115. At 538, network entity 105 can extract the PDUs in the PDU set and transmit them to UE 115.

[0140] Figure 6 A block diagram 600 of a device 605 is shown, illustrating a technology for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of a UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0141] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, etc., related to technologies used for configuring PSI field semantics and QoS provisioning). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0142] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels (e.g., control channels, data channels, and information channels related to the technology used for configuring PSI field semantics and QoS provisioning), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0143] The communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be examples of components for various aspects of the techniques used to perform the configuration of PSI field semantics and QoS provisioning as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0144] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0145] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0146] In some examples, the communication manager 620 may be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0147] The communication manager 620 can support media session management according to the examples described herein. For example, the communication manager 620 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at a first device. The communication manager 620 is capable of, configured to, or operable to support components for: first communication that conveys information associated with the interpretation of the PSI field in the PDU header in connection with establishing the PDU session. The communication manager 620 is capable of, configured to, or operable to support components for: second communication that conveys one or more PDUs from one or more PDU sets associated with an application based on the interpretation of the PSI field.

[0148] Additionally or alternatively, the communication manager 620 may support media session management according to the examples described herein. For example, the communication manager 620 is capable of, configured to, or operable to support components for establishing a session between a first device and a second device based on an application at the first device. The communication manager 620 is capable of, configured to, or operable to support components for selecting a set of communication parameters for one or more PDUs associated with an application, based on the media type (as indicated by field values ​​such as PSI field values). The communication manager 620 is capable of, configured to, or operable to support components for transmitting the one or more PDUs based on the set of communication parameters.

[0149] Additionally or alternatively, the communication manager 620 may support media session management according to the examples described herein. For example, the communication manager 620 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at the first device. The communication manager 620 is capable of, configured to, or operable to support components for: receiving information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters in connection with establishing a PDU session. The communication manager 620 is capable of, configured to, or operable to support components for: selecting a first set of communication parameters for a first PDU set associated with an application based on the mapping. The communication manager 620 is capable of, configured to, or operable to support components for: transmitting a first PDU set based on the first set of communication parameters.

[0150] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0151] Figure 7 A block diagram 700 of a device 705 is shown, illustrating a technology supporting configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720) may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, etc., related to technologies used for configuring PSI field semantics and QoS provisioning). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0153] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels, such as control channels, data channels, and information channels (e.g., control channels, data channels, and information channels related to the technology used for configuring PSI field semantics and QoS provisioning), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0154] Device 705 or its various components may be examples of various aspects of the techniques used to perform configurations for PSI field semantics and QoS provisioning as described herein. For example, communication manager 720 may include PDU session component 725, PSI semantic component 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or integrate in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0155] The communication manager 720 can support media session management according to the examples described herein. The PDU session component 725 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at the first device. The PSI semantic component 730 is capable of, configured to, or operable to support components for: first communication that conveys information associated with the interpretation of the PSI field in the PDU header in connection with establishing a PDU session. The PSI semantic component 730 is capable of, configured to, or operable to support components for: second communication that conveys one or more PDUs from one or more PDU sets associated with an application based on the interpretation of the PSI field.

[0156] Additionally or alternatively, the communication manager 720 may support media session management according to the examples described herein. The PDU session component 725 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at the first device. The PDU session component 725 is capable of, configured to, or operable to support components for: selecting a set of communication parameters for one or more PDUs associated with the application, based on the media type (as indicated by field values ​​such as PSI field values). The PDU session component 725 is capable of, configured to, or operable to support components for: transmitting the one or more PDUs based on the set of communication parameters.

[0157] Additionally or alternatively, the communication manager 720 may support media session management according to the examples described herein. The PDU session component 725 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at the first device. The PDU session component 725 is capable of, configured to, or operable to support components for: receiving information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters in connection with establishing the PDU session. The PDU session component 725 is capable of, configured to, or operable to support components for: selecting a first set of communication parameters for a first PDU set associated with an application based on the mapping. The PDU session component 725 is capable of, configured to, or operable to support components for: transmitting a first PDU set based on the first set of communication parameters.

[0158] Figure 8 A block diagram 800 of a communication manager 820 supporting techniques for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of the techniques for configuring PSI field semantics and QoS provisioning as described herein. For example, the communication manager 820 may include a PDU session component 825, a PSI semantics component 830, an application 835, a filtering component 840, an MSH component 845, a QoS or QoE component 850, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0159] The communication manager 820 can support media session management according to the examples described herein. The PDU session component 825 is capable of, configured to, or operable to support components for establishing a PDU session between a first device and a second device based on an application at the first device. The PSI semantic component 830 is capable of, configured to, or operable to support components for conveying information associated with the interpretation of the PSI field in the PDU header in connection with establishing the PDU session. In some examples, the PSI semantic component 830 is capable of, configured to, or operable to support components for conveying information associated with the interpretation of the PSI field in one or more PDU sets associated with an application in connection with the second communication.

[0160] In some examples, in order to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 830 is capable of, configured to, or operable to support components for sending to or receiving messages including information associated with the interpretation of a PSI field from a second device.

[0161] In some examples, the MSH component 845 is capable of, configured to, or operable to support components for: extracting an interpretation of the PSI field via a media session handler associated with the first device. In some examples, the MSH component 845 is capable of, configured to, or operable to support components for: sending information associated with the interpretation of the PSI field to a network entity, wherein a second communication conveying the one or more PDUs is performed in connection with sending the information associated with the interpretation of the PSI field to the network entity.

[0162] In some examples, the network entity is AF. In some examples, the first device is associated with WebRTC based on the PDU session and extracts an interpretation of the PSI field via a media session handler.

[0163] In some examples, to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 830 is capable, configured, or operable to support components for: sending a first message to a network entity including a request for the interpretation of a PSI field. In some examples, to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 830 is capable, configured, or operable to support components for: receiving a second message from a network entity, the second message including acceptance or modification of the interpretation of a PSI field requested by the first device, wherein second communication conveying the one or more PDUs is performed based on the network entity's acceptance or modification of the interpretation of the PSI field.

[0164] In some examples, the first message is a PDU session modification request message. In some examples, the PDU session modification request message includes a set of fields or one or more bits indicating the interpretation of the PSI field requested by the first device.

[0165] In some examples, the network entity is the core network entity.

[0166] In some examples, the PDU session component 825 is capable of, configured to, or able to operate to support components for: receiving second information associated with a resource allocation for a PDU session between a first device and a second device, wherein a second communication conveying the one or more PDUs is performed based on the resource allocation.

[0167] In some examples, resource allocation indicates: one or more physical resources associated with a PDU session, a first mapping between each PSI field value in a set of multiple PSI field values ​​and the corresponding QoS flow, a second mapping between each PSI field value in a set of multiple PSI field values ​​and the corresponding QoS parameter set, a third mapping that associates two or more PSI field values ​​in a set of multiple PSI field values ​​with a corresponding PDU set having dependencies, or any combination thereof.

[0168] In some examples, resource allocation is received from network entities.

[0169] In some examples, in order to support the first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 830 is capable of, configured to, or operable to support the following component: receiving messages from a network entity that include information associated with the interpretation of a PSI field.

[0170] In some examples, the message is received from a network entity based on meeting one or more conditions. In some examples, these one or more conditions include one or two of the following: the network congestion level meets a threshold network congestion level, or the network load level meets a threshold network load level. In some examples, these one or more conditions include: the PDU set error rate meets a threshold PDU set error rate, or the PDU set error rates for multiple service types are within a range close to each other's thresholds.

[0171] In some examples, the multiple service types include a first service type associated with I-frames of video data and a second service type associated with P-frames of video data. In some examples, the PSI field is interpreted to indicate the priority of I-frames of video data and the priority of P-frames of video data by decreasing the first PSI field value corresponding to the first PDU set of I-frames carrying video data and increasing the second PSI field value corresponding to the second PDU set of P-frames carrying video data.

[0172] In some examples, the QoS or QoE component 850 is capable of, configured to, or able to operate to support components for sending second information to a network entity associated with a QoS metric or QoE (QoE) metric, wherein an interpretation of the PSI field is received from the network entity in connection with sending one or both of the QoS metric or QoE metric to the network entity.

[0173] In some examples, network entities forward one or both of the QoS metric or QoE metric to the policy control function associated with the network entity. In some examples, the policy control function generates an interpretation of the PSI field.

[0174] In some examples, the interpretation of the PSI field indicates a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding service type. In some examples, according to the mapping, a first PSI field value corresponds to a first service type, and a second PSI field value corresponds to a second service type. In some examples, according to the mapping, a first PSI field value corresponds to telemetry data, a second PSI field value corresponds to audio data, a third PSI field value corresponds to an I-frame of video data, and a fourth PSI field value corresponds to a P-frame of video data.

[0175] In some examples, the interpretation of the PSI field indicates a mapping that associates two or more PSI field values ​​from a set of multiple PSI field values ​​with corresponding PDU sets having dependencies. In some examples, according to the mapping, a first PDU set associated with a first PSI field value and a second PDU set associated with a second PSI field value have a first dependency. In some examples, the first dependency indicates that the first PDU set depends on the second PDU set. In some examples, the first PDU set is associated with audio data, and the second PDU set is associated with audio metadata. In some examples, the first PDU set is associated with P-frames of video data, and the second PDU set is associated with I-frames of video data. In some examples, according to the mapping, a third PDU set associated with a third PSI field value and a fourth PDU set associated with a fourth PSI field value have a second dependency. In some examples, the second dependency indicates that the third PDU set depends on the fourth PDU set.

[0176] In some examples, the interpretation of the PSI field indicates a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding set of communication parameters. In some examples, according to the mapping, a first PSI field value corresponds to a first set of communication parameters, and a second PSI field value corresponds to a second set of communication parameters. In some examples, the corresponding set of communication parameters includes a corresponding set of QoS parameters. In some examples, according to the mapping, a first PSI field value corresponds to a first set of QoS parameters, and a second PSI field value corresponds to a second set of QoS parameters. In some examples, the first set of QoS parameters includes a first set of PDU delay budget and a first set of PDU error rate, and the second set of QoS parameters includes a second set of PDU delay budget and a second set of PDU error rate.

[0177] In some examples, to support second communication conveying the one or more PDUs, application 835 is capable of, configured to, or able to operate to support the following component: obtaining the first PDU from the application. In some examples, to support second communication conveying the one or more PDUs, filtering component 840 is capable of, configured to, or able to operate to support the following component: filtering the first PDU according to a packet filter based on a first PSI field value associated with the first PDU. In some examples, to support second communication conveying the one or more PDUs, filtering component 840 is capable of, configured to, or able to operate to support the following component: determining a first QoS flow associated with the first PDU based on the packet filter. In some examples, to support second communication conveying the one or more PDUs, PDU session component 825 is capable of, configured to, or able to operate to support the following component: sending the first PDU according to a set of QoS parameters associated with the first QoS flow.

[0178] In some examples, the PDU session component 825 is capable of, configured to, or able to operate to support the following: receiving, in association with establishing a PDU session, second information associated with a mapping between each of a set of multiple PDU sets and a corresponding QoS parameter set, wherein, according to the mapping, a first PDU set of a first QoS flow is associated with a first QoS parameter set, and a second PDU set of a first QoS flow is associated with a second QoS parameter set.

[0179] Additionally or alternatively, the communication manager 820 may support media session management according to the examples described herein. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for establishing a PDU session between a first device and a second device based on an application at the first device. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for selecting a set of communication parameters for one or more PDUs associated with an application, based on the media type (as indicated by field values ​​such as PSI field values). In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for transmitting one or more PDUs based on the set of communication parameters.

[0180] In some examples, application 835 is capable of, configured to, or able to operate to support components for obtaining the one or more PDUs from the application. In some examples, filtering component 840 is capable of, configured to, or able to operate to support components for filtering (e.g., grouping) the one or more PDUs into a QoS flow according to a packet filter based on a PSI field value, wherein the set of communication parameters is selected in association with filtering (e.g., grouping) the one or more PDUs into a QoS flow according to a packet filter based on a PSI field value.

[0181] In some examples, the filtering component 840 is capable of, can be configured to, or is operable to support components for determining the QoS flow associated with the one or more PDUs based on the group filter, wherein the set of communication parameters is selected in connection with determining the QoS flow associated with the one or more PDUs.

[0182] In some examples, the PSI field value and the Internet Protocol parameter set jointly define the QoS flow based on a packet filter. In some examples, the corresponding PSI field value and the corresponding Internet Protocol parameter set jointly define the corresponding QoS flow based on a packet filter. In some examples, the packet filter is an Internet Protocol packet filter or an Ethernet packet filter. In some examples, the communication parameter set includes a QoS parameter set.

[0183] Additionally or alternatively, the communication manager 820 may support media session management according to the examples described herein. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at a first device. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for: receiving information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters in connection with establishing a PDU session. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for: selecting a first set of communication parameters for a first PDU set associated with an application based on the mapping. In some examples, the PDU session component 825 is capable of, configured to, or operable to support components for: transmitting a first PDU set based on the first set of communication parameters.

[0184] In some examples, the PDU session component 825 is capable of, configured to, or operable to support the following: selecting a second set of communication parameters for a second set of PDUs associated with an application, based on a mapping. In some examples, the PDU session component 825 is capable of, configured to, or operable to support the following: sending a second set of PDUs based on the second set of communication parameters.

[0185] In some examples, the first PDU set and the second PDU set are associated with the same QoS flow. In some examples, the first PDU set is associated with a first service type, and the second PDU set is associated with a second service type. In some examples, the first service type is associated with I-frames of video data, and the second service type is associated with P-frames of video data. In some examples, the first service type is associated with telemetry data, and the second service type is associated with audio data. In some examples, the first service type is associated with audio data, and the second service type is associated with audio metadata.

[0186] In some examples, the first communication parameter set includes a first QoS parameter set, and the second communication parameter set includes a second QoS parameter set. In some examples, the first QoS parameter set is associated with a first PDU set delay budget, a first PDU set error rate, and first PDU set integrated processing information, and the second QoS parameter set is associated with a second PDU set delay budget, a second PDU set error rate, and second PDU set integrated processing information.

[0187] In some examples, the delay budget, error rate, and integrated processing information of the first PDU set are associated with the first PSI field value, which are different from the delay budget, error rate, and integrated processing information of the second PDU set, respectively. The first PSI field value is different from the second PSI field value associated with the second PDU set.

[0188] In some examples, associated with the first PDU set and the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are equal to the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, respectively, and the first PSI field value is equal to the second PSI field value associated with the second PDU set.

[0189] Figure 9 A diagram of a system 900 including a device 905 supporting configuration for PSI field semantics and QoS provisioning, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller (e.g., I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

[0190] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0191] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may perform bidirectional communication using a wired or wireless link via one or more antennas 925 as described herein. For example, transceiver 915 may represent a wireless transceiver and may perform bidirectional communication with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0192] At least one memory 930 may include random access memory (RAM), read-only memory (ROM), or any combination thereof. At least one memory 930 may store computer-readable code, computer-executable code, or processor-executable code, such as code 935. Code 935 may include instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 930 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0193] At least one processor 940 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting techniques for configuring PSI field semantics and QoS provisioning). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein.

[0194] In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.

[0195] The communication manager 920 can support media session management according to the examples described herein. For example, the communication manager 920 can, is configured to, or is operable to support components for: establishing a PDU session between a first device and a second device based on an application at a first device. The communication manager 920 can, is configured to, or is operable to support components for: first communication that conveys information associated with the interpretation of the PSI field in the PDU header in connection with establishing the PDU session. The communication manager 920 can, is configured to, or is operable to support components for: second communication that conveys one or more PDUs from one or more PDU sets associated with an application based on the interpretation of the PSI field.

[0196] Additionally or alternatively, the communication manager 920 may support media session management according to the examples described herein. For example, the communication manager 920 can, is configured to, or is operable to support components for establishing a PDU session between a first device and a second device based on an application at the first device. The communication manager 920 can, is configured to, or is operable to support components for selecting a set of communication parameters for one or more PDUs associated with an application, based on the media type (as indicated by field values ​​such as PSI field values). The communication manager 920 can, is configured to, or is operable to support components for transmitting the one or more PDUs based on the set of communication parameters.

[0197] Additionally or alternatively, the communication manager 920 may support media session management according to the examples described herein. For example, the communication manager 920 is capable of, configured to, or operable to support components for: establishing a PDU session between a first device and a second device based on an application at the first device. The communication manager 920 is capable of, configured to, or operable to support components for: receiving information associated with a mapping between each of a set of multiple PDU sets and a corresponding set of communication parameters in connection with establishing a PDU session. The communication manager 920 is capable of, configured to, or operable to support components for: selecting a first set of communication parameters for a first PDU set associated with an application based on the mapping. The communication manager 920 is capable of, configured to, or operable to support components for: transmitting a first PDU set based on the first set of communication parameters.

[0198] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0199] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or executed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of the techniques described herein for configuring PSI field semantics and QoS provisioning, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0200] Figure 10 A block diagram 1000 of a device 1005 supporting configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, communication manager 1020) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0201] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0202] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0203] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be examples of components for various aspects of the techniques used to perform the configuration of PSI field semantics and QoS provisioning as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0204] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0205] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be executed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as a component for performing the functions described in this disclosure).

[0206] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0207] The communication manager 1020 can support media session management according to the examples described herein. For example, the communication manager 1020 is capable of, configured to, or operable to support components that: convey information associated with the interpretation of the PSI field of the PDU header of the PDU transmitted between the first and second devices in connection with the establishment of a PDU session between the first and second devices. The communication manager 1020 is capable of, configured to, or operable to support components that: convey a second communication associated with providing one or more PDUs from one or more PDU sets from the first device to the second device, based on the interpretation of the PSI field.

[0208] Additionally or alternatively, the communication manager 1020 may support media session management according to the examples described herein. For example, the communication manager 1020 is capable of, configured to, or operable to support components for: acquiring one or more PDUs in association with a PDU session between a first device and a second device. The communication manager 1020 is capable of, configured to, or operable to support components for: selecting a set of communication parameters for the one or more PDUs based on the media type associated with the one or more PDUs (as indicated by field values ​​such as PSI field values). The communication manager 1020 is capable of, configured to, or operable to support components for: transmitting the one or more PDUs according to the set of communication parameters.

[0209] Additionally or alternatively, the communication manager 1020 may support media session management according to the examples described herein. For example, the communication manager 1020 is capable of, configured to, or operable to support components for: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets in connection with the establishment of a PDU session between the first device and the second device; the communication manager 1020 is capable of, configured to, or operable to support components for: obtaining a first PDU set based on the PDU session between the first device and the second device; the communication manager 1020 is capable of, configured to, or operable to support components for: selecting a first communication parameter set for the associated first PDU set based on the mapping; and the communication manager 1020 is capable of, configured to, or operable to support components for: transmitting the first PDU set based on the first communication parameter set.

[0210] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., controlling receiver 1010, transmitter 1015, communication manager 1020 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0211] Figure 11 A block diagram 1100 of a device 1105 is shown, illustrating a technology supporting configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, communication manager 1120) may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0212] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0213] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0214] Device 1105 or its various components may be examples of various aspects of the techniques used to perform configurations for PSI field semantics and QoS provisioning as described herein. For example, communication manager 1120 may include PSI semantic component 1125, PDU session component 1130, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or integrate with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0215] Communication manager 1120 can support media session management according to the examples described herein. PSI semantic component 1125 is capable of, configured to, or operable to support components for: conveying information associated with the interpretation of the PSI field of the PDU header of the PDU transmitted between the first and second devices in connection with the establishment of a PDU session between the first and second devices. PDU session component 1130 is capable of, configured to, or operable to support components for: conveying second communication associated with providing one or more PDUs from one or more PDU sets from the first device to the second device, based on the interpretation of the PSI field.

[0216] Additionally or alternatively, the communication manager 1120 may support media session management according to the examples described herein. The PDU session component 1130 is capable of, configured to, or operable to support components for: acquiring one or more PDUs in association with a PDU session between a first device and a second device. The PDU session component 1130 is capable of, configured to, or operable to support components for: selecting a set of communication parameters for the one or more PDUs based on the media type associated with the associated one or more PDUs (as indicated by field values ​​such as PSI field values). The PDU session component 1130 is capable of, configured to, or operable to support components for: transmitting the one or more PDUs according to the set of communication parameters.

[0217] Additionally or alternatively, the communication manager 1120 may support media session management according to the examples described herein. The PDU session component 1130 is capable of, configured to, or operable to support components for: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets in connection with the establishment of a PDU session between the first and second devices. The PDU session component 1130 is capable of, configured to, or operable to support components for: obtaining a first PDU set based on the PDU session between the first and second devices. The PDU session component 1130 is capable of, configured to, or operable to support components for: selecting a first communication parameter set for the associated first PDU set based on the mapping. The PDU session component 1130 is capable of, configured to, or operable to support components for: transmitting the first PDU set based on the first communication parameter set.

[0218] Figure 12A block diagram 1200 of a communication manager 1220 supporting techniques for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of the techniques for configuring PSI field semantics and QoS provisioning as described herein. For example, the communication manager 1220 may include a PSI semantics component 1225, a PDU session component 1230, a resource allocation component 1235, a filtering component 1240, an AF component 1245, a QoS or QoE component 1250, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0219] Communication manager 1220 can support media session management according to the examples described herein. PSI semantic component 1225 is capable of, configured to, or operable to support components for: conveying information associated with the interpretation of the PSI field of the PDU header of the PDU transmitted between the first and second devices in connection with the establishment of a PDU session between the first and second devices. PDU session component 1230 is capable of, configured to, or operable to support components for: conveying second communication associated with providing one or more PDUs from one or more PDU sets from the first device to the second device, based on the interpretation of the PSI field.

[0220] In some examples, in order to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 1225 is capable of, configured to, or operable to support the receiving of information associated with the interpretation of a PSI field via a message communicated between a first device and a second device.

[0221] In some examples, in order to support receiving information associated with the interpretation of PSI fields via messages communicated between a first device and a second device, the PSI semantic component 1225 is capable of, configured to, or operable to support components for intercepting information associated with the interpretation of PSI fields from messages communicated between the first device and the second device via proxy call session control functions associated with network entities.

[0222] In some examples, network entities associate the PDU session between the first and second devices with the Internet Protocol Multimedia Subsystem and intercept the interpretation of the PSI field via the proxy call session control function.

[0223] In some examples, in order to support first communication conveying information associated with the interpretation of PSI fields, PSI semantic component 1225 is capable of, configured to, or operable to support receiving messages including information associated with the interpretation of PSI fields from a media session handler entity associated with a first or second device.

[0224] In some examples, the interpretation of the PSI field is extracted by the media session handler entity associated with the first or second device, based on the PDU session between the first and second devices and its association with WebRTC.

[0225] In some examples, to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 1225 is capable of, configured to, or operable to support components for: receiving a first message including a request for the interpretation of a PSI field. In some examples, to support first communication conveying information associated with the interpretation of a PSI field, the PSI semantic component 1225 is capable of, configured to, or operable to support components for: sending a second message including acceptance or modification of the interpretation of a PSI field, wherein the second communication conveying the information associated with providing the one or more PDUs is based on the network entity's acceptance or modification of the interpretation of the PSI field.

[0226] In some examples, the first message is a PDU session modification request message. In some examples, the PDU session modification request message includes a set of fields or one or more bits indicating the interpretation of the PSI field.

[0227] In some examples, the network entity is the core network entity.

[0228] In some examples, the resource allocation component 1235 is capable of, configured to, or able to operate to support components that determine resource allocation associated with the second communication based on the interpretation of the PSI field.

[0229] In some examples, in order to support the determination of resource allocation, the resource allocation component 1235 can be, configured, or operated to support the reconfiguration of a set of QoS parameters for multiple PDU sets associated with a PDU session via policy control functions associated with network entities.

[0230] In some examples, resource allocation component 1235 is capable of, can be configured to, or is operable to support components for identifying QoS flows via UPF associated with network entities based on the interpretation of the PSI field, wherein a set of QoS parameters of multiple PDU sets are reconfigured in association with identifying the QoS flow.

[0231] In some examples, resource allocation component 1235 is capable of, configured to, or operable to support components that: map service types to QoS parameter sets via policy control functions based on the interpretation of PSI fields, wherein a set of QoS parameters for multiple PDU sets is reconfigured in association with the service type-to-QoS parameter set mapping. In some examples, resource allocation component 1235 is capable of, configured to, or operable to support components that: send indications of the service type-to-QoS parameter set mapping to one or more of the SMF, UPF, or radio access network components associated with a network entity.

[0232] In some examples, to support the determination of resource allocation, the resource allocation component 1235 is capable of, configured to, or operable to support components that send an interpretation of the PSI field to one or more of the SMF, UPF, or radio access network components associated with the network entity as input for determining resource allocation. In some examples, to support the determination of resource allocation, the resource allocation component 1235 is capable of, configured to, or operable to support components that determine resource allocation at one or more of the SMF, UPF, or radio access network components associated with the network entity as the output of the determination.

[0233] In some examples, to support the determination of resource allocation, the resource allocation component 1235 is capable of, configured to, or operable to support components for accepting or modifying the interpretation of the PSI field. In some examples, to support the determination of resource allocation, the resource allocation component 1235 is capable of, configured to, or operable to support components for configuring one or more of the SMF, UPF, or radio access network components associated with a network entity in connection with accepting or modifying the interpretation of the PSI field.

[0234] In some examples, the resource allocation component 1235 is capable of, configured to, or operable to support components for sending second information associated with a resource allocation for a PDU session between the first device and the second device to one or both of the first device and the second device, wherein the second communication associated with providing the one or more PDUs is made in accordance with the resource allocation.

[0235] In some examples, resource allocation indicates: one or more first physical resources associated with a PDU session between a first device and a second device; one or more second physical resources for two or more network entities associated with providing the one or more PDUs from the first device to the second device; a first mapping between each PSI field value in a set of multiple PSI field values ​​and a corresponding QoS flow; a second mapping between each PSI field value in a set of multiple PSI field values ​​and a corresponding set of QoS parameters; a third mapping that associates two or more PSI field values ​​in a set of multiple PSI field values ​​with a corresponding set of PDUs having dependencies; or any combination thereof.

[0236] In some examples, in order to support the first communication conveying information associated with the interpretation of the PSI field, the PSI semantic component 1225 is capable of, configured to, or operable to support the sending of a message including information associated with the interpretation of the PSI field.

[0237] In some examples, to support the sending of the message, AF component 1245 is capable of, configured to, or able to operate to support the following: sending the message via an AF associated with a network entity to an application at one or both of a first device or a second device, in association with a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding service type, in conjunction with the interpretation indication of the PSI field.

[0238] In some examples, the message is sent based on a request for an updated interpretation of the PSI field. In some examples, the request is received from a radio access network component associated with the network entity. In some examples, the request is received based on the fulfillment of one or more conditions. In some examples, the message is sent based on the fulfillment of one or more conditions. In some examples, the one or more conditions include one or both of the following: the network congestion level meets a threshold network congestion level, or the network load level meets a threshold network load level. In some examples, the one or more conditions include: the PDU set error rate meets a threshold PDU set error rate, or the PDU set error rates for multiple service types are within a range close to each other's thresholds.

[0239] In some examples, the multiple service types include a first service type associated with I-frames of video data and a second service type associated with P-frames of video data. In some examples, the PSI field is interpreted to indicate the priority of I-frames of video data and the priority of P-frames of video data by decreasing the first PSI field value corresponding to the first PDU set of I-frames carrying video data and increasing the second PSI field value corresponding to the second PDU set of P-frames carrying video data.

[0240] In some examples, the QoS or QoE component 1250 is capable of, configured to, or able to operate to support components for receiving second information associated with a QoS metric or QoE metric, wherein an interpretation of the PSI field is sent to a network entity in connection with receiving one or both of the QoS metric or QoE metric.

[0241] In some examples, the QoS or QoE component 1250 is capable of, configured to, or operable to support components that forward one or both of the QoS or QoE metrics to a policy control function associated with a network entity. In some examples, the PSI semantic component 1225 is capable of, configured to, or operable to support components that generate interpretations of PSI fields at a policy control function.

[0242] In some examples, to support the sending of the message, the PSI semantic component 1225 is capable of, configured to, or able to operate to support the sending of the message to one or more of the following components: in association with the interpretation indication of the PSI fields, two or more PSI field values ​​from a set of multiple PSI field values ​​are associated with a mapping corresponding to a set of PDUs with dependencies: an application at one or both of the first or second devices, a UPF, or a radio access network component associated with a network entity.

[0243] In some examples, to support the sending of the message, the PSI semantic component 1225 is capable of, configured to, or able to operate to support the sending of the message to one or both of the UPF or the radio access network component associated with the network entity, in association with a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding set of QoS parameters, in relation to the interpretation indication of the PSI fields.

[0244] In some examples, the interpretation of the PSI field indicates a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding service type. In some examples, according to the mapping, a first PSI field value corresponds to a first service type, and a second PSI field value corresponds to a second service type. In some examples, according to the mapping, a first PSI field value corresponds to telemetry data, a second PSI field value corresponds to audio data, a third PSI field value corresponds to an I-frame of video data, and a fourth PSI field value corresponds to a P-frame of video data.

[0245] In some examples, the interpretation of the PSI field indicates a mapping that associates two or more PSI field values ​​from a set of multiple PSI field values ​​with corresponding PDU sets having dependencies. In some examples, according to the mapping, a first PDU set associated with a first PSI field value and a second PDU set associated with a second PSI field value have a first dependency. In some examples, the first dependency indicates that the first PDU set depends on the second PDU set. In some examples, the first PDU set is associated with audio data, and the second PDU set is associated with audio metadata. In some examples, the first PDU set is associated with P-frames of video data, and the second PDU set is associated with I-frames of video data.

[0246] In some examples, according to the mapping, the third PDU set associated with the third PSI field value and the fourth PDU set associated with the fourth PSI field value have a second dependency. In some examples, the second dependency indicates that the third PDU set depends on the fourth PDU set.

[0247] In some examples, the interpretation of the PSI field indicates a mapping that associates each PSI field value in a set of multiple PSI field values ​​with a corresponding set of communication parameters. In some examples, according to the mapping, a first PSI field value corresponds to a first set of communication parameters, and a second PSI field value corresponds to a second set of communication parameters. In some examples, the corresponding set of communication parameters includes a corresponding set of QoS parameters. In some examples, according to the mapping, a first PSI field value corresponds to a first set of QoS parameters, and a second PSI field value corresponds to a second set of QoS parameters. In some examples, the first set of QoS parameters includes a first set of PDU delay budget and a first set of PDU error rate, and the second set of QoS parameters includes a second set of PDU delay budget and a second set of PDU error rate.

[0248] In some examples, to support the communication of a second communication associated with the provision of the one or more PDUs, the PDU session component 1230 is capable of, configured to, or operable to support the following: obtaining a first PDU associated with a first PSI field value. In some examples, to support the communication of a second communication associated with the provision of the one or more PDUs, the filtering component 1240 is capable of, configured to, or operable to support the following: filtering the first PDU according to a grouping filter based on the first PSI field value. In some examples, to support the communication of a second communication associated with the provision of the one or more PDUs, the filtering component 1240 is capable of, configured to, or operable to support the following: determining a first QoS flow associated with the first PDU, defined at least in part based on the first PSI field value. In some examples, to support the communication of a second communication associated with the provision of the one or more PDUs, the PDU session component 1230 is capable of, configured to, or operable to support the following: sending the first PDU according to a set of communication parameters associated with the first QoS flow.

[0249] In some examples, the PDU session component 1230 is capable of, configured to, or able to operate to support components for: sending second information associated with a mapping between each of a set of multiple PDU sets and a corresponding QoS parameter set in connection with the establishment of a PDU session, wherein, according to the mapping, a first PDU set of a first QoS flow is associated with a first QoS parameter set, and a second PDU set of a first QoS flow is associated with a second QoS parameter set.

[0250] Additionally or alternatively, the communication manager 1220 may support media session management according to the examples described herein. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: acquiring one or more PDUs in association with a PDU session between a first device and a second device. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: selecting a set of communication parameters for the one or more PDUs based on the media type associated with the one or more PDUs (as indicated by field values ​​such as PSI field values). In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: transmitting the one or more PDUs according to the set of communication parameters.

[0251] In some examples, PDU session component 1230 is capable of, configured to, or operable to support components for obtaining one or more PDUs from either a first device or a second device or from a UPF associated with a network entity. In some examples, filtering component 1240 is capable of, configured to, or operable to support components for filtering (e.g., grouping) one or more PDUs into a QoS flow according to a packet filter based on a PSI field value, wherein the set of communication parameters is selected in association with filtering (e.g., grouping) one or more PDUs according to a packet filter based on a PSI field value.

[0252] In some examples, the filtering component 1240 is capable of, can be configured to, or is operable to support components for determining QoS flows associated with one or more PDUs based on a group filter, wherein the set of communication parameters is selected in connection with determining the QoS flows associated with one or more PDUs.

[0253] In some examples, the PSI field value and the Internet Protocol parameter set jointly define the QoS flow based on a packet filter. In some examples, the corresponding PSI field value and the corresponding Internet Protocol parameter set jointly define the corresponding QoS flow based on a packet filter. In some examples, the packet filter is an Internet Protocol packet filter or an Ethernet packet filter. In some examples, the communication parameter set includes a QoS parameter set.

[0254] Additionally or alternatively, the communication manager 1220 may support media session management according to examples as described herein. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets in connection with the establishment of a PDU session between the first device and the second device. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: obtaining a first PDU set based on the PDU session between the first device and the second device. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: selecting a first communication parameter set for the associated first PDU set based on the mapping. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support components for: transmitting the first PDU set based on the first communication parameter set.

[0255] In some examples, the first PDU set is obtained from either the first or second device, or from the UPF associated with the network entity.

[0256] In some examples, the PDU session component 1230 is capable of, configured to, or operable to support the following: obtaining a second PDU set based on a PDU session between a first device and a second device. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support the following: selecting a second set of communication parameters for the second PDU set based on a mapping. In some examples, the PDU session component 1230 is capable of, configured to, or operable to support the following: sending the second PDU set based on the second set of communication parameters.

[0257] In some examples, the first PDU set and the second PDU set are associated with the same QoS flow.

[0258] In some examples, a first PDU set is associated with a first service type (e.g., a first media type), and a second PDU set is associated with a second service type (e.g., a second media type). In some examples, a first service type is associated with I-frames of video data, and a second service type is associated with P-frames of video data. In some examples, a first service type is associated with telemetry data, and a second service type is associated with audio data. In some examples, a first service type is associated with audio data, and a second service type is associated with audio metadata.

[0259] In some examples, the first communication parameter set includes a first QoS parameter set, and the second communication parameter set includes a second QoS parameter set. In some examples, the first QoS parameter set is associated with a first PDU set delay budget, a first PDU set error rate, and first PDU set integrated processing information, and the second QoS parameter set is associated with a second PDU set delay budget, a second PDU set error rate, and second PDU set integrated processing information.

[0260] In some examples, the delay budget, error rate, and integrated processing information of the first PDU set are associated with the first PSI field value, which are different from the delay budget, error rate, and integrated processing information of the second PDU set, respectively. The first PSI field value is different from the second PSI field value associated with the second PDU set.

[0261] In some examples, associated with the first PDU set and the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are equal to the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, respectively, and the first PSI field value is equal to the second PSI field value associated with the second PDU set.

[0262] Figure 13 A diagram of a system 1300 including a device 1305 supporting configuration for PSI field semantics and QoS provisioning, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and acquisition of communication, such as a communication manager 1320, a transceiver 1310, one or more antennas 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1340).

[0263] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1315, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0264] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1330. Code 1330 may include instructions that, when executed by one or more processors of at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by one of the processors of at least one processor 1335, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0265] At least one processor 1335 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more GPUs, one or more NPUs (also known as neural network processors or DLPs), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting techniques for configuring PSI field semantics and QoS provisioning). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, wherein the at least one processor 1335 and the at least one memory 1325 are configured to perform the various functions described herein. At least one processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1330) host various functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories in at least one memory 1325).

[0266] In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1335 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1335 or a processing system including at least one processor 1335 may be configured, capable of being configured, or operable to cause device 1305 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1325 or otherwise.

[0267] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one component of different components or partitioned between different components).

[0268] In some examples, the communication manager 1320 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 can manage the transfer of data communication with client devices, such as one or more UEs 115. In some examples, the communication manager 1320 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., cooperating with one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0269] Communication manager 1320 can support media session management according to examples as described herein. For example, communication manager 1320 is capable of, configured to, or operable to support components that: communicate information associated with the interpretation of the PSI field of the PDU header of the PDU transmitted between the first and second devices in connection with the establishment of a PDU session between the first and second devices. Communication manager 1320 is capable of, configured to, or operable to support components that: communicate a second communication associated with the provision of one or more PDUs from one or more PDU sets from the first device to the second device, based on the interpretation of the PSI field.

[0270] Additionally or alternatively, the communication manager 1320 may support media session management according to the examples described herein. For example, the communication manager 1320 is capable of, configured to, or operable to support components for: acquiring one or more PDUs in association with a PDU session between a first device and a second device. The communication manager 1320 is capable of, configured to, or operable to support components for: selecting a set of communication parameters for the one or more PDUs based on the media type associated with the one or more PDUs (as indicated by field values ​​such as PSI field values). The communication manager 1320 is capable of, configured to, or operable to support components for: transmitting the one or more PDUs according to the set of communication parameters.

[0271] Additionally or alternatively, the communication manager 1320 may support media session management according to the examples described herein. For example, the communication manager 1320 is capable of, configured to, or operable to support components for: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of multiple PDU sets in connection with the establishment of a PDU session between the first device and the second device; the communication manager 1320 is capable of, configured to, or operable to support components for: obtaining a first PDU set based on the PDU session between the first device and the second device; the communication manager 1320 is capable of, configured to, or operable to support components for: selecting a first communication parameter set for the associated first PDU set based on the mapping; and the communication manager 1320 is capable of, configured to, or operable to support components for: transmitting the first PDU set based on the first communication parameter set.

[0272] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience associated with processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0273] In some examples, the communication manager 1320 may be configured to use or otherwise cooperate with transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more of at least one processor 1335 to cause device 1305 to perform various aspects of the techniques described herein for configuring PSI field semantics and QoS provisioning, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0274] Figure 14 A flowchart illustrating a method 1400 for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be performed by, as referenced... Figure 1 - Figure 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0275] At 1405, the method may include: establishing a PDU session between the first device and the second device based on an application at the first device. The operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0276] At 1410, the method may include: a first communication that, in association with establishing a PDU session, conveys information associated with the interpretation of the PSI field of the PDU header. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to... Figure 8 The described PSI semantic component 830 is executed.

[0277] At 1415, the method may include: conveying a second communication, based on the interpretation of the PSI field, one or more PDUs from one or more PDU sets associated with the application. The operation of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 8 The described PSI semantic component 830 is executed.

[0278] Figure 15 A flowchart illustrating a method 1500 for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figure 1 - Figure 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0279] At 1505, the method may include: establishing a PDU session between the first device and the second device based on an application at the first device. The operation of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0280] At 1510, the method may include: selecting a set of communication parameters for one or more PDUs associated with the application based on a media type associated with those PDUs. The operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0281] At point 1515, the method may include: sending the one or more PDUs according to a set of communication parameters. The operation of point 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of point 1515 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0282] Figure 16 A flowchart illustrating a method 1600 for configuring PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be implemented by, as referenced... Figure 1 - Figure 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0283] At 1605, the method may include: establishing a PDU session between the first device and the second device based on an application at the first device. The operation of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0284] At 1610, the method may include: receiving information associated with a mapping between each of a plurality of PDU sets and a corresponding set of communication parameters, in connection with establishing a PDU session. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 8 The described PDU session component 825 is executed.

[0285] At 1615, the method may include: selecting, according to a mapping, a first set of communication parameters for a first set of PDUs associated with an application and a second set of communication parameters for a second set of PDUs associated with an application, wherein the first set of PDUs and the second set of PDUs are associated with the same QoS flow. The operation of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 8 The described PDU session component 825 is executed.

[0286] At 1620, the method may include: sending a first set of PDUs according to a first set of communication parameters. The operation of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1620 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0287] At 1625, the method may include: sending a second set of PDUs according to a second set of communication parameters. The operation at 1625 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1625 may be provided by reference to [reference needed]. Figure 8 The described PDU session component 825 is executed.

[0288] Figure 17 A flowchart illustrating a method 1700 that supports configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be performed by, as referenced... Figure 1 - Figure 5 and Figure 10 - Figure 13 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0289] At 1705, the method may include: a first communication relating to the establishment of a PDU session between the first and second devices, conveying information associated with the interpretation of the PSI field of the PDU header of the PDU communicated between the first and second devices. Operation of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1705 may be provided by reference to... Figure 12 The described PSI semantic component 1225 is executed.

[0290] At 1710, the method may include: conveying a second communication associated with providing one or more PDUs from a set of one or more PDUs from a first device to a second device, based on the interpretation of the PSI field. Operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be provided by reference to... Figure 12 The described PDU session component 1230 is executed.

[0291] Figure 18 A flowchart illustrating a method 1800 that supports configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. The operation of method 1800 can be implemented by a network entity or its components as described herein. For example, the operation of method 1800 can be implemented by, as referenced... Figure 1 - Figure 5 and Figure 10 - Figure 13 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0292] At 1805, the method may include: obtaining one or more PDUs in association with a PDU session between the first device and the second device. The operation of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0293] At 1810, the method may include: selecting a set of communication parameters for the one or more PDUs based on the media type associated with those PDUs. The operation of 1810 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0294] At 1815, the method may include: sending the one or more PDUs according to a set of communication parameters. The operation of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 12 The described PDU session component 1230 is executed.

[0295] Figure 19 A flowchart illustrating a method 1900 that supports configuration for PSI field semantics and QoS provisioning according to one or more aspects of this disclosure is shown. The operation of method 1900 can be implemented by a network entity or its components as described herein. For example, the operation of method 1900 can be implemented by, as referenced... Figure 1 - Figure 5 and Figure 10 - Figure 13 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0296] At 1905, the method may include: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a set of a plurality of PDU sets, in connection with the establishment of a PDU session between the first device and the second device. The operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0297] At 1910, the method may include: obtaining a first PDU set and a second PDU set based on a PDU session between a first device and a second device, wherein the first PDU set and the second PDU set are associated with the same QoS flow. The operation of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0298] At point 1915, the method may include: sending a first set of PDUs according to a first set of communication parameters mapped to the first set of PDUs. The operation at point 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at point 1915 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0299] At point 1920, the method may include: sending a second PDU set according to a second set of communication parameters mapped to the second PDU set. The operation at point 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at point 1920 may be derived from references... Figure 12 The described PDU session component 1230 is executed.

[0300] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for media session management at a first device, the method comprising: establishing a PDU session between a first device and a second device based on an application at the first device; a first communication that communicates information associated with an interpretation of a PSI field in a PDU header in connection with establishing the PDU session; and a second communication that communicates one or more PDUs from one or more sets of PDUs associated with the application based on the interpretation of the PSI field.

[0301] Aspect 2: According to the method of aspect 1, the first communication conveying the information associated with the interpretation of the PSI field includes: sending to or receiving from the second device a message including the information associated with the interpretation of the PSI field.

[0302] Aspect 3: According to the method of aspect 2, the method further includes: extracting the interpretation of the PSI field via a media session handling procedure associated with the first device; and sending the information associated with the interpretation of the PSI field to a network entity, wherein the second communication conveying the one or more PDUs is performed in connection with sending the information associated with the interpretation of the PSI field to the network entity.

[0303] Aspect 4: According to the method of aspect 3, wherein the network entity is AF, and the first device is associated with WebRTC based on the PDU session, and extracts the interpretation of the PSI field via the media session handler.

[0304] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first communication conveying the information associated with the interpretation of the PSI field comprises: sending a first message to a network entity including a request for the interpretation of the PSI field; and receiving a second message from the network entity, the second message including an acceptance or modification of the interpretation of the PSI field requested by the first device, wherein the second communication conveying the one or more PDUs is performed based on the network entity's acceptance or modification of the interpretation of the PSI field.

[0305] Aspect 6: According to the method of aspect 5, wherein the first message is a PDU session modification request message, and the PDU session modification request message includes a set of fields or one or more bits indicating the interpretation of the PSI field requested by the first device.

[0306] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the network entity is a core network entity.

[0307] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving second information associated with a resource allocation for the PDU session between the first device and the second device, wherein the second communication conveying the one or more PDUs is performed in accordance with the resource allocation.

[0308] Aspect 9: The method according to aspect 8, wherein the resource allocation indicates: one or more physical resources associated with the PDU session, a first mapping between each of a plurality of PSI field values ​​and a corresponding QoS flow, a second mapping between each of the plurality of PSI field values ​​and a corresponding set of QoS parameters, a third mapping that associates two or more of the plurality of PSI field values ​​as corresponding to a set of PDUs with dependencies, or any combination thereof.

[0309] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the resource allocation is received from a network entity.

[0310] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first communication conveying the information associated with the interpretation of the PSI field comprises: receiving from a network entity a message including the information associated with the interpretation of the PSI field.

[0311] Aspect 12: According to the method of aspect 11, the message is received from the network entity based on the satisfaction of one or more conditions.

[0312] Aspect 13: According to the method of aspect 12, the one or more conditions include one or two of the following: the network congestion level meets a threshold network congestion level, or the network load level meets a threshold network load level.

[0313] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the one or more conditions include: the PDU set error rate meets a threshold PDU set error rate, or the PDU set error rates for multiple service types are within a range close to each other's thresholds.

[0314] Aspect 15: According to the method of aspect 14, wherein the plurality of service types include a first service type associated with an I-frame of video data and a second service type associated with a P-frame of video data, and the interpretation of the PSI field indicates the priority of the I-frame of video data to be increased and the priority of the P-frame of video data to be decreased by decreasing the first PSI field value corresponding to a first PDU set of the I-frame carrying video data and increasing the second PSI field value corresponding to a second PDU set of the P-frame carrying video data.

[0315] Aspect 16: The method according to any one of Aspects 11 to 15, the method further comprising: sending to the network entity second information associated with a QoS metric or a QoE metric, wherein the interpretation of the PSI field is received from the network entity in connection with sending to the network entity one or both of the QoS metric or the QoE metric.

[0316] Aspect 17: According to the method of aspect 16, wherein the network entity forwards one or both of the QoS metric or the QoE metric to a policy control function associated with the network entity, and the policy control function generates the interpretation of the PSI field.

[0317] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the interpretation of the PSI field indicates a mapping that associates each of the plurality of PSI field values ​​with a corresponding business type.

[0318] Aspect 19: According to the method of aspect 18, wherein, according to the mapping, the first PSI field value corresponds to the first service type, and the second PSI field value corresponds to the second service type.

[0319] Aspect 20: The method according to any one of Aspects 18 to 19, wherein, according to the mapping, a first PSI field value corresponds to telemetry data, a second PSI field value corresponds to audio data, a third PSI field value corresponds to an I-frame of video data, and a fourth PSI field value corresponds to a P-frame of video data.

[0320] Aspect 21: The method according to any one of Aspects 1 to 20, wherein the interpretation of the PSI field indicates associating two or more PSI field values ​​among a plurality of PSI field values ​​as a mapping corresponding to a set of PDUs with dependencies.

[0321] Aspect 22: According to the method of aspect 21, wherein, according to the mapping, a first set of PDUs associated with a first PSI field value and a second set of PDUs associated with a second PSI field value have a first dependency relationship.

[0322] Aspect 23: According to the method of aspect 22, wherein the first dependency indicates that the first PDU set depends on the second PDU set.

[0323] Aspect 24: According to the method of aspect 23, wherein the first PDU set is associated with audio data and the second PDU set is associated with audio metadata.

[0324] Aspect 25: The method according to any one of Aspects 23 to 24, wherein the first PDU set is associated with P frames of video data and the second PDU set is associated with I frames of video data.

[0325] Aspect 26: The method according to any one of Aspects 22 to 25, wherein, according to the mapping, a third PDU set associated with a third PSI field value and a fourth PDU set associated with a fourth PSI field value have a second dependency relationship, and the second dependency relationship indicates that the third PDU set depends on the fourth PDU set.

[0326] Aspect 27: The method according to any one of aspects 1 to 26, wherein the interpretation of the PSI field indicates a mapping that associates each of the plurality of PSI field values ​​with a corresponding set of communication parameters.

[0327] Aspect 28: According to the method of aspect 27, wherein, according to the mapping, the first PSI field value corresponds to the first set of communication parameters, and the second PSI field corresponds to the second set of communication parameters.

[0328] Aspect 29: The method according to any one of Aspects 27 to 28, wherein the corresponding communication parameter set includes a corresponding QoS parameter set.

[0329] Aspect 30: According to the method of aspect 29, wherein, according to the mapping, the first PSI field value corresponds to the first QoS parameter set, and the second PSI field value corresponds to the second QoS parameter set.

[0330] Aspect 31: According to the method of aspect 30, the first QoS parameter set includes a first PDU set delay budget and a first PDU set error rate, and the second QoS parameter set includes a second PDU set delay budget and a second PDU set error rate.

[0331] Aspect 32: The method according to any one of aspects 1 to 31, wherein the second communication conveying the one or more PDUs comprises: obtaining a first PDU from the application; filtering the first PDU according to a packet filter based at least in part on a first PSI field value associated with the first PDU; determining a first QoS flow associated with the first PDU based at least in part on the packet filter; and transmitting the first PDU according to a set of QoS parameters associated with the first QoS flow.

[0332] Aspect 33: The method according to any one of aspects 1 to 32, the method further comprising: receiving, in association with establishing the PDU session, second information associated with a mapping between each of a plurality of PDU sets and a corresponding QoS parameter set, wherein, according to the mapping, a first PDU set of a first QoS flow is associated with a first QoS parameter set, and a second PDU set of a first QoS flow is associated with a second QoS parameter set.

[0333] Aspect 34: A method for media session management at a first device, the method comprising: establishing a PDU session between a first device and a second device based on an application at the first device; selecting a set of communication parameters for the one or more PDUs associated with the application based on a media type (such as indicated by a field value, such as a PSI field value); and transmitting the one or more PDUs based on the set of communication parameters.

[0334] Aspect 35: The method according to aspect 34 further includes: obtaining the one or more PDUs from the application; and filtering (e.g., grouping) the one or more PDUs into a QoS stream according to a grouping filter based at least in part on the PSI field value, wherein the set of communication parameters is selected in association with filtering (e.g., grouping) the one or more PDUs according to the grouping filter based at least in part on the PSI field value.

[0335] Aspect 36: The method according to aspect 35, the method further comprising: determining a QoS flow associated with the one or more PDUs based at least in part on the packet filter, wherein the set of communication parameters is selected in connection with determining the QoS flow associated with the one or more PDUs.

[0336] Aspect 37: According to the method of aspect 36, wherein the PSI field value and the Internet Protocol parameter set jointly define the QoS flow according to the packet filter.

[0337] Aspect 38: The method according to any one of Aspects 36 to 37, wherein the corresponding PSI field value and the corresponding Internet Protocol parameter set jointly define the corresponding QoS flow according to the packet filter.

[0338] Aspect 39: The method according to any one of Aspects 35 to 38, wherein the packet filter is an Internet Protocol packet filter or an Ethernet packet filter.

[0339] Aspect 40: The method according to any one of aspects 34 to 39, wherein the set of communication parameters includes a set of QoS parameters.

[0340] Aspect 41: A method for media session management at a first device, the method comprising: establishing a PDU session between a first device and a second device based on an application at the first device; receiving information associated with a mapping between each of a plurality of PDU sets and a corresponding communication parameter set in connection with establishing the PDU session; selecting a first communication parameter set for a first PDU set associated with the application based on the mapping; and transmitting the first PDU set based on the first communication parameter set.

[0341] Aspect 42: According to the method of aspect 41, the method further includes: selecting a second set of communication parameters for a second set of PDUs associated with the application based on the mapping; and sending the second set of PDUs based on the second set of communication parameters.

[0342] Aspect 43: According to the method of aspect 42, wherein the first PDU set and the second PDU set are associated with the same QoS flow.

[0343] Aspect 44: The method according to any one of Aspects 42 to 43, wherein the first PDU set is associated with a first service type and the second PDU set is associated with a second service type.

[0344] Aspect 45: According to the method of aspect 44, wherein the first service type is associated with an I-frame of video data and the second service type is associated with a P-frame of video data.

[0345] Aspect 46: The method according to any one of Aspects 44 to 45, wherein the first service type is associated with telemetry data and the second service type is associated with audio data.

[0346] Aspect 47: The method according to any one of Aspects 44 to 46, wherein the first service type is associated with audio data and the second service type is associated with audio metadata.

[0347] Aspect 48: The method according to any one of aspects 42 to 47, wherein the first set of communication parameters includes a first set of QoS parameters, and the second set of communication parameters includes a second set of QoS parameters.

[0348] Aspect 49: According to the method of aspect 48, wherein the first QoS parameter set is associated with the first PDU set delay budget, the first PDU set error rate and the first PDU set integrated processing information, and the second QoS parameter set is associated with the second PDU set delay budget, the second PDU set error rate and the second PDU set integrated processing information.

[0349] Aspect 50: According to the method of aspect 49, wherein, associated with the first PDU set and the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are different from the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, respectively, and the first PSI field value is different from the second PSI field value associated with the second PDU set.

[0350] Aspect 51: The method according to any one of Aspects 49 to 50, wherein, associated with the first PDU set and in relation to the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are respectively equal to the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, and the first PSI field value is equal to the second PSI field value associated with the second PDU set.

[0351] Aspect 52: A method for media session management at a network entity, the method comprising: first communication relating to the establishment of a PDU session between a first device and a second device, conveying information associated with the interpretation of a PSI field in a PDU header of a PDU transmitted between the first device and the second device; and second communication relating to the provision of one or more PDUs from one or more PDU sets from the first device to the second device based on the interpretation of the PSI field.

[0352] Aspect 53: According to the method of aspect 52, the first communication conveying the information associated with the interpretation of the PSI field includes: receiving the information associated with the interpretation of the PSI field via a message communicated between the first device and the second device.

[0353] Aspect 54: According to the method of aspect 53, receiving the information associated with the interpretation of the PSI field via the message communicated between the first device and the second device includes: intercepting the information associated with the interpretation of the PSI field from the message communicated between the first device and the second device via a proxy call session control function associated with the network entity.

[0354] Aspect 55: According to the method of aspect 54, wherein the network entity is associated with the Internet Protocol Multimedia Subsystem based on the PDU session between the first device and the second device, and intercepts the interpretation of the PSI field via the proxy call session control function.

[0355] Aspect 56: The method according to any one of Aspects 52 to 55, wherein the first communication conveying the information associated with the interpretation of the PSI field comprises: receiving a message including the information associated with the interpretation of the PSI field from a media session handler entity associated with the first device or the second device.

[0356] Aspect 57: According to the method of aspect 56, wherein the interpretation of the PSI field is extracted by the media session handler entity associated with the first device or the second device based on the PDU session between the first device and the second device being associated with WebRTC.

[0357] Aspect 58: The method according to any one of Aspects 52 to 57, wherein the first communication conveying the information associated with the interpretation of the PSI field comprises: receiving a first message including a request for the interpretation of the PSI field; and sending a second message including acceptance or modification of the interpretation of the PSI field, wherein the second communication conveying the information associated with providing the one or more PDUs is based on the network entity's acceptance or modification of the interpretation of the PSI field.

[0358] Aspect 59: According to the method of aspect 58, wherein the first message is a PDU session modification request message, and the PDU session modification request message includes a field or a set of one or more bits indicating the interpretation of the PSI field.

[0359] Aspect 60: The method according to any one of Aspects 58 to 59, wherein the network entity is a core network entity.

[0360] Aspect 61: The method according to any one of aspects 52 to 60, the method further comprising: determining a resource allocation associated with the second communication based on the interpretation of the PSI field.

[0361] Aspect 62: According to the method of aspect 61, determining the resource allocation includes: reconfiguring QoS parameters of a plurality of PDU sets associated with the PDU session via a policy control function associated with the network entity.

[0362] Aspect 63: The method according to aspect 62, the method further comprising: identifying a QoS flow via a UPF associated with the network entity based on the interpretation of the PSI field, wherein the QoS parameters of the plurality of PDU sets are reconfigured in association with identifying the QoS flow.

[0363] Aspect 64: The method according to any one of Aspects 62 to 63, the method further comprising: mapping a service type to a QoS parameter set via the policy control function according to the interpretation of the PSI field, wherein the QoS parameters of the plurality of PDU sets are reconfigured in association with the mapping of the service type to the QoS parameter set; and sending an indication of the mapping of the service type to the QoS parameter set to one or more of the SMF, UPF, or radio access network components associated with the network entity.

[0364] Aspect 65: The method according to any one of Aspects 61 to 64, wherein determining the resource allocation comprises: sending the interpretation of the PSI field to one or more of the SMF, UPF, or radio access network components associated with the network entity as input for determining the resource allocation; and determining the resource allocation at one or more of the SMF, the UPF, or the radio access network components associated with the network entity as output of the determination.

[0365] Aspect 66: The method according to any one of Aspects 61 to 65, wherein determining the resource allocation comprises: accepting or modifying the interpretation of the PSI field; and configuring one or more of the SMF, UPF, or radio access network components associated with the network entity in connection with accepting or modifying the interpretation of the PSI field.

[0366] Aspect 67: The method according to any one of aspects 61 to 66, the method further comprising: sending to one or both of the first device or the second device second information associated with a resource allocation for a PDU session between the first device and the second device, wherein the second communication associated with providing the one or more PDUs is performed based on the resource allocation.

[0367] Aspect 68: The method according to any one of Aspects 61 to 67, wherein the resource allocation indicates: one or more first physical resources associated with the PDU session between the first device and the second device, one or more second physical resources for two or more network entities associated with providing the one or more PDUs from the first device to the second device, a first mapping between each of a plurality of PSI field values ​​and a corresponding QoS flow, a second mapping between each of the plurality of PSI field values ​​and a corresponding set of QoS parameters, a third mapping that associates two or more of the plurality of PSI field values ​​as corresponding to a set of PDUs with dependencies, or any combination thereof.

[0368] Aspect 69: The method according to any one of Aspects 52 to 68, wherein the first communication conveying the information associated with the interpretation of the PSI field comprises: sending a message including the information associated with the interpretation of the PSI field.

[0369] Aspect 70: According to the method of aspect 69, sending the message includes: in association with the interpretation indication of the PSI field, a mapping that associates each of the plurality of PSI field values ​​with a corresponding service type, sending the message via an AF associated with the network entity to an application at one or both of the first device or the second device.

[0370] Aspect 71: The method according to aspect 70, wherein the message is sent in accordance with a request for an updated interpretation of the PSI field.

[0371] Aspect 72: The method according to aspect 71, wherein the request is received from a radio access network component associated with the network entity, and the request is received based on the satisfaction of one or more conditions.

[0372] Aspect 73: The method according to any one of aspects 70 to 72, wherein the message is sent based on the satisfaction of one or more conditions.

[0373] Aspect 74: According to the method of aspect 73, the one or more conditions include one or two of the following: the network congestion level meets a threshold network congestion level, or the network load level meets a threshold network load level.

[0374] Aspect 75: The method according to any one of Aspects 73 to 74, wherein the one or more conditions include: the PDU set error rate meets a threshold PDU set error rate, or the PDU set error rates for multiple service types are within a range close to each other's thresholds.

[0375] Aspect 76: According to the method of aspect 75, wherein the plurality of service types includes a first service type associated with an I-frame of video data and a second service type associated with a P-frame of video data, and the interpretation of the PSI field indicates increasing the priority of the I-frame of video data and decreasing the priority of the P-frame of video data by decreasing the first PSI field value corresponding to a first PDU set of the I-frame carrying video data, and increasing the second PSI field value corresponding to a second PDU set of the P-frame carrying video data.

[0376] Aspect 77: The method according to any one of aspects 70 to 76, the method further comprising: receiving second information associated with a QoS metric or a QoE metric, wherein the interpretation of the PSI field is sent to the network entity in connection with receiving one or both of the QoS metric or the QoE metric.

[0377] Aspect 78: The method according to aspect 77 further includes: forwarding one or both of the QoS metric or the QoE metric to a policy control function associated with the network entity; and generating the interpretation of the PSI field at the policy control function.

[0378] Aspect 79: The method according to any one of Aspects 69 to 78, wherein sending the message comprises: in association with the interpretation indication of the PSI field, associating two or more PSI field values ​​of a plurality of PSI field values ​​as a mapping corresponding to a set of PDUs with dependencies, sending the message to one or more of the following: an application, a UPF, or a radio access network component associated with the network entity at one or both of the first device or the second device.

[0379] Aspect 80: The method according to any one of Aspects 69 to 79, wherein sending the message comprises: sending the message to one or both of the UPF or the radio access network component associated with the network entity, in association with a mapping that associates each of a plurality of PSI field values ​​with a corresponding set of QoS parameters, in relation to the interpretation indication of the PSI field.

[0380] Aspect 81: The method according to any one of Aspects 52 to 80, wherein the interpretation of the PSI field indicates a mapping that associates each of the plurality of PSI field values ​​with a corresponding business type.

[0381] Aspect 82: According to the method of aspect 81, wherein, according to the mapping, the first PSI field value corresponds to the first service type, and the second PSI field value corresponds to the second service type.

[0382] Aspect 83: The method according to any one of Aspects 81 to 82, wherein, according to the mapping, a first PSI field value corresponds to telemetry data, a second PSI field value corresponds to audio data, a third PSI field value corresponds to an I-frame of video data, and a fourth PSI field value corresponds to a P-frame of video data.

[0383] Aspect 84: The method according to any one of Aspects 52 to 83, wherein the interpretation of the PSI field indicates associating two or more PSI field values ​​among a plurality of PSI field values ​​as a mapping corresponding to a set of PDUs with dependencies.

[0384] Aspect 85: The method according to aspect 84, wherein, according to the mapping, a first set of PDUs associated with a first PSI field value and a second set of PDUs associated with a second PSI field value have a first dependency relationship.

[0385] Aspect 86: The method according to aspect 85, wherein the first dependency indicates that the first PDU set depends on the second PDU set.

[0386] Aspect 87: The method according to aspect 86, wherein the first PDU set is associated with audio data and the second PDU set is associated with audio metadata.

[0387] Aspect 88: The method according to any one of Aspects 86 to 87, wherein the first PDU set is associated with P frames of video data and the second PDU set is associated with I frames of video data.

[0388] Aspect 89: The method according to any one of aspects 85 to 88, wherein, according to the mapping, a third PDU set associated with a third PSI field value and a fourth PDU set associated with a fourth PSI field value have a second dependency relationship, and the second dependency relationship indicates that the third PDU set depends on the fourth PDU set.

[0389] Aspect 90: The method according to any one of aspects 52 to 89, wherein the interpretation of the PSI field indicates a mapping that associates each of the plurality of PSI field values ​​with a corresponding set of communication parameters.

[0390] Aspect 91: According to the method of aspect 90, wherein, according to the mapping, the first PSI field value corresponds to the first set of communication parameters, and the second PSI field corresponds to the second set of communication parameters.

[0391] Aspect 92: The method according to any one of aspects 90 to 91, wherein the corresponding communication parameter set includes a corresponding QoS parameter set.

[0392] Aspect 93: According to the method of aspect 92, wherein, according to the mapping, the first PSI field value corresponds to the first QoS parameter set, and the second PSI field value corresponds to the second QoS parameter set.

[0393] Aspect 94: According to the method of aspect 93, wherein the first QoS parameter set includes a first PDU set delay budget and a first PDU set error rate, and the second QoS parameter set includes a second PDU set delay budget and a second PDU set error rate.

[0394] Aspect 95: The method according to any one of aspects 52 to 94, wherein conveying the second communication associated with providing the one or more PDUs comprises: obtaining a first PDU associated with a first PSI field value; filtering the first PDU according to a packet filter at least partially based on the first PSI field value; determining a first QoS flow associated with the first PDU based at least partially based on the first PSI field value; and transmitting the first PDU according to a set of communication parameters associated with the first QoS flow.

[0395] Aspect 96: The method according to any one of aspects 52 to 95, the method further comprising: transmitting, in association with the establishment of the PDU session, second information associated with a mapping between each of a plurality of PDU sets and a corresponding QoS parameter set, wherein, according to the mapping, a first PDU set of a first QoS flow is associated with a first QoS parameter set, and a second PDU set of a first QoS flow is associated with a second QoS parameter set.

[0396] Aspect 97: A method for media session management at a network entity, the method comprising: obtaining one or more PDUs in association with a PDU session between a first device and a second device; selecting a set of communication parameters for the one or more PDUs based on a media type associated with the associated one or more PDUs (such as indicated by a field value, such as a PSI field value); and transmitting the one or more PDUs based on the set of communication parameters.

[0397] Aspect 98: The method according to aspect 97, the method further comprising: obtaining the one or more PDUs from one of the first device or the second device or from a UPF associated with the network entity; and filtering (e.g., grouping) the one or more PDUs into a QoS flow according to a packet filter at least partially based on the PSI field value, wherein the set of communication parameters is selected in association with filtering (e.g., grouping) the one or more PDUs according to the packet filter at least partially based on the PSI field value.

[0398] Aspect 99: The method according to aspect 98 further includes: determining a QoS flow associated with the one or more PDUs based at least in part on the packet filter, wherein the set of communication parameters is selected in connection with determining the QoS flow associated with the one or more PDUs.

[0399] Aspect 100: The method according to aspect 99, wherein the PSI field value and the Internet Protocol parameter set jointly define the QoS flow according to the packet filter.

[0400] Aspect 101: The method according to any one of Aspects 99 to 100, wherein the corresponding PSI field value and the corresponding Internet Protocol parameter set jointly define the corresponding QoS flow according to the packet filter.

[0401] Aspect 102: The method according to any one of aspects 98 to 101, wherein the packet filter is an Internet Protocol packet filter or an Ethernet packet filter.

[0402] Aspect 103: The method according to any one of aspects 97 to 102, wherein the set of communication parameters includes a set of QoS parameters.

[0403] Aspect 104: A method for media session management at a network entity, the method comprising: transmitting information associated with a mapping between each protocol PDU set and a corresponding communication parameter set in a plurality of PDU sets in connection with the establishment of a PDU session between a first device and a second device; obtaining a first PDU set based on the PDU session between the first device and the second device; selecting a first communication parameter set for the associated first PDU set based on the mapping; and transmitting the first PDU set based on the first communication parameter set.

[0404] Aspect 105: The method according to aspect 104, wherein the first PDU set is obtained from one of the first device or the second device or from a UPF associated with the network entity.

[0405] Aspect 106: The method according to any one of aspects 104 to 105, the method further comprising: obtaining a second PDU set based on the PDU session between the first device and the second device; selecting a second set of communication parameters for the second PDU set based on the mapping; and sending the second PDU set based on the second set of communication parameters.

[0406] Aspect 107: The method according to aspect 106, wherein the first PDU set and the second PDU set are associated with the same QoS flow.

[0407] Aspect 108: The method according to any one of Aspects 106 to 107, wherein the first PDU set is associated with a first service type and the second PDU set is associated with a second service type.

[0408] Aspect 109: According to the method of aspect 108, wherein the first service type is associated with an I-frame of video data and the second service type is associated with a P-frame of video data.

[0409] Aspect 110: The method according to any one of Aspects 108 to 109, wherein the first service type is associated with telemetry data and the second service type is associated with audio data.

[0410] Aspect 111: The method according to any one of Aspects 108 to 110, wherein the first service type is associated with audio data and the second service type is associated with audio metadata.

[0411] Aspect 112: The method according to any one of aspects 106 to 111, wherein the first set of communication parameters includes a first set of QoS parameters, and the second set of communication parameters includes a second set of QoS parameters.

[0412] Aspect 113: According to the method of aspect 112, wherein the first QoS parameter set is associated with the first PDU set delay budget, the first PDU set error rate and the first PDU set integrated processing information, and the second QoS parameter set is associated with the second PDU set delay budget, the second PDU set error rate and the second PDU set integrated processing information.

[0413] Aspect 114: According to the method of aspect 113, wherein, associated with the first PDU set and the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are different from the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, respectively, and the first PSI field value is different from the second PSI field value associated with the second PDU set.

[0414] Aspect 115: The method according to any one of Aspects 113 to 114, wherein, associated with the first PDU set and related to the first PSI field value, the first PDU set delay budget, the first PDU set error rate, and the first PDU set integration processing information are respectively equal to the second PDU set delay budget, the second PDU set error rate, and the second PDU set integration processing information, and the first PSI field value is equal to the second PSI field value associated with the second PDU set.

[0415] Aspect 116: A first device for media session management, the first device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first device to perform a method according to any one of aspects 1 to 33.

[0416] Aspect 117: A first device for media session management, the first device comprising at least one component for performing the method according to any one of aspects 1 to 33.

[0417] Aspect 118: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 33.

[0418] Aspect 119: A first device for media session management, the first device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first device to perform a method according to any one of aspects 34 to 40.

[0419] Aspect 120: A first device for media session management, the first device comprising at least one component for performing the method according to any one of aspects 34 to 40.

[0420] Aspect 121: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform a method according to any one of aspects 34 to 40.

[0421] Aspect 122: A first device for media session management, the first device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first device to perform a method according to any one of aspects 41 to 51.

[0422] Aspect 123: A first device for media session management, the first device comprising at least one component for performing the method according to any one of aspects 41 to 51.

[0423] Aspect 124: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform a method according to any one of aspects 41 to 51.

[0424] Aspect 125: A network entity for media session management, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 52 to 96.

[0425] Aspect 126: A network entity for media session management, the network entity comprising at least one component for performing the method according to any one of aspects 52 to 96.

[0426] Aspect 127: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform a method according to any one of aspects 52 to 96.

[0427] Aspect 128: A network entity for media session management, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 97 to 103.

[0428] Aspect 129: A network entity for media session management, the network entity comprising at least one component for performing the method according to any one of aspects 97 to 103.

[0429] Aspect 130: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform the method according to any one of aspects 97 to 103.

[0430] Aspect 131: A network entity for media session management, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 104 to 115.

[0431] Aspect 132: A network entity for media session management, the network entity comprising at least one component for performing the method according to any one of aspects 104 to 115.

[0432] Aspect 133: A non-transitory computer-readable medium storing code for media session management, the code including instructions executable by one or more processors to perform a method according to any one of aspects 104 to 115.

[0433] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.

[0434] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0435] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0436] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, NPU, FPGA, or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

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

[0438] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0439] As used herein, the word "or" 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") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0440] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0441] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0442] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0443] The description herein, illustrated in conjunction with the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: The establishment of a Protocol Data Unit (PDU) session between the first device and the second device is associated with the transmission of information related to the mapping between each protocol PDU set and the corresponding communication parameter set in a plurality of PDU sets; A first PDU set and a second PDU set are obtained based on the PDU session between the first device and the second device, wherein the first PDU set and the second PDU set are associated with the same Quality of Service (QoS) flow. The first PDU set is sent according to the first set of communication parameters mapped to the first PDU set; as well as The second PDU set is sent according to the second set of communication parameters mapped to the second PDU set.

2. The network entity of claim 1, wherein the first PDU set is obtained from one of the first device or the second device or from a user plane function associated with the network entity.

3. The network entity according to claim 1, wherein: The first PDU set is associated with a first media type, and the second PDU set is associated with a second media type that is different from the first media type; and The first set of communication parameters is different from the second set of communication parameters, since the first set of PDUs is associated with the first media type and the second set of PDUs is associated with the second media type.

4. The network entity according to claim 1, wherein: The first PDU set is associated with a first PDU set importance (PSI) field value, and the second PDU set is associated with a second PSI field value that is different from the first PSI field value; and The first set of communication parameters is different from the second set of communication parameters, since the first set of PDUs is associated with the first PSI field value and the second set of PDUs is associated with the second PSI field value.

5. The network entity according to claim 1, wherein the first communication parameter set includes a first quality of service parameter set, and the second communication parameter set includes a second quality of service parameter set.

6. The network entity according to claim 5, wherein: The first set of service quality parameters is associated with the latency budget of the first PDU set, the error rate of the first PDU set, and the integration and handling information of the first PDU set; and The second set of service quality parameters is associated with the second set of PDU delay budget, the second set of PDU error rate, and the second set of PDU integrated handling information.

7. A first device, the first device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the first device: Establish a Protocol Data Unit (PDU) session between the first device and the second device based on the application at the first device; The set of communication parameters for the one or more PDUs is selected based on the media type associated with the application. as well as The one or more PDUs are sent according to the set of communication parameters.

8. The first device of claim 7, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first device to: Obtain the one or more PDUs from the application; and The one or more PDUs are grouped into a Quality of Service stream based at least in part on a grouping filter based on the media type. The set of communication parameters is selected based on the packet filter, which is at least partially based on the media type.

9. The first device of claim 8, wherein the media type and Internet Protocol parameter set jointly define the Quality of Service flow according to the packet filter.

10. The first device of claim 8, wherein the packet filter is an Internet Protocol packet filter or an Ethernet packet filter.

11. The first device according to claim 7, wherein the set of communication parameters includes a set of quality of service parameters.

12. The first device of claim 7, wherein the media type associated with the one or more PDUs is at least partially based on field values ​​associated with the one or more PDUs.

13. The first device according to claim 12, wherein the field value is a PDU set importance (PSI) field value.

14. A first device, the first device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the first device: Establish a Protocol Data Unit (PDU) session between the first device and the second device based on the application at the first device; The first communication associated with the establishment of the PDU session conveys information related to the interpretation of the PDU Set Importance (PSI) field in the PDU header; as well as The second communication conveys one or more PDUs from one or more PDU sets associated with the application, based on the interpretation of the PSI field.

15. The first device of claim 14, wherein, in order to convey the first communication of information associated with the interpretation of the PSI field, the one or more processors are individually or jointly capable of executing the code to cause the first device to: Sending a message to or receiving from the second device that includes the information associated with the interpretation of the PSI field.

16. The first device of claim 14, wherein, in order to convey the first communication of information associated with the interpretation of the PSI field, the one or more processors are individually or jointly capable of executing the code to cause the first device to: Sending a first message to the network entity including a request for the interpretation of the PSI field; and A second message is received from the network entity, the second message including acceptance or modification of the interpretation of the PSI field requested by the first device. The second communication of one or more PDUs is carried out based on the network entity's acceptance or modification of the interpretation of the PSI field.

17. The first device of claim 14, wherein, in order to convey the first communication of information associated with the interpretation of the PSI field, the one or more processors are individually or jointly capable of executing the code to cause the first device to: Receive a message from the network entity that includes the information associated with the interpretation of the PSI field.

18. The first device of claim 14, wherein the interpretation of the PSI field indicates a mapping that associates each of a plurality of PSI field values ​​with a corresponding media type.

19. The first device of claim 14, wherein the interpretation of the PSI field indicates the following mapping: Associate two or more PSI field values ​​from a set of PSI field values ​​with dependencies; and Each of the plurality of PSI field values ​​is associated with a corresponding set of communication parameters.

20. The first device of claim 14, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first device to: In connection with the establishment of the PDU session, second information associated with a mapping between each of the plurality of PDU sets and a corresponding set of quality of service parameters is received, and Each of the multiple PDU sets is associated with the same Quality of Service (QoS) flow. According to the mapping, the first PDU set of the same quality of service flow is associated with a first quality of service parameter set, and the second PDU set of the same quality of service flow is associated with a second quality of service parameter set that is different from the first quality of service parameter set.

Images