WO2025158379A1

WO2025158379A1 - Framework for per application data off exemption for internet protocol multimedia subsystem data channel

Info

Publication number: WO2025158379A1
Application number: PCT/IB2025/050814
Authority: WO
Inventors: George Foti
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2024-01-26
Filing date: 2025-01-24
Publication date: 2025-07-31
Anticipated expiration: 2026-07-26

Abstract

A method, system and apparatus are disclosed. A method in a first network node configured to communicate with a second network node is described. The method includes receiving a notification of one or more session events related to one or more application data channel requests, where the notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device (WD), applying a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN, and determining that at least one of one or more application data channels are not allowed for the WD based on the applied policy. The method also includes instructing the second network node based on the determination.

Description

FRAMEWORK FOR PER APPLICATION DATA OFF EXEMPTION FOR INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM DATA CHANNEL

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to determining exemptions for Internet Protocol (IP) Multimedia Subsystem (IMS) Data Channel (IMS DC).

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes (NNs), such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

A WD may typically support services that allow the WD to transmit and/or receive data from other devices and/or network nodes in a network. However, the services may be deactivated when a predetermined condition is met such as when a user of the WD has deactivated the services, the WD is connected to a predetermined network such as a visited network that requires roaming and roaming is disabled. However, a WD may support or enable communication services when the services are exempted from a predetermined condition or requirement. For example, a WD may support or enable communication services such as “Data Off’ exempted services (e.g., when the WD is data exempt). “Data Off’ exempted services may refer to services that can be supported even though user “Data Off’ status is active, or other conditions are met. However, exempted services may cause all applications over an IMS data channel to be allowed to communicate, without being able to select specific applications for communication. Further, an IMS DC may be treated as a single service that is not exempted when data services are turned off and/or Data Off is active, when the WD is roaming, i.e., IMS DC may not be available when these conditions are met.

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for determining exemptions for predetermined data channels such as IMS DC. One or more embodiments provide a fine granularity for data channels such as the IMS DC such that the data channels are exempted (e.g., one or more Data Off exemptions are enabled or allowed, the data channels can be used for communication, etc.). In some embodiments, data channels are allowed to be used for communication based on one or more application identifiers (IDs), e.g., where applications corresponding to the applications IDs are allowed to communicate when Data Off is enabled or any other restrictions are active. That is, the exemptions can be used when Data Off or any other restrictions are active.

In some embodiments, a framework that enables communication on a per- application or per-application-ID or other parameter/attribute basis is provided. In some embodiments, a first application (e.g., having a first application ID, or associated with a predetermined parameter or attribute, etc.) may be data exempt but can be used to transmit and/or receive data to/from another device or node (e.g., in a network such as visited Public Land Mobile Network (PLMN)), while a second application (e.g., having a second application ID, or associated with a predetermined parameter or attribute, etc.) is not data exempt and is not allowed to transmit and/or receive data to/from another device or node (e.g., in a network such as the visited PLMN).

According to one aspect, a method in a first network node configured to communicate with a second network node is described. The method includes receiving a notification of one or more session events related to one or more application data channel requests, where the notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device (WD), applying a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN, and determining that at least one of one or more application data channels are not allowed for the WD based on the applied policy. The method also includes instructing the second network node based on the determination.

In some embodiments, the instructing includes, if all requested applications data channels are not allowed, transmitting a first instruction to the second network node instructing the second network node to return a modified Session Description Protocol (SDP) answer to the WD in response to a first media flow offer from the WD.

In some other embodiments, the first instruction further instructs the second network node to terminate the first media flow offer.

In some embodiments, the instructing includes, if at least one of the requested application data channels are not allowed, transmitting a second instruction to the second network node. The second instruction instructs the second network node to transmit a second media flow offer to a target network (e.g., target network and/or WD). The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value. The first reserved ID value indicates that the WD is not allowed to use a first application data channel of the at least one of the requested application data channels.

In some other embodiments, the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value. The second reserved ID value indicates that the WD is allowed to use a second application data channel of the at least one of the requested application data channels.

In some embodiments, the second instruction further instructs the second network node to terminate the first media flow offer.

In some other embodiments, instructing the second network node is further based on whether the WD is roaming.

In some embodiments, the first network node includes a Data Channel Signaling Function (DCSF), and the second network node includes an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

According to another aspect, a first network node configured to communicate with a second network node is described. The first network node is configured to perform one or more steps of any one of the method embodiments implemented in the first network node.

According to one aspect, a method in a second network node configured to communicate with a first network node is described. The method includes transmitting a notification of one or more session events related to one or more application data channel requests. The notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device. The notification is usable by the first network node to apply a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN. The method further includes receiving an instruction from the first network node, where the instruction instructs the second network node that at least one of one or more application data channels are not allowed for the wireless device. The instruction is based on the policy. In addition, the method includes performing one or more actions based on the instruction.

In some embodiments, if all requested applications data channels are not allowed, the instruction includes a first instruction instructing the second network node to return a modified Session Description Protocol (SDP) answer to the WD in response to a first media flow offer from the WD. The one or more actions includes returning the modified SDP answer to the WD.

In some other embodiments, the one or more actions includes terminating the first media flow offer in response to the first instruction.

In some embodiments, if at least one of the requested application data channels are not allowed, the instruction includes a second instruction instructing the second network node to transmit a second media flow offer to one or both of a target network and the WD. The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value. The first reserved ID value indicates that the WD is not allowed to use a first application data channel of the at least one of the requested application data channels. The one or more actions includes transmitting the second media flow offer.

In some embodiments, the second instruction further instructs the second network node to terminate the first media flow offer, and the one or more actions includes terminating the first media flow offer.

In some other embodiments, the instruction is further based on whether the WD is roaming.

In some embodiments, the first network node includes a Data Channel Signaling Function (DCSF), and the second network node comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

According to another aspect, a second network node configured to communicate with a first network node is described. The second network node is configured to perform one or more steps of any one of the method embodiments implemented in the second network node.

According to one aspect, a method in a wireless device (WD) configured to communicate with a first network node and a second network node is described. The WD is served by a Public Land Mobile Network (PLMN). The method includes transmitting, to the second network node, a first media flow offer including information related to one or more application data channels requested by the WD to one or both of transmit and receive data. The method also includes receiving, from the first network node via the second network node, a response message indicating that the WD is not allowed to use at least one of the one or more application data channels to one or both of transmit and receive data while being served by the PLMN. In addition, the method includes performing one or more actions based on the response message.

In some embodiments, if the WD is not allowed to use all applications data channels, the response message includes a modified Session Description Protocol (SDP) answer, and the first media flow offer is terminated.

In some other embodiments, if the WD is not allowed to use at least one of the application data channels, the response message includes a second media flow offer (e.g., the response message and/or second media flow offer is sent to the WD, the WD receives the response message and/or second media flow offer, etc.). The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value, and the first reserved ID value indicates that the WD is not allowed to use a first application data channel of the one or more application data channels.

In some embodiments, the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value. The second reserved ID value indicates that the WD is allowed to use a second application data channel of the at least one of the requested application data channels.

In some other embodiments, when the response message includes the second media flow offer, the first media flow offer is terminated.

In some embodiments, the first network node comprises a Data Channel Signaling Function (DCSF) and the second network node comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

According to another aspect, a wireless device (WD) configured to communicate with a first network node and a second network node is described. The WD is served by a Public Land Mobile Network (PLMN) and is configured to perform one or more steps of any one of the method embodiments implemented in the WD.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 2 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 3 is a flowchart of an example process in a first network node according to some embodiments of the present disclosure;

FIG. 4 is a flowchart of an example process in a second network node according to some embodiments of the present disclosure;

FIG. 5 is a flowchart of an example process in a first network node according to some embodiments of the present disclosure;

FIG. 6 is a flowchart of an example process in a second network node according to some embodiments of the present disclosure;

FIG. 7 is a flowchart of an example process in a WD according to some embodiments of the present disclosure;

FIG. 8 shows steps of an example call flow indicating how information can be conveyed and used according to some embodiments of the present disclosure; and

FIG. 9 shows other steps of the example call flow indicating how information can be conveyed and used according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to determining exemptions for IMS DC. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), IMS DC, IMS AS, a call session control function (CSCF) (e.g., proxy CSCF (P-CSCF), PS CSCF, etc.), media function (MF), media resource function (MRF), DC AS, etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-ccll/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

In some embodiments, a software application may be referred to as an application. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network (RAN) 12, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first WD 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as WDs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16. Core network 14 may include one or more core network nodes (also referred to herein as network nodes 16) having hardware and/or software that generally corresponds to the hardware and/or software in network node 16, but arranged to perform the functions of the particular core network node as opposed to a network node 16 in the access network 12.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

A network node 16 is configured to include a node management unit 24 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., network node functions. A WD 22 is configured to include a WD management unit 26 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., WD functions.

Further, any of the radio access network 12 (and/or its components such as network nodes 16 and/or WDs 22) and/or core network 14 may be in communication with any other network such as a cloud network. Although not shown, core network 14 may include one or more network nodes 16 (and/or WDs 22).

Example implementations, in accordance with an embodiment, of the WD 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

The communication system 10 includes a network node 16 provided in a communication system 10. Network node 16 includes hardware 28 enabling it to communicate with the WD 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The radio interface 30 includes an array of antennas 31 to radiate and receive signal(s) carrying electromagnetic waves. In some embodiments, radio interface 30 may be configured for setting up and maintaining at least a wireless/wired connection with other network nodes 16. In some embodiments, network node 16 may include a communication interface 34 configured to perform functions similar to the radio interface functions, e.g., communicate with other network nodes 16 via wired or wireless links.

In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and/or read from) the memory 40, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may include application 44 which may include software application configured to provide application functions, such as a functions associated with a service provided to WD 22.

The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and/or processing circuitry 36, causes the processor 38 and/or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include a node management unit 24 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., network node functions.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 46 that may include a radio interface 48 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 48 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The radio interface 48 includes an array of antennas 50 to radiate and receive signal(s) carrying electromagnetic waves. In some embodiments, WD 22 may include a communication interface configured to perform functions similar to radio interface 48, e.g., communicate with other WDs 22 via wired or wireless links.

The hardware 46 of the WD 22 further includes processing circuitry 52. The processing circuitry 52 may include a processor 54 and memory 56. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 52 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 54 may be configured to access (e.g., write to and/or read from) memory 56, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 58, which is stored in, for example, memory 56 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 58 may be executable by the processing circuitry 52. The software 58 may include an application 60. The application 60 may be operable to provide a service to a human or non-human user via the WD 22 and/or be configured to provide application client functions, e.g., associated with application 44.

The processing circuitry 52 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 54 corresponds to one or more processors 54 for performing WD 22 functions described herein. The WD 22 includes memory 56 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 58 and/or the application 60 may include instructions that, when executed by the processor 54 and/or processing circuitry 52, causes the processor 54 and/or processing circuitry 52 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 52 of the WD 22 may include WD management unit 26 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., WD functions.

In some embodiments, the inner workings of the network node 16 and WD 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

The wireless connection 32 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

Although FIGS. 1 and 2 show various “units” such as node management unit 24 and WD management unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 3 is a flowchart of an example process in a first network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and/or communication interface 34. Network node 16 such as via processing circuitry 36 and/or processor 38 and/or radio interface 30 and/or communication interface 34 is configured to receive (Block SI 00) a notification of one or more session events related to one or more application data channel requests, where the notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device 22, and apply (Block S102) a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN. The first network node 16 is further configured to determine (Block SI 04) that all requested application data channels of the one or more application data channels are not allowed for the wireless device or at least one of the one or more application data channels are not allowed for the wireless device and instruct (Block SI 06) the second network node 16 based on the determination.

In some embodiments, instructing includes, if all requested applications data channels are not allowed then, transmitting a first instruction “TerminateAndReturnModifiedMediaAnswer” to the second network node 16 to immediately return a Session Description Protocol (SDP) answer back to the wireless device 22.

In some other embodiments, instructing includes, if some of the requested application data channels are not allowed, transmitting a second instruction “TerminateAndOriginateModifiedMedia” to the second network node 16 and including a new offer to be sent by the second network node 16 towards a target network, where the new offer changes an “a:dcmap” attribute for the not allowed application data channels to a reserved stream ID value of “99999”. However, it noted that the reserved stream ID value of “99999” is only an example value for ease of understanding and any other reserve stream ID values may be used.

In some embodiments, the first network node 16 comprises a Data Channel Signaling Function (DCSF) and the second network node 16 comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS). FIG. 4 is a flowchart of an example process in a second network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and/or communication interface 34. Network node 16 such as via processing circuitry 36 and/or processor 38 and/or radio interface 30 and/or communication interface 34 is configured to transmit (Block S108) a notification of one or more session events related to one or more application data channel requests, where the notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device 22, and the notification is usable by the first network node 16 to apply a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN. The second network node 16 is further configured to receive (Block SI 10) an instruction from the first network node 16 instructing the second network node 16 based on whether all requested application data channels of the one or more application data channels are not allowed for the wireless device 22 or at least one of the one or more application data channels are not allowed for the wireless device 22.

In some embodiments, instructing includes if all requested applications data channels are not allowed, receiving a first instruction “TerminateAndReturnModifiedMediaAnswer” from the first network node 16 instructing the second network node 16 to immediately return a Session Description Protocol (SDP) answer back to the wireless device 22.

In some other embodiments, instructing includes if some of the requested application data channels are not allowed, receiving a second instruction “TerminateAndOriginateModifiedMedia” from the first network node 16, the second instruction including a new offer to be sent by the second network node 16 towards a target network. The new offer changes “an a:dcmap” attribute for the not allowed application data channels to a reserved stream ID value of “99999”. However, as noted above, the reserved stream ID value of “99999” is only an example value, and any other reserve stream ID values may be used.

In some embodiments, the first network node 16 comprises a Data Channel Signaling Function (DCSF) and the second network node 16 comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

FIG. 5 is a flowchart of an example process in a first network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and/or communication interface 34. Network node 16 such as via processing circuitry 36 and/or processor 38 and/or radio interface 30 and/or communication interface 34 is configured to receive (Block SI 12) a notification of one or more session events related to one or more application data channel requests, where the notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device (WD) 22, applying (Block SI 14) a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN (e.g., access network 12, core network 14, or any other network), and determining (Block SI 16) that at least one of one or more application data channels are not allowed for the WD 22 based on the applied policy. The network node 16 is also configured to instruct (Block SI 18) the second network node 16 based on the determination.

In some embodiments, the instructing includes, if all requested applications data channels are not allowed, transmitting a first instruction to the second network node 16 instructing the second network node 16 to return a modified Session Description Protocol (SDP) answer to the WD 22 in response to a first media flow offer from the WD 22.

In some other embodiments, the first instruction further instructs the second network node 16 to terminate the first media flow offer.

In some embodiments, the instructing includes, if at least one of the requested application data channels are not allowed, transmitting a second instruction to the second network node 16. The second instruction instructs the second network node 16 to transmit a second media flow offer to a target network (e.g., target network and/or WD 22). The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value. The first reserved ID value indicates that the WD 22 is not allowed to use a first application data channel of the at least one of the requested application data channels.

In some other embodiments, the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value. The second reserved ID value indicates that the WD 22 is allowed to use a second application data channel of the at least one of the requested application data channels.

In some embodiments, the second instruction further instructs the second network node 16 to terminate the first media flow offer.

In some other embodiments, instructing the second network node 16 is further based on whether the WD 22 is roaming. In some embodiments, the first network node 16 includes a Data Channel Signaling Function (DCSF), and the second network node 16 includes an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

FIG. 6 is a flowchart of an example process in a second network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, radio interface 30 and/or communication interface 34. Network node 16 such as via processing circuitry 36 and/or processor 38 and/or radio interface 30 and/or communication interface 34 is configured to transmit (Block S120) a notification of one or more session events related to one or more application data channel requests. The notification includes a serving Public Land Mobile Network (PLMN) serving a wireless device. The notification is usable by the first network node 16 to apply a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN. The network node 16 is also configured to transmit (Block SI 22) an instruction from the first network node 16, where the instruction instructs the second network node 16 that at least one of one or more application data channels are not allowed for the wireless device. The instruction is based on the policy. In addition, network node 16 is configured to perform (Block S124) one or more actions based on the instruction.

In some embodiments, if all requested applications data channels are not allowed, the instruction includes a first instruction instructing the second network node 16 to return a modified Session Description Protocol (SDP) answer to the WD 22 in response to a first media flow offer from the WD 22. The one or more actions includes returning the modified SDP answer to the WD 22.

In some embodiments, if at least one of the requested application data channels are not allowed, the instruction includes a second instruction instructing the second network node 16 to transmit a second media flow offer to one or both of a target network and the WD 22. The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value. The first reserved ID value indicates that the WD 22 is not allowed to use a first application data channel of the at least one of the requested application data channels. The one or more actions includes transmitting the second media flow offer. In some other embodiments, the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value. The second reserved ID value indicates that the WD 22 is allowed to use a second application data channel of the at least one of the requested application data channels.

In some embodiments, the second instruction further instructs the second network node 16 to terminate the first media flow offer, and the one or more actions includes terminating the first media flow offer.

In some other embodiments, the instruction is further based on whether the WD 22 is roaming.

In some embodiments, the first network node 16 includes a Data Channel Signaling Function (DCSF), and the second network node 16 comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

FIG. 7 is a flowchart of an example process in a WD 22. One or more blocks described herein may be performed by one or more elements of WD 22 such as by one or more of processing circuitry 52 (including the WD management unit 26), processor 54, radio interface 48. WD 22 such as via processing circuitry 52 and/or processor 54 and/or radio interface 48 is configured to transmit (Block S126), to the second network node 16, a first media flow offer including information related to one or more application data channels requested by the WD 22 to one or both of transmit and receive data. The WD 22 is also configured to receive (Block S128), from the first network node 16 via the second network node 16, a response message indicating that the WD 22 is not allowed to use at least one of the one or more application data channels to one or both of transmit and receive data while being served by the PLMN. In addition, WD 22 is configured to perform (Block S130) one or more actions based on the response message.

In some embodiments, if the WD 22 is not allowed to use all applications data channels, the response message includes a modified Session Description Protocol (SDP) answer, and the first media flow offer is terminated.

In some other embodiments, if the WD 22 is not allowed to use at least one of the application data channels, the response message includes a second media flow offer (e.g., the response message and/or second media flow offer is sent to the WD 22, the WD 22 receives the response message and/or second media flow offer, etc.). The second media flow offer includes a first attribute that is changed to a first reserved stream identifier (ID) value, and the first reserved ID value indicates that the WD 22 is not allowed to use a first application data channel of the one or more application data channels. In some embodiments, the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value. The second reserved ID value indicates that the WD 22 is allowed to use a second application data channel of the at least one of the requested application data channels.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for determining exemptions for one or more applications over data channels such as IMS DC. In some embodiments, a DCSF may be referred to as a first network node 16 and an IMS AS may be referred to as a second network node 16.

In some embodiments:

• System 10 (and/or any of its components such as home network) has a list of applications data channel IDs that can be data exempt (i.e., IDs of applications that can be used for communication) when WD 22 is roaming and/or data off is active. In some embodiments, this list may be subject to continuous update. The list may also be dependent on roaming regions such as countries. A network node 16 such as a Data Channel Signaling Function (DCSF) may hold the list. The list may be operator controlled.

• Information about applications data channel exemption status when data off is active may be conveyed as metadata or any other format during downloads performed by WD 22, where the downloads may include available applications over the bootstrap channel. The list can also be sent via Device Management to WD 22. Any other options can also be used.

• The network or network node 16, e.g., the DCSF, enforces application data channel exemption status. The network node 16 (e.g., configured as the DCSF) may receive the WD location including serving Public Land Mobile Network (PLMN) during notification about WD DC (e.g., UE DC) session establishment. The network node 16 (e.g., configured as IMS AS) may receive this information via third party registration. • An offer answer model is used by the DCSF to enforce application data channel exemption status while roaming. A reserved stream ID, e.g., 9999, may be allocated to a requested application data channel that otherwise would not be allowed to be used by WD 22 while roaming, i.e., not data exempt, to convey to WD 22 that requested application data channel is non-exempt and the application is not allowed to be used while roaming.

• SDP may provide for fields that describe a call or session. The fields may be followed by “m” fields or lines. For example, an “m=” line (or “mline”) defines a separate media stream, and lines associated with that “m=” line may relate to a media stream, and another “m=” line may similarly define additional media.

• System 10 may include an originating network a terminating network, a first WD associated with the originating network (e.g., originating WD), and a second WD associated with the terminating network (e.g., terminating WD). The originating network may be an access network 12, core network 14, or any other network. The terminating network may be another access network 12, another core network 14, or any other network.

• The reserved stream ID is used by network node 16 (DCSF) of the network belonging to the requesting WD 22 to overwrite the original stream ID for the requested application data channel by WD 22. The reserved stream ID may be ignored by the terminating network when received in an SDP offer. The terminating network may include one or more network nodes 16 described herein, where the network nodes 16 may be configured to perform the terminating network functions such as ignoring the reserved stream ID. The reserved stream ID may be ignored, regardless of whether a single application is used per SDP mline is used or in case of multiplexed applications on a single SDP mline and where some application data channels are exempt while others are not used. The terminating network, however, may include the reserved stream ID in the returned SDP answer as received so that the originating WD can receive the reserved stream ID and/or apply the reserved stream ID to avoid using the application(s). The SDP answer may be referred to as a response message.

• Network node 16 (DCSF) may send a notification, via a push mechanism, over the bootstrap channel to notify the end user (e.g., WD 22) about the non- exemption status (or exemption status) of a requested application data channel.

As an example, an offer (e.g., Initial Offer, offer indication, indication, message, etc.), including three applications using multiplexing on a single SDP mline, may be as follows: m=application 12345 ... a=3gpp-req-app:appl sid=1234 ... a=3gpp-req-app:app2 sid=7890 ... a=3gpp-req-app:app3 sid=7654 ... a=dcmap:1234 a=dcmap:7890 a=dcmap:7620

The offer and associated attributes and/or parameters may be as described in 3GPP Technical Specification (TS) 26.114 VI 8.5.0. In some embodiments, the term “offer” refers to an SDP offer. Further, if WD 22 is not allowed to use the third application, then the returned SDP answer may change an attribute such as the “dcmap” attribute for such an application to some reserved stream number that is reserved to imply that the application cannot be used while roaming. In the following example, the reserved stream ID 9999 is used for that purpose.

Final SDP Answer: m=application 54231 ... a=3gpp-req-app:appl sid=1234 ... a=3gpp-req-app:app2 sid=7890 ... a=3gpp-req-app:app3 sid=7654 ... a=dcmap:1234 a=dcmap:7890 a=dcmap:9999

The example final SDP answer above may be the offer or indication that is modified by network node 16 (DCSF) of the requesting WD 22 and is received by the terminating network (and/or corresponding network nodes 16). The offer or indication (e.g., including a=dcmap:9999) may be returned in the final SDP answer (e.g., to the WD 22 or other network nodes 16). The use of a reserved value to indicate unavailability of an application while roaming can be used in conjunction with the generation of a notification over the bootstrap channel to state the same message. The reserved value may also be read by WD 22 and/or the subscriber using WD 22. WD 22 may be configured to enable or disable communication using the corresponding application.

In a similar example, e.g., with multiple SDP mlines, one SDP mline may be included per application. The offer (e.g., Initial Offer, offer indication, indication, message, etc.) may include three applications (represented by the terms appl, app2, app3) or any other quantity of applications: m=application 12345 ... a=3gpp-req-app:appl sid=1234 ... a=dcmap:1234 m=application 12346 ... a=3gpp-req-app:app2 sid=7890 ... a=dcmap:7890 m=application 12347 ... a=3gpp-req-app:app3 sid=7654 ... a=dcmap:7620

If WD 22 is not allowed to use the third application (i.e., app3), then the returned SDP answer may change an attribute such as the “dcmap” attribute for such an application to a reserved stream number that is reserved to imply that the application cannot be used while roaming. In the following example, the reserved stream ID 9999 is used for that purpose.

Answer: m=application 12345 ... a=3gpp-req-app:appl sid=1234 ... a=dcmap:1234 m=application 12346 ... a=3gpp-req-app:app2 sid=7890 ... a=dcmap:7890 m=application 12347 ... a=3gpp-req-app:app3 sid=7654 ... a=dcmap:9999

FIGS. 8 and 9 show an example call flow indicating how information can be conveyed and used. Although the steps of the example call flow are shown in an order, the embodiments are not limited as such, and the steps may be performed in any order and/or without requiring any particular step. In this nonlimiting example, it may be assumed that network node 16a (e.g., the DCSF) and/or network node 16b (e.g., IMS AS) received the WD 22 serving PLMN and/or related information from an IMS, e.g., during the notification. This may require an update to a service operation such as the Nimsas_SessionEventControl_Notify service operation (e.g., of step S206) to add the serving PLMN.

Update to Nimsas SessionEventControl Notify service operation (as described in 3GPP TS 23.228 V19.1.0)

Modifications to the procedure specified in the standard are shown herein using bold fonts.

AA.2.4.2.2 Nimsas_SessionEventControl_Notify service operation Service operation name: Nimsas_SessionEventControl_Notify

Description: This service operation enables IMS AS to notify consumers of session events related to a specific served IMS subscriber requesting use of IMS data channel media.

Inputs, Required: Session ID, Event ID, serving PLMN.

Session ID is the identity of the IMS session for which the event relates to. Event ID is the event triggered within the IMS session.

Serving PLMN can be the home PLMN or the PLMN where WD 22 (UE) is roaming

Inputs, Optional: Calling ID, Called ID, Session case, Event initiator, Media info list.

The steps shown in the call flow of FIGS. 8 and 9 may be as follows:

S200. IMS session and bootstrap data channel have been established by one or more of the WDs 22 and/or network nodes 16. Selected data channel application(s) have been downloaded to WD 22a (i.e., UE#1) and possibly WD 22b (i.e., UE#2).

S202. WD 22a (i.e., UE#1) sends a request (the SIP re-INVITE request) with an updated SDP to network node 16b (IMS AS), through originating network node 16c, 16d (P-CSCF and/or S-CSCF). The updated SDP contains (or may include) the Application Data Channel media information, e.g., according to 3GPP Technical Specification (TS) 26.114 V18.5.0. S204. The network node 16b (i.e., IMS AS) validates user subscription data to determine whether the media change request event should be notified to network node 16a (the DCSF).

S206. The network node 16b (i.e., IMS AS) notifies the network node 16a (i.e., DCSF), via a notification such as Nimsas_SessionEventControl_Notify (which may include MediaChangeRequest Event, Session ID, Event Direction, Event initiator, Media Info List, the serving PLMN) of the media change request event.

S208. After receiving the session event notification, network node 16a (i.e., DCSF) determines a policy (e.g., control policy) that specifies how to process the application data channel establishment request based on the related parameters (i.e. associated DC application binding information) in the notification and/or DCSF service specific policy. The first network node 16a (i.e., DCSF) may apply the policy based on the type of network (e.g., serving PLMN, home or visited domain). The policy may include information usable to determine what applications a subscriber or WD 22 is allowed (or not allowed) to use.

S210. Network node 16a (i.e., DCSF) determines that the added Application Data Channel media of or in the SDP offer takes DC Application Server as target endpoint and requires to anchor in the MF. Additionally, network node 16a (i.e., DCSF) determines if some of the requested Application Data Channels are not allowed while roaming based on the type of network (e.g., visited domain, visited PLMN, etc.). Network node 16a (i.e., DCSF) instructs the IMS AS that one or more of the requested Application Data Channels are not allowed while roaming based on the determination.

S212. Network node 16a (i.e., DCSF) invokes a service operation such as Nimsas_MediaControl service operation to instruct network node 16b (IMS AS) to do the following: a. If all requested applications data channels are not allowed then, first network node 16a (i.e., DCSF) sends a new instruction (e.g., “TerminateAndReturnModifiedMediaAnswer”) to network node 16b (the IMS AS) to return (e.g., immediately return) the SDP answer back to the WD 22, e.g., the update to the Nimsas MediaControl Mediainstruction service operation. As depicted in the updated service operation, network node 16a (DCSF) includes the SDP final answer to be returned to the WD 22. In some embodiments, the procedure may end at this step. b. If some of the requested applications are not allowed, the first network node 16a (i.e., DCSF) sends the new instruction (e.g., “TerminateAndOriginateModifiedMedia”) to network node 16b (the IMS AS) to perform one or more steps as described with respect to Nimsas MediaControl Mediainstruction service operation. The update to the Nimsas_MediaControl_MediaInstruction service operation is further described below. The first network node 16a (DCSF) includes the new offer (e.g., message, indication, etc.) to be sent by network node 16b (the IMS AS) to the target network (e.g., visited PLMN, another PLMN, or any other network). The new offer changes the a:dcmap attribute for not allowed application to the reserved stream ID value of “99999”.

In this example, one application (or application data channel) is allowed to progress (and/or communicate with other devices, networks, nodes, etc.), and another application had the dcmap converted to the reserved stream ID. Hence, the network node 16 (DCSF) invokes Nimsas_MediaControl service operation with the TerminateAndOriginateModifiedMedia” instruction to instruct network node 16 (IMS AS) to anchor the media flow of the originating WD 22 (UE) to Media Function (MF) for the allowed application. The instruction includes (or may also include) information to be consumed by the MF that the data channel media shall (or is to) be relayed via a communication interface such as the MDC2 interface, e.g., the MDC2 interface as specified in 3GPP TS 23.228 V19.1.0. The non-allowed application may have the a:dcmap attribute converted to the reserved stream ID number.

S214. Network node 16b (i.e., IMS AS) may request MF to reserve originating side media resource, where the MF allocates resources from originating MDC2 for use by network node 16a. Network node 16 (IMS AS) invokes or may invoke Nmf_MRM_Create(Eist of Media Termination Descriptors) service operation to instruct MF on application data channel establishment and data channel media resource reservation based on the DC media information received from the first network node 16a (i.e., DCSF).

S216. Network node 16b (i.e., IMS AS) notifies the MediaControl instruction control response to network node 16a (DCSF) (e.g., via a response).

S218. Network node 16a (i.e., DCSF) stores the media resource information and/or sends an application data channel establishment request (e.g., Person to Application (P2A) application data channel establishment request) including or which may the MDC2 media resource received from MF) to network node 16e (the DC Application Server) via DC3/DC4 (i.e., interface reference points).

S220. Network node 16e (DC Application Server) accepts the P2A application data channel establishment request, returning an MDC2 reserved media resource as answer and is prepared for WD 22a (UE#1) traffic through MDC2.

NOTE: Details on how DCSF communicates with the DC Application Server is out of scope of this Release.

S222. Network node 16a (i.e., DCSF) requests network node 16b (IMS AS) to update the MF resource with MDC2 media endpoint information of network node 16e (DC AS), e.g., via Nimsas_MediaControl_MediaInstruction (SessionlD, MedialnstructionSet).

S224. Network node 16b (i.e., IMS AS) updates the MF resource, e.g., requests MF to update originating side media resource.

S226. The second network node 16b (i.e., IMS AS) notifies the MediaControl instruction control response to network node 16a (DCSF), e.g., via Nimsas_MediaControl_MediaInstructionResponse (Result, MediaResourcelnformation) .

S228. Network node 16a (i.e., DCSF) replies to the notification received in step S226, e.g., via Nimsas_SessionEventControl_NotifyResponse.

S230-S232. Network node 16b (i.e., IMS AS) sends a message, such as the re- INVITE, with the SDP offer requested by network node 16a (DCSF) to the remote network side and WD 22b (UE#2), via network node 16d (the originating S-CSCF), which does not include application data channel request in the SDP for the application data channel. In case of multiplexed applications on a single SDP mline, the terminating network does not consider the application that has an a:dcmap attribute value of the reserved stream ID. However, this is still included in the final SDP response returned to the originating WD 22a (UE1) by the terminating network (e.g., access network 12 or any other network). The same applies for the case where a single SDP mline is used per application having the reserved stream ID value which is included in the final SIP 200 OK response.

S234-S238: WD 22b (UE#2_ and terminating network) returns a 200 OK response with SDP answer for audio/video. In case of multiplexed applications on a single SDP mline, the WD 22b (UE#2) includes the applications with a a:dcmap value set to the reserved stream ID in the final response returned to the originating WD 22a (UE#1). The same applies for the case where a single SDP mline is used per application having the reserved stream ID value which is included in the final SIP 200 OK response (i.e., step S250).

S240. Network node 16b (i.e., IMS AS) notifies network node 16a (DCSF) about the successful result of an event associated with the media change request, e.g., the MediaChangeRequest event. For example, the notification may be via Nimsas_SessionEventControl_Notify (mediaChangeSuccessEvent, SessionlD, MedialnfoList).

S242. The first network node 16a (i.e., DCSF) replies to the notification by transmitting a response such as Nimsas_SessionEventControl_Notify Response.

S244-S246. The second network node 16b (i.e., IMS AS) includes SDP answer for application data channels to WD 22a (UE#1) in 200 OK response and sends 200 OK response to network node 16d (S-CSCF) (e.g., by sending “200 OK (audio/video/bootstrap DC answer, SDP answer for application DC”)) and network node 16c (P-CSCF)(e.g., by sending “200 OK (audio/video/bootstrap DC answer, SDP answer for application DC)”).

S248. The originating network P-CSCF (i.e., at least network node 16c) executes Quality of Service (QoS) procedure for application data channel media based on the SDP answer information from the response (e.g., the 200 OK response).

S250. Network node 16c (P-CSCF) returns the 200 OK response (e.g., 200 OK (audio/video/bootstrap DC answer, SDP answer for application DC) to WD 22a (UE#1).

S252. WD 22a (UE#1) sends an acknowledgment (ACK) to the terminating network.

S254. The application data channel between WD 22a (UE#1) and network node 16e (DC Application Server) is established via network node 16f (MF). Network node 16f (MF) forwards data channel traffic between WD 22a (UE#1) and network node 16e (DC Application Server) based on MDC2 media point information received in steps S218 and S224.

Steps S200-S254 correspond to Steps 0-27 in 3GPP TS 23.228 V19.1.0.

Updates to the Nimsas MediaControl Mediainstruction service operation (as described in 3GPP TS 23.228 V19.1.0)

AA.2.4.3.2 Nimsas_MediaControI_MediaInstruction service operation Service operation name: Nimsas_MediaControI_MediaInstruction

Description: This operation provides instructions to a network node 16, such as the IMS AS, for all media flows a consumer wants to control based on its policies for the received IMS session event, and that may require resource reservation in the media resource, e.g. MF.

For the case when a specific media flow needs to be terminated in MF media resource (i.e., termination of a Data Channel media descriptor offered by one of the IMS subscribers) or originated by a network node 16, such as the MF, (i.e. origination of a data channel media descriptor to be offered towards one of the IMS subscribers), the consumer (e.g., WD 22) must or may provide a complete MF media specification including information required by MF to know how to terminate or originate the media flow.

Inputs, Required: Session ID, Media instruction set

Session ID specifies the IMS session for which the media instruction (e.g., Mediainstruction) operation applies. Media instruction set includes a set of instructions for each media flow to control.

Each instruction includes:

Media ID: used by the producer a network node 16, such as the IMS AS, and the consumer WD 22 or network node 16 for referencing purposes. The consumer reuses the media ID it received from network node 16 (the IMS AS) for referencing the same media. This field may be null for instructions related to originating new media.

Media resource capability: identify the Media Resource capabilities the Media instruction is intended for (e.g. DCMF, ARMF).

Media instruction: includes instructions to the producer (IMS AS) for handling the media. The following instructions are supported:

"TerminateMedia": Terminate the offered media descriptor of the WD 22 (UE) in the mediaResource, i.e., this media descriptor may not be exposed to the other WDs (UEs).

"OriginateMedia": Originate and offer a media descriptor from the mediaResource to the WD 22 (UE). The media ID representing the new media flow will or may be provided by producer a network node 16, such as the IMS AS, in the response.

"TerminateAndOriginateMedia": Terminate the offered media flow in the mediaResource from WD 22 (UE) and originate the same media flow from the mediaResource to the other WD 22 (UE), i.e., the offered media descriptor of the originating UE will or may be replaced by the mediaResource provided media descriptor, which is sent towards the other WD 22 (UE).

"TerminateAndReturnModifiedMediaAnswer": Terminate the offered media flow offer from WD 22 (UE) and return a modified final SDP answer to the received offer.” This instruction may be sent by a network node 16, such as the DCSF, in case all requested applications in the received offer are not allowed to be used while the subscriber is roaming.

NOTE: See optional input for the modified SDP information to be returned to WD 22(UE).

"TerminateAndOriginateModifiedMedia": Terminates the offered media flow in the mediaResource from WD 22 (UE) and originate a modified media flow from the mediaResource to the other WD 22 (UE), i.e., the offered media descriptor of the originating WD 22 (UE) may be replaced by the mediaResource provided media descriptor, which may be sent towards the other WD 22 (UE). This instruction may be sent by the DCSF in case some of requested application in the received offer are not allowed to be used while the subscriber is roaming. Hence, some applications may be allowed to progress (e.g., communicate with other devices or nodes).

NOTE: See optional input for the modified SDP information.

"UpdateMedia": Update a media flow of the mediaResource previously allocated by the instructions "TerminateMedia", "OriginateMedia" and " Terminate AndOriginateMedia"

"DeleteMedia": Delete a media flow of the mediaResource previously allocated by the instructions "TerminateMedia", "OriginateMedia" and "TerminateAndOriginateMedia" .

"RejectMedia": Remove an offered media flow, i.e., the offered media descriptor will or may be removed both from the offer sent to the remote WD 22 (UE) and from the answer returned to the initiator of the offer.

DC Media Specification: Description of additional media specification information needed for data channel media stream from application layer, which includes or may include: i. Media proxy configuration (Hypertext Transfer Protocol (HTTP) or User Datagram Protocol (UDP)) applicable to the media flow. ii. MDC1/MDC2 media endpoint address of the application layer. iii. Replacement HTTP Uniform Resource Locator (URL) per stream ID allocated by the application layer representing the application list (e.g., graphical user interface) provided to the IMS subscriber via the MDC1 interface. iv. Data Channel Mapping and Configuration information when originating/terminating data channel media flows on the Mb interface, e.g., the Mb interface as specified in 3GPP TS 23.228 V19.1.0. v. Augmented Reality (AR) Media Specification: Description of additional media specification information needed for AR communication services from application layer, which includes: 1. Media Processing Specification: It specifies how the media stream should be processed.

NOTE: DC Media Specification and AR Media Specification may be optional depending on the scenario and media type, where:

Inputs, Conditional: None.

Inputs, Optional: One of the following inputs is or may be included depending on the case:

- The modified SDP offer that must be or is or may be included by a network node 16, such as the IMS AS, in an outgoing re-INVITE towards a terminating network in case the instruction (e.g., “TerminateAndOriginateModifiedMedia" instruction) is sent to a network node 16, such as the IMS AS. The modified SDP offer includes the original SDP=mline of the received SDP offer representing application data channels. For applications that cannot be used, the a:dcmap attribute value is overwritten by the reserved stream number indicating that the application cannot be used while roaming. Allowed applications may not undergo any change and may be included as received in the original SDP offer. In some embodiments, a network node 16, such as IMS AS, may consider only allowed applications for MF handling. This may be applied for all requested application data channels whether a single SDP mline is used per application or when multiple applications are multiplexed on a single SDP mline.

- The final SDP answer that must be or is or may be included by a network node 16, such as the IMS AS, in a final SDP response to the originating WD 22 (UE) in case the “TerminateAndReturnModifiedMediaAnswer " instructions is sent to the network node 16, such as the IMS AS.

The final SDP answer may include the original SDP=mline of the received offer. For applications that cannot be used, the a:dcmap attribute value is overwritten by the reserved stream number indicating that the application cannot be used while roaming. In some embodiments, allowed applications do not undergo any change and are included as received in the original SDP offer. This may be applied for all requested application data channels whether a single SDP mline is used per application or when multiple applications are multiplexed on a single SDP mline, where: Outputs, Required: operation result indication.

Outputs, Optional: media resource information set:

This set includes or may include entries corresponding to each instruction in the received media instruction set. Each entry in the set includes the media ID (same as received or new for new media) and includes the media type according to SDP. Each entry may optionally contain or include DC Media Specification and/or AR Media Specification. The DC Media Specification shall or may exist only with media type "DC" and contains (or includes) additional media resource information, e.g., allocated media address for MDC2 interface when an offer must be provided to Data Channel Application Server. The AR Media Specification includes or may include media processing instruction for the MF on how to process the media.

The following is a nonlimiting list of example embodiments.

Embodiment Al. A method in a first network node configured to communicate with a second network node, the method comprising: receiving a notification of one or more session events related to one or more application data channel requests, the notification including a serving Public Land Mobile Network (PLMN) serving a wireless device; applying a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN; determining that: all requested application data channels of the one or more application data channels are not allowed for the wireless device; or at least one of the one or more application data channels are not allowed for the wireless device; and instructing the second network node based on the determination.

Embodiment A2. The method of Embodiment Al , wherein instructing includes: if all requested applications data channels are not allowed, transmitting a first instruction “TerminateAndReturnModifiedMediaAnswer” to the second network node to immediately return a Session Description Protocol (SDP) answer back to the wireless device.

Embodiment A3. The method of Embodiment Al , wherein instructing includes: if some of the requested application data channels are not allowed, transmitting a second instruction “TerminateAndOriginateModifiedMedia” to the second network node and including a new offer to be sent by the second network node towards a target network, the new offer changing an a:dcmap attribute for the not allowed application data channels to a reserved stream ID value of “99999” or any other reserved stream ID value.

Embodiment A4. The method of any one of Embodiments A1-A3, wherein the first network node comprises a Data Channel Signaling Function (DCSF) and the second network node comprises an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).

Embodiment Bl. A first network node configured to communicate with a second network node, the first network node configured to, and/or comprising a radio interface and/or communication interface and/or processing circuitry configured to perform one or more steps of Embodiments A1-A4.

Embodiment Cl. A method in a second network node configured to communicate with a first network node, the method comprising: transmitting a notification of one or more session events related to one or more application data channel requests, the notification including a serving Public Land Mobile Network (PLMN) serving a wireless device, the notification being usable by the first network node to apply a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN; and receiving an instruction from the first network node instructing the second network node based on whether all requested application data channels of the one or more application data channels are not allowed for the wireless device or at least one of the one or more application data channels are not allowed for the wireless device.

Embodiment C2. The method of Embodiment C 1 , wherein instructing includes: if all requested applications data channels are not allowed, receiving a first instruction “TerminateAndReturnModifiedMediaAnswer” from the first network node instructing the second network node to immediately return a Session Description Protocol (SDP) answer back to the wireless device.

Embodiment C3. The method of Embodiment C 1 , wherein instructing includes: if some of the requested application data channels are not allowed, receiving a second instruction “TerminateAndOriginateModifiedMedia” from the first network node, the second instruction including a new offer to be sent by the second network node towards a target network, the new offer changing an a:dcmap attribute for the not allowed application data channels to a reserved stream ID value of “99999” or any other reserved stream ID value.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method in a first network node (16) configured to communicate with a second network node (16), the method comprising: receiving (SI 12) a notification of one or more session events related to one or more application data channel requests, the notification including a serving Public Land Mobile Network, PLMN, serving a wireless device, WD (22); applying (SI 14) a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN; determining (SI 16) that at least one of one or more application data channels are not allowed for the WD (22) based on the applied policy; and instructing (SI 18) the second network node (16) based on the determination.

2. The method of Claim 1, wherein the instructing includes: if all requested applications data channels are not allowed, transmitting a first instruction to the second network node (16) instructing the second network node (16) to return a modified Session Description Protocol, SDP, answer to the WD (22) in response to a first media flow offer from the WD (22).

3. The method of Claim 2, wherein the first instruction further instructs the second network node (16) to terminate the first media flow offer.

4. The method of Claim 1, wherein the instructing includes: if at least one of the requested application data channels are not allowed, transmitting a second instruction to the second network node (16), the second instruction instructing the second network node (16) to transmit a second media flow offer to a target network, the second media flow offer including a first attribute that is changed to a first reserved stream identifier, ID, value, the first reserved ID value indicating that the WD (22) is not allowed to use a first application data channel of the at least one of the requested application data channels.

5. The method of Claim 4, wherein the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value, the second reserved ID value indicating that the WD (22) is allowed to use a second application data channel of the at least one of the requested application data channels.

6. The method of any one of Claims 4 and 5, wherein the second instruction further instructs the second network node (16) to terminate the first media flow offer.

7. The method of any one of Claims 1-6, wherein instructing the second network node (16) is further based on whether the WD (22) is roaming.

8. The method of any one of Claims 1-7, wherein the first network node (16) comprises a Data Channel Signaling Function, DCSF, and the second network node (16) comprises an Internet Protocol Multimedia Subsystem, IMS, Application Server, AS.

9. A first network node (16) configured to communicate with a second network node (16), the first network node (16) configured to perform one or more steps of any one of Claims 1-8.

10. A method in a second network node (16) configured to communicate with a first network node (16), the method comprising: transmitting (SI 20) a notification of one or more session events related to one or more application data channel requests, the notification including a serving Public Land Mobile Network, PLMN, serving a wireless device, the notification being usable by the first network node (16) to apply a policy associated with processing the one or more application data channel establishment requests based at least on the serving PLMN; receiving (SI 22) an instruction from the first network node (16), the instruction instructing the second network node (16) that at least one of one or more application data channels are not allowed for the wireless device, the instruction being based on the policy; and performing (SI 24) one or more actions based on the instruction.

11. The method of Claim 10, wherein if all requested applications data channels are not allowed, the instruction includes a first instruction instructing the second network node (16) to return a modified Session Description Protocol, SDP, answer to the WD (22) in response to a first media flow offer from the WD (22), and the one or more actions includes returning the modified SDP answer to the WD (22).

12. The method of Claim 11, wherein the one or more actions includes: terminating the first media flow offer in response to the first instruction.

13. The method of Claim 10, wherein if at least one of the requested application data channels are not allowed, the instruction includes a second instruction instructing the second network node (16) to transmit a second media flow offer to one or both of a target network and the WD (22), the second media flow offer including a first attribute that is changed to a first reserved stream identifier, ID, value, the first reserved ID value indicating that the WD (22) is not allowed to use a first application data channel of the at least one of the requested application data channels, the one or more actions including transmitting the second media flow offer.

14. The method of Claim 13, wherein the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value, the second reserved ID value indicating that the WD (22) is allowed to use a second application data channel of the at least one of the requested application data channels.

15. The method of any one of Claims 13 and 14, wherein the second instruction further instructs the second network node (16) to terminate the first media flow offer, and the one or more actions includes terminating the first media flow offer.

16. The method of any one of Claims 10-15, wherein the instruction is further based on whether the WD (22) is roaming.

17. The method of any one of Claims 10-16, wherein the first network node (16) comprises a Data Channel Signaling Function, DCSF, and the second network node (16) comprises an Internet Protocol Multimedia Subsystem, IMS, Application Server, AS.

18. A second network node (16) configured to communicate with a first network node (16), the second network node (16) configured to perform one or more steps of any one of Claims 10-17.

19. A method in a wireless device, WD, (22) configured to communicate with a first network node (16) and a second network node (16), the WD (22) being served by a Public Land Mobile Network, PLMN, the method comprising: transmitting (S126), to the second network node (16), a first media flow offer including information related to one or more application data channels requested by the WD (22) to one or both of transmit and receive data; receiving (S128), from the first network node (16) via the second network node (16), a response message indicating that the WD (22) is not allowed to use at least one of the one or more application data channels to one or both of transmit and receive data while being served by the PLMN; and performing (SI 30) one or more actions based on the response message.

20. The method of Claim 19, wherein if the WD (22) is not allowed to use all applications data channels, the response message includes a modified Session Description Protocol, SDP, answer and the first media flow offer is terminated.

21. The method of Claim 19, wherein if the WD (22) is not allowed to use at least one of the application data channels, the response message includes a second media flow offer, the second media flow offer including a first attribute that is changed to a first reserved stream identifier, ID, value, the first reserved ID value indicating that the WD (22) is not allowed to use a first application data channel of the one or more application data channels.

22. The method of Claim 21, wherein the second media flow offer further includes a second attribute that is unchanged and is a second reserved stream ID value, the second reserved ID value indicating that the WD (22) is allowed to use a second application data channel of the at least one of the requested application data channels.

23. The method of any one of Claims 21 and 22, wherein when the response message includes the second media flow offer, the first media flow offer is terminated.

24. The method of any one of Claims 19-23, wherein the first network node (16) comprises a Data Channel Signaling Function, DCSF, and the second network node (16) comprises an Internet Protocol Multimedia Subsystem, IMS, Application Server, AS.

25. A wireless device, WD, (22) configured to communicate with a first network node (16) and a second network node (16), the WD (22) being served by a Public Land Mobile Network, PLMN, the WD (22) being configured to perform one or more steps of any one of Claims 19-24.