Patent ID: 12206717

Corresponding reference characters indicate corresponding parts throughout the drawings. References made throughout this disclosure. relating to specific examples, are provided for illustrative purposes, and are not meant to limit all implementations or to be interpreted as excluding the existence of additional implementations that also incorporate the recited features.

DETAILED DESCRIPTION

Solutions are disclosed that provide for proxy-call session control function (P-CSCF) awareness of access point name (APN) or data network name (DNN). This permits the P-CSCF to enforce policies regarding use of internet protocol (IP) multimedia subsystem (IMS) resources, such as certain voice codecs (e.g., enhanced voice services (EVS) and adaptive multi-rate (AMR) wideband (AMD-WB)) that use larger amounts of bandwidth, based on the APN/DNN assigned to a user equipment (UE). For example, certain IMS resources may be prioritized for home UEs over mobile virtual network operator (MVNO) UEs, or outbound roamers over inbound roamers, leveraging the P-CSCF's awareness of APN/DNN. In some examples, a packet gateway (PGW) or session management function (SMF) inserts APN/DNN information into a session initiation protocol (SIP) message going to the P-CSCF. In some examples, the P-CSCF retrieves APN/DNN information from a policy and charging rules function (PCRF) or a policy control function (PCF).

Aspects of the disclosure improve the efficiency of cellular networks, by introducing a mechanism to prioritize use of IMS resources. The result is that the cellular network requires fewer IMS resources to serve a given number of authorized/prioritized users—or a larger number of authorized/prioritized users may be supported with the same level of resources. These advantageous results are accomplished, at least in part, by extracting, by a proxy node, a network name from a session message and, based on at least the network name and a set of policies associated with a plurality of network names, enforcing a policy associated with the network name for a data session (of a UE) that passes through the proxy node.

With reference now to the figures,FIG.1illustrates an exemplary architecture that advantageously provides for proxy node (e.g., P-CSCF) awareness of network name (e.g., APN or DNN). In the scene depicted inFIG.1, a UE102is using wireless network110for a phone call with another UE106, and a UE104is also using wireless network110for a phone call with another UE108. UE102and UE104may each be a cellular telephone, such as a smartphone, but may also represent other telecommunication devices capable of using a wireless network, such as a personal computer (PC, e.g., desktop, notebook, tablet, etc.) with a cellular modem.

Wireless network110may be a cellular network such as a fifth-generation cellular technology (5G) network, a fourth-generation cellular technology (4G) network, or another cellular generation network. UE102uses an air interface103to communicate with a base station111of wireless network110, and UE104is also using base station111via an air interface105. In some scenarios, base station111may also be referred to as a radio access network (RAN). Wireless network110has a control plane115comprising an access node112, a session management node113, and a policy node114. Wireless network110also has a packet routing node116in a user plane, and a proxy node117.

Base station111is in communication with access node112and packet routing node116. Access node112is in communication with session management node113and session management node113is in communication with policy node114. Packet routing node116is in communication with session management node113, proxy node117, and an external packet data network152, such as the internet. In some 5G examples, base station111comprises a gNodeB (gNB), access node112comprises an access mobility function (AMF), session management node113comprises a session management function (SMF), policy node114comprises a PCF, and packet routing node116comprises a user plane function (UPF).

In some 4G examples, base station111comprises an eNodeB (eNB), access node112comprises a mobility management entity (MME), session management node113comprises a system architecture evolution gateway (SAEGW) control plane (SAEGW-C), and packet routing node116comprises an SAEGW-user plane (SAEGW-U). In some examples an SAEGW-C may be referred to, or include, a PGW-control plane (PGW-C), and an SAEGW-U may be referred to, or include, a PGW-user plane (PGW-U). In some examples, proxy node117comprises a proxy call session control function (P-CSCF) in both 4G and 5G. In some examples, wireless network110has multiple ones of each of the components illustrated, in addition to other components and other connectivity among the illustrated components. In some examples, wireless network110has components of multiple cellular technologies operating in parallel in order to provide service to UEs of different cellular generations.

Proxy node117is in communication with an IMS140, in order to provide connectivity to other wireless (cellular) networks or a public switched telephone system (POTS). In some examples, proxy node117may be considered to be within IMS140. UE102reaches a media resource156using IMS140(which includes an IMS access gateway, IMS-AGW). Data packets, including voice, video, and short message service (SMS), to/from UE102pass through base station111, packet routing node116, and proxy node117on their way to/from IMS140and either media resource156or UE106. For other packet data traffic (e.g., generic internet traffic), data packets to/from UE102pass through base station111and packet routing node116on their way to external packet data network152and a network resource154(e.g., a website).

IMS140enables voice calls, video calls, and other communication services such as SMS (commonly-referred to as text messages), multimedia messaging service (MMS), and connectivity to a public switched telephone network (PSTN). IMS140also supports interoperability across different devices, networks, and operators such as, for example, providing transcoding from the codec used by one UE in a voice and/or video call does not match the codec (or other voice communication scheme) used by the other side. For examples, UE102may use AMR narrowband (AMR-NB) whereas UE106using AMR-WB or represents a landline phone on a PSTN that uses the G.711 codec. Some resource within IMS140transcodes between AMR-NB and AMR-WB or G.711.

In the scenario depicted inFIG.1, UE102communicates with UE106using a data session160that passes through proxy node117to/from IMS140, and UE104communicates with UE108using a data session162that also passes through proxy node117to/from IMS140. In such a scenario, transcoding for data sessions160and162, which occurs within IMS140, is invoked by proxy node117. Thus, proxy node117should be configured to only invoke the authorized transcoding and other services within IMS140. The authorizations are contained within policies130.

IMS140is shown as having a pool of IMS functions, including an IMS function142and an IMS function146. IMS functions142and146represent and relevant IMS nodes, servers, or other capabilities, such as an AGW or media gateway (MGW) with transcoding capability, or another IMS entity. IMS functions142and146are each illustrated as having resources, for example, IMS function142has a resource144aand a resource144b, and IMS function146has a resource148aand a resource148b. For purposes of describing the example scenario herein, resource144aand resource148aare the same resource, an EVS codec, and resource144band resource148bare also the same resource, an AMR-NB codec. It should be understood, however, that other examples of architecture100may have a larger number of IMS functions, each with a larger number of resources, and resources may vary among IMS functions.

When UE102attaches to wireless network110, session management node113uses APN assignment logic120to assign an IMS function to UE, typically based on the status of UE102. UE102may be a home (non-roaming) subscriber, an MVNO subscriber, an inbound roamer, or an outbound roamer. Different IMS functions may be reserved for different types of UEs. For example, an MVNO subscriber may be assigned an APN/DNN corresponding to IMS function142, whereas a home (non-roaming) subscriber may be assigned an APN/DNN corresponding to IMS function146. There may be similar set of IMS functions for roamers (also based on the roaming partner), peering network users, partner carrier users, prepaid versus postpaid accounts, cellular technology (e.g., 5G versus 4G users), and UEs located in certain countries. Some UEs may be assigned an SOS-only function for an emergency call, from SOS MGW pool150. An example of this is a UE with no subscriber identity module (SIM) that is attempting to place a 911 call.

Different resources may thus be available for the different UEs based on the APN/DNN assigned to the UE, including different codecs (e.g., voice and video codecs), resource management for internet of things (IoT) and mobile-to-mobile (M2M) devices and communications, access to artificial intelligence (AI), machine learning (ML), and generative AI services, and other.

After attachment, upon being assigned an APN/DNN, UE102transmits a SIP message (e.g., a SIP Register) to the IMS function associated with the APN/DNN. This SIP message passes through proxy node117. However, this SIP message has only the IP address of the assigned IMS function (e.g., the IP address of IMS function142). The actual APN/DNN (generically, network name) is not included within the SIP message to IMS function142—at least as transmitted by UE102.

However, in some examples of architecture100, APN assignment logic120adds the APN/DNN (e.g., network name132) into the SIP message. Proxy node117uses APN awareness logic122to extract network name132(the APN/DNN), and caches it. In some examples, APN awareness logic122retrieves network name132by subscribes APN information from policy node114. This is done using a diameter request (Rx interface) in 4G or http (N5 interface) in 5G. Policy node114retrieves network name132from session management node113, and sends network name132to proxy node117. With either approach, proxy node117has network name132.

Proxy node117uses policies130to determine which resources within IMS140to permit UE102to access. Policies130has a set of policies131associated with a plurality of network names133. Plurality of network names133includes network name132for IMS function142and a network name136for IMS function146. A policy134aand a policy134bare for UEs assigned to network name132, and a policy138aand a policy138bare for UEs assigned to network name136.

In the illustrated example scenario, IMS function142is an IMS function for UEs using an MVNO, and has an EVS codec as resource144aand an AMR-NB codec as resource144b. (IMS function142is able to transcode or access a transcoder, and may also offer AMS-WB as another resource.) Network name132is for IMS function142, and policy134astates that resource144a(EVS codec) is prohibited and policy134bstates that resource144b(AMR-NB codec) is permitted. UE102is an MVNO subscriber, and so is assigned to IMS function142. Thus, UE102is prohibited from using EVS on wireless network110, but is permitted to use AMR-NB.

Also in the illustrated example scenario, IMS function146is an IMS function for home subscriber UEs, and is configured similarly to IMS function142, having an EVS codec as resource148aand an AMR-NB codec as resource148b. Network name136is for IMS function146, and policy138astates that resource148a(EVS codec) is permitted and policy138bstates that resource148b(AMR-NB codec) is permitted. UE104is a home subscriber, and so is assigned to IMS function146. Thus, UE104is permitted to use both EVS and AMR-NB on wireless network110. The use of one codec or another may be determined by other factors, such as UE capability and channel quality, but both are permitted.

Proxy node117retrieves network name136using APN awareness logic122, either extracting network name136from a SIP message sent by UE104to IMS function146, after APN assignment logic120inserted network name136into the SIP message, or using policy node114to retrieve network name136from session management node113.

In some examples, policies may prevent a UE from using a resource not by an outright prohibition, but instead by a prioritization in which an insufficient number of IMS or network resources are available. For example, rather than prohibiting use of an EVS codec, policy134ade-prioritizes MVNO UEs, using the current loading of wireless network110as the determining factor. For example, when loading of wireless network110is below a low threshold, MVNO UEs are permitted to use an EVS codec. Meanwhile, policy138aprioritizes home subscriber UEs, by using a higher threshold (i.e., higher than the low threshold) of the loading of wireless network110to permit home subscriber UEs to use an EVS codec. Other resources may be prioritized and other prioritization schemes may be used, such as a count of UEs using a particular resource.

FIG.2illustrates a message sequence diagram200of messaging that may occur in examples of architecture100, andFIG.3illustrates a flowchart300of exemplary operations associated with message sequence diagram200occurring within architecture100.FIGS.2and3are described together. In some examples, at least a portion of flowchart300may be performed using one or more computing devices700ofFIG.7.

Flowchart300commences with UE102attaching to wireless network110in operation302, which is shown as message202in message sequence diagram200ofFIG.2. Session management node113(a control plane node) assigns network name132to UE102in operation304, and transmits the IP address of IMS function142(which corresponds to network name132) to UE102as message204.

UE102transmits session message206to IMS function142in operation306. In some examples, session message206comprises a SIP message, such as a SIP Register or a SIP Invite. Because session message206is a signaling message, it passes through control plane115of wireless network and is received by session management node113in operation308. In operation310, session management node113inserts network name132into session message206. This is shown as message208. In some examples, network name132includes an operator identifier field. In some examples, access node112inserts network name132into session message206. In some examples, session management node113or access node112generates a new session message and inserts network name132into the new session message.

Session management node113forwarding session message206with network name132to proxy node117in operation312, and proxy node117receives session message206in operation314. Session message206contains both an indication of UE102and also network name132. Proxy node117extracts network name132and the identity of UE102from session message206in operation316. This is shown as message210.

Wireless network110creates data session160for UE102in operation318. Data session160passes through proxy node117, carrying data traffic between UE102and IMS140. In operation320, proxy node117enforces policy134aassociated with network name132for data session160, based on at least network name132and set of policies131associated with plurality of network names133(specifically policies134aand134bassociated with network name132). This is shown as message212. In some examples, policy134aprevents use of a resource by UE102, such as a codec, WiFi calling, or another resource (e.g., resource144a).

UE104attaches to wireless network110in operation332, which is shown as message232. Session management node113assigns network name136to UE104in operation334, and transmits the IP address of IMS function142(which corresponds to network name136) to UE104as message234.

UE104transmits session message236to IMS function142in operation336. In some examples, session message236comprises a SIP message, such as a SIP Register or a SIP Invite. Because session message236is a signaling message, it passes through control plane115of wireless network and is received by session management node113in operation338. In operation340, session management node113inserts network name136into session message236. This is shown as message238. In some examples, network name136includes an operator identifier field. In some examples, access node112inserts network name136into session message236. In some examples, session management node113or access node112generates a new session message and inserts network name136into the new session message.

Session management node113forwarding session message236with network name136to proxy node117in operation342, and proxy node117receives session message236in operation344. Session message236contains both an indication of UE104and also network name136. Proxy node117extracts network name136and the identity of UE104from session message236in operation346. This is shown as message240.

Wireless network110creates data session162for UE104in operation348. Data session162passes through proxy node117, carrying data traffic between UE104and IMS140. In operation350, proxy node117enforces policy138aassociated with network name136for data session160, based on at least network name136and set of policies131associated with plurality of network names133(specifically policies138aand138bassociated with network name136). This is shown as message242. In some examples, policy138apermits use of a resource by UE104, such as a codec, WiFi calling, or another resource (e.g., resource148a) that had been prevented for UE102(e.g., by policy134a).

In some examples, policy134aprevents use of a resource by UE102and policy138apermits use of the same or an equivalent resource by UE104as a consequence of prioritizing UE104over UE102for use of that resource, whereas in some examples policy134aoutright prohibits use of resource144a(independently of prioritization). For example, in scenarios of prioritization, policy134amay permit UE102to use a certain codec when bandwidth demand on wireless network is low, whereas policy138apermits UE104to use that same codec even when bandwidth demand on wireless network is higher.

FIG.4illustrates a message sequence diagram400of messaging that may occur in examples of architecture100, in an alternate form of operation, andFIG.5illustrates a flowchart500of exemplary operations associated with message sequence diagram400occurring within architecture100.FIGS.4and5are described together. In some examples, at least a portion of flowchart500may be performed using one or more computing devices700ofFIG.7. In some examples, the messages of message sequence diagrams200and400and the operations of flowcharts300and500may be blended into a combined form of operation.

Flowchart500commences with UE102attaching to wireless network110in operation502, which is shown as message402in message sequence diagram400ofFIG.4. Session management node113assigns network name132to UE102in operation504, and transmits the IP address of IMS function142to UE102as message404.

UE102transmits session message406to IMS function142in operation506. In some examples, session message406comprises a SIP message, such as a SIP Register or a SIP Invite. Because session message406is a signaling message, it passes through control plane115of wireless network110. Session management node113receives session message406from UE102in operation508and forwards session message406(without network name132in this sequence of operations) to proxy node117in operation510. Proxy node117receives session message406, which has an indication of UE102and the IP address of IMS function142(but not network name132) in operation512.

Proxy node117retrieves network name132from policy node114in operation514, which may be performed using operations516-524. In operation516, proxy node117subscribes to APN/DNN information with policy node114, which is shown as message408. Policy node114retrieves network name132from session management node113in operation518, which in some examples is performed using operations520and522. In some examples, policy node114pulls APN/DNN information from session management node113by requesting the APN/DNN information (which includes network name132) in operation520. This is shown as message410.

In operation522, session management node113transmits network name132to policy node114as message412. In some examples, this is in response to message410, whereas in some examples, session management node113pushes APN/DNN information to policy node114. In operation524, policy node114transmits network name132to proxy node117as message414.

Wireless network110creates data session160for UE102in operation526. Data session160passes through proxy node117, carrying data traffic between UE102and IMS140. In operation528, proxy node117enforces policy134aassociated with network name132for data session160, based on at least network name132and set of policies131associated with plurality of network names133(specifically policies134aand134bassociated with network name132). This is shown as message416. In some examples, policy134aprevents use of a resource by UE102, such as a codec, WiFi calling, or another resource (e.g., resource144a).

UE104attaches to wireless network110in operation532, which is shown as message432. Session management node113assigns network name132to UE104in operation534, and transmits the IP address of IMS function142to UE104as message434. UE104transmits session message436to IMS function142in operation536. In some examples, session message436comprises a SIP message, such as a SIP Register or a SIP Invite. Because session message436is a signaling message, it passes through control plane115of wireless network110.

Session management node113receives session message436from UE104in operation538and forwards session message436(without network name136in this sequence of operations) to proxy node117in operation540. Proxy node117receives session message436, which has an indication of UE104and the IP address of IMS function142(but not network name136) in operation542.

Proxy node117retrieves network name136from policy node114in operation544, which may be performed using operations546-554. In operation546, proxy node117subscribes to APN/DNN information with policy node114, which is shown as message438. Policy node114retrieves network name136from session management node113in operation548, which in some examples is performed using operations550and552. In some examples, policy node114pulls APN/DNN information from session management node113by requesting the APN/DNN information (which includes network name136) in operation550. This is shown as message440.

In operation552, session management node113transmits network name136to policy node114as message442. In some examples, this is in response to message440, whereas in some examples, session management node113pushes APN/DNN information to policy node114. In operation554, policy node114transmits network name136to proxy node117as message444.

Wireless network110creates data session162for UE104in operation556. Data session162passes through proxy node117, carrying data traffic between UE104and IMS140. In operation558, proxy node117enforces policy138aassociated with network name136for data session162, based on at least network name136and set of policies131associated with plurality of network names133(specifically policies138aand138bassociated with network name136). This is shown as message446.

FIG.6Aillustrates a flowchart600of exemplary operations associated with examples of architecture100. In some examples, at least a portion of flowchart600may be performed using one or more computing devices700ofFIG.7. Flowchart600commences with operation602, which includes inserting, by a control plane node of a wireless network, into a first session message, a first network name assigned to a first UE.

Operation604includes forwarding the first session message with the first network name to a proxy node. Operation606includes extracting, by the proxy node, the first network name from the first session message. Operation608includes, based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node.

FIG.6Billustrates a flowchart650of exemplary operations associated with examples of architecture100. In some examples, at least a portion of flowchart650may be performed using one or more computing devices700ofFIG.7. Flowchart650commences with operation652, which includes receiving, by a proxy node of a wireless network, a first session message indicating a first UE. Operation654includes receiving, by the proxy node, a second session message indicating a second UE.

Operation656includes retrieving, from a first control plane node, a first network name assigned to the first UE and a second network name assigned to the second UE. Operation658includes, based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node. Operation660includes, based on at least the second network name and the set of policies associated with the plurality of network names, enforcing a second policy associated with the second network name for a second data session of the second UE that passes through the proxy node, wherein the first policy prevents use of a resource by the first UE and the second policy permits use of the resource by the second UE.

FIG.7illustrates a block diagram of computing device700that may be used as any component described herein that may require computational or storage capacity. Computing device700has at least a processor702and a memory704that holds program code710, data area720, and other logic and storage730. Memory704is any device allowing information, such as computer executable instructions and/or other data, to be stored and retrieved. For example, memory704may include one or more random access memory (RAM) modules, flash memory modules, hard disks, solid-state disks, persistent memory devices, and/or optical disks. Program code710comprises computer executable instructions and computer executable components including instructions used to perform operations described herein. Data area720holds data used to perform operations described herein. Memory704also includes other logic and storage730that performs or facilitates other functions disclosed herein or otherwise required of computing device700. An input/output (I/O) component740facilitates receiving input from users and other devices and generating displays for users and outputs for other devices. A network interface750permits communication over external network760with a remote node770, which may represent another implementation of computing device700. For example, a remote node770may represent another of the above-noted nodes within architecture100.

Additional Examples

An example system comprises: a processor; and a computer-readable medium storing instructions that are operative upon execution by the processor to: insert, by a control plane node of a wireless network, into a first session message, a first network name assigned to a first UE: forward the first session message with the first network name to a proxy node; extract, by the proxy node, the first network name from the first session message; and based on at least the first network name and a set of policies associated with a plurality of network names, enforce a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node.

An example method of wireless communication comprises: inserting, by a control plane node of a wireless network, into a first session message, a first network name assigned to a first UE; forwarding the first session message with the first network name to a proxy node: extracting, by the proxy node, the first network name from the first session message; and based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node.

One or more example computer storage devices has computer-executable instructions stored thereon, which, upon execution by a computer, cause the computer to perform operations comprising: inserting, by a control plane node of a wireless network, into a first session message, a first network name assigned to a first UE; forwarding the first session message with the first network name to a proxy node: extracting, by the proxy node, the first network name from the first session message; and based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node.

Another example system comprises: a processor; and a computer-readable medium storing instructions that are operative upon execution by the processor to: receive, by a proxy node of a wireless network, a first session message indicating a first UE; receive, by the proxy node, a second session message indicating a second UE; retrieve, from a first control plane node, a first network name assigned to the first UE and a second network name assigned to the second UE; based on at least the first network name and a set of policies associated with a plurality of network names, enforce a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node; and based on at least the second network name and the set of policies associated with the plurality of network names, enforce a second policy associated with the second network name for a second data session of the second UE that passes through the proxy node, wherein the first policy prevents use of a resource by the first UE and the second policy permits use of the resource by the second UE.

Another example method of wireless communication comprises: receiving, by a proxy node of a wireless network, a first session message indicating a first UE: receiving, by the proxy node, a second session message indicating a second UE; retrieving, from a first control plane node, a first network name assigned to the first UE and a second network name assigned to the second UE: based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node; and based on at least the second network name and the set of policies associated with the plurality of network names, enforcing a second policy associated with the second network name for a second data session of the second UE that passes through the proxy node, wherein the first policy prevents use of a resource by the first UE and the second policy permits use of the resource by the second UE.

One or more example computer storage devices has computer-executable instructions stored thereon, which, upon execution by a computer, cause the computer to perform operations comprising: receiving, by a proxy node of a wireless network, a first session message indicating a first UE: receiving, by the proxy node, a second session message indicating a second UE: retrieving, from a first control plane node, a first network name assigned to the first UE and a second network name assigned to the second UE; based on at least the first network name and a set of policies associated with a plurality of network names, enforcing a first policy associated with the first network name for a first data session of the first UE that passes through the proxy node; and based on at least the second network name and the set of policies associated with the plurality of network names, enforcing a second policy associated with the second network name for a second data session of the second UE that passes through the proxy node, wherein the first policy prevents use of a resource by the first UE and the second policy permits use of the resource by the second UE.

Alternatively, or in addition to the other examples described herein, examples include any combination of the following:inserting, by the control plane node, into a second session message, a second network name assigned to a second UE, the second network name different from the first network name;forwarding the second session message with the second network name to the proxy node;extracting, by the proxy node, the second network name from the second session message;based on at least the second network name and the set of policies associated with the plurality of network names, enforcing a second policy associated with the second network name for a second data session of the second UE that passes through the proxy node;the first policy prevents use of a resource by the first UE and the second policy permits use of the resource by the second UE;the first policy prevents use of the resource by the first UE and the second policy permits use of the resource by the second UE as a consequence of prioritizing the second UE over the first UE for use of the resource;the first policy prevents use of a codec by the first UE;the codec comprises an EVS codec or an AMD-WB codec;the first network name comprises an APN or a DNN;the control plane node comprises a PGW or an SMF;the proxy node comprises a P-CSCF;the first session message comprises a SIP message;the first session message comprises a SIP Register or a SIP Invite;the first data session carries data traffic to and from an IMS;retrieving, by the first control plane node, from a second control plane node, the first network name and the second network name;the second network name comprises an APN or a DNN;the first control plane node comprises a PCRF or a PCF;the second control plane node comprises a PGW or an SMF;the second session message comprises a SIP message;the second session message comprises a SIP Register or a SIP Invite;the first UE attaches to the wireless network;the second UE attaches to the wireless network;assigning, by the control plane node, to the first UE, the first network name;assigning, by the control plane node, to the second UE, the second network name;the first network name and the second network name each includes an operator identifier field;the control plane node comprises a PGW-Cthe control plane node comprises an MME or an AMF;the first UE transmits the first session message to a network node (IMS function) corresponding to the first network name;the second UE transmits the second session message to a network node (IMS function) corresponding to the second network name;receiving, by the control plane node, the first session message from the first UE and the second session message from the second UE;the control plane node generates the first session message and the second session message;the control plane node forwards the first session message and the second session message;forwarding the first session message to the proxy node comprises forwarding the session message through another control plane node of the wireless network;receiving, by the proxy node, the first session message;receiving, by the proxy node, the second session message;creating the first data session;creating the second data session; andthe first policy prohibits use of the resource by the first UE.

The order of execution or performance of the operations in examples of the disclosure illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and examples of the disclosure may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the disclosure. It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. When introducing elements of aspects of the disclosure or the examples thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. The term “exemplary” is intended to mean “an example of.”

Having described aspects of the disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the disclosure as defined in the appended claims. As various changes may be made in the above constructions, products, and methods without departing from the scope of aspects of the disclosure, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.