EP4413778A1 - Appareil, procédés et programmes informatiques - Google Patents

Appareil, procédés et programmes informatiques

Info

Publication number
EP4413778A1
EP4413778A1 EP21786962.7A EP21786962A EP4413778A1 EP 4413778 A1 EP4413778 A1 EP 4413778A1 EP 21786962 A EP21786962 A EP 21786962A EP 4413778 A1 EP4413778 A1 EP 4413778A1
Authority
EP
European Patent Office
Prior art keywords
function
identifier
application
application function
signalling
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
EP21786962.7A
Other languages
German (de)
English (en)
Inventor
Dinh Thai Bui
Shubhranshu Singh
Klaus Hoffmann
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.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
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 Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of EP4413778A1 publication Critical patent/EP4413778A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
    • H04L47/785—Distributed allocation of resources, e.g. bandwidth brokers among multiple network domains, e.g. multilateral agreements
    • H04L47/786—Mapping reservation between domains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • the present disclosure relates to apparatus, methods, and computer programs, and in particular but not exclusively to apparatus, methods and computer programs for network apparatuses.
  • a communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, access nodes and/or other nodes by providing carriers between the various entities involved in the communications path.
  • a communication system can be provided for example by means of a communication network and one or more compatible communication devices.
  • the communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and/or content data and so on.
  • Content may be multicast or unicast to communication devices.
  • a user can access the communication system by means of an appropriate communication device or terminal.
  • a communication device of a user is often referred to as user equipment (UE) or user device.
  • the communication device may access a carrier provided by an access node and transmit and/or receive communications on the carrier.
  • the communication system and associated devices typically operate in accordance with a required standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined.
  • UTRAN 3G radio
  • Another example of an architecture that is known is the long-term evolution (LTE) or the Universal Mobile Telecommunications System (UMTS) radioaccess technology.
  • LTE long-term evolution
  • UMTS Universal Mobile Telecommunications System
  • Another example communication system is so called 5G system that allows user equipment (UE) or user device to contact a 5G core via e.g. new radio (NR) access technology or via other access technology such as Untrusted access to 5GC or wireline access technology.
  • NR new radio
  • an apparatus for a network function located in a first domain comprising means for: determining that a user plane path currently used for a session is to be reconfigured; signalling, to a first application function located in a second domain, a first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining; and receiving signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function may comprise signalling the first application function via a network exposure function.
  • the apparatus may comprise means for: exchanging signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signalling the identifier of the at least one candidate application function to the first application function.
  • the apparatus may comprise means for: exchanging signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and selecting the second application function using the obtained analytics information.
  • the apparatus may comprise means for: receiving an indication that the first and second application functions have no established trust between them; and generating the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the apparatus may comprise means for: signalling a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus may comprise means for: signalling at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured. [0014] The signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • the network function may be a session management function.
  • an apparatus for a first application function located in a second domain comprising means for: receiving signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured; determining whether the first application function has an established trust with the second application function; and signalling the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the apparatus may comprise means for, when the first application function has an established trust with the second application function: receiving signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signalling the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the means for signalling the first identifier to the second application function may comprise means for exchanging context information for the session with the second application function.
  • the apparatus may comprise means for, when the first application function does not have an established trust with the second application function: receiving, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchanging context information for the session with the second application function via the proxy function using the third identifier.
  • the second identifier may be received from a network function located in a first domain, and the exchanging may be performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • an apparatus for a proxy function comprising means for: establishing a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions; receiving at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured; and exchanging signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • an apparatus for a network repository function comprising means for: storing, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function; receiving, from a first network function, a request for an identifier of an application function for serving a subscriber; selecting at least one first application function from the set of application functions; and providing the first network function with an identifier of the at least one first application function to the first network function.
  • Said means for providing may comprise means for providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • an apparatus for a network analytics function comprising means for: receiving from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function; and providing said information to said first network function.
  • an apparatus for a network function located in a first domain comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: determine that a user plane path currently used for a session is to be reconfigured; signal, to a first application function located in a second domain, a first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining; and receive signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function may comprise signalling the first application function via a network exposure function.
  • the apparatus may be caused to: exchange signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signal the identifier of the at least one candidate application function to the first application function.
  • the apparatus may be caused to: exchange signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and select the second application function using the obtained analytics information.
  • the apparatus may be caused to: receive an indication that the first and second application functions have no established trust between them; and generate the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the apparatus may be caused to: signal a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus may be caused to: signal at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • the network function may be a session management function.
  • an apparatus for a first application function located in a second domain comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: receive signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured; determine whether the first application function has an established trust with the second application function; and signal the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the apparatus may be caused to, when the first application function has an established trust with the second application function: receive signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signal the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the signalling the first identifier to the second application function may comprise exchanging context information for the session with the second application function.
  • the apparatus may be caused to, when the first application function does not have an established trust with the second application function: receive, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchange context information for the session with the second application function via the proxy function using the third identifier.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • an apparatus for a second application function located in a third domain comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: receive one of a first identifier and a second identifier, the first identifier authorising a first application function located in a second domain to update routing information for a reconfigured user plane path, and the second identifier identifying a proxy function having an established trust between the first and second application functions; exchange, with the first application function, context information for a session with the first application in the second domain using the first identifier or the second identifier; and signal a network function located in a first domain updated routing information for the reconfigured user plane path.
  • the first identifier may be received from the first application function, and the exchanging is performed using direct communications between the first and second application functions.
  • the second identifier may be received from a network function located in a first domain, and the exchanging may be performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • an apparatus for a proxy function comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: establish a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions; receive at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured; and exchange signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • an apparatus for a network repository function comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: store, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function; receive, from a first network function, a request for an identifier of an application function for serving a subscriber; select at least one first application function from the set of application functions; and provide the first network function with an identifier of the at least one first application function to the first network function.
  • Said providing may comprise providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • an apparatus for a network analytics function comprising: at least one processor; and at least one memory comprising code that, when executed by the at least one processor, causes the apparatus to: receive from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function; and provide said information to said first network function.
  • a method for an apparatus for a network function located in a first domain comprising: determining that a user plane path currently used for a session is to be reconfigured; signalling, to a first application function located in a second domain, a first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining; and receiving signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function may comprise signalling the first application function via a network exposure function.
  • the method may comprise: exchanging signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signalling the identifier of the at least one candidate application function to the first application function.
  • the method may comprise: exchanging signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and selecting the second application function using the obtained analytics information.
  • the method may comprise: receiving an indication that the first and second application functions have no established trust between them; and generating the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the method may comprise: signalling a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the method may comprise: signalling at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • the network function may be a session management function.
  • a method for an apparatus for a first application function located in a second domain comprising: receiving signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured; determining whether the first application function has an established trust with the second application function; and signalling the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the method may comprise, when the first application function has an established trust with the second application function: receiving signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signalling the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the signalling the first identifier to the second application function may comprise exchanging context information for the session with the second application function.
  • the method may comprise, when the first application function does not have an established trust with the second application function: receiving, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchanging context information for the session with the second application function via the proxy function using the third identifier.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • a method for an apparatus for a second application function located in a third domain comprising: receiving one of a first identifier and a second identifier, the first identifier authorising a first application function located in a second domain to update routing information for a reconfigured user plane path, and the second identifier identifying a proxy function having an established trust between the first and second application functions; exchanging, with the first application function, context information for a session with the first application in the second domain using the first identifier or the second identifier; and signalling a network function located in a first domain updated routing information for the reconfigured user plane path.
  • the first identifier may be received from the first application function, and the exchanging is performed using direct communications between the first and second application functions.
  • the second identifier may be received from a network function located in a first domain, and the exchanging may be performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • a method for an apparatus for a proxy function comprising: establishing a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions; receiving at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured; and exchanging signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • a method for an apparatus for a network repository function comprising: storing, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function; receiving, from a first network function, a request for an identifier of an application function for serving a subscriber; selecting at least one first application function from the set of application functions; and providing the first network function with an identifier of the at least one first application function to the first network function.
  • Said providing may comprise providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • a method for an apparatus for a network analytics function comprising: receiving from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function; and providing said information to said first network function.
  • an apparatus for a network function located in a first domain comprising: determining circuitry for determining that a user plane path currently used for a session is to be reconfigured; signalling circuitry for signalling, to a first application function located in a second domain, a first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining; and receiving circuitry for receiving signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function may comprise signalling the first application function via a network exposure function.
  • the apparatus may comprise: exchanging circuitry for exchanging signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signalling circuitry for signalling the identifier of the at least one candidate application function to the first application function.
  • the apparatus may comprise: exchanging circuitry for exchanging signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and selecting circuitry for selecting the second application function using the obtained analytics information.
  • the apparatus may comprise: receiving circuitry for receiving an indication that the first and second application functions have no established trust between them; and generating circuitry for generating the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the apparatus may comprise: signalling circuitry for signalling a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus may comprise: signalling circuitry for signalling at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • the network function may be a session management function.
  • an apparatus for a first application function located in a second domain comprising: receiving circuitry for receiving signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured; determining circuitry for determining whether the first application function has an established trust with the second application function; and signalling circuitry for signalling the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the apparatus may comprise circuitry for, when the first application function has an established trust with the second application function: receiving signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signalling the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the signalling circuitry for signalling the first identifier to the second application function may comprise exchanging circuitry for exchanging context information for the session with the second application function.
  • the apparatus may comprise circuitry for, when the first application function does not have an established trust with the second application function: receiving, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchanging context information for the session with the second application function via the proxy function using the third identifier.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • an apparatus for a second application function located in a third domain comprising: receiving circuitry for receiving one of a first identifier and a second identifier, the first identifier authorising a first application function located in a second domain to update routing information for a reconfigured user plane path, and the second identifier identifying a proxy function having an established trust between the first and second application functions; exchanging circuitry for exchanging, with the first application function, context information for a session with the first application in the second domain using the first identifier or the second identifier; and signalling circuitry for signalling a network function located in a first domain updated routing information for the reconfigured user plane path.
  • the first identifier may be received from the first application function, and the exchanging is performed using direct communications between the first and second application functions.
  • the second identifier may be received from a network function located in a first domain, and the exchanging may be performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • an apparatus for a proxy function comprising: establishing circuitry for establishing a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions; receiving circuitry for receiving at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured; and exchanging circuitry for exchanging signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • an apparatus for a network repository function comprising: storing circuitry for storing, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function; receiving circuitry for receiving, from a first network function, a request for an identifier of an application function for serving a subscriber; selecting circuitry for selecting at least one first application function from the set of application functions; and providing circuitry for providing the first network function with an identifier of the at least one first application function to the first network function.
  • Said providing circuitry for providing may comprise providing circuitry for providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • an apparatus for a network analytics function comprising: receiving circuitry for receiving from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function; and providing circuitry for providing said information to said first network function.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a network function located in a first domain to perform at least the following: determine that a user plane path currently used for a session is to be reconfigured; signal, to a first application function located in a second domain, a first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining; and receive signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function may comprise signalling the first application function via a network exposure function.
  • the apparatus may be caused to: exchange signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signal the identifier of the at least one candidate application function to the first application function.
  • the apparatus may be caused to: exchange signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and select the second application function using the obtained analytics information.
  • the apparatus may be caused to: receive an indication that the first and second application functions have no established trust between them; and generate the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the apparatus may be caused to: signal a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus may be caused to: signal at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • the network function may be a session management function.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a first application function located in a second domain to perform at least the following: receive signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured; determine whether the first application function has an established trust with the second application function; and signal the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the apparatus may be caused to, when the first application function has an established trust with the second application function: receive signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signal the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the signalling the first identifier to the second application function may comprise exchanging context information for the session with the second application function.
  • the apparatus may be caused to, when the first application function does not have an established trust with the second application function: receive, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchange context information for the session with the second application function via the proxy function using the third identifier.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a second application function located in a third domain to perform at least the following: receive one of a first identifier and a second identifier, the first identifier authorising a first application function located in a second domain to update routing information for a reconfigured user plane path, and the second identifier identifying a proxy function having an established trust between the first and second application functions; exchange, with the first application function, context information for a session with the first application in the second domain using the first identifier or the second identifier; and signal a network function located in a first domain updated routing information for the reconfigured user plane path.
  • the first identifier may be received from the first application function, and the exchanging is performed using direct communications between the first and second application functions.
  • the second identifier may be received from a network function located in a first domain, and the exchanging may be performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a proxy function to perform at least the following: establish a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions; receive at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured; and exchange signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a network repository function to perform at least the following: store, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function; receive, from a first network function, a request for an identifier of an application function for serving a subscriber; select at least one first application function from the set of application functions; and provide the first network function with an identifier of the at least one first application function to the first network function.
  • Said providing may comprise providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • non-transitory computer readable medium comprising program instructions for causing an apparatus for a network analytics function to perform at least the following: receive from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function; and provide said information to said first network function.
  • a computer program product stored on a medium that may cause an apparatus to perform any method as described herein.
  • an electronic device that may comprise apparatus as described herein.
  • a chipset that may comprise an apparatus as described herein.
  • Figures 1A and 1 B show a schematic representation of a 5G system
  • Figure 2 shows a schematic representation of a network apparatus
  • Figure 3 shows a schematic representation of a user equipment
  • Figure 4 shows a schematic representation of a non-volatile memory medium storing instructions which when executed by a processor allow a processor to perform one or more of the steps of the methods of some examples;
  • Figure 5 shows a schematic representation of a network
  • Figure 6 shows a schematic representation of different entities located in different domains
  • FIG. 7 to 11 illustrate example signalling
  • Figures 12 to 17 are flow chart illustrating potential operations that may be performed by apparatus described herein.
  • FIG. 1A shows a schematic representation of a 5G system (5GS) 100.
  • the 5GS may comprise a user equipment (UE) 102 (which may also be referred to as a communication device or a terminal), a 5G access network (AN) (which may be a 5G Radio Access Network (RAN) or any other type of 5G AN such as a Non-3GPP Interworking Function (N3IWF) /a Trusted Non3GPP Gateway Function (TNGF) for Untrusted / Trusted Non-3GPP access or Wireline Access Gateway Function (W-AGF) for Wireline access) 104, a 5G core (5GC) 106, one or more application functions (AF) 108 and one or more data networks (DN) 110.
  • UE user equipment
  • AN which may also be referred to as a communication device or a terminal
  • AN which may be a 5G Radio Access Network (RAN) or any other type of 5G AN such as a Non-3GPP Interworking Function (N3
  • the 5G RAN may comprise one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) unit functions.
  • the RAN may comprise one or more access nodes.
  • the 5GC 106 may comprise one or more Access and Mobility Management Functions (AMF) 112, one or more Session Management Functions (SMF) 114, one or more authentication server functions (AUSF) 116, one or more unified data management (UDM) functions 118, one or more user plane functions (UPF) 120, one or more unified data repository (UDR) functions 122, one or more network repository functions (NRF) 128, and/or one or more network exposure functions (NEF) 124.
  • the role of an NEF is to provide secure exposure of network services (e.g. voice, data connectivity, charging, subscriber data, etc.) towards a 3rd party.
  • NRF 128 is not depicted with its interfaces, it is understood that this is for clarity reasons and that NRF 128 may have a plurality of interfaces with other network functions.
  • the 5GC 106 also comprises a network data analytics function (NWDAF) 126.
  • NWDAF network data analytics function
  • the NWDAF is responsible for providing network analytics information upon request from one or more network functions or apparatus within the network.
  • Network functions can also subscribe to the NWDAF 126 to receive information therefrom.
  • the NWDAF 126 is also configured to receive and store network information from one or more network functions or apparatus within the network.
  • the data collection by the NWDAF 126 may be performed based on at least one subscription to the events provided by the at least one network function.
  • the network may further comprise a management data analytics service (MDAS).
  • MDAS may provide data analytics of different network related parameters including for example load level and/or resource utilisation.
  • the MDAS for a network function (NF) can collect the NF’s load related performance data, e.g., resource usage status of the NF.
  • the analysis of the collected data may provide forecast of resource usage information in a predefined future time. This analysis may also recommend appropriate actions e.g., scaling of resources, admission control, load balancing of traffic, etc.
  • Figure 1 B shows a schematic representation of a 5GC 106’ represented in current 3GPP specifications.
  • Figure 1 B shows a UPF 120’ connected to an SMF 114’ over an N4 interface.
  • the SMF 114’ is connected to each of a UDR 122’, an NEF 124’, an NWDAF 126’, an AF 108’, a Policy Control Function (PCF) 130’, an AMF 112’, and a Charging function 132’ over an interconnect medium that also connects these network functions to each other.
  • PCF Policy Control Function
  • 3GPP refers to a group of organizations that develop and release different standardized communication protocols. 3GPP is currently developing and publishing documents related to Release 16, relating to 5G technology, with Release 17 currently being scheduled for 2022.
  • an application function (AF) is configured to provide at least one service to a subscriber during a session managed by an SMF
  • the AF and SMF may exchange signalling to maintain an efficient user plane path. This is particularly useful when there is a change in AF from a source AF to a target AF.
  • the following considers the case of source and target AFs being in different domains, such as in different edge computing domains. More particularly, the following considers the interactions between a core network architecture (e.g. a 5G core) and edge computing domains when a switch is made from a source AF located in a first edge computing domain to a target AF located in a second edge computing domain while a service is being provided to a user equipment by the source AF during a session.
  • a core network architecture e.g. a 5G core
  • Figure 6 provides a schematic overview of the network architecture that may be involved when source and target application functions are located in different edge computing domains.
  • an Edge computing domain may be considered to be an edge computing infrastructure (e.g. an infrastructure that provides network functions, compute functions, and storage functions) under the responsibility of an infrastructure administration having its own business goals.
  • An example of an edge computing domain is an operator’s complete edge computing infrastructure.
  • An edge computing domain could be part of an operator’s edge computing infrastructure managed by a business entity of the operator.
  • Figure 6 shows a first domain 601 comprising a plurality of domain entities.
  • the first domain may be, for example, a 3GPP communication domain.
  • the example domain entities shown comprise a first radio access network 602 connected to a first plurality of user plane functions 603, 604 connected in series, a second radio access network 605 connected to a second plurality of user plane functions 606, 607 connected in series.
  • a domain may be considered to be a cloud or communication infrastructure under the administration of an operator with its own business goals.
  • the first radio access network 602 and the first plurality of user plane functions 603, 604 are associated with a first access and mobility function 608, a first session management function 609, and a first network edge function/policy control function 610.
  • the second radio access network 605 and the second plurality of user plane functions 606, 607 are associated with a second access and mobility function 611 , a second session management function 612, and a second network edge function/policy control function 613.
  • FIG. 6 further illustrates a second domain 614.
  • This second domain may be, for example, a first edge computing domain.
  • the second domain 614 comprises an administrative controller 615 (which may be, for example, a Multi-access Edge Computing Orchestrator/ Multi-access Edge Computing Manager/Multi-access Edge Platform).
  • the administrative controller 615 may be configured to receive signalling from the first network edge function/policy control function 610 and a Multi-access Edge Computing (MEC) Host 616 that is configured to receive user data traffic from the first plurality of user plane functions 603, 604.
  • MEC Multi-access Edge Computing
  • FIG. 6 further illustrates a third domain 617.
  • This third domain may be, for example, a second edge computing domain.
  • the third domain 617 comprises an administrative controller 619 (which may be, for example, an MEC Orchestrator/MEC Manager) configured to receive signalling from the second network edge function/policy control function 613 and an MEC Host 618 that is configured to receive user data traffic from the second plurality of user plane functions 606, 607.
  • an administrative controller 619 which may be, for example, an MEC Orchestrator/MEC Manager
  • MEC Host 618 that is configured to receive user data traffic from the second plurality of user plane functions 606, 607.
  • Figure 6 further illustrates a UE that may connect to the first domain 601 via at least one of the first radio access network 602, the second radio access network 605, the first access and mobility function 608, and the second access and mobility function 611 .
  • This connection may not be simultaneous, but rather reflect a mobility of the UE as it moves from accessing a service via one of the first and second radio access networks to accessing a service via the other one of the first and second radio access networks.
  • Some of the communication connections between these domain entities are illustrated by lines therebetween.
  • the path switch may mean that the service being provided to the user equipment is better provided through the third domain 617 than from second domain 614. This means that it would be useful to facilitate context exchange between entities located in the first and second edge computing domains.
  • This change from service provision via a first edge computing domain to service provision via a second edge computing domain is also referred to as edge application server (EAS) relocation with an application function.
  • EAS edge application server
  • 3GPP TS 23.502 V17.1.0 provides a procedure to deal with Edge Application Server relocation with an application function.
  • Figure 7 shows signalling between a UPF 701 , an SMF 702, a PCF 703, an NEF 704, and an AF 705.
  • the SMF 702 determines that a criteria for causing a handover from a first application function to a second application function has been met.
  • the SMF 702 signals the NEF 704. This signalling may be an indication that the criteria has been met.
  • the SMF may signal the NEF 704 at 7002 in response to a determination that the AF has requested an “early notification” of the criteria being met. This may be defined in a subscription of the AF to be informed about the criteria being met.
  • An early notification relates to a notification that is sent prior to any protocol data unit (PDU) session reconfiguration being performed.
  • the signalling of 7002 may comprise the target Data Network Access Identifier (DNAI) of the PDU Session by invoking Nsmf_EventExposure_Notify service operation.
  • the DNAI is an operator defined identifier of a user plane access to one or more data networks (also referred to herein as domains) where applications are deployed.
  • the NEF 704 signals the AF705.
  • This signalling may be an indication that network traffic is having an adverse effect on signalling.
  • This signalling may be performed after the NEF 704 performs information mapping (e.g. of an AF Transaction Internal ID to an AF Transaction ID, of a permanent subscriber identifier (e.g. SUPI) to a Generic Public Subscription Identifier (GPSI), etc.) and trigger an appropriate message (e.g. the Nnef_Trafficlnfluence_Notify message in current 3GPP terminology) to be sent to the source application function 705.
  • information mapping e.g. of an AF Transaction Internal ID to an AF Transaction ID, of a permanent subscriber identifier (e.g. SUPI) to a Generic Public Subscription Identifier (GPSI), etc.
  • GPSI Generic Public Subscription Identifier
  • the SMF 702 signals the AF 705.
  • This signalling may be an indication that the criteria has been met.
  • This signalling may be the early direct notification to which the AF is subscribed.
  • This signalling may comprise, for example, the target DNAI of the PDU Session.
  • This signalling may comprise an indication of the capability of supporting Edge Application Server (EAS) Internet Protocol (IP) replacement in the 5GC.
  • EAS Edge Application Server
  • IP Internet Protocol
  • the AF 705 signals the NEF 704.
  • This signalling may comprise relocation information for the AF 705.
  • this signalling may comprise N6 traffic routing details corresponding to the target DNAI and /or the 'uplink buffering' indication to indicate that buffering of uplink traffic to the target DNAI is needed.
  • the AF may include Information for EAS IP Replacement in the 5GC.
  • the signalling may be performed by invoking the Nnef_Trafficlnfluence_AppRelocationlnfo service operation either immediately or after any required application relocation in the target DNAI is completed.
  • the signalling may instead be a negative acknowledgment when the AF determines that the application relocation cannot be completed successfully and/or on time
  • the NEF 704 forwards the relocation received at 7005 to the SMF 702.
  • the AF 705 signals an update to the relocation information to the NEF 704.
  • the AF 705 signals updated relocation information to the SMF 702.
  • the AF 705 signals a policy update authorization to the PCF 703.
  • the UPF 701 and SMF 702 exchange signalling related to the UPF’s addition, relocation, or removal.
  • the SMF enforces the change of DNAI, or addition, change, or removal of a UPF at 7010.
  • the SMF 702 signals a notification regarding the change in UPF status signalled at 7010 to the NEF 704 when the AF has subscribed to this information being provided via the NEF. This may be performed as part of “late notification”, as it is performed after the PDU session reconfiguration has been performed.
  • This signalling may comprise the target DNAI of the PDU Session and may indicate the capability of the 5GC of supporting EAS IP replacement. Using current 3GPP terminology, this signalling may be performed by invoking an Nsmf_EventExposure_Notify service operation.
  • the NEF 704 signals an indication of a traffic influence of this change in UPF status to the application function 705.
  • the NEF may perform a similar information mapping as described above in relation to “early notification” signalling.
  • the SMF 702 signals a notification regarding the change in UPF status signalled at 7010 to the application function 705. This may be as described above in relation to “early notification”, bar the present signalling is considered to be “late notification”.
  • the application function 705 determines whether an application function instance change would be beneficial in light of the change in UPF status and the change in traffic signalled.
  • the application function 705 signals any application function relocation information to the NEF 704, which may in turn provide this information to the SMF 702. [0180] At 7016, the application function 705 signals any application function relocation information to the SMF 702.
  • the application function 705 signals any application function relocation information to the PCF 703.
  • the new application function may also signal the SMF 702, PCF 703, and/or the NEF 704. [0183] This signalling of 7015 onwards may allow the old application function (the new and/or the old application function) to synchronize the PCF with any rule updates for the change in application function. These steps won’t be illustrated for simplicity reasons.
  • Figure 8 illustrates procedures and message details related to AF change that may be performed during 7015 to 7017. This signalling relates to how the Application Function and the SMF may exchange signalling to maintain an efficient user plane path for Application Functions.
  • Figure 8 illustrates signalling that may be performed between an AMF 801 , a UPF 802, an SMF 803, a PCF 804, a UDR 805, an NEF 806 and an AF 807.
  • the AF 807 creates an AF request.
  • the request may comprise an AF Transaction Id.
  • the transaction ID is defined by the AF when the AF sends a subscription request.
  • the transaction ID is used to help to correlate later received and/or transmitted notifications to the corresponding session.
  • the AF request may also comprise an indication that the AF desires to receive the corresponding notifications (AF notification reporting information).
  • the AF request may enable the AF to cause traffic influence updates and/or to create subscriptions to notifications from an SMF (e.g. early and/or late notifications to indications that a user plane path is to be reconfigured).
  • the AF 807 signals the NEF 806.
  • This signalling may be an indication to create, update, or delete a traffic influence information, which relates to traffic routing over an N6 interface (i.e. an interface between a user plane function and the AF).
  • Traffic influence information is currently defined and used in several 3GPP Technical Specifications (see, for example TS 23.501 and TS 23.502).
  • the AF may invoke a Nnef_Trafficlnfluence_Update or Nnef_Trafficlnfluence_Delete service operation when providing the corresponding AF Transaction Id.
  • the creation of a new request may be performed using an Nnef_Trafficlnfluence_Create service operation by a target AF [0190]When an update procedure is invoked, the NEF may update the subscription resource.
  • the Nnef_Trafficlnfluence_Update service operation may comprise an updated notification target address.
  • the updated subscription resource is used by the target AF.
  • the NEF 806 and UDR 805 exchange signalling related to storing, updating or removing the traffic influence information stored at the UDR 805.
  • the information stored at the UDR may comprise a data set.
  • the data set may comprise application data.
  • the data set may comprise AF traffic influence request information and a data key.
  • the data key may comprise, for example, an AF Transaction Internal ID, slice identification information (e.g. a single-network slice selection assistance information (S-NSSAI)), and/or a data network name, and/or Internal Group Identifier, and/or a subscriber identifier, such as a subscriber permanent identifier (SUPI).
  • slice identification information e.g. a single-network slice selection assistance information (S-NSSAI)
  • S-NSSAI single-network slice selection assistance information
  • SUPI subscriber permanent identifier
  • the NEF 806 signals the AF 807 to confirm whether or not the traffic influence information has been created, updated, or deleted.
  • the UDR 805 signals the PCF 804 to notify the PCF 804 regarding the change in traffic influence information. This signalling may be performed subsequent to the PCF 804 subscribing to changes related to each one of the data key information items.
  • the PCF 804 signals any policy updates made in response to the change in traffic influence to the SMF 803. This signalling may be performed in response to the PCF 804 determining that existing PDU Sessions are potentially impacted by the AF request and, for each of these PDU Sessions, updating the affected SMF with corresponding new policy information about the PDU Session.
  • the SMF 803 is an example “affected SMF”.
  • the SMF 803 confirms receipt of the updated policy information to the PCF 804.
  • the SMF 803 and UPF 802 exchange signalling to reconfigure any traffic routing based on the changed traffic influence information.
  • the SMF may take appropriate actions to reconfigure the User plane of the PDU Session in 8008 to which the updated policy information relates.
  • the SMF 803 signals the AMF 801. This signalling may comprise updated session information.
  • target AF selected by the source AF has a connection agreement with the 5GS (i.e. the 3GPP 5G domain), has the right UE and service subscription, and provides a compliant Edge Application Server for end to end latency (e.g. when target AFs connected to the source AF have Edge computing sites too far from the UE location).
  • Further Edge computing domains may be in competition with each other when they are deployed by different operators. Thus, the selection of the target Edge computing by the source Edge computing may raise some conflicts of interest between the different operators. In any case, there should be a possibility to allow the 5GS to propose/select the list of potential target AF/Edge computers.
  • source and target AFs may not share their respective traffic descriptors as these may reveal their respective (interconnection) topology (with the 5GS). In other words, confidentially between application functions may be maintained.
  • the following relates to providing at least one mechanism for addressing at least one of the issues mentioned above.
  • a 5GS entity such as for example, an SMF
  • the 5GS entity can act as a trusted entity that proxies traffics between Edge computing domains (such as, for example, between source and target AFs) when there is no interconnection agreement between the Edge computing domains.
  • the 5GS entities may use a Relocation Session ID that allows the source and target AFs to map their respective internal Service IDs (since no a priori agreement between them).
  • the source AF Transaction ID may be used by the target AF Traffic Influence request so that the 5GS entity can replace source AF traffic descriptors (or forwarding rules) by the target AF ones.
  • the selection of the target AF may be triggered due to at least one condition being met.
  • the selection may be triggered in response to a detected UE mobility (as this may impact, for example, traffic latency, supported QoS, etc.).
  • the selection may be triggered in response to the UE moving out of source AF coverage. This latter situation may occur when the AF in question gets overloaded, or when the AF has been or will be taken out of service.
  • the SMF may have subscribed to notifications from NRF and/or NWDAF which may trigger the SMF to re-locate the AF.
  • the selection may be triggered in response to a determination that an end to end latency, or more generally a QoE (Quality of Experience), is likely to be better with another AF.
  • QoE Quality of Experience
  • the SMF generally selects the AF via the help of a NRF and/or /NWDAF. For instance, the Operations, Administration and Maintenance (QAM) of the PLMN or the AF may inject corresponding attributes into the NRF. SMF consults the NRF and retrieves a list of candidate AF(s) available to the PLMN. SMF may also subscribe or request analytics information from NWDAF to help in selecting the best suited AF, based on QoE, load, delay, service area, etc.
  • QAM Operations, Administration and Maintenance
  • the NRF may maintain an AF list that comprises a list of AFs and their associated parameters.
  • the parameters may comprise, for each AF stored in the list, one or more of: an indication of the Edge computing domain the AF serves, service area, Tracking Area Identifier, the load I QoE and the application(s) supported.
  • a similar list may be maintained by a local and/or Central NEF.
  • the NEF may maintain an AF list that comprises a list of AFs and their associated parameters.
  • the parameters may comprise, for each AF stored in the list, one or more of: an indication of the Edge computing domain the AF serves, service area, a Tracking Area Identifier, the load / QoE, and the application supported.
  • a previous AF list may be established based on a pre-existing configuration (i.e. static procedure) or could be dynamically computed. The dynamic computation may be performed in dependence on a maximum end-to-end latency negotiation.
  • the 5GS entity may select at least one potential target AF based on at least one factor.
  • the at least one factor may comprise at least one of: a current location for the UE, an end-to-end latency compliance, and a UE app subscription/service (e.g. whether the target Edge computing supports the UE app subscription/service). Additional information may be provided by the 5GS entity to the select target AF so that the later can select the appropriate local target AF.
  • the target AF selected by the 5GS entity e.g. SMF
  • the target AF may redirect any local NEF messages to a local target AF.
  • a Network Function (NF) in the 5GS selects the list of potential target AF(s) and provides it to the source AF. This may be performed using notification messages.
  • the notification messages may be early or late notification messages, and may be expanded versions of those notifications discussed above in relation to Figure 7.
  • an early notification is considered to be a notification/signalling related to a change in application function prior to the PDU session being reconfigured.
  • a late notification is considered to be a notification/signalling related to a change in application function after the PDU session is reconfigured.
  • the source AF may then exchange information with the target AF to exchange AF context and to relocate Edge Application Server.
  • This signalling may also comprise providing the target AF with the source AF’s transaction ID.
  • the target AF may signal a create/update traffic influence request that comprises the source AF transaction ID so that 5GS NFs can replace source AF forwarding rules by target AF forwarding rules.
  • the NF in the 5GS e.g. the SMF
  • Figures 9 and 10 both illustrate this example in which a network function in the 5GS provides an identifier to the target AF, with Figure 9 relating to an example in which the source transaction ID is provided in an early notification message, while Figure 10 relates to an example in which the source transaction ID is provided in a late notification message.
  • the timing and current form of early and late notification are specified in 3GPP TS 23.502, but are further modified over current specifications to comprise at least one identifier, as described herein. It is understood that although the examples of Figures 9 and 10 refer to an SMF as performing certain functions, these functions may be performed by another network function located in the 5GS.
  • Figure 9 illustrates signalling that may be performed between an SMF 901 , an NEF 902, a source AF 903 and a target AF 904. It is understood that although AFs are referred to herein, that the following may be applied more generally to any entities in different EC domains.
  • the SMF 901 determines that at least one trigger condition has been fulfilled for selecting a new AF (e.g. for selecting target AF 904.
  • the trigger condition may be, for example, a determination that the UE associate with a particular session has moved to a new location (due to mobility).
  • Another example trigger condition may be when the user plane function associated with this session has been relocated.
  • the SMF 902 signals the NEF 902.
  • This signalling may comprise a target AF identifier.
  • This signalling may comprise a source AF transaction identifier.
  • This signalling may comprise an early notification. Using current 3GPP terminology, this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 902 signals the source AF 903.
  • This signalling may comprise the target AF identifier.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an early notification. Using current 3GPP terminology, this signalling may be provided using an Nef_Trafficlnfluence_Notify service procedure.
  • 9004 and 9005 relate to a context exchange between the source and target AFs.
  • the source AF 903 may signal the target AF 904.
  • This signalling may comprise a relocation request.
  • This signalling may comprise an Edge Application Server identifier for the source AF.
  • This signalling may comprise a service identifier.
  • This signalling may comprise the source AF transaction identifier.
  • the target AF 904 responds to the signaling of 9004.
  • the response may comprise a relocation reply.
  • This response may comprise an Edge Application Server identifier for the target AF.
  • This response may comprise the service identifier.
  • This response may comprise the source AF transaction identifier.
  • the Source AF 903 signals the NEF 902.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an acknowledgement.
  • This signalling may indicate that uplink buffering is activated. Using current 3GPP terminology, this signalling may be labelled as Nnef_Trafficlnfluence_Applicationlnfo.
  • the NEF 902 signals the SMF 901.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an acknowledgement.
  • This signalling may indicate that uplink buffering is activated. Using current 3GPP terminology, this signalling may be labelled as Nsmf_EventExposure_Applicationlnfo.
  • the PDU session reconfiguration is performed. This may additionally be performed with a UPF PDU Session anchor (PSA) relocation.
  • PSA PDU Session anchor
  • the SMF 902 signals the NEF 902.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise a late notification.
  • this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 902 signals the target AF 904.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise a late notification.
  • this signalling may be provided using an Nef_Trafficlnfluence_Notify service procedure.
  • 9012 and 9013 relate to the provision by the target AF of new traffic descriptors to replace the old ones which were installed by the source AF.
  • This signalling comprises the source AF transaction ID to enable the SMF to correlate between old and new traffic descriptors.
  • the target AF 904 signals the NEF 902.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise a target EAS Internet Protocol Address.
  • This signalling may comprise the source AF transaction identifier. Using current 3GPP terminology, this signalling may be labelled as Nnef_Trafficlnfluence_AppRelocationlnfo.
  • the NEF 902 signals the SMF 901.
  • This signalling may be a Traffic Influence message.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server identifier.
  • the identifier may be, for example, an Internet Protocol Address, or otherwise represent some identifier by which the source edge application server may be located.
  • This signalling may comprise a target EAS identifier.
  • This identifier may be, for example, an Internet Protocol Address, or otherwise represent some identifier by which the source edge application server may be located.
  • This signalling may comprise the source AF transaction identifier. Using current 3GPP terminology, this signalling may be labelled as Nsmf_EventExposure_AppRelocationlnfo.
  • the target AF 904 signals the source AF 903.
  • This signalling may comprise an indication that the relocation has been completed.
  • This signalling may comprise the service identifier.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may cause the source AF to delete Edge Application Server contexts stored therein, thereby finalizing the relocation.
  • Figure 10 illustrates signalling between an SMF 1001 , an NEF 1002, a source AF 1003, and a target AF 1004.
  • the SMF 1001 determines that at least one trigger condition has been fulfilled for selecting a new AF (e.g. for selecting target AF 1004.
  • the trigger condition may be, for example, a determination that the UE associate with a particular session has moved to a new location (due to mobility).
  • Another example trigger condition may be when the user plane function associated with this session has been relocated.
  • the SMF 1001 signals the NEF 1002.
  • This signalling may comprise a source AF transaction identifier.
  • This signalling may comprise an early notification. Using current 3GPP terminology, this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 1002 signals the source AF 1003.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an early notification. Using current 3GPP terminology, this signalling may be provided using an Nnef_Trafficlnfluence_Notify service procedure.
  • the Source AF 1003 signals the NEF 1002.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an acknowledgement to indicate that uplink buffering is activated.
  • this signalling may be labelled as Nnef_Trafficlnfluence_Applicationlnfo.
  • the NEF 1002 signals the SMF 1001.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise an acknowledgement to indicate that uplink buffering is activated.
  • this signalling may be labelled as Nsmf_EventExposure_Applicationlnfo.
  • the PDU session reconfiguration is performed. This may additionally be performed with a UPF PSA relocation.
  • the SMF 1002 signals the NEF 1002.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise a target AF identifier.
  • This signalling may comprise a late notification. Using current 3GPP terminology, this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 1002 signals the source AF 1003.
  • This signalling may comprise a late notification.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may comprise the target AF identifier.
  • this signalling may be provided using an Nef_Trafficlnfluence_Notify service procedure.
  • 10009 and 10010 relate to a context exchange between the source and target AFs.
  • the source AF 1003 may signal the target AF1004.
  • This signalling may comprise a relocation request.
  • This signalling may comprise an Edge Application Server identifier at the source AF.
  • This signalling may comprise a service identifier.
  • This signalling may comprise the source AF transaction identifier.
  • the target AF 1004 responds to the signaling of 10009.
  • the response may comprise a relocation reply.
  • This response may comprise an Edge Application Server identifier at the target AF.
  • This response may comprise the service identifier.
  • This response may comprise the source AF transaction identifier.
  • the Edge Application Server is relocated.
  • the application layer context are also exchanged.
  • the application layer context information that may be exchanged will be dependent on the application being used. For example, if the application is a game-based application, the application layer context may be the user’s present game environment parameters.
  • 10012 and 10013 relate to the provision by the target AF of new traffic descriptors to replace the old ones which were installed by the source AF.
  • This signalling comprises the source AF transaction ID to enable the SMF to correlate between old and new traffic descriptors.
  • uplink buffering is deactivated if it was previously enabled.
  • the target AF 1004 signals the NEF 1002.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise a target EAS Internet Protocol Address.
  • This signalling may comprise the source AF transaction identifier. Using current 3GPP terminology, this signalling may be labelled as Nnef_Trafficlnfluence_AppRelocationlnfo.
  • the NEF 1002 signals the SMF 1001.
  • This signalling may be a Traffic Influence message.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise a target EAS Internet Protocol Address.
  • This signalling may comprise the source AF transaction identifier. Using current 3GPP terminology, this signalling may be labelled as Nsmf_EventExposure_AppRelocationlnfo.
  • the target AF 1004 signals the source AF 1003.
  • This signalling may comprise an indication that the relocation has been completed.
  • This signalling may comprise the service identifier.
  • This signalling may comprise the source AF transaction identifier.
  • This signalling may cause the source AF to delete Edge Application Server contexts stored therein, thereby finalizing the relocation.
  • Figures 9 and 10 relate to examples in which it is assumed that there is an interconnection agreement between the source and target AFs.
  • the example illustrated in Figure 11 relates to an example in which there is assumed to be no interconnection agreement between the source and target AFs. It is understood that the source and target AFs in this latter may still reach each other for signalling purposes using their respective public Internet Protocol (IP) addresses. In other words, an IP connectivity may exist between the source and target AFs.
  • IP Internet Protocol
  • a network function in the 5GS e.g. the SMF
  • the notification message may be an early notification.
  • the notification message may be a late notification.
  • the former sends a negative acknowledgement message back to the 5GS.
  • the 5GS decides to act as a trusted entity to both the source and target AFs, and proxies control traffic between the source and the target AFs.
  • the 5GS is able to act as a proxy as it has its own respective interconnection agreements with both of the Edge computing domains in which the source and target AFs are located.
  • the entity in the 5GS that performs this proxying will be referred to herein as a proxy function.
  • the proxy function may be identifiable via a proxy function identity (proxy ID).
  • the 5GS can advertise a proxy ID and a Relocation Session ID (Relo ID) that it generates.
  • the latter allows both source and target AFs to map their respective internal information, such as Service ID, to the Relocation Session ID.
  • Figure 11 shows signalling between an SMF 1101 , an NEF 1102, a source AF 1103, a proxy function 1104, and a target AF 1105.
  • the SMF 1101 determines that at least one trigger condition has been fulfilled for selecting a new AF (e.g. for selecting target AF 1104).
  • the trigger condition may be, for example, a determination that the UE associate with a particular session has moved to a new location (due to mobility).
  • Another example trigger condition may be when the user plane function associated with this session has been relocated.
  • the SMF 1 101 signals the NEF 1102.
  • This signalling may comprise a target AF identifier.
  • This signalling may comprise an early notification.
  • this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 1102 signals the source AF 1103.
  • This signalling may comprise the target AF identifier.
  • This signalling may comprise an early notification. Using current 3GPP terminology, this signalling may be provided using an Nnef_Trafficlnfluence_Notify service procedure.
  • the Source AF 1103 signals the NEF 1102.
  • This signalling may comprise a negative acknowledgment to the signalling of 11003.
  • This signalling may indicate that the negative acknowledgment is being sent as there is no connection between the source and target AFs that allow for context exchange to be performed, such as when there is no interconnection agreement between the source and target AFs.
  • this signalling may be labelled as Nnef_Trafficlnfluence_Applicationlnfo or Nsmf_EventExposure_AppRelocationlnfo.
  • the NEF 1102 signals the SMF 1101.
  • This signalling may comprise a negative acknowledgment to the signalling of 11002.
  • This signalling may indicate that the negative acknowledgment is being sent as there is no interconnection agreement between the source and target AFs.
  • this signalling may be labelled as Nsmf_EventExposure_Applicationlnfo or Nsmf_EventExposure_AppRelocationlnfo..
  • the SMF 1101 signals the NEF 1102.
  • This signalling may comprise an early notification.
  • This signalling may comprise an identifier of the proxy function 1104 (called herein a proxy identifier/Proxy ID).
  • the signalling may comprise a Relocation Session ID generated by the SMF 1101.
  • the NEF 1102 signals the target AF 1105.
  • This signalling may comprise an early notification.
  • This signalling may comprise the proxy identifier.
  • the signalling may comprise the Relocation Session ID.
  • the SMF 1101 signals the NEF 1102.
  • This signalling may comprise an early notification.
  • This signalling may comprise the proxy identifier.
  • the signalling may comprise the Relocation Session ID.
  • the NEF 1102 signals the source AF 1103.
  • This signalling may comprise an early notification.
  • This signalling may comprise the proxy identifier.
  • the signalling may comprise the Relocation Session ID.
  • 11010 to 11013 relate to AF context being exchanged between the source and target AFs using the proxy function as an intermediary.
  • the source AF 1103 signals the proxy function 1104.
  • This signalling may comprise a relocation request.
  • the relocation request may comprise a GPSI.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise an identifier for the service.
  • the proxy function 1104 signals the target AF 1105.
  • This signalling may comprise a relocation request.
  • the relocation request may comprise the GPSI.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise the identifier for the service.
  • the target AF 1105 signals the proxy function 1104.
  • This signalling may comprise a relocation request.
  • the relocation request may comprise a GPSI.
  • This signalling may comprise a target Edge Application Server Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise an identifier for the service.
  • the proxy function 1104 signals the source AF 1103.
  • This signalling may comprise a relocation request.
  • the relocation request may comprise the GPSI.
  • This signalling may comprise the target Edge Application Server Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise the identifier for the service.
  • the Edge Application Server is relocated.
  • the application layer context are also exchanged.
  • the source AF 1103 signals the NEF 1102.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise an acknowledgement to indicate that uplink buffering is activated.
  • this signalling may be labelled as Nnef_Trafficlnfluence_Applicationlnfo.
  • the NEF 1102 signals the SMF 1101.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise an acknowledgement to indicate that uplink buffering is activated. Using current 3GPP terminology, this signalling may be labelled as Nsmf_EventExposure_Applicationlnfo.
  • the PDU session reconfiguration is performed. This may additionally be performed with a UPF PSA relocation.
  • the SMF 1 101 signals the NEF 1 102.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise the GPSI.
  • This signalling may comprise a late notification. Using current 3GPP terminology, this signalling may be provided using an Nsmf_EventExposure_Notify service procedure.
  • the NEF 1102 signals the target AF 1105.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may comprise the GPSI.
  • This signalling may comprise a late notification. Using current 3GPP terminology, this signalling may be provided using an Nef_Trafficlnfluence_Notify service procedure.
  • 11020 and 11021 relate to the provision by the target AF of new traffic descriptors to replace the old ones which were installed by the source AF.
  • This signalling comprises the source AF transaction ID to enable the SMF to correlate between old and new traffic descriptors.
  • the target AF 1105 signals the NEF 1102.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise a target EAS Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID. Using current 3GPP terminology, this signalling may be labelled as Nnef_Trafficlnfluence_AppRelocationlnfo.
  • the NEF 1102 signals the SMF 1101.
  • This signalling may be a Traffic Influence message.
  • This signalling may be a Traffic Influence message.
  • This signalling may comprise a GPSI.
  • This signalling may comprise traffic information.
  • This signalling may comprise a source Edge Application Server Internet Protocol Address.
  • This signalling may comprise a target EAS Internet Protocol Address.
  • This signalling may comprise the Relocation Session ID. Using current 3GPP terminology, this signalling may be labelled as Nsmf_EventExposure_AppRelocationlnfo.
  • the target AF 1105 signals the proxy function 1104.
  • This signalling may comprise an indication that the relocation has been completed.
  • This signalling may comprise the service identifier.
  • This signalling may comprise the Relocation Session ID.
  • the proxy function 1104 signals the source AF 1103.
  • This signalling may comprise an indication that the relocation has been completed.
  • This signalling may comprise the service identifier.
  • This signalling may comprise the Relocation Session ID.
  • This signalling may cause the source AF to delete Edge Application Server contexts stored therein, thereby finalizing the relocation.
  • Figures 12 to 17 are flow charts illustrating potential operations that may be performed by various apparatus described herein. It is therefore understood that features described above in relation to specific examples may also be performed by the apparatus described hereunder. It is also understood that the apparatus of Figures 12 to 17 may interact with each other where applicable.
  • Figure 12 illustrates potential operations that may be performed by an apparatus for a network function located in a first domain.
  • the network function may be, for example, a session management function.
  • the first domain may be a core network part of a network, such as, for example, a 5G core, a 6G core, or an LTE core.
  • the apparatus determines that a user plane path currently used for a session is to be reconfigured.
  • the current user plane path may be provided by a first application function located in a second domain.
  • the new user plane path may be provided by a second application function located in a third domain.
  • the second and third domains may be different edge computing domains that are under the control of respective administrators.
  • the apparatus receives signalling from a second application function located in a third domain, the signalling comprising the first identifier and comprising an indication confirming that said routing information has been updated.
  • Said signalling to a first application function comprises signalling the first application function via a network exposure function.
  • the apparatus may exchange signalling, with a network repository function to obtain an identifier of at least one candidate application function for the second application function: and signal the identifier of the at least one candidate application function to the first application function.
  • the apparatus may exchange signalling, with a network analytics function to obtain analytics information for use in selecting the second application function from the at least one candidate application function: and select the second application function (and/or the at least one candidate application function) using the obtained analytics information.
  • the at least one candidate application function may comprise the second application function.
  • the apparatus may receive an indication that the first and second application functions have no established trust between them; and generate the first identifier in response to receiving said indication that the first and second application functions have no established trust between them.
  • the first identifier may be the relocation identifier referred to in the above specific examples.
  • the apparatus may signal a second identifier to the first application with the first identifier, the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus may signal at least one of the first identifier and/or the second identifier to the second application function.
  • the first identifier may comprise a transaction identifier used by the first application function for the session.
  • the Transaction ID is used between the first application function and the network function (e.g. the session management function) in the first domain.
  • the PDU session ID is internal to the first domain, and the session management function in the first domain may map the Transaction ID to the related session ID.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured. In other words, the signalling may be comprised within an early notification.
  • the signalling to at least one of the first application function and/or second application function may be performed after the user plane path has been reconfigured. In other words, the signalling may be comprised within a late notification.
  • Figure 13 illustrates potential operations that may be performed by an apparatus for a first application function located in a second domain.
  • the first application function may be a source application function.
  • the second domain may be as described above in relation to Figure 12.
  • the apparatus receive signalling from a network function located in a first domain, the signalling comprising an indication of a second application function located in a third domain and an indication that a user plane path currently used by the first application function is to be reconfigured.
  • the apparatus determines whether the first application function has an established trust with the second application function.
  • the apparatus signals the results of the determination to the network function.
  • the network function may be one of a session management function and a network exposure function.
  • the network function may be as described above in relation to Figure 12.
  • the apparatus may, when the first application function has an established trust with the second application function: receive signalling from the network function, the signalling comprising a first identifier authorising the first application function to update routing information for the reconfigured user plane path; and signal the first identifier to the second application function, wherein the first identifier comprises a transaction identifier used by the first application function for the session.
  • the signalling the first identifier to the second application function may comprise exchanging context information for the session with the second application function.
  • the apparatus may, when the first application function does not have an established trust with the second application function: receive, from the network function, signalling from the network function, the signalling comprising a second identifier that identifies a proxy function having an established trust between the first and second application functions and a third identifier to identify the user plane path being reconfigured; and exchange context information for the session with the second application function via the proxy function using the third identifier.
  • the signalling to at least one of the first application function and/or second application function may be performed before the user plane path has been reconfigured. In other words, the signalling may be comprised within an early notification.
  • Figure 14 illustrates potential operations that may be performed by an apparatus for a second application function located in a third domain.
  • the second application function may be a target application function.
  • the second application function may interact as per the second application function described above in relation to Figures 12 and 13.
  • the third domain may be as described above in relation to Figure 12.
  • the apparatus receives one of a first identifier and a second identifier, the first identifier authorising a first application function located in a second domain to update routing information for a reconfigured user plane path, and the second identifier identifying a proxy function having an established trust between the first and second application functions.
  • the apparatus exchanges, with the first application function, context information for a session with the first application in the second domain using the first identifier or the second identifier.
  • the apparatus signals a network function located in a first domain updated routing information for the reconfigured user plane path.
  • the first identifier may be received from the first application function, and the exchanging may be performed using direct communications between the first and second application functions.
  • the first and/or second identifier may be as discussed above in relation to Figure 12.
  • the second identifier may be received from a network function located in a first domain, and the exchanging is performed using indirect communications between the first and second application functions via the proxy function using a third identifier, the third identifier being received from the network function during said receiving and identifying the user plane path being reconfigured.
  • Figure 15 is a flow chart illustrating potential operations that may be performed by an apparatus for a proxy function.
  • the proxy function may interact as discussed above in relation to Figures 12 to 14.
  • the apparatus establishes a trust with each of a first application function located in a second domain and a second application function located in a third domain, wherein the proxy function is configured to act on behalf of an application function to each of the first and second application functions.
  • the apparatus receives at least one of a first identifier and a third identifier from a network function located in a first domain, the first identifier authorising the first application function to update routing information for the reconfigured user plane path in response to the determining and the third identifier identifying the user plane path being reconfigured.
  • the apparatus exchanges signalling with each of the first and second application functions using the received identifier to facilitate the exchange of context information between the first and second application functions.
  • Figure 16 illustrates potential operations that may be performed by an apparatus for a network repository function.
  • the apparatus of Figure 16 may interact with the apparatus of Figure 12 as discussed above.
  • the apparatus stores, for each application function in a set of application functions, an identifier of said application function and an indication of a domain served by said application function.
  • the apparatus receives, from a first network function, a request for an identifier of an application function for serving a subscriber.
  • the apparatus selects at least one first application function from the set of application functions.
  • the apparatus provides the first network function with an identifier of the at least one first application function to the first network function.
  • Said providing may comprising providing, for each of the at a least one first application functions, an indication of at least one of: the domain served by said application function, a service area covered by said application function, a tracking area identifier for said application function, and/or an application supported by said application function.
  • Figure 17 illustrates potential operations that may be performed by an apparatus for a network analytics function.
  • the apparatus of Figure 17 may interact with the apparatus of Figure 12 as discussed above.
  • the apparatus receives from a first network function, a request for information for selecting an application function for serving a subscriber, the request comprising an identifier of said application function and an indication of a domain served by said application function.
  • FIG. 2 shows an example of a control apparatus for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, gNB, a central unit of a cloud architecture or a node of a core network such as an MME or S-GW, a scheduling entity such as a spectrum management entity, or a server or host, for example an apparatus hosting an NRF, NWDAF, AMF, SMF, UDM/UDR etc.
  • the control apparatus may be integrated with or external to a node or module of a core network or RAN.
  • base stations comprise a separate control apparatus unit or module.
  • the control apparatus can be another network element such as a radio network controller or a spectrum controller.
  • the control apparatus 200 can be arranged to provide control on communications in the service area of the system.
  • the apparatus 200 comprises at least one memory 201 , at least one data processing unit 202, 203 and an input/output interface 204. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the apparatus.
  • the receiver and/or the transmitter may be implemented as a radio front end or a remote radio head.
  • the control apparatus 200 or processor 201 can be configured to execute an appropriate software code to provide the control functions.
  • a communication device 300 Such a communication device is often referred to as user equipment (UE) or terminal.
  • UE user equipment
  • An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals.
  • Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like.
  • MS mobile station
  • PDA personal data assistant
  • a mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.
  • a wireless communication device may be for example a mobile device, that is, a device not fixed to a particular location, or it may be a stationary device.
  • the wireless device may need human interaction for communication, or may not need human interaction for communication.
  • the terms UE or “user” are used to refer to any type of wireless communication device.
  • the wireless device 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals.
  • transceiver apparatus is designated schematically by block 306.
  • the transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement.
  • the antenna arrangement may be arranged internally or externally to the wireless device.
  • a wireless device is typically provided with at least one data processing entity 301 , at least one memory 302 and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices.
  • the data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 704.
  • the user may control the operation of the wireless device by means of a suitable user interface such as keypad 305, voice commands, touch sensitive screen or pad, combinations thereof or the like.
  • a display 308, a speaker and a microphone can be also provided.
  • a wireless communication device may comprise appropriate connectors (either wired or' wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
  • Figure 4 shows a schematic representation of non-volatile memory media 400a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 400b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 402 which when executed by a processor allow the processor to perform one or more of the steps of the methods of Figure 9 and/or Figure 10 and/or Figure 11 , and/or Figure 12, and/or Figure 13, and/or Figure 14, and/or Figure 15, and/or Figure 16, and/or Figure 17.
  • CD computer disc
  • DVD digital versatile disc
  • 400b e.g. universal serial bus (USB) memory stick
  • embodiments may thus vary within the scope of the attached claims.
  • some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto.
  • various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware.
  • any procedures e.g., as in Figure 9 and/or Figure 10 and/or Figure 11 , and/or Figure 12, and/or Figure 13, and/or Figure 14, and/or Figure 15, and/or Figure 16, and/or Figure 17, may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions.
  • the software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.
  • the memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (AStudy ItemC), gate level circuits and processors based on multi-core processor architecture, as non-limiting examples.
  • circuitry may be configured to perform one or more of the functions and/or method steps previously described. That circuitry may be provided in the base station and/or in the communications device.
  • circuitry may refer to one or more or all of the following:
  • any portions of hardware processor(s) with software including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • software e.g., firmware
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example integrated device.
  • UMTS universal mobile telecommunications system
  • UTRAN wireless local area network
  • WiFi wireless local area network
  • WiMAX worldwide interoperability for microwave access
  • PCS personal communications services
  • WCDMA wideband code division multiple access
  • UWB ultra-wideband
  • sensor networks mobile ad-hoc networks
  • MANETs mobile ad-hoc networks
  • IMS Internet Protocol multimedia subsystems
  • Figure 5 depicts examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown.
  • the connections shown in Figure 5 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 5.
  • the example of Figure 5 shows a part of an exemplifying radio access network.
  • the radio access network may support sidelink communications described below in more detail.
  • Figure 5 shows devices 500 and 502.
  • the devices 500 and 502 are configured to be in a wireless connection on one or more communication channels with a node 504.
  • the node 504 is further connected to a core network 506.
  • the node 504 may be an access node such as (eZg)NodeB serving devices in a cell.
  • the node 504 may be a non-3GPP access node.
  • the physical link from a device to a (eZg)NodeB is called uplink or reverse link and the physical link from the (eZg)NodeB to the device is called downlink or forward link.
  • (eZg)NodeBs or their functionalities may be implemented by using any node, host, server or access point etc. entity suitable for such a usage.
  • a communications system typically comprises more than one (eZg)NodeB in which case the (eZg)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signalling purposes.
  • the (eZg)NodeB is a computing device configured to control the radio resources of communication system it is coupled to.
  • the NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment.
  • the (eZg)NodeB includes or is coupled to transceivers. From the transceivers of the (eZg)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to devices.
  • the antenna unit may comprise a plurality of antennas or antenna elements.
  • the (eZg)NodeB is further connected to the core network 506 (CN or next generation core NGC). Depending on the deployed technology, the (eZg)NodeB is connected to a serving and packet data network gateway (S-GW +P-GW) or user plane function (UPF), for routing and forwarding user data packets and for providing connectivity of devices to one or more external packet data networks, and to a mobile management entity (MME) or access mobility management function (AMF), for controlling access and mobility of the devices.
  • S-GW +P-GW serving and packet data network gateway
  • UPF user plane function
  • MME mobile management entity
  • AMF access mobility management function
  • Examples of a device are a subscriber unit, a user device, a user equipment (UE), a user terminal, a terminal device, a mobile station, a mobile device, etc
  • the device typically refers to a mobile or static device (e.g. a portable or nonportable computing device) that includes wireless mobile communication devices operating with or without an universal subscriber identification module (IISIM), including, but not limited to, the following types of devices: mobile phone, smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device.
  • IISIM universal subscriber identification module
  • a device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction, e.g. to be used in smart power grids and connected vehicles.
  • the device may also utilise cloud.
  • a device may comprise a user portable device with radio parts (such as a watch, earphones or eyeglasses) and the computation is carried out in the cloud.
  • the device illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a device may be implemented with a corresponding apparatus, such as a relay node.
  • a relay node is a layer 3 relay (self-backhauling relay) towards the base station.
  • the device (or, in some examples, a layer 3 relay node) is configured to perform one or more of user equipment functionalities.
  • CPS cyber-physical system
  • ICT interconnected information and communications technology
  • devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.
  • apparatuses have been depicted as single entities, different units, processors and/or memory units (not all shown in Figure 5) may be implemented.
  • 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • MIMO multiple input - multiple output
  • 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications (such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control).
  • 5G is expected to have multiple radio interfaces, e.g.
  • 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, 6 or above 24 GHz - cmWave and mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, 6 or above 24 GHz - cmWave and mmWave.
  • network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
  • the current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network.
  • the low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multiaccess edge computing (MEC).
  • 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors.
  • MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time.
  • Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).
  • the communication system is also able to communicate with other networks 512, such as a public switched telephone network, or a VoIP network, or the Internet, or a private network, or utilize services provided by them.
  • the communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 5 by “cloud” 514). This may also be referred to as Edge computing when performed away from the core network.
  • the communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.
  • the technology of Edge computing may be brought into a radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN).
  • RAN radio access network
  • NFV network function virtualization
  • SDN software defined networking
  • Using the technology of edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts.
  • Application of cloudRAN architecture enables RAN real time functions being carried out at or close to a remote antenna site (in a distributed unit, DU 508) and non- real time functions being carried out in a centralized manner (in a centralized unit, CU 510).
  • 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling.
  • Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, Mobile Broadband, (MBB) or ensuring service availability for critical communications, and future railway/maritime/aeronautical communications.
  • Satellite communication may utilise geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed).
  • GEO geostationary earth orbit
  • LEO low earth orbit
  • mega-constellations systems in which hundreds of (nano)satellites are deployed.
  • Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells.
  • the on-ground cells may be created through an on-ground relay node or by a gNB located on-ground or in
  • the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (eZg)NodeBs, the device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (eZg)NodeBs or may be a Home(eZg)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided.
  • Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells.
  • the (eZg)NodeBs of Figure 5 may provide any kind of these cells.
  • a cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (eZg)NodeBs are required to provide such a network structure.
  • a network which is able to use “plug-and-play” (eZg)Node Bs includes, in addition to Home (eZg)NodeBs (H(eZg)nodeBs), a home node B gateway, or HNB-GW (not shown in Figure 5).
  • HNB-GW HNB Gateway
  • a HNB Gateway (HNB-GW) which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé, un programme d'ordinateur et un appareil pour une fonction de réseau située dans un premier domaine, qui amène l'appareil à : déterminer qu'un trajet de plan d'utilisateur actuellement utilisé pour une session doit être reconfiguré ; signaler, à une première fonction d'application située dans un second domaine, un premier identifiant autorisant la première fonction d'application à mettre à jour des informations de routage pour le trajet de plan utilisateur reconfiguré en réponse à la détermination ; et recevoir une signalisation à partir d'une seconde fonction d'application située dans un troisième domaine, la signalisation comprenant le premier identifiant et comprenant une indication confirmant que lesdites informations de routage ont été mises à jour.
EP21786962.7A 2021-10-06 2021-10-06 Appareil, procédés et programmes informatiques Pending EP4413778A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/077541 WO2023057058A1 (fr) 2021-10-06 2021-10-06 Appareil, procédés et programmes informatiques

Publications (1)

Publication Number Publication Date
EP4413778A1 true EP4413778A1 (fr) 2024-08-14

Family

ID=78080354

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21786962.7A Pending EP4413778A1 (fr) 2021-10-06 2021-10-06 Appareil, procédés et programmes informatiques

Country Status (2)

Country Link
EP (1) EP4413778A1 (fr)
WO (1) WO2023057058A1 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007052916A1 (fr) * 2005-10-31 2007-05-10 Lg Electronics Inc. Procede de traitement d'informations de commande dans un systeme de communications mobile sans fil
KR102373738B1 (ko) * 2018-03-08 2022-03-15 지티이 코포레이션 상이한 액세스 네트워크들 간에 모바일 통신 디바이스의 핸드오버를 수행하기 위한 방법 및 시스템

Also Published As

Publication number Publication date
WO2023057058A1 (fr) 2023-04-13

Similar Documents

Publication Publication Date Title
US11212731B2 (en) Mobile network interaction proxy
US11071055B1 (en) Network slice selection in cellular system
US20210227353A1 (en) Logical radio network
US20230124206A1 (en) Apparatus, methods, and computer programs
EP4132199A1 (fr) Appareil, procédés et programmes informatiques
EP4106273A1 (fr) Appareil, procédés et programmes informatiques
EP4413778A1 (fr) Appareil, procédés et programmes informatiques
EP4280557A1 (fr) Appareil, procédés et programmes informatiques
WO2022261972A1 (fr) Appareils, procédés et programmes informatiques
US20230148200A1 (en) Apparatus, methods, and computer programs
US20230262806A1 (en) Apparatus, methods, and computer programs
US20230254931A1 (en) Apparatus, methods, and computer programs
US20240031415A1 (en) Locating recipient
US20230261792A1 (en) Apparatus, methods, and computer programs
US20230216929A1 (en) Apparatus, methods, and computer programs
US20230099315A1 (en) Apparatus, methods, and computer programs
WO2024026640A1 (fr) Appareil, procédé et programme informatique
WO2024033833A1 (fr) Appareil, procédé et programme d'ordinateur
US20240163766A1 (en) Apparatus, method, and computer program
WO2023194350A1 (fr) Appareil, procédés et programmes informatiques pour tranches de réseau temporairement indisponibles
WO2022268296A1 (fr) Découverte et sélection de services de fonction de réseau (nf) enregistrés dans une fonction de dépôt de réseau (nrf)
WO2024033180A1 (fr) Connectivité double
WO2023051918A1 (fr) Gestion d'abonnements à des notifications de changements de données liés à un service de fonction de réseau
WO2024028809A1 (fr) Appareil, procédé et programme informatique
WO2023131407A1 (fr) Appareil, procédés et programmes informatiques

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240506

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR