NETWORK FUNCTIONALITY (NF) AWARE SERVICE PROVISION BASED ON SERVICE COMMUNICATION PROXY (SCP)
There is provided a method for operating a first network node, which is performed by the first network node. The first network node is a first service communication proxy (SCP) node that is configured to operate as an SCP between a first network function (NF) node of a service consumer and a second NF node of a service producer in the network or the first network node is the second NF node. In response to receiving a first request transmitted towards the second NF node via the first SCP node, information indicative of a functionality supported by the first NF node is acquired. The first request is for the second NF node to provide a first service requested by the first NF node. The first network node operates based on the functionality supported by the first NF node.
The disclosure relates to methods for providing information to, and operating, a network node. The disclosure also relates to network nodes configured to operate in accordance with those methods.
BACKGROUNDThere exist various techniques for handling a request for a service in a network. A service request is generally from a consumer of the service (“service consumer”) to a producer of the service (“service producer”). For example, a service request may be from a network function (NF) node of a service consumer to an NF node of a service producer. The NF node of the service consumer and the NF node of the service producer can communicate directly or indirectly. This is referred to as direct communication and indirect communication respectively. In the case of indirect communication, the NF node of the service consumer and the NF node of the service producer may communicate via a service communication proxy (SCP) node.
In the systems illustrated in
In the systems illustrated in
In the system illustrated in
In the system illustrated in
For the fifth generation core (5GC), from Release 16, the SCP is included as a network element to allow indirect communication between an NF node of a service consumer and an NF node of a service producer. The indirect communication that is used can be either of the two indirect communications options described earlier with reference to
In
As illustrated by arrow 604 of
As illustrated by arrow 606 of
As illustrated by block 612 of
As illustrated by arrow 618 of
As illustrated by arrow 622 of
In
As illustrated by arrow 630 of
As illustrated by arrow 636 of
As illustrated by arrow 644 of
Thus, the procedure is successful when the first NF node 20 supports binding, but unsuccessful when the first NF node 20 does not support binding.
SUMMARYAs mentioned earlier, the procedure illustrated in
It is an object of the disclosure to obviate or eliminate at least some of the above-described disadvantages associated with existing techniques.
Therefore, according to an aspect of the disclosure, there is provided a method for operating a first network node. The method is performed by the first network node. The first network node is a first service communication proxy (SCP) node that is configured to operate as an SCP between a first network function (NF) node of a service consumer and a second NF node of a service producer in the network or wherein the first network node is the second NF node. The first request is for the second NF node to provide a first service requested by the first NF node. The method comprises acquiring information indicative of a functionality supported by the first NF node and operating based on the functionality supported by the first NF node. The information is acquired in response to receiving a first request transmitted towards the second NF node via the first SCP node.
In some embodiments, the information may be acquired from a network repository function (NRF) node.
In some embodiments, the first request received at the first network node may comprise one or more identifiers that allow the first NF node to be identified and acquiring the information from the NRF node may comprise acquiring the information from the NRF node using the one or more identifiers.
In some embodiments, acquiring the information from the NRF node may comprise acquiring the information from a profile of the first NF node stored at the NRF node.
In some embodiments, acquiring the information from the NRF node may comprise initiating transmission of a second request for the information towards the NRF node.
In some embodiments, acquiring the information from the NRF node may comprise receiving the information from the NRF node.
In some embodiments, an entity may comprise the first SCP node and the NRF node.
In some embodiments, the information may be acquired from the first NF node.
In some embodiments, the first request received at the first network node may comprise the information and acquiring the information from the first NF node may comprise acquiring the information from the first request.
In some embodiments, a header of the first request received at the first network node may comprise the information.
In some embodiments, the header of the first request may be a hypertext transfer protocol (HTTP) header.
In some embodiments, the information may be stored in a memory and acquiring the information may comprise acquiring the information from the memory.
In some embodiments, the information stored in the memory may be from a third request transmitted towards the second NF node via the first SCP node, wherein the third request may be for the second NF node to provide the first service requested by the first NF node and the third request may be received at the first network node prior to the first request.
In some embodiments, the method may comprise controlling the memory to store the information from the third request comprising the information in response to receiving the third request.
In some embodiments, a header of the third request may comprise the information.
In some embodiments, the header of the third request may be a hypertext transfer protocol (HTTP) header.
In some embodiments, the first SCP node and the first NF node may be deployed in independent deployment units and/or the first SCP node and the second NF node may be deployed in independent deployment units.
In some embodiments, the first SCP node may be deployed as a distributed network element.
In some embodiments, part of the first SCP node may be is deployed in the same deployment unit as the first NF node, and/or part of the first SCP node may be deployed in the same deployment unit as the second NF node.
In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node and the first SCP node, and/or at least one third SCP node may be configured to operate as an SCP between the first SCP node and the second NF node.
In some embodiments, the first SCP node and one or both of the at least one second SCP node and the at least one third SCP node may be deployed in independent deployment units.
In some embodiments, the at least one second SCP node and/or the at least one third SCP node may be deployed as distributed network elements.
According to another aspect of the disclosure, there is provided a first network node comprising processing circuitry configured to operate in accordance with the method described earlier in respect of the first network node.
In some embodiments, the first network node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the first network node to operate in accordance with the method described earlier in respect of the first network node.
According to another aspect of the disclosure, there is provided a method for providing information to a first network node. The method is performed by a second network node. The second network node is a network repository function (NRF) node or a first network function (NF) node of a service consumer. The first network node is a first service communication proxy (SCP) node configured to operate as an SCP between the first NF node and a second NF node of a service producer in the network or the first network node is the second NF node. The method comprises providing the first network node with access to information indicative of a functionality supported by the first NF node to allow the first network node to operate based on the functionality supported by the first NF node.
In some embodiments, the NRF node may provide the first network node with access to the information by providing the first network node with access to a profile of the first NF node stored at the NRF node, wherein the profile comprises the information.
In some embodiments, the NRF node may provide the first network node with access to the information in response to receiving a second request for the information.
In some embodiments, the NRF node may provide the first network node with access to the information by initiating transmission of the information towards first network node.
In some embodiments, the method performed by the NRF node may comprise receiving a registration request from the first NF node, wherein the registration request comprises the information.
In some embodiments, an entity may comprise the first SCP node and the NRF node.
In some embodiments, the method performed by first NF node may comprise initiating transmission of a first request towards the second NF node via the first SCP node, wherein the first request may be for the second NF node to provide a first service requested by the first NF node.
In some embodiments, the first NF node may provide the first network node with access to the information by the first request comprising the information and/or one or more identifiers that allow the first NF node to be identified, wherein the one or more identifiers are for use by the first network node to acquire the information from the NRF node.
In some embodiments, a header of the first request may comprise the information.
In some embodiments, the header of the first request may be a hypertext transfer protocol (HTTP) header.
In some embodiments, the first NF node may provide the first network node with access to the information by, prior to initiating transmission of the first request, initiating transmission of a third request towards the second NF node via the first SCP node, wherein the third request may be for the second NF node to provide a first service requested by the first NF node and wherein the third request comprises the information.
In some embodiments, a header of the third request may comprise the information.
In some embodiments, the header of the third request is a hypertext transfer protocol (HTTP) header.
In some embodiments, the first SCP node and the first NF node may be deployed in independent deployment units and/or the first SCP node and the second NF node may be deployed in independent deployment units.
In some embodiments, the first SCP node may be deployed as a distributed network element.
In some embodiments, part of the first SCP node may be deployed in the same deployment unit as the first NF node and/or part of the first SCP node may be deployed in the same deployment unit as the second NF node.
In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node and the first SCP node and/or at least one third SCP node may be configured to operate as an SCP between the first SCP node and the second NF node.
In some embodiments, the first SCP node and one or both of the at least one second SCP node and the at least one third SCP node may be deployed in independent deployment units.
In some embodiments, the at least one second SCP node and/or the at least one third SCP node may be deployed as distributed network elements.
According to another aspect of the disclosure, there is provided a second network node comprising processing circuitry configured to operate in accordance with the method described earlier in respect of the second network node.
In some embodiments, the second network node may comprise at least one memory for storing instructions which, when executed by the processing circuitry, cause the second network node to operate in accordance with the method described earlier in respect of the second network node.
According to another aspect of the disclosure, there is provided a method performed by a system. The method comprises the method described earlier in respect of the first network node and/or the method described earlier in respect of the second network node.
According to another aspect of the disclosure, there is provided a system comprising at least one first SCP node as described earlier in respect of the first network node and/or at least one second NF node as described earlier in respect of the first network node, and at least one first NF node as described earlier in respect of the second network node and/or at least one NRF node as described earlier in respect of the second network node.
According to another aspect of the disclosure, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method as described earlier in respect of the first network node and/or second network node.
According to another aspect of the disclosure, there is provided a computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the method as described earlier in respect of the first network node and/or second network node.
Thus, an improved technique is described for providing information to and operating a network node in a network.
For a better understanding of the technique, and to show how it may be put into effect, reference will now be made, by way of example, to the accompanying drawings, in which:
Herein, techniques for handling a service request in a network are described. A service request can also be referred to as a request for a service. Generally, a service is software intended to be managed for users. Herein, a service can be any type of service, such as a communication service (e.g. a notification service or a callback service), a context management (e.g. user equipment context management (UECM)) service, a data management (DM) service, or any other type of service. The techniques described herein can be used in respect of any network, such as any communications or telecommunications network, e.g. cellular network. The network may be a fifth generation (5G) network or any other generation network. In some embodiments, the network may be a core network or a radio access network (RAN). The techniques described herein are implemented by a first service communication proxy (SCP) node and a first network function (NF) node.
An NF is a third generation partnership project (3GPP) adopted or 3GPP defined processing function in a network, which has defined functional behaviour and 3GPP defined interfaces. An NF can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. Herein, the term “node” in relation to an “NF node” will be understood to cover each of these scenarios.
As illustrated in
Briefly, the processing circuitry 12 of the first network node 10, 30 is configured to, in response to receiving a first request transmitted towards the second NF node via the first SCP node, acquire information indicative of a functionality supported by the first NF node. The first request is for the second NF node to provide (e.g. execute or run) a first service requested by the first NF node. The processing circuitry 12 of the first network node 10, 30 is configured to operate based on the functionality supported by the first NF node.
As illustrated in
The processing circuitry 12 of the first network node 10, 30 can be connected to the memory 14 of the first network node 10, 30. In some embodiments, the memory 14 of the first network node 10, 30 may be for storing program code or instructions which, when executed by the processing circuitry 12 of the first network node 10, 30, cause the first network node 10, 30 to operate in the manner described herein in respect of the first network node 10, 30. For example, in some embodiments, the memory 14 of the first network node 10, 30 may be configured to store program code or instructions that can be executed by the processing circuitry 12 of the first network node 10, 30 to cause the first network node 10, 30 to operate in accordance with the method described herein in respect of the first network node 10, 30. Alternatively or in addition, the memory 14 of the first network node 10, 30 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. The processing circuitry 12 of the first network node 10, 30 may be configured to control the memory 14 of the first network node 10, 30 to store information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
In some embodiments, as illustrated in
Although the first network node 10, 30 is illustrated in
The method is performed in response to receiving a first request transmitted towards the second NF node via the first SCP node. The first request is for the second NF node to provide (e.g. execute or run) a first service requested by the first NF node. As illustrated at block 102 of
In some embodiments where the information is acquired from an NRF node, the first request received at the first network node 10, 30 may comprise one or more identifiers that allow the first NF node 20 to be (e.g. uniquely) identified and acquiring the information from the NRF node may comprise acquiring the information from the NRF node 60 using the one or more identifiers. In some embodiments, acquiring the information from the NRF node may comprise acquiring the information from a profile of the first NF node stored at the NRF node. In some embodiments, acquiring the information from the NRF node may comprise initiating transmission of a second request for the information towards the NRF node. In some embodiments, acquiring the information from the NRF node may comprise receiving the information from the NRF node.
In some embodiments where the information is acquired from the first NF node, the first request received at the first network node 10, 30 may comprise the information and acquiring the information from the first NF node may comprise acquiring the information from the first request. In some embodiments, a header of the first request received at the first network node 10, 30 may comprise the information. In some embodiments, the header of the first request may be a hypertext transfer protocol (HTTP) header. This header is a new header, i.e. a header that is not currently included in the first request according to existing techniques. The header can be a custom header.
In some embodiments where the information is acquired from a memory, the information stored in the memory may be from a third request transmitted towards the second NF node 30 via the first SCP node 10. The third request can be for the second NF node 30 to provide the first service requested by the first NF node. The third request is received at the first network node 10, 30 prior to the first request. In some embodiments, in response to receiving the third request comprising the information, the method may comprise controlling the memory to store the information from the third request. In some embodiments, a header of the third request may comprise the information. In some embodiments, the header of the third request may be a hypertext transfer protocol (HTTP) header. This header is a new header, i.e. a header that is not currently included in the third request according to existing techniques. The header can be a custom header.
In some embodiments, the first SCP node 10 may acquire the information in any of the ways described earlier and the second NF node 30 may acquire the information from the first SCP node 10. For example, the first SCP node 10 may initiate transmission of the information towards the second NF node 30 according to some embodiments. In these embodiments, the second NF node 30 acquires the information by receiving the information from the first SCP node 10.
In an example, the acquired information referred to herein may be indicative of whether or not the first NF node 20 supports binding and the first network node 10, 30 can operate based on whether or not binding is supported by the first NF node 20. For example, the first network node 10, 30 may include binding information in a response to a request received from the first NF node 20 if the acquired information is indicative that the first NF node 20 supports binding and/or may omit binding information from the response to the request received from the first NF node 20 if the acquired information is indicative that the first NF node 20 does not support binding. Thus, more generally, the first network node 10, 30 may provide the first NF node 20 with information that the first NF node 20 can actually use.
In another example, the acquired information referred to herein may be indicative of whether or not the first NF node 20 supports management of load provided by one or more NF nodes of the service producer (e.g. the second NF node 30, the third NF node 70, and/or any other NF nodes of the service producer) and the first network node 10, 30 can operate based on whether or not load management is supported by the first NF node 20. For example, the first network node 10, 30 may handle the load management (e.g. load balancing) if the acquired information is indicative that the first NF node 20 does not support load management.
As illustrated in
Briefly, the processing circuitry 22 of the second network node 20, 60 is configured to, provide the first network node 10, 30 with access to information indicative of a functionality supported by the first NF node to allow the first network node 10, 30 to operate based on the functionality supported by the first NF node.
As illustrated in
The processing circuitry 22 of the second network node 20, 60 can be connected to the memory 24 of the second network node 20, 60. In some embodiments, the memory 24 of the second network node 20, 60 may be for storing program code or instructions which, when executed by the processing circuitry 22 of the second network node 20, 60, cause the second network node 20, 60 to operate in the manner described herein in respect of the second network node 20, 60. For example, in some embodiments, the memory 24 of the second network node 20, 60 may be configured to store program code or instructions that can be executed by the processing circuitry 22 of the second network node 20, 60 to cause the second network node 20, 60 to operate in accordance with the method described herein in respect of the second network node 20, 60. Alternatively or in addition, the memory 24 of the second network node 20, 60 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. The processing circuitry 22 of the second network node 20, 60 may be configured to control the memory 24 of the second network node 20, 60 to store information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.
In some embodiments, as illustrated in
Although the second network node 20, 60 is illustrated in
As illustrated at block 202 of
For example, in an embodiment where the second network node 20, 60 is an NRF node 60, the NRF node 60 may provide the first network node 10, 30 with access to the information by providing the first network node 10, 30 with access to a profile of the first NF node stored at the NRF node 60. In this embodiment, the profile of the first NF node comprises the information. Thus, the profile of the first NF node comprises a new attribute by way of this information, i.e. an attribute that is not currently included in the profile of an NF node of a consumer according to existing techniques.
In some embodiments, the NRF node 60 may provide the first network node 10, 30 with access to the information in response to receiving a second request for the information. In some embodiments, the NRF node 60 may provide the first network node 10, 30 with access to the information by initiating transmission of the information towards first network node 10, 30. In some embodiments, the method performed by the NRF node 60 may comprise receiving a registration request from the first NF node and the registration request can comprise the information.
In an embodiment where the second network node 20, 60 is the first NF node 20, the method performed by the first NF node 20 may comprise initiating transmission of a first request towards the second NF node 30 via the first SCP node 10. The first request can be for the second NF node 30 to provide (e.g. execute or run) a first service requested by the first NF node 20. In some embodiments, the first NF node 20 may provide the first network node 10, 30 with access to the information by the first request comprising the information. In some embodiments, a header of the first request may comprise the information. In some embodiments, the header of the first request may be a hypertext transfer protocol (HTTP) header, such as a new 3GPP specific HTTP header. Alternatively or in addition, in some embodiments, the first NF node 20 may provide the first network node 10, 30 with access to the information by the first request comprising one or more identifiers that allow the first NF node 20 to be (e.g. uniquely) identified. In these embodiments, the one or more identifiers are for use by the first network node 10, 30 to acquire the information from the NRF node 60.
The first request referred to herein may be an initial request or a subsequent request. In some embodiments, the information may be comprised in the initial request only. In these embodiments, the first network node 10, 30 may store the information. Alternatively, in some embodiments, the information may be comprised in all requests, i.e. the initial request and all subsequent requests.
In some embodiments, the first NF node 20 may provide the first network node 10, 30 with access to the information by, prior to initiating transmission of the first request, initiating transmission of a third request towards the second NF node 30 via the first SCP node 10. In these embodiments, the third request comprises the information. The third request can be for the second NF node 30 to provide (e.g. execute or run) a first service requested by the first NF node 20. In some embodiments, a header of the third request may comprise the information. In some embodiments, the header of the third request may be a hypertext transfer protocol (HTTP) header. In embodiments involving a third request, the third request referred to herein may be the initial request and the first request may be a subsequent request, such that all requests comprise the information.
There is also provided a system. The system can comprise at least one first network node 10, 30 as described herein and/or at least one second network node 20, 60 as described herein. For example, the system can comprise at least one first SCP node 10 configured to operate in the manner described herein in respect of the first network node, at least one second NF node 30 configured to operate in the manner described herein in respect of the first network node, at least one first NF node 20 as described herein in respect of the second network node, and/or at least one NRF node 60 as described herein in respect of the second network node. The system may also comprise any one or more of the other nodes mentioned herein.
The system illustrated in
In some embodiments, the first SCP node 10 and the first NF node 20 may be deployed in independent deployment units, the first SCP node 10 and the second NF node 30 may be deployed in independent deployment units, and/or the first SCP node 10 and the third NF node 70 may be deployed in independent deployment units. Thus, an SCP node based on independent deployment units is possible, as described in 3GPP TS 23.501 V16.4.0. In other embodiments, the first SCP node 10 may be deployed as a distributed network element. For example, in some embodiments, part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the first NF node 20, part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the second NF node 30, and/or part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the third NF node 70. Thus, an SCP node based on service mesh is possible, as described in 3GPP TS 23.501 V16.4.0.
In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node 20 and the first SCP node 10, at least one third SCP node may be configured to operate as an SCP between the first SCP node 10 and the second NF node 30, and/or at least one fourth SCP node may be configured to operate as an SCP between the first SCP node 10 and the third NF node 70. Thus, a multipath of SCP nodes is possible. In some of these embodiments, the first SCP node 10 and one or more of the at least one at least one second SCP node, the at least one third SCP node, and the at least one fourth SCP node may be deployed in independent deployment units. In some embodiments, the at least one second SCP node and/or the at least one third SCP node may be deployed as distributed network elements.
Steps 500-502 and 600-618 of
Herein, binding information can be any information that is indicative of one or more parameters by which the first NF node 20 is bound when selecting a second service 40, 80 in an NF node 30, 70 of a service producer for a subsequent second request. The subsequent second request can be a subsequent second request that follows the first (or third) request directly, or a subsequent second request that follows the first (or third) request indirectly, e.g. it may be a request that follows another one or more requests that follow the first (or third) request. In some embodiments, the subsequent second request may be linked to the first service 40. For example, the subsequent second request may be associated with a resource used to provide the first service 40. The first service 40 and the second service 40 may be the same service, or the first service 40 and the second service 80 may be different services. The term “binding information” is well-recognised in the art and thus a person skilled in the art will be aware of various parameters that may be indicated by the binding information referred to herein. Nevertheless, some examples will be provided for completeness.
For example, in some embodiments, the one or more parameters may comprise a parameter that binds the first NF node 20 to selecting the second service 40, 80 in the second NF node 30 for the subsequent second request, or a parameter that binds the first NF node 20 to selecting the second service 40, 80 in a third NF node 70 for the subsequent second request. In some embodiments, the parameter that binds the first NF node 20 to selecting the second service 40, 80 in the second NF node 30 for the subsequent second request comprises an identifier that (e.g. uniquely) identifies the second NF node 30 and/or the parameter that binds the first NF node 20 to selecting the second service 40, 80 in the third NF node 70 for the subsequent second request comprises an identifier that (e.g. uniquely) identifies the set 402 of NF nodes. In some embodiments, the binding information can comprise an identifier that (e.g. uniquely) identifies the second NF node 30 (or the selected instance of the second NF node 30, e.g. NFp instance Id), an identifier that (e.g. uniquely) identifies the set 402 of NF nodes that comprises the second NF node 30 (e.g. NFp Set X Id), and a name of the first service 40 (e.g. Service A). Other examples of one or more parameters that the binding information may comprise are those in Table 6.3.1.0-1 of 3GPP TS 23.501 V16.5.0.
Returning back to
Thus, with reference to
In more detail, the first request 604 received at the first SCP node 10 comprises one or more identifiers (e.g. the NF instance Id of the first NF node 20) that allow the first NF node 20 to be (e.g. uniquely) identified. It can be mandatory for the first request 604 to comprise the one or more identifiers. As illustrated by block 700 of
In particular, as illustrated by arrow 702 of
In some embodiments, the information can be comprised in a profile of the first NF node 20 stored at the NRF node 60. Thus, in some embodiments, the NRF node 60 can provide the first SCP node 10 with access to the information by providing the first SCP node 10 with access to the profile of the first NF node. The profile of the first NF node 20 may comprise the one or more identifiers, such that the NRF node 60 can identify the profile that belongs to the first NF node 20. It may then be the profile of the first NF node 20 comprising the information that is received by the first SCP node 10. In these embodiments, as illustrated by block 706 of
As illustrated by block 708 of
Although the embodiment illustrated in
The system illustrated in
In some embodiments, the first SCP node 10 and the first NF node 20 may be deployed in independent deployment units, the first SCP node 10 and the second NF node 30 may be deployed in independent deployment units, and/or the first SCP node 10 and the third NF node 70 may be deployed in independent deployment units. Thus, an SCP node based on independent deployment units is possible, as described in 3GPP TS 23.501 V16.4.0. In other embodiments, the first SCP node 10 may be deployed as a distributed network element. For example, in some embodiments, part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the first NF node 20, part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the second NF node 30, and/or part (e.g. a service agent) of the first SCP node 10 may be deployed in the same deployment unit as the third NF node 70. Thus, an SCP node based on service mesh is possible, as described in 3GPP TS 23.501 V16.4.0.
In some embodiments, at least one second SCP node may be configured to operate as an SCP between the first NF node 20 and the first SCP node 10, at least one third SCP node may be configured to operate as an SCP between the first SCP node 10 and the second NF node 30, and/or at least one fourth SCP node may be configured to operate as an SCP between the first SCP node 10 and the third NF node 70. Thus, a multipath of SCP nodes is possible. In some of these embodiments, the first SCP node 10 and one or more of the at least one at least one second SCP node, the at least one third SCP node, and the at least one fourth SCP node may be deployed in independent deployment units. In some embodiments, the at least one second SCP node and/or the at least one third SCP node may be deployed as distributed network elements.
Steps 500-502 and 600-602 of
Steps 606-618 of
As illustrated by block 804 of
Although the embodiment illustrated in
There is also provided a computer program comprising instructions which, when executed by processing circuitry (such as the processing circuitry 12 of the first network node 10, 30 described earlier and/or the processing circuitry 22 of the second network node 20, 60 described earlier), cause the processing circuitry to perform at least part of the method described herein. There is provided a computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry (such as the processing circuitry 12 of the first network node 10, 30 described earlier and/or the processing circuitry 22 of the second network node 20, 60 described earlier) to cause the processing circuitry to perform at least part of the method described herein. There is provided a computer program product comprising a carrier containing instructions for causing processing circuitry (such as the processing circuitry 12 of the first network node 10, 30 described earlier and/or the processing circuitry 22 of the second network node 20, 60 described earlier) to perform at least part of the method described herein. In some embodiments, the carrier can be any one of an electronic signal, an optical signal, an electromagnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.
Other embodiments include those defined in the following numbered statements:
Embodiment 1. A method for operating a first network node (10, 30), wherein the method is performed by the first network node (10, 30), wherein the first network node (10, 30) is a first service communication proxy, SCP, node (10) that is configured to operate as an SCP between a first network function, NF, node (20) of a service consumer and a second NF node (30) of a service producer in the network or wherein the first network node is the second NF node (30), the method comprising:
-
- in response to receiving a first request (604, 616, 800) transmitted towards the second NF node (30) via the first SCP node (10), wherein the first request (604, 616, 800) is for the second NF node (30) to provide a first service (40) requested by the first NF node (20):
- acquiring (102, 700, 702, 704, 800, 802) information indicative of a functionality supported by the first NF node (20); and
- operating (104, 708, 804) based on the functionality supported by the first NF node (20).
- in response to receiving a first request (604, 616, 800) transmitted towards the second NF node (30) via the first SCP node (10), wherein the first request (604, 616, 800) is for the second NF node (30) to provide a first service (40) requested by the first NF node (20):
Embodiment 2. A method according to Embodiment 1, wherein:
-
- the information is acquired from a network repository function, NRF, node (60).
Embodiment 3. A method according to Embodiment 2, wherein:
-
- the first request (604, 616) received at the first network node (10, 30) comprises one or more identifiers that allow the first NF node (20) to be identified; and
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
- acquiring the information from the NRF node (60) using the one or more identifiers.
Embodiment 4. A method according to Embodiment 2 or 3, wherein:
-
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
- acquiring the information from a profile of the first NF node (20) stored at the NRF node (60).
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
Embodiment 5. A method according to any of Embodiments 2 to 4, wherein:
-
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
- initiating (702) transmission of a second request (702) for the information towards the NRF node (60).
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
Embodiment 6. A method according to any of Embodiments 2 to 5, wherein:
-
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
- receiving (704) the information from the NRF node (60).
- acquiring (102, 700, 702, 704) the information from the NRF node (60) comprises:
Embodiment 7. A method according to any of Embodiments 1 to 6, wherein:
-
- an entity comprises the first SCP node (10) and the NRF (60) node.
Embodiment 8. A method according to any of Embodiments 1 to 7, wherein:
-
- the information is acquired from the first NF node (20).
Embodiment 9. A method according to Embodiment 8, wherein:
-
- the first request (800) received at the first network node (10, 30) comprises the information; and
- acquiring (102, 800, 804) the information from the first NF node (20) comprises:
- acquiring (804) the information from the first request (700, 800).
Embodiment 10. A method according to Embodiment 9, wherein:
-
- a header of the first request (800) received at the first network node (10, 30) comprises the information.
Embodiment 11. A method according to Embodiment 10, wherein:
-
- the header of the first request (800) is a hypertext transfer protocol, HTTP, header.
Embodiment 12. A method according to any of Embodiments 1 to 11, wherein:
-
- the information is stored in a memory (14); and
- acquiring (102) the information comprises:
- acquiring the information from the memory (14).
Embodiment 13. A method according to Embodiment 12, wherein:
-
- the information stored in the memory (14) is from a third request transmitted towards the second NF node (30) via the first SCP node (10), wherein the third request is for the second NF node (30) to provide the first service (40) requested by the first NF node (20) and the third request is received at the first network node (10, 30) prior to the first request (800).
Embodiment 14. A method according to Embodiment 13, the method comprising:
-
- in response to receiving the third request comprising the information:
- controlling the memory (14) to store the information from the third request.
- in response to receiving the third request comprising the information:
Embodiment 15. A method according to Embodiment 13 or 14, wherein:
-
- a header of the third request comprises the information.
Embodiment 16. A method according to Embodiment 15, wherein:
-
- the header of the third request is a hypertext transfer protocol, HTTP, header.
Embodiment 17. A method according to any of Embodiments 1 to 16, wherein:
-
- the first SCP node (10) and the first NF node (20) are deployed in independent deployment units; and/or
- the first SCP node (10) and the second NF node (30) are deployed in independent deployment units.
Embodiment 18. A method according to any of Embodiments 1 to 16, wherein:
-
- the first SCP node (10) is deployed as a distributed network element.
Embodiment 19. A method according to Embodiment 18, wherein:
-
- part of the first SCP node (10) is deployed in the same deployment unit as the first NF node (20); and/or
- part of the first SCP node (10) is deployed in the same deployment unit as the second NF node (30).
Embodiment 20. A method according to any of Embodiments 1 to 19, wherein:
-
- at least one second SCP node is configured to operate as an SCP between the first NF node (20) and the first SCP node (10); and/or
- at least one third SCP node is configured to operate as an SCP between the first SCP node (10) and the second NF node (30).
Embodiment 21. A method according to Embodiment 20, wherein:
-
- the first SCP node (10) and one or both of the at least one second SCP node and the at least one third SCP node are deployed in independent deployment units.
Embodiment 22. A method according to Embodiment 20, wherein:
-
- the at least one second SCP node and/or the at least one third SCP node are deployed as distributed network elements.
Embodiment 23. A first network node (10, 30) comprising:
-
- processing circuitry (12) configured to operate in accordance with any of Embodiments 1 to 22.
Embodiment 24. A first network node (10, 30) according to Embodiment 23, wherein:
-
- the first network node (10, 30) comprises:
- at least one memory (14) for storing instructions which, when executed by the processing circuitry (12), cause the first network node (10, 30) to operate in accordance with any of Embodiments 1 to 22.
- the first network node (10, 30) comprises:
Embodiment 25. A method for providing information to a first network node (10, 30), wherein the method is performed by a second network node (20, 60), wherein the second network node (20, 60) is a network repository function, NRF, node (60) or a first network function, NF, node (20) of a service consumer, wherein the first network node (10, 30) is a first service communication proxy, SCP, node (10) configured to operate as an SCP between the first NF node (20) and a second NF node (30) of a service producer in the network or wherein the first network node (10, 30) is the second NF node (30), the method comprising:
-
- providing (202, 704, 800) the first network node (10, 30) with access to information indicative of a functionality supported by the first NF node (20) to allow the first network node (10, 30) to operate based on the functionality supported by the first NF node (20).
Embodiment 26. A method according to Embodiment 25, wherein:
-
- the NRF node (60) provides the first network node (10, 30) with access to the information by:
- providing (704) the first network node (10, 30) with access to a profile of the first NF node (20) stored at the NRF node (60), wherein the profile comprises the information.
- the NRF node (60) provides the first network node (10, 30) with access to the information by:
Embodiment 27. A method according to Embodiment 25 or 26, wherein:
-
- the NRF node (60) provides the first network node (10, 30) with access to the information in response to receiving a second request (702) for the information.
Embodiment 28. A method according to any of Embodiments 25 to 27, wherein:
-
- the NRF node (60) provides the first network node (10, 30) with access to the information by:
- initiating (704) transmission of the information towards first network node (10, 30).
- the NRF node (60) provides the first network node (10, 30) with access to the information by:
Embodiment 29. A method according to any of Embodiments 25 to 28, wherein the method performed by the NRF node (60) comprises:
-
- receiving a registration request from the first NF node (20), wherein the registration request comprises the information.
Embodiment 30. A method according to any of Embodiments 25 to 29, wherein:
-
- an entity comprises the first SCP node (10) and the NRF (60) node.
Embodiment 31. A method according to any of Embodiments 25 to 30, wherein:
-
- the method performed by first NF node (20) comprises:
- initiating transmission of a first request (604, 616, 800) towards the second NF node (30) via the first SCP node (10), wherein the first request (604, 616, 800) is for the second NF node (30) to provide a first service (40) requested by the first NF node (20).
- the method performed by first NF node (20) comprises:
Embodiment 32. A method according to Embodiment 31, wherein:
-
- the first NF node (20) provides the first network node (10, 30) with access to the information by:
- the first request (604, 616, 800) comprising the information and/or one or more identifiers that allow the first NF node (20) to be identified, wherein the one or more identifiers are for use by the first network node (10, 30) to acquire the information from the NRF node (60).
- the first NF node (20) provides the first network node (10, 30) with access to the information by:
Embodiment 33. A method according to Embodiment 32, wherein:
-
- a header of the first request (800) comprises the information.
Embodiment 34. A method according to Embodiment 33, wherein:
-
- the header of the first request (800) is a hypertext transfer protocol, HTTP, header.
Embodiment 35. A method according to any of Embodiments 31 to 34, wherein:
-
- the first NF node (20) provides the first network node (10, 30) with access to the information by:
- prior to initiating transmission of the first request (604, 616, 800), initiating transmission of a third request towards the second NF node (30) via the first SCP node (10), wherein the third request is for the second NF node (30) to provide a first service (40) requested by the first NF node (20) and wherein the third request comprises the information.
- the first NF node (20) provides the first network node (10, 30) with access to the information by:
Embodiment 36. A method according to Embodiment 35, wherein:
-
- a header of the third request comprises the information.
Embodiment 37. A method according to Embodiment 36, wherein:
-
- the header of the third request is a hypertext transfer protocol, HTTP, header.
Embodiment 38. A method according to any of Embodiments 25 to 37, wherein:
-
- the first SCP node (10) and the first NF node (20) are deployed in independent deployment units; and/or
- the first SCP node (10) and the second NF node (30) are deployed in independent deployment units.
Embodiment 39. A method according to any of Embodiments 25 to 37, wherein:
-
- the first SCP node (10) is deployed as a distributed network element.
Embodiment 40. A method according to Embodiment 39, wherein:
-
- part of the first SCP node (10) is deployed in the same deployment unit as the first NF node (20); and/or
- part of the first SCP node (10) is deployed in the same deployment unit as the second NF node (30).
Embodiment 41. A method according to any of Embodiments 25 to 40, wherein:
-
- at least one second SCP node is configured to operate as an SCP between the first NF node (20) and the first SCP node (10); and/or
- at least one third SCP node is configured to operate as an SCP between the first SCP node (10) and the second NF node (30).
Embodiment 42. A method according to Embodiment 41, wherein:
-
- the first SCP node (10) and one or both of the at least one second SCP node and the at least one third SCP node are deployed in independent deployment units.
Embodiment 43. A method according to Embodiment 41, wherein:
-
- the at least one second SCP node and/or the at least one third SCP node are deployed as distributed network elements.
Embodiment 44. A second network node (20, 60) comprising:
-
- processing circuitry (22) configured to operate in accordance with any of Embodiments 25 to 43.
Embodiment 45. A second network node (20, 60) according to Embodiment 44, wherein:
-
- the second network node (20, 60) comprises:
- at least one memory (24) for storing instructions which, when executed by the processing circuitry (22), cause the second network node (20, 60) to operate in accordance with any of Embodiments 25 to 43.
- the second network node (20, 60) comprises:
Embodiment 46. A method performed by a system, the method comprising:
-
- the method according to any of Embodiments 1 to 22; and/or
- the method according to any of Embodiments 25 to 43.
Embodiment 47. A system comprising:
-
- at least one first SCP node (10) according to Embodiment 23 or 24 and/or at least one second NF node (30) according to Embodiment 23 or 24; and
- at least one first NF node (20) according to Embodiment 44 or 45 and/or at least one NRF node (60) according to Embodiment 44 or 45.
Embodiment 48. A computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method according to any of Embodiments 1 to 22 and/or any of Embodiments 25 to 43.
Embodiment 49. A computer program product, embodied on a non-transitory machine-readable medium, comprising instructions which are executable by processing circuitry to cause the processing circuitry to perform the method according to any of Embodiments 1 to 22 and/or any of Embodiments 25 to 43.
In some embodiments, the first network node functionality and/or the second network node functionality described herein can be performed by hardware. Thus, in some embodiments, any one or more of the first network node 10, 30 and the second network node 20, 60 described herein can be a hardware node. However, it will also be understood that optionally at least part or all of the first network node functionality and/or the second network node functionality described herein can be virtualized. For example, the functions performed by any one or more of the first network node 10, 30 and the second network node 20, 60 described herein can be implemented in software running on generic hardware that is configured to orchestrate the node functionality. Thus, in some embodiments, any one or more of the first network node 10, 30 and the second network node 20, 60 described herein can be a virtual node. In some embodiments, at least part or all of the first network node functionality and/or the second network node functionality described herein may be performed in a network enabled cloud. The first network node functionality and/or the second network node functionality described herein may all be at the same location or at least some of the node functionality may be distributed.
It will be understood that at least some or all of the method steps described herein can be automated in some embodiments. That is, in some embodiments, at least some or all of the method steps described herein can be performed automatically. The method described herein can be a computer-implemented method.
Thus, in the manner described herein, there is advantageously provided improved techniques for network node operation. In particular, by way of the technique described herein, it is possible for the first network node (e.g. the first SCP node 10 and/or the second NF node 30) to know if the first NF node supports a certain functionality. The first network node 10, 30 can thus adapt its behaviour depending on whether the first NF node 20 supports a certain functionality. In some cases, this may be crucial for some functionality to work and thus the network node operation is advantageously improved.
It should be noted that the above-mentioned embodiments illustrate rather than limit the idea, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.
Claims
1. A method for operating a first network node performed by the first network node, the first network node being a first service communication proxy, SCP, node that is configured to operate as an SCP between a first network function, NF, node of a service consumer and a second NF node of a service producer in the network or the first network node being the second NF node, the method comprising:
- acquiring information indicative of a functionality supported by the first NF node in response to receiving a first request transmitted towards the second NF node via the first SCP node, the first request being for the second NF node to provide a first service requested by the first NF node; and
- operating based on the functionality supported by the first NF node.
2. The method as claimed in claim 1, wherein:
- the information is acquired from a network repository function, NRF, node.
3. The method as claimed in claim 2, wherein:
- the first request received at the first network node comprises one or more identifiers that allow the first NF node to be identified; and
- acquiring the information from the NRF node comprises: acquiring the information from the NRF node using the one or more identifiers.
4. The method as claimed in claim 2, wherein:
- acquiring the information from the NRF node comprises: acquiring the information from a profile of the first NF node stored at the NRF node.
5. The method as claimed in claim 2, wherein:
- acquiring the information from the NRF node comprises: initiating transmission of a second request for the information towards the NRF node.
6. The method as claimed in claim 2, wherein:
- acquiring the information from the NRF node comprises: receiving the information from the NRF node.
7. The method as claimed in claim 1, wherein:
- the information is acquired from the first NF node.
8. The method as claimed in claim 7, wherein:
- the first request received at the first network node comprises the information; and
- acquiring the information from the first NF node comprises: acquiring the information from the first request.
9. (canceled)
10. (canceled)
11. The method as claimed in claim 1, wherein:
- the information is stored in a memory; and
- acquiring the information comprises: acquiring the information from the memory.
12. The method as claimed in claim 11, wherein:
- the information stored in the memory is from a third request transmitted towards the second NF node via the first SCP node, wherein the third request is for the second NF node to provide the first service requested by the first NF node and the third request is received at the first network node prior to the first request.
13.-15. (canceled)
16. A first network node, the first network node being a first service communication proxy, SCP, node that is configured to operate as an SCP between a first network function, NF, node of a service consumer and a second NF node of a service producer in the network or the first network node being the second NF node, the first network node comprising:
- processing circuitry; and
- at least one memory for storing instructions which, when executed by the processing circuitry, cause the first network node to: acquire information indicative of a functionality supported by the first NF node in response to receiving a first request transmitted towards the second NF node via the first SCP node, the first request being for the second NF node to provide a first service requested by the first NF node; and operate based on the functionality supported by the first NF node.
17. (canceled)
18. A method for providing information to a first network node performed by a second network node, the second network node being a network repository function, NRF, node or a first network function, NF, node of a service consumer, the first network node being a first service communication proxy, SCP, node configured to operate as an SCP between the first NF node and a second NF node of a service producer in the network or the first network node being the second NF node, the method comprising:
- providing the first network node with access to information indicative of a functionality supported by the first NF node to allow the first network node to operate based on the functionality supported by the first NF node.
19. The method as claimed in claim 18, wherein:
- the NRF node provides the first network node with access to the information by: providing the first network node with access to a profile of the first NF node stored at the NRF node, wherein the profile comprises the information.
20. The method as claimed in claim 18, wherein:
- the NRF node provides the first network node with access to the information in response to receiving a second request for the information.
21. The method as claimed in claim 18, wherein:
- the NRF node provides the first network node with access to the information by: initiating transmission of the information towards first network node.
22. The method as claimed in claim 18, wherein the method performed by the NRF node comprises:
- receiving a registration request from the first NF node, wherein the registration request comprises the information.
23. The method as claimed in claim 18, wherein:
- the method performed by first NF node comprises: initiating transmission of a first request towards the second NF node via the first SCP node, wherein the first request is for the second NF node to provide a first service requested by the first NF node.
24. The method as claimed in claim 23, wherein:
- the first NF node provides the first network node with access to the information by: the first request comprising one or both of the information and one or more identifiers that allow the first NF node to be identified, wherein the one or more identifiers are for use by the first network node to acquire the information from the NRF node.
25. (canceled)
26. (canceled)
27. The method as claimed in claim 23, wherein:
- the first NF node provides the first network node with access to the information by: prior to initiating transmission of the first request, initiating transmission of a third request towards the second NF node via the first SCP node, wherein the third request is for the second NF node to provide a first service requested by the first NF node and wherein the third request comprises the information.
28. (canceled)
29. (canceled)
30. A second network node, the second network node being a network repository function, NRF, node or a first network function, NF, node of a service consumer, the first network node being a first service communication proxy, SCP, node configured to operate as an SCP between the first NF node and a second NF node of a service producer in the network or the first network node being the second NF node, the second network node comprising:
- processing circuitry; and
- at least one memory for storing instructions which, when executed by the processing circuitry, cause the second network node to: provide the first network node with access to information indicative of a functionality supported by the first NF node to allow the first network node to operate based on the functionality supported by the first NF node.
31.-35. (canceled)
Type: Application
Filed: Jun 25, 2021
Publication Date: Aug 31, 2023
Inventors: Maria Cruz Bartolome RODRIGO (Madrid), Magnus HALLENSTAL (Täby)
Application Number: 18/005,693