WO2023174542A1 - Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g - Google Patents

Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g Download PDF

Info

Publication number
WO2023174542A1
WO2023174542A1 PCT/EP2022/056963 EP2022056963W WO2023174542A1 WO 2023174542 A1 WO2023174542 A1 WO 2023174542A1 EP 2022056963 W EP2022056963 W EP 2022056963W WO 2023174542 A1 WO2023174542 A1 WO 2023174542A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
network function
session
information elements
entity
Prior art date
Application number
PCT/EP2022/056963
Other languages
English (en)
Inventor
Thomas Belling
Devaki Chandramouli
Mu HE
Philippe Godin
Klaus Hoffmann
Bruno Landais
Laurent Thiebaut
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
Priority to PCT/EP2022/056963 priority Critical patent/WO2023174542A1/fr
Publication of WO2023174542A1 publication Critical patent/WO2023174542A1/fr

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present application relates to a method, apparatus, system and computer program and in particular but not exclusively to enabling direct service-based requests from Radio Access Network nodes towards 5G Core Network Functions.
  • a communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations 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, video, electronic mail (email), text message, multimedia and/or content data and so on.
  • Nonlimiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
  • wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link.
  • wireless systems comprise public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN).
  • PLMN public land mobile networks
  • WLAN wireless local area networks
  • Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.
  • a user can access the communication system by means of an appropriate communication device or terminal.
  • a communication device of a user may be referred to as user equipment (UE) or user device.
  • UE user equipment
  • a communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users.
  • the communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and/or receive communications on the carrier.
  • the communication system and associated devices typically operate in accordance with a given 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
  • Other examples of communication systems are the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology and so-called 5G or New Radio (NR) networks.
  • LTE long-term evolution
  • UMTS Universal Mobile Telecommunications System
  • NR New Radio
  • an apparatus comprising means for: obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function; and providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • the network function identifier may enable the access node to directly access the network function associated with the network function identifier.
  • the apparatus or entity may further comprise means for providing a session identifier to the access node.
  • the network function identifier may comprise at least one of: a network address of the network function associated with the network function identifier; and an identifier of a set of network functions that comprises the network function associated with the network function identifier.
  • the means for obtaining the information elements may be for receiving the information elements from the network function associated with the network function identifier.
  • the means for receiving the information elements from the network function associated with the network function identifier may be for receiving the information elements within a N2 interface message container.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • the means for providing the information elements to the access node may be for generating and providing at least one of: an interface protocol data unit session request comprising the information elements from an access and mobility function node to the access node; and a discovery response comprising the information elements from an access and mobility function node to an access node.
  • the means for obtaining the information elements may be further for receiving the network function context identifier, the network function identifier and the session identifier in a Nsmf_PDUSession_CreateSMContext Response, and the means may be further for storing the information elements in a context associated with the identified session.
  • the means for providing the network function identifier may be further for including the network function context identifier; and the network function identifier in a N2 PDU session request when receiving a Namf_Communication_N1N2Message transfer message.
  • the means may be further for: receiving a Namf_Communication_N1 N2Message transfer request containing a session identifier, and providing the network function identifier to the access node associated with the session identified by the session identifier, in response to receiving the Namf_Communication_N1N2Message transfer request.
  • the means for obtaining information elements may be further for: receiving the user equipment identifier, the user equipment identifier associated with a first user equipment and the network function identifier; and storing the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
  • the means may be further for providing a second user equipment identifier associated with the first user equipment to the network function associated with the network function identifier.
  • the user equipment identifier may be a first user equipment identifier and the means may be further for receiving a discovery request user equipment identifier from the access node, wherein the discovery request may comprise at least one of: a second user equipment identifier; a session identifier; and a type of the network function associated with the network function identifier to discover.
  • the network node may comprise an access and mobility function node.
  • the network function associated with the network function identifier may comprise a Session Management Function.
  • an access node or entity comprising means for: receiving, information elements comprising: a network function identifier associated with a network function; and employing the information elements to directly access the network function associated with the network function identifier.
  • the network function identifier may comprise at least one of: a network address of the network function; and an identifier of a set of network functions that comprises the network function.
  • the information elements may further comprise a network function context identifier; and the means for employing the information elements to directly access the network function associated with the network function identifier may be further for providing the network function context identifier in a request towards the network function.
  • the means may be further for storing the information elements.
  • the means may be further for forwarding the information elements to a target access node as part of a user equipment context transfer.
  • the means for receiving the information elements may be for receiving the information elements from a second network function.
  • the means for receiving the information elements from the second network function may be for receiving the information elements according to one of: an interface protocol data unit session request comprising the information elements from an access and mobility function; a user equipment context transfer comprising the information elements from a source access node; and a discovery response comprising the information elements from an access and mobility function node.
  • the means may be further for requesting discovery of the network function from the second network function, wherein the request for the discovery may comprise at least one of: a user equipment identifier; a session identifier; and a type of the network function to discover.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • the means for employing the information elements to directly access the network function associated with the network function address/identifier/set identifier may be for: generating a discovery message comprising the network set identifier and obtaining a response indicating the network function with which to directly communicate; and generating a request to communicate directly with the indicated network function.
  • a Session Management Function or entity comprising means for: sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • the identifier of the session management function may comprise at least one of: an network address of the session management function and an identifier of a set of session management functions that comprises the session management function.
  • a method for a network node or entity comprising: obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • the network function identifier may enable the access node to directly access the network function associated with the network function identifier.
  • the method may further comprise providing a session identifier to the access node.
  • the network function identifier may comprise at least one of: a network address of the network function associated with the network function identifier; and an identifier of a set of network functions that comprises the network function associated with the network function identifier.
  • Obtaining the information elements may comprise receiving the information elements from the network function associated with the network function identifier.
  • Receiving the information elements from the network function associated with the network function identifier may comprise receiving the information elements within a N2 interface message container.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • Providing the information elements to the access node may comprise generating and providing at least one of: an interface protocol data unit session request comprising the information elements from an access and mobility function node to the access node; and a discovery response comprising the information elements from an access and mobility function node to an access node.
  • Obtaining the information elements may further comprise receiving the network function context identifier, the network function identifier and the session identifier in a Nsmf_PDUSession_CreateSMContext Response, and the method may further comprise storing the information elements in a context associated with the identified session.
  • Providing the network function identifier may further comprise including the network function context identifier; and the network function identifier in a N2 PDU session request when receiving a Namf_Communication_N1 N2Message transfer message.
  • the method may further comprise: receiving a Namf_Communication_N1 N2l ⁇ /lessage transfer request containing a session identifier, and providing the network function identifier to the access node associated with the session identified by the session identifier, in response to receiving the Namf_Communication_N1N2Message transfer request.
  • Obtaining information elements may further comprise: receiving the user equipment identifier, the user equipment identifier associated with a first user equipment and the network function identifier; and storing the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
  • the method may further comprise providing a second user equipment identifier associated with the first user equipment to the network function associated with the network function identifier.
  • the user equipment identifier may be a first user equipment identifier and the method may further comprise receiving a discovery request user equipment identifier from the access node, wherein the discovery request may comprise at least one of: a second user equipment identifier; a session identifier; and a type of the network function associated with the network function identifier to discover.
  • the network node may comprise an access and mobility function node.
  • the network function associated with the network function identifier may comprise a Session Management Function.
  • a method for an access node or entity comprising: receiving, information elements comprising: a network function identifier; and employing the information elements to directly access a network function associated with the network function identifier.
  • the network function identifier may comprise at least one of: a network address of the network function; and an identifier of a set of network functions that comprises the network function.
  • the information elements may further comprise a network function context identifier; and employing the information elements to directly access the network function associated with the network function identifier may further comprise providing the network function context identifier in a request towards the network function.
  • the method may further comprise storing the information elements.
  • the method may further comprise forwarding the information elements to a target access node as part of a user equipment context transfer.
  • Receiving the information elements may comprise receiving the information elements from a second network function.
  • Receiving the information elements from the second network function may comprise receiving the information elements according to one of: an interface protocol data unit session request comprising the information elements from an access and mobility function; a user equipment context transfer comprising the information elements from a source access node; and a discovery response comprising the information elements from an access and mobility function node.
  • the method may further comprise requesting discovery of the network function from the second network function, wherein the request for the discovery may comprise at least one of: a user equipment identifier; a session identifier; and a type of the network function to discover.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • Employing the information elements to directly access a network function associated with the network function address/identifier/set identifier may comprise: generating a discovery message comprising the network set identifier and obtaining a response indicating the network function with which to directly communicate; and generating a request to communicate directly with the indicated network function.
  • a method for a Session Management Function or entity comprising: sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • the identifier of the session management function may comprise at least one of: a network address of the session management function and an identifier of a set of session management functions that comprises the session management function.
  • an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: obtain information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and provide the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • the network function identifier may enable the access node to directly access the network function associated with the network function identifier.
  • the apparatus or entity may further be caused to provide a session identifier to the access node.
  • the network function identifier may comprise at least one of: a network address of the network function associated with the network function identifier; and an identifier of a set of network functions that comprises the network function associated with the network function identifier.
  • the apparatus caused to obtain the information elements may be caused to receive the information elements from the network function associated with the network function identifier.
  • the apparatus caused to receive the information elements from the network function associated with the network function identifier may be caused to receive the information elements within a N2 interface message container.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • the apparatus caused to provide the information elements to the access node may be caused to generate and provide at least one of: an interface protocol data unit session request comprising the information elements from an access and mobility function node to the access node; and a discovery response comprising the information elements from an access and mobility function node to an access node.
  • the apparatus caused to obtain the information elements may be further caused to receive the network function context identifier, the network function identifier and the session identifier in a Nsmf_PDUSession_CreateSI ⁇ /IContext Response, and the apparatus may be further caused to store the information elements in a context associated with the identified session.
  • the apparatus caused to provide the network function identifier may be further caused to include the network function context identifier; and the network function identifier in a N2 PDU session request when receiving a Namf_Communication_N1 N2Message transfer message.
  • the apparatus may further be caused to: receive a Namf_Communication_N1N2Message transfer request containing a session identifier, and provide the network function identifier to the access node associated with the session identified by the session identifier, in response to receiving the Namf_Communication_N1 N2l ⁇ /lessage transfer request.
  • the apparatus caused to obtain information elements may be further caused to: receive the user equipment identifier, the user equipment identifier associated with a first user equipment and the network function identifier; and store the user equipment identifier associated with the first user equipment and the network function identifier in a context associated with the identified first user equipment.
  • the apparatus may be further caused to provide a second user equipment identifier associated with the first user equipment to the network function associated with the network function identifier.
  • the user equipment identifier may be a first user equipment identifier and the apparatus may be further caused to receive a discovery request user equipment identifier from the access node, wherein the discovery request may comprise at least one of: a second user equipment identifier; a session identifier; and a type of the network function associated with the network function identifier to discover.
  • the network node may comprise an access and mobility function node.
  • the network function associated with the network function identifier may comprise a Session Management Function.
  • an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: receive, information elements comprising: a network function identifier; and employ the information elements to directly access a network function associated with the network function identifier.
  • the network function identifier may comprise at least one of: a network address of the network function; and an identifier of a set of network functions that comprises the network function.
  • the information elements may further comprise a network function context identifier; and the apparatus caused to employ the information elements to directly access a network function associated with the network function identifier may be further caused to provide the network function context identifier in a request towards the network function.
  • the apparatus may further be caused to store the information elements.
  • the apparatus may be further caused to forward the information elements to a target access node as part of a user equipment context transfer.
  • the apparatus caused to receive the information elements may be caused to receive the information elements from a second network function.
  • the apparatus caused to receive the information elements from the second network function may be caused to receive the information elements according to one of: an interface protocol data unit session request comprising the information elements from an access and mobility function; a user equipment context transfer comprising the information elements from a source access node; and a discovery response comprising the information elements from an access and mobility function node.
  • the apparatus may be further caused to request discovery of the network function from the second network function, wherein the request for the discovery may comprise at least one of: a user equipment identifier; a session identifier; and a type of the network function to discover.
  • the information elements may further comprise a session identifier.
  • the information elements may further comprise binding information.
  • the apparatus caused to employ the information elements to directly access the network function associated with the network function address/identifier/set identifier may be caused to: generate a discovery message comprising the network set identifier and obtain a response indicating the network function with which to directly communicate; and generating a request to communicate directly with the indicated network function.
  • an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: sending a session management container in an Namf_Communication_N1N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • the identifier of the session management function may comprise at least one of: a network address of the session management function and an identifier of a set of session management functions that comprises the session management function.
  • an apparatus comprising: means for obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and means for providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • an access node or entity comprising: means for receiving, information elements comprising: a network function identifier; and means for employing the information elements to directly access a network function associated with the network function identifier.
  • a Session Management Function or entity comprising: means for sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and means for receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • a computer program comprising instructions [or a computer readable medium comprising program instructions] for causing an apparatus, a network node or entity, to perform at least the following: obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • a fourteenth aspect there is provided a computer program comprising instructions [or a computer readable medium comprising program instructions] for causing an apparatus, an access node or entity, to perform at least the following: receiving, information elements comprising: a network function identifier associated with a network function; and employing the information elements to directly access the network function associated with the network function identifier.
  • a computer program comprising instructions [or a computer readable medium comprising program instructions] for causing an apparatus, a Session Management Function or entity, to perform at least the following: sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus, a network node or entity, to perform at least the following: obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus, an access node or entity, to perform at least the following: receiving, information elements comprising: a network function identifier associated with a network function; and employing the information elements to directly access the network function associated with the network function identifier.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus, a Session Management Function or entity, to perform at least the following: sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • an apparatus comprising: obtaining circuitry configured to obtain information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and providing circuitry configured to provide the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.
  • an access node or entity comprising: receiving circuitry configured to receive, information elements comprising: a network function identifier associated with a network function; and employing circuitry configured to employ the information elements to directly access the network function associated with the network function identifier.
  • a Session Management Function or entity comprising: sending circuitry configured to send a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving circuitry configured to receive a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • a computer readable medium comprising program instructions for causing an apparatus, a network node or entity, to perform at least the following: obtaining information elements comprising: a network function context identifier and/or user equipment identifier; and a network function identifier associated with a network function identifier; and providing the network function identifier to an access node associated with the user equipment identifier and/or with a session matching the network function context identifier.:
  • a computer readable medium comprising program instructions for causing an apparatus, an access node or entity, to perform at least the following: receiving, information elements comprising: a network function identifier associated with a network function; and employing the information elements to directly access the network function associated with the network function identifier.
  • a computer readable medium comprising program instructions for causing an apparatus, a Session Management Function or entity, to perform at least the following: sending a session management container in an Namf_Communication_N1 N2Messge transfer request, wherein the session management container comprises an identifier of a session, an identifier of a session management function and an identifier of a session management context associated with the session; and receiving a request related to the session from an access node, wherein the request comprises the identifier of the session management context.
  • An apparatus comprising means for performing the actions of the method as described above.
  • An apparatus configured to perform the actions of the method as described above.
  • a computer program comprising program instructions for causing a computer to perform the method as described above.
  • a computer program product stored on a medium may cause an apparatus to perform the method as described herein.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any of the preceding aspects.
  • Figure 1 shows a representation of a network system according to some example embodiments
  • Figure 2 shows a representation of a control apparatus according to some example embodiments
  • Figure 3 shows a representation of an apparatus according to some example embodiments
  • FIGS 4 and 5 show flow diagrams of N2 service management signalling according to example embodiments
  • Figure 6 shows a flow diagram of Xn based handover with a direct request towards the service management function according to some example embodiments.
  • Figure 7 shows a flow diagram of signalling to enable direct service-based requests towards 5G core network functions according to some example embodiments.
  • FIG 1 shows a schematic representation of a 5G system (5GS).
  • the 5GS may be comprised by a terminal or user equipment (UE), a 5G radio access network (5GRAN) or next generation radio access network (NG-RAN), a 5G core network (5GC), one or more application function (AF) and one or more data networks (DN).
  • UE terminal or user equipment
  • 5GRAN 5G radio access network
  • NG-RAN next generation radio access network
  • GC 5G core network
  • AF application function
  • DN data networks
  • the 5G-RAN may comprise one or more gNodeB (GNB), one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions, or one or more next generation eNodeB (NGENB).
  • GNB gNodeB
  • NGENB next generation eNodeB
  • the 5GC may comprise for instance the following entities: Network Slice Selection Function (NSSF); Network Exposure Function (NEF); Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM); Application Function (AF); Authentication Server Function (AUSF); an Access and Mobility Management Function (AMF); and Session Management Function (SMF).
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Repository Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • AF Application Function
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • Session Management Function SMF
  • Access to the 5GC may be done more generally via a 5G access network (3G-AN), that can corresponding to a 3GPP access (e.g. NR or LTE access with a 5G-RAN) or a non- 3GPP access (e.g. untrusted WLAN access via an N3IWF, trusted WLAN access via a TNGF, wirelines access via a W-AGF).
  • 3G-AN 5G access network
  • a 3GPP access e.g. NR or LTE access with a 5G-RAN
  • a non- 3GPP access e.g. untrusted WLAN access via an N3IWF, trusted WLAN access via a TNGF, wirelines access via a W-AGF.
  • FIG. 2 illustrates an example of a control apparatus 200 for controlling a function of the 5GRAN or the 5GC as illustrated on Figure 1.
  • the control apparatus may comprise at least one random access memory (RAM) 211a, at least on read only memory (ROM) 211b, at least one processor 212, 213 and an input/output interface 214.
  • the at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211 b.
  • the at least one processor 212, 213 may be configured to execute an appropriate software code 215.
  • the software code 215 may for example allow to perform one or more steps to perform one or more of the present aspects.
  • the software code 215 may be stored in the ROM 211b.
  • the control apparatus 200 may be interconnected with another control apparatus 200 controlling another function of the 5GRAN or the 5GC.
  • each function of the 5GRAN or the 5GC comprises a control apparatus 200.
  • two or more functions of the 5GRAN or the 5GC may share a control apparatus.
  • FIG 3 illustrates an example of a terminal 300, such as the terminal illustrated on Figure 1.
  • the terminal 300 may be provided by any device capable of sending and receiving radio signals.
  • Non-limiting examples comprise a user equipment, 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), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (loT) type communication device or any combinations of these or the like.
  • the terminal 300 may provide, for example, communication of data for carrying communications.
  • the communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.
  • the terminal 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 mobile device.
  • the terminal 300 may be provided with at least one processor 301 , at least one memory ROM 302a, at least one RAM 302b 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 at least one processor 301 is coupled to the RAM 311a and the ROM 311b.
  • the at least one processor 301 may be configured to execute an appropriate software code 308.
  • the software code 308 may for example allow to perform one or more of the present aspects.
  • the software code 308 may be stored in the ROM 311b.
  • the processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 304.
  • the device may optionally have a user interface such as key pad 305, touch sensitive screen or pad, combinations thereof or the like.
  • a display, a speaker and a microphone may be provided depending on the type of the device.
  • the AMF Access and Mobility Management Function
  • 5G core 5G core
  • RAN Radio Access Network
  • the AMF is configured to exhibit granular service-based HTTP based interfaces and can also employ services offered by other core network functions (NFs).
  • NFs core network functions
  • the AMF is configured to employ non-service-based interfaces, for example a N2 interface between AMF and the RAN.
  • the AMF is configured to hide the permanent UE identifier (Subscriber Permanent Identifier - SUPI) used in the 5GC from RAN nodes and instead assigns a temporary and changeable identifier, which can be designated the AMF UE Next Generation Access Protocol (NGAP) ID, for the purpose of identifying a UE in communication with RAN nodes over the NG interface.
  • NGAP Next Generation Access Protocol
  • 3GPP TS 23.502 and the associated figures within the document show examples such as PDU Session establishment, where the AMF / NAS handler is aware of the PDU Sessions and the SMFs serving them.
  • the document shows a Xn-based handover, where only N2 signalling is able to bypass the NAS handler.
  • N2-based handover since no NAS signalling is involved, the NAS handler could be entirely bypassed.
  • the AMF I NAS handler is aware of the PDU Sessions and SMFs serving them.
  • the AMF acts as a mere forwarding node for messages from RAN nodes towards the SMF during handover procedures.
  • the purpose of the Namf_Communication_N2lnfoNotify service operation in TS 23.502 is to notify a particular N2 message information towards the CN NFs that have subscribed for the specific information.
  • the purpose of the Namf_Communication_N 1 MessageNotify service operation in TS 23.502 (typically subscribed by the SMF) is to notify N1 message received from the UE to a destination CN NF.
  • the concept as discussed in the embodiments herein aims to enable the RAN nodes to directly address services that might be offered by the NFs in the 5GC.
  • the concept as such can be one in which the RAN nodes are able to discover the 5GC NFs handling a UE context or PDU session, and the 5GC NFs configured to understand the provided RAN specific PDU identities.
  • the RAN nodes are configured to be able to discover the MB-SMF handling a particular MBS session and directly communicate with associated MB-SMF.
  • an AMF receives event subscriptions, the AMF is configured to send event subscriptions to RAN nodes, RAN nodes are then configured to send the event notifications directly to core nodes.
  • a SMF is known to add event subscription information into a N2 container that is transparently forwarded by the AMF.
  • the embodiments enable direct signalling between the RAN and 5GC NFs for optimization of procedures with frequent signalling.
  • frequent signalling are Service Requests and Xn-based Handover procedure and are discussed in further detail below, but it would be understood that the methods and functions discussed below could be applied to other procedures without substantive inventive input.
  • N2 SM related signalling (which would be applicable also for path switch requests that occur during X2 handover).
  • SMF handling a PDU session the signalling from AMF to an AN (access network) node related to PDU session is extended with a SMF ID/address/set ID, possible binding information for SMF handling PDU session, and SM context ID related to PDU session.
  • the AMF furthermore can then be configured to provide the SM context ID, SMF ID/address/set ID, and possible binding information as received in previous signalling received from the SMF for a given UE and PDU Session.
  • the SMF is configured to employ the existing Namf_Communication_N1N2 Message Transfer AMF service (or the Nsmf_Create SM Context response or Nsmf_Update SM Context response) and provide, within the encapsulated N2 SM information, SM context ID, SMF set ID, and/or SMF instance ID, and/or SMF URI/SMF address as defined for the aforementioned existing services, and the AMF is configured to forward the N2 SM information transparently to the AN node.
  • the existing Namf_Communication_N1N2 Message Transfer AMF service or the Nsmf_Create SM Context response or Nsmf_Update SM Context response
  • the AMF is configured to forward the N2 SM information transparently to the AN node.
  • the AN node is configured to employ the received SMF ID/address/set ID, SM Context ID and/or information derived from the received binding information to address the subsequent PDU session related service based (SB) session management (SM) requests directly towards the given SMF for that particular UE and PDU session, also including the SM context ID identifying the SM context in the SMF (that identifies, among others, the UE).
  • SB PDU session related service based
  • SM session management
  • the network can be configured for PDU session related signalling (and also for non PDU session related signalling)
  • the AN node is configured to query the AMF for a core network function (NF) serving a UE and/or PDU session and uses the received information about the core NF to address the subsequent UE context or PDU session related service based requests directly towards that particular core NF.
  • NF core network function
  • the signalling from the AMF to the AN node related to the PDU session is extended with information such as a SMF ID/address/set ID, possible binding info for SMF handling PDU session, and SM context ID (e.g. URI of the SM Context resource in the SMF) related to the PDU session.
  • a SMF ID/address/set ID e.g. a SMF ID/address/set ID
  • possible binding info for SMF handling PDU session e.g. URI of the SM Context resource in the SMF
  • N2_PDU_Session_Request_Message related to NGAP PDU Session Resource Setup Request message can be extended as shown in the example with respect to Figure 4 below.
  • the AMF can be configured to provide the SM context ID, SMF ID/address/set ID, and binding information as received in previous signaling received from the SMF.
  • the AMF can also in some embodiments include an identifier that can identify the given UE - N2SMAP_SM_UEID. This identifier can help the SMF locate the context for the UE based on the message. For instance, as received in the
  • the AN node can furthermore be configured to store and employ the received SMF ID/address/set ID, information derived from the received binding information and/or SM Context ID to address subsequent PDU session related requests directly towards the SMF.
  • the AN node may use the information to query the NRF for the profile of SMFs. Additionally in some embodiments the AN node can be configured to delegate the SMF discovery to an SCP and provide the information as discovery parameters towards the SCP. In some embodiments the AN node is configured to route the N2 SM signalling based on the received binding information (SMF ID/address/set ID) and it includes binding information equivalent to the received binding information in the request towards the SMF for a given UE and PDU Session. The AN node, in some embodiments furthermore is configured to include the received SM context ID in the request towards the SMF (for instance as part of the request URI of the Nsmf_PDUSession service).
  • the SMF in some embodiments can furthermore use the SM context ID in the request to identify the SM context and is configured to reply directly to the AN node sending the request.
  • the first request from the AN node to the SMF can include an AN Context ID, which can be used by the SMF and the AN node as a reference for the context of the UE in the AN node for any following exchanges.
  • Nsmf_PDUSession_UpdateSMContext Request during N2-based HO to be sent directly by T-RAN rather than by T-AMF;
  • Nsmf_PDUSession_UpdateSMContext Request during service request to be sent directly by (R)AN rather than by AMF;
  • PDU Session Resource Modify messages such as described within 3GPP TS 38.413.
  • N2 interface SM related signalling towards a SMF from a AN node for example the direct messaging according to some embodiments and in particular the example of a Nsmf_PDUSession_UpdateSMContext Request.
  • the service request can for example be a Nsmf_PDUSession_CreateSMContext Request.
  • the operation of generating and transmitting the service request is shown in Figure 4 by step 401.
  • the 5GC NF 406 (for example the SMF) can then generate the service response which can in some embodiments comprise the binding information such as shown in Figure 4 by step 403.
  • the AMF 402 can then be configured to store the UE context, the 5GC NF ID and possible information. Additionally in some embodiments the AMF is configured to store the SM context for the PDU session.
  • the AMF storing operation is shown in Figure 4 by step 405.
  • a PDU session establishment/modification/service request is shown by the block 407.
  • the request process according to some embodiments comprises the 5GC NF 406 is configured to generate and transmit to the AMF 402 a Namf_Communication_N1 N2MessageTransfer (PDU session ID) message as shown in Figure 4 by step 409.
  • the AMF is then configured to store the PDU session ID handled by the SMF as shown in Figure 4 by step 411.
  • the AMF can then be configured to generate a N2 PDU session request which is passed to the AN node 400, for example the gNB, as shown in Figure 4 by step 413.
  • the N2 PDU session request which can be designated N2_PDU_Session_Request_Message, related to a NGAP PDU Session Resource Setup Request message can be extended, also triggered by the registration procedure.
  • the AMF can be configured not only to provide the PDU session ID but also provide a SM context ID, SMF ID/address/set ID.
  • the message is extended to provide binding information as received in previous signalling from the SMF.
  • the message comprises a SM context ID.
  • the AN node 400 can furthermore be configured to cache or store for the PDU session ID values such as the SMF Address/ID/Set ID, the possible binding info, the SM context ID and the PDU session ID as shown in Figure 4 by step 415.
  • PDU session ID values such as the SMF Address/ID/Set ID, the possible binding info, the SM context ID and the PDU session ID as shown in Figure 4 by step 415.
  • the AN node 400 can be configured to generate and transmit to a NRF (network repository function) 404 a NRF_NF_discovery message as shown in Figure 4 by step 417.
  • the NRF 404 then can be configured to generate and transmit back to the AN node
  • the discovery response message NRF_NF discovery response message in some embodiments comprises SMF profile information (SMF profile 1 , SMF profile 2,).
  • the AN node 400 can then be configured to generate and transmit SM related SB requests directly to the 5GC NF 406 as shown in Figure 4 by step 421.
  • SM related SB requests directly to the 5GC NF 406 as shown in Figure 4 by step 421.
  • a Msmf_PDUSession_UpdateSMContext Request containing a SM context ID value.
  • the 5GC NF 406, for example the SMF, is configured to generate and transmit back to the AN node 400 a SM related SB reply as shown in Figure 4 by step 423.
  • the SMF can be configured to use the existing Namf_Communication_N1N2 Message Transfer AMF service and provide within the N2 SM information (shown as N2 container in step 509 of Figure 5) SM context information, SMF set ID, and/or SMF instance ID, and/or SMF URI/SMF address, and optionally N2SMAP_SM_UEID.
  • the N2 SM information can in some embodiments be forwarded transparently to the AN node by the AMF.
  • the SMF includes these I E(s) (Information Elements) to enable the AN node to reach the SMF directly and a particular SM context (for the particular UE and PDU session) in the SMF in subsequent SM related signalling.
  • the SMF ID/address/set ID, binding information and SM context ID can be included in the NGAP PDU Session Resource Setup Request Transfer container IE by the SMF to be directly relayed by AMF to the AN node.
  • the service request can for example be a Nsmf_PDUSession_CreateSMContext Request.
  • the operation of generating and transmitting the service request is shown in Figure 5 by step 501.
  • the 5GC NF 406 (for example the SMF) can then generate the service response which can in some embodiments comprise the binding information such as shown in Figure 5 by step 503.
  • the AMF 402 can then be configured to store the UE context, the 5GC NF ID and possible information. Additionally in some embodiments the AMF is configured to store the SM context for the PDU session.
  • the AMF storing operation is shown in Figure 5 by step 505.
  • a PDU session establishment/modification/service request according to some embodiments is shown by the block 507.
  • the request process comprises the 5GC NF 406 is configured to generate and transmit to the AMF 402 the IE(s) within a Namf_Communication_N1 N2MessageT ransfer message as shown in Figure 5 by step 509.
  • the Namf_Communication_N1 N2MessageTransfer comprises a N2_Container which comprises a N2 PDU Session Request.
  • the N2 PDU Session Request can comprise the information elements such as the PDU session ID, SMF address/ID/set ID, N2SM_SM_UEID, and SM context ID.
  • the AMF 402 is then configured to store the PDU session ID handled by the SMF as shown in Figure 5 by step 511 .
  • the A F 402 can then be configured to generate a N2 PDU session request which is passed to the AN node 400, for example the gNB, as shown in Figure 5 by step 513.
  • the N2 PDU session request which can be designated N2_PDU_Session_Request_Message, related to a NGAP PDU Session Resource Setup Request message can be extended.
  • the AMF can be configured not only to provide the PDU session ID but also provide a SMF ID/address/set ID and the N2SM_SM_UEID and SM context ID.
  • the AN node 400 can furthermore be configured to cache or store for the PDU session ID values such as the SMF Address/ID/Set ID, the NGAP_SM_UEID and PDU session ID as part of the UE context information as shown in Figure 5 by step 515.
  • PDU session ID values such as the SMF Address/ID/Set ID, the NGAP_SM_UEID and PDU session ID as part of the UE context information as shown in Figure 5 by step 515.
  • the AN node 400 can be configured to generate and transmit to a NRF (network repository function) 404 a NRF_NF_discovery message as shown in Figure 5 by step 517.
  • the NRF 404 then can be configured to generate and transmit back to the AN node 400 a discovery response message as shown in Figure 5 by step 519.
  • the discover response message NRF_NF discovery response message in some embodiments comprises SMF profile information (SMF profile 1 , SMF profile 2,).
  • the AN node 400 can then be configured to generate and transmit SM related SB requests directly to the 5GC NF 406 as shown in Figure 5 by step 521.
  • SM related SB requests directly to the 5GC NF 406 as shown in Figure 5 by step 521.
  • a Msmf_PDUSession_UpdateSMContext Request containing a SM context ID value.
  • the 5GC NF 406, for example the SMF, is configured to generate and transmit back to the AN node 400 a SM related SB reply as shown in Figure 5 by step 523.
  • the N2 SM information also contains information that enables the AN node to send Notifications to the SMF.
  • the information comprises notification URI and possibly notification correlation ID information and furthermore information about events for which the SMF desires notifications.
  • the AN node can in these embodiments uses this information when any of the indicated events occur to send notifications to the indicated URI.
  • the possible notifications correlation ID is also included in those notifications. This enables the AN node to transfer the following messages directly towards the SMF (for instance using a similar service operation as the Namf_Communication_N2lnfoNotify service operation but with AN node as service producer):
  • a source NG-RAN transfers over an Xn interface the stored SM context ID along with SMF identifiers (SMF ID and/or SMF address and/or SMF URI and/or SMF set ID and possibly additional information derived from the received binding information) to the target NG-RAN.
  • SMF ID and/or SMF address and/or SMF URI and/or SMF set ID and possibly additional information derived from the received binding information to the target NG-RAN.
  • the Target NG-RAN then is configured to use the received context and binding information to reach the SMF directly.
  • the UE 600, source NG-RAN 602 and the target NG-RAN 604 participate in handover preparation as shown in Figure 6 by step 601.
  • the handover execution process comprises a forwarding of data from the source NG-RAN 602 to the target NG-RAN 604 as shown in Figure 6 by step 605.
  • the handover execution process can comprise furthermore a generation and transmitting of a RAN usage report from the source NG-RAN 602 to the A F 606 as shown in Figure 6 by step 607.
  • the UE context transfer message comprising the cached SMF Set ID, SMF Instance and the SM context ID can then be generated and passed from the source NG-RAN 602 to the target NG-RAN 604 as shown in Figure 6 by step 609.
  • the target NG-RAN 604 as shown in Figure 6 by step 611 is configured to implement a NRF interaction for SMF discovery using the SMF set ID/instance information.
  • the target NG-RAN 604 is configured to generate and pass, to the discovered SMF(s) 608, the Nsmf_PDUSession_UpdateSMContext Request comprising the SM context ID as shown in Figure 6 by step 613.
  • the SMF(s) 608 can then be configured to generate and transmit to the UPF(s) 610 a N4 Session Modification Request as shown in Figure 6 by step 615.
  • the UPF(s) 610 furthermore can be configured to generate and transmit back to the SMF(s) 608 a N4 Session Modification Response as shown in Figure 6 by step 617 in response to the N4 Session Modification Request.
  • the UPF(s) 610 is furthermore configured to generate and transmit to the Source NG- RAN 602 an N3 End Marker as shown in Figure 6 by step 619.
  • the Source NG-RAN 602 forwards the received N3 End Marker to the Target NG-RAN 604 as shown in Figure 6 by step 621.
  • the UPF(s) 610 furthermore can be configured to generate and transmit to the UE 600 downlink data as shown in Figure 6 by step 623.
  • the SMF(s) 608 is configured to generate and transmit to the A F 606 a Nsmf_PDUSession_UpdateSMContext Response as shown in Figure 6 by step 625.
  • the AMF 606 can then be configured to transmit to the Target NG-RAN 604 a N2 Path Switch Request Acknowledgement message as shown in Figure 6 by step 627.
  • Target NG-RAN 604 is configured to generate and pass to the Source NG-RAN 602 a release resources message as shown in Figure 6 by step 629.
  • the registration procedure between the UE 600, Source NG-RAN 602, Target NG- RAN 604 and the AMF 606 are implemented and completed as shown in Figure 6 by step 631.
  • PDU related direct signalling (which would also be suitable for non PDU session related signalling) can implement an introduced AMF Core network function discovery service operation.
  • This operation can have as an input: UE temporary entity or UE context identifier in the AMF, e.g. AMF UE NGAP ID or GUTI, possibly network function type (e.g. SMF, SMSF, PCF, LMF, AMF) and/or service type, for SMF, PDU session ID.
  • AMF UE temporary entity or UE context identifier in the AMF
  • UE context identifier e.g. AMF UE NGAP ID or GUTI
  • possibly network function type e.g. SMF, SMSF, PCF, LMF, AMF
  • service type for SMF, PDU session ID.
  • this operation can have as an output: NF ID/address/set ID, possible binding info of 5GC NF/service of requested type handling UE context/PDU session, possible SM context ID for PDU session.
  • the AN node can then be configured to use the received NF ID/address/set ID and information derived from the received binding information to address subsequent UE context or PDU session related service based (SB) requests directly towards the 5GC NF.
  • SB PDU session related service based
  • the AN node can use the information to query the profile of 5GC NFs at the NRF.
  • the AN node can furthermore delegate the 5GC NF discovery to an SCP and provide the information as discovery parameters.
  • the AN node can furthermore include binding information equivalent to the received binding information in the request towards the 5GC NF.
  • the SB request contains an AMF UE NGAP ID, it also contains an AMF ID.
  • the following operations can, in some embodiments, be introduced to enable 5GC NFs to interpret AMF UE NGAP ID as UE ID received in direct signalling from AN nodes.
  • service operation can in some embodiments comprise as an input a AMF UE NGAP ID and output SUPI.
  • access can be restricted to 5GC network elements.
  • the 5GC NF addresses the AMF which was previously indicated in the SB request that included the AMF UE NGAP ID to invoke this service operation.
  • the AMF can be configured to signal the AMF UE NGAP ID identifier in existing interaction with 5GC NF to avoid the need for an inquiry.
  • the AMF 402 has stored the UE context as shown in Figure 7 by step 701 .
  • the AMF 402 is also configured to communicate with the 5GC NF, for example the SMF, 406 based on a Service request or response (comprising the AMF UE NGAP ID) as shown in Figure 7 by step 703.
  • the AN node 400 is configured to generate and transmit to the AMF 402 an AMF_CMF_discovery message as shown in Figure 7 by step 705.
  • the discovery message comprises AMF UE NGAP ID or GUTI, and also possibly the PDU session ID, NF type and/or service type).
  • the AMF 402 is then configured to respond to the AMF_CMF_discovery message with a suitable AMF_CMF_discovery response message as shown in Figure 7 by step 707.
  • the response message in some embodiments comprises 5GC NF address/ID/Set ID, binding info, and possible SM context ID.
  • the AN node 400 furthermore is configured to cache or store the 5GC NF for AMF UE NGAP ID and possible PDU session as shown in Figure 7 by step 709.
  • the AN node 400 can be configured to generate and transmit to a NRF (network repository function) 404 a NRF_NF_discovery message as shown in Figure 7 by step 711.
  • the NRF 404 then can be configured to generate and transmit back to the AN node 400 a discovery response message as shown in Figure 7 by step 713.
  • the discovery response message NRF_NF discovery response message in some embodiments comprises SMF profile information (SMF profile 1 , SMF profile 2,).
  • the AN node 400 can then be configured to generate and transmit SMF requests directly to the 5GC NF 406 as shown in Figure 7 by step 715.
  • the 5GC NF (SMF) 406 is then configured to generate and transmit an AMF_UE_ldentity_Map message to the AMF 402 the which is shown in Figure 7 by step 717.
  • the AMF_UE_ldentity_Map message in some embodiments comprises the AMF UE NGAP ID information element.
  • the AMF 402 is then configured to generate and transmit a response to the AMF_UE_ldentity_Map message in the form of an AMF_US_ldentity_Map response to the 5GC NF (SMF) 406 which is shown in Figure 7 by step 719.
  • the AMF_UE_ldentity_Map response message in some embodiments comprises the SUPI (Subscriber permanent identifier) element.
  • the 5GC NF (SMF) 406 can then be configured to cache or store the SUPI for the AMF US NGAP ID as shown in Figure 7 by step 721.
  • MBS multicast and broadcast services
  • the extension to MBS can be implemented by the methods as described above and with following changes:
  • the embodiments allow SMF (or other Core NF) services to be directly addressed by the AN node. Furthermore in some embodiments the SMF session management service or notifications can be directly invoked by gNB. This can be particularly advantageous during a transition phase where only some direct communication is enabled, and AMF is configured to know the gNB from other interactions. Additionally as discussed above the embodiments provide an improved Xn-based handover process.
  • apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception.
  • apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure 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 the disclosure is not limited thereto. While various aspects of the disclosure 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.
  • circuitry may refer to one or more or all of the following:
  • 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 and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware.
  • Computer software or program also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks.
  • a computer program product may comprise one or more computerexecutable components which, when the program is run, are configured to carry out embodiments.
  • the one or more computer-executable components may be at least one software code or portions of it.
  • any blocks of the logic flow as in the Figures 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 physical media is a non-transitory media.
  • 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 comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
  • Embodiments of the disclosure may be practiced in various components such as integrated circuit modules.
  • the design of integrated circuits is by and large a highly automated process.
  • Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

Landscapes

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

Abstract

L'invention concerne un appareil, un nœud ou entité de réseau, comprenant des moyens pour : obtenir des éléments d'informations comprenant : un identifiant de contexte de fonction réseau et/ou un identifiant d'équipement utilisateur ; et un identifiant de fonction réseau associé à une fonction réseau ; et fournir l'identifiant de fonction réseau à un nœud d'accès associé à l'identifiant d'équipement utilisateur et/ou à une session correspondant à l'identifiant de contexte de fonction réseau.
PCT/EP2022/056963 2022-03-17 2022-03-17 Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g WO2023174542A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/056963 WO2023174542A1 (fr) 2022-03-17 2022-03-17 Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/056963 WO2023174542A1 (fr) 2022-03-17 2022-03-17 Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g

Publications (1)

Publication Number Publication Date
WO2023174542A1 true WO2023174542A1 (fr) 2023-09-21

Family

ID=81308457

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/056963 WO2023174542A1 (fr) 2022-03-17 2022-03-17 Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d'accès radio à destination de fonctions de réseau central 5g

Country Status (1)

Country Link
WO (1) WO2023174542A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020145523A1 (fr) * 2019-01-09 2020-07-16 엘지전자 주식회사 Méthode de gestion d'ebi
WO2020185949A2 (fr) * 2019-03-11 2020-09-17 Ryu Jinsook Radiomessagerie de dispositif sans fil par le biais d'un réseau sans fil
WO2021066346A1 (fr) * 2019-10-02 2021-04-08 엘지전자 주식회사 Procédé permettant de déplacer une session de pdu sur un accès non 3gpp vers un accès 3gpp

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020145523A1 (fr) * 2019-01-09 2020-07-16 엘지전자 주식회사 Méthode de gestion d'ebi
WO2020185949A2 (fr) * 2019-03-11 2020-09-17 Ryu Jinsook Radiomessagerie de dispositif sans fil par le biais d'un réseau sans fil
WO2021066346A1 (fr) * 2019-10-02 2021-04-08 엘지전자 주식회사 Procédé permettant de déplacer une session de pdu sur un accès non 3gpp vers un accès 3gpp
EP4021075A1 (fr) * 2019-10-02 2022-06-29 LG Electronics Inc. Procédé permettant de déplacer une session de pdu sur un accès non 3gpp vers un accès 3gpp

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.501
3GPP TS 38.413
LG ELECTRONICS: "Clarification on handover failure between 3GPP and non-3GPP accesses", vol. SA WG2, no. Split, Croatia; 20191014 - 20191018, 4 October 2019 (2019-10-04), XP051795709, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_135_Split/Docs/S2-1909614.zip> [retrieved on 20191004] *

Similar Documents

Publication Publication Date Title
EP3790305B1 (fr) Gestion de session pour des sessions permanentes
US11979937B2 (en) Method, apparatus and computer program
CN112637785B (zh) 用于多播传输的方法和装置
US20230413214A1 (en) Method, apparatus and computer program
JP2023518344A (ja) ユーザ装置またはｐｐｄｕセッションにサービスする分散ネットワーク機能の露出と発見
US20230035572A1 (en) Scope parameter for binding indication
WO2020200057A1 (fr) Procédé et appareil de communication
WO2022033680A1 (fr) Transfert intercellulaire d&#39;un équipement utilisateur (ue) recevant des données de multidiffusion vers un nœud d&#39;accès ne prenant pas en charge la multidiffusion
WO2023174542A1 (fr) Autorisation de demandes basées sur un service direct en provenance de nœuds de réseau d&#39;accès radio à destination de fonctions de réseau central 5g
CN113438692B (zh) 传输模式转换指示方法、接入网设备及终端设备
EP4011105A1 (fr) Amélioration de données d&#39;abonnement de sélection de tranche
US11895580B2 (en) Method, apparatus and computer program to provide data to a network function consumer
EP4149077A1 (fr) Appareil, procédé et programme informatique
US20220264286A1 (en) Apparatus, method, and computer program
EP4398610A1 (fr) Procédé et appareil de communication
US20220330140A1 (en) Edge computing
CN114642079B (zh) 通信方法及装置
US20230276339A1 (en) Analytics and path selection
WO2023103575A1 (fr) Procédé de communication de diffusion/multidiffusion et appareil associé
US20220022023A1 (en) Method and Apparatus for Selecting Session Management Network Element
EP4255001A1 (fr) Mécanisme d&#39;accès à des données d&#39;abonnement
WO2023143252A1 (fr) Procédé de service temporel et appareil de communication
CA3233839A1 (fr) Procede et appareil de communication
US20220353668A1 (en) Methods, network function nodes and computer readable media for contents communication management
WO2024033315A1 (fr) Mise à jour de configuration de cellule conditionnelle

Legal Events

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

Ref document number: 22716350

Country of ref document: EP

Kind code of ref document: A1