Source provider network node, target provider network node and methods performed therein

Abstract

Embodiments herein relate to, for example, a method performed by a source provider network node (120) for handling one or more network services in a communication network. The source provider network node (120) provides a network service to a consumer network node (110). Upon determining to initiate transfer, to a target provider network node (130), provision of the network service for the consumer network node (110), the source provider network node (120) transmits a first indication to the target provider network node (130), wherein the first indication indicates a preparation of transferring the provision of the network service. The source provider network node (120) further determines whether the transfer is to be finalized or aborted and transmits a second indication to the target provider network node (130), wherein the second indication indicates whether the transfer is to be finalized or aborted.

Description

[0001] SOURCE PROVIDER NETWORK NODE, TARGET PROVIDER NETWORK NODE AND METHODS PERFORMED THEREIN

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a source provider network node, a target provider network node and methods performed therein regarding communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to transferring provision of network services in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (ST A) and / or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), User Plane Function (UPF), Access Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

[0009] The topic of this disclosure is about handling change of service provider for an ongoing network service, e.g., a subscription, which has been established by a service consumer using, for example, a service-based interface (SBI). In particular, the disclosure focuses on handling synchronization of the ongoing service between the two service providers and towards the consumer, looking at it from the angle of provider-side handling the service change, i.e. , the focus is not on the consumer deciding to change provider. Currently, change of provider for subscriptiontype of services could happen among NFs of the CN.

[0010] One approach used in 3GPP is that, when a new NF takes over the provider role from an old NF, the new NF obtains information about active subscriptions provided by the old NF when it retrieves the Context from the old NF. One example is at registration where, if RAN cannot determine the (old) AMF of a UE, RAN forwards the Registration Request to a new AMF which has been configured in RAN. The new AMF will determine the old AMF and will use the Namf_Communication_UEContextTransfer operation to retrieve the context of the UE in order to continue with the registration. If the old AMF was providing subscriptions associated to the UE, the new AMF needs to take over these subscriptions. In detail, the old AMF provides the list of the events which other NFs subscribed to as well as any information on how to send the corresponding notifications.

[0011] Another approach used in 3GPP is to use dedicated system operation. One example is considered in Network Data Analytics Function (NWDAF) specifications in 3GPP Technical Specification (TS) 23.288, shown in Fig. 1a. A consumer has a subscription, or more, established with a certain NWDAF provider (source). This source NWDAF provider could trigger an analytics subscription transfer to another (target) NWDAF provider invoking the Nnwdaf_AnalyticsSubscription_Transfer operation, and the subscription transfer will include information on the Subscription Correlation ID(s) and the associated consumer. Finally, the target NWDAF provider can inform the analytics consumer about the successful analytics subscription transfer using a Nnwdaf_AnalyticsSubscription_Notify message, including in this message the old Subscription Correlation ID(s) so that the consumer can correlate the new provider to the correct subscriptions.

[0012] Both approaches described above have the following common aspects:

[0013] • The new provider takes over as service provider right after obtaining a context transfer from the old provider, for the AMF example above, or after being triggered by the old provider with subscription transfer, for the NWDAF example above.

[0014] • The service consumer is only reached by one provider at a time. In particular, after the context transfer or subscription transfer, the new provider starts providing the service to the consumer, i.e. , the old provider is no longer providing the service.

[0015] Currently as part of 6G research there are proposals for standardization of SBIs within the RAN and between RAN and CN network functions. As part of these ideas, it is possible that the CN-RAN relations will be modelled as the RAN functions consuming and / or providing different network services from / to the CN functions. The service interactions can use both request-response and subscribe-notify communication patterns. The latter pattern is particularly interesting since it allows to model UE-specific service interactions and more long-lasting relations between NFs as subscriptions. For example, RAN functions can subscribe to updates on e.g., UE session related information from CN functions, while CN functions can subscribe to updates on e.g., UE state or mobility related information from RAN. Herein focus is on services which the RAN provides to the CN functions. Examples of services that the RAN could provide to the CN functions could be:

[0016] UE session related information, e.g., change of admitted and / or supported Quality of Service (QoS) Flows, change of the supported QoS level by providing index of the Alternative QoS Profile for a certain UE / user plane session, etc.

[0017] UE capability related information matching specific system level functionality, e.g., support for network configuration to support of voice over IP Multimedia Subsystem (IMS).

[0018] Traffic or mobility related information, e.g., change of UE location information.

[0019] UE-state related information, e.g., UE changing from inactive to active state.

[0020] RAN configuration changes, e.g., change of support level for some Tracking Area (TA) or Public Land Mobile Network (PLMN).

[0021] - Etc. Furthermore, there could be new network services, e.g., sensing or computation offloading, which could create new relationships between RAN and CN that should be updated in case of change of the RAN node serving a UE.

[0022] A re-design of system procedures, leveraging on SBI and on design principles such as loose coupling and modularity among services, may bring permanent / semi-permanent relationships between RAN and CN in the form of subscription see Fig. 1b. In case of mobility, i.e., a UE moves from a source to a target RAN node or function, the subscriptions established between the CN and the source RAN need to be re-established or transferred to the target RAN node or function, e.g., target base station. Fig. 1b shows a possible 6G architecture with SBIs between RAN and CN functions, showing that relations of service producer between RAN and CN are updated in case of RAN changes for a UE.

[0023] The same discussion applies when a CN function has subscriptions established with RAN and there is a change of CN function, e.g., due to relocation, or scaling up / down, failure. These subscriptions need to be re-stablished or transferred to the target CN function as illustrated in Fig. 1c. Fig. 1c shows a possible 6G architecture with SBIs between RAN and CN functions, illustrating that relations of service between the RAN and CN should be updated in case of changes of CN functions with relationships, e.g., subscribed services, to the RAN.

[0024] When focusing on the update of relations established between a RAN node or function and a CN function due to UE mobility, one should note that radio handovers, or other radio mobility events, and associated RAN function change could happen quite frequently, e.g. for UEs moving along a road, for some UEs, hence one could expect that updates of relations established between RAN nodes or functions and a CN function could be more frequently compared to updates of relations between CN functions.

[0025] Furthermore, radio handover typically involves a preparation phase where the new RAN node or function is preparing resources for the incoming handover as well as transferring network service information. In this time interval, the UE is still handled by the old RAN. Hence, it could be that the old RAN still has service-related information to deliver to the consumer, of a certain subscription, even if handover preparation started. And eventually, it could be that handover fails during execution, i.e., the UE is not moved to the target RAN. In this case the UE may continue to be served by the old RAN function.

[0026] Another aspect to highlight is that for certain services it might not be possible to start with providing the service right after the subscription has been moved to a new provider. For instance, one could think about prediction-related services where the new provider might need some time to gather UE information or measurements, or to subscribe to events / information from other functions, before being able to run some predictions and hence start with service delivery. SUMMARY

[0027] As part of developing embodiments herein one or more problems have been identified. With current approaches, the new service provider takes over as soon as it obtains a context transfer from the old provider or after being triggered by the old provider with subscription transfer. This means that the old provider stops service delivery to the consumer. When considering the case of change of provider role due to handover, providers being RAN nodes or functions, the following problems arise:

[0028] • If the new provider takes over the role as service provider at handover preparation, there are two potential issues to consider. o Handover may fail, i.e. , the UE will not move to the target and the old provider needs to take back the role as service provider, for a certain subscription. This creates more signalling since the network service is moved twice, it complicates service synchronization between old / new service providers, and it involves more complexity for the consumer side, e.g., understand validity of messages received from different providers. o Depending on the service, it could be the case that source RAN may still have notifications to send to the service consumer. One example could be services such as notifications of a UE-related event or a UE-related prediction. An example of the latter case is “prediction of QoS fulfilment or achievable QoS”, where RAN provides in-advance notifications with information on whether QoS will be fulfilled or not or information on which QoS / performance are predicted in a certain future time interval for a certain traffic. In this example, the source RAN could still generate notifications related to a UE as it is still handled by the source RAN, but with the current approach the source RAN would not be able to send such notifications if the provider role has moved to the target RAN at handover preparation. This might lead to loosing service information which could be of relevance for the consumer.

[0029] • For services where it may not be possible to start with providing the service right after the subscription has been moved to a new provider, regardless if subscription is moved at preparation phase or after execution, using the current approach would involve inefficiency in service delivery towards the consumer which will experience a time gap with no service provided. In fact, the old provider is no longer providing the service, but the new provider may need some time before being able to, e.g., generate notifications and this is the case regardless if the provider role is moved at handover preparation or at handover execution. One could think of extending the current approach allowing multiple providers, e.g., an old and a new provider, to send notifications to the consumer. In this way, even if the handover fails and the UE remains at the source RAN, the old provider is still one of the providers providing the service to the consumer. Whilst this approach seems reasonable for services where notifications from different providers are independent from each other, e.g., events on whether a cell is loaded is independent between two cells, a different approach might be needed for services where notifications from different providers are related to each other. An example of the latter case could be a service providing notifications of expected performance, e.g., achievable QoS, for a UE: two RANs would be trying to predict the performance of a UE and could reach to different predictions depending on their local situations. In this case, how would the consumer interpret receiving for instance a notification from one provider predicting “good performance” and a notification from another provider predicting “poor performance” for the UE? Hence, for these types of services, a consumer simultaneously receiving from multiple providers might involve high complexity in terms of understanding the validity of messages from multiple providers, handling of conflicts among messages from multiple providers, re-ordering messages from different providers, etc.

[0030] An object of embodiments herein is to handle provision of a network service in a communication network in an efficient manner.

[0031] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a source provider network node for handling one or more network services in a communication network. The source provider network node provides a network service to a consumer network node. Upon determining to initiate transfer, to a target provider network node, provision of the network service for the consumer network node, the source provider network node transmits a first indication to the target provider network node, wherein the first indication indicates a preparation of transferring the provision of the network service. The source provider network node determines whether the transfer is to be finalized or aborted, and further transmits a second indication to the target provider network node, wherein the second indication indicates whether the transfer is finalized or aborted.

[0032] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a target provider network node for handling one or more network services in a communication network. The target provider network node receives a first indication from a source provider network node, wherein the first indication indicates a preparation of transferring a provision of a network service provided for a consumer network node. The target provider network node further receives a second indication from the source provider network node, wherein the second indication indicates whether the transferring is finalized or aborted.

[0033] It is furthermore provided herein a computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods above, as performed by the source provider network node and the target provider network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the methods above, as performed by the source provider network node and the target provider network node, respectively.

[0034] According to another aspect a source provider network node and a target provider network node are herein provided to be configured to perform the methods herein, respectively.

[0035] Thus, according to an aspect the object is achieved, according to some embodiments herein, by providing a source provider network node that comprises a network interface configured to communicate with other network nodes, and a processing circuitry configured to: provide a network service to a consumer network node via the network interface; upon determining to initiate transfer, to a target provider network node, provision of the network service for the consumer network node, transmit a first indication to the target provider network node via the network interface, wherein the first indication indicates a preparation of transferring the provision of the network service; determine whether the transfer is to be finalized or aborted; and transmit a second indication to the target provider network node (130) via the network interface, wherein the second indication indicates whether the transfer is to be finalized or aborted.

[0036] According to yet another aspect the object is achieved, according to some embodiments herein, by providing a target provider network node comprising a network interface configured to communicate with other network nodes, and a processing circuitry configured to: receive from a source provider network node a first indication via the network interface, wherein the first indication indicates a preparation of transferring a provision of a network service provided for a consumer network node; and receive a second indication from the source provider network node via the network interface, wherein the second indication indicates whether the transferring is finalized or aborted.

[0037] Embodiments herein provide a solution for cases when a source provider network node, such as a service provider, wants to transfer a network service, e.g., notifications, for a consumer network node that subscribes to it, to a different provider network node. The indications mentioned herein, that may be explicit information, are sent by the source provider network node providing the network service, to inform the target provider network node about preparing and finalizing or aborting preparation of the provision.

[0038] The embodiments herein provide one or more of the following advantages:

[0039] Embodiments herein allow the target provider network node to “prepare” the upcoming service delivery, e.g., collecting data, buffering service-related information, before the target provider network node takes over the service delivery which may be explicitly triggered by the source provider network node with the second indication. Another advantage is that some embodiments guarantee synchronization between the provider network nodes. The synchronization is guaranteed from the point of view of who contacts and when to contact the consumer network node, as the source provider network node explicitly sends the second indication to the target provider network node, so the target provider network node knows exactly when to start with the network service delivery. In addition, even if the source provider network node may continue with service delivery towards the consumer network node before sending the second indication, synchronization between the provider network nodes is also achieved. This is because the target provider network node can remain updated with service-related information from the source provider network node if relevant in order to maintain the service context up-to-date. This can happen either as part of the transfer finalization or while the preparation phase is ongoing. I

[0040] Another advantage is that some embodiments guarantee synchronization at the consumer network node as the consumer network node receives only from one provider at a time, hence avoiding complexity such as re-ordering of messages from different providers.

[0041] A difference to highlight is that in the current approach the target provider network node is contacted only when it should start taking over and delivering the network service. As with some embodiments herein the target provider network node does not need to directly start with service delivery when firstly contacted by the source provider network node, and the source provider network node may continue providing the network service to the consumer network node.

[0042] Another advantage is that some embodiments herein allow to change functionalities also for network services which have a longer preparation time without involving a time gap in the service delivery to the consumer network node.

[0043] Another advantage is that embodiments herein allow to abort a service transfer, if needed, without any extra signalling and complexity towards the consumer network node, which will be only reached by the source provider network node. Thus, embodiments herein handle provision of a network service in a communication network in an efficient manner.

[0044] BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0046] Fig. 1a shows an analytics Subscription Transfer initiated by source NWDAF according to prior art;

[0047] Fig. 1b shows a possible 6G architecture with service based interfaces; Fig. 1c shows a possible 6G architecture with service based interfaces;

[0048] Fig. 2a is a schematic overview depicting a communication network according to embodiments herein;

[0049] Fig. 2b is a combined flowchart and signalling scheme according to embodiments herein;

[0050] Fig. 3 is a schematic flowchart depicting a method performed by a source provider network node according to embodiments herein;

[0051] Fig. 4 is a schematic flowchart depicting a method performed by a target provider network node according to embodiments herein;

[0052] Fig. 5 is a combined flowchart and signalling scheme according to some embodiments herein;

[0053] Fig. 6a is a combined flowchart and signalling scheme according to some embodiments herein;

[0054] Fig. 6b is a combined flowchart and signalling scheme according to some embodiments herein;

[0055] Fig. 7a is a combined flowchart and signalling scheme according to some embodiments herein;

[0056] Fig. 7b is a combined flowchart and signalling scheme according to some embodiments herein;

[0057] Fig. 8a is a combined flowchart and signalling scheme according to some embodiments herein;

[0058] Fig. 8b is a combined flowchart and signalling scheme according to some embodiments herein;

[0059] Fig. 8c is a combined flowchart and signalling scheme according to some embodiments herein;

[0060] Fig. 8d is a combined flowchart and signalling scheme according to some embodiments herein;

[0061] Fig. 9a is a combined flowchart and signalling scheme according to some embodiments herein;

[0062] Fig. 9b is a combined flowchart and signalling scheme according to some embodiments herein;

[0063] Fig. 10 is a block diagram depicting a source provider network node according to embodiments herein;

[0064] Fig. 11 is a block diagram depicting a target provider network node according to embodiments herein;

[0065] Fig. 12 shows an example of a communication system QQ100 in accordance with some embodiments;

[0066] Fig. 13 shows a UE QQ200 in accordance with some embodiments; Fig. 14 shows a network node QQ300 in accordance with some embodiments;

[0067] Fig. 15 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 12, in accordance with various aspects described herein;

[0068] Fig. 16 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized; and

[0069] Fig. 17 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0070] DETAILED DESCRIPTION

[0071] Embodiments herein relate to communication networks in general. Fig. 2a is a schematic overview depicting a communication network 1 . The communication network 1 comprises one or more access networks such as RANs and one or more CNs. The communication network 1 may use one or a number of different technologies, such as 6G, NR, LTE, WiFi, wired networks etc.

[0072] In the communication network 1 , one or more UEs such as a UE 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a wired device, a STA and / or a wireless terminal, are comprised communicating via e.g. one or more Access Networks (AN), e.g. RAN, to one or more CNs. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, computer, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

[0073] The communication network 1 comprises a first radio network node 12, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The first radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a NG-RAN-CU-UP node, base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminology used. The first radio network node may communicate with the UE 10 in form of DL transmissions to the UE 10 and UL transmissions from the UE 10. The communication network 1 comprises a second radio network node 13, providing radio coverage over a geographical area, a second service area 14 or second cell, of a second RAT, such as NR, LTE, or similar. The second radio network node 13 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a WLAN access point or an AP STA, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the second radio network node depending e.g. on the first radio access technology and terminology used. The second radio network node communicates with the UE in form of DL transmissions to the UE and UL transmissions from the UE.

[0074] It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0075] The first RAT may be the same RAT as the second RAT or the first RAT may be a different RAT than the second RAT.

[0076] The communication network 1 may further comprise a number of network nodes providing network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first network node 15, for example, an AMF, and a second network node 16 such as another AMF or an SMF. The different NF instances may have same or different tasks. Other functions may be for LTE such as MME or similar.

[0077] The respective node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks. Embodiments herein may be applied to both non-cloud and cloud implementation of RAN and CN functions.

[0078] According to embodiments herein a network service such as a subscription of updates and / or changes of a NF or a radio network node function, is established between a consumer network node 110 and a source provider network node 120. The consumer network node 110 may comprise the UE 10, the first or the second radio network node 12, 13, respectively, or any of the network nodes. The source provider network node 120 may comprise any of the network nodes or the first or the second radio network node 12, 13, respectively.

[0079] Thus, the consumer network node 110 consumes, such as subscribes to, the network service from the source provider network node 120.

[0080] Provision of the network service may be transferred to a target provider network node 130. The target provider network node 130 may comprise any of the network nodes or the first or the second radio network node. This transferring of provision may be determined based on, or triggered by: mobility of the consumer network node 110, or the source / target provider network node; decommissioning of the source provider network node 120; updating software and / or version updates at the source provider network node 120; and / or scaling in or out a capacity of the network service.

[0081] According to embodiments herein the source provider network node 120, upon determining to initiate transfer, to the target provider network node 130, provision of the network service for the consumer network node 110, transmits a first indication to the target provider network node 130. The first indication indicates a preparation of transferring the provision of the network service. The target provider network node 130 may, upon reception of the first indication, then prepare for handling provision of the network service, such as gathering data or similar, but may not provide the network service. The source provider network node 120 determines whether the transfer is to be finalized or aborted, and further transmits a second indication to the target provider network node 130. The second indication indicates whether the transfer is finalized or aborted. This may thus at the target provider network node 130 trigger initiation of the network service from the target provider network node 130 or that the process is aborted at the target provider network node 130.

[0082] Thus, it is herein disclosed how the source provider network node 120, e.g., a source network function such as a source RAN node or function or a CN function, prepares and executes the transfer of the network service, such as a subscription service, to the target provider network node 130, e.g., a target network function. The network service may be provided to one or more consumer network nodes, e.g., CN network functions or RAN node or function.

[0083] The source provider network node 120 may provide the target provider network node 130 with service information comprising the first indication during a preparation phase. The source provider network node 120 may continue to provide the network service to the consumer network node 110 during the preparation phase. At a determined time or due to one or more events, the source provider network node 120 provides the target provider network node 130 with the second indication indicating finalization or abortion of the transferring, and may stop or continue providing the network service.

[0084] As an example, the service information with the first indication may be transferred during a handover preparation phase, and may be included in a handover preparation message from the source provider network node 120 to the target provider network node 130 or in a separate message, e.g., dedicated to transferring service information.

[0085] The source provider network node 120 may provide the second indication in response to receiving a complete indication that target provider network node 130, i.e. , the target network function, has taken over a target object or resource, such as the UE 10, a RAN node, a network node or a client, from the source provider network node 120, i.e., the source network function. The complete indication may comprise an indication or message that a handover was successful, or that the UE 10 has arrived in a target cell, node, or function, or that a new CN function has taken over with providing the network service from another CN function. Thus, the target provider network node 130 is provided for receiving the transfer of, for example, a subscription service provided to one or more consumer network nodes (e.g., RAN nodes or functions or CN network functions), from the source provider network node 120 including both a preparation phase and a finalization phase. That is, according to embodiments herein the target provider network node 130 receives the first indication such as a service transfer preparation message or indication, and the second indication such as a service transfer finalization message or indication. The target provider network node 130 may then, in response to receiving the second indication, initiate, stop or resume the provisioning of the network service towards the consumer network node 110. Embodiments herein allow the target provider network node to, for example, prepare the upcoming service delivery, e.g., collecting data, buffering service-related information, before the target provider network node 130 takes over the service delivery which may be explicitly triggered by the source provider network node 120 with the second indication. Thus, embodiments herein handle provision of a network service in the communication network in an efficient manner.

[0086] In the remainder, the following terminology may be used:

[0087] • with “RAN” it is indicated a RAN node, e.g., a gNB or base station, or a function of a RAN entity, e.g., a control plane functionality such as central unit (CU) control plane (CP).

[0088] • “service” or “network service” is established between a provider, e.g., RAN, and a consumer, e.g., CN. For instance, a CN NF subscribing to a service provided by RAN, with the service being associated to a target object / resource such as a wireless device, e.g., UE, handled by the RAN. Nevertheless, embodiments herein are generic and possible to apply also in other cases, such as a RAN as consumer of a service provided by a CN NF, a CN NF as service provider and another CN NF as service consumer, etc. As part of this network service, the service provider provides the consumer with notifications, e.g., the service could be a subscription-based service where service-related information is e.g., notifications of events, analytics, or information associated to a target object or resource of the network service. Thus, the network service may comprise a service providing a relationship between the provider network node and the respective consumer network node associated to a target object / resource. The network service may, for example, comprise a subscription to notifications of updates or changes to information associated to the target object I resource hosted at or obtained by the provider network node. The network service may comprise a subscription to notifications of one or more network events monitored by the provider network node associated to the target object / resource. The network service may comprise a service provided by the provider network node related to handling the respective target object I resource requested by the consumer network node, e.g., to create or modify or get the status of the target object / resource. A service consumer, such as the consumer network node 110, may have a long-lasting relation with a service provider for a certain service, e.g., subscription-based service. Nevertheless, embodiments herein may be applied also to the case of request-response services. It is herein considered the case when there is a change of provider network node, with which the consumer network node 110 has previously established the network service, to the new provider network node, e.g., a new provider which will provide the service to the consumer. This change could happen, for example, because of the change of RAN serving the UE if it is RAN providing a service which is associated to a UE. In this case, the first serving RAN, being an example of the source provider network node 120, might no longer provide the network service to its consumer as the UE 10 is now served by a second RAN, being an example of the target provider network node 130. The case of change of provider network node due to handover is a main example used herein. However, a provider network node may be a CN function, and change of provider may happen because of a new CN function that takes over the provisioning of a network service of another CN function due to relocation, scaling up / down, failure, etc., or because of deployment choices: one example could be segmentation, which involves that a new CN function should take over the provisioning of network services if e.g. a UE moves to a different segment of the communication network. Furthermore, change of service provider could happen for other reasons, such as decommissioning of the old provider, for software / version updates, due to scaling in or out the capacity of the service, etc.

[0089] Fig. 2b is a combined signalling scheme and flowchart depicting some embodiments herein.

[0090] Action 201. The consumer network node 110 consumes, e.g. uses, the network service from the source provider network node 120. Thus, the source provider network node 120 provides the network service and may notify the consumer network node 110 according to the network service provided by the source provider network node 120.

[0091] Action 202. The source provider network node 120 may determine to initiate transfer of provision of the network service to one or another provider network node such as the target provider network node 130. This may be determined based on: mobility of the consumer network node 110, or mobility of the source / target provider network node; decommissioning of the source provider network node; updating software and / or version updates; and / or scaling in or out a capacity of the network service.

[0092] Action 203. The source provider network node 120 transmits the first indication to the target provider network node 130. The first indication indicates a preparation of transferring the provision of the network service.

[0093] Action 204. The target provider network node 130 may then prepare for providing the network service to the consumer network node 110. The target provider network node 130 may, for example, not yet provide the network service to the consumer network node 110, but may start with one or more operations related to provision of the network service. For instance, target provider network node 130 may start gathering and processing information which will be useful when providing the network service to the consumer network node 110.

[0094] Action 205. The target provider network node 130 may, once prepared such as having accepted an HO, transmit a confirmation back to the source provider network node 120.

[0095] Action 206. The source provider network node 120 determines whether the transfer is to be finalized or aborted.

[0096] Action 207. The source provider network node 120 further transmits the second indication to the target provider network node 130. The second indication indicates whether the transfer is finalized or aborted.

[0097] Action 208. The consumer network node 110 may then consume, e.g. use, the network service from the target provider network node 130. Thus, the target provider network node 130 may provide such as the network service and notifying the consumer network node 110 according to the network service provided by the target provider network node 120. If the second indication indicates an abortion the target provider network node 130 may abort the transfer.

[0098] The method actions performed by the source provider network node 120, such as an NF node or a radio network node, for handling one or more network services in the communication network 1 according to embodiments will now be described with reference to a flowchart depicted in Fig. 3. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0099] Action 301. The source provider network node 120 provides the network service to the consumer network node 110.

[0100] Action 302. The source provider network node 120 may determine to initiate transfer provision of the network service to the target provider network node 130. This may be determined based on or triggered by: mobility of the consumer network node 110, mobility of the source / target provider network node, decommissioning of the source provider network node, updating software and / or version updates, and / or scaling in or out a capacity of the network service.

[0101] Action 303. The source provider network node 120, upon determining to initiate transfer, to the target provider network node 130, provision of the network service for the consumer network node 110, transmits the first indication to the target provider network node. The first indication indicates the preparation of transferring the provision of the network service. The first indication may comprise one or more of the following parameters:

[0102] ■ Service name;

[0103] ■ Subscription ID;

[0104] ■ Security token; ■ Service I Subscription target object / resource ; and

[0105] ■ Information of the consumer network node 110 enabling the target provider network node 130 to reach the consumer network node 110.

[0106] Action 304. The source provider network node 120 determines whether the transfer is to be finalized or aborted. The source provider network node 120 may obtain a complete indication. The complete indication may indicate completion of preparation of the transferring of the network service or a completion of handover of a responsibility of the UE or similar. For example, the source provider network node 120 may receive the confirmation back from the target provider network node 130. This may trigger the source provider network node 120 to transmit the second indication. The source provider network node 120 may be triggered to transmit the second indication when one or more of the following occurs: obtaining information indicating that the target object or resource of the network service, e.g., UE, is no longer handled by the source provider network node 120; obtaining information indicating that handover execution has failed and that the target object or resource of the network service is still handled by the source provider network node 120; receiving an handover success from the target provider network node 130; receiving an “UE Context release request” from the target provider network node 130; and / or becoming aware that operations for network service decommission have been triggered.

[0107] Action 305. The source provider network node 120 further transmits the second indication to the target provider network node 130. The second indication indicates whether the transfer is finalized or aborted. As an example, the second indication may indicate a finalization of transferring the provision of the network service. The second indication may comprise one or more of the following parameters:

[0108] ■ Service name;

[0109] ■ Subscription ID;

[0110] ■ Security token;

[0111] ■ Service I Subscription target object / resource;

[0112] ■ Information of the consumer network node;

[0113] ■ Information related to service synchronization; and

[0114] ■ An indication of transfer aborted informing that the transfer is no longer valid.

[0115] Action 306. The source provider network node 120 may then stop or continue provision of the network service to the consumer network node 110. The source provider network node 120 may then decommission the network service, install software and / or version updates, and / or scale in or out a capacity of the network service. In case of a handover (HO) of the target object or resource of the network service, or transferring of the provision has failed, the source provider network node 120 may continue providing the network service. This may be performed prior, same time, or after action 305. It should be understood that the source provider network node 120 may comprise a provider network function and the consumer network node 110 may comprise a consumer network function. Furthermore, the network service may comprise an establishment of a relationship between the provider network function and the consumer network function. The relationship may comprise a subscription from the consumer network function to the provider network function for updates or changes, such as subscription to notifications of changes to status of information hosted at or obtained by the provider network function, or to events which are monitored by the provider network function, or to analytics generated by the provider function, where such subscriptions to the provider network function may be related to specific target objects like a specific UE and / or a specific network information.

[0116] The method actions performed by the target provider network node 130, such as a radio network node or an NF node, for handling one or more network services in the communication network 1 according to embodiments will now be described with reference to a flowchart depicted in Fig. 4. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0117] Action 401. The target provider network node 130 receives, from the source provider network node 120, the first indication. The first indication indicates the preparation of transferring the provision of the network service. The first indication may comprise one or more of the following parameters:

[0118] ■ Service name;

[0119] ■ Subscription ID;

[0120] ■ Security token;

[0121] ■ Service / Subscription target object / resource ; and

[0122] ■ Information of the consumer network node 110 enabling the target provider network node 130 to reach the consumer network node 110.

[0123] Action 402. The target provider network node 130 may prepare for providing the network service to the consumer network node 110. The target provider network node 130 may, for example, not yet provide the network service to the consumer network node 110, but may start with one or more operations related to provision of the network service. For instance, the target provider network node 130 may start gathering and processing information which will be useful when providing the network service to the consumer network node 110.

[0124] Action 403. The target provider network node 130 may, once prepared, transmit a confirmation back to the source provider network node 120. The confirmation may be an example of the complete indication. Thus, the target provider network node 130 may transmit the complete indication back to the source provider network node 120. The complete indication may indicate completion of preparation of the transferring of the network service or a completion of handover of a responsibility of the target object or resource of the network service or similar. The complete indication may indicate one or more of the following: that the target object or resource of the network service is no longer handled by the source provider network node 120; that handover execution has failed and that the target object or resource of the network service is still handled by the source provider network node 120; a handover success from the target provider network node 130; or an “UE Context release request”.

[0125] Action 404. The target provider network node 130 further receives the second indication from the source provider network node 120, wherein the second indication indicates whether the transferring is finalized or aborted. The second indication may comprise one or more of the following parameters:

[0126] ■ Service name;

[0127] ■ Subscription ID;

[0128] ■ Security token;

[0129] ■ Service / Subscription target object / resource;

[0130] ■ Information of the consumer network node;

[0131] ■ Information related to service synchronization; and

[0132] ■ An indication of transfer aborted informing that the transfer is no longer valid.

[0133] Action 405. The target provider network node 130 may then initiate, or proceed, or stop provision (or start providing) the network service to the consumer network node 110. This may be based on the received second indication. It should be noted that the target provider network node 130 may not start with providing the network service to the consumer network node 110 until it receives the second indication from the source provider network node 120. This covers cases when synchronicity between the two provider network nodes should be guaranteed. For completeness, there could be considered cases where the target provider network node 130 may decide on its own when to start providing the service to the consumer network node 110, i.e. , potentially before the reception of the second indication from the source provider network node 120. This could be handled in the following way. During the service transfer preparation, the source provider network node 120 may add a start indication indicating “start with providing the service before transfer finalization - allowed”. In this case, the target provider network node 130 may start with providing the network service to the consumer network node 110 before the reception of the second indication, and eventually the second indication might or might not be sent by the source provider network node 120. One could think that the start indication such as a “start with providing the service before transfer finalization - not allowed” indication may be included by the source provider network node 120 when the source provider network node 120 wants to inform that the target provider network node 130 must wait until the reception of the second indication before starting with providing the network service to the consumer network node 110. It should be understood that the source provider network node 120 may comprise a provider network function and the consumer network node 110 may comprise a consumer network function. Furthermore, the network service may comprise an establishment of a relationship between the provider network function and the consumer network function. The relationship may comprise a subscription from the consumer network function to the provider network function for updates or changes, such as subscription to notifications of changes to status of information hosted at or obtained by the provider network function, or to events which are monitored by the provider network function, or to analytics generated by the provider function, where such subscriptions to the provider network function may be related to specific target objects like a specific UE and / or a specific network information

[0134] Embodiments herein disclose that the source provider network node 120, also referred to as the old service provider, interacts with the target provider network node 130, also referred to as new service provider, to prepare the transfer of a service provider role. The source provider network node 120 further sends information, that is the first and second indication, to the target provider network node 130 indicating when to start providing the network service. Thus, the information exchange may be split into two phases:

[0135] • The first phase is when the source provider network node 120 interacts with the target provider network node 130 to trigger the service transfer - this may be called a “service transfer preparation”.

[0136] • The second phase is when the source provider network node 120 informs the target provider network node 130 that the source provider network node 120 will stop providing the network service towards the consumer network node 110. Hence, the target provider network node 130 may start providing the network service -this may be called a “service transfer finalization”.

[0137] Examples of embodiments herein are shown in Fig. 5, wherein the consumer network node 110 consumes the network service from the source provider network node 120, see action 51. Furthermore, Fig. 5 shows that the target provider network node 130 is firstly informed, see action 52, that the network service is being transferred from the source provider network node 120, and in the second phase the target provider network node 130 is informed, see action 53, when the source provider network node 120 stops providing the network service and consequently the target provider network node 130 knows when to start providing the network service towards the consumer.

[0138] One thing to underline is that the “service transfer preparation” does not trigger the target provider network node 130 to deliver the network service to the consumer network node 110. This approach is different than current approaches where when a target provider network node takes over the role as service provider right after being contacted the first time by the source provider network node, e.g., when the source provider network node 120 sends the “subscription transfer request” referring to Fig. 1a. Embodiments herein disclose that the source provider network node 120 explicitly informs the target provider network node 130 when the source provider network node 120 will terminate provision of the network service to the consumer network node 110, so that the target provider network node 130 can take over the role as service provider, see action 54.

[0139] As stated in Action 303, the source provider network node 120 transmits the first indication to the target provider network node 130. During the “service transfer preparation”, the source provider network node 120 may inform the target provider network node 130 about which network service is, or which network services are, being transferred.

[0140] The first indication may be comprised in a message such as a “service transfer preparation” message and may include one or more fields, such as:

[0141] • Service name

[0142] • Subscription ID, e.g., correlation ID,

[0143] • Security token, e.g., exchanged at establishment of a subscription,

[0144] • Service / Subscription target object / resource, e.g., UE ID,

[0145] • Information of the associated consumer(s), e.g., a list of one or more identities, Uniform Resource Locators (URL) etc., so that the new provider knows how to reach the consumer, e.g., for sending notifications.

[0146] The first indication may be sent to the target provider network node 130 in different ways:

[0147] • One possibility is to include the first indication in an existing message. This is shown in Fig. 6a. In one example where provider network nodes are RAN nodes or functions, the existing message could be e.g. a handover request sent by the source RAN which include information about all services to be transferred. Or, in general, as part of the service context, e.g., UE context, transferred between old and new provider, which applies to both cases where providers are RAN nodes or functions or ON functions.

[0148] • Another possibility is to use a specific message for this purpose. For instance, the old provider could send a “service transfer preparation request” to the new provider, which in turn could respond with a “service transfer preparation response” indicating whether the transfer is accepted or not, potentially including a Notification Target Address that the old provider could use to further send service-related information to the new provider. This is shown in Fig. 6b. For the case of multiple services being transferred, it could be that a single service transfer preparation request is sent which include information of all services, or it could be that one service transfer preparation request is sent for each service to be transferred. The sending of the first indication may be triggered, see action 302, based on:

[0149] • Considering the case of change of provider due to e.g., mobility of service target object / resource, e.g., a UE, the trigger could be when the source RAN (old provider) triggers a handover to the target RAN (new provider).

[0150] • When the source provider network node 120 becomes aware that it does not have, or will not have, enough resources to provide the service, e.g., the old provider started providing other services with higher priority and low-priority services need to be moved due to lack of resources.

[0151] • When the source provider network node 120 becomes aware that it is going to stop providing the service, e.g., because it is going to be decommissioned.

[0152] After receiving the first indication, the target provider network node 130 is not yet providing the service to the consumer network node 110, i.e. , not sending notifications, but it can start with the operations related to the upcoming role as active service provider, see action 402. For instance, the target provider network node 130 may start gathering and processing information which will be useful when providing the service to the consumer network node 110. This could be data obtained from management system, or information obtained by subscribing to other services such as events / analytics notification which are relevant to the network service. It could also be that the target provider network node 130 receives service-related information from the source provider network node 120. For example, if the source provider network node 120 generates a notification to the consumer network node 110, or if the service context changes, the source provider network node 120 may send such information to the target provider network node 130 so that the service status at the target provider network node 130 is synched with the source provider network node 120.

[0153] Referring to Action 305, when the source provider network node 120 stops acting as service provider, it informs the target provider network node 130 with the second indication also referred to as a “service transfer finalization” indication.

[0154] The second indication may include one or more fields, such as:

[0155] • Service name,

[0156] • Subscription ID, e.g., correlation ID,

[0157] • Security token, e.g., exchanged at establishment of a subscription or previously exchanged between the old and new providers,

[0158] • Service / Subscription target object / resource, e.g., UE ID,

[0159] • Information of the associated consumer(s), if changed, e.g., identity, URL,

[0160] • Information related to service synchronization, e.g., changes to service context or notifications sent to the consumer which the new provider is not yet aware of. • An indication “transfer aborted”, added if for instance the handover has failed, i.e., the UE is still handled by the source RAN, and hence the old provider will continue as service provider. In this case, the new provider is informed that the transfer is no longer valid.

[0161] For the case of aborting a service transfer, the usage of the indication “transfer aborted” being included in the second indication is only one alternative. Other alternatives are presented later.

[0162] The second indication may be sent to the target provider network node 130 in different ways:

[0163] • As part of other service-related information. For instance, the second indication may be sent as part of a service notification which includes a “service transfer finalization” indication as new field. This is shown in Fig. 7a. It could be a notification with a normal body, e.g., including an actual event or analytics notification, or it could be a notification including only the “service transfer finalization” indication, i.e., not carrying any other information.

[0164] • As a new service operation for “service transfer finalization”. It could be that the source provider network node 120 sends a “service transfer finalization request” to the target provider network node 130, which could reply with a “service transfer finalization response”. This is shown in Fig. 7b.

[0165] For the case of multiple network services being transferred, it could be that a single service transfer finalization is sent which include information of all services, or it could be that one service transfer finalization is sent for each network service to be transferred.

[0166] The transmitting of the second indication may be triggered based on, using a UE as an example of the target object or resource of the network service, see Action 304:

[0167] • (if provider is a RAN node or function) RAN-internal information indicating that the UE is no longer handled by the source RAN (old provider). Or, eventually, RAN-internal information indicating that handover execution has failed and that the UE is still handled by the source RAN.

[0168] • (if provider is a RAN node or function) For a Daul Active Protocol Stack (DAPS) HO or for conditional handover, the trigger could be the reception by the source RAN (old provider) of an “handover success” from the target RAN (new provider).

[0169] • (if provider is a RAN node or function) Reception by the source RAN (old provider) of an “UE Context release request” from the target RAN (new provider).

[0170] • Old provider becoming aware that operations for service or function decommission have been triggered (generally valid for any target object / resource of the network service). The reception of the second indication may trigger a start of providing the network service at the target provider network node 130 towards the consumer network node 110, see action 405.

[0171] To abort the network service transfer, please note that one possibility introduced above is that the source provider network node 120 sends to the target provider network node 130 a “service transfer finalization” with an indication “transfer aborted” - this alternative is shown in Fig. 8a. Other possibilities could be considered too, including:

[0172] • The source provider network node 120 may send a second “service transfer preparation” which refers to the service previously transferred, e.g., including a service name and / or correlation / subscription ID, adding an indication “transfer aborted”. This is shown in Fig. 8b.

[0173] • The source provider network node 120 may send a separate “transfer aborted” message to the target provider network node 130. This is shown in Fig. 8c.

[0174] • The source provider network node 120 may include a “transfer aborted” indication in a message informing the target provider network node 130 that the whole transfer of responsibility of the target object / resource of the network service, e.g., UE, has failed, e.g., if the UE returns to the source provider network node 120 or if the UE 10 has moved to different new provider. This is shown in Fig. 8d, considering the example when the “transfer aborted” is carried within an HO cancel message.

[0175] • The target provider network node 130 may use a timer, triggered from when it received the first indication. The target provider network node 130 may abort the service transfer if the target provider network node 130 has not received the second indication such as a “service transfer finalization” before the expiration of the timer. This is shown in Fig. 9a. Timer duration may either be standard-defined, or left to implementation, and / or agreed between the source provider network node 120 and the target provider network node 130 during the “service transfer preparation” phase.

[0176] • The target provider network node 130 may infer “transfer aborted” when receiving a message informing the target provider network node 130 that the whole transfer of responsibility of the target object or resource has failed, e.g., if the UE 10 returns to the source provider network node 120 or if the UE 10 has moved to a different new provider. This is shown in Fig. 9b, considering the example when the “transfer aborted” is inferred by the reception of an HO cancel message. Please note that this case is different from that in Fig. 8d, as in Fig. 8d, the source provider network node 120 explicitly adds a “transfer aborted" in the HO cancel message whereas in this case the HO cancel received by the target provider network node 130 does not contain such indication, but is an implicit second indication. It should be noted that the target provider network node 130 may not start providing the network service to the consumer network node 110 until the target provider network node 130 receives the second indication such as the “service transfer finalization” from the source provider network node 120. This is to cover cases when synchronicity between the two provider network nodes is guaranteed. However, for completeness, there could be considered cases where the target provider network node 130 may decide on its own when to start providing the network service to the consumer network node 110, i.e., potentially before the reception of the “service transfer finalization” from the source provider network node 120. For example, during the service transfer preparation, the source provider network node 120 may add an additional indication such as an information element or bit “start with providing the service before transfer finalization - allowed”. In this case, the target provider network node 130 may start with providing the network service to the consumer network node 110 before the reception of the second indication, and eventually the “service transfer finalization” might or might not be sent by the old provider. The additional indication such as a “start with providing the service before transfer finalization - not allowed” is included by the source provider network node 120 when the source provider network node 120 wants to inform that the target provider network node 130 must wait until the reception of the second indication before starting with providing the service to the consumer network node 110.

[0177] Fig. 10 is a block diagram depicting the source provider network node 120 such as an NF node or a RAN node, for handling a network service in the communication network 1 according to embodiments will now be described.

[0178] The source provider network node 120 may comprise processing circuitry 1001 , e.g., one or more processors, configured to perform the methods herein.

[0179] It should be understood that the source provider network node 120 may comprise a provider network function and the consumer network node 110 may comprise a consumer network function. Furthermore, the network service may comprise the establishment of a relationship between the provider network function and the consumer network function. The relationship may comprise a subscription from the consumer network function to the provider network function for updates or changes, such as subscription to notifications of changes to status of information hosted at or obtained by the provider network function, or to events which are monitored by the provider network function, or to analytics generated by the provider function, where such subscriptions to the provider network function may be related to specific target objects like a specific UE and / or a specific network information.

[0180] The source provider network node 120 may comprise a memory 1005. The memory 1005 comprises one or more units to be used to store data on, such as data packets, indications, messages, network service information, service messages, synchronization status, network information, session information, configurations, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the source provider network node 120 comprises a network interface 1006 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas, configured to communicate with other network nodes.

[0181] The source provider network node 120 and / or the processing circuitry 1001 is configured to provide the network service to the consumer network node 110 via the network interface.

[0182] Upon determining to initiate transfer, to the target provider network node 130, provision of the network service for the consumer network node 110, the source provider network node 120 and / or the processing circuitry 1001 is configured to transmit the first indication to the target provider network node 130 via the network interface, wherein the first indication indicates the preparation of transferring the provision of the network service.

[0183] The source provider network node 120 and / or the processing circuitry 1001 is configured to determine whether the transfer is to be finalized or aborted; and to transmit the second indication to the target provider network node 130 via the network interface, wherein the second indication indicates whether the transfer is to be finalized or aborted.

[0184] The source provider network node 120 and / or the processing circuitry 1001 may be configured to determine to initiate transfer provision of the network service to the target provider network node 130. This may be determined based on or triggered by: mobility of the consumer network node 110, mobility of the source / target provider network node, decommissioning of the source provider network node, updating software and / or version updates, and / or scaling in or out a capacity of the network service.

[0185] The first indication may comprise one or more of the following parameters:

[0186] ■ Service name;

[0187] ■ Subscription ID;

[0188] ■ Security token;

[0189] ■ Service / Subscription target object / resource ; and

[0190] ■ Information of the consumer network node 110 enabling the target provider network node 130 to reach the consumer network node 110.

[0191] The source provider network node 120 and / or the processing circuitry 1001 may be configured to obtain the complete indication. The complete indication may indicate completion of preparation of the transferring of the network service or a completion of handover of a responsibility of the UE or similar. For example, the source provider network node 120 and / or the processing circuitry 1001 may be configured to receive the confirmation back from the target provider network node 130. This may trigger the source provider network node 120 and / or the processing circuitry 1001 to transmit the second indication. The source provider network node 120 and / or the processing circuitry 1001 may be configured to be triggered to transmit the second indication when one or more of the following occurs: obtaining information indicating that the target object or resource of the network service, e.g., UE, is no longer handled by the source provider network node 120; obtaining information indicating that handover execution has failed and that the target object or resource of the network service is still handled by the source provider network node 120; receiving an handover success from the target provider network node 130; receiving an “UE Context release request” from the target provider network node 130; and / or becoming aware that operations for network service decommission have been triggered.

[0192] The second indication may indicate a finalization of transferring the provision of the network service. The second indication may comprise one or more of the following parameters:

[0193] ■ Service name;

[0194] ■ Subscription ID;

[0195] ■ Security token;

[0196] ■ Service / Subscription target object / resource;

[0197] ■ Information of the consumer network node;

[0198] ■ Information related to service synchronization; and

[0199] ■ An indication of transfer aborted informing that the transfer is no longer valid. The source provider network node 120 and / or the processing circuitry 1001 may be configured to stop or continue provision of the network service to the consumer network node 110. The source provider network node 120 and / or the processing circuitry 1001 may be configured to decommission the network service, install software and / or version updates, and / or scale in or out a capacity of the network service. In case HO of the target object or resource of the network service, or transferring of the provision has failed, the source provider network node 120 and / or the processing circuitry 1001 may be configured to continue providing the network service.

[0200] The methods according to the embodiments described herein for the source provider network node 120 are respectively implemented by means of, e.g., a computer program product 1007 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the source provider network node 120. The computer program product 1007 may be stored on a computer-readable storage medium 1008, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 1008, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the source provider network node 120. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the source provider network node 120 for handling communication in a communication network, wherein the source provider network node 120 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said source provider network node 120 is operative to perform any of the methods herein.

[0201] Fig. 11 is a block diagram depicting the target provider network node 130, such as an NF node or a RAN node, for handling a network service in the communication network 1 according to embodiments will now be described.

[0202] The target provider network node 130 may comprise processing circuitry 1101 , e.g., one or more processors, configured to perform the methods herein.

[0203] It should be understood that the source provider network node 120 may comprise a provider network function and the consumer network node 110 may comprise a consumer network function. Furthermore, the network service may comprise the establishment of a relationship between the provider network function and the consumer network function. The relationship may comprise a subscription from the consumer network function to the provider network function for updates or changes, such as subscription to notifications of changes to status of information hosted at or obtained by the provider network function, or to events which are monitored by the provider network function, or to analytics generated by the provider function, where such subscriptions to the provider network function may be related to specific target objects like a specific UE and / or a specific network information.

[0204] The target provider network node 130 may comprise a memory 1105. The memory 1105 comprises one or more units to be used to store data on, such as data packets, indications, messages, network service information, message information, synchronization status, network information, session information, configurations, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the target provider network node 130 comprises a network interface 1106 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas, configured to communicate with other network nodes.

[0205] The target provider network node 130 and / or the processing circuitry 1101 is configured to receive from the source provider network node 120 the first indication via the network interface. The first indication indicates the preparation of transferring the provision of the network service provided for the consumer network node 110.

[0206] The target provider network node 130 and / or the processing circuitry 1101 is configured to receive the second indication from the source provider network node 120 via the network interface. The second indication indicates whether the transferring is finalized or aborted.

[0207] The first indication may comprise one or more of the following parameters:

[0208] ■ Service name;

[0209] ■ Subscription ID;

[0210] ■ Security token; ■ Service / Subscription target object / resource ; and

[0211] ■ Information of the consumer network node 110 enabling the target provider network node 130 to reach the consumer network node 110.

[0212] The target provider network node 130 and / or the processing circuitry 1101 may be configured to prepare for providing the network service to the consumer network node 110. The target provider network node 130 and / or the processing circuitry 1101 may be configured to start with one or more operations related to provision of the network service. For instance, the target provider network node 130 and / or the processing circuitry 1101 may be configured to start gathering and processing information which will be useful when providing the network service to the consumer network node 110.

[0213] The target provider network node 130 and / or the processing circuitry 1101 may be configured to, once prepared, transmit a confirmation back to the source provider network node 120. The confirmation may be an example of the complete indication. Thus, the target provider network node 130 and / or the processing circuitry 1101 may be configured to transmit the complete indication back to the source provider network node 120. The complete indication may indicate completion of preparation of the transferring of the network service or a completion of handover of a responsibility of the target object or resource of the network service or similar. The complete indication may indicate one or more of the following: that the target object or resource of the network service is no longer handled by the source provider network node 120; that handover execution has failed and that the target object or resource of the network service is still handled by the source provider network node 120; a handover success from the target provider network node 130; or an “UE Context release request”.

[0214] The second indication may comprise one or more of the following parameters:

[0215] ■ Service name;

[0216] ■ Subscription ID;

[0217] ■ Security token;

[0218] ■ Service / Subscription target object / resource;

[0219] ■ Information of the consumer network node;

[0220] ■ Information related to service synchronization; and

[0221] ■ An indication of transfer aborted informing that the transfer is no longer valid.

[0222] The target provider network node 130 and / or the processing circuitry 1101 may be configured to initiate, or proceed, or stop provision (or start providing) the network service to the consumer network node 110. This may be based on the received second indication.

[0223] The methods according to the embodiments described herein for the target provider network node 130 are respectively implemented by means of, e.g., a computer program product 1107 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the target provider network node 130. The computer program product 1107 may be stored on a computer-readable storage medium 1108, e.g., a disc, a USB stick or similar. The computer-readable storage medium 1108, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the target provider network node 130. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the target provider network node 130 for handling communication in a communication network, wherein the target provider network node 130 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said target provider network node 130 is operative to perform any of the methods herein.

[0224] In some embodiments a more general term “network node” or “radio network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node.

[0225] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0226] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. 6G, NR, Wi-Fi, LTE, LTE-Advanced, WCDMA, Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0227] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0228] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0229] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0230] Fig. 12 shows an example of a communication system QQ100 in accordance with some embodiments.

[0231] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110) being examples of the first radio network node 12 and second radio network node 13, or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node, being examples of the entities herein, is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0232] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of the user equipment (UE) 10, such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0233] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0234] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102. In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) such as network node 15 that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0235] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0236] As a whole, the communication system QQ100 of Fig. 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0237] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0238] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0239] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0240] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0241] Fig. 13 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0242] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0243] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0244] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0245] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0246] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0247] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems. The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card’. The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0248] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0249] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), WCDMA, GSM, LTE, NR, UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0250] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0251] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 13.

[0252] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0253] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0254] Fig. 14 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0255] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0256] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0257] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0258] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0259] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0260] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0261] The communication interface QQ306 is used in wired or wireless communication of signalling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0262] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0263] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port. The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0264] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0265] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 14 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0266] Fig. 15 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 12, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0267] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0268] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over- the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG- DASH), etc.

[0269] Fig. 16 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0270] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0271] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0272] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0273] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0274] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0275] Fig. 17 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 12 and / or UE QQ200 of Figure 13), network node (such as network node QQ110a of Figure 12 and / or network node QQ300 of Figure 14), and host (such as host QQ116 of Figure 12 and / or host QQ400 of Figure 15) discussed in the preceding paragraphs will now be described with reference to Figure 17.

[0276] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0277] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 12) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0278] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0279] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0280] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0281] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0282] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve transfer of provision of network services and thereby provide benefits such as better communication, better responsiveness, and / or better battery life. In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0283] In some examples, 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. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0284] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0285] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0286] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1. A method performed by a source provider network node (120) for handling one or more network services in a communication network, the method comprising:- providing (301) a network service to a consumer network node (110); upon determining (302) to initiate transfer, to a target provider network node (130), provision of the network service for the consumer network node (110), transmitting (303) a first indication to the target provider network node (130), wherein the first indication indicates a preparation of transferring the provision of the network service; determining (304) whether the transfer is to be finalized or aborted; and transmitting (305) a second indication to the target provider network node (130), wherein the second indication indicates whether the transfer is finalized or aborted.

2. The method according to claim 1, further comprising: determining (302) to initiate transfer the provision of the network service to the target provider network node (130), based on: mobility of the consumer network node (110), mobility of the source / target provider network node, decommissioning of the source provider network node, updating software and / or version updates, and / or scaling in or out a capacity of the network service.

3. The method according to any of the claims 1-2, wherein determining (304) comprises: obtaining a complete indication, wherein the complete indication indicates a completion of preparation of the transferring of the network service, or a completion of handover of a responsibility of a target object or resource of the network service.

4. The method according to any of the claims 1-3, wherein transmitting (305) the second indication is triggered when one or more of the following occurs: obtaining information indicating that a target object or resource of the network service is no longer handled by the source provider network node (120); obtaining information indicating that handover execution has failed and that target object or resource of the network service is still handled by the source provider network node (120); receiving an handover success from the target provider network node (130); receiving an “UE Context release request” from the target provider network node (130); receiving a confirmation of transferring the provision of the network service to a target provider network node; and / or becoming aware that operations for network service decommission have been triggered.

5. The method according to any of the claims 1-4, further comprising:if the transfer is finalized, stopping provision of the network service to the consumer network node (110); or if the transfer is aborted, continuing providing the network service to the consumer network node (110).

6. The method according to any of the claims 1-5, wherein the source provider network node (120) comprises a provider network function and the consumer network node (110) comprises a consumer network function, and furthermore the network service comprises a service providing a relationship between the provider network function and the consumer network function associated to a target object or resource of the network service.

7. The method according to any of the claims 1-6, wherein the first indication comprises one or more of the following parameters:■ Service name;■ Subscription ID;■ Security token;■ Service / Subscription target object / resource; and■ Information of the consumer network node (110) enabling the target provider network node (130) to reach the consumer network node (110).

8. The method according to any of the claims 1-7, wherein the second indication comprises one or more of the following parameters:■ Service name;■ Subscription ID;■ Security token;■ Service / Subscription target object / resource;■ Information of the consumer network node;■ Information related to service synchronization; and■ An indication of transfer aborted informing that the transfer is no longer valid.

9. A method performed by a target provider network node (130) for handling one or more network services in a communication network, the method comprising: receiving (401) from a source provider network node (120) a first indication, wherein the first indication indicates a preparation of transferring a provision of a network service provided for a consumer network node (110); and receiving (404) a second indication from the source provider network node (120), wherein the second indication indicates whether the transferring is finalized or aborted.

10. The method according to claim 9, further comprising:- preparing (402) for providing the network service to the consumer network node (110).

11. The method according to any of the claims 9-10, further comprising transmitting (403) a complete indication back to the source provider network node (120), wherein the complete indication indicates a completion of preparation of the transferring of the network service or a completion of handover of a responsibility of a target object or resource of the network service.

12. The method according to any of the claims 9-11 , further comprising, upon receiving the second indication and that the second indication indicates that the transferring is finalized, initiating (405) provision of the network service to the consumer network node (110).

13. The method according to any of the claims 9-12, wherein the source provider network node (120) comprises a provider network function and the consumer network node (110) comprises a consumer network function, and furthermore the network service comprises a service providing a relationship between the provider network function and the consumer network function.

14. The method according to any of the claims 9-13, wherein the first indication comprises one or more of the following parameters:■ Service name;■ Subscription ID;■ Security token;■ Service / Subscription target object / resource; and■ Information of the consumer network node (110) enabling the target provider network node (130) to reach the consumer network node (110).

15. The method according to any of the claims 9-14, wherein the second indication comprises one or more of the following parameters:■ Service name;■ Subscription ID;■ Security token;■ Service / Subscription target object / resource;■ Information of the consumer network node;■ Information related to service synchronization; and■ An indication of transfer aborted informing that the transfer is no longer valid.

16. A source provider network node (120) comprising a network interface configured to communicate with other network nodes, and a processing circuitry configured to:provide a network service to a consumer network node (110) via the network interface; upon determining to initiate transfer, to a target provider network node (130), provision of the network service for the consumer network node (110), transmit a first indication to the target provider network node (130) via the network interface, wherein the first indication indicates a preparation of transferring the provision of the network service; determine whether the transfer is to be finalized or aborted; and transmit a second indication to the target provider network node (130) via the network interface, wherein the second indication indicates whether the transfer is to be finalized or aborted.

17. The source provider network node (120) according to claim 16, wherein the source provider network node (120) is configured to perform the method according to any of the claims 2-8.

18. A target provider network node (130) comprising a network interface configured to communicate with other network nodes, and a processing circuitry configured to: receive from a source provider network node (120) a first indication via the network interface, wherein the first indication indicates a preparation of transferring a provision of a network service provided for a consumer network node (110); and receive a second indication from the source provider network node (120) via the network interface, wherein the second indication indicates whether the transferring is finalized or aborted.

19. The target provider network node (130) according to claim 18, wherein target provider network node (130) is configured to perform the method according to any of the claims 10-15.

20. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the method according to any of the claims 1-15, as performed by the source provider network node (120) and the target provider network node (130), respectively.

21. A computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-15, asperformed by the source provider network node (120) and the target provider network node (130), respectively.

Images