[go: up one dir, main page]

WO2025158379A1 - Cadre pour exemption de données désactivées par application pour canal de données de sous-système multimédia de protocole internet - Google Patents

Cadre pour exemption de données désactivées par application pour canal de données de sous-système multimédia de protocole internet

Info

Publication number
WO2025158379A1
WO2025158379A1 PCT/IB2025/050814 IB2025050814W WO2025158379A1 WO 2025158379 A1 WO2025158379 A1 WO 2025158379A1 IB 2025050814 W IB2025050814 W IB 2025050814W WO 2025158379 A1 WO2025158379 A1 WO 2025158379A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
application data
allowed
media flow
instruction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IB2025/050814
Other languages
English (en)
Inventor
George Foti
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025158379A1 publication Critical patent/WO2025158379A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • the present disclosure relates to wireless communications, and in particular, to determining exemptions for Internet Protocol (IP) Multimedia Subsystem (IMS) Data Channel (IMS DC).
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • IMS DC Internet Protocol Data Channel
  • 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.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • 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.
  • NWs network nodes
  • WD mobile wireless devices
  • 6G Sixth Generation
  • 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.
  • 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.
  • a WD may support or enable communication services when the services are exempted from a predetermined condition or requirement.
  • 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.
  • 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.).
  • 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.
  • IDs application identifiers
  • a framework that enables communication on a per- application or per-application-ID or other parameter/attribute basis is provided.
  • a first application e.g., having a first application ID, or associated with a predetermined parameter or attribute, etc.
  • PLMN Public Land Mobile Network
  • 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.
  • a method in a first network node configured to communicate with a second network node 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.
  • PLMN Public Land Mobile Network
  • the method also includes instructing the second network node based on the determination.
  • 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.
  • SDP Session Description Protocol
  • the first instruction further instructs the second network node to terminate the first media flow offer.
  • 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.
  • ID first reserved stream identifier
  • 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.
  • the second instruction further instructs the second network node to terminate the first media flow offer.
  • instructing the second network node is further based on whether the WD is roaming.
  • the first network node includes a Data Channel Signaling Function (DCSF)
  • the second network node includes an Internet Protocol Multimedia Subsystem (IMS) Application Server (AS).
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Application Server
  • a first network node configured to communicate with a second network node.
  • 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.
  • a method in a second network node configured to communicate with a first network node 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.
  • PLMN Public Land Mobile Network
  • 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.
  • the method includes performing one or more actions based on the instruction.
  • 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.
  • SDP Session Description Protocol
  • the one or more actions includes terminating the first media flow offer in response to the first instruction.
  • 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.
  • ID 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.
  • 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.
  • 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.
  • the instruction is further based on whether the WD is roaming.
  • the first network node includes a Data Channel Signaling Function (DCSF)
  • DCSF Data Channel Signaling Function
  • AS Internet Protocol Multimedia Subsystem
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Application Server
  • a second network node configured to communicate with a first network node.
  • 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.
  • a method in a wireless device configured to communicate with a first network node and a second network node.
  • the WD is served by a Public Land Mobile Network (PLMN).
  • PLMN Public Land Mobile Network
  • 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.
  • the method includes performing one or more actions based on the response message.
  • the response message includes a modified Session Description Protocol (SDP) answer, and the first media flow offer is terminated.
  • SDP Session Description Protocol
  • 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.
  • ID reserved stream identifier
  • 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.
  • the response message when the response message includes the second media flow offer, the first media flow offer is terminated.
  • 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).
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Application Server
  • a wireless device configured to communicate with a first network node and a second network node.
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • 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.
  • 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.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • 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.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node 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 (DA).
  • BS base station
  • wireless device 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.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • LME Customer Premises Equipment
  • NB-IOT Narrowband loT
  • radio network node 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).
  • RNC evolved Node B
  • MCE Multi-ccll/multicast Coordination Entity
  • IAB node IAB node
  • relay node relay node
  • access point access point
  • radio access point radio access point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • 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.
  • 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.
  • a software application may be referred to as an application.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • radio interface 30 may be configured for setting up and maintaining at least a wireless/wired connection with other network nodes 16.
  • 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.
  • 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.
  • 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).
  • the memory 40 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • memory 56 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • 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.
  • SDP Session Description Protocol
  • 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”.
  • 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.
  • 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).
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Internet Protocol Multimedia Subsystem
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • SDP Session Description Protocol
  • 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”.
  • the reserved stream ID value of “99999” is only an example value, and any other reserve stream ID values may be used.
  • 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.
  • the first instruction further instructs the second network node 16 to terminate the first media flow offer.
  • 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.
  • ID first reserved stream identifier
  • 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.
  • the second instruction further instructs the second network node 16 to terminate the first media flow offer.
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • SDP Session Description Protocol
  • the one or more actions includes terminating the first media flow offer in response to the first instruction.
  • 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.
  • the instruction is further based on whether the WD 22 is roaming.
  • 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).
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Application Server
  • 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.
  • WD 22 is configured to perform (Block S130) one or more actions based on the response message.
  • 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.
  • 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.
  • the response message when the response message includes the second media flow offer, the first media flow offer is terminated.
  • 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.
  • DCSF Data Channel Signaling Function
  • the network node 16 e.g., configured as the DCSF
  • PLMN Public Land Mobile Network
  • the network node 16 e.g., configured as IMS AS
  • An offer answer model is used by the DCSF to enforce application data channel exemption status while roaming.
  • a reserved stream ID 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.
  • 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 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 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.
  • the offer and associated attributes and/or parameters may be as described in 3GPP Technical Specification (TS) 26.114 VI 8.5.0.
  • the term “offer” refers to an SDP offer.
  • 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.
  • 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 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.
  • 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.
  • the reserved stream ID 9999 is used for that purpose.
  • FIGS. 8 and 9 show an example call flow indicating how information can be conveyed and used.
  • 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.
  • network node 16a e.g., the DCSF
  • network node 16b e.g., IMS AS
  • 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.
  • Nimsas_SessionEventControl_Notify service operation e.g., of step S206
  • Nimsas_SessionEventControl_Notify service operation Service operation name: Nimsas_SessionEventControl_Notify
  • 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.
  • 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).
  • 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.
  • TS 3GPP Technical Specification
  • 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).
  • 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.
  • Nimsas_SessionEventControl_Notify which may include MediaChangeRequest Event, Session ID, Event Direction, Event initiator, Media Info List, the serving PLMN
  • network node 16a 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
  • the policy 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.
  • Network node 16a 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.
  • DCSF the type of network
  • 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.
  • a new instruction e.g., “TerminateAndReturnModifiedMediaAnswer”
  • network node 16a includes the SDP final answer to be returned to the WD 22.
  • the procedure may end at this step.
  • the first network node 16a i.e., DCSF
  • the new instruction e.g., “TerminateAndOriginateModifiedMedia”
  • network node 16b the IMS AS
  • the update to the Nimsas_MediaControl_MediaInstruction service operation is further described below.
  • the first network node 16a 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”.
  • 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.
  • DCSF network node 16
  • IMS AS TerminateAndOriginateModifiedMedia
  • 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.
  • Network node 16b 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).
  • Network node 16b i.e., IMS AS
  • DCSF MediaControl instruction control response to network node 16a
  • Network node 16a i.e., DCSF
  • 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).
  • P2A Person to Application
  • DC3/DC4 i.e., interface reference points
  • 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.
  • Network node 16a i.e., DCSF
  • IMS AS network node 16b
  • MDC2 media endpoint information of network node 16e DC AS
  • Nimsas_MediaControl_MediaInstruction SessionlD, MedialnstructionSet
  • Network node 16b updates the MF resource, e.g., requests MF to update originating side media resource.
  • 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) .
  • Network node 16a i.e., DCSF
  • Network node 16b i.e., IMS AS
  • 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 terminating network e.g., access network 12 or any other network.
  • S234-S238 WD 22b (UE#2_ and terminating network) returns a 200 OK response with SDP answer for audio/video.
  • 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).
  • 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).
  • 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.
  • the notification may be via Nimsas_SessionEventControl_Notify (mediaChangeSuccessEvent, SessionlD, MedialnfoList).
  • the first network node 16a i.e., DCSF
  • replies to the notification by transmitting a response such as Nimsas_SessionEventControl_Notify Response.
  • 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)”).
  • S-CSCF network node 16d
  • P-CSCF network node 16c
  • 200 OK audio/video/bootstrap DC answer, SDP answer for application DC
  • the originating network P-CSCF i.e., at least network node 16c
  • QoS Quality of Service
  • Network node 16c returns the 200 OK response (e.g., 200 OK (audio/video/bootstrap DC answer, SDP answer for application DC) to WD 22a (UE#1).
  • 200 OK audio/video/bootstrap DC answer, SDP answer for application DC
  • WD 22a (UE#1) sends an acknowledgment (ACK) to the terminating network.
  • 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.
  • 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.
  • MF media resource i.e., termination of a Data Channel media descriptor offered by one of the IMS subscribers
  • a network node 16 such as the MF
  • the consumer e.g., WD 22
  • the consumer must or may provide a complete MF media specification including information required by MF to know how to terminate or originate the media flow.
  • 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.
  • IMS AS the producer for handling the media.
  • the following instructions are supported:
  • “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.
  • 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.
  • 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).
  • 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.
  • AR Augmented Reality
  • 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.
  • 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 a:dcmap attribute value is overwritten by the reserved stream number indicating that the application cannot be used while roaming.
  • 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.
  • 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.
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • SDP Session Description Protocol
  • 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).
  • DCSF Data Channel Signaling Function
  • IMS Internet Protocol Multimedia Subsystem
  • AS Application Server
  • 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.
  • PLMN Public Land Mobile Network
  • 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.
  • SDP Session Description Protocol
  • 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.
  • 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.
  • 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.
  • 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++.
  • 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.
  • 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).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé, un système et un appareil sont divulgués. L'invention concerne un procédé dans un premier nœud de réseau conçu pour communiquer avec un second nœud de réseau. Le procédé consiste à : recevoir une notification d'un ou de plusieurs événements de session associés à une ou plusieurs demandes de canal de données d'application, la notification comprenant un réseau mobile terrestre public de desserte (PLMN) desservant un dispositif sans fil (WD) ; appliquer une politique associée au traitement de la ou des demandes d'établissement de canal de données d'application sur la base au moins du PLMN de desserte ; et déterminer qu'au moins un du ou des canaux de données d'application ne sont pas autorisés pour le WD sur la base de la politique appliquée. Le procédé consiste également à donner des instructions au second nœud de réseau sur la base de la détermination.
PCT/IB2025/050814 2024-01-26 2025-01-24 Cadre pour exemption de données désactivées par application pour canal de données de sous-système multimédia de protocole internet Pending WO2025158379A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463625573P 2024-01-26 2024-01-26
US63/625,573 2024-01-26

Publications (1)

Publication Number Publication Date
WO2025158379A1 true WO2025158379A1 (fr) 2025-07-31

Family

ID=94605453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/050814 Pending WO2025158379A1 (fr) 2024-01-26 2025-01-24 Cadre pour exemption de données désactivées par application pour canal de données de sous-système multimédia de protocole internet

Country Status (1)

Country Link
WO (1) WO2025158379A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230071408A1 (en) * 2020-02-13 2023-03-09 Lg Electronics Inc. Communication related to multi access pdu session
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230071408A1 (en) * 2020-02-13 2023-03-09 Lg Electronics Inc. Communication related to multi access pdu session
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质

Similar Documents

Publication Publication Date Title
US12425480B2 (en) Access network with service-based interfaces
CN110351777B (zh) 指示业务分流的方法和装置
CN113767672B (zh) 用于在插入中间会话管理功能之后管理无线通信的移动通信核心网络装置及方法
US11729599B2 (en) Communication system
WO2022015595A1 (fr) Relation spatiale par défaut pour pucch et srs avec multi-trp
US12426117B2 (en) Apparatus and method of a mobile terminating user equipment connecting to a fallback network
WO2021063657A1 (fr) Fourniture d'informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées
WO2020088594A1 (fr) Procédé et appareil de transmission de données
US12368761B2 (en) First IMS node, first core network node, second IMS node, and methods performed therein
WO2023143212A1 (fr) Procédé et appareil de communication
CN112005580B (zh) 边缘服务连续性
US11902393B2 (en) Proxy-call session control function (P-CSCF) to P-CSCF communication
WO2025158379A1 (fr) Cadre pour exemption de données désactivées par application pour canal de données de sous-système multimédia de protocole internet
EP4573735A1 (fr) Noeuds de sous-système multimédia de protocole internet (ims), noeuds de réseau central et procédés pour sélectionner une instance de noeud ims de desserte dans un réseau de communications
WO2022238910A1 (fr) Cadriciel pour une gestion dynamique de ressources dans une tranche partagée
WO2024011555A1 (fr) Nœud de réseau central, nœuds de sous-système multimédia de protocole internet (ims) et procédés associés dans un réseau de communication
WO2024011568A1 (fr) Nœuds de sous-système multimédia de protocole internet (ims), nœud de réseau central et procédés associés, dans un réseau de communications
EP4320850B1 (fr) Découverte dynamique de passerelle multimédia dans ims
US20240276183A1 (en) Methods for handling a service for a communications device and network nodes implementing the method in a communications network
WO2024012689A1 (fr) Fonction distributrice, fonction localisatrice et procédés dans un réseau de communication
WO2023035229A1 (fr) Nœuds de réseau, nœud ims et procédés réalisés dans un réseau de communication
US20240275829A1 (en) Methods for upgrading a first data session for a first media type to handle a second media type, network nodes and a communication device implementing the methods in a communications network
EP3991395A1 (fr) Noeud serveur, assistant numérique et procédés de gestion de la confidentialité associés à des appels entrants dans un réseau de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25705325

Country of ref document: EP

Kind code of ref document: A1