WO2023237769A1

WO2023237769A1 - Data handling

Info

Publication number: WO2023237769A1
Application number: PCT/EP2023/065556
Authority: WO
Inventors: Emiliano MERINO; Maria Cruz Bartolome Rodrigo
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-06-10
Filing date: 2023-06-09
Publication date: 2023-12-14

Abstract

The present application relates to a method (400) for handling data in a network. The method is performed by a network repository function (NRF) node. The method comprises receiving (410) a first message from a first network node. The first network node is one of a plurality of first network function (NF) nodes of a service producer or the first network node is a first service communication proxy (SCP) node configured to operate as an SCP between the NRF node and the plurality of first NF nodes. The first message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. The method comprises handling (420) the common data based on the first message.

Description

DATA HANDLING

Technical Field

The disclosure relates to methods for handling data in a network, and nodes configured to operate in accordance with those methods.

There 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.

Figure 1A-D illustrates different existing systems for handling service requests, as set out in the Third Generation Partnership Project (3GPP) Technical Standard (TS) 23.501 v16.4.0. In more detail, Figures 1A and 1 B illustrate systems that use direct communication, while Figures 10 and 1 D illustrate systems that use indirect communication.

In the systems illustrated in Figures 1A and 1 B, a service request is sent directly from the NF node of the service consumer to the NF node of the service producer. A response to the service request is sent directly from the NF node of the service producer to the NF node of the service consumer. Similarly, any subsequent service requests are sent directly from the N F node of the service consumer to the N F node of the service producer. The system illustrated in Figure 1 B also comprises a network repository function (NRF) node. Thus, in the system illustrated in Figure 1 B, the NF node of the service consumer can query the NRF node to discover suitable NF nodes of the service producer to which to send the service request. In response to such a query, the NF node of the service consumer can receive an NF profile for one or more NF nodes of the service producer and, based on the received NF profile(s) can select an NF node of the service producer to which to send the service request. In the system illustrated in Figure 1A, the NRF node is not used and instead the NF node of the service consumer may be configured with the NF profile(s) of the NF node(s) of the service producer.

In the systems illustrated in Figures 1C and 1 D, a service request is sent indirectly from the NF node of the service consumer to the NF node of the service producer via a service communication proxy (SCP) node. A response to the service request is sent indirectly from the NF node of the service producer to the NF node of the service consumer via the SCP. Similarly, any subsequent service requests are sent indirectly from the NF node of the service consumer to the NF node of the service producer via the SCP. The systems illustrated in Figures 1C and D also comprise an NRF node.

In the system illustrated in Figure 1 C, the NF node of the service consumer can query the NRF node to discover suitable NF nodes of the service producer to which to send the service request. In response to such a query, the NF node of the service consumer can receive an NF profile for one or more NF nodes of the service producer and, based on the received NF profile(s) can select an NF node of the service producer to which to send the service request. In this case, the service request sent from the NF node of the service consumer to the SCP comprises the address of the selected NF node of the service producer. The SCP can forward the service request without performing any further discovery or selection. In case the selected NF node of the service producer is not accessible for any reason, it may be up to the NF node of the service consumer to find an alternative. In other cases, the SCP may communicate with the NRF node to acquire selection parameters (e.g. location, capacity, etc.) and the SCP may select an NF node of the service producer to which to send the service request.

In the system illustrated in Figure 1 D, the NF node of the service consumer does not carry out the discovery or selection process. Instead, the NF node of the service consumer adds any necessary discovery and selection parameters (required to find a suitable NF node of the service producer) to the service request that it sends via the SCP. The SCP uses the request address and the discovery and selection parameters in the service request to route the service request to a suitable NF node of the service producer. The SCP can perform discovery with the NRF node. 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 Figures 10 and 1 D.

As described above, in 5GC, an NF service producer (NFp), may register with the NRF. To register with the NRF, the NFp may register a respective NF profile with the NRF. Alternatively, the NFp may register its own NF profile with each NF service consumer (NFc), for example in a similar manner to that described above with respect to Figure 1A. In such examples, the NF profile is stored locally by each NFc. However, in some examples, registering the NF profile of the NFp with each NFc may not be an efficient solution due to the large Operations and Maintenance (O&M) tasks associated with such examples, which may substantially increase operational expenditure (OPEX).

The NF profile is a data structure that contains information which is published by the NRF to enable an NFc to select an appropriate NFp for a given service. The NF profile data structure is defined in 3GPP TS 29.510 v17.5.0.

A plurality of NFps which provide the same service may, in some examples, be defined as an NF set or NF service set. The NF set and NF service set concepts are defined in 3GPP TS 23.501 v17.3.0, which recites:

“NF Service Set: A group of interchangeable NF service instances of the same service type within an NF instance. The NF service instances in the same NF Service Set have access to the same context data".

“NF Set: A group of interchangeable NF instances of the same type, supporting the same services and the same Network Slice(s). The NF instances in the same NF Set may be geographically distributed but have access to the same context data".

In examples according to the present disclosure, the term “interchangeable” means that all the members of an NF set or NF service set are functionally equivalent, that is, they are able to provide the same service.

A plurality of NFps which provide the same service may, in other examples, be defined as an NF group. An NF group is also defined in 3GPP, and refers to the NF instances or NF service instances, which provide service to a partition or a segment of subscribers. In other words, any NF instance or NF service instance that belongs to the same NF group is able to provide a service to the same subscribers. All members of an NF group may also be considered “interchangeable”. The NF group concept is defined in 3GPP TS 23.501 v17.3.0, which recites:

“PCF [policy control function] Group ID [identifier]: This refers to one or more PCF instances managing a specific set of SUPIs [subscription permanent identifiers]. A PCF Group consists of one or multiple PCF Sets.

AU SF [authentication server function] Group ID: This refers to one or more AUSF instances managing a specific set of SUPIs. An AUSF Group consists of one or multiple AUSF Sets.

BSF [binding support function] Group ID: This refers to one or more BSF instances managing a specific set of SUPIs or GPSIs [general public subscription identifiers]. A BSF Group consists of one or multiple BSF Sets.

CHF [charging function] Group ID: This refers to one or more CHF instances managing a specific set of SUPIs.

UDM [unified data management] Group ID: This refers to one or more UDM instances managing a specific set of SUPIs. An UDM Group consists of one or multiple UDM Sets.

UDR Group ID: This refers to one or more UDR instances managing a specific set of SUPIs. An UDR Group consists of one or multiple UDR Sets".

Summary

The information included in the NF profile of an NFp can determine the functionality and capabilities of each NF instance or NF service instance.

As described above, NFps, which belong to the same NF set, NF service set or NF group are able to provide “interchangeable” functionality. For the NFps to be “interchangeable” at least some of the data defined in the NF profile of one NF instance or NF service instance must be the same as the data defined in the NF profile in another NF instance or NF service instance if both are defined as members of the same NF (service) set or as part of an NF Group. This is due to the fact that the NF instances or NF service instances which are members of the same NF (service) Set and/or NF Group are functionally equivalent, where the data in the NF profile of the NF instances or NF service instances determines the provided functionality. As such, at least some of the data comprised in the NF profile of each member of an NF set, NF service set or NF group is the same.

In some examples according to the present disclosure, data that is common between NF profiles of an NF set or NF group may be referred to as ‘common data’. In conventional examples, said common data has not yet been defined. The lack of an ability to identify common data in the NF profiles of a plurality of NF nodes (e.g. the NF profiles of an NF set, NF service set, or NF group) may lead to several drawbacks. In particular, the drawbacks can include bandwidth and signalling inefficiency, transient lack of data consistency, and/or inefficient storage of NF profiles in the NRF.

It is an object of the disclosure to obviate or eliminate at least some of the abovedescribed disadvantages associated with existing techniques.

Therefore, according to a first aspect of the present disclosure, there is provided a first method for handling data in a network. The first method is performed by a network repository function (NRF) node. The first method comprises receiving a first message from a first network node. The first network node is one of a plurality of first network function (NF) nodes of a service producer or the first network node is a first service communication proxy (SOP) node configured to operate as an SOP between the NRF node and the plurality of first NF nodes. The first message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. The first method comprises handling the common data based on the first message.

According to a second aspect of the present disclosure, there is provided a second method for handling data in a network. The second method is performed by an NRF node. The second method comprises receiving a third message from a second network node. The second network node is a second NF node of a service consumer or the second network node is a second SCP node configured to operate as an SCP between the NRF node and the second NF node. The third message requests information of a plurality of first NF nodes of a service producer. The second method comprises transmitting a fourth message to the second network node. The fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes.

According to a third aspect of the present disclosure, there is provided a third method for handling data in a network. The third method is performed by a second network node. The second network node is a second NF node of a service consumer or the second network node is a second SCP node configured to operate as an SCP between the second NF node and an NRF node. The third method comprises transmitting a third message to the NRF node. The third message requests information of a plurality of first NF nodes of a service producer. The third method comprises receiving a fourth message from the NRF node. The fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. The third method comprises handling the common data based on the fourth message.

According to a fourth aspect of the present disclosure, there is provided a fourth method for handling data in a network. The fourth method is performed by a first network node. The first network node is a first NF node of a service producer or the first network node is a first SCP node configured to operate as an SCP between the first NF node and an NRF node. The fourth method comprises transmitting a first message to the NRF node. The first message comprises common data that is common to an NF profile of each one of a plurality of first NF nodes of the service producer. The first NF node is one of the plurality of first NF nodes of the service producer.

According to a fifth aspect of the present disclosure, there is provided a fifth method for handling data in a network. The fifth method is performed by a first network node. The first network node is a first NF node of a service producer or the first network node is a first SCP node configured to operate as an SCP between the first NF node and an NRF node. The fifth method comprises transmitting an eighth message to the NRF node. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

According to a sixth aspect of the present disclosure, there is provided a sixth method for handling data in a network. The sixth method is performed by an NRF node. The sixth method comprises receiving an eighth message from a first network node. The first network node is a first NF node of a service producer or the first network node is a first SCP node configured to operate as an SCP between the first NF node and the NRF node. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

According to a seventh aspect of the present disclosure, there is provided an NRF node comprising processing circuitry configured to operate in accordance with any one or more of the first aspect, the second aspect, and the sixth aspect.

According to an eight aspect of the present disclosure, there is provided a first network node. The first network node comprises processing circuitry configured to operate in accordance with any one or both of the fourth aspect and the fifth aspect.

According to a ninth aspect of the present disclosure, there is provided a second network node. The second network node comprises processing circuitry configured to operate in accordance with the third aspect.

According to another aspect of the disclosure, there is provided a method performed by a system. The method comprises the method described in respect of any two or more of the first to sixth aspects.

According to another aspect of the disclosure, there is provided a system comprising any two or more of the NRF node according to the seventh aspect, the first network node according to the eighth aspect, and the second network node according to the ninth aspect.

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 any one or more of the first to sixth methods.

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 any one or more of the first to sixth methods.

Brief description of the drawings

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:

Figure 1A-D is a block diagram illustrating different existing systems;

Figure 2 is a signalling diagram illustrating an exchange of signals in an existing system;

Figure 3 is a block diagram illustrating an NRF node according to an embodiment;

Figures 4-6 are block diagrams illustrating a method performed by an NRF node according to some embodiments;

Figure 7 is a block diagram illustrating a second network node according to an embodiment;

Figure 8 is a flowchart illustrating a method performed by a second network node according to an embodiment;

Figure 9 is a block diagram illustrating a first network node according to an embodiment;

Figures 10 and 11 are block diagrams illustrating methods performed by a first network node according to some embodiments;

Figure 12 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment; Figure 13 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment; and

Figure 14 is a signalling diagram illustrating an exchange of signals in a system according to an embodiment.

Detailed Description

Herein, techniques for handling NF profile data in a network are described. Said NF profile data may be used for handling service requests and responses in the network. A service request can also be referred to as a request for a service. Generally, a service is software intended to be managed for a user. 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 (LIECM)) 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 network repository function (NRF), a first network node, and a second network node. The first network node is a first network function (NF) node of a service producer or the first network node is a first service communication proxy (SOP) node configured to operate as an SOP between the first NF node and an NRF node. The second network node is a second NF node of a service consumer or the second network node is a second SOP node configured to operate as an SOP between the second NF node and an NRF node. An NRF node enables NF nodes to identify services offered by other NF nodes. Further definitions of an NRF node are provided in 3GPP TS 29.510 V16.5.0 and V17.2.0 and the NRF node described herein may be capable of operating in accordance with any of the methods described therein.

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. Herein, references to a plurality of NF nodes of a service producer may refer to, for example, functionally equivalent instances of NF nodes of the service producer.

To provide additional context to the description of the methods and network nodes according to the present disclosure, there now follows a further discussion of the drawbacks, which conventional methods and network nodes suffer from.

Figure 2 is a signalling diagram illustrating an exchange of signals in an existing system 200. The system 200 comprises an NRF node 110 (“NRF”), a first NF set 130 (“Set 1”) comprising a first NF node 132 of a first service producer (“NFp1”), a third NF node 134 of a service producer (“NFp2”), and a second NF node 120 of a service consumer (“NFc”). Although only two NF nodes 132, 134, of the NF set 130 are illustrated, it will be appreciated that the NF set 130 may comprise more than two NF nodes. The first NF node 132 and the third NF node 134 can be configured to provide (e.g. execute or run) a service 40 (“service A”).

As illustrated in Figure 2, during an initial registration process 140, each NF instance of the NF set 130 registers with the NRF node 110, in a similar manner to that described above with respect to Figures 1 B-1 D. As such, the first NF node 132 registers its NF profile with the NRF node 110 in step 141 and receives an acknowledgment in step 142. Similarly, the third NF node 134 registers its NF profile with the NRF node 110 in step 143 and receives an acknowledgement in step 144. In steps 141 and 143, the whole NF profile is provided from first NF node 132 and second NF node 134. More specifically, the whole NF profile of the first NF node 132 is provided from first NF node 132 and the whole NF profile of the third NF node 134 is provided from third NF node 134. There is no possibility for first NF node 132 and the third NF node 134 to only provide the data that may be unique for each NF instance. A message for each NF instance is used and the NRF node 110 is unaware of the common data between the NF profiles of the first NF node 132 and the third NF node 134. During a discovery process 150, the second NF node 120 requests information of the NF producers of the NF set 130 providing the service A 40, which are registered with the NRF node 110. Thus, in step 152, the second NF node 120 requests information of the NF producers associated with service A 40 by transmitting a discovery message to the NRF node 110. In step 154, the whole NFp profile is provided (to the second NF node 120) for both the first NF node 132 and the third NF node 134, with the common data between the two profiles duplicated in each profile.

As noted above, both the first NF node 132 and the third NF node 134 need to register their NF profile with the NRF node 110 individually. In such examples, a possible error could be that the second NF node 120 performs a discovery operation with NRF node 110, after first NF node 132 has registered with the NRF node 110, but before the third NF node 134 has been able to register with the NRF node 110. In such examples, from the perspective of the second NF node 120, the third NF node 134 does not exist until another future discovery operation is performed by the second NF node 120 or the second NF node 120 subscribes to be informed about new members in the NF set 130.

As illustrated in Figure 2, during a subscription to changes process 160, the second NF node 120 subscribes to any changes of the NF set 130. Thus, in step 162, the second NF node 120 subscribes to said changes with the NRF node 110 and, in step 164, the NRF node 110 transmits an acknowledgement message to the second NF node 120.

During a profile update process 170, both the first NF node 132 and the third NF node 134 may update their respective NF profiles at the NRF node 110, in response to data changing within the NF profiles of the first NF node 132 and the third NF node 134. Thus, in step 172, the first NF node 132 may transmit an updated NF profile to the NRF node 110 and receive an acknowledgment in step 174. Similarly, in step 176, the third NF node 134 may transmit an updated NF profile to the NRF node 110 and receive an acknowledgment in step 178. If any common data for the functionality offered by the NF set 130 is updated, then a new update message is sent for each NF profile of the first NF node 132 and the third NF node 134. However, if said common data is updated, then the updated data may be common to both the first NF node 132 and the third NF node 134. As illustrated in Figure 2, during a notification of profile changes process 180, the second NF node 120 is subscribed to receive profile updates. When each NF profile of the first NF node 132 and the third NF node 134 is updated, the NRF node 110 sends a notification message for each updated profile to the second NF node 120, even when the change may be to common data for both the first NF node 132 and the third NF node 134 as members in the NF set 130. Thus, in step 182, the NRF node 110 transmits information of the updated NF profile for the first NF node 132 to the second NF node 120 and receives an acknowledgement in step 184. Similarly, in step 186, the NRF node 110 transmits information of the updated NF profile for the third NF node 134 to the second NF node 120 and receives an acknowledgement in step 188. If common data between the NF profiles of both the first NF node 132 and the third NF node 134 is updated, then the second NF node 120 may thus receive this updated common data twice in steps 182 and 186.

Both the first NF node 132 and the third NF node 134 transmitting their updated profiles to the NRF node 110 can also cause additional problems. In one example, the NF profile of the first NF node 132 may be updated via O&M e.g. to serve a new Subscription Permanent Identifier (SlIPI) or new user equipment (UE) range. The NRF node 110 may thus notify the second NF node 120 immediately about the change, which may cause the first NF node 132 to be selected for all UEs within the new UE range by the second NF node 120. The third NF node 134, which is in the same NF set 130 as the first NF node 132, will not be selected until it is configured (again, via O&M) with the newly added SUPI or UE range. In such examples, the first NF node 132 and the third NF node 134 are not equivalent during a time period in which members of an NF set are being updated, since the NF configurations or NF profiles are not considered equivalent from the protocol or application programming interface (API) perspective.

As mentioned above, information included in the NF profile of an NFp can determine the functionality and capabilities of each NF instance or NF service instance. For example, the NF profile may be expressed according to the format of Table 1 , which is further defined in 3GPP TS 29.510 v17.5.0:

In one example, the NF profile of a unified data management (UDM) function, may include a Udmlnfo data type. The Udmlnfo data type may include the data outlined in Table 2, which is further defined in 3GPP TS 29.510 v17.5.0:

Table 2

As also mentioned above, the lack of an ability to identify common data in the NF profiles of a plurality of NF nodes (e.g. the NF profiles of an NF set, NF service set, or NF group) can lead to several drawbacks.

One of the drawbacks is bandwidth and signalling inefficiency. Interactions between an NRF and an NF instance can be based on a “per NF profile” granularity. The interactions may be NF instance-centric, meaning that a message may be transmitted between the NF instance and the NRF per NF instance. For example, if an NF Set comprises NFp1 and NFp2, NFp1 may register its NF profile with the NRF, comprising all NF profile data, and additionally NFp2 may also register its NF profile with the NRF, comprising all NF profile data in an independent manner. Since, for the purposes of this example, both NFp1 and NFp2 are part of the same NF Set, at least some of the data contained within their respective NF profiles will be common data, meaning that this common data is transmitted to the NRF multiple times. A similar situation may occur if the NF profiles of NFp1 and NFp2 are updated and the updated NF profiles of both NFp1 and NFp2 are sent to the NRF. The updated profiles may also contain updated common data, which is transmitted to the NRF multiple times. Additionally, the updated NF profiles of NFp1 and NFp2 may also separately be transmitted to an NFc or other NF instance, which has subscribed to notifications of changes of the NF profiles of NFp1 and NFp2. In such examples, the updated common data may therefore be transmitted multiple times to the NFc from the NRF. Thus, throughout the network, common data may be transmitted between network nodes multiple times, leading to bandwidth and signalling inefficiencies.

Another of the drawbacks is transient lack of data consistency, since not all NF instances of an NF Set or NF Group may be functionally equivalent. As described above, each NF instance in an NF Set or NF Group can be functionally equivalent and interchangeable. However, as the NF profile of each NF instance in the NF Set is registered, updated and notified independently, then there may be a time gap where all of the NF profiles of the members NF Set do not have exactly the same information. For example, NFp1 and NFp2 may belong to the same NF Set where both NFp1 and NFp2 update their respective NF profiles. NFp1 may thus register its updated NF profile at the NRF before NFp2 registers its NFp profile. Thus, during the period after NFp1 has registered its updated profile, but before NFp2 has registered its updated NF profile, the NF profiles of NFp1 and NFp2 registered at the NRF are not functionally equivalent. This issue may cause unexpected malfunctioning. If each NF instance registers its own NF profile data in an individual manner, it is also expected that the operator needs to perform an O&M configuration on each NF in a small time window to avoid transient situations. During a time window in which all the NF instances in an NF Set or NF Group do not share the same common data of their NF profiles, inaccurate load balancing may be performed by NF service consumers.

Another of the drawbacks is inefficient storage of NF profiles in the NRF. Part of the NF profile of NF instances in the same NF Set or NF Group may contain the same common data. The size of this common data may be very large, for example, hundreds of user equipment (UE) ranges, hundreds of tracking area identifiers (TAIs), etc. As such, if the NF profiles of each member of the NF Set or NF Group are stored independently, the storage may therefore be inefficient.

Examples according to the present disclosure provide a method in which common data between NF profiles of a plurality of NF nodes may be identified. Said plurality of NF nodes may thus be part of the same NF Set and/or NF Group. In this way, problems associated with the conventional operations, as described above, can be at least partly alleviated. Examples according to the present disclosure may improve signalling throughput and bandwidth, as well as help ensure data consistency among the members of an NF Set or NF Group, while storage in the NRF is improved.

Figure 3 illustrates an NRF node 10 in accordance with an aspect of the disclosure. The NRF node 10 is for handling (e.g. identifying) data in a network (e.g. common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer and/or specific data comprised in an NF profile of one or at least one first NF node of the plurality of first NF nodes of the service producer). In some embodiments, the NRF node 10 can, for example, be a physical machine (e.g. a server) or a virtual machine (VM).

As illustrated in Figure 3, the NRF node 10 comprises processing circuitry (or logic) 12. The processing circuitry 12 controls the operation of the NRF node 10 and can implement the method described herein in respect of the NRF node 10. The processing circuitry 12 can be configured or programmed to control the NRF node 10 in the manner described herein. The processing circuitry 12 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules. In particular implementations, each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the NRF node 10. In some embodiments, the processing circuitry 12 can be configured to run software to perform the method described herein in respect of the NRF node 10. The software may be containerised according to some embodiments. Thus, in some embodiments, the processing circuitry 12 may be configured to run a container to perform the method described herein in respect of the NRF node 10.

Briefly, the processing circuitry 12 of the NRF node 10 is configured to receive a message from a first network node. This message is referred to herein as the ‘first’ message. The first network node is one of a plurality of first NF nodes of a service producer or the first network node is a first SCP node configured to operate as an SCP between the NRF node and the plurality of first NF nodes. The first message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. The processing circuitry 12 of the NRF node 10 is configured to handle (e.g. identify) the common data based on the first message.

For example, the processing circuitry 12 of the NRF node 10 can be configured to receive, from one of a plurality of first NF nodes of a service producer, the first message comprising common data. The common data is comprised in the NF profile of each one of the plurality of first NF nodes. The processing circuitry 12 of the NRF node 10 is further configured to handle (e.g. identify) this common data based on the first message.

Alternatively, or in addition, the processing circuitry 12 of the NRF node 10 is configured to receive a message from a second network node. This message is referred to herein as the ‘third’ message. The second network node is a second NF node of a service consumer or the second network node is a second SCP node configured to operate as an SCP between the NRF node 10 and the second NF node. The third message requests information of a plurality of first NF nodes of a service producer. The processing circuitry 12 of the NRF node 10 is further configured to transmit a message to the second network node. This message is referred to herein as the ‘fourth’ message. The fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes.

Alternatively, or in addition, the processing circuitry 12 of the NRF node 10 is configured to receive a message from a first network node. This message is referred to herein as the ‘eighth’ message. The first network node is a first NF node of a service producer or the first network node is a first SCP node configured to operate as an SCP between the first NF node and the NRF node. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

As illustrated in Figure 3, in some embodiments, the NRF node 10 may optionally comprise a memory 14. The memory 14 of the NRF node 10 can comprise a volatile memory or a non-volatile memory. In some embodiments, the memory 14 of the NRF node 10 may comprise a non-transitory media. Examples of the memory 14 of the NRF node 10 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital video disk (DVD), and/or any other memory.

The processing circuitry 12 of the NRF node 10 can be connected to the memory 14 of the NRF node 10. In some embodiments, the memory 14 of the NRF node 10 may be for storing program code or instructions which, when executed by the processing circuitry 12 of the NRF node 10, cause the NRF node 10 to operate in the manner described herein in respect of the NRF node 10. For example, in some embodiments, the memory 14 of the NRF node 10 may be configured to store program code or instructions that can be executed by the processing circuitry 12 of the NRF node 10 to cause the NRF node 10 to operate in accordance with the method described herein in respect of the NRF node 10. Alternatively or in addition, the memory 14 of the NRF node 10 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 NRF node 10 may be configured to control the memory 14 of the NRF node 10 to store information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

In some embodiments, as illustrated in Figure 3, the NRF node 10 may optionally comprise a communications interface 16. The communications interface 16 of the NRF node 10 can be connected to the processing circuitry 12 of the NRF node 10 and/or the memory 14 of NRF node 10. The communications interface 16 of the NRF node 10 may be operable to allow the processing circuitry 12 of the NRF node 10 to communicate with the memory 14 of the NRF node 10 and/or vice versa. Similarly, the communications interface 16 of the NRF node 10 may be operable to allow the processing circuitry 12 of the NRF node 10 to communicate with one of the plurality of first NF nodes, a network node (e.g. the first network node referred to herein and/or the second network node referred to herein), and/or any other node. The communications interface 16 of the NRF node 10 can be configured to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. In some embodiments, the processing circuitry 12 of the NRF node 10 may be configured to control the communications interface 16 of the NRF node 10 to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. Although the NRF node 10 is illustrated in Figure 3 as comprising a single memory 14, it will be appreciated that the NRF node 10 may comprise at least one memory (i.e. a single memory or a plurality of memories) 14 that operate in the manner described herein. Similarly, although the NRF node 10 is illustrated in Figure 3 as comprising a single communications interface 16, it will be appreciated that the NRF node 10 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 16 that operate in the manner described herein. It will also be appreciated that Figure 3 only shows the components required to illustrate an embodiment of the NRF node 10 and, in practical implementations, the NRF node 10 may comprise additional or alternative components to those shown.

Figure 4 is a flowchart illustrating a method 400 performed by an NRF node 10 in accordance with an embodiment. The method is for handling (e.g. identifying) data in a network (e.g. common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer). In some examples, the plurality of first NF nodes may thus be part of the same NF set, NF service set or NF group. The NRF node 10 described earlier with reference to Figure 3 can be configured to operate in accordance with the method 400 of Figure 4. The method can be performed by or under the control of the processing circuitry 12 of the NRF node 10.

The method 400 comprises, in step 410, receiving a first message from a first network node. The first network node is one of a plurality of first NF nodes of a service producer or the first network node is a first SCP node configured to operate as an SCP between the NRF node 10 and the plurality of first NF nodes. The first message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. Thus, for example, in step 410, the method can comprise receiving, from one of the plurality of first NF nodes, a first message comprising the common data.

Common data can be defined herein as data which is comprised in an NF profile of each one of (i.e. all first NF nodes of) a plurality of first NF nodes of a service producer, such as each first NF node of an NF Set or an NF Group. That is, common data can be data which is common to (i.e. shared by) the NF profile of each one of (i.e. all first NF nodes of) the plurality of first NF nodes of the service producer. Herein, the terms “common data” and “shared data” can be used interchangeably. As will be described in more detail below, in some examples, the first message may register the one of the plurality of first NF nodes with the NRF node 10. In some examples, the first message may comprise the NF profile of the one of the plurality of first NF nodes. In some examples, the NF profile may comprise a common data indicator indicating the common data within the NF profile. In some examples, the first message may comprise at least a portion of an NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises the common data. In some examples, the at least a portion of the NF profile may comprise a common data indicator indicating the common data within the at least a portion of the NF profile. In some examples, the common data indicator may comprise a common data registration operation for registering the common data. In some examples, the first message may comprise a same set identifier or a same group identifier. In some examples, the first message may comprise a common data registration operation for registering the common data. In some embodiments, the first message may comprise any one or more of the above elements.

Returning back to Figure 4, the method 400 further comprises, in step 420, handling the common data based on the first message. In some examples, handling the common data may comprise identifying the common data based on the first message. In some examples, identifying the common data based on the first message may comprise identifying the common data based on the common data indicator.

The method 400 may further comprise receiving, from the first SCP node or the plurality of first NF nodes, one or more messages. These one or more messages are referred to herein as one or more ‘second’ messages. The one or more second messages each comprise the common data. The step 420 of handling the common data based on the first message may comprise handling (e.g. identifying) the common data based on the first message and the one or more second messages. In some examples, the at least a portion of the NF profile may comprise the NF profile of the one of the plurality of first NF nodes, the one or more second messages may comprise NF profiles of the plurality of first NF nodes, and the NF profiles may each comprise the common data. As will be described in more detail below, in some examples, the NRF node 10 may receive the NF profiles of a plurality of the first NF nodes. The NRF node 10 may thus be able to handle (e.g. identify) the common data comprised in a plurality of the received NF profiles. In some examples, the NRF node 10 may be able to handle (e.g. identify) the common data comprised in each of the received NF profiles. In some examples, the NRF node 10 may handle (e.g. identify) the common data comprised in the NF profiles based on a configuration of the NRF node 10.

In some examples, the method 400 may further comprise receiving, from the first SCP node or the plurality of first NF nodes, one or more second messages each comprising a partial NF profile of the plurality of first NF nodes, wherein each one of the partial NF profiles may exclude the common data. In some examples, the method 400 may further comprise updating each one of the partial NF profiles to comprise one or more data fields of the common data based on the common data indicator.

In some examples, the common data indicator may comprise one or more first parameter indicators associated with the one or more data fields of the common data. In some examples, the one or more first parameter indicators may indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data. In some examples, the mandatory data fields may comprise data fields necessary for the NF instances of the plurality of first NF nodes to be ‘interchangeable’.

In some examples, each one of the partial NF profiles may comprise one or more second parameter indicators corresponding to one or more of the one or more first parameter indicators. In some examples, updating each one of the partial NF profiles to comprise the one or more data fields of the common data based on the common data indicator may comprise associating the one or more second parameter indicators with corresponding ones of the one or more first parameter indicators.

In some examples, the NF profile of each one of the plurality of first NF nodes may comprise a plurality identifier. In some examples, the plurality identifier may comprise a same set identifier or a same group identifier. In some examples, each one of the partial NF profiles may comprise the plurality identifier and the one or more first parameter indicators may be further associated with the plurality identifier. In some examples, updating each one of the partial NF profiles to comprise one or more data fields of the common data based on the common data indicator may be further based on associating the partial NF profiles with the one or more first parameter indicators based on the plurality identifier comprised in each one of the partial NF profiles. In some examples, the NRF node 10 may thus associate common data of an NF set or NF group with the set or group identifier for the NF set or NF group. The partial NF profiles may thus be updated with the common data based on the set or group identifier comprised in the partial NF profiles.

In some examples, the common data indicator may comprise a common data registration operation for registering the common data. The step 420, of handling (e.g. identifying) the common data based on the first message, may comprise handling (e.g. identifying) the common data based on the common data registration operation. In some examples, an operation may be defined for registering the common data with the NRF node 10. In some examples, the first message may further comprise specific data of the NF profile. In some examples, the method 400 may further comprise receiving, from the first network node (e.g. one of the plurality of first NF nodes or the first SCP node), an additional message comprising specific data of the NF profile. In some examples, the specific data of the NF profile of the one of the plurality of first NF nodes may thus be comprised in the first message comprising the common data registration operation. In other examples, the first message, comprising the common data registration operation may exclude the specific data of the NF profile of the one of the plurality of first NF nodes. The specific data of the NF profile of the one of the plurality of first NF nodes may thus be transmitted to the NRF node 10 in an additional message.

Specific data can be defined herein as data that is comprised in an NF profile of a (e.g. at least one) first NF node of a plurality of first NF nodes of a service producer, such as a first NF node of an NF Set or an NF Group, but that excludes the common data referred to herein. That is, specific data can be data in an NF profile of a (e.g. at least one) first NF node of the plurality of first NF nodes of the service producer that is not comprised in the NF profile of all first NF nodes of the plurality of first NF nodes of the service producer. In one example, specific data may be data that is specific to the NF profile of only one of the plurality of first NF nodes of the service producer.

Figure 5 is a flowchart illustrating a method 1300 performed by an NRF node 10 in accordance with an embodiment. The method is for handling data in a network. The NRF node 10 described earlier with reference to Figure 3 can be configured to operate in accordance with the method 1300 of Figure 5. The method can be performed by or under the control of the processing circuitry 12 of the NRF node 10. The method 1300 comprises, in step 1310, receiving a message from a second network node. This message is referred to herein as the ‘third’ message. The second network node is a second NF node of a service consumer or the second network node is a second SCP node configured to operate as an SCP between the NRF node 10 and the second NF node. The third message requests information of a plurality of first NF nodes of a service producer. The method 1300 also comprises, in step 1320, transmitting a message to the second network node. This message is referred to herein as the ‘fourth’ message. The fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. Thus, for example, the method 1300 may comprise receiving, from a second NF node of a service consumer, a third message requesting information of the plurality of first NF nodes and transmitting, to the second NF node, a fourth message comprising the common data.

In some examples, the third message may comprise a discovery operation to discover the plurality of first NF nodes. In some examples, the method 1300 may comprise obtaining the common data. In some examples, obtaining the common data may comprise obtaining the common data from a memory, for example, memory 14 described above. In some examples, the fourth message may comprise a discovery response message.

In some examples, the fourth message may comprise at least a portion of an NF profile of one of the plurality of first NF nodes, and the at least a portion of the NF profile may comprise the common data. In some examples, the at least a portion of the NF profile may comprise specific data of the NF profile of the one of the plurality of first NF nodes. Thus, in some examples, the at least a portion of the NF profile may comprise the NF profile of one of the plurality of first NF nodes.

In some examples, the fourth message may comprise one or more partial NF profiles of a remainder of the plurality of first NF nodes. The one or more partial NF profiles may exclude the common data. In some examples, the one or more partial NF profiles may comprise specific data of the remainder of the plurality of first NF nodes. In some examples, each one of the one or more partial NF profiles may comprise a plurality identifier. In some examples, the plurality identifier may comprise the same set identifier or the same group identifier. In some examples, the at least a portion of the NF profile may comprise one or more common data field identifiers associated with one or more data fields of the common data. The one or more partial NF profiles may comprise one or more of the one or more common data field identifiers.

As will be described in more detail below, the second NF node of the service consumer may handle (e.g. identify) the common data based on the fourth message.

In some examples, the third message may comprise a common data discovery operation for discovering the common data. In some of these examples, obtaining the common data may be based on the common data discovery operation. In some examples, the fourth message may comprise a common data discovery response operation for indicating the common data to the second NF node. In some examples, an operation may thus be defined for discovering the common data at the NRF node 10 and an operation may thus be defined for indicating the common data to the second NF node.

In some examples, the method 1300 may comprise receiving a message from a first network node. This message is referred to herein as the ‘fifth’ message. The first network node is one of the plurality of first NF nodes or the first network node is a first SCP node configured to operate as an SCP between the NRF node and the plurality of first NF nodes. In some examples, the fifth message may comprise at least a portion of an NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile may comprises updated common data. In some examples, the at least a portion of an NF profile of the one of the plurality of first NF nodes may comprise the updated common data identifier. In some examples, the at least a portion of an NF profile of the one of the plurality of first NF nodes may comprise the NF profile of the one of the plurality of first NF nodes.

The fifth message may comprise updated common data. In some examples, handling (e.g. identifying) the updated common data may be based on the fifth message. In some examples, the fifth message may comprise an update message for updating the common data. In some examples, the fifth message may comprise an updated common data identifier for handling (e.g. identifying) the updated common data.

In some examples, the method 1300 may comprise receiving, from the plurality of first NF nodes, one or more messages. These one or more message are referred to herein as one or more ‘ninth’ messages. The one or more ninth messages may each comprise the common data. In some examples, handling (e.g. identifying) the updated common data based on the fifth message may further comprise handling (e.g. identifying) the updated common data based on the fifth message and the one or more ninth messages. In some examples, the one or more ninth messages may comprise at least a portion of NF profiles of the plurality of first NF nodes, wherein the at least a portion of the NF profiles can each comprise the updated common data. In some examples the at least a portion of NF profiles of the plurality of first NF nodes may comprise the NF profiles of the plurality of first NF nodes. In some examples, the NRF node 10 may handle (e.g. identify) the updated common data comprised in the NF profiles of the fifth message and the one or more ninth messages. In some examples, the NRF node 10 may handling (e.g. identify) the updated common data based on a configuration of the NRF node 10.

In some examples, the fifth message may exclude specific data of the at least a portion of the NF profile of the one of the plurality of first NF nodes. In some examples, the fifth message may comprise the updated common data and may not comprise specific data of the at least a portion of the NF profile of the one of the plurality of first NF nodes.

In some examples, the fifth message may comprise a common data update operation for updating the common data. In some embodiments, handling (e.g. identifying) the updated common data based on the fifth message may comprise handling (e.g. identifying) the updated common data based on the common data update operation. In some examples, an operation may be defined for updating the common data.

In some examples, the method 1300 may comprise transmitting, to the second network node, a message comprising the updated common data. This message is referred to herein as the ‘tenth’ message. In some examples, the tenth message may comprise an updated common data identifier for identifying the updated common data. In some examples, the tenth message may notify the second network node of changes of the common data. In some examples, the method 1300 may comprise receiving, from a second NF node of a service consumer, a message for subscribing to updates of the common data. This message is referred to herein as the ‘sixth’ message. In some embodiments, the sixth message may comprise a common data subscription operation for subscribing to updates of the common data. In some examples, an operation may thus be defined for subscribing to updates of the common data. In some examples, the tenth message may comprise the at least a portion of the NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile may comprise the updated common data. In some examples, the at least a portion of the NF profile may comprise the updated common data identifier. In some examples, the at least a portion of the NF profile of the one of the plurality of first NF nodes may comprise the NF profile of the one of the plurality of first NF nodes.

In some examples, the tenth message may exclude specific data of the at least a portion of the NF profile. In some examples, the tenth message may comprise the updated common data and may not comprise the specific data of the at least a portion of the NF profile.

In some examples, the tenth message may comprise a common data notify operation for notifying the second network node (e.g. the second NF node) of the updated common data. In some examples, an operation may be defined for notifying the second network node (e.g. the second NF node) of the updated common data.

Figure 6 is a flowchart illustrating a method 1400 performed by an NRF node 10 in accordance with an embodiment. The method is for handling data in a network. The NRF node 10 described earlier with reference to Figure 3 can be configured to operate in accordance with the method 1400 of Figure 6. The method can be performed by or under the control of the processing circuitry 12 of the NRF node 10.

The method 1400 comprises receiving, in step 1410, a message from a first network node. This message is referred to herein as the ‘eighth’ message. The first network node is a first NF node of a service producer or the first network node is a first SCP node configured to operate as an SCP between the first NF node and the NRF node. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

Figure 7 illustrates a second network node 20 in accordance with an embodiment. The second network node 20 is for handling (e.g. identifying) data in a network (e.g. common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer). The second network node 20 is a second NF node of a service consumer or a second SCP node. The second SCP node is configured to operate as an SCP between the second NF node and an NRF node 10. In some embodiments, the second network node 20 (e.g. the second NF node and/or the second SCP node) can, for example, be a physical machine (e.g. a server) or a virtual machine (VM). The second NF node can be, for example, a user equipment (UE).

As illustrated in Figure 7, the second network node 20 comprises processing circuitry (or logic) 22. The processing circuitry 22 controls the operation of the second network node 20 and can implement the method described herein in respect of the second network node 20. The processing circuitry 22 can be configured or programmed to control the second network node 20 in the manner described herein. The processing circuitry 22 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules. In particular implementations, each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the second network node 20. In some embodiments, the processing circuitry 22 can be configured to run software to perform the method described herein in respect of the second network node 20. The software may be containerised according to some embodiments. Thus, in some embodiments, the processing circuitry 22 may be configured to run a container to perform the method described herein in respect of the second network node 20.

Briefly, the processing circuitry 22 of the second network node 20 is configured to transmit a message to an NRF node 10. This message is referred to herein as the ‘third’ message. The third message requests information of a plurality of first NF nodes of a service producer. The processing circuitry 22 of the second network node 20 is configured to, receive a message from the NRF node 10. This message is referred to herein as the ‘fourth’ message. The fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes. The processing circuitry 22 of the second network node 20 is configured to handle (e.g. identify) the common data based on the fourth message.

Thus, for example, the processing circuitry 22 of the second network node 20 can be configured to transmit, to an NRF node, a third message requesting information of the plurality of second NF nodes. The processing circuitry 22 of the second network node 20 can be further configured to receive, from the NRF node, a fourth message comprising the common data. The processing circuitry 22 of the second network node 20 can be further configured to handle (e.g. identify) the common data based on the fourth message.

As illustrated in Figure 7, in some embodiments, the second network node 20 may optionally comprise a memory 24. The memory 24 of the second network node 20 can comprise a volatile memory or a non-volatile memory. In some embodiments, the memory 24 of the second network node 20 may comprise a non-transitory media. Examples of the memory 24 of the second network node 20 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital video disk (DVD), and/or any other memory.

The processing circuitry 22 of the second network node 20 can be connected to the memory 24 of the second network node 20. In some embodiments, the memory 24 of the second network node 20 may be for storing program code or instructions which, when executed by the processing circuitry 22 of the second network node 20, cause the second network node 20 to operate in the manner described herein in respect of the second network node 20. For example, in some embodiments, the memory 24 of the second network node 20 may be configured to store program code or instructions that can be executed by the processing circuitry 22 of the second network node 20 to cause the second network node 20 to operate in accordance with the method described herein in respect of the second network node 20. Alternatively or in addition, the memory 24 of the second network node 20 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 may be configured to control the memory 24 of the second network node 20 to store information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

In some embodiments, as illustrated in Figure 7, the second network node 20 may optionally comprise a communications interface 26. The communications interface 26 of the second network node 20 can be connected to the processing circuitry 22 of the second network node 20 and/or the memory 24 of second network node 20. The communications interface 26 of the second network node 20 may be operable to allow the processing circuitry 22 of the second network node 20 to communicate with the memory 24 of the second network node 20 and/or vice versa. Similarly, the communications interface 26 of the second network node 20 may be operable to allow the processing circuitry 22 of the second network node 20 to communicate with the NRF node 10 referred to herein, the first network node (e.g. the first NF node of a service producer or the first SCP node) referred to herein, the second NF node of the service consumer referred to herein (in embodiments in which the second network node is the second SCP node), the second SCP node referred to herein (in embodiments in which the second network node is the second NF node), and/or any other node. The communications interface 26 of the second network node 20 can be configured to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. In some embodiments, the processing circuitry 22 of the second network node 20 may be configured to control the communications interface 26 of the second network node 20 to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

Although the second network node 20 is illustrated in Figure 7 as comprising a single memory 24, it will be appreciated that the second network node 20 may comprise at least one memory (i.e. a single memory or a plurality of memories) 24 that operate in the manner described herein. Similarly, although the second network node 20 is illustrated in Figure 7 as comprising a single communications interface 26, it will be appreciated that the second network node 20 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 26 that operate in the manner described herein. It will also be appreciated that Figure 7 only shows the components required to illustrate an embodiment of the second network node 20 and, in practical implementations, the second network node 20 may comprise additional or alternative components to those shown.

Figure 8 is a flowchart illustrating a method 600 performed by a second network node 20 in accordance with an embodiment. As mentioned earlier, the second network node 20 is a second NF node of a service consumer or a second SCP node that is configured to operate as an SCP between the second NF node and an NRF node 10. The method 600 is for handling (e.g. identifying) data in a network (e.g. common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer). The second network node 20 described earlier with reference to Figure 7 can be configured to operate in accordance with the method of Figure 8. The method can be performed by or under the control of the processing circuitry 22 of the second network node 20.

The method 600 comprises, in step 610, transmitting a message to an NRF node 10. This message is referred to herein as the ‘third’ message. The third message requests information of a plurality of first NF nodes of a service producer. The method 600 comprises, in step 620, receiving a message from the NRF node 10. This message is referred to herein as the ‘fourth’ message. The fourth message comprises common data that is common to an NF profile of each one of the plurality of second NF nodes. The method 600 comprises, in step 630, handling (e.g. identifying) the common data based on the fourth message.

Thus, for example, the method 600 can comprise transmitting, to an NRF node, a third message requesting information of the plurality of second NF nodes. The method 600 can further comprise receiving, from the NRF node, a fourth message comprising the common data. The method 600 can further comprise handling (e.g. identifying) the common data based on the fourth message.

In some examples, the third message may comprise a discovery message for discovering information of the plurality of second NF nodes. In some examples, the fourth message may comprise a discovery response message.

In some examples, the fourth message may comprise at least a portion of an NF profile of one of the plurality of first NF nodes. The at least a portion of the NF profile may comprise the common data. In some examples, handling (e.g. identifying) the common data may comprise handling (e.g. identifying) the common data based on the fourth message. In some examples, handling (e.g. identifying) the common data based on the fourth message may comprise handling (e.g. identifying) the common data based on the at least a portion of the NF profile. In some examples, the at least a portion of the NF profile may comprise specific data of the NF profile of the one of the plurality of first NF nodes. In some examples, the at least a portion of an NF profile of one of the plurality of first NF nodes may comprise the NF profile of one of the plurality of first NF nodes. In some examples, the method 600 may further comprise storing the common data separately from the specific data of the NF profile of the one of the plurality of first NF nodes. For example, the common data and the specific data may be stored separately in memory 24, described above.

In some examples, the fourth message may further comprise one or more partial NF profiles of a remainder of the plurality of first NF nodes. The one or more partial NF profiles may exclude the common data. In some examples, handling (e.g. identifying) the common data based on the fourth message may comprise handling (e.g. identifying) the common data based on the at least a portion of the NF profile and the one or more partial NF profiles. In some examples, handling (e.g. identifying) the common data based on the at least a portion of the NF profile and the one or more partial NF profiles may comprise identifying that the at least a portion of the NF profile comprises the common data and identifying that the one or more partial NF profiles exclude the common data. In some examples, the second network node 20 (e.g. the second NF node) may identify that the at least a portion of the NF profile comprises a complete NF profile including the common data and that the one or more partial NF profiles comprise incomplete NF profile data that does not include the common data. The second network node 20 (e.g. the second NF node) may thus identify the common data by identifying that the common data is present in the complete NF profile and is absent from the one or more partial NF profiles.

In some examples, the one or more partial NF profiles may comprise specific data of the remainder of the plurality of first NF nodes. In some examples, the method 600 may comprise storing the common data separately from the specific data of the one or more partial NF profiles. For example, the second network node 20 (e.g. the second NF node) may store the common data separately from the specific data of the one or more partial NF profiles in memory 24.

In some examples, each one of the one or more partial NF profiles may comprise a plurality identifier. In some examples, the plurality identifier may comprise a same set identifier or a same group identifier. In some examples, the at least a portion of the NF profile may comprise one or more common data identifiers associated with one or more data fields of the common data. In some examples, the one or more partial NF profiles may comprise one or more of the one or more common data field identifiers. In some examples, the method 600 may comprise associating the one or more of the one or more common data field identifiers with the one or more data fields of the common data. For example, the second network node 20 (e.g. the second NF node) may update the one or more partial NF profiles to comprise one or more data fields of the common data based on the one or more common data identifiers.

In some examples, the third message may comprise a common data discovery operation for discovering the common data. In some examples, an operation may thus be defined for discovering the common data. In some examples, the fourth message may comprise a common data discovery response operation for indicating the common data to the second network node 20 (e.g. the second NF node). In some examples, an operation may thus be defined for indicating the common data to the second network node 20 (e.g. the second NF node).

In some examples, the method 600 may further comprise receiving, from the NRF node 10, a message comprising updated common data. This message is referred to herein as the ‘seventh’ message. In some examples, the method 600 may further comprise handling (e.g. identifying) the updated common data based on the seventh message. In some examples, the seventh message may comprise an updated common data identifier for identifying the updated common data. In some examples, the seventh message may comprise a message for notifying the second network node 20 (e.g. the second NF node of the service consumer) of changes of the plurality of first NF nodes of the service producer. In some examples, the method 600 may thus comprise transmitting, to the NRF node, a message for subscribing to updates of the common data. This message is referred to herein as the ‘sixth' message. In some examples, the sixth message may comprise a common data subscription operation for subscribing to updates of the common data. In some examples, an operation may thus be defined for subscribing to updates of the common data.

In some examples, the sixth message may comprise at least a portion of an NF profile of one of the plurality of first NF nodes. The at least a portion of the NF profile may comprise updated common data. In some examples, the at least a portion of the NF profile may comprise the NF profile of the one of the plurality of second NF nodes.

In some examples, handling (e.g. identifying) the updated common data may comprise associating the at least a portion of the NF profile with the identified common data of the plurality of first NF nodes. In some examples, the at least a portion of the NF profile may comprise a plurality identifier and associating the at least a portion of the NF profile with the identified common data of the plurality of first NF nodes may be based on the plurality identifier. In some examples, the plurality identifier may comprise a same set identifier or a same group identifier.

In some examples, the seventh message may exclude specific data of the NF profile of the one of the plurality of first NF nodes. In some examples, the seventh message may comprise updated common data and may not comprise specific data of the NF profile of the one of the plurality of first NF nodes.

In some examples, the seventh message may comprise a common data notify operation for notifying the second network node (e.g. the second NF node) of the updated common data. In some examples, an operation may thus be defined for notifying the second network node (e.g. the second NF node) of the updated common data.

In some examples, the method 600 may further comprise updating the common data based on the updated common data. For example, the common data stored in memory 24 may be updated.

Figure 9 illustrates a first network node 30 in accordance with an embodiment. The first network node 30 is for handling data in a network. For example, the first network node 30 may be for providing common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer. Alternatively or in addition, the first network node 30 may be for providing specific data comprised in an NF profile of a first NF node of a service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer. The first network node 30 is the first NF node of a service producer or a first SCP node. The first SCP node is configured to operate as an SCP between the first NF node and an NRF node 10. In some embodiments, the first network node 30 (e.g. the first NF node and/or the first SCP node) can, for example, be a physical machine (e.g. a server) or a virtual machine (VM). The first NF node can be, for example, a user equipment (UE).

As illustrated in Figure 9, the first network node 30 comprises processing circuitry (or logic) 32. The processing circuitry 32 controls the operation of the first network node 30 and can implement the method described herein in respect of the first network node 30. The processing circuitry 32 can be configured or programmed to control the first network node 30 in the manner described herein. The processing circuitry 32 can comprise one or more hardware components, such as one or more processors, one or more processing units, one or more multi-core processors and/or one or more modules. In particular implementations, each of the one or more hardware components can be configured to perform, or is for performing, individual or multiple steps of the method described herein in respect of the first network node 30. In some embodiments, the processing circuitry 32 can be configured to run software to perform the method described herein in respect of the first network node 30. The software may be containerised according to some embodiments. Thus, in some embodiments, the processing circuitry 32 may be configured to run a container to perform the method described herein in respect of the first network node 30.

The processing circuitry 32 of the first network node 30 is configured to transmit a message to an NRF node 10. This message is referred to herein as the ‘first’ message. The first message comprises common data that is common to an NF profile of each one of a plurality of first NF nodes of the service producer. The first NF node is one of the plurality of first NF nodes of the service producer.

Alternatively or in addition, the processing circuitry 32 of the first network node 30 is configured to transmit a message to an NRF node 10. This message is referred to herein as the ‘eight’ message. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

Thus, for example, the processing circuitry 32 of the first network node 30 can be configured to, transmit, to an NRF node, a first message comprising the common data and/or the processing circuitry 32 of the first network node 30 can be configured to transmit, to an NRF node, an eighth message comprising specific data comprised in an NF profile of the first network node 30.

As illustrated in Figure 9, in some embodiments, the first network node 30 may optionally comprise a memory 34. The memory 34 of the first network node 30 can comprise a volatile memory or a non-volatile memory. In some embodiments, the memory 34 of the first network node 30 may comprise a non-transitory media. Examples of the memory 34 of the first network node 30 include, but are not limited to, a random access memory (RAM), a read only memory (ROM), a mass storage media such as a hard disk, a removable storage media such as a compact disk (CD) or a digital video disk (DVD), and/or any other memory.

The processing circuitry 32 of the first network node 30 can be connected to the memory 34 of the first network node 30. In some embodiments, the memory 34 of the first network node 30 may be for storing program code or instructions which, when executed by the processing circuitry 32 of the first network node 30, cause the first network node 30 to operate in the manner described herein in respect of the first network node 30. For example, in some embodiments, the memory 34 of the first network node 30 may be configured to store program code or instructions that can be executed by the processing circuitry 32 of the first network node 30 to cause the first network node 30 to operate in accordance with the method described herein in respect of the first network node 30. Alternatively or in addition, the memory 34 of the first network node 30 can be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. The processing circuitry 32 of the first network node 30 may be configured to control the memory 34 of the first network node 30 to store information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

In some embodiments, as illustrated in Figure 9, the first network node 30 may optionally comprise a communications interface 36. The communications interface 36 of the first network node 30 can be connected to the processing circuitry 32 of the first network node 30 and/or the memory 34 of the first network node 30. The communications interface 36 of the first network node 30 may be operable to allow the processing circuitry 32 of the first network node 30 to communicate with the memory 34 of the first network node 30 and/or vice versa. Similarly, the communications interface 36 of the first network node 30 may be operable to allow the processing circuitry 32 of the first network node 30 to communicate with the NRF node 10 referred to herein, the second network node 20 referred to herein, the first NF node referred to herein (in embodiments in which the first network node 30 is the first SCP node), the first SCP node referred to herein (in embodiments in which the first network node 30 is the first NF node), and/or any other node. The communications interface 36 of the first network node 30 can be configured to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein. In some embodiments, the processing circuitry 32 of the first network node 30 may be configured to control the communications interface 36 of the first network node 30 to transmit and/or receive information, data, messages, requests, responses, indications, notifications, signals, or similar, that are described herein.

Although the first network node 30 is illustrated in Figure 9 as comprising a single memory 34, it will be appreciated that the first network node 30 may comprise at least one memory (i.e. a single memory or a plurality of memories) 34 that operate in the manner described herein. Similarly, although the first network node 30 is illustrated in Figure 9 as comprising a single communications interface 36, it will be appreciated that the first network node 30 may comprise at least one communications interface (i.e. a single communications interface or a plurality of communications interfaces) 36 that operate in the manner described herein. It will also be appreciated that Figure 9 only shows the components required to illustrate an embodiment of the first network node 30 and, in practical implementations, the first network node 30 may comprise additional or alternative components to those shown.

Figure 10 is a flowchart illustrating a method 800 performed by a first network node 30 in accordance with an embodiment. As mentioned earlier, the first network node 30 is the first NF node of a service producer or a first SCP node that is configured to operate as an SCP between the first NF node and an NRF node 10. The method is for handling data (e.g. common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer). The first network node 30 described earlier with reference to Figure 9 may be configured to operate in accordance with the method of Figure 10. The method can be performed by or under the control of the processing circuitry 32 of the first network node 30.

The method 800 comprises, in step 810, transmitting a message to an NRF node 10. This message is referred to herein as the ‘first’ message. The first message comprises common data that is common to an NF profile of each one of a plurality of first NF nodes of the service producer. The first NF node is one of the plurality of first NF nodes of the service producer. In some examples, the first message may comprise a register message for registering with the NRF node.

In some examples, the first message may comprise at least a portion of an NF profile of the first NF node. In some examples, the at least a portion of the NF profile may comprise the common data. In some examples, the at least a portion of an NF profile of the first NF node may comprise the NF profile of the first NF node. In some examples, the first message may comprise a same set identifier or a same group identifier for each of the plurality of first NF nodes. In some examples, the first message may comprise a common data registration operation for registering the common data with the NRF node. The first message may comprise any one or more of the above elements.

In some examples, the at least a portion of the NF profile may comprise a common data indicator indicating the common data within the at least a portion of the NF profile. In some examples, the common data indicator may comprise one or more first parameter indicators associated with one or more data fields of the common data. In some examples, the one or more first parameter indicators may indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data. In some examples, the mandatory data fields may comprise data fields necessary for the NF instances of the plurality of first NF nodes to be ‘interchangeable’.

In some examples, the at least a portion of the NF profile may comprise a plurality identifier. In some examples, the plurality identifier may comprise the same set identifier or a same group identifier for each of the plurality of first NF nodes.

In some examples, the first message may comprise a common data registration operation for registering the common data with the NRF node 10. In some examples, an operation may thus be defined for registering the common data with the NRF node 10. In some examples, the method 800 may further comprise transmitting, to the NRF node 10, a message comprising updated common data. This message is referred to herein as the ‘second’ message. In some examples, the second message may comprise at least a portion of an updated NF profile of the first NF node. In some examples, the at least a portion of the updated NF profile may comprise the updated common data. In some examples, the at least a portion of an updated NF profile of the first NF node may comprise the updated NF profile of the first NF node. In some examples, the second message may comprise an updated common data identifier for identifying the updated common data. In some examples, the at least a portion of an updated NF profile of the first NF node may comprise the updated common data identifier.

In some examples, the at least a portion of the updated NF profile may exclude specific data of the updated NF profile of the first NF node. In some examples, the second message may comprise the updated common data and may not comprise specific data of the updated NF profile of the first NF node.

In some examples, the second message may comprise a common data update operation for registering the updated common data with the NRF node 10. In some examples, an operation may be defined for registering the updated common data with the NRF node 10.

Figure 11 is a flowchart illustrating a method 900 performed by a first network node 30 in accordance with an embodiment. As mentioned earlier, the first network node 30 can be a first NF node of a service consumer or a first SCP node that is configured to operate as an SCP between the first NF node and an NRF node 10. The method is for handling data in a network (e.g. specific data comprised in an NF profile of the first NF node of the service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer). The first network node 30 described earlier with reference to Figure 9 may be configured to operate in accordance with the method of Figure 11. The method can be performed by or under the control of the processing circuitry 32 of the first network node 30.

The method 900 comprises, in step 910, transmitting a message, to an NRF node 10.

This message is referred to herein as the ‘eighth’ message. The eighth message comprises specific data of an NF profile of the first NF node. The first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes. The eighth message may comprise a message (e.g. request) for registering the first NF node with the NRF.

In some examples, the eighth message may comprise a partial NF profile of the first NF node. In some examples, the partial NF profile may exclude common data comprised in an NF profile of each one of the plurality of first NF nodes.

In some examples, the partial NF profile may comprise one or more first parameter indicators associated with the one or more data fields of the common data. In some examples, the one or more first parameter indicators may indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data. In some examples, the one or more first parameter indicators may be used by the NRF node 10 for updating the partial NF profile with the common data.

In some examples, the partial NF profile may comprise a plurality identifier. In some examples, the plurality identifier may comprise a same set identifier or a same group identifier for each of the plurality of first NF nodes.

There is provided a method performed by a second SCP node for identifying common data comprised in an NF profile of each one of a plurality of first NF nodes of a service producer. The method comprises transmitting, to an NRF node 10, a third message requesting information of the plurality of first NF nodes. The method comprises receiving, from the NRF node 10, a fourth message comprising the common data, and identifying the common data based on the fourth message.

There is also provided a method performed by a first SCP node for providing specific data comprised in an NF profile of a first NF node of a service producer, wherein the first NF node is one of a plurality of first NF nodes of the service producer. The method comprises transmitting, to an NRF node 10, an eighth message comprising the specific data. There is also provided an SCP node comprising processing circuitry configured to operate in accordance with the methods described above with reference to the first SCP node and/or the second SCP node.

There is also provided a method performed by a system. The method comprises any one or more of the methods described herein in respect of the NRF node 10, any one or more of the methods described herein in respect of the second network node 20 (e.g. the second NF node), and any one or more of the methods described herein in respect of the first network node 30 (e.g. the first NF node). There is also provided a system comprising at least one NRF node 10 as described herein, at least one second network node 20 (e.g. at least one second NF node and/or at least one second SCP node) as described herein, and at least one first network node 30 (e.g. at least one first NF node and/or at least one first SCP node) as described herein.

The discussion above provides an overview of the examples of the present disclosure. There now follows a more detailed discussion of how the examples of the present disclosure discussed above may be implemented.

As described above, examples according to the present disclosure are able to handle (e.g. identify) common data comprised in the NF profiles of members of a plurality of NF nodes (e.g. members of an NF set, NF service set, or NF group). The NF profile of each member of a plurality of NF nodes (e.g. each member of an NF set, NF service set, or NF group) comprises said common data in order for the members to be ‘interchangeable’.

In examples according to the present disclosure, the data fields of an NF profile for members of a plurality of NF nodes (e.g. members of an NF set, NF service set, or NF group) may be divided into three categories: specific data of an NF profile; mandatory common data of an NF profile; and optional common data of an NF profile. Specific data of an NF profile may be unique for the NF profile of each NF instance. Mandatory common data may be data that is mandatory to be common to the NF profiles of all NF instances in a plurality of NF nodes (e.g. in an NF set, NF service set, or NF group). The mandatory common data may thus be the data enabling each NF instance to be ‘interchangeable’. The optional common data can be optionally common to the NF profiles of all NF instances in a plurality of NF nodes (e.g. in an NF set, NF service set, or NF group).

Table 3 below illustrates the NF profile of a unified data management (UDM) instance, where the three data types described above are indicated. In Table 3, italicised data fields represent specific data, bold data fields represent mandatory common data, single underlined data fields represent optionally common data fields, and double underlined data fields represent data that is not relevant for a UDM profile.

Table 3

As will be described in more detail below, in some examples, the common data, whether mandatory or optional, may be identified in the NF profile. In one example, common data for the data that is mandatory data is indicated for a plurality of NF nodes (e.g. an NF set, NF service set or NF group). In such examples, the data that is optionally common may also be indicated. In some examples, parameter indicators may be applied to each data field indicating the mandatory common data and the optional common data. For the optional common data, said parameter indicators may indicate the optional common data fields which are applicable for a given NF profile. In some examples, the identified common data could be defined per NF type. For example, a common data indicator may indicate the common data for particular NF types.

Figure 12 is a signalling diagram illustrating an exchange of signals in a system 1000 according to an embodiment. The system 1000 comprises an NRF node 10 (“NRF”), a first NF set 130 comprising a first NF node 132 of a first service producer (“NFp1”) and a third NF node 134 of a service producer (“NFp2”). The system 1000 also comprises a second network node 20. In the embodiment illustrated in Figure 12, the second network node 20 is a second NF node of a service consumer (“NFc”). However, it will be understood that, in some embodiments, the second network node 20 may be a second SCP node as described herein. Similarly, in the embodiment illustrated in Figure 12, the system 1000 comprises two first network nodes 30, which are the first and third NF nodes 132, 134. However, it will be understood that, in some embodiments, the first network node 30 may be a first SCP node as described herein.

Although only two NF nodes 132, 134 of NF set 130 are illustrated, it will be appreciated that NF set 130 may comprise more than two NF nodes. The first NF node 132 and the third NF node 134 can be configured to provide (e.g. execute or run) service 40 (“service A”). The NRF node 10 can be as described earlier with reference to any one or more of Figures 3, 4, 5 and 6. The first NF node 132 and the third NF node 134 can be as described earlier with reference to any one or more of Figures 9, 10 and 11. The second network node 20 can be as described earlier with reference to any one or more of Figures 7 and 8.

As illustrated in Figure 12, in some embodiments, during an initial registration 240, each NF instance of NF set 130 may register with the NRF node 10, in a similar manner to that described above with respect to Figure 2. As such, the first NF node 132 may register its NF profile with the NRF node 10 in step 141 and receive an acknowledgment in step 142. Similarly, in step 143, the third NF node 134 may register its NF profile with the NRF node 10 and receive an acknowledgement 144. In steps 141 and 143, the whole NF profile may be provided from the first NF node 132 and the third NF node 134.

In step 145, the NRF node 10 may handle (e.g. identify) the common data of the NF profiles received from the first NF node 132 and the third NF node 134. For example, the NRF node 10 may be configured to identify or recognize the common data comprised in each NF profile. In some examples, the NRF node 10 may be configured with the common data of a plurality of NF nodes of a service producer. For example, configuring the NRF node 10 with the common data may comprise the NRF node 10 obtaining the common data for the plurality of NF nodes of the service producer. In some examples, the NRF node 10 may thus associate the obtained common data with a plurality identifier of the plurality of NF nodes of the service producer e.g. the set identifier of the NF set 130. The NRF node 10 may thus identify the common data comprised in the NF profile of the first NF node 132 based on the obtained common data. For example, the NRF node 10 may associate the set identifier of the first NF node 132 with the obtained common data. Similarly, the NRF node 10 may thus identify the common data comprised in the NF profile of the third NF node 134 based on the obtained common data. For example, the NRF node 10 may associate the set identifier of the third NF node 134 with the obtained common data.

The NRF node 10 may store the common data as a data structure for all the members of the NF set 130. In this way, the storage needs for the NF set 130 are minimized, compared to storing the NF profile of each member of the set, where each NF profile comprises the common data. The NRF node 10 may additionally store the specific data of the NF profiles separately from the common data. As will be described in more detail below, storing the common data structure separately from the specific data may additionally enable the common data to be updated for all members of the NF set 130 at the same time, therefore improving the consistency of common data changes.

As illustrated in Figure 12, in some embodiments, during a discovery 250, the second network node 20 may request information of the NF producers of the NF set 130 providing service A 40, which are registered with the NRF node 10. Thus, in step 152, the second network node 20 may request information of the NF producers associated with service A 40 by transmitting a discovery message to the NRF node 10. In some embodiments, the NRF node 10 may thus receive the discovery message from the second network node 20.

In some embodiments, in response to the discovery message, in step 251 , the NRF node 10 may handle (e.g. identify) the common data associated with the NF profiles of the members of the NF set 130. For example, the NRF node 10 may retrieve the common data for the NF set 130 from a memory (e.g. the memory 14 of the NRF node 10). The NRF node 10 may further retrieve the specific data of the NF profiles of the members of the NF set 130. In step 253, the NRF node 10 may transmit a discovery response message to the second network node 20 comprising the complete profile of the first NF node 132 and a partial NF profile of the third NF node 134. Thus, in some embodiments, the second network node 20 may receive the discovery response from the NRF node 10.

The partial NF profile of the third NF node 134 may comprise specific data of the NF profile of the third NF node 134 and may not comprise the common data. In some examples, the NRF node 10 may thus transmit one complete NF profile to the second network node 20 and a partial NF profile for each of the remainder of the members of the NF set 130, where the partial NF profiles do not comprise the common data. In this way, the bandwidth of the signalling is improved, as less bandwidth is used to transmit one complete NF profile and one or more partial NF profiles, compared to transmitting a plurality of complete NF profiles, each comprising the common data.

In some embodiments, in response to receiving the discovery response message, in step 254, the second network node 20 may identify that the discovery response message comprises the complete NF profile of the first NF node 132 and the partial profile of the third NF node 134. The second network node 20 may thus identify the common data comprised in the complete NF profile of the first NF node 132 by, for example, comparing the complete NF profile of the first NF node 132 and the partial profile of the third NF node 134. In some examples, the complete NF profile may comprise one or more common data field identifiers associated with one or more data fields of the common data. The partial NF profile may comprise one or more of the one or more common data field identifiers. The second network node 20 may thus identify the common data to be comprised in the partial NF profiles based on the one or more common data field identifiers.

The second network node 20 may thus identify that the common data is common for the NF profiles of each member of the NF set 130 for providing the service A 40. The second network node 20 may thus associate the common data with the members of the NF set 130 based on a set identifier comprised in the complete NF profiles and the one or more partial NF profiles.

Similarly to the NRF node 10, the second network node 20 may store the common data separately from the specific data for each NF profile of the NF set 130. In this way, storage needs at the second network node 20 are reduced compared to storing a complete NF profile for each member of the NF set 130. Furthermore, as will be described in more detail below, storing the common data structure separately from the specific data may additionally enable the common data to be updated for all members of the NF set 130 at the same time, therefore improving the consistency of common data changes.

As illustrated in Figure 12, in some embodiments, during a subscription to changes 160, the second network node 20 may subscribe to any changes of NF set 130. Thus, in step 162, the second network node 20 may transmit a subscription to changes request message to the NRF node 10 for subscribing to said changes. In some embodiments, the NRF node 10 may thus receive the subscription to changes request message from the second network node 20. In step 164, the NRF node 10 may transmit an acknowledgement message to the second network node 20. Thus, in some embodiments, the second network node 20 may receive the acknowledgement message from the NRF node 10. As illustrated in Figure 12, in some embodiments, during a profile update 270 both the first NF node 132 and the third NF node 134 may update their respective NF profiles at the NRF node 10, for example, in response to data changing within the NF profiles of the first NF node 132 and the third NF node 134. Thus, in step 172, the first NF node 132 may transmit an updated NF profile to the NRF node 10. In some embodiments, the NRF node 10 may thus receive the updated NF profile from the first NF node 132. In some embodiments, the first NF node 132 may receive an acknowledgment in step 174. Similarly, in step 176, the third NF node 134 may transmit an updated NF profile to the NRF node 10. Thus, in some embodiments, the NRF node 10 may receive the updated NF profile from the third NF node 134. In some embodiments, the third NF node 134 may receive an acknowledgment in step 178.

In step 272, the NRF node 10 may identify that the updated NF profile of the first NF node 132 and the updated NF profile of the third NF node 134 both comprise updated common data. For example, the NRF node 10 may identify the common data by comparing the updated NF profiles. The NRF node 10 may thus update the stored common data in response to identifying the updated common data. The stored common data for all members of the NF set 130 may thus be updated in a single action, thereby improving the consistency of common data changes.

As illustrated in Figure 12, in some embodiments, during a notification of profile changes 280, the NRF node 10 may transmit the updated common data to the second network node 20 (e.g. as the second network node 20 subscribed to changes of the NF set 130 during the subscription to changes 160). In step 281 , the NRF node 10 may identify that common data for the NF set 130 has been updated. In step 282, the NRF node 10 may transmit a notification message to the second network node 20 comprising the complete NF profile of the first NF node 132, where the complete NF profile of the first NF node 132 comprises the updated common data. Thus, in some embodiments, the second network node 20 may receive the notification message from the NRF node 10. The second network node 20 may transmit an acknowledgement to the NRF node 10 in step 284. Thus, in some embodiments, the NRF node 10 may receive the acknowledgement from the second network node 20. T ransmitting a single notification message comprising an NF profile comprising the updated common data reduces signalling and bandwidth compared to transmitting a plurality of notification messages comprising the updated NF profile for each member of the NF set 130. In step 286, the second network node 20 may identify that the notification message comprises a complete NF profile associated with the NF set 130. For example, said association may be made based on a set identifier comprised in the complete NF profile. The second network node 20 may further identify that the complete NF profile comprises updated common data for the NF set 130. The second network node 20 may thus update the common data stored by the second network node 20. In this way, the common data may be updated in a single action to improve the consistency of common data changes.

Figure 13 is a signalling diagram illustrating an exchange of signals in a system 1100 according to an embodiment. The system 1100 comprises common elements and steps described above with respect to Figure 12, where said common elements and steps are labelled with corresponding reference numerals, and the corresponding description will be understood to apply.

In the embodiment according to Figure 13, the common data for the NF set 130 may be standardized. For example, data fields of the NF profiles of the NF set 130 may be associated with a common data indicator indicating the common data within each profile. It is therefore standardized that the common data may be applicable for each NF profile as indicated by the common data indicator.

In some examples, the common data indicator may comprise one or more parameter indicators associated with one or more data fields of the common data. As described above, the common data may be formed of mandatory common data and optional common data. The parameter indicators may thus indicate common data that is or is not applicable for a given NF profile. For example, the parameter indicators may indicate that the mandatory common data is applicable for each NF profile of the NF set 130. However, the parameter indicators may indicate the data fields of the optional common data which are applicable for a given NF profile, but may also indicate the data fields of the optional common data which are not applicable for a given NF profile.

Referring to Figure 13, during an initial registration 340, each NF instance of the NF set 130 may register with the NRF node 10. In step 341 , the first NF node 132 may register its NF profile with the NRF node 10 and receive an acknowledgment in step 342. The first NF node 132 may transmit a registration message to the NRF node 10 including its complete NF profile. Thus, in some embodiments, the NRF node 10 may receive the registration message from the first NF node 132. The complete NF profile may comprise a common data indicator indicating the common data within the NF profile. In some examples, the common data indicator may further comprise one or more parameter indicators, as described above. The complete NF profile may also comprise specific data of the complete NF profile of the first NF node 132.

In step 343, the third NF node 134 may register with the NRF node 10 and receive an acknowledgement in step 344. In step 343, the third NF node 134 may transmit a register message to the NRF node 10 comprising a partial NF profile of the third NF node 134. Thus, in some embodiments, the NRF node 10 may receive the register message from the third NF node 134. The partial NF profile may exclude the common data. The partial NF profile may thus comprise specific data of the NF profile of the third NF node 134.

In step 345, the NRF node 10 may identify that a complete NF profile comprising the common data and a common data indicator is provided in the registration message from the first NF node 132 in step 341 and that a partial NF profile is provided from the third NF node 134 in step 343. The NRF node 10 may thus identify the common data for the NF set 130, which is comprised in the complete NF profile based on the common data indicator. The NRF node 10 may thus associate the common data with each member of the NF set 130, even though the remainder of the NF set may transmit a partial NF profile to the NRF node 10. For example, the NRF node 10 may associate the common data to the NF profile of the third NF node 134, which provided a partial NF profile to the NRF node 10.

As described above, in some examples, the common data indicator may comprise one or more parameter indicators associated with one or more data fields of the common data, which in some examples may be referred to as ‘first parameter indicators’. In some examples, the partial NF profiles of an NF set 130 may comprise one or more corresponding parameter indicators, which in some examples may be referred to as ‘second parameter indicators’. The parameter indicators of the partial NF profiles may thus indicate the data fields of the common data, which are applicable for a given partial NF profile. For example, as described above, in step 343, the third NF node 134 may register a partial NF profile with the NRF node 10, comprising one or more parameter indicators. In step 345, the NRF node 10 may associate the one or more parameter indicators of the partial NF profile with the parameter indicators of the common data, which therefore indicate the common data fields which are applicable for the NF profile of the third NF node 134.

In some examples, the one or more parameter indicators of the common data indicator may be associated with a set identifier of the NF set 130. In such examples, when the NRF node 10 receives a partial NF profile from the NF set 130 comprising the set identifier, the NRF node 10 may associate the partial NF profile with the NF set 130 based on the set identifier. The NRF node 10 may thus update the partial NF profile to comprise data fields of the common data based on associating the partial NF profile with the set identifier of an NF set 130.

In step 345, the NRF node 10 may update the internal information of the partial NF profile of the third NF node 134 based on the common data indicator. In some examples, the NRF node 10 may update the internal information of the partial NF profile of the third NF node 134 based on the one or more parameter indicators, as described above. In some examples, the NRF node 10 may update the internal information of the partial NF profile of the third NF node 134 based on the set identifier, as described above.

In a similar manner to that described above, the NRF node 10 may store the common data in a separate data structure to the specific data for the NF profiles of the members of the NF set 130. The specific data for each of the NF profiles of the NF set 130 may thus be stored separately to the common data, for example as partial NF profiles. However, the partial NF profiles may additionally comprise the common data indicator and/or the one or more parameter indicators indicating the common data applicable for a given partial NF profile.

As illustrated in Figure 13, in some embodiments, during a discovery 350, the second network node 20 may request information of the NF producers of the NF set 130 providing service A 40, which are registered with the NRF node 10. Thus, in step 152, the second network node 20 may request information of the NF producers associated with service A 40 by transmitting a discovery message to the NRF node 10. Therefore, in some embodiments, the NRF node 10 may receive the discovery message from the second network node 20.

In a similar manner to that described above for Figure 12, in response to the discovery message, in step 351 , the NRF node 10 may handle (e.g. identify) the common data associated with the NF profiles of the members of the NF set 130. For example, the NRF node 10 may retrieve the common data for the NF set 130 from a memory (e.g. memory 14 of the NRF node 10). The NRF node 10 may retrieve the specific data of the NF profiles of the members of the NF set 130. In step 353, the NRF node 10 may transmit a discovery response message to the second network node 20 comprising the complete profile of the first NF node 132 and a partial NF profile of the third NF node 134. The partial NF profile of the third NF node 134 comprises specific data of the NF profile of the third NF node 134 and does not comprise the common data. In some examples, the NRF node 10 may transmit, to the second network node 20, one complete NF profile and a partial NF profile for each of the remainder of the members of the NF set 130, where the partial NF profiles do not comprise the common data. Thus, in some embodiments, the second network node 20 may receive these NF profiles from the NRF node 10.

In response to receiving the discovery response message, in step 354, the second network node 20 may identify that the discovery response message comprises the complete NF profile of the first NF node 132 and the partial profile of the third NF node 134. The second network node 20 may identify the common data comprised in the complete NF profile of the first NF node 132 by, for example, comparing the complete NF profile of the first NF node 132 and the partial profile of the third NF node 134.

In some examples, the complete NF profile transmitted in step 353 may comprise the common data indicator. The second network node 20 may thus identify the common data for the NF set 130 based on the common data indicator. In some examples, the common data indicator may comprise parameter indicators, and the partial NF profile(s) of the remainder of the NF set 130 may comprise corresponding parameter indicators. The second network node 20 may identify the data fields of the common data that are applicable for the partial NF profile(s) based on the parameter indicators. As described above with respect to Figure 12, the second network node 20 may store the common data separately from the specific data for each NF profile of the NF set 130.

As described above with respect to Figure 12, the second network node 20 may subscribe to any changes of the NF set 130, during a subscription to changes procedure 160. The subscription to changes procedure 160 substantially corresponds to that described above for Figure 12 and is thus not repeated here for brevity.

As illustrated in Figure 13, during a profile update 370, in some examples, the common data of the NF set 130 may be updated for all members of the NF set 130. Thus, in step 372, the first NF node 132 may transmit an update message to the NRF node 10 comprising the updated common data. Therefore, in some embodiments, the NRF node 10 may receive the update message from the first NF node 132. In some embodiments, the first NF node 132 may receive an acknowledgement in step 374. The update message may comprise a common data indicator, indicating the updated common data. In some examples, the update message may comprise the updated common data and may exclude specific NF profile data of the first NF node 132. In some examples, the update message may comprise the complete NF profile of the first NF node 132 comprising the updated common data.

The NRF node 10 may thus receive the updated common data and, in step 376, handle (e.g. identify) the updated common data for the NF set 130. The NRF node 10 may update the stored common data for the NF set 130 using the updated common data.

As the common data is updated for each member of the NF set 130 in the example according to Figure 13, only one update message may be sent from the NF set 130 to the NRF node 10 to update the common data. In other words, each member of the NF set 130 may not transmit an update message to the NRF node 10 in the example according to Figure 13, in examples where the common data is updated for each member of the NF set 130. In this way, signalling is reduced and bandwidth is improved.

The NRF node 10 may update the common data in a single action based on the update common data received in step 372. In this way, the common data associated with each member of the NF set 130 is consistently updated. As illustrated in Figure 13, in some embodiments, during a notification of profile changes 380, the NRF node 10 may transmit the updated common data to the second network node 20 (e.g. as the second network node 20 can be subscribed to changes of the NF set 130 during the subscription to changes 160). In step 381 , the NRF node 10 may identify that common data for the NF set 130 has been updated. In step 382, the NRF node 10 may transmit a notification message to the second network node 20 comprising the updated common data. Thus, in some embodiments, the second network node 20 may receive the notification message from the NRF node 10. The notification message may comprise the complete NF profile of the first NF node 132 comprising the updated common data. In some examples, the complete NF profile of the first NF node 132 may comprise a common data indicator, indicating the updated common data. In step 384, the second network node 20 may transmit an acknowledgement message to the NRF node 10. Thus, in some embodiments, the NRF node 10 may receive the acknowledgement message from the second network node 20.

In step 386, the second network node 20 may identify that the notification message comprises updated common data associated with the NF set 130. For example, said association may be made based on a set identifier comprised in a complete NF profile of the first NF node 132. In some examples, the notification message may comprise the complete NF profile of the first NF node 132. In some examples, the notification message may comprise a common data indicator, indicating the updated common data. The second network node 20 may update the stored common data for the NF set 130 based on the updated common data.

Figure 14 is a signalling diagram illustrating an exchange of signals in a system 1200 according to an embodiment. The system 1200 comprises common elements and steps described above with respect to Figure 12 and Figure 13, where said common elements and steps are labelled with corresponding reference numerals, and the corresponding description will be understood to apply.

In a similar manner to that described above for Figure 13, in the embodiment according to Figure 14 the common data for the NF set 130 may be standardized, for example, with a common data indicator and parameter indicators, as described above. In the example according to Figure 14 operations may be defined for handling the common data for an NF set. As will be described in more detail below, specific operations may be defined for transmitting the common data between the entities of system 1200. For example, said specific operations may be defined in a future 3GPP TS.

Referring to Figure 14, during an initial registration 440, each NF instance of the NF set 130 may register with the NRF node 10. In step 441 , the first NF node 132 may register with the NRF node 10 by transmitting a registration message to the NRF node 10. Thus, in some embodiments, the NRF node 10 may receive the registration message from the first NF node 132. In some embodiments, the first NF node 132 may receive an acknowledgment in step 442. The registration message may comprise a common data registration operation for registering the common data of the NF set 130 with the NRF node 10. In some examples, the common data registration operation may effectively perform a similar function to the common data indicator described above with respect to Figure 14, where the common data registration operation may indicate the common data for the NF set 130 to the NRF node 10. In some examples, the registration message may further comprise the specific data of the NF profile of the first NF node 132. In other examples, the first NF node 132 may transmit an additional message to the NRF node 10 comprising the specific data of the NF profile of first NF node 132. Thus, in some embodiments, the NRF node 10 may receive the additional message from the first NF node 132.

In step 443, the third NF node 134 may register with the NRF node 10. For example, in step 443, the third NF node 134 may transmit a register message to the NRF node 10 comprising a partial NF profile of the third NF node 134. Thus, in some embodiments, the NRF node 10 may receive the register message from the third NF node 134. The partial NF profile may exclude the common data. The partial NF profile may comprise specific data of the NF profile of the third NF node 134. The register message transmitted from the third NF node 134 may not comprise the common data registration operation. In some embodiments, in step 444, the NRF node 10 may transmit an acknowledgment message to the third NF node 134. Thus, in some embodiments, the third NF node 134 may receive the acknowledgement message from the NRF node 10.

In step 345, the NRF node 10 may identify that the common data for the NF set 130 has been provided by the first NF node 132 in step 441 using a common data registration operation. The NRF node 10 may identify the common data for each NF profile of the NF set 130 based on the common data registration operation. The NRF node 10 may associate the common data with the NF set 130. For example, the NRF node 10 may associate the common data with the set identifier of the NF set 130.

The NRF node 10 may update the internal information of the partial NF profile of the third NF node 134 by associating the partial NF profile of the third NF node 134 with the common identifier, for example, based on the set identifier. In a similar manner to that described above for Figure 13, the partial NF profile of the third NF node 134 may comprise one or parameter indicators. The NRF node 10 may thus update the internal information of the partial NF profile of the third NF node 134 based on the one or parameter indicators, in a similar manner to that described above for Figure 13.

As illustrated in Figure 14, in some embodiments, during a discovery 450, the second network node 20 may request information of the NF producers of the NF set 130 providing service A 40, which are registered with the NRF node 10. Thus, in step 452, the second network node 20 may request information of the NF producers associated with service A 40 by transmitting a discovery message to the NRF node 10. Therefore, in some embodiments, the NRF node 10 may receive the discovery message from the second network node 20.

The discovery message transmitted in step 452 may comprise a common data discovery operation for discovering the common data. In some examples, the common data discovery operation may therefore be used to discover the common data of an NF set. In some examples, the common data discovery operation may therefore not be used for discovering specific data of the NF profiles of the NF set 130.

In step 451 , responsive to receiving the discovery message comprising the common data discovery operation, the NRF node 10 may retrieve the common data for the NF set 130, for example, from a memory (e.g. memory 14 of the NRF node 10). In step 453, the NRF node 10 may transmit a discovery response message comprising the common data to the second network node 20. Thus, in some embodiments, the second network node 20 may receive the discovery response message from the NRF node 10. The discovery response message may comprise a common data discovery response operation. The common data discovery response operation may thus indicate the common data to the second network node 20. In some examples, the discovery response message may exclude specific data of the NF profiles of the NF set 130.

In step 454, the second network node 20 may identify the common data based on the common data discovery response operation. The second network node 20 may thus store the common data, for example, in a memory.

As illustrated in Figure 14, in some embodiments, during a subscription to changes 460, the second network node 20 may subscribe to changes of the common data of the NF set 130. Thus, in step 462, the second network node 20 may transmit a subscription to changes request message to the NRF node 10 for subscribing to changes of the common data for the NF set 130. Therefore, in some embodiments, the NRF node 10 may receive the subscription to changes request message from the second network node 20. The subscription to changes request message may comprise a common data subscription operation for subscribing to updates of the common data. In step 464, the NRF node 10 may transmit an acknowledgment to the second network node 20. Thus, in some embodiments, the second network node 20 may receive the acknowledgement from the NRF node 10.

In a similar manner to that described above for Figure 13, during profile update 470, the common data of the NF set 130 may be updated for all members of the NF set 130. Thus, in step 472, the first NF node 132 may transmit an update message to the NRF node 10 comprising the updated common data. Therefore, in some embodiments, the NRF node 10 may receive the update message from the first NF node 132. In some embodiments, the first NF node 132 may receive an acknowledgement from the NRF node 10 in step 474. The update message may comprise a common data update operation for updating the common data. The common data update operation may be used to update the common data for all members of the NF set 130. Thus, a single message may be transmitted to the NRF node 10 to update the common data for each member of the NF set 130. In some examples, the update message may exclude specific data of the NF profiles of the NF set 130.

The NRF node 10 may identify the updated common data based on the common data update operation. In step 476, NRF node 10 may thus update the stored common data for the NF set 130 using the updated common data.

As illustrated in Figure 14, in some embodiments, during a notification of profile changes 480, the NRF node 10 may transmit the updated common data to the second network node 20 (e.g. as the second network node 20 subscribed to changes of the NF set 130 during the subscription to changes 460). In step 481 , the NRF node 10 may identify that common data for the NF set 130 has been updated. In step 482, the NRF node 10 may transmit a notification message to the second network node 20 comprising the updated common data. Thus, in some embodiments, the second network node 20 may receive the notification message from the NRF node 10. The notification message may comprise a common data notify operation for notifying the second network node 20 of the updated common data. In some examples, the notification message may exclude specific data of the NF profiles of the NF set 130. In step 484, the second network node 20 may transmit an acknowledgment message to the NRF node 10. Thus, in some embodiments, the NRF node 10 may receive the acknowledgement message from the second network node 20.

The common data notify operation may indicate the updated common data to the second network node 20. In step 486, the second network node 20 may identify the updated common data based on the common data notify operation. The second network node 20 may update the stored common data for the NF set 130 based on the updated common data.

There is also provided a computer program comprising instructions which, when executed by processing circuitry (such as the processing circuitry 12 of the NRF node 10 described earlier, and/or the processing circuitry 22 of the second network node 20 described earlier, and/or the processing circuitry 32 of the first network node 30 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 NRF node 10 described earlier, and/or the processing circuitry 22 of the second network node 20 described earlier, and/or the processing circuitry 32 of the first network node 30 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 NRF node 10 described earlier and/or the processing circuitry 22 of the second network node 20 described earlier, and/or the processing circuitry 32 of the first network node 30 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.

Examples according to the present disclosure thus present techniques in which common data of a plurality of NF profiles may be identified. The identification of the common data can be subsequently leveraged to provide improvements in, for example, reduced signalling, improved bandwidth, improved storage and improved common data update consistency.

For example, the common data may be stored at an NRF node 10 and/or an NFc node as a single data structure for the NF profiles of the plurality of NF nodes. The stored common data may thus be associated with the plurality of NF nodes. This thus results in storage savings compared to conventional techniques, where the complete NF profile of each of the plurality of NF profiles is stored, where each complete NF profile comprises the common data. The common data is thus stored multiple times in each NF profile in conventional techniques.

In another example, the common data for a plurality of NF nodes may be registered, updated, and/or notified with a single action and/or message. This reduces signalling and improves bandwidth compared to conventional techniques, where the common data for each NF profile of the plurality of NF nodes may be registered, updated, and/or notified per NF profile. Furthermore, the ability to register, update and/or notify changes in the common data with a single action improves data consistency within the plurality of NF nodes, as this eliminates the time delay which may be present in conventional techniques, where the common data for each NF profile of the plurality of NF nodes may be registered, updated, and/or notified at different times.

In another example, the NRF node 10 can be configured with information of the common data for a given plurality of NF nodes. For example, by one of the plurality of NF nodes indicating the common data to the NRF node 10. Subsequently, a remainder of the plurality of NF nodes may register their partial NF profiles with the NRF node 10. The NRF node 10 may subsequently associate the partial NF profiles with the common data based on, for example, a plurality identifier of the plurality of NF nodes. In this way, the common data is configured in one place, which simplifies the network configuration and reduces OP EX.

In some embodiments, the functionality of any one or more nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) described herein can be performed by hardware. Thus, in some embodiments, any one or more of the nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) described herein can be a hardware node. However, it will also be understood that optionally at least part or all of the functionality of any one or more nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) described herein can be virtualized. For example, the functions performed by any one or more of the nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) 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 nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) described herein can be a virtual node. In some embodiments, at least part or all of the functionality of any one or more nodes (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) described herein may be performed in a network enabled cloud. The node (e.g. the first network node, the second network node, any one or more NRF nodes, any one or more NF nodes, and/or any one or more SCP nodes) functionality described herein may all be at the same location or at least some of the node functionality may be distributed.

Other embodiments of the present disclosure are defined in the following numbered statements:

Statement 1. A method (400), performed by a network repository function, NRF, node for identifying common data comprised in a network function, NF, profile of each one of a plurality of first NF nodes of a service producer, the method comprising: receiving (410), from one of the plurality of first NF nodes, a first message comprising the common data; and identifying (420) the common data based on the first message.

Statement 2. A method according to Statement 1 wherein the first message comprises at least a portion of a NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises the common data.

Statement 3. A method according to Statement 1 or 2 further comprising receiving, from the plurality of first NF nodes, one or more second messages, wherein the one or more second messages each comprise the common data; wherein identifying the common data based on the first message further comprises identifying the common data based on the first message and the one or more second messages.

Statement 4. A method according to Statement 3 wherein the at least a portion of the NF profile comprises the NF profile of the one of the plurality of first NF nodes; and wherein the one or more second messages comprise NF profiles of the plurality of first NF nodes, wherein the NF profiles each comprise the common data.

Statement 5. A method according to Statement 2 wherein the at least a portion of the NF profile comprises a common data indicator indicating the common data within the at least a portion of the NF profile; wherein identifying the common data based on the first message comprises identifying the common data based on the common data indicator. Statement 6. A method according to Statement 5 further comprising receiving, from the plurality of first NF nodes, one or more second messages each comprising a partial NF profile of the plurality of first NF nodes, wherein each one of the partial NF profiles excludes the common data.

Statement 7. A method according to Statement 6 further comprising updating each one of the partial NF profiles to comprise one or more data fields of the common data based on the common data indicator.

Statement s. A method according to any one of Statements 5 to 7 wherein the common data indicator comprises one or more first parameter indicators associated with the one or more data fields of the common data.

Statement 9. A method according to Statement 8 wherein the one or more first parameter indicators indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data.

Statement 10. A method according to Statement 9, when dependent on Statement 8, wherein each one of the partial NF profiles comprises one or more second parameter indicators corresponding to one or more of the one or more first parameter indicators; and wherein updating each one of the partial NF profiles to comprise the one or more data fields of the common data based on the common data indicator comprises associating the one or more second parameter indicators with corresponding ones of the one or more first parameter indicators.

Statement 11. A method according to Statement 8 or 9 wherein the NF profile of each one of the plurality of first NF nodes comprises a plurality identifier; wherein each one of the partial NF profiles comprises the plurality identifier; wherein the one or more first parameter indicators are further associated with the plurality identifier; and wherein updating each one of the partial NF profiles to comprise one or more data fields of the common data based on the common data indicator is further based on associating the partial NF profiles with the one or more first parameter indicators based on the plurality identifier comprised in each one of the partial NF profiles. Statement 12. A method according to any of Statements 5-11 wherein the common data indicator comprises a common data registration operation for registering the common data; and wherein identifying the common data based on the first message comprises identifying the common data based on the common data registration operation.

Statement 13. A method according to Statement 12 wherein the first message further comprises specific data of the NF profile.

Statement 14. A method according to Statement 12 further comprising receiving, from the one of the plurality of first NF nodes, an additional message comprising specific data of the NF profile.

Statement 15. A method according to any preceding Statement further comprising: receiving, from a second NF node of a service consumer a third message requesting information of the plurality of first NF nodes; obtaining the common data; and transmitting, to the second NF node, a fourth message comprising the common data.

Statement 16. A method according to Statement 15 wherein the fourth message comprises at least a portion of a NF profile of one of the plurality of first NF nodes; and wherein the at least a portion of the NF profile comprises the common data.

Statement 17. A method according to Statement 16 wherein the at least a portion of the NF profile further comprises specific data of the NF profile of the one of the plurality of first NF nodes.

Statement 18. A method according to Statements 16 or 17 wherein the fourth message further comprises one or more partial NF profiles of a remainder of the plurality of first NF nodes, wherein the one or more partial NF profiles exclude the common data.

Statement 19. A method according to Statement 18 wherein the one or more partial NF profiles comprise specific data of the remainder of the plurality of first NF nodes. Statement 20. A method according to Statement 19 wherein each one of the one or more partial NF profiles comprise a plurality identifier.

Statement 21. A method according to any of Statements 18-20 wherein the at least a portion of the NF profile comprises one or more common data field identifiers associated with one or more data fields of the common data; and wherein the one or more partial NF profiles comprise one or more of the one or more common data field identifiers.

Statement 22. A method according to any of Statements 15 to 21 wherein the third message comprises a common data discovery operation for discovering the common data; and wherein obtaining the common data is based on the common data discovery operation.

Statement 23. A method according to Statement 22 wherein the fourth message comprises a common data discovery response operation for indicating the common data to the second NF node.

Statement 24. A method according to any preceding Statement further comprising: receiving, from one of the plurality of first NF nodes, a fifth message comprising updated common data; and identifying the updated common data based on the fifth message.

Statement 25. A method according to Statement 24 wherein the fifth message comprises at least a portion of a NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises the updated common data.

Statement 26. A method according to Statement 25 further comprising receiving, from the plurality of first NF nodes, one or more sixth messages, wherein the one or more sixth messages each comprise the updated common data; wherein identifying the updated common data based on the fifth message further comprises identifying the updated common data based on the fifth message and the one or more sixth messages.

Statement 27. A method according to Statement 26 wherein the one or more sixth messages comprise at least a portion of NF profiles of the plurality of first NF nodes, wherein the at least a portion of the NF profiles each comprise the updated common data.

Statement 28. A method according to Statement 24 wherein the fifth message excludes specific data of the at least a portion of NF profile of the one of the plurality of first NF nodes.

Statement 29. A method according to Statement 28 wherein the fifth message comprises a common data update operation for updating the common data; and wherein identifying the updated common data based on the fifth message comprises identifying the updated common data based on the common data update operation.

Statement 30. A method according to any of Statements 24 to 29 further comprising transmitting, to a second NF node, a seventh message comprising the updated common data.

Statement 31. A method according to Statement 30 wherein the seventh message comprises the at least a portion of the NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises the updated common data.

Statement 32. A method according to Statement 30 wherein the seventh message excludes specific data of the at least a portion of the NF profile.

Statement 33. A method according to Statement 32 wherein the seventh message comprises a common data notify operation for notifying the second NF node of the updated common data.

Statement 34. A method according to any preceding Statement further comprising receiving, from a second NF node of a service consumer, an eighth message for subscribing to updates of the common data, wherein the eighth message comprises a common data subscription operation for subscribing to updates of the common data. Statement 35. A method according to any preceding Statement wherein the NF profile of each one of a plurality of first N F nodes comprise a same set identifier or a same group identifier.

Statement 36. A method according to Statement 35 when dependent on Statement 10 or Statement 18 by any dependency, wherein the plurality identifier comprises the same set identifier or the same group identifier.

Statement s?. A NRF node comprising processing circuitry configured to operate in accordance with any of Statements 1 to 36.

Statement 38. A NRF node according to Statement 37 further comprising at least one memory for storing instructions which, when executed by the processing circuitry, cause the NRF node to operate in accordance with any of Statements 1 to 36.

Statement 39. A method (600), performed by a first NF network node of a service consumer, for identifying common data comprised in a NF profile of each one of a plurality of second NF nodes of a service producer, the method comprising: transmitting (610), to a NRF node, a first message requesting information of the plurality of second NF nodes; receiving (620), from the NRF node, a second message comprising the common data; and identifying (630) the common data based on the second message.

Statement 40. A method according to Statement 39 wherein the second message comprises at least a portion of a NF profile of one of the plurality of second NF nodes; and wherein the at least a portion of the NF profile comprises the common data; wherein identifying the common data based on the second message comprises identifying the common data based on the at least a portion of the NF profile.

Statement 41. A method according to Statement 40 wherein the at least a portion of the NF profile further comprises specific data of the NF profile of the one of the plurality of first NF nodes. Statement 42. A method according to Statement 41 further comprising storing the common data separately from the specific data of the NF profile of the one of the plurality of first NF nodes.

Statement 43. A method according to any of Statements 40-42 wherein the second message further comprises one or more partial NF profiles of a remainder of the plurality of second NF nodes, wherein the one or more partial NF profiles exclude the common data; wherein identifying the common data based on the second message comprises identifying the common data based on the at least a portion of the NF profile and the one or more partial NF profiles.

Statement 44. A method according to Statement 43 wherein identifying the common data based on the at least a portion of the NF profile and the one or more partial NF profiles comprises identifying that the at least a portion of the NF profile comprises the common data and identifying that the one or more partial NF profiles exclude the common data.

Statement 45. A method according to Statement 43 or 44 wherein the one or more partial NF profiles comprise specific data of the remainder of the plurality of second NF nodes.

Statement 46. A method according to Statement 45, when dependent on Statement 42, further comprising storing the common data separately from the specific data of the one or more partial NF profiles.

Statement 47. A method according to any of Statements 43-46 wherein each one of the one or more partial NF profiles comprise a plurality identifier.

Statement 48. A method according to any of Statements 44-48 wherein the at least a portion of the NF profile comprises one or more common data identifiers associated with one or more data fields of the common data; wherein the one or more partial NF profiles comprise one or more of the one or more common data field identifiers; wherein the method further comprises associating the one or more of the one or more common data field identifiers with the one or more data fields of the common data. Statement 49. A method according to any of Statements 39 to 48 wherein the first message comprises a common data discovery operation for discovering the common data.

Statement 50. A method according to any of Statements 39 to 49 wherein the second message comprises a common data discovery response operation for indicating the common data to the first NF node.

Statement 51. A method according to any of Statements 39 to 50 further comprising receiving, from the NRF node, a third message comprising updated common data; and identifying the updated common data based on the third message.

Statement 52. A method according to Statement 51 wherein the third message comprises at least a portion of a NF profile of one of the plurality of second NF nodes, wherein the at least a portion of the NF profile comprises the updated common data; and wherein identifying the updated common data comprises associating the at least a portion of the NF profile with the identified common data of the plurality of second NF nodes.

Statement 53. A method according to Statement 52 wherein the at least a portion of the NF profile comprises a plurality identifier and associating the at least a portion of the NF profile with the identified common data of the plurality of second NF nodes is based on the plurality identifier.

Statement 54. A method according to any of Statements 51-53 wherein the third message excludes specific data of the NF profile of the one of the plurality of first NF nodes.

Statement 55. A method according to Statement 54 wherein the third message comprises a common data notify operation for notifying the second NF node of the updated common data.

Statement 56. A method according to any of Statements 51 to 55 further comprising updating the common data based on the updated common data. Statement 57. A method according to any of Statements 39 to 56 further comprising transmitting, to the NRF node, a fifth message for subscribing to updates of the common data, wherein the fifth message comprises a common data subscription operation for subscribing to updates of the common data.

Statement 58. A method according to any of Statements 39 to 57 wherein the NF profile of each one of a plurality of first NF nodes comprise a same set identifier or a same group identifier.

Statement 59. A method according to Statement 58 when dependent on Statement 47 or Statement 53 by any dependency, wherein the plurality identifier comprises the same set identifier or the same group identifier.

Statement 60. A first NF node of a service consumer comprising processing circuitry configured to operate in accordance with any of Statements 39 to 59.

Statement 61. A first NF node according to Statement 60 further comprising at least one memory for storing instructions which, when executed by the processing circuitry, cause the NRF node to operate in accordance with any of Statements 39 to 59.

Statement 62. A method (700), performed by a first NF network node of a service producer, for providing common data comprised in a network function, NF, profile of each one of a plurality of first NF nodes of the service producer, wherein the first NF network node is one of the plurality of first NF nodes of the service producer, the method comprising: transmitting (710), to a NRF node, a first message comprising the common data.

Statement 63. A method according to Statement 62 wherein the first message comprises at least a portion of a NF profile of the first NF node, wherein the at least a portion of the NF profile comprises the common data.

Statement 64. A method according to Statement 63 wherein the at least a portion of the NF profile comprises a common data indicator indicating the common data within the at least a portion of the NF profile. Statement 65. A method according to Statement 64 wherein the common data indicator comprises one or more first parameter indicators associated with one or more data fields of the common data.

Statement 66. A method according to Statement 65 wherein the one or more first parameter indicators indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data.

Statement 67. A method according to any of Statements 63 to 66 wherein the at least a portion of the NF profile comprises a plurality identifier.

Statement 68. A method according to Statement 67 wherein the plurality identifier comprises a same set identifier or a same group identifier for each of the plurality of first NF nodes.

Statement 69. A method according to any of Statements 62 to 68 wherein the first message comprises a common data registration operation for registering the common data with the NRF node.

Statement 70. A method according to any of Statements 62 to 69 further comprising transmitting, to the NRF node, a second message comprising updated common data.

Statement 71. A method according to Statement 70 wherein the second message comprises at least a portion of an updated NF profile of the first NF node, wherein the at least a portion of the updated NF profile comprises the updated common data.

Statement 72. A method according to Statement 71 wherein the at least a portion of the updated NF profile excludes specific data of the updated NF profile of the first NF node.

Statement 73. A method according to Statement 72 wherein the second message comprises a common data update operation for registering the updated common data with the NRF node. Statement 74. A method (900), performed by a first NF network node of a service producer, for providing specific data comprised in a network function, NF, profile of the first NF node of the service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer, the method comprising: transmitting (910), to a NRF node, a first message comprising the specific data.

Statement 75. A method according to Statement 74 wherein the first message comprises a partial NF profile of the first NF node, wherein the partial NF profile excludes common data, wherein the common data is comprised in a NF profile of each one of the plurality of first NF nodes.

Statement 76. A method according to Statement 75 wherein the partial NF profile comprises one or more first parameter indicators associated with the one or more data fields of the common data.

Statement 77. A method according to Statement 76 wherein the one or more first parameter indicators indicate one or more mandatory data fields of the common data or one or more optional data fields of the common data.

Statement 78. A method according to any of Statements 74 to 77 wherein the partial NF profile comprises a plurality identifier.

Statement 79. A method according to Statement 78 wherein the plurality identifier comprises a same set identifier or a same group identifier for each of the plurality of first NF nodes.

Statement 80. A first NF node comprising processing circuitry configured to operate in accordance with any of Statements 62 to 73 or 74 to 79.

Statement 81. A first NF node according to Statement 80 further comprising at least one memory for storing instructions which, when executed by the processing circuitry, cause the first NF node to operate in accordance with any of Statements 62 to 73 or 74 to 79.

Statement 82. A method performed by a system, the method comprising: the method as in any of Statements 1 to 36; the method as in any of Statements 39 to 59; the method as in any of Statements 62 to 73 and/or 74 to 79.

Statement 83. A system comprising: at least one NRF node as in Statement 37 or 38; at least one first NF node as in Statement 61 or 62; and at least one first NF node as in Statement 80 or 81 .

Statement 84. A computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method according to any of Statements 1 to 36, any of Statements 39 to 59, any of Statements 62 to 73, and/or any of Statements 74 to 79.

Statement 85. 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 Statements 1 to 36, any of Statements 39 to 59, any of Statements 62 to 73, and/or any of Statements 74 to 79.

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 (400) for handling data in a network, wherein the method is performed by a network repository function, NRF, node, the method comprising: receiving (410, 341, 441) a first message from a first network node, wherein the first network node is one of a plurality of first network function, NF, nodes of a service producer or the first network node is a first service communication proxy, SCP, node configured to operate as an SCP between the NRF node and the plurality of first NF nodes, and wherein the first message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes; and handling (420, 345) the common data based on the first message.

2. A method according to claim 1 , wherein: the first message comprises any one or more of: at least a portion of an NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises the common data; a same set identifier or a same group identifier; and a common data registration operation for registering the common data.

3. A method according to claim 1 or 2, comprising: receiving, from the first SCP node or the plurality of first NF nodes, one or more second messages each comprising a partial NF profile of the plurality of first NF nodes, wherein each one of the partial NF profiles excludes the common data.

4. A method according to any of the preceding claims, wherein: the first message comprises specific data of the NF profile; or the method comprises receiving, from the first network node, an additional message comprising specific data of the NF profile.

5. A method (1300) for handling data in a network, wherein the method is performed by a network repository function, NRF, node, the method comprising: receiving (1310, 452) a third message from a second network node, wherein the second network node is a second network function, NF, node of a service consumer or the second network node is a second service communication proxy, SCP, node configured to operate as an SCP between the NRF node and the second NF node, and wherein the third message requests information of a plurality of first NF nodes of a service producer; and transmitting (1320, 453) a fourth message to the second network node, wherein the fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes.

6. A method according to claim 5, wherein: the fourth message comprises at least a portion of an NF profile of one of the plurality of first NF nodes; and the at least a portion of the NF profile comprises the common data.

7. A method according to claim 6, wherein: the at least a portion of the NF profile further comprises specific data of the NF profile of the one of the plurality of first NF nodes.

8. A method according to claim 6 or 7, wherein: the fourth message further comprises one or more partial NF profiles of a remainder of the plurality of first NF nodes; and the one or more partial NF profiles exclude the common data.

9. A method according to claim 8, wherein: the one or more partial NF profiles comprise specific data of the remainder of the plurality of first NF nodes.

10. A method according to any of claims 5 to 9, wherein: the third message comprises a common data discovery operation for discovering the common data; and obtaining the common data is based on the common data discovery operation.

11. A method according to any of claims 5 to 10, comprising: receiving a fifth message from a first network node, wherein the first network node is one of the plurality of first NF nodes or the first network node is a first SCP node configured to operate as an SCP between the NRF node and the plurality of first NF nodes, and wherein the fifth message comprises at least a portion of an NF profile of the one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises updated common data.

12. A method according to claim 11, wherein: the fifth message excludes specific data of the at least a portion of the NF profile of the one of the plurality of first NF nodes.

13. A method according to claim 11 or 12, comprising: transmitting the fifth message to the second network node.

14. A method according to any preceding claim, further comprising: receiving, from a second NF node of a service consumer, a sixth message for subscribing to updates of the common data, wherein the sixth message comprises a common data subscription operation for subscribing to updates of the common data.

15. A method (600) for handling data in a network, wherein the method is performed by a second network node and wherein the second network node is a second network function, NF, node of a service consumer or the second network node is a second service communication proxy, SCP, node configured to operate as an SCP between the second NF node and a network repository function, NRF, node, the method comprising: transmitting (610, 452) a third message to the NRF node, wherein the third message requests information of a plurality of first NF nodes of a service producer; receiving (620, 453) a fourth message from the NRF node, wherein the fourth message comprises common data that is common to an NF profile of each one of the plurality of first NF nodes; and handling (630) the common data based on the fourth message.

16. A method according to claim 15, wherein: the fourth message comprises at least a portion of an NF profile of one of the plurality of first NF nodes; the at least a portion of the NF profile comprises the common data; and handling the common data based on the fourth message comprises handling the common data based on the at least a portion of the NF profile.

17. A method according to claim 16, wherein: the at least a portion of the NF profile comprises specific data of the NF profile of the one of the plurality of first NF nodes.

18. A method according to claim 17, comprising: storing the common data separately from the specific data of the NF profile of the one of the plurality of first NF nodes.

19. A method according to any of claims 16 to 18, wherein: the fourth message comprises one or more partial NF profiles of a remainder of the plurality of first NF nodes; the one or more partial NF profiles exclude the common data; and handling the common data based on the fourth message comprises handling the common data based on the at least a portion of the NF profile and the one or more partial NF profiles.

20. A method according to claim 19, wherein: handling the common data based on the at least a portion of the NF profile and the one or more partial NF profiles comprises: identifying that the at least a portion of the NF profile comprises the common data; and identifying that the one or more partial NF profiles exclude the common data.

21. A method according to claim 19 or 20, wherein: the one or more partial NF profiles comprise specific data of the remainder of the plurality of first NF nodes.

22. A method according to any of claims 15 to 21 , wherein: the third message comprises a common data discovery operation for discovering the common data.

23. A method according to any of claims 15 to 22, wherein: the fourth message comprises a common data discovery response operation for indicating the common data to the second NF node.

24. A method according to any of claims 15 to 23, comprising: receiving, from the NRF node, a seventh message comprising at least a portion of an NF profile of one of the plurality of first NF nodes, wherein the at least a portion of the NF profile comprises updated common data.

25. A method according to claim 24, wherein: the seventh message excludes specific data of the NF profile of the one of the plurality of first NF nodes.

26. A method according to any of claims 15 to 25, further comprising: transmitting, to the NRF node, a sixth message for subscribing to updates of the common data, wherein the sixth message comprises a common data subscription operation for subscribing to updates of the common data.

27. A method (800) for handling data in a network, wherein the method is performed by a first network node, wherein the first network node is a first network function, NF, node of a service producer or 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 network repository function, NRF node, the method comprising: transmitting (810, 341, 441) a first message to the NRF node, wherein the first message comprises common data that is common to an NF profile of each one of a plurality of first NF nodes of the service producer, wherein the first NF node is one of the plurality of first NF nodes of the service producer.

28. A method according to claim 27, wherein: the first message comprises: at least a portion of an NF profile of the first NF node, wherein the at least a portion of the NF profile comprises the common data; a same set identifier or a same group identifier for each of the plurality of first NF nodes; and a common data registration operation for registering the common data with the NRF node.

29. A method according to claim 27 or 28, comprising: transmitting, to the NRF node, a second message comprising at least a portion of an updated NF profile of the first NF node, wherein the at least a portion of the updated NF profile comprises updated common data.

30. A method according to claim 29, wherein: the at least a portion of the updated NF profile excludes specific data of the updated NF profile of the first NF node.

31. A method (900) for handling data in a network, wherein the method is performed by a first network node, wherein the first network node is a first network function, NF, node of a service producer or 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 network repository function, NRF, node, the method comprising: transmitting (910, 343, 443) an eighth message to the NRF node, wherein the eighth message comprises specific data of an NF profile of the first NF node, wherein the first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

32. A method (1400) for handling data in a network, wherein the method is performed by a network repository function, NRF, node, the method comprising: receiving (1410, 343, 443) an eighth message from a first network node, wherein the first network node is a first network function, NF, node of a service producer or the first network node is a first service communication proxy, SCP, node configured to operate as an SCP between the first NF node and the NRF node, wherein the eighth message comprises specific data of an NF profile of the first NF node, wherein the first NF node is one of a plurality of first NF nodes of the service producer and the specific data excludes common data that is common to an NF profile of each one of the plurality of first NF nodes.

33. A network function repository, NRF, node (10) comprising: processing circuitry (12) configured to operate in accordance with any of claims 1 to 4, any of claims 5 to 14, and/or claim 32.

34. A first network node (30) comprising: processing circuitry (32) configured to operate in accordance with any of claims 27 to 30 and/or claim 31.

35. A second network node (20) comprising: processing circuitry (22) configured to operate in accordance with any of claims 15 to 26.

36. A method performed by a system, the method comprising: the method as claimed in any of claims 1 to 4, any of claims 5 to 14, and/or claim 32; the method as claimed in any of claims 27 to 30 and/or claim 31 ; and/or the method as claimed in any of claims 15 to 26.

37. A system comprising any two or more of: an NRF node (10) as claimed in claim 33; a first network node (30) as claimed in claim 34; and a second network node (20) as claimed in claim 35.

38. A computer program comprising instructions which, when executed by processing circuitry, cause the processing circuitry to perform the method according to any of claims 1 to 4, any of claims 5 to 14, any of claims 15 to 26, any of claims 27 to 30, claim 31 , and/or claim 32.