Policy control and mapping for data channels in internet protocol multimedia subsystem networks

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may send a session description protocol (SDP) invitation to a network, and may include an indication of an application identifier (ID) and quality of service (QoS) cue information (e.g., a threshold QoS for an application) in the SDP invitation. The network may utilize the application ID to determine charging (e.g., billing) information for the user. Additionally or alternatively, the network may account for a threshold QoS in determining (e.g., granting) QoS resources on the data channel for the UE to initiate communications on the data channel.

Description

Technical Field

[0001] The following relates to wireless communications, including policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to 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, advanced LTE (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 use 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 spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network. For example, the technology described herein can support a user equipment (UE) sending a session description protocol (SDP) invitation to a network. The SDP invitation (e.g., SDP invitation) can include an indication of an application identifier (ID) and service quality (QoS) hint information (e.g., a threshold QoS for the application). The network can use the application ID to determine charging (e.g., billing) information for the user. Additionally or alternatively, the network can consider the threshold QoS when determining (e.g., granting) QoS resources on a data channel for the UE to initiate communication on the data channel.

[0004] A method for wireless communication at a user equipment (UE) is described. The method may include sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; receiving an SDP response for the application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and sending a response confirmation based on receiving the SDP response.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send an SDP invitation for an application associated with a data channel, the SDP invitation including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; receive an SDP response for the application associated with the data channel based on sending the SDP invitation, the SDP invitation authorizing quality of service resources that meet the threshold quality of service; and send a response confirmation based on receiving the SDP response.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; means for receiving an SDP response for the application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and means for sending a response confirmation based on receiving the SDP response.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; receiving an SDP response for the application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and sending a response confirmation based on receiving the SDP response.

[0008] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for initiating communications by an application on a data channel in an Internet Protocol Multimedia Subsystem session based on an outgoing SDP response and in accordance with a threshold quality of service.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier includes a tag indicating a name of the data channel.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier comprises a media-level attribute of a data channel subprotocol attribute associated with the data channel.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for a public land mobile network identifier, a data channel application provider, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the threshold quality of service may include operations, features, components, or instructions for a threshold packet loss for an application, a threshold latency for an application, or both.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining an indication of an application identifier related to installing an application at a UE; and including the indication of the application identifier in an SDP offer.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a data channel application packet associated with an application, the data channel application packet including an application identifier; and including an indication of the application identifier in an SDP offer based on the data channel application packet.

[0016] A method for wireless communication at a network device is described. The method may include: obtaining an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; outputting an SDP response for the application associated with the data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and obtaining a response confirmation based on receiving the SDP response.

[0017] An apparatus for wireless communication at a network device is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: obtain an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; output an SDP response for the application associated with the data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and obtain a response confirmation based on receiving the SDP response.

[0018] Another apparatus for wireless communication at a network device is described. The apparatus may include: means for obtaining, from a first UE, an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; means for outputting, based on receiving the SDP offer, an SDP response for the application associated with the data channel, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and means for obtaining a response confirmation based on receiving the SDP response.

[0019] A non-transitory computer-readable medium storing code for wireless communication at a network device is described. The code may include instructions executable by a processor to: obtain an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; output an SDP response for the application associated with the data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; and obtain a response confirmation based on receiving the SDP response.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for authorizing quality of service resources that meet a threshold quality of service, wherein the outgoing SDP response may be based on the authorization.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: forwarding the SDP offer to the second UE; and obtaining an SDP response from the second UE.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the SDP response may include operations, features, components, or instructions for forwarding the SDP response obtained from the second UE to the first UE.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for initiating communications by an application on a data channel in an Internet Protocol Multimedia Subsystem session based on an outgoing SDP response and in accordance with a threshold quality of service.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating billing information associated with an application for an Internet Protocol Multimedia Subsystem session based on an application identifier.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing billing information to a service provider associated with the first UE.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier includes a tag indicating a name of the data channel.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the application identifier comprises a media-level attribute of a data channel subprotocol attribute associated with the data channel.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for a public land mobile network identifier, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for associating an application identifier with a data channel application package corresponding to the application, wherein receiving an SDP offer including an application identifier can be based on associating the application identifier with the data channel application package.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the threshold quality of service may include operations, features, components, or instructions for a threshold packet loss for an application, a threshold latency for an application, or both. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An example of a wireless communication system supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network in accordance with one or more aspects of the present disclosure is illustrated.

[0033] Figure 2 An example of a wireless communication system supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 3 An example of a process flow supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 4 and Figure 5 A block diagram of an apparatus supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0036] Figure 6 A block diagram of a communications manager supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0037] Figure 7 A diagram of a system including a device supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0038] Figure 8 and Fig. 9 A block diagram of an apparatus supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0039] Fig.10 A block diagram of a communications manager supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig.11 A diagram of a system including a device supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network is shown in accordance with one or more aspects of the present disclosure.

[0041] Figures 12 to 17 A flow chart illustrating a method of supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0042] In some wireless communication systems, user equipment (UE) can use one or more applications on a data channel. For example, a UE can use one or more applications (e.g., via a network) to communicate wirelessly with another UE. However, in some examples, the technology for charging users for data channel usage may not be sophisticated enough to reach application-specific levels. For example, some billing for Internet Protocol Management Sessions (IMS) sessions (e.g., initiated via Session Description Protocol (SDP) signaling) may be global only for data channel usage, and has nothing to do with individual application usage. However, such global billing procedures may not take into account the complexity, quality of service requirements, complexity levels, priorities, or other costs associated with individual applications. Additionally, some applications may have a higher tolerance for variable quality of service than other applications. Therefore, some data channels may or may not support some applications (e.g., if the data channel cannot support quality of service requirements for specific applications).

[0043] The techniques described herein may support specific service quality levels for different applications, and may further support application-specific fine-grained charging mechanisms. The UE may send an SDP offer to the network, and may include an indication of an application identifier (ID) and quality of service (QoS) hint information (e.g., a threshold QoS for the application) in the SDP offer. The network may utilize the application ID to determine charging (e.g., billing) information for the user. Additionally or alternatively, the network may consider the threshold QoS when determining (e.g., granting) QoS resources on a data channel for the UE to initiate communication on the data channel.

[0044] Aspects of the present disclosure are first described in the context of wireless communication systems. Aspects of the present disclosure are further illustrated and described by and with reference to wireless communication systems and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to device diagrams, system diagrams, and flow diagrams related to policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network.

[0045] Figure 1An example of a wireless communication system 100 that supports policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 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 according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0046] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0047] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0048] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a 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, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a 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 a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

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

[0050] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0051] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (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) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 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 the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

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

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

[0055] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access, wireless self-backhaul capabilities for UE 115). 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 that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0056] For example, the IAB node 104 may be referred to as a parent node supporting child IAB node communications and as a child IAB node associated with an IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmission to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmission. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0057] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0059] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0060] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate," when referring to the network entity 105, may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0061] In some examples, such as in a carrier aggregation configuration, a carrier may also 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 located based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

[0063] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0064] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that adopts MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the 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), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device can be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0065] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0066] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain 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 certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

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

[0068] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0069] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0070] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0071] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, 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 prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency are used interchangeably herein.

[0072] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (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 a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in the group may be outside the coverage area 110 of the network entity 105, or otherwise not able or configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

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

[0074] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0075] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the length of the wavelength ranges from about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0076] The wireless communication system 100 may also operate in a super high frequency (SHF) region (also known as a centimeter band) using a frequency band of 3 GHz to 30 GHz or in an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) of the spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0077] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

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

[0079] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0080] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate through logical channels. The MAC layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, transport channels may be mapped to physical channels.

[0081] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0082] The UE 115 may send an SDP offer to the network and may include in the SDP offer an indication of the application ID and QoS hint information (e.g., a threshold QoS for the application). The network may utilize the application ID to determine charging (e.g., billing) information for the user. Additionally or alternatively, the network may consider the threshold QoS when determining (e.g., granting) QoS resources on the data channel for the UE to initiate communication on the data channel.

[0083] Figure 2 An example of a wireless communication system 200 that supports policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include a network entity 105-a and one or more UEs 115 (e.g., UE 115-a), a core network 130-a, a data network 205, which may be reference Figure 1 The wireless communication system 200 may also include an SDP device 116 , which may be an example of another UE 115 , a server, or other device capable of communicating with the UE 115 - a via an SDP session 215 .

[0084] The wireless communication system 200 may support communication between a UE 115-a and another wireless device, such as an SDP device 116. The data network 205 is via a network entity 105-a and a core network 130-a. For example, the UE 115-a may be connected to the network entity 105-a via a bidirectional communication link 210, the network entity 105-a may communicate with the core network 130-a, and the core network 130-a may provide one or more gateways to the data network 205. The data network 205 may include one or more packet-switched data networks (PDNs), such as an internal or restricted data network, the Internet or another public data network, or a combination thereof.

[0085] In some examples, core network 130 may include one or more IMS entities and may support IMS sessions, such as to implement SDP session 215, which allows UE 115-a to communicate with other devices (such as SDP device 116) via data network 205. SDP session 215 may include negotiation procedures, such as sending an SDP offer (e.g., from UE 115-a to SDP device 116) or receiving an SDP response (e.g., from SDP device 116 to UE 115-a), which may be facilitated by the IMS entities supporting the IMS session.

[0086] In one example, the SDP device 116 may be a second UE connected to the data network 205 via different network entities and core networks. Thus, the UE 115-a may communicate with the SDP device 116 by negotiating an SDP session 215 with the SDP device 116 via the core network 130-a (e.g., via a connection with the network entity 105-a). In this example, the UE 115-a may communicate with the SDP device 116 via the SDP session 215, which may be routed through the network entity 105-a serving the UE 115-a, the core network 130-a, the data network 205, the core network of the SDP device 116, and the network entity serving the SDP device 116.

[0087] In another example, the SDP device 116 and the data network 205 may include the Internet. In this example, the SDP session 215 may be routed directly to the SDP device 116 through the network entity 105-a serving the UE 115-a, the core network 130-a, and the data network 205.

[0088] The wireless communication system 200 may support a multimedia IMS session, such as an SDP session 215, which may be used to implement a video call between a UE 115-a and an SDP device 116. An IMS data channel and associated sessions may support multiple media types between two endpoints (e.g., a UE 115-a and an SDP device 116). The media delivered on the data channel may be standardized or customized for a specific data channel application. Multiple data channels may be established simultaneously for a data channel IMS multimedia telephony service (MTSI), which may support service delivery for different data channel applications. However, the IMS network may not be able to access information about the QoS requirements of different media types delivered via the data channel. Without access to such information, the network may not be able to accurately or efficiently allocate relevant QoS resources (e.g., relevant bearer resources in an IP Connectivity Access Network (IP-CAN)) on the data channel. In addition, without a technique for identifying specific application usage on a data channel, the network may not be able to identify and provide granular, application-specific charging (e.g., billing) information to a user or provider.

[0089] When an application of UE 115-a initiates an SDP session 215 to communicate with an application of SDP device 116, one or more data channel SDP media descriptions may be included in the SDP offer (e.g., along with other SDP media descriptions such as voice, video, etc.). Multiple data channels may be mapped to a single data channel SDP media description, each data channel having a corresponding SDP attribute (e.g., "a=dcmap") and a stream ID.

[0090] During the SDP negotiation procedure, an IMS network entity (e.g., a proxy call session control function (P-CSCF), a serving call session control function (S-CSCF), etc.) may trigger reporting of charging data record (CDR) information for an SDP session to a charging system. The reported CDR may carry a list of SDP media components included in an SDP offer and / or an SDP response. Consumers of data channel applications, IMS network providers, and data channel applications may have access to records for each data channel application (e.g., data channel application ID, application start time, application close time, etc.). However, if such information is not included in the SDP media description for a data channel, such information cannot be used for more sophisticated billing procedures and improved quality of service. This article describes techniques for providing such information.

[0091] A data channel may be allocated to UE 115-a (e.g., via an indication of a data channel flow ID). A data channel flow ID may be allocated for other data channel applications after a previous data channel is released. An IMS network entity may not have access to a mapping relationship between data channel applications and data access flow IDs, and may not have access to usage information for data channel applications.

[0092] As described herein, in order to efficiently and effectively collect billing information for data channel services, and to support data channel application usage statistics, UE 115-a may utilize the SDP media description of the data channel to identify the service application of each data channel with a data channel application ID. UE 115 (e.g., UE 115-a) may send an SDP invitation (e.g., message 215-a) to the network, and may include an indication of the application ID, QoS hint information (e.g., a threshold QoS for the application), or both in the SDP invitation.

[0093] QoS hint information may be included in an SDP attribute (e.g., a=3gpp-qos-hint). The QoS hint information may be referred to as a threshold QoS for a specific application. The threshold QoS may indicate a threshold packet loss or latency that a data channel media for a specific data channel application can support. In such an example, a data channel MTSI supporting a UE (e.g., UE 115-a) may include QoS hint information in an SDP invitation message. In such an example, a network (e.g., at a policy control level) may consider the QoS hint information for the affected media (e.g., for the application indicated in the SDP invitation). In some examples, if QoS hint information is not provided in the SDP, the network may default to a fallback QoS level, or may derive best effort transport level QoS information based on one or more conditions or parameters (e.g., based on UE subscription information, network policies, or a combination thereof, etc.).

[0094] For example, UE 115-a may request (e.g., in QoS hint information) an end-to-end 2% loss, but the local link at UE 115-a may support a threshold of 1% loss. In such an example, UE 115-a may include QoS hint information indicating loss=2 in the SDP request. SDP device 116 may be able to accept a threshold of 2% loss end-to-end, and the local link at SDP device 116 may support a threshold of 1% loss. In such an example, SDP device 116 may indicate a QoS hint of loss=2 in the SDP response. This may result in a threshold packet loss of 2% (e.g., 1%+1%=2%). Similarly, if UE 115-a requests a threshold of 0.2% loss with a local link that supports a threshold of 0.1%, and SDP device 116 may accept a threshold of 0.2% loss with a local link that supports a threshold of 0.1%, the resulting threshold loss may be 0.2%. If UE 115 - a requests a threshold of 0.02% loss with a local link that supports a threshold of 0.01%, and SDP device 116 may accept a threshold of 0.02% loss with a local link that supports a threshold of 0.01%, the resulting threshold loss may be 0.02%.

[0095] In some examples, UE 115-a and the network may negotiate more than one data channel with different QoS requirements in the same media description of the SDP offer. In such examples, the threshold QoS values ​​(e.g., requirements) for all indicated data channel flows may be aggregated and exported into a single line of the SDP attribute (e.g., if more than one media flow is part of the same media description, then the a=3gpp-qos-hint attribute line applies jointly to the aggregation of all packets). The QoS hint information included in such an attribute may be equally applicable to all packets in the requested one or more data channels.

[0096] In some examples, UE 115-a, which is a data channel MTSI UE, may request to establish a data channel with a specific threshold QoS. In such examples, a separate media description with QoS hint information (e.g., a=3gpp-qos-hint attribute) may be included in the SDP invitation. The established data channel may be associated with different configurations (e.g., User Datagram Protocol (UDP) configuration, Datagram Transport Layer Security (DTLS) configuration, or Stream Control Transmission Protocol (SCTP) configuration, etc.). Different source UDP ports, target UDP ports, or both may be used for the transport layer for the indicated data channel. In some examples, if UE 115-a is assigned an IP prefix, different IP addresses (e.g., IP version 6 (IPv6) addresses) may be used. In some examples, IP tuple information of the data channel transport layer may be provided by one or more IMS entities (e.g., P-CSCF) to a policy control function (PCF) in a service data flow filter. Data channels may be mapped to various media types.

[0097] In some examples, UE 115-a may include an indication of the application ID in the SDP offer. In some examples, the application ID may be included in the media description of the SDP. In such examples, the PCF may verify the QoS hint information provided by the UE and may determine an appropriate QoS configuration for the application on the data channel based on the QoS hint information, the application ID, the operator policy, or any combination thereof.

[0098] The application ID may be defined or provided by a third party entity (e.g., an application function (AF) or a high-level operating system (HLOS)). In some examples, UE 115-a may obtain the application ID after downloading or installing the application. The IMS network provider may assign an application ID to each data channel application (e.g., which is uploaded to a data channel application repository). The assigned data channel application ID may be configured in the data channel application package, or may be signaled to the UE when the data channel application is downloaded or installed to UE 115-a in a bootstrap data channel. When UE 115-a initiates a data channel for the application (e.g., initiates communication on the data channel using the application), the data channel application may be included in the SDP media description of the SDP invitation.

[0099] A network provider may define each data channel application ID, and each data channel application ID may include one or more elements or parameter values. For example, an application ID may include a public land mobile network (PLMN) ID (e.g., including a mobile network code (MNC) and a mobile country code (MCC)). The application ID may include a data channel application provider (e.g., a user or a network provider). The application ID may include a data channel application number that may be assigned by a network provider. The application ID may include an application name, which may include human-readable information).

[0100] UE 115-a may include an indication of an application ID in an SDP offer (e.g., message 215-a). The indication of the application ID may include a tag attribute for the data channel application ID. For example, the tag parameter may indicate the name of the data channel and may represent a tag used to distinguish a real-time communication (RTC) data channel object from other RTC data channel objects. For example, UE 115-a may include an indication of application #1 (e.g., a=dcmap:38754max-time=150; tag="DC application #1"), an indication of application #2 (e.g., a=dcmap:7216max-retr=5; tag="DC application #2"), or both in the SDP offer. Such a tag may be an existing tag (e.g., used to distinguish channel objects) that may be reused or re-used for an indication of an application ID. In some examples, UE 115-a may indicate the application ID via an attribute dedicated to the data channel application ID in the media-level attributes of the data channel map (DCMAP). In such an example, UE 115-a may include an indication of an application ID for application #1 (e.g., a-dcmap:38754max-time=150; dcapp-id="DC application #1") in the SDP offer. In some examples, UE 115-a may indicate the application ID in an attribute dedicated to the application ID in the media level attributes of the data channel subprotocol attributes (DCSA). In such an example, UE 115-a may include an indication of application #1 (e.g., a=dcmap:38754max-time=150; a=dcsa:38754; dcapp-idd="DC application #1").

[0101] The network may utilize the application ID to determine charging (eg, billing) information for the user.

[0102] For example, one or more network entities or IMS entities (e.g., P-CSCF, S-CSCF, multimedia resource function (MRF), data channel server (DChS), or IMS application server (AS), etc.) may trigger a CDR report to the charging system. A network entity (e.g., network entity 105-a) may indicate the application ID by including an SDP media description (e.g., in a CDR report) containing a data channel application ID. In some examples, the DChS may report the CDR to the charging system. For example, the CDR information may be triggered by events such as guiding data channel establishment, update, and release, download of a data channel application, and data channel establishment to the DChS triggered by a UE application. Any such trigger may result in a CDR including an indication of the application ID. The charging system may then aggregate the CDRs collected from the IMS entities and the 5G core (5GC) network function (NF). The IMS entities may derive charging information for various data channel services based on MNO policies or at different levels of granularity (e.g., per IMS session level granularity, per SDP media description level granularity, or per data channel application level granularity, etc.). The billing information is then transmitted by the billing system to the user for billing purposes.

[0103] Additionally or alternatively, the network may consider the threshold QoS when determining (e.g., authorizing) the QoS. For example, the network may allocate channel resources according to the QoS indicated in the SDP invitation, as shown in FIG. Figure 3 Described in more detail.

[0104] Figure 3 An example of a process flow 300 for supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network in accordance with one or more aspects of the present disclosure is illustrated. The process flow 300 may include one or more UEs 115 (e.g., UEs 115-b and UEs 115-c), one or more network entities 105, and one or more IMS entities (e.g., PCF 106, P-CSCF 107, S CSCF 108, and terminating IMS 109). In some examples, the IMS entity may be an example of a network entity 105. The UE 115 and the network entity 105 may be reference Figure 1 to Figure 2 An example of a corresponding device described. UE 115-c may be Figure 2The PCF 106 may be an example of an SDP device 116 of the IMS. The PCF 106 may help operators create and deploy policies. The PCF 106 may use policy subscription information stored in a User Data Repository (UDR) to provide policy rules to network functions (Session Management Function (SMF) or Access Mobility Management Function (AMF)). The P-CSCF 106 may act as a proxy server for the UE, and Session Initiation Protocol (SIP) signaling services may be delivered through the P-CSCF 107. The S-CSCF 107 may act as a master node in the IMS and may be responsible for session control. A subscriber may be assigned an S-CSCF for the duration of the IMS registration to facilitate routing of SIP messages as part of the service establishment procedure.

[0105] At 305, UE 115-b may send an SDP offer for an application associated with a data channel. The SDP offer may include an application ID associated with the application and one or more indications of a threshold QoS (e.g., QoS hint information) associated with the application. The application ID may be a tag indicating the name of a data channel or application. The application ID may be a media-level attribute of a data channel mapping for a data channel. The application ID may be a media-level attribute of a data channel subprotocol attribute for a data channel. In some examples, the application ID may include one or more parameter values, such as a PLMN ID, a data channel application provider, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof. The threshold QoS may indicate a threshold packet loss for an application or data channel, or a threshold latency for an application or data channel, or any combination thereof.

[0106] UE 115-b may obtain an indication of an application ID associated with installing or downloading an application at UE 115-b, and may then include the obtained application ID in an SDP offer. In some examples, UE 115-a may receive a data channel application package for an application, and the data channel application package may include the application ID (e.g., which UE 115-b may include in the SDP offer). For example, a data channel application downloaded at UE 115-b may trigger establishment of a data channel via a SIP invite request (e.g., an SDP invite) containing an SDP media description for one or more data channels. Each data channel attribute may be identified with a data channel application ID in the SDP. If the data channel application has special QoS requirements (e.g., threshold QoS), UE 115-a may include QoS hint information (e.g., a line with a=3gpp-qos-hint) in the SDP media description.

[0107] One or more network entities 105 may obtain an SDP offer from UE 115-b and may output an SDP response for the application and data channel indicated in the SDP offer. One or more network entities may obtain a response confirmation from UE 115-b based on having output the SDP response. For example, at 310, P-CSCF 107 may forward the SDP offer to S-CSCF 108. At 315, S-CSCF 108 may forward the SDP offer to terminating IMS 109. In some examples, at 320, terminating IMS 109 may forward the SDP offer to another wireless device (e.g., UE 115-c). UE 115-c may respond to the SDP offer by generating and sending an SDP response. The SDP response may include an accepted media stream description. In some examples, QoS hint information may be accepted in the SDP. CDRs may be generated by relevant terminating and originating IMS entities (eg, terminating IMS 109, S-CSCF 108, P-CSCF 107, PCF 106, IMS-AS, DChS, MRFC, etc.) and reported to the charging system. The CDR may include the DC application ID in the SDP media description.

[0108] At 325, the UE 115-c may transmit the SDP response to the terminating IMS 109. At 330, the terminating IMS 109 may forward the SDP response to the S-CSCF. At 335, the S-CSCF 108 may forward the SDP response to the P-CSCF. At 340, the P-CSCF 107 may instruct the PCF 106 to authorize QoS resources for the data channel based on the SDP media description. The PCF 106 may derive QoS parameters based on QoS hint information in the media stream description of the SDP request, the SDP response, or both. The PCF 106 may generate a service data flow filter based on an IP tuple (e.g., an IP 5-tuple) provided by the P-CSCF 107. The created PCC rules may be transmitted to the PCF 106 and may trigger a session modification procedure to establish a QoS flow for the transmission of the data channel service. In some examples (e.g., where the data channel application data ID is included in the media description of the SDP), PCF 106 may validate the QoS hints provided by UE 115-a and may determine a proposed QoS configuration based on network operator policy.

[0109] At 345, UE 115-b may receive an SDP response for an application associated with the data channel in response to the SDP request sent at 305. P-CSCF 107 may forward the invitation SDP response to UE 115-b. The SDP response may authorize QoS resources on the data channel that meet the threshold QoS. UE 115-a may then send a response confirmation based on having received the SDP response. UE 115-b may initiate communication by the application (e.g., with UE 115-c or with another wireless device or network entity 105, etc.) in an IMS session (such as an SDP session) (e.g., based on the threshold QoS). P-CSCF 107 may forward the SDP response to UE 115-b, and UE 115-b may confirm receipt of the SDP response and transmit the response confirmation to P-CSCF 107.

[0110] As described herein, the DChS may generate CDRs triggered by one or more events. Such events may include directing data channel establishment, update, and / or release, downloading or installing a data channel application, data channel establishment triggered by a UE application via the DChS, and the like. IMS network entities (e.g., S-CSCF 106, P-CSCF 107, IMS-AS, MRFC, IBCF, etc.) may support generation of CDRs in SDP negotiation, including a data channel application ID for each data channel flow. PCF 106 may support functionality including deriving QoS parameters based on receiving QoS hint attributes from P-CSCF 107 and validating data channel QoS requirements via the data channel application ID.

[0111] Figure 4 A block diagram 400 of a device 405 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0112] Receiver 410 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network, data channels, information channels). The information may be communicated to other components of device 405. Receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0113] Transmitter 415 may provide means for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels (e.g., control channels related to policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0114] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0115] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0116] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0117] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or integrate with receiver 410, transmitter 415, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0118] According to examples as disclosed herein, the communication manager 420 may support wireless communications at the UE. For example, the communication manager 420 may be configured to or otherwise support a component for sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The communication manager 420 may be configured to or otherwise support a component for receiving an SDP response for the application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The communication manager 420 may be configured to or otherwise support a component for sending a response confirmation based on receiving the SDP response.

[0119] By including or configuring a communication manager 420 according to examples as described herein, the device 405 (e.g., a processor controlling the receiver 410, the transmitter 415, the communication manager 420, or a combination thereof or otherwise coupled thereto) can support techniques for IMS sessions, resulting in more reliable service, improved communication quality, more accurate and helpful billing information, and an improved user experience.

[0120] Figure 5 A block diagram 500 of a device 505 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] Receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network, data channels, information channels). The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0122] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels related to policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0123] Device 505 or its various components may be examples of components for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, communication manager 520 may include SDP invitation manager 525, SDP response manager 530, response confirmation manager 535, or any combination thereof. Communication manager 520 may be an example of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or integrate with receiver 510, transmitter 515, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0124] According to examples as disclosed herein, the communication manager 520 may support wireless communications at the UE. The SDP offer manager 525 may be configured to or otherwise support components for sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The SDP response manager 530 may be configured to or otherwise support components for receiving an SDP response for an application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The response confirmation manager 535 may be configured to or otherwise support components for sending a response confirmation based on receiving the SDP response.

[0125] Figure 6A block diagram 600 of a communication manager 620 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The communication manager 620 may be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, the communication manager 620 may include an SDP invitation manager 625, an SDP response manager 630, a response confirmation manager 635, an IMS session manager 640, an application identifier manager 645, a quality of service manager 650, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0126] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. The SDP offer manager 625 may be configured to or otherwise support components for sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The SDP response manager 630 may be configured to or otherwise support components for receiving an SDP response for an application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The response confirmation manager 635 may be configured to or otherwise support components for sending a response confirmation based on receiving the SDP response.

[0127] In some examples, IMS session manager 640 may be configured or otherwise support components for initiating communications by an application on a data channel in an Internet Protocol Multimedia Subsystem session based on an outgoing SDP response and according to a threshold quality of service.

[0128] In some examples, the application identifier includes a tag indicating the name of the data channel.

[0129] In some examples, the application identifier includes a media-level attribute of a data channel map associated with the data channel.

[0130] In some examples, the application identifier includes a media level attribute of a data channel subprotocol attribute associated with the data channel.

[0131] In some examples, the application identifier manager 645 may be configured or otherwise support components for a public land mobile network identifier, a data channel application provider, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0132] In some examples, to support threshold quality of service, quality of service manager 650 may be configured or otherwise support components for threshold packet loss for an application, threshold latency for an application, or both.

[0133] In some examples, application identifier manager 645 may be configured or otherwise support components for obtaining an indication of an application identifier related to installing an application at the UE. In some examples, application identifier manager 645 may be configured or otherwise support components for including the application identifier in the SDP offer.

[0134] In some examples, application identifier manager 645 may be configured or otherwise support components for receiving a data channel application packet associated with an application, the data channel application packet including an application identifier. In some examples, application identifier manager 645 may be configured or otherwise support components for including the application identifier in an SDP offer based on the data channel application packet.

[0135] Figure 7 A diagram of a system 700 including a device 705 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein, or include components thereof. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

[0136] I / O controller 710 can manage input and output signals for device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor, such as processor 740. In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.

[0137] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. As described herein, the transceiver 715 may communicate bidirectionally via one or more antennas 725, wired or wireless links. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. The transceiver 715 or the transceiver 715 and the one or more antennas 725 may be examples of transmitters 415, transmitters 515, receivers 410, receivers 510, or any combination thereof or components thereof as described herein.

[0138] The memory 730 may include random access memory (RAM) and read-only memory (ROM). The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 735 may not be directly executable by the processor 740, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 730 may contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0139] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to enable the device 705 to perform various functions (e.g., functions or tasks supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.

[0140] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for sending an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The communication manager 720 may be configured to or otherwise support a component for receiving an SDP response for an application associated with the data channel based on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The communication manager 720 may be configured to or otherwise support a component for sending a response confirmation based on receiving the SDP response.

[0141] By including or configuring a communications manager 720 according to examples as described herein, the device 705 can support techniques for IMS sessions resulting in more reliable service, improved communication quality, more accurate and helpful billing information, and an improved user experience.

[0142] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions that are executable by the processor 740 to cause the device 705 to perform various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.

[0143] Figure 8 A block diagram 800 of a device 805 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be communicated to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0145] The transmitter 815 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 805. For example, the transmitter 815 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, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0146] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0147] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0148] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0149] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0150] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network device. For example, the communication manager 820 may be configured to or otherwise support a component for obtaining an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The communication manager 820 may be configured to or otherwise support a component for outputting an SDP response for an application associated with the data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The communication manager 820 may be configured to or otherwise support a component for obtaining a response confirmation based on receiving the SDP response.

[0151] By including or configuring a communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof or otherwise coupled thereto) can support techniques for IMS sessions, resulting in more reliable service, improved communication quality, more accurate and helpful billing information, and an improved user experience.

[0152] Fig. 9 A block diagram 900 of a device 905 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0153] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be communicated to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0154] The transmitter 915 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 905. For example, the transmitter 915 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, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0155] Device 905 or its various components may be examples of components for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, communication manager 920 may include SDP invitation manager 925, SDP response manager 930, response confirmation manager 935, or any combination thereof. Communication manager 920 may be an example of various aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 910, transmitter 915, or both. For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate with receiver 910, transmitter 915, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0156] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network device. The SDP offer manager 925 may be configured to or otherwise support components for obtaining an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The SDP response manager 930 may be configured to or otherwise support components for outputting an SDP response for an application associated with a data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The response confirmation manager 935 may be configured to or otherwise support components for obtaining a response confirmation based on receiving the SDP response.

[0157] Fig.10 A block diagram 1000 of a communication manager 1020 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein. For example, the communication manager 1020 may include an SDP offer manager 1025, an SDP response manager 1030, a response confirmation manager 1035, a quality of service manager 1040, an IMS session manager 1045, an application identifier manager 1050, a change information manager 1055, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0158] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network device. The SDP offer manager 1025 may be configured to or otherwise support components for obtaining, from a first UE, an SDP offer for an application associated with a data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The SDP response manager 1030 may be configured to or otherwise support components for outputting an SDP response for an application associated with a data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The response confirmation manager 1035 may be configured to or otherwise support components for obtaining a response confirmation based on receiving the SDP response.

[0159] In some examples, quality of service manager 1040 may be configured or otherwise support components for authorizing quality of service resources that meet a threshold quality of service, where the outgoing SDP response is based on the authorization.

[0160] In some examples, SDP offer manager 1025 can be configured or otherwise support components for forwarding the SDP offer to the second UE. In some examples, SDP response manager 1030 can be configured or otherwise support components for obtaining an SDP response from the second UE.

[0161] In some examples, to support outgoing SDP responses, SDP response manager 1030 may be configured or otherwise support components for forwarding an SDP response obtained from the second UE to the first UE.

[0162] In some examples, IMS session manager 1045 may be configured or otherwise support components for initiating communications by an application on a data channel in an Internet Protocol Multimedia Subsystem session based on an outgoing SDP response and according to a threshold quality of service.

[0163] In some examples, change information manager 1055 may be configured or otherwise support components for generating billing information associated with an application for an Internet Protocol Multimedia Subsystem session based on an application identifier.

[0164] In some examples, change information manager 1055 may be configured or otherwise support components for providing billing information to a service provider associated with the first UE.

[0165] In some examples, the application identifier includes a tag indicating the name of the data channel.

[0166] In some examples, the application identifier includes a media-level attribute of a data channel map associated with the data channel.

[0167] In some examples, the application identifier includes a media level attribute of a data channel subprotocol attribute associated with the data channel.

[0168] In some examples, application identifier manager 1050 may be configured or otherwise support components for a public land mobile network identifier, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0169] In some examples, application identifier manager 1050 may be configured or otherwise support components for associating an application identifier with a data channel application package corresponding to the application, wherein receiving an SDP offer including the application identifier is based on associating the application identifier with the data channel application package.

[0170] In some examples, to support threshold quality of service, quality of service manager 1040 may be configured or otherwise support components for threshold packet loss for an application, threshold latency for an application, or both.

[0171] Fig.11 A diagram of a system 1100 including a device 1105 supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0172] As described herein, the transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both. For example, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. The transceiver 1110 or the transceiver 1110 and one or more antennas 1115 or a wired interface (where applicable) may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or components thereof as described herein. In some examples, the transceiver 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, fronthaul communication link 168).

[0173] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1130 may not be directly executable by the processor 1135, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 1125 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0174] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can 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 host functionality for performing functions of device 1105 (e.g., by executing code 1130).

[0175] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of the different components or divided between the different components).

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

[0177] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network device. For example, the communication manager 1120 may be configured to or otherwise support a component for obtaining an SDP offer for an application associated with a data channel from a first UE, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The communication manager 1120 may be configured to or otherwise support a component for outputting an SDP response for an application associated with the data channel based on receiving the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service. The communication manager 1120 may be configured to or otherwise support a component for obtaining a response confirmation based on receiving the SDP response.

[0178] By including or configuring a communications manager 1120 according to examples as described herein, the device 1105 can support techniques for IMS sessions resulting in more reliable service, improved communication quality, more accurate and helpful billing information, and an improved user experience.

[0179] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0180] Fig.12 A flow chart illustrating a method 1200 for supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0181] At 1205, the method may include sending an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 6 The described SDP invitation manager 625 is executed.

[0182] At 1210, the method may include receiving an SDP response for an application associated with the data channel based on sending an SDP offer, the SDP offer authorizing quality of service resources that meet a threshold quality of service. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figure 6 The described SDP response manager 630 is performed.

[0183] At 1215, the method may include sending a response confirmation based on receiving the SDP response. The operations of 1215 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference Figure 6 The described response confirmation manager 635 is executed.

[0184] Fig.13 A flow chart illustrating a method 1300 for supporting policy control and mapping for data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1305, the method may include sending an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 6 The described SDP invitation manager 625 is executed.

[0186] At 1310, the method may include receiving an SDP response for an application associated with the data channel based on sending an SDP offer, the SDP offer authorizing quality of service resources that meet a threshold quality of service. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 6 The described SDP response manager 630 is executed.

[0187] At 1315, the method may include sending a response confirmation based on receiving the SDP response. The operations of 1315 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference Figure 6 The described response confirmation manager 635 is executed.

[0188] At 1320, the method may include initiating communication by the application on a data channel in the Internet Protocol Multimedia Subsystem session based on the outgoing SDP response and according to a threshold quality of service. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 6 The described IMS session manager 640 is performed.

[0189] Fig.14 A flow chart illustrating a method 1400 for supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 and Figures 8 to 11 In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0190] At 1405, the method may include obtaining, from the first UE, an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.10 The described SDP invitation manager 1025 is executed.

[0191] At 1410, the method may include outputting an SDP response for an application associated with the data channel based on receiving an SDP offer that authorizes quality of service resources that meet a threshold quality of service. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.10 The described SDP response manager 1030 is executed.

[0192] At 1415, the method may include obtaining a response confirmation based on receiving the SDP response. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.10 The described response confirmation manager 1035 is executed.

[0193] Fig.15 A flow chart illustrating a method 1500 for supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 3 and Figures 8 to 11 In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0194] At 1505, the method may include obtaining, from the first UE, an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.10 The described SDP invitation manager 1025 is executed.

[0195] At 1510, the method may include authorizing a quality of service resource that satisfies a threshold quality of service. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.10 The described quality of service manager 1040 is implemented.

[0196] At 1515, the method may include outputting an SDP response for an application associated with the data channel based on receiving an SDP offer, the SDP offer authorizing quality of service resources that meet a threshold quality of service, and wherein outputting the SDP response is based on the authorization. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.10 The described SDP response manager 1030 is executed.

[0197] At 1520, the method may include obtaining a response confirmation based on receiving the SDP response. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.10 The described response confirmation manager 1035 is executed.

[0198] Fig.16 A flow chart illustrating a method 1600 for supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 and Figures 8 to 11 In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0199] At 1605, the method may include obtaining, from the first UE, an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.10 The described SDP invitation manager 1025 is executed.

[0200] At 1610, the method may include forwarding the SDP invitation to the second UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference Fig.10 The described SDP invitation manager 1025 is executed.

[0201] At 1615, the method may include obtaining an SDP response from the second UE. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.10The described SDP response manager 1030 is executed.

[0202] At 1620, the method may include outputting an SDP response for an application associated with the data channel based on receiving an SDP offer that authorizes quality of service resources that meet a threshold quality of service. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.10 The described SDP response manager 1030 is executed.

[0203] At 1625, the method may include obtaining a response confirmation based on receiving the SDP response. The operations of 1625 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig.10 The described response confirmation manager 1035 is executed.

[0204] Fig.17 A flow chart illustrating a method 1700 for supporting policy control and mapping of data channels in an Internet Protocol Multimedia Subsystem network according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 and Figures 8 to 11 In some examples, the network entity may execute an instruction set 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 various aspects of the described functions.

[0205] At 1705, the method may include obtaining, from the first UE, an SDP offer for an application associated with the data channel, the SDP offer including an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.10 The described SDP invitation manager 1025 is executed.

[0206] At 1710, the method may include outputting an SDP response for an application associated with the data channel based on receiving an SDP offer that authorizes quality of service resources that meet a threshold quality of service. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.10 The described SDP response manager 1030 is executed.

[0207] At 1715, the method may include obtaining a response confirmation based on receiving the SDP response. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.10 The described response confirmation manager 1035 is executed.

[0208] At 1720, the method may include initiating communication by the application on a data channel in the Internet Protocol Multimedia Subsystem session based on the outgoing SDP response and according to a threshold quality of service. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.10 The described IMS session manager 1045 is performed.

[0209] The following provides an overview of various aspects of the disclosure:

[0210] Aspect 1: A method for wireless communication at a UE, comprising: sending an SDP invitation for an application associated with a data channel, the SDP invitation including an application identifier associated with the application and one or more indications of a threshold service quality associated with the application; receiving an SDP response for the application associated with the data channel based at least in part on sending the SDP invitation, the SDP invitation authorizing service quality resources that meet the threshold service quality; and sending a response confirmation based at least in part on receiving the SDP response.

[0211] Aspect 2: The method according to Aspect 1 further includes: initiating communication by the application on the data channel in the Internet Protocol Multimedia Subsystem session based at least in part on outputting the SDP response and according to the threshold service quality.

[0212] Aspect 3: The method according to any one of aspects 1 to 2, wherein the application identifier comprises a tag indicating the name of the data channel.

[0213] Aspect 4: The method according to any one of aspects 1 to 3, wherein the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

[0214] Aspect 5: The method according to any one of aspects 1 to 4, wherein the application identifier comprises a media-level attribute of a data channel subprotocol attribute associated with the data channel.

[0215] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the application identifier includes one or more parameter values, and the one or more parameter values ​​include: a public land mobile network identifier, a data channel application provider, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0216] Aspect 7: The method according to any one of aspects 1 to 6, wherein the threshold quality of service includes: a threshold packet loss for the application, a threshold latency for the application, or both.

[0217] Aspect 8: The method according to any one of aspects 1 to 7 further includes: obtaining an indication of the application identifier related to installing the application at the UE; and including the indication of the application identifier in the SDP offer.

[0218] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving a data channel application package associated with the application, the data channel application package including the application identifier; and including the indication of the application identifier in the SDP invitation at least partially based on the data channel application package.

[0219] Aspect 10: A method for performing wireless communications at a network device, comprising: obtaining an SDP invitation for an application associated with a data channel from a first UE, the SDP invitation comprising an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; outputting an SDP response for the application associated with the data channel based at least in part on obtaining the SDP invitation, the SDP invitation authorizing quality of service resources that meet the threshold quality of service; and obtaining a response confirmation based at least in part on outputting the SDP response.

[0220] Aspect 11: The method according to aspect 10 further comprises: authorizing quality of service resources that meet the threshold quality of service, wherein outputting the SDP response is based at least in part on the authorization.

[0221] Aspect 12: The method according to any one of aspects 10 to 11 further includes: forwarding the SDP invitation to a second UE; and obtaining the SDP response from the second UE.

[0222] Aspect 13: The method according to aspect 12, wherein outputting the SDP response includes: forwarding the SDP response obtained from the second UE to the first UE.

[0223] Aspect 14: The method according to any one of Aspects 10 to 13 further includes: initiating communication by the application on the data channel in the Internet Protocol Multimedia Subsystem session based at least in part on outputting the SDP response and based on the threshold quality of service.

[0224] Aspect 15: The method according to aspect 14 further comprises: generating billing information associated with the application for the Internet Protocol Multimedia Subsystem session based at least in part on the application identifier.

[0225] Aspect 16: The method according to aspect 15 further includes: providing the charging information to a service provider associated with the first UE.

[0226] Aspect 17: The method according to any one of aspects 10 to 16, wherein the application identifier comprises a tag indicating the name of the data channel.

[0227] Aspect 18: The method according to any one of aspects 10 to 17, wherein the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

[0228] Aspect 19: The method according to any one of aspects 10 to 18, wherein the application identifier comprises a media-level attribute of a data channel subprotocol attribute associated with the data channel.

[0229] Aspect 20: A method according to any one of Aspects 10 to 19, wherein the application identifier comprises one or more parameter values, and the one or more parameter values ​​comprise: a public land mobile network identifier, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

[0230] Aspect 21: The method according to any one of Aspects 10 to 20 further includes: associating the application identifier with a data channel application package corresponding to the application, wherein receiving the SDP invitation including the application identifier is at least partially based on associating the application identifier with the data channel application package.

[0231] Aspect 22: The method according to any one of aspects 10 to 21, wherein the threshold quality of service comprises: a threshold packet loss for the application, a threshold latency for the application, or both.

[0232] Aspect 23: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 9.

[0233] Aspect 24: An apparatus for wireless communication at a UE, comprising: at least one component for performing a method according to any one of aspects 1 to 9.

[0234] Aspect 25: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 9.

[0235] Aspect 26: An apparatus for performing wireless communications at a network device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 10 to 22.

[0236] Aspect 27: An apparatus for wireless communication at a network device, comprising: at least one component for performing the method according to any one of aspects 10 to 22.

[0237] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a network device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 10 to 22.

[0238] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0239] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0241] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0242] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0243] Computer-readable medium includes both non-transient computer storage medium and communication medium, including any medium that promotes computer program to be transmitted from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage or other magnetic storage device or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0244] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0245] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0246] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label or other subsequent reference labels.

[0247] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples". The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0248] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a session description protocol (SDP) offer for an application associated with a data channel, the SDP offer comprising an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; receiving an SDP response for the application associated with the data channel based at least in part on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; as well as A response acknowledgment is sent based at least in part on receiving the SDP response.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on outputting the SDP response and in accordance with the threshold quality of service, initiating communication by the application over the data channel in an Internet Protocol Multimedia Subsystem session. 3 . The apparatus of claim 1 , wherein the application identifier comprises a tag indicating a name of the data channel.

4. The apparatus of claim 1, wherein the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

5. The apparatus of claim 1, wherein the application identifier comprises a media-level attribute of a data channel subprotocol attribute associated with the data channel.

6. The apparatus of claim 1, wherein the instructions are executable by the processor to cause the apparatus to: A public land mobile network identifier, a data channel application provider, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

7. The apparatus of claim 1, wherein the instructions for thresholding quality of service are executable by the processor to cause the apparatus to: A threshold packet loss for the application, a threshold latency for the application, or both.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: obtaining an indication of the application identifier associated with installing the application at the UE; and The application identifier is included in the SDP offer.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a data channel application packet associated with the application, the data channel application packet including the application identifier; and The application identifier is included in the SDP offer based at least in part on the data channel application packet.

10. An apparatus for wireless communication at a network device, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: obtaining, from a first user equipment (UE), a session description protocol (SDP) offer for an application associated with a data channel, the SDP offer comprising an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; outputting an SDP response for the application associated with the data channel based at least in part on obtaining the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; as well as A response acknowledgement is obtained based at least in part on outputting the SDP response.

11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: Quality of service resources that meet the threshold quality of service are authorized, wherein outputting the SDP response is based at least in part on the authorization.

12. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: forwarding the SDP invite to a second UE; and The SDP response is obtained from the second UE.

13. The apparatus of claim 12, wherein the instructions for outputting the SDP response are executable by the processor to cause the apparatus to: The SDP response obtained from the second UE is forwarded to the first UE.

14. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on outputting the SDP response and in accordance with the threshold quality of service, initiating communication by the application over the data channel in an Internet Protocol Multimedia Subsystem session.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Billing information associated with the application is generated for the Internet Protocol Multimedia Subsystem session based at least in part on the application identifier.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: The charging information is provided to a service provider associated with the first UE.

17. The apparatus of claim 10, wherein the application identifier comprises a tag indicating a name of the data channel.

18. The apparatus of claim 10, wherein the application identifier comprises a media-level attribute of a data channel map associated with the data channel.

19. The apparatus of claim 10, wherein the application identifier comprises a media level attribute of a data channel subprotocol attribute associated with the data channel.

20. The apparatus of claim 10, wherein the instructions are executable by the processor to cause the apparatus to: A public land mobile network identifier, a data channel application number assigned by a network provider, a data channel application name, or any combination thereof.

21. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: The application identifier is associated with a data channel application package corresponding to the application, wherein receiving the SDP offer including the application identifier is based at least in part on associating the application identifier with the data channel application package.

22. The apparatus of claim 10, wherein the instructions for thresholding quality of service are executable by the processor to cause the apparatus to: A threshold packet loss for the application, a threshold latency for the application, or both.

23. A method for wireless communication at a user equipment (UE), comprising: sending a session description protocol (SDP) offer for an application associated with a data channel, the SDP offer comprising an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; receiving an SDP response for the application associated with the data channel based at least in part on sending the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; as well as A response acknowledgment is sent based at least in part on receiving the SDP response.

24. The method of claim 23, wherein the application identifier comprises: A tag indicating a name of the data channel, a media-level attribute of a data channel map associated with the data channel, or a data channel subprotocol attribute associated with the data channel.

25. The method of claim 23, wherein the threshold quality of service comprises: A threshold packet loss for the application, a threshold latency for the application, or both.

26. A method for wireless communication at a network device, comprising: obtaining, from a first user equipment (UE), a session description protocol (SDP) offer for an application associated with a data channel, the SDP offer comprising an application identifier associated with the application and one or more indications of a threshold quality of service associated with the application; outputting an SDP response for the application associated with the data channel based at least in part on obtaining the SDP offer, the SDP offer authorizing quality of service resources that meet the threshold quality of service; as well as A response acknowledgement is obtained based at least in part on outputting the SDP response.

27. The method according to claim 26, further comprising: Quality of service resources that meet the threshold quality of service are authorized, wherein outputting the SDP response is based at least in part on the authorization.

28. The method of claim 26, further comprising: Based at least in part on outputting the SDP response and in accordance with the threshold quality of service, initiating communication by the application over the data channel in an Internet Protocol Multimedia Subsystem session.

29. The method according to claim 28, further comprising: Billing information associated with the application is generated for the Internet Protocol Multimedia Subsystem session based at least in part on the application identifier.

30. The method of claim 29, further comprising: The charging information is provided to a service provider associated with the first UE.

Images