WO2021063657A1 - Fourniture d'informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées - Google Patents

Fourniture d'informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées Download PDF

Info

Publication number
WO2021063657A1
WO2021063657A1 PCT/EP2020/075587 EP2020075587W WO2021063657A1 WO 2021063657 A1 WO2021063657 A1 WO 2021063657A1 EP 2020075587 W EP2020075587 W EP 2020075587W WO 2021063657 A1 WO2021063657 A1 WO 2021063657A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
service
endpoint
subscription
information
Prior art date
Application number
PCT/EP2020/075587
Other languages
English (en)
Inventor
Maria Cruz BARTOLOMÉ RODRIGO
Jesus-Angel De-Gregorio-Rodriguez
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2021063657A1 publication Critical patent/WO2021063657A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • Embodiments herein relate to a first node, a second node and methods therein. In some aspects, they relate to handling a subscription, which subscription applies to notifications of data changes related to a Network Function (NF) service offered by the second node.
  • NF Network Function
  • wireless devices also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipment (UE), communicate via a Local Area Network such as a Wi-Fi network or a Radio Access Network (RAN) to one or more Core Networks (CN).
  • STA mobile stations, stations
  • UE User Equipment
  • RAN Radio Access Network
  • CN Core Networks
  • the RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a W-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5G.
  • a service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.
  • the Evolved Packet System also called a Fourth Generation (4G) network
  • EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • E- UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs used in 3G networks.
  • the functions of a 3G RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network.
  • the RAN of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs.
  • the E-UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.
  • Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. The performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel.
  • MIMO Multiple-Input Multiple-Output
  • Such systems and/or related techniques are commonly referred to as MIMO.
  • the 5G networks architecture is defined from 3GPP Release 15 and Release 16 see 3GPP TS 23.502, V16.2.1 Procedures for the 5G System; Stage 2 and 3GPP TS 23.501, V16.2.0, System Architecture for the 5G System; Stage 2.
  • a key aspect in which the 3GPP networks will differ, starting from Release 15, is that the CN architecture is mostly built around a Service Based Architecture (SBA) paradigm. That is, there will be a network domain, basically the CN, in which different functional components are defined as services, which are self-contained functionalities that may be changed and modified in an isolated manner, without affecting the others. Services may be deployed as part of a Network Function (NF).
  • SBA Service Based Architecture
  • 5GC 5th Generation Core Network
  • DB proprietary database
  • a service may be deployed as a member of an NF Service Set, while an NF may be deployed as a member of an NF Set.
  • Definitions in 3GPP TS 23.501 , V16.2.0, System Architecture for the 5G System; Stage 2 are as follows:
  • - NF Set A group of interchangeable NF instances of the same type, supporting the same services and the same network slice(s).
  • the NF instances in the same NF Set may be geographically distributed but have access to the same context.
  • NF profile of NF instance in a Network Repository Function includes:
  • a NF instance may be deployed such that several NF instances are present within an NF Set to provide distribution, redundancy and scalability together as a set of NF instances. The same is also supported for NF Services. This may be achieved when the equivalent NFs and NF Services share the same context data or by NF/NF Service Context Transfer procedures as specified in clause 4.26 of TS 23.502 in 3GPP TS 29.503, V16.0.0, 5G System; Unified Data Management Services; Stage 3.
  • a NF may be replaced by an alternative NF within the same NF Set in case of scenarios such as failure, load balancing, load re-balancing.”
  • the NF producer instance is the NF instance which hosts the NF Service Producer. When the NF producer instance is not available, another NF producer instance within the same NF Set is selected.
  • the NF Service consumer or SCP selects another NF Service instance of the same NF Service Set within the NF instance, if available. Otherwise the NF Service consumer or SCP selects a different NF instance within the same NF Set.
  • a consumer within an NF service framework is an SBA service that consumes and/or makes use of another SBA service, by a request-response operation, including subscription request and response.
  • a consumer may act as a notification receiver, as it receives a notification request sent by another service.
  • a Producer within an NF service framework is an SBA service that provides an action, procedure, execution, functionality, and the like, to be consumed and/or used by another SBA service.
  • a Control Plane NF_B e.g. a NF Service Producer
  • NF_A e.g. a NF Service Consumer
  • NF_B provides an NF service based on the request by NF_A.
  • NF_B may in turn consume NF services from other NFs.
  • communication is one to one between two NFs, consumer and producer, and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. This is illustrated in Figure 1 which relates to Figure 7.1.2-1: "Request- response" NF Service illustration.
  • a Control Plane NF_A e.g. a NF Service Consumer, subscribes to a NF Service offered by another Control Plane NF_B, e.g. NF Service Producer. Multiple Control Plane NFs may subscribe to the same Control Plane NF Service.
  • NF_B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service.
  • the subscription request shall include the notification endpoint, e.g. the notification Uniform Resource Locator (URL), of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to.
  • the subscription request may include a notification request for periodic updates or a notification triggered through certain events, e.g., the information requested gets changed or reaches a certain threshold.
  • the subscription for notification may be performed through one of the following ways:
  • the subscription for notification is included as part of another NF service operation of the same NF Service.
  • a Control Plane NF_A may also subscribe to a NF Service offered by Control Plane NF_B on behalf of Control Plane NF_C, i.e. it may request the NF Service Producer to send the event notification to another consumer.
  • NF_A includes the notification endpoint of the NF_C in the subscription request.
  • NF_A may also additionally include the notification endpoint of NF A associated with a subscription change related Event ID(s), e.g. a Subscription Correlation ID Change, in the subscription request, so that NF_A may receive the notification of the subscription change related event.
  • Event ID(s) e.g. a Subscription Correlation ID Change
  • Routing of the messages for the NF interaction mechanisms above may be direct, as shown in Figures 1-3 relating to Figures 7.1.2-1 to 7.1.2-3 respectively, or indirect.
  • an SCP is employed by the NF service consumer.
  • the SCP routes messages between NF service consumers and NF service producers and may perform discovery and associated selection of the NF service producer on behalf of a NF service consumer.
  • Figure 4 relating to Figure 7.1.2-4 shows the principle for a request-response interaction
  • Figure 5 relating to Figure 7.1.2-5 shows an example of a subscribe-notify interaction.
  • Figure 4 relating to Figure 7.1.2-4 illustrates a request response using indirect communication
  • Figure 5 relating to Figure 7.1.2-5 illustrates subscribe-notify using indirect communication.
  • the subscribe request and notify request may be routed by different SCPs.
  • the notification endpoint is standardized as the so called “callback U R I ” , for example, 3GPP TS 29.503, V16.0.0, 5G System; Unified Data Management Services; Stage 3:
  • FIG 6 relating to Figure 5.2.2.3.2-1 shows a scenario where the NF service consumer sends a request to the User Data Management (UDM), also known as Unified Data Management, to subscribe to notifications of data changes.
  • UDM User Data Management
  • the request contains a notification endpoint, e.g. callback, which is defined as a Uniform Resource Identifier (URI) and the URI of the monitored resource.
  • URI Uniform Resource Identifier
  • Figure 6 relating to Figure 5.2.2.3.2-1 illustrates NF service consumer subscribes to notifications.
  • the operation POST e.g. subscription operation, includes the “creation” of the callbacks for the future notification, see marked in underlined:
  • the ' ⁇ request.bodv#/callbackReference ⁇ ' takes the “callbackReference” from the request and uses it as the notification URI.
  • the “callbackReference” is the way to link by the NF consumer, i.e. the sender of the subscription request, the specific subscription, e.g. for a specific SMContexld, to a specific notification received. That is, the callbackReference included in the subscription request, by e.g. Session Management Function (SMF) for an SMContextldl , is the way for the SMF to identify that the request received in that callbackReference is a notification for that specific SMContextldl .
  • Session Management Function SMF
  • the notification endpoint e.g. a notification target address
  • a notification correlation id it may be required not only a way to identify the notification endpoint, e.g. a notification target address, but also a way to correlate the notification received with the corresponding subscription request, e.g. a notification correlation id.
  • SM Session Management
  • the Notify SM Context Status service operation may be used by the SMF to notify the NF Service Consumer about the status of an SM context related to a Protocol Data Unit (PDU) session, e.g. when the SM context is released, in the SMF, or the Visited Session Management Function (V-SMF) for Home Routed (HR) roaming scenarios.
  • PDU Protocol Data Unit
  • V-SMF Visited Session Management Function
  • the SMF shall notify the NF Service Consumer by using the Hypertext Transfer Protocol (HTTP) POST method as shown in Figure 7 relating to Figure 5.2.2.5.1-1.
  • HTTP Hypertext Transfer Protocol
  • Figure 7 relating to Figure 5.2.2.5.1-1 illustrates SM context status notification:
  • the SMF may send a POST request, e.g. comprising a SmContextStatusNotification to the SM Context Status callback reference provided by the NF Service Consumer during the subscription to this notification.
  • the payload body of the POST request shall contain the notification payload.
  • SmContextStatusNotification only includes status info and nothing else that may be used by the receiver to identify to which subscription the notification corresponds.
  • a producer may include an indication in the request to a certain level of expected binding of the subsequent requests, i.e. to the NF service instance Id, NF service Id, NF instance Id or NF set Id. See clause 4.17.12 in 3GPP TS 23.502, V16.2.1 Procedures for the 5G System; Stage 2.
  • Binding may be created as part of the implicit subscription request.
  • the response to the service request that creates the implicit subscription may include a binding indication as in clause 4.17.12.2.
  • bindings may be used.
  • the description in 4.17.12.1 applies for Figure 8 relating to Figure 4.17.12.4.-1.
  • Figure 8 relating to Figure 4.17.12.4-1 thus illustrates binding for subscription requests.
  • the information included in a subscription to notification, by a NF service consumer, that is expected to identify the notification receiver is not enough for the NF service producer to be able to identify the notification receiver in case the callback URI provided is not reachable for any reason. Then, the notification request and/or response does not benefit for the resiliency principles defined in 3GPP Release-16, that may allow the consumer to select an alternative producer within the NF service set and/or the NF Set.
  • the problem is similar for any type of subscription, e.g. implicit or explicit.
  • An object of embodiments herein is to improve the performance of a core network.
  • the object is achieved by a method performed by a second node, e.g. for handling a subscription.
  • the subscription applies to notifications of data changes related to a NF service offered by the second node.
  • the second node operates in a core network.
  • the second node receives a request for the subscription from a first node, which operates in the core network.
  • the request for the subscription comprises a first information identifying a first endpoint to which notifications related to the requested subscription shall be sent, and a second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second node identifies, based on the second information, an alternative endpoint to which the notifications related to the requested subscription shall be sent.
  • the object is achieved by a method performed by a first node, e.g. for assisting a second node, for handling a subscription, which subscription applies to notifications of data changes related to a NF service offered by the second node, which first node and second node operate in a core network.
  • the first node sends to the second node, a request for a subscription.
  • the request for the subscription comprises a first information identifying a first endpoint to which notifications related to the requested subscription shall be sent, and a second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second information assists the second node to identify an alternative endpoint to which the notifications related to the requested subscription shall be sent when the first endpoint is not accessible via the first information.
  • the object is achieved by a second node, e.g. configured to handle a subscription, which subscription is applicable to notifications of data changes related to a NF service to be offered by the second node, which second node is operable in a core network.
  • the second node is configured to receive from a first node, which operates in the core network, a request for the subscription.
  • the request for the subscription is adapted to comprise a first information adapted to identify a first endpoint to which notifications related to the requested subscription shall be sent, and a second information adapted to comprise any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second node is adapted to, when the first endpoint is not accessible via the first information, identify, based on the second information, an alternative endpoint to which the notifications related to the requested subscription shall be sent.
  • the object is achieved by a first node, e.g. configured to assist a second node, to handle a subscription, which subscription is applicable to notifications of data changes related to a NF service offered by the second node, which first node and second node are operable in a core network.
  • the first node is configured to send to the second node, a request for a subscription.
  • the request for the subscription is adapted to comprise a first information adapted to identify a first endpoint to which notifications related to the requested subscription shall be sent, and a second information adapted to comprise any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second information is adapted to assist the second node to identify an alternative endpoint to which the notifications related to the requested subscription shall be sent when the first endpoint is not accessible via the first information.
  • an alternative endpoint is identified to which the notifications related to the requested subscription shall be sent when the first endpoint is not available. This results in an improved performance of a core network.
  • Figure 1 is a schematic sequence diagram illustrating a request-response scenario of an NF service.
  • Figure 2 is a schematic sequence diagram illustrating a subscribe-notify scenario of an NF service.
  • Figure 3 is a schematic sequence diagram illustrating a subscribe-notify scenario of an NF service.
  • Figure 4 is a schematic sequence diagram illustrating a principle for a request- response interaction.
  • Figure 5 is a schematic sequence diagram illustrating an example of a subscribe- notify interaction.
  • Figure 6 is a schematic sequence diagram illustrating a scenario where a NF service consumer sends a request to subscribe to notifications of data changes
  • Figure 7 is a schematic sequence diagram illustrating SM context status notification
  • Figure 8 is a schematic sequence diagram illustrating binding for subscription requests.
  • Figure 9 is a schematic block diagram illustrating embodiments of a wireless communications network.
  • Figure 10 is a flowchart depicting embodiments of a method in a second node
  • Figure 11 is a flowchart depicting embodiments of a method in a first node
  • Figure 12 is a schematic sequence diagram illustrating subscribe, unsubscribe and notify operations according to some embodiments
  • Figure 13 is a schematic sequence diagram illustrating a subscription to notification procedure with indirect communication according to some embodiments
  • Figure 14 is a schematic sequence diagram illustrating a notification procedure with indirect communication according to some embodiments
  • Figure 15 is a schematic sequence diagram illustrating binding for implicit subscription requests according to some embodiments.
  • Figure 16 is a schematic sequence diagram illustrating binding for notification requests according to some embodiments.
  • Figure 18ab are schematic block diagram illustrating embodiments of a first node.
  • Figure 19 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.
  • Figure 20 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.
  • Figures 21-24 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • a subscription to notification only includes the notification endpoint, e.g. URI.
  • the subscription to notification does not include the information to allow re-selection of a new receiver for the expected notification. More information should be included in the subscription request to achieve reliability for the notifications.
  • notifications requests will fail, without the option to re-select an alternative destination.
  • the information to identify the notification receiver should include information to allow a producer to discover corresponding default notification endpoints, from the NRF.
  • Embodiments herein relate to an endpoint sometimes referred to as a consumer, subscribing to notifications of data changes related to an NF service, also referred to as a producer.
  • An NF service provides services such as e.g. Nudm_SDM, Nudm_UECM and Npcf_SMPolicyControl service.
  • an alternative notification endpoint e.g. Notification Target Address, also referred to as an alternative notification receiver and as an alternative endpoint, in an effective way in case an intended notification endpoint such as a provided callback URI, also named as callback Reference, or Notification Target Address is not accessible.
  • the alternative endpoint may e.g.
  • NF instance Id a NF instance Id and optionally a NF service name or alternatively, if applicable a NF Set Id or a NF Service Set Id, of the expected notification receiver NF to receive the notification.
  • this information allows a producer, i.e. a sender of the notification, to discover from an NRF the NF instances within the NF Set Id, for that NF type. All, or a part, of the NF instances within the NF Set may include a default callback URI.
  • the notification sender may select one NF instance and one applicable default callback URI, configured in that NF instance, to send the notification, that identifies the alternative notification target address. Since all the NF instances in an NF Set may share context data, the new selected NF instance would have the same required information as the original notification receiver in the original callback URI.
  • Embodiments herein also provide to include in the notification request the information that identifies the specific subscription, received in the subscription request it is part of the callback URI the so called Notification Correlation Id), to allow any notification receiver to be able to identify at notification reception, the specific subscription it corresponds to.
  • a binding indication when used herein is a value and/or attribute that determines the possible bindings, e.g. whether the preferred alternative producer instance would be within the same NF Set, or NF service Set, or NF instance, or just the same producer instance.
  • a binding concept when used herein means a way to provide the means to a consumer to identify a preferred alternative producer instance in case of re-selection.
  • the consumer may include the NF type and, if applicable, NF Set Id and/or the NF service name and, if applicable, NF service Set Id. Additionally, if the notification receiver is defined as a service in the consumer, which may be optional, then the NF service name plus optionally the NF service Set Id may be included.
  • Embodiments herein may be applicable to both direct and indirect mode.
  • a SCP may need to modify the notification receiver information in the subscription before forwarding it to the producer, to include the SCP as the notification receiver, but also include the original notification receiver. This original notification receiver may be included in the notification response, to allow the SCP to forward the notification to the expected receiver.
  • An advantage with embodiments herein is that they provide the means to allow that a notification reaches an equivalent notification address target, such as an alternative endpoint, if applicable in the same NF set and/or NF service set, and correlate the notification request with the corresponding subscription. This is required when the first endpoint is not accessible such as in case of failure of the originally provided callback URI, on the contrary the notification fails. This may also be required to achieve load balancing or load re-balancing in the sending of the notifications, even in case the callback URI is still working, which is provided by some embodiments herein. Then, embodiments herein provide reliability for the notification requests, applying the NF Set concept defined above.
  • binding concept i.e. consumer requests may be bound to a specific NF service instance, NF service set, NF instance or NF Set, for either implicit, explicit, or default notifications, is supported.
  • the binding concept is also applicable to notification requests.
  • a further advantage with embodiments herein is that they provide a mechanism to work with both direct and indirect communication.
  • Embodiments herein relate to wireless communication networks in general.
  • Figure 9 is a schematic overview depicting a wireless communications network 100.
  • the wireless communications network 100 comprises one or more RANs and one or more CNs, such as a CN 105.
  • the wireless communications network 100 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • LTE Long Term Evolution
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • GSM/EDGE Global System for Mobile communications/enhanced Data rate for GSM Evolution
  • WMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • Embodiments herein relate to recent
  • wireless devices e.g. one or more UEs 120 also referred to as a device, an loT device, a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and/or a wireless terminals, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN).
  • AN e.g. RAN
  • CN core networks
  • wireless device is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.
  • MTC Machine Type Communication
  • D2D Device to Device
  • the wireless communications network 100 comprises a radio network node 110 providing radio coverage in one or more cells, such as a cell 11, which may also be referred to as a beam or a beam group of beams.
  • the radio network node 110 may be a NG-RAN node, transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g.
  • WLAN Wireless Local Area Network
  • AP STA Access Point Station
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device within the service area served by the network node 110 depending e.g. on the first radio access technology and terminology used.
  • the radio network node 110 may be referred to as a serving radio network node and communicates with the UE 120 with Downlink (DL) transmissions to the UE 120 and Uplink (UL) transmissions from the UE 120.
  • DL Downlink
  • UL Uplink
  • a number of network nodes operate in the CN 105 such as an EPC, e.g. a first node 131 and a second node 140.
  • the CN 105 further comprises end points also referred to as NF service consumers, such as first endpoints 131, and 132, and an alternative endpoint 135.
  • the first node 131 is also a first endpoint and is in this case also referred to as the first endpoint 131.
  • the first node 131 is acting for or is handling another endpoint which endpoint in that case is the first end point 132.
  • Methods herein may be performed by the first node 131 and the second node 140.
  • a Distributed Node (DN) and functionality e.g. comprised in a cloud 160 as shown in Figure 9, may be used for performing or partly performing the methods herein.
  • Example embodiments of a method performed by the second node 140, e.g. for handling a subscription will now be described with reference to a flowchart depicted in Figure 10.
  • the subscription applies to notifications of data changes related to a NF service offered by the second node 140.
  • the second node 140 operates in the core network 105.
  • the first node 131 is in some embodiments referred to as a consumer.
  • the second node 140 is in some embodiments referred to as a producer.
  • the method comprises the following actions, which actions may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes. Action 1001
  • the subscription may e.g. be for notifications on changes and/or modifications of data and may include deletion.
  • the data may be owned, stored and/or managed by a producer service or by an NF.
  • the second node 140 receives a request for the subscription from the first node 131, which operates in the core network 105.
  • the request for the subscription comprises a first information identifying the first endpoint 131, 132 to which notifications related to the requested subscription shall be sent.
  • the request for the subscription also comprises a second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the NF type may also be referred to as NF name and both terms may be used for a same or similar purpose.
  • the second information may be used when the first endpoint 131, 132 is not accessible via the first information. This is to be able to identify the alternative endpoint 135 to which the notifications related to the requested subscription shall be sent. In the second information:
  • the NF type may be of an NF that is part of an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF service name may be of an NF service that is part of an NF service Set Id to which the first endpoint 131, 132 belongs, and/or the NF Set Id allows identifying an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF instance Id may allow finding an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF Service Set Id allows identifying an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF instance Id and/or the NF service name may allow finding the NF service Set Id to which the first endpoint 131, 132 belongs, and wherein the alternative endpoint 135 and first endpoint 131, 132 may share data related to the requested subscription.
  • the reselection may be performed thanks to that multiple default notification endpoints are registered and/or configured at NF instance level, or at service level within an NF instance. According to some other embodiments the reselection may be performed when there is not a subscription message, that is, for default subscriptions.
  • the expectation is to have multiple default notification endpoints defined at service level in that NF.
  • NF Set Id there may also be multiple instances at the NF instance Id and/or service level, but there are multiple NF instances in the Set, with possibly multiple default notification endpoints.
  • NF service Set Id there may also be multiple instances at service level.
  • the first node 131 is the first endpoint 131.
  • the second node 140 sends to the identified alternative endpoint 135 notifications related to the requested subscription.
  • the second node 140 receives the request for the subscription from the first node 131 via the Service Communication Proxy (SCP) node 173, and wherein the request further comprises a third information identifying the SCP node 173 via which, the notifications related to the requested subscription shall be sent.
  • SCP Service Communication Proxy
  • the NF type e.g. NF name
  • the notification endpoint e.g. the first information identifying the first endpoint 131, included in the subscription, may not identify neither an NF nor an NF service, just an URI.
  • embodiments herein may allow reselection. For that it may be required to select another endpoint, e.g. the alternative endpoint 135.
  • It may be another endpoint, e.g. any NF, when former first endpoint data is lost, but it provides at least an alternative re-selection.
  • An advantageous case is to select the alternative endpoint 135 that has access to the same data as the first endpoint 131. This may occur when the alternative endpoint is included in the same NF instance such as a default notification endpoint defined in the NF profile, or the same NF service instance, or in another NF instance or NF service instance that belong to the same Set.
  • the second node 140 identifies the alternative endpoint 135 to which the notifications related to the requested subscription shall be sent. This is based on the second information.
  • the first endpoint 131, 132 may not be accessible due to e.g. a network failure or TCP failure.
  • the second node 140 may perform one or multiple searches to the NRF, and filter the results. This may be performed by interaction with the NRF, using the discovery mechanisms, e.g. by Nnrf_NFDiscovery_Request service operation.
  • the alternative endpoint 135 may be expected to be, registered to the NRF or configured in the NRF, default notification endpoint at either NF instance level or service instance level, within an NF. This may be either for the same NF instance Id provided in the subscription, or NF instance Id and NF service name, or for any NF instance or NF service instance within the corresponding NF Set Id or NF service set Id.
  • Default notification endpoints that are registered and/or configured in the NRF, may thus be used for notification re-selection.
  • the default configuration is registered and/or configured to support reselection: that is, multiple of them may be registered and/or configured at one or different levels, e.g. NF instance, NF service instance, NF Set Id, NF service set Id, this may be used to provide notification re-selection for default subscriptions.
  • the default subscription may not count on a subscription message, or request message with subscription information, in which new info is included. On the contrary, it may be enough with the configuration, and the producer may then select the default notification endpoint. Then, if multiple default notification endpoints are provided and even at different levels, the producer is able to re select.
  • the second node 140 may then send notifications related to the requested subscription to the identified alternative endpoint 135.
  • Example embodiments of a method performed by the first node 131, e.g. for assisting the second node 140 in handling a subscription will now be described with reference to the flowchart depicted in Figure 11.
  • the subscription applies to notifications of data changes related to an NF service offered by the second node 140.
  • the first node 131 is in some embodiments referred to as a consumer.
  • the second node 140 is in some embodiments referred to as a producer.
  • the method comprises the following actions, which actions may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.
  • the first node 131 sends to the second node 140, a request for a subscription.
  • the subscription may e.g. be for notifications on changes and/or modifications of data and may include deletion.
  • the data may be owned, stored and/or managed by a producer service or by an NF.
  • the request for the subscription comprises the first information identifying the first endpoint 131, 132 to which notifications related to the requested subscription shall be sent.
  • the request for the subscription further comprises the second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second information assists the second node 140 to identify an alternative endpoint 135 to which the notifications related to the requested subscription shall be sent when the first endpoint 131, 132 is not accessible via the first information.
  • the NF type may be of an NF that is part of an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF service name may be of an NF service that is part of an NF service Set Id to which the first endpoint 131, 132 belongs, and/or the NF Set Id allows identifying an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF instance Id may allow finding an NF Set Id to which the first endpoint 131,
  • the NF Service Set Id allows identifying an NF Set Id to which the first endpoint 131, 132 belongs, and/or the NF instance Id and/or NF service name may allow finding an NF service Set Id to which the first endpoint 131, 132 belongs, and wherein the alternative endpoint 135 and first endpoint 131, 132 may share data related to the requested subscription.
  • the first node 131 is the first endpoint 131.
  • the first node 131 sends the request for the subscription to the second node 140 via the Service Communication Proxy (SCP) node 173.
  • SCP Service Communication Proxy
  • the first node 131 when the first endpoint 131 is not accessible by the second node 140 via the first information, the first node 131 obtains notifications related to the requested subscription from the alternative endpoint 135. This is possible as the second information assists the second node 140 to identify the alternative endpoint 135.
  • NF Service Consumer or consumer
  • NF Service Producer or producer
  • NF Service Consumer - NF Service Producer interactions The end-to-end interaction between two NFs, e.g. a consumer such as the first node 131 and a producer such as the second node 140, within this NF service framework follows two mechanisms, irrespective of whether direct communication or indirect communication is used:
  • a Control Plane NF_B e.g. the NF Service Producer such as the second node 140 is requested by another Control Plane NF_A, e.g. the NF Service Consumer, such as the first node 131, to provide a certain NF service, which either performs an action or provides information or both.
  • NF_B provides an NF service based on the request by NF_A. In order to fulfil the request, NF_B may in turn consume NF services from other NFs.
  • communication is one to one between two NFs, e.g. consumer and producer, and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. This is illustrated in Figure 1 which relates to Figure 7.1.2-1.
  • the Control Plane NF_A e.g. the NF Service Consumer, subscribes to the NF Service offered by another Control Plane NF_B, e.g. the NF Service Producer. Multiple Control Plane NFs may subscribe to the same Control Plane NF Service. NF_B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service.
  • the subscription request may include the notification endpoint, e.g. the first endpoint 131, 132, i.e. the notification target address, and a Notification Correlation ID, e.g. the notification URL, of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to.
  • the notification endpoint URL may be constructed by both the notification endpoint and the Notification Correlation ID.
  • the NF Service Consumer may also add the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id and/or the NF Service Set Id, which may be used by the NF Service Producer to discover an alternative default notification endpoint, e.g. the alternative endpoint 135.
  • the producer will use both the notification endpoint and the Notification Correlation ID when sending a Notify to the NF Service Consumer.
  • the subscription request may include notification request for periodic updates or notification triggered through certain events, e.g., the information requested gets changed and/or reaches certain threshold.
  • the subscription for notification may be performed through one of the following ways:
  • Implicit subscription The subscription for notification is included as part of another NF service operation of the same NF Service;
  • the Control Plane NF_A may also subscribe to the NF Service offered by the Control Plane NF_B on behalf of a Control Plane NF_C, i.e. it requests the NF Service Producer to send the event notification to another consumer.
  • the NF_A includes the notification endpoint, i.e. the notification target address, and the Notification Correlation ID, e.g. the notification URL, of the NF_C in the subscription request.
  • the NF_A may also additionally include the notification endpoint and a Notification Correlation ID of the NF_A associated with subscription change related Event ID(s), e.g. Subscription Correlation ID Change, in the subscription request, so that the NF_A ma receive the notification of the subscription change related event.
  • the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id may be included, to allow the NF Service Producer to discover alternative default notification endpoints, e.g. the alternative endpoint 135.
  • Routing of the messages for the NF interaction mechanisms above may be direct, as shown in the Figures 1-3 relating to Figures 7.1.2-1 to 7.1.2-3 respectively, or indirect.
  • the SCP is employed by the NF service consumer.
  • the SCP routes messages between NF service consumers and NF service producers and may perform discovery and associated selection of the NF service producer on behalf of the NF service consumer.
  • Figure 4 relating to Figure 7.1.2-4 shows the principle for a request-response interaction
  • Figure 5 relating to Figure 7.1.2-5 shows an example of a subscribe-notify interaction.
  • the subscribe request and notify request may be routed by different SCPs.
  • the NF Service Consumer may add either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id to allow the NF service producer to discover alternative notification endpoints, such as the alternative endpoint 135.
  • These notification endpoints are default notification endpoints that the NF Service Consumer may register in the NRF as part of the NF profile.
  • the default notification endpoints may be either on NF level, or NF service level. In case the provided notification endpoint by the NF Service Consumer to the NF
  • the NF Service Producer may discover and use a default notification endpoint. In this case, the NF Service Producer may select a default notification endpoint within the constructed NF, NF service, NF Set and/or NF Service set based on the information included in the subscription.
  • the subscription to notification in the prior-art, only includes the so called notification endpoint e.g. the first endpoint 131.
  • the subscription to notification does not include the information to allow re-selection of a new receiver for the expected notification.
  • Subscription to notifications with indirect communication requires to insert the SCP as a notification receiver in the flow. Binding may apply to notification requests.
  • Binding for subscription requests is updated to consider re-selection.
  • Subscription request operations are updated to include attributes for re selection.
  • the first node 131 is referred to as NF Service Consumer or consumer and the second node 140 is referred to as NF Service Producer or producer.
  • FIG. 12 shows Namf_EventExposure_Subscribe, Unsubscribe and Notify operations according to some embodiments.
  • the operations are used by the NF to subscribe to notifications and to explicitly cancel a previous subscription.
  • Cancelling is performed by sending an Namf_EventExposure_UnSubscribe request identifying Subscription Correlation ID.
  • the notification steps 3 and 4 are not applicable in a cancellation case. If the AMF receives a monitoring event subscription for roaming UEs and l-NEF is deployed as defined in clause 6.2.5a of 3GPP TS 23.501 , V16.2.0, System Architecture for the 5G System; Stage 2, clause 4.15.3.2.3a applies after step 2.
  • Step 1 The NEF 170 sends a request to subscribe to one or more Event ID(s) in the AMF 171. This is performed by sending the Namf_EventExposure_Subscribe request.
  • the NEF 170 may be the same NF subscribing to receive the event notification reports, i.e. the Event Receiving NF 172, or it may be a different NF.
  • the NEF 170 subscribes itself as the Event Receiving NF for one or several Event ID(s), it provides its notification target address and Notification Correlation Id for each related event.
  • the NEF 170 subscribes on behalf of another NF, i.e. Event Receiving NF 172, for one or several Event ID(s), it provides the notification target address and Notification Correlation Id of the Event Receiving NF 172. Additionally, the NEF 170 provides its own notification target address and Notification Correlation Id, to assure that the NEF 170 may receive the notification of subscription change related event, e.g. Subscription Correlation
  • Event reporting information defines the type of reporting requested. If the reporting event subscription is authorized by the AMF 171, the AMF 171 records the association of the event trigger and the requester identity.
  • Step 2 The AMF 171 acknowledges the execution of the Namf_EventExposure_Subscribe response.
  • Step 3 This step is conditional and depends on the event.
  • the AMF 171 detects that the monitored event occurs and sends the event report by means of the Namf_EventExposure_Notify message, to the notification endpoint, e.g. the first endpoint 131, of the Event Receiving NF 172.
  • Step 4 This step is conditional and depends on the event.
  • the AMF 171 detects that the subscription change related event occurs, e.g. a Subscription Correlation ID change due to AMF reallocation.
  • the AMF 171 sends the event report by means of Namf_EventExposure_Notify message to the NEF 170. Subscription to notifications with indirect communication
  • the subscription to notification procedure with indirect communication is illustrated in Figure 13 and comprises the following steps:
  • the NF service consumer e.g. the first node 131, shown as NF-A Consumer in Figure 13, sends the subscription request via the SCP 173, by indirect communication.
  • the request includes the expected notification endpoint, e.g. the first endpoint 131, i.e. the request comprises the notification target address and the Notification Correlation ID, and additionally, the NF type and, if applicable, the NF Set Id and/or the NF service type and, if applicable, the NF Service Set Id may be included to identify alternative default notification endpoints, e.g. the alternative endpoint 135.
  • the expected notification receiver may be either the NF-A Consumer or the NF-A Consumer may subscribe on behalf of another NF, see clause 5.21.3.X in 3GPP TS 23.501, V16.2.0, System Architecture for the 5G System; Stage 2.
  • Step 2 The SCP 173 defines itself as the notification endpoint.
  • Step 3 The SCP 173 forwards the subscription request with the new notification receiver information, including the original notification receiver information, to the second node 140, shown as NF-B Producer in Figure 13.
  • Step 4 The NF-B Producer sends the subscription response to the SCP 173.
  • Step 5 The SCP 173 forwards the subscription response to the NF Consumer.
  • the notification procedure with indirect communication is illustrated in Figure 14 and comprises the following steps:
  • the NF-B Producer e.g. the second node 140, sends the notification request via the SCP 173, by indirect communication.
  • the request includes the information of the original notification receiver as provided during the subscription to the notification procedure.
  • the notification reguest may include subscription information to allow the NF- consumer, e.g. the first node 131, shown as NF-X Consumer in Figure 14, to identify to which specific subscription the notification corresponds to.
  • Step 2. The SCP 173 forwards the notification request to the indicated original notification target address, e.g. the first endpoint 131.
  • the information received in Step 1 is used to discover from the NRF any other available default notification endpoint, e.g. the alternative endpoint 135.
  • the alternative notification target address is used to reach the notification receiver.
  • the Notification reguest comprises the Notification Correlation Id.
  • Step 3 The NF-X Consumer sends the Notification response to the SCP 173.
  • Step 4 The SCP 173 then forwards the Notification response to the NF-B Producer.
  • Binding may be created as part of the implicit subscription request.
  • the response to the service request that creates the implicit subscription may include a binding indication as described above.
  • bindings may be used.
  • the first node 131 may initiate a new request to the second node 140, shown as NF Service Producer in Figure 15, with an updated Notification Correlation ID and binding indication.
  • This figure describes an implicit subscription to notifications.
  • the operation request includes the information of the subscription, implicitly in the operation request.
  • the request includes the expected notification endpoint, i.e. Notification Target Address and a Notification Correlation ID, and additionally, either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or NF Service Set Id may be included to identify alternative default notification endpoints.
  • the implicit subscription is created in the producer.
  • the operation response includes resource information plus optional binding indication.
  • Step 3 A subsequent subscription update takes into account the binding indication received in step 2.
  • Step 4. The subscription response may include a binding update or resource information update.
  • Binding for notification requests Binding may be created as part of a subscription request as indicated, in this case, this may be applied for the notification re-selection, which is illustrated in Figure 16:
  • the first node 131 shown as the NF Service Consumer, sends the subscription request comprising the notification endpoint, e.g. the first endpoint 131, the Notification Correlation ID, either the NF instance Id, and optionally the NF service name, or alternatively, if applicable, NF Set Id or NF Service Set Id.
  • the subscription request also comprises the binding indication.
  • the subscription request is sent to the second node 140, shown as NF Service Provider in Figure 16.
  • Step 2 The subscription is created by the NF Service Producer and the Subscription Response is sent from the NF Service Producer to the NF Service Consumer.
  • An NF invokes this service operation to subscribe for the delivery of information contained in a specific N2 message type.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF
  • This service operation is used by an NF to subscribe for AMF Status Change notification.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • the consumer NF uses this service operation to subscribe to or modify event reporting for one UE, a group of UE(s) or any UE.
  • Event ID UE(s) ID, SUPI or Internal Group Identifier or indication that any UE is targeted, (set of) Event ID(s) defined in clause 5.2.2.3.1, Notification Target Address and Notification Correlation ID(s), and Event Reporting Information.
  • Event Filter (s) associated with each Event ID Event Filter(s) are defined in clause 5.2.2.3.1, Subscription Correlation ID, in the case of modification of the event subscription, Expiry time.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • Output, Required When the subscription is accepted: Subscription Correlation ID, required for management of this subscription, Expiry time, required if the subscription may be expired based on the operator's policy.
  • the NF consumer subscribes to the event notification by invoking Namf_EventExposure to the AMF.
  • the AMF allocates a Subscription Correlation ID for the subscription and responds to the consumer NF with the Subscription Correlation ID.
  • UE ID identifies the UE, SUPI and/or GPSI.
  • the Event ID see clause 4.15.1, identifies the events that the NF consumer is interested in.
  • the Subscription Correlation ID is unique within the AMF Set.
  • the (set of) Event ID(s), Notification Target Address and Notification Correlation ID helps the Event Receiving NF to co-relate a notification against a corresponding event subscription for the indicated Event ID.
  • the NF consumer In the case that the NF consumer subscribes to the AMF on behalf of other NF, the NF consumer include the Notification Target Address and Notification Correlation ID of another NF for the Event ID which is to be notified to another NF directly, and the Notification Target Address and Notification Correlation ID of itself for the Subscription Correlation ID change event. Each Notification Target Address and Notification Correlation ID is associated with the related (set of) Event ID(s). When the Subscription Correlation ID change due to the AMF reallocation, the notification is sent to NF consumer which triggers this subscription.
  • the Event filter may include "AN type(s)" as part of the list of parameter values to match, and it indicates to subscribe the event per Access Type.
  • Event receiving NF ID identifies the NF that shall receive the event reporting.
  • the consumer NF When the consumer NF needs to modify an existing subscription previously created by itself in the AMF, it invokes Namf_EventExposure_Subscribe service operation which contains the Subscription Correlation ID and the new Event Filters with Event ID to the AMF.
  • Service operation name Nudm_UECM_Registration Description: Register UE's serving NF, if NF Type is AMF, Short Message Service Function (SMSF), or Session's serving NF, if NF Type is SMF, on the UDM. This operation implies the following:
  • the authorization if applicable, to register the NF service consumer in UDM for the UE, e.g. based on UE roaming and/or RAT restrictions applicable when NF type is AMF. If this is successful, the NF service consumer is set as a serving NF for the corresponding UE and/or Session context.
  • P-CSCF Proxy-Call Session Control Function
  • NF ID Subscription Permanent Identifier
  • PEI Permanent Equipment Identity
  • NF Type Access Type
  • SMSF Serving Mobility Function
  • PDU Session ID if NF Type is SMF.
  • SMF Data Network Name (DNN) or Indication of Emergency Services
  • PGW-C+SMF FQDN for S5/S8 if the PDU Session supports EPS interworking.
  • NF type is AMF and Access Type is 3GPP access: Registration type.
  • SMSF SMSF MAP address and/or Diameter address. Notification Target Address and Notification Correlation ID.
  • P-CSCF Restoration notification information GUAMI, backup AMF(s), if NF Type is AMF, "Homogeneous Support of IMS Voice over PS Sessions" indication, if NF Type is AMF, UE SRVCC capability, if NF Type is AMF, indication that access is from evolved Packet Data Gateway (ePDG), shall be sent if NF Type is SMF and PDU Session is setup via S2b.
  • Backup AMF(s) sent only once by the AMF to the UDM in its first interaction with the UDM.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • the NF consumer subscribes for updates to UE's Subscriber Data indicated by the 'subscription data type' input.
  • the UDM shall check that the requested consumer is authorized to subscribe to requested updates.
  • Inputs, Required Subscription data type(s), Key for each Subscription data type(s). Notification Target Address and Notification Correlation ID. Inputs, Optional: Data Sub Key(s).
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • the NF consumer subscribes to receive an event, or if the subscription is already defined in UDM, then the subscription is updated.
  • Target of Event Reporting UE(s) ID, SUPI or Generic Public Subscription Identifier (GPSI), Internal Group Identifier or External Group Identifier, or indication that any UE is targeted, Event filter containing the Event ld(s), see clause 4.15.3.1 and Event Reporting Information defined in Table 4.15.1-1. Notification Target Address and Notification Correlation ID.
  • notification receiver information i.e. either the NF instance Id and optionally the Service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • Outputs optional: First corresponding event report is included, if corresponding information is available, see clause 4.15.1, Number of UE if the External Group Identifier and Maximum Number of Reports are included in the inputs.
  • Number of UEs indicates the number of UEs within the group identified by the External Group Identifier.
  • the NEF uses this value to determine whether the monitoring event has been reported for all group member UEs.
  • Npcf_PolicyAuthorization_Subscribe service operation relating to clause 5.2.5.3.6.
  • the target of PCF event reporting the subscription for an individual AF session An UE IP address (IPv4 address or IPv6 prefix) optionally together with a DNN and/or Single Network Slice Selection Assistance Information S-NSSAI), or with a UE ID, SUPI or GPSI.
  • IPv4 address or IPv6 prefix optionally together with a DNN and/or Single Network Slice Selection Assistance Information S-NSSAI
  • S-NSSAI Single Network Slice Selection Assistance Information
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • Npcf_EventExposure_Subscribe service operation relating to clause 5.2.5.7.2.
  • the consumer NF uses this service operation to subscribe to or modify event reporting for a group of UE(s) or any UE accessing a combination of DNN and/or S- NSSAI.
  • NF ID Target of Event Reporting (Internal Group Identifier or indication that any UE accessing a combination of DNN and/or S-NSSAI is targeted, (set of) Event ID(s) defined in clause 5.2.5.7.1, Notification Target Address and Notification Correlation ID, and Event Reporting Information.
  • Event Filter associated with each Event ID.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • the NF consumer subscribes to the event notification by invoking Npcf_EventExposure to the PCF.
  • the PCF allocates a Subscription Correlation ID for the subscription and responds to the consumer NF with the Subscription Correlation ID.
  • Event receiving NF ID identifies the NF that shall receive the event reporting.
  • Inputs required: (Set of) Event ID(s) as specified in clause 4.15.3.1 or Npcf_PolicyAuthorization_Notify and Naf_EventExposure_Subscribe service operation, Target of Event Reporting, GPSI or External Group Identifier, Event Reporting Information, Notification Target Address and Notification Correlation ID.
  • Inputs optional: Event Filter, Subscription Correlation ID, in case of modification of the event subscription, Expiry time.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • PFDF Packet Flow Description Function
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • Nnef_APISupportCapability_Subscribe service operation relating to clause 5.2.6.12.2. Service operation name: Nnef_APISupportCapability_Subscribe
  • the AF subscribes to receive notification about the availability or expected level of support of a service API for a UE or a group of UEs.
  • Inputs required: UE ID or External Group ID, Report Type, one-time report or continuous report. Notification Target Address and Notification Correlation ID.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • the NF consumer subscribes or modifies an existing subscription on analytics information.
  • Inputs required: (Set of) Analytic ID(s), Analytic Filter Information, Target of Analytic Reporting, UEs, External Group Identifier, any UEs, Analytic Reporting Information, Notification Target Address and Notification Correlation ID. These input parameters are detailed in 3GPP TS 23.288.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, the NF Set Id or the NF Service Set Id.
  • NF ID (Set of) Event ID(s) as specified in clause 4.15.3.1, Target of Event Reporting, GPSI or External Group Identifier, Event Reporting Information defined in Table 4.15.1-1, Notification Target Address, Notification Correlation ID, Subscription Correlation ID.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, NF Set Id or NF Service Set id.
  • This service operation is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE.
  • Event Filter(s) associated with each Event ID Event Filter(s) are defined in clause 5.2.8.3.1, Subscription Correlation ID, in case of modification of the event subscription, Expiry time.
  • notification receiver information i.e. either the NF instance Id and optionally the Service name or alternatively, if applicable, NF Set Id or NF Service Set Id.
  • Notification Target Address and Notification Correlation ID is used to correlate Notifications sent by SMF with this subscription.
  • NF service consumer performs the subscription to notification to data modified in the UDR.
  • the events can be changes on existing data, addition of data.
  • Inputs, Required Data Set Identifier as defined in clause 5.2.12.2.1, Notification Target Address and Notification Correlation ID, Event Reporting Information defined in Table 4.15.1-1.
  • Inputs optional: Target of Event Reporting as defined in clause 5.2.12.2.1, Data Subset Identifier(s) as defined in clause 5.2.12.2.1, Subscription Correlation ID, in the case of modification of the event subscription.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable NF Set Id or NF Service Set Id.
  • Nnssf_NSSAIAvailability_Subscribe service operation relating to clause 5.2.16.3.4.
  • This service operation enables a NF Service Consumer, e.g. AMF, to subscribe to a notification of any changes in status of the NSSAI availability information, e.g. S-NSSAI, available per TA and the restricted S-NSSAI(s) per PLMN in that TA in the serving PLMN of the UE, upon this is updated by another AMF.
  • AMF NF Service Consumer
  • Notification Target Address and Notification Correlation ID list of TAIs supported by the NF service consumer, event to be subscribed.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, NF Set Id or NF Service Set Id.
  • Expiry time (if present in the request, may be included in the response based on operator's policy and taking into account the expiry time present in the request, i.e. should be less than or equal to that value; if not present in the request, may be included in the response based on operator's policy. Whatever the case, if not included in the response, this means that the subscription is valid without an expiry time.
  • Outputs optional: A list of TAIs and, for each TAI, the S-NSSAIs supported by the AMF and 5G-AN, and authorized by the NSSF for the TAI, and a list of S-NSSAIs restricted per PLMN for the TAI.
  • Notification Correlation Target (required for the Initial Spending Limit request, Event Filter Information "List of policy counter identifier (s)", Event Reporting Information, continuous reporting.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, NF Set Id or NF Service Set Id.
  • Outputs optional: Pending policy counter statuses and their activation times, for all policy counter(s) available for this subscriber. If list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses and their activation times, per required policy counter identifier in the Event Information, SubscriptionCorrelationld.
  • the NF consumer subscribes for updates to UCMF dictionary entries.
  • the UCMF shall check the requested consumer is authorized to subscribe to requested updates.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, NF Set Id or NF Service Set Id.
  • the consumer NF subscribes the event to collect AF data for UE(s), group of UEs, or any UE, or updates the subscription which is already defined in AF.
  • Target of Event Reporting external UE ID(s), External Group Identifier, or indication that any UE is targeted, (set of) Event ID(s), Notification Target Address and Notification Correlation ID, and Event Reporting Information as defined in Table 4.15.1-1, Expiry time.
  • notification receiver information i.e. either the NF instance Id and optionally the NF service name or alternatively, if applicable, NF Set Id or NF Service Set id.
  • NEF ID is used as NF ID.
  • An NF service consumer sends an explicit subscribe request to a NF service producer.
  • the subscription request includes a notification endpoint, a URI.
  • the producer responds with a subscription ID.
  • the NF service consumer does not indicate which NF service in the NF service consumer the subscribe-notify operation relates to.
  • An NF service consumer includes a notification endpoint, e.g. a callback URI, in a normal request. There is not explicit control of the notification endpoint, e.g. delete or update subscription, and thus there is no need for any subscription ID.
  • the NF service consumer does not indicate which service in the NF service consumer the implicit subscription relates to.
  • the Nsmf_PDUSession_SMContextStatusNotify service operation uses the notification endpoint received when AMF uses the Nsmf_PDUSession_CreateSMContext service operation. SMF does not know which service in AMF that the implicit subscription relates to.
  • the NF has default subscription(s) in the NF profile.
  • the NF may subscribe to different notification types by default. See 3GPP TS 29.510.
  • Each notification type has its own notification endpoint, e.g. URI. This is typically used for event in AMF towards AMF or location services, or data changes in UDR towards UDM.
  • the different NF service producer instances offered by a NF are registered in NRF, and thereby the NF service consumer can identify NF producer service instances within NF instances, NF service set and NF Set, when doing selection and re-selection.
  • the NF service consumer can identify NF producer service instances within NF instances, NF service set and NF Set, when doing selection and re-selection.
  • Notification endpoints for implicit and explicit subscriptions is not part of the NF profile, and thus they cannot be part of a NF service set nor a NF set.
  • Proposal 1 Introduce default notification endpoints in the NF profile.
  • a default endpoint can be on NF level or on NF service level in the NF profile.
  • the NF producer can use a default notification endpoint.
  • NF consumer also communicates under which construct a notification can be found: NF, NF Set, NF Service, NF service set
  • the notifications from a NF is sent without any preceding subscription by a NF consumer, the subscriptions are performed by default and is part of the NF profile. For this case binding is not relevant. However, with the use of NF set and NF service set, a NF should be able to send notifications related to the default subscription to any notification endpoint within the concerned set.
  • Proposal 2 A NF should be able to send a notification related to a default subscription to any notification endpoint within the NF Set and/or NF service set.
  • the second node 140 is configured to handle the subscription, which subscription is applicable to notifications of data changes related to the NF service to be offered by the second node 140, which second node 140 is operable in the core network 10.
  • the second node 140 may comprise an arrangement depicted in Figures 17a and 17b.
  • the second node 140 may comprise an input and output interface 1700 configured to communicate with network nodes such as the second node 140 and the first node 131.
  • the input and output interface may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).
  • the second node 140 may further be configured to, e.g. by means of a receiving unit 1710 in the second node 140, receive from the first node 131, which operates in the core network 105, a request for the subscription, which request for the subscription is adapted to comprise: a first information adapted to identify the first endpoint 131 , 132 to which notifications related to the requested subscription shall be sent, and a second information adapted to comprise any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id.
  • the second node 140 is adapted to, when the first endpoint 131, 132 is not accessible via the first information, identify, based on the second information, an alternative endpoint 135 to which the notifications related to the requested subscription shall be sent.
  • the NF type may be adapted to be of an NF that is part of an NF Set Id to which the first endpoint 131, 132 belongs
  • the NF service name may be adapted to be of an NF service that is part of an NF service Set Id to which the first endpoint 131, 132 belongs
  • the NF instance Id may be adapted to allow finding an NF Set Id to which the first endpoint 131, 132 belongs
  • the NF service instance Id may be adapted to allow finding the NF service Set Id to which the first endpoint 131, 132 belongs
  • the alternative endpoint 135 and first endpoint 131, 132 may be adapted to share data related to the requested subscription.
  • the first node 131 may be adapted to be the first endpoint 131.
  • the second node 140 may further be configured to receive the request for the subscription from the first node 131, by receiving the request via the Service Communication Proxy (SCP) node 173, and wherein the request may further be adapted to comprise a third information to identify the SCP node 173 via which the notifications related to the requested subscription shall be sent.
  • SCP Service Communication Proxy
  • the second node 140 is further configured to, e.g. by means of an identifying unit 1720 in the second node 140, when the first endpoint 131, 132 is not accessible via the first information, identify, based on the second information, an alternative endpoint 135 to which the notifications related to the requested subscription shall be sent.
  • the second node 140 is further configured to, e.g. by means of a sending unit 1730 in the second node 140 send to the identified alternative endpoint 135, notifications related to the requested subscription.
  • the embodiments herein may be implemented through a processor or one or more processors, such as the processor 1740 of a processing circuitry in the the second node 140 depicted in Figure 17a, together with respective computer program code 1760 for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier 1770 carrying computer program code for performing the embodiments herein when being loaded into the second node 140.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the second node 140.
  • the second node 140 may further comprise a memory 1750 comprising one or more memory units.
  • the memory 1750 comprises instructions executable by the processor in second node 140.
  • the memory 1750 is arranged to be used to store e.g. information, notifications, subscriptions, data, configurations, and applications to perform the methods herein when being executed in the second node 140.
  • a computer program 1760 comprises instructions, which when executed by the respective at least one processor 1740, cause the at least one processor 1740 of the second node 140 to perform the actions above.
  • a carrier 1770 comprises the respective computer program 1760, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the units in the second node 140 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the second node 140, that when executed by the respective one or more processors such as the processor described above.
  • processors as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC Application-Specific Integrated Circuitry
  • SoC system-on-a-chip
  • the first node 131 is configured to assist the second node 140, to handle a subscription, which subscription is applicable to notifications of data changes related to a Network Function (NF) service offered by the second node 140, which first node 131 and second node 140 are operable in the core network 105.
  • the first node 131 may comprise an arrangement depicted in Figures 18a and 18b.
  • the first node 131 may comprise an input and output interface 1800 configured to communicate with network nodes such as the first node 131 and the second node 140.
  • the input and output interface may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).
  • the first node 131 is configured to, e.g.
  • a sending unit 1810 in the first node 131 sends to the second node 140, a request for a subscription, which request for the subscription is adapted to comprise: a first information adapted to identify a first endpoint 131, 132 to which notifications related to the requested subscription shall be sent, and a second information adapted to comprise any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id, which second information is adapted to assist the second node 140 to identify the alternative endpoint 135 to which the notifications related to the requested subscription shall be sent when the first endpoint 131, 132 is not accessible via the first information.
  • the NF type may be adapted to be of an NF that is part of an NF Set Id to which the first endpoint 131, 132 belongs
  • the NF service name may be adapted to be of an NF service that is part of an NF service Set Id to which the first endpoint 131, 132 belongs
  • the NF instance Id may be adapted to allow finding an NF Set Id to which the first endpoint 131, 132 belongs
  • the NF service instance Id may be adapted to allow finding an NF service Set Id to which the first endpoint 131, 132 belongs
  • the alternative endpoint 135 and first endpoint 131, 132 may be adapted to share data related to the requested subscription.
  • the first node 131 may be adapted to be the first endpoint 131.
  • the first node 131 is further configured to, e.g. by means of an obtaining unit 1820 in the first node, wherein the first endpoint 131 is not accessible by the second node 140 via the first information, the first node 131 is further configured to obtain from the alternative endpoint 135, notifications adapted to be related to the requested subscription.
  • the embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 1830 of a processing circuitry in the first 131 depicted in Figure 18a, together with respective computer program code 1850 for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier 1860 carrying computer program code for performing the embodiments herein when being loaded into the first node 131.
  • a data carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the first node 131.
  • the first node 131 may further comprise a memory 1840 comprising one or more memory units.
  • the memory 1840 comprises instructions executable by the processor in first node 131.
  • the memory 1840 is arranged to be used to store e.g. information, notifications, subscriptions, data, configurations, data, configurations, and applications to perform the methods herein when being executed in the first node 131.
  • a computer program 1850 comprises instructions, which when executed by the respective at least one processor 1830, cause the at least one processor of the first node 131 to perform the actions above.
  • a respective carrier 1860 comprises the respective computer program 1850, wherein the carrier 1860 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the units in the first node 131 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the first node, that when executed by the respective one or more processors such as the processors described above.
  • processors as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC Application-Specific Integrated Circuitry
  • SoC system-on-a-chip
  • Embodiment 1 A method performed by a second node (140), e.g. for handling a subscription, which subscription applies to notifications of data changes related to a Network Function, NF, service offered by the second node (140), which second node (140) operates in a core network (105), the method comprising: receiving (1001) from a first node (131), which operates in the core network (105), a request for the subscription, which request for the subscription comprises: a first information identifying a first endpoint (131, 132) to which notifications related to the requested subscription shall be sent, and a second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id, and wherein when the first endpoint (131, 132) is not accessible via the first information, identifying (1002) based on the second information, an alternative endpoint (135) to which the notifications related to the requested subscription shall be sent.
  • Embodiment 2 The method according to embodiment 1, wherein the first endpoint (131) is not accessible by the second node (140) via the first information, the method further comprising: sending (1003), toward the alternative endpoint (135), notifications related to the requested subscription.
  • Embodiment 3 The method according to any of the embodiments 1-2, wherein the NF type is of an NF that is part of an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service name is of an NF service that is part of an NF service Set Id to which the first endpoint (131, 132) belongs, and/or the NF Set Id allows identifying an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id allows finding an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF Service Set Id allows identifying an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id and/or NF service name allows finding the NF service Set Id to which the first endpoint (131, 132) belongs, and wherein the alternative endpoint (135) and first endpoint (131, 132) share data related to the requested subscription.
  • Embodiment 4 The method according to any of the embodiments 1-3, wherein the first node (131) is the first endpoint (131).
  • Embodiment 5. The method according to any of the embodiments 1-4, further comprising: sending (1003) to the identified alternative endpoint (135), notifications related to the requested subscription.
  • Embodiment 6 The method according to any of the embodiments 1-5, wherein the receiving (1001) of the request for the subscription from the first node (131), is performed by receiving the request via a Service Communication Proxy, SCP, node (173), and wherein the request further comprises a third information identifying the SCP node (173) via which, the notifications related to the requested subscription shall be sent.
  • Embodiment 7 A computer program (1760) comprising instructions, which when executed by a processor (1740), causes the processor (1740) to perform actions according to any of the embodiments 1-6.
  • Embodiment 8 A carrier (1770) comprising the computer program (1760) of embodiment 7, wherein the carrier (1770) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • Embodiment 9 A method performed by a first node (131), e.g. for assisting a second node (140), in handling a subscription, which subscription applies to notifications of data changes related to a Network Function, NF, service offered by the second node (140), which first node (131) and second node (140) operate in a core network (105), the method comprising: sending (1101) to the second node (140), a request for the subscription, which request for the subscription comprises: a first information identifying a first endpoint (131, 132) to which notifications related to the requested subscription shall be sent, and a second information comprising any one or more out of: an NF type, an NF service name, an NF Set Id, an NF service Set Id, an NF instance Id, and an NF service instance Id, which second information assists the second node (140) to identify an alternative endpoint (135) to which the notifications related to the requested subscription shall be sent when the first endpoint (131 , 132) is not accessible via the first
  • Embodiment 10 The method according to embodiment 9, wherein the NF type is of an NF that is part of an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service name is of an NF service that is part of an NF service Set Id to which the first endpoint (131, 132) belongs, and/or the NF Set Id allows identifying an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id allows finding an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service Set Id allows identifying an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id and/or the NF service name allows finding an NF service Set Id to which the first endpoint (131, 132) belongs, and wherein the alternative endpoint (135) and first endpoint (131, 132) share data related to the requested subscription.
  • Embodiment 11 The method according to any of the embodiments 9-10, wherein the first node (131) is the first endpoint (131).
  • Embodiment 12 The method according to embodiments 9-11, wherein the first endpoint (131) is not accessible by the second node (140) via the first information, the method further comprising: obtaining (1102) from the alternative endpoint (135), notifications related to the requested subscription.
  • Embodiment 13 The method according to any of the embodiments 9-12, wherein the sending (1101) of the request for the subscription to the second node (140), is performed by sending it via a Service Communication Proxy, SCP, node (173).
  • Embodiment 14 A computer program (1850) comprising instructions, which when executed by a processor (1830), causes the processor (1830) to perform actions according to any of the embodiments 9-13.
  • Embodiment 15 A carrier (1860) comprising the computer program (1850) of embodiment 14, wherein the carrier (1860) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • Embodiment 17 The second node (140) according to embodiment 16, wherein the first endpoint (131,132) is not accessible by the second node (140) via the first information, the second node (140) is further configured to: send, toward the alternative endpoint (135), notifications adapted to be related to the requested subscription.
  • Embodiment 18 The second node (140) according to any of the embodiments 16-17, wherein the NF type is adapted to be of an NF that is part of an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service name is adapted to be of an NF service that is part of an NF service Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id is adapted to allow finding an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service instance Id is adapted to allow finding the NF service Set Id to which the first endpoint (131, 132) belongs, and wherein the alternative endpoint (135) and first endpoint (131, 132) are adapted to share data related to the requested subscription.
  • the alternative endpoint (135) and first endpoint (131, 132) are adapted to share data related to the requested subscription.
  • Embodiment 19 The second node (140) according to any of the embodiments 16-18, wherein the first node (131) is adapted to be the first endpoint (131).
  • Embodiment 20 The second node (140) according to any of the embodiments 16-19, further being configured to: send to the identified alternative endpoint (135), notifications related to the requested subscription.
  • Embodiment 21 The second node (140) according to any of the embodiments 16-20, wherein the second node (140) further is configured to receive the request for the subscription from the first node (131), by receiving the request via a Service Communication Proxy, SCP, node (173), and wherein the request is further adapted to comprise a third information to identify the SCP node (173) via which the notifications related to the requested subscription shall be sent.
  • SCP Service Communication Proxy
  • Embodiment 23 The first node (131) according to embodiment 22, wherein the NF type is adapted to be of an NF that is part of an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service name is adapted to be of an NF service that is part of an NF service Set Id to which the first endpoint (131, 132) belongs, and/or the NF instance Id is adapted to allow finding an NF Set Id to which the first endpoint (131, 132) belongs, and/or the NF service instance Id is adapted to allow finding an NF service Set Id to which the first endpoint (131, 132) belongs, and wherein the alternative endpoint (135) and first endpoint (131, 132) are adapted to share data related to the requested subscription.
  • Embodiment 24 The first node (131) according to any of the embodiments 22-23, wherein the first node (131) is adapted to be the first endpoint (131).
  • Embodiment 25 The first node (131) according to embodiments 22-24, wherein the first endpoint (131) is not accessible by the second node (140) via the first information, the first node (131) is further configured to: obtain from the alternative endpoint (135), notifications adapted to be related to the requested subscription.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • a telecommunication network 3210 such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub networks (not shown).
  • the communication system of Figure 19 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 20) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Figure 20) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 20 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 19, respectively.
  • the inner workings of these entities may be as shown in Figure 20 and independently, the surrounding network topology may be that of Figure 19.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the [select the applicable RAN effect: data rate, latency, power consumption] and thereby provide benefits such as [select the applicable corresponding effect on the OTT service: reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime]
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • FIG 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 19 and Figure 20.
  • a host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIG 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 19 and Figure 20.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIG 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 19 and Figure 20.
  • a host computer e.g., a AP STA
  • a UE e.g., a Non-AP STA
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 19 and Figure 20.
  • a base station such as a AP STA
  • a UE such as a Non-AP STA which may be those described with reference to Figure 19 and Figure 20.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Landscapes

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

Abstract

Un procédé réalisé par un second nœud permettant de gérer un abonnement est fourni. L'abonnement s'applique à des notifications de changements de données relatifs à un service NF offert par le second nœud. Le second nœud reçoit (1001) une demande d'abonnement en provenance d'un premier nœud. Le second nœud et le premier nœud fonctionnent dans un réseau central. La demande d'abonnement comprend : De premières informations identifiant un premier point d'extrémité auquel des notifications relatives à l'abonnement demandé doivent être envoyées, et de secondes informations comprenant un ou plusieurs parmi : Un type NF, un nom de service NF, un Id d'ensemble NF, un Id d'ensemble de services NF, un Id d'instance NF, et un Id d'instance de service NF. Lorsque le premier point d'extrémité n'est pas accessible par l'intermédiaire des premières informations, le second nœud identifie (1002), sur la base des secondes informations, un point d'extrémité alternatif (135) auquel les notifications relatives à l'abonnement demandé doivent être envoyées.
PCT/EP2020/075587 2019-10-02 2020-09-14 Fourniture d'informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées WO2021063657A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP19382849 2019-10-02
EP19382849.8 2019-10-02

Publications (1)

Publication Number Publication Date
WO2021063657A1 true WO2021063657A1 (fr) 2021-04-08

Family

ID=72560557

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/075587 WO2021063657A1 (fr) 2019-10-02 2020-09-14 Fourniture d'informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées

Country Status (1)

Country Link
WO (1) WO2021063657A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023006022A1 (fr) * 2021-07-30 2023-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Noeuds de réseau et procédés dans ceux-ci pour faciliter la découverte de fonction de réseau
WO2023038558A1 (fr) * 2021-09-09 2023-03-16 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau et procédé de gestion d'un enregistrement d'instance de fonction réseau dans un réseau de communication
WO2023051918A1 (fr) * 2021-09-30 2023-04-06 Nokia Technologies Oy Gestion d'abonnements à des notifications de changements de données liés à un service de fonction de réseau
WO2023129129A1 (fr) * 2021-12-28 2023-07-06 Rakuten Mobile, Inc. Communication d'architecture de service 5g (sba) sur la base d'un apprentissage automatique

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
"5G System; Session Management Services", 3GPP TS 29.502
"5G System; Unified Data Management Services", 3GPP TS 29.503
"Procedures for the 5G System", 3GPP TS 23.502
"System Architecture for the 5G System", 3GPP TS 23.501
3GPP TSG-SA WG2 MEETING #134 SPLIT
CT4: "LS on Binding indication for subscribe/notify", vol. CT WG3, no. Portoroz, Slovenia; 20191007 - 20191011, 30 September 2019 (2019-09-30), XP051803169, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ct/WG3_interworking_ex-CN3/TSGC3_106_Portoroz/Docs/C3-194193.zip C3-194193.docx> [retrieved on 20190930] *
NOKIA ET AL: "Support of stateless NFs", vol. CT WG4, no. Wroclaw, Poland; 20190826 - 20190830, 8 September 2019 (2019-09-08), XP051781838, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ct/TSG_CT/TSGC_85_Newport_Beach/Docs/CP-192194.zip> [retrieved on 20190908] *
ZTE: "Clarification on Binding Indication and Resource information", vol. SA WG2, no. Split, Croatia; 20191011 - 20191018, 1 October 2019 (2019-10-01), XP051801051, Retrieved from the Internet <URL:https://ftp.3gpp.org/Meetings_3GPP_SYNC/SA2/Docs/S2-1908821.zip S2-1908821 501 Clarification on binding ID and endpoint address.docx> [retrieved on 20191001] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023006022A1 (fr) * 2021-07-30 2023-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Noeuds de réseau et procédés dans ceux-ci pour faciliter la découverte de fonction de réseau
WO2023038558A1 (fr) * 2021-09-09 2023-03-16 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau et procédé de gestion d'un enregistrement d'instance de fonction réseau dans un réseau de communication
WO2023051918A1 (fr) * 2021-09-30 2023-04-06 Nokia Technologies Oy Gestion d'abonnements à des notifications de changements de données liés à un service de fonction de réseau
WO2023129129A1 (fr) * 2021-12-28 2023-07-06 Rakuten Mobile, Inc. Communication d'architecture de service 5g (sba) sur la base d'un apprentissage automatique

Similar Documents

Publication Publication Date Title
US11509728B2 (en) Methods and apparatuses for discovering a network function acting as network function service consumer
WO2021063657A1 (fr) Fourniture d&#39;informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées
EP3949354B1 (fr) Procédé et appareil pour la découverte de services
US20230045195A1 (en) First Node, Second Node and Methods Performed Thereby for Handling Identification of a Communications Network
EP4252445A1 (fr) Procédé et système pour exposer des données de réseau d&#39;accès radio (ran)
EP3895470B1 (fr) Noeud de politique, noeud de plan utilisateur, noeud de plan de commande et procédés associés pour gérer la qualité de service dans un réseau de communication sans fil
US20230042754A1 (en) Gateway node, user equipment and methods therein for handling rules and policies in a wireless communications network
WO2021201741A1 (fr) Appareil et procédé dans un réseau de communication radio
US11974174B2 (en) First service communication proxy node, second communication proxy node and methods in a wireless communication network
US20240008103A1 (en) First ims node, second server, subscriber server and methods in a communications network
US20230199618A1 (en) Network Node, User Equipment and Methods in a Radio Communications Network
EP4315666A1 (fr) Premier noeud ims, premier noeud de réseau central, second noeud ims, et procédés exécutés dans ceux-ci
WO2024011568A1 (fr) Nœuds de sous-système multimédia de protocole internet (ims), nœud de réseau central et procédés associés, dans un réseau de communications
KR20200114916A (ko) 이동 통신 시스템에서 네트워크 분석 정보를 udm을 통해 전달 할 때 nf의 동작과 동기화 방법
WO2024011555A1 (fr) Nœud de réseau central, nœuds de sous-système multimédia de protocole internet (ims) et procédés associés dans un réseau de communication
WO2023134884A1 (fr) Nœud ims, serveur d&#39;applications et procédés dans un réseau de communication
US20230275934A1 (en) Application server node, user equipment and methods in a communications network
WO2023134885A1 (fr) Premier nœud ims, second nœud ims, nœud de réseau et procédés dans un réseau de communication
US20240129029A1 (en) Network node, terminal, and methods therein
US20240137392A1 (en) First IMS Node, First Core Network Node, Second IMS Node, and Methods Performed Therein
WO2023087229A1 (fr) Nœud mandataire, terminal et procédés dans un réseau de communication
WO2024012689A1 (fr) Fonction distributrice, fonction localisatrice et procédés dans un réseau de communication
WO2023182911A1 (fr) Nœud de réseau central, équipement utilisateur et procédés dans un réseau de communication sans fil
WO2022216195A1 (fr) Dispositif, nœud de réseau, et procédés dans un réseau de communication
WO2023179838A1 (fr) Équipement utilisateur, nœud de gestion de session et procédés dans un réseau de communication

Legal Events

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

Ref document number: 20774912

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20774912

Country of ref document: EP

Kind code of ref document: A1