WO2020113405A1

WO2020113405A1 - Configuration updates of service functions in service-based network architecture

Info

Publication number: WO2020113405A1
Application number: PCT/CN2018/119101
Authority: WO
Inventors: Zhiwei Qu; Dinand Roeland; Yin Wang
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-12-04
Filing date: 2018-12-04
Publication date: 2020-06-11

Abstract

In one aspect, a first network node can provide to one or more other network nodes information pertaining to a configuration update performed by the first network node so that the one or more other nodes do not need to retrieve the configuration update information from a central database.

Description

[Title established by the ISA under Rule 37.2] CONFIGURATION UPDATES OF SERVICE FUNCTIONS IN SERVICE-BASED NETWORK ARCHITECTURE

TECHNICAL FIELD

Disclosed are embodiments related to handling configuration updates of service functions in a service-based network architecture (e.g., a 5G core network) .

BACKGROUND

In a service-based network architecture, the network may contain multiple network nodes that implement the same service function. One way to configure these network nodes is to let each network node download configuration data from a central database. For example, information pertaining to a configuration update can be sent to each of these network nodes from the central database using a publish-subscribe model, where each network node subscribes to the configuration update.

SUMMARY

One problem with the above described publish-subscribe model is that it can create a high load on the central database. Another problem is that the central database needs to store all of the up-to-date configuration parameters.

This disclosure provides alternative ways for configuring network nodes. For example, instead of each network node accessing a central database to obtain information pertaining to a configuration update, some of the disclosed embodiments take a more distributed approach where, for instance, one network node can provide to one or more other network nodes the information pertaining to the configuration update so that these one or more other nodes do not need to retrieve this information from the central database.

Accordingly, in one aspect, there is a method performed by a second network node implementing a service function of a first type. In some embodiments, the method includes: (1) the second network node receiving a message transmitted by a control node, wherein the message indicates that a first network node has performed a first configuration update and further wherein the first network node implements the service function of the first type; (2) the second network node, based on the message, transmitting to the first network node a request message requesting information pertaining to the first configuration update; and (3) after transmitting the request message to the first network node, the second network node receiving an update message transmitted by the first network node in response to the request message, wherein the update message comprises the information pertaining to the first configuration update.

In some embodiments, the method also includes the second network node performing a second configuration update based on the update message transmitted by the first network node, and after the second network node performs the second configuration update, the second network node sends an acknowledgement message to the control node, wherein the acknowledgement message indicates that the second network node has performed the second configuration update.

In some embodiments, the information pertaining to the first configuration update comprises an updated parameter value, and the first configuration update performed by the first network node comprises the first network node replacing a first stored parameter value (e.g., a parameter value stored on a storage unit that is a component of the first network node) with the updated parameter value, and the second configuration update performed by the second network node comprises the second network node replacing a second stored parameter value (e.g., a parameter value stored on a storage unit that is a component of the first network node) with the updated parameter value included in the update message.

With respect to other embodiments, in one aspect, there is a method performed by a first network node that implements a service function of a first type. The method includes (1) performing a first configuration update; (2) after performing the first configuration update, sending a first message to a control node; (3) after sending the first message to the control node, receiving a second message transmitted by the control node in response to the first message, wherein the second message includes identifier information identifying a second network node to which the first network node is to send information pertaining to the first configuration update, wherein the second network node implements the service function of the first type; and (4) based on receiving the second message from the control node, sending to the second network node a first update message comprising the information pertaining to the first configuration update, wherein the first update message triggers the second network node to initiate a second configuration update.

In some embodiments, the method also includes the second network node performing a second configuration update based on the information pertaining to the first configuration update included in the first update message, and after the second network node performs the second configuration update, the second network node sends an acknowledgement message to the first network node, wherein the acknowledgement message indicates that the second network node has performed the second configuration update.

In some embodiments, the information pertaining to the first configuration update comprises an updated parameter value, and the first configuration update performed by the first network node comprises the first network node replacing a first stored parameter value (e.g., a parameter value stored on a storage unit that is a component of the first network node) with the updated parameter value, and the step of performing the second configuration update comprises the second network node replacing a second stored parameter value (e.g., a parameter value stored on a storage unit that is a component of the first network node) with the updated parameter value included in the update message.

In some embodiments, the first update message is configured to trigger the second network node to send to the control node a third message requesting identifier information of at least one other network node that needs to perform a configuration update corresponding to the first configuration update performed by the first network node.

In some embodiments, the method further includes the first network node, based on receiving the second message transmitted by the control node, sending to a third network node a second update message containing the information pertaining to the update, where the second update message triggers the third network node to initiate a third configuration update. In some embodiments, the second message transmitted by the control node includes identifier information identifying the third network node, and the third network node implements the service function of the first type.

In some embodiments, the method further includes the first network node sending to the control node an acknowledgment after the third network node has performed the third configuration update, wherein the acknowledgment message indicates that the third network node has performed the third configuration update and further indicates that the second network node has received the first update message.

In some embodiments, the second update message is configured to not trigger the third network node to send to the control node any request message requesting identifier information of at least one other network node that needs to perform a configuration update corresponding to the first configuration update performed by the first network node.

In another aspect there is a method performed by a control node. The method comprises: (1) receiving a first message transmitted by a first network node that implements a service function of a first type, wherein the first network node transmitted the first message after performing a configuration update; and (2) based on receiving the first message, sending a second message to a second network node that implements the service function of the first type, wherein the second message is configured to trigger the second network node to initiate a process for fetching from the first network node information pertaining to the configuration update. In other embodiments, the first message contains the information pertaining to the configuration update and the second message contains the information pertaining to the configuration update.

In some embodiments, the method further includes the control node, based on receiving the first message and prior to sending the second message to the second network node, selecting one or more network nodes from a set of network nodes, wherein each network node included in the set of network nodes implements the service function of the first type, and the second network node is one of the one or more selected network nodes.

With respect to other embodiments, in another aspect, there is a method performed by a control node. The method includes (1) receiving a first message transmitted by a first network node, wherein the first message indicates that the first network node has performed a first configuration update; and (2) based on receiving the first message, sending a second message to the first network node, wherein the second message identifies a second network node and triggers the first network node to transmit to the second network node a first update message comprising information pertaining to the update, wherein the first network node implements a service function of a first type, and the second network node implements the service function of the first type.

In some embodiments, the method further includes the control node receiving a third message transmitted by the second network node; and based on receiving the third message, sending a fourth message to the second network node, wherein the fourth message identifies a third network node and triggers the second network node to transmit to the third network node a second update message comprising information pertaining to the first configuration update performed by the first network node.

In some embodiments, the first update message is configured to trigger the second network node to send the third message to the control node.

In some embodiments, the method further includes the control node, based on receiving the first message and prior to sending the second message to the first network node, selecting a group of one or more network nodes from a set of network nodes, wherein each network node included in the set of network nodes implements the service function of the first type, and the second message comprises, for each node included in the selected group, an identifier identifying the node.

In some embodiments, the method further includes the control node obtaining capability information pertaining to the first network node, wherein a number of network nodes in the group is selected based on the obtained capability information.

In some embodiments, the control node further includes receiving an acknowledgement message transmitted by the first network node, wherein the acknowledgement message indicates that the second network node has received the first update message.

An advantage of the above described embodiments is that unlike the publish-subscribe model, not all configuration parameters need to be known in the central database. This makes management of the overall system easier. Furthermore, the above described embodiments allow network nodes to make configuration updates without having to communicate with the central database, thereby lowering the probability that the central database will become overloaded.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

FIG. 1A illustrates a service-based architecture view, according to some embodiments.

FIG. 1B is a message flow diagram illustrating an exchange of messages between two network nodes.

FIG. 2 illustrates data stored in a control node.

FIG. 3 is a flow chart illustrating a process according to some embodiments.

FIG. 4 is a message flow diagram illustrating exchanges of messages among a plurality of network nodes and a control node.

FIG. 5 is a message flow diagram illustrating exchanges of messages among a plurality of network nodes and a control node.

FIG. 6 is a message flow diagram illustrating exchanges of messages among a plurality of network nodes and a control node.

FIG. 7A is a flow chart illustrating a process according to some embodiments.

FIG. 7B is a flow chart illustrating a process according to some embodiments.

FIG. 8A is a flow chart illustrating a process according to some embodiments.

FIG. 8B is a flow chart illustrating a process according to some embodiments.

FIG. 9 is a block diagram of an apparatus according to some embodiments.

DETAILED DESCRIPTION

FIG. 1A illustrates a service-based network architecture, according to some exemplary embodiment. The service-based architecture 100 includes a plurality of network nodes 101-104 and a control node 105 (e.g., a node implementing a 3GPP 5G Network Repository Function (NRF) ) . According to the present invention, a network node can be a physical computing device or a virtual machine. Thus, two different network nodes can be two different physical computing devices or two different virtual machines running in the same physical computing device. In the embodiment shown, each of network nodes 101-104 are connected to control node 105 via a network 110 (e.g., an IP network) . Additionally, each network node 101-104 (or “node” for short) implements a service function, such as, for example, a 3GPP network function listed in 3GPP TS 23.501 v 15.3.0 section 4.2.2. In a preferred embodiment, each node 101-104 implements a service function of the same type. For instance, in one example, each node 101-104 implements an Access and Mobility Management Function (AMF) , or, as another example, each node 101-104 implements a Session Management Function (SMF) , or, as another example, each node 101-104 implements a User Plane Function (UPF) .

FIG. 1B is a message flow diagram according to an embodiment. As shown in FIG. 1B, node 101 detects a configuration update event, which triggers a configuration update at node 101 (Step 150) . The event may be an operator of node 101 initiating the configuration update and/or another node (e.g., an node that is a part of an operations and maintenance (O&M) system) initiating the configuration update, or a scheduled event (e.g., a pre-scheduled update) . In response to detecting the event, node 101 performs a configuration update (Step 152) . In some embodiments, performing the configuration update comprises or consists of node 101 changing the value of a configuration parameter (e.g., a threshold value, a weight value, etc. ) stored in a storage medium of node 101. Accordingly, as an example, in step 150 node 101 replaces a currently stored threshold value (e.g., thresh1=10) with a new (or “updated” ) threshold value (e.g., thresh1=12) .

After node 101 completes the configuration update, node 101 sends to node 102 a message 154 comprising information pertaining to the configuration update. The information pertaining to the configuration update may contain a new value for a configuration parameter. Thus, message 154 may include a field containing the new (i.e., updated) parameter value or a name-value-pair containing the name of the update configuration parameter and the updated parameter value. Based on the received information pertaining to the configuration update, node 102 performs a configuration update. For example, as described above, in some embodiments the information pertaining to the configuration update comprises an updated parameter value (e.g., a name-value-pair (e.g., thresh1=12) that contains the updated parameter value) and node 102 performs the configuration update by replacing a stored parameter value (e.g., thresh1=10) (e.g., a parameter value stored on a storage unit that is a component of node 102) with the updated parameter value (e.g., thresh1=12) . Optionally, after node 102 performs the configuration update, node 102 sends to the first network node a message 158 acknowledging the completion of the configuration update by node 102.

FIG. 4 is a message flow diagram according to some embodiments. Initially, network node 101 performs step 150, which is described above. That is, node 101 detects an event, which triggers a configuration update at network node 101.

In response to detecting the event, network node 101 performs a configuration update (step 152) . As discussed above, the configuration update performed at network node 101 may be changing the value of a configuration parameter stored in a storage medium of network node 101. Once network node 101 completes the configuration update, network node 101 sends to control node 105 a notification message 454 providing an indication that network node 101 has performed the configuration update. Notification message 454 may be an existing standard message, such as “Nnrf_NFDiscovery_Request” disclosed in 3GPP TS 23.502 v 15.1.0 section 4.17.4, with an additional parameter providing the indication that network node 101 has performed the configuration update, or it may be a new message. Based on notification message 454, control node 105 sends to network node 101 a response message 456. The content of response message 456 is determined by control node 105, as discussed below.

FIG. 3 illustrates a process showing how control node 105 determines the content of response message 456 in one embodiment. Based on notification message 454 received from network node 101, control node 105 identifies the type of a service function implemented by node 101 (step 302) (e.g., node 105 determines that node 101 implements an AMF) . After identifying the service function, control node 105 obtains capability information pertaining to a capability of network node 101 (step 304) to update other nodes. In the embodiments shown on FIG. 3, the capability information is obtained after control node 105 identifies the type of the service function implemented by network node 101. However, the capability information may be obtained at any time before control node 105 sends response message 456 to network node 101.

Based on the identified service function implemented by network node 101 and the obtained capability information, control node 105 selects a group of nodes from a set of nodes (e.g., set 203 or set 204) . Each node in the set of nodes implements the service function of the identified type (e.g., if node 101 implements an AMF, then each node in the set of nodes also implements an AMF) . In the embodiments shown on FIG. 4, network nodes 101-104 are included in the set of nodes.

Before the group of nodes is selected from the set of nodes, the number of nodes to be included in the group is determined based on the capability information. The capability information may indicate the processing power of node 101, the current load on node 101, and/or other information indicating node 101’s capability to update other nodes. In the embodiments shown on FIG. 4, control node 105 selects two nodes (e.g., network nodes 102 and 103) from the set of nodes (e.g., network nodes 101-104) . In order for control node 105 to select the group of nodes from the set of nodes based on the capability information, control node 105 may include data shown on FIG. 2.

FIG. 2 illustrates data stored in control node 105. The data includes two tables 201 and 202. Table 201 includes identifiers of nodes included in a first set of nodes 203 each implementing a service function of a first type (e.g., AMF) , and capability information for the nodes in the first set. Similarly, table 202 includes identifiers of nodes included in a second set of nodes 204 each implementing a service function of a second type (e.g., SMF) , and capability information for the nodes included in the second set. In some embodiments, an identifier identifying a node may be an IP address, an Endpoint Address, an Uniform Resource Identifier (URI) , or a name assigned to the node (e.g., Fully Qualified Domain Name (FQDN) ) . The format of the data (i.e., a table format) , the number of nodes for each service function type, and the number of service function types are shown on FIG. 2 for illustration purpose only, and do not limit the present invention in any way.

Referring back to FIG. 4, as explained above, based on notification message 454, control node 105 identifies the type of the service function implemented by network node 101 and selects a group of nodes from the set of nodes implementing the service function of the identified type. When there is no node implementing the service function of the identified type, control node 105 may not take any action or may just send to network node 101 a message acknowledging the receipt of notification message 454.

After selecting the group of nodes, control node 105 generates response message 456 that comprises, for each node included in the selected group, an identifier identifying the node. As explained above, the number of node identifiers included in response message 456 (i.e., the size of the selected group) may be determined based on the obtained capability information for network node 101 (e.g., the load on node 101) . In this example, the selected group consists of

nodes

102 and 103. Accordingly, response message 456 comprises an identifier identifying node 102 and an identifier identifying node 103.

Response message 456 may also provide an indication (e.g., a first flag set to a value of 1 or “fwd” ) that network node 102 should send a notification message to control node 105 after network node 102 receives a message 458 and response message 456 may provide an indication (e.g., a second flag set to a value of 0 or “no fwd” ) that node 103 should not send a notification message to control node 105 after node 103 receives a message 464. The difference between the two indications may be based on the capabilities of and/or or load on

network nodes

102 and 103. Thus, for example, if control node 105 determines that node 103 does not have a capability to update other nodes (e.g., is in an overload state) , then control node 105 may configure response message 456 such that response message 456 indicates that node 103 should not send a notification message to control node 105 after receiving message 464.

Based on response message 456, network node 101 sends to network node 102 a message 458 (e.g., Update) including information pertaining to the configuration update performed at network node 101. Similarly, based on response message 456, network node 101 sends to network node 103 a message 464 (e.g., Update ) including information pertaining to the configuration update performed at network node 101. In some embodiments, the information pertaining to the configuration update may include an updated parameter value and information identifying the parameter (e.g., threshold-1=10) .

Based on message 458, network node 102 performs a configuration update (step 460) and optionally sends to network node 101 a message 462 (e.g., an ACK) providing an indication that network node 102 has completed the configuration update. As mentioned above, the information pertaining to the configuration update may include an updated parameter value and information identifying the parameter and node 102 performs the configuration update by replacing a stored parameter value (e.g., a parameter value stored on a storage unit that is a component of node 102) with the updated parameter value. For instance, if threshold-1 was equal to 5 before node 102 received message 458, then as a result of receiving message 458 node 102 updates threshold-1 so that it is now equal to 10.

Based on message 464, network node 103 performs a configuration update and optionally sends to network node 101 message 468 providing an indication that network node 103 has completed its configuration update. As explained above, response message 456 may provide an indication that network node 103 should not send a notification message to control node 105. Thus, message 464 transmitted by network node 101 to network node 103 may provide an indication that network node 103 should not send a notification message to control node 105. For example, a flag included in message 464 may be set to a value of 0 (i.e., “not fwd” ) or message 464 may not contain a particular parameter (e.g., attribute-value-pair (AVP) or name-value-pair) , and the absence of the particular parameter indicates that node 103 should not send a notification message to control node 105. In some embodiments, the messages disclosed herein are formatted in accordance with JavaScript Object Notation (JSON) format.

As a result receiving

positive acknowledgement messages

462 and 468, network node 101 sends to control node 105 message 470 indicating that network node 101 has sent configuration update messages to

nodes

102 and 103 and had receives from each of node 102 and 103 a positive acknowledgement. Optionally, control node 105 may acknowledge message 470 by sending to node 101 message 472.

As explained above, response message 456 may provide an indication that network node 102 should send a message to control node 105. Thus, message 458 may trigger network node 102 to send a notification message 474 to control node 105 (e.g., message 458 may include a flag set to a value of 1 or “fwd” ) . Based on notification message 474, control node 105 sends to network node 102 a response message 476 including an identifier identifying one or more network nodes to which network node 102 should send information about the configuration update performed at network node 102 (in this case the one or more identified network nodes includes node 104) . Response message 476 may also provide an indication that network node 104 should not send a notification message to control node 105.

Based on response message 476, network node 102 sends to network node 104 a message 478 (e.g., Update) including information pertaining to the configuration update performed at network node 102 (which is the same configuration update performed at nodes 101 and 103) . Based on the information, network node 104 performs a configuration update and then optionally sends to network node 102 a message 482 providing an indication that network node 104 has completed its configuration update. As a result of receiving message 482, node 102 sends to control node 105 a message 484 providing an indication that node 104 has completed its configuration update. Optionally, control node 105 may then send to network node 102 a message 486 acknowledging the receipt of message 484.

FIG. 5 is a message flow diagram according to some embodiments. Initially, network node 101 performs

steps

150 and 152, described above.

After network node 101 performs step 152, network node 101 sends to control node 105 a notification message 554 providing an indication that network node 101 has performed a configuration update. Notification message 554 may be an existing standard message, such as “Nnrf_NFDiscovery_Request” disclosed in 3GPP TS 23.502 v 15.1.0 section 4.17.4, with an additional parameter providing the indication that network node 101 has performed the configuration update, or it may be a new message. Based on notification message 554, control node 105 may send a response message 556 to network node 102. In some embodiments, based on notification message 554, control node 105 identifies the type of a service function implemented by network node 101 and sends to a selected group of one or more nodes implementing the service function of the identified type message 558 (e.g., Configuration Update) . In the embodiments shown on FIG. 5, network node 102 is one of nodes in the selected group. If control node 105 determines that there is no other node implementing the service function of the identified type, control node 105 may not take any action or may send to control node 101 a message simply acknowledging the receipt of message 554.

Furthermore, in some embodiments, the selected group of nodes is selected from a set of nodes implementing the service function of the identified type based on the capability of node 101. Thus, even though, in the embodiments shown on FIG. 5, control node 105 sends message 558 to only network node 102, control node 105 may send message 558 to other additional nodes or may not send message 558 to network node 102 or any other node depending on the capability of network node 101.

Referring back to FIG. 5, message 558 is configured to trigger network node 102 to fetch from network node 101 information pertaining to the configuration update performed at network node 101. Thus, message 558 may include an identifier identifying node 101. In some embodiments, an identifier identifying a node may be an IP address, an Endpoint Address, an Uniform Resource Identifier (URI) , or a name assigned to the node (e.g., Fully Qualified Domain Name (FQDN) ) . Based on message 558, node 102 sends to network node 101 a message 560 (a Get message) requesting network node 101 to send to node 102 the information pertaining to the configuration update. As a result of receiving message 560, network node 101 sends to node 101 a message 562 (a. k. a., update message) containing information pertaining to the configuration update performed by node 101. Based on message 562, network node 102 performs a configuration update (step 564) . Optionally, after network node 102 performs the configuration update, network node 102 sends to control node 105 a message 568 providing an indication that network node 102 has completed its configuration update and sends to network node 101 a message 566 providing an indication that network node 102 has completed a configuration update.

FIG. 6 is a message flow diagram according to some embodiments. Initially, network node 101 performs

steps

150 and 152.

After network node 101 performs step 152, node 101 sends to control node 105 a notification message 654 that contains information pertaining to the configuration update performed by node 101 in step 152 (e.g., message 654 includes a field containing an updated parameter value or a name-value-pair containing the name of a parameter and the updated parameter value) . Notification message 654 may be an existing standard message, such as “Nnrf_NFDiscovery_Request” disclosed in 3GPP TS 23.502 v 15.1.0 section 4.17.4, extended to include the information pertaining to the configuration update, or message 654 may be a new message. Based on notification message 654, control node 105 sends a message 658 to network node 102. Optionally, control node 105 may send to node 101 a response message 656 confirming the receipt of notification message 654. In some embodiments, based on notification message 654, control node 105 identifies a type of a service function implemented by network node 101 and sends the received information pertaining to the configuration update to a group of nodes implementing the service function of the identified type. In the embodiments shown on FIG. 6, node 102 is one of nodes in the group. If control node 105 determines that there is no other node implementing the service function of the identified type, control node 105 may not take any action or may send to network node 101 a message simply acknowledging the receipt of notification message 654.

Based on notification message 654 received from network node 101, control node 105 sends to network node 102 a message 658 (e.g., Update) including the information pertaining to the configuration update that was included in notification message 654. Based on message 658, network node 102 performs a configuration update (step 660) . Optionally, after network node 102 performs the configuration update, network node sends to control node 105 a message 662 indicating that network node 102 has performed its configuration update.

In some embodiments, features of the embodiments shown on FIG. 4 may be combined with features of the embodiments shown on FIG. 6. Specifically, in the modified embodiments of FIG. 6, control node 105 may determine the capability of network node 102 and select a group of nodes from a set of nodes implementing the service function of the identified type based on the capability of network node 102. Then, control node 105 sends identifiers of the group of nodes to network node 102 such that network node 102 can send the information about the configuration update performed at network node 102 to the group of nodes.

FIG. 7A is a flowchart illustrating a process 700 for performing a configuration update. Process 700 may begin in step 702.

Step 702 comprises a second network node (e.g., node 102) , which implements a service function of a first type (e.g., implements an AMF) , receiving a message (e.g., message 558) transmitted by control node 105, wherein the message provides an indication that a first network node (e.g., node 101) , which, in this example, also implements the service function of the first type, has performed a first configuration update.

Step 704 comprises the second network node, based on the message, transmitting to the first network node a request message (e.g., message 560) requesting information pertaining to the first configuration update.

Step 706 comprises, after transmitting the request message to the first network node, the second network node receiving an update message (e.g. message 562) transmitted by the first network node in response to the request message, wherein the update message comprises the information pertaining to the first configuration update.

In some embodiments, process 700 also includes the second network node performing a second configuration update based on the update message (e.g., message 562) transmitted by the first network node, and after the second network node performs the second configuration update, the second network node sends an acknowledgement message (e.g., message 568) to control node 105, wherein the acknowledgement message indicates that the second network node has performed the second configuration update.

FIG. 7B is a flowchart illustrating a process 750 for performing a configuration update. Process 750 may begin in step 752.

Step 752 comprises a first network node performing a first configuration update, wherein the first network node implements a service function of a first type.

Step 754 comprises the first network node sending to control node 105 a first message (e.g. message 454) providing an indication that the first network node has completed the first configuration update.

Step 756 comprises the first network node receiving a second message (e.g., message 456) transmitted by control node 105 in response to the first message, wherein the second message includes an identifier identifying a second network node (e.g., an IP address or name assigned to the second network node) . The second network node (e.g., node 102) , in this example, also implements the service function of the first type.

Step 758 comprises the first network node sending to the second network node a first update message (e.g., message 458) containing information pertaining to the first configuration update (e.g., containing at least one update configuration value) .

In some embodiments, process 750 also includes the second network node performing a second configuration update based on the information pertaining to the first configuration update included in the first update message, and after the second network node performs the second configuration update, the second network node sends an acknowledgement message to the first network node, wherein the acknowledgement message indicates that the second network node has performed the second configuration update.

In some embodiments, the first update message is configured to trigger the second network node to send to the control node a third message (e.g., message 474) requesting identifier information of at least one other network node that needs to perform a configuration update corresponding to the first configuration update performed by the first network node.

In some embodiments, process 750 further includes the first network node, based on receiving the second message transmitted by the control node, sending to a third network node (e.g., network nod 103) a second update message (e.g., message 464) containing the information pertaining to the update, where the second update message triggers the third network node to initiate a third configuration update. In some embodiments, the second message transmitted by the control node includes identifier information identifying the third network node, and the third network node implements the service function of the first type.

In some embodiments, process 750 further includes the first network node sending to the control node an acknowledgment (e.g., message 470) after the third network node has performed the third configuration update, wherein the acknowledgment message indicates that the third network node has performed the third configuration update and further indicates that the second network node has received the first update message.

FIG. 8A is a flowchart illustrating a process 800 for performing a configuration update. Process 800 may begin in step 802.

Step 802 comprises control node 105 receiving a first message (e.g. message 554 or message 654) transmitted by a first network node (e.g., node 101) .

Step 804 comprises control node 105, based on the first message, transmitting to a second network node (e.g., node 102) a second message (e.g., message 556 or message 658) , wherein the second message is configured to trigger the second network node to initiate a process for fetching from the first network node information pertaining to the configuration update, or the first message contains the information pertaining to the configuration update and the second message contains the information pertaining to the configuration update.

In some embodiments, process 800 further includes control node 105, based on receiving the first message and prior to sending the second message to the second network node, selecting one or more network nodes from a set of network nodes, wherein each network node included in the set of network nodes implements the service function of the first type, and the second network node is one of the one or more selected network nodes.

FIG. 8B is a flowchart illustrating a process 850 for performing a configuration update. Process 850 may begin in step 852.

Step 852 comprises control node 105 receiving a first message (e.g., message 454) transmitted by a first network node (e.g., node 101) , wherein the first message indicates that the first network node has performed a first configuration update.

Step 854 comprises control node 105, based on receiving the first message, sending a second message (e.g., message 456) to the first network node, wherein the second message identifies a second network node (e.g., node 102) and triggers the first network node to transmit to the second network node an update message (e.g., message 458) comprising information pertaining to the update, wherein the first network node implements a service function of a first type, and the second network node implements the service function of the first type.

In some embodiments, process 850 further includes control node 105 receiving a third message (e.g., message 474) transmitted by the second network node; and based on receiving the third message, sending a fourth message (e.g., message 476) to the second network node, wherein the fourth message identifies a third network node (104) and triggers the second network node to transmit to the third network node a second update message (e.g., message 478) comprising information pertaining to the first configuration update performed by the first network node.

In some embodiments, the first update message (458) is configured to trigger the second network node to send the third message to the control node.

In some embodiments, process 850 further includes control node 150, based on receiving the first message and prior to sending the second message to the first network node, selecting a group of one or more network nodes (e.g., nodes 102 and 103) from a set of network nodes (e.g., set 203) , wherein each network node included in the set of network nodes implements the service function of the first type, and the second message comprises, for each node included in the selected group, an identifier identifying the node.

In some embodiments, process 850 further includes control node 105 obtaining capability information pertaining to the first network node, wherein a number of network nodes in the group is selected based on the obtained capability information.

In some embodiments, process 850 further includes receiving an acknowledgement message (e.g., message 470) transmitted by the first network node, wherein the acknowledgement message indicates that the second network node has received the first update message.

FIG. 9 is a block diagram of an apparatus 900, according to some embodiments, for implementing any one or more of network nodes 101-104 or control node 105. As shown in FIG. 9, apparatus 900 may comprise: processing circuitry (PC) 902, which may include one or more processors (P) 955 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC) , field-programmable gate arrays (FPGAs) , and the like) , which processors may be co-located in a single housing or in a single data center or may be geographically distributed; a network interface 948 comprising a transmitter (Tx) 945 and a receiver (Rx) 947 for enabling apparatus 900 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 948 is connected; and a local storage unit (a. k. a., “data storage system” ) 908, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. In embodiments where PC 902 includes a programmable processor, a computer program product (CPP) 941 may be provided. CPP 941 includes a computer readable medium (CRM) 942 storing a computer program (CP) 943 comprising computer readable instructions (CRI) 944. CRM 942 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk) , optical media, memory devices (e.g., random access memory, flash memory) , and the like. In some embodiments, the CRI 944 of computer program 943 is configured such that when executed by PC 902, the CRI causes apparatus 900 to perform steps described herein (e.g., steps described herein with reference to the flow charts) . In other embodiments, apparatus 900 may be configured to perform steps described herein without the need for code. That is, for example, PC 902 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

While various embodiments of the present disclosure are described herein (including the appendices, if any) , it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

Claims

A method (700) performed by a second network node (102) that implements a service function of a first type, the method comprising:

the second network node (102) receiving (702) a message (558) transmitted by a control node (105) , wherein the message indicates that a first network node (101) has performed a first configuration update and further wherein the first network node (101) implements the service function of the first type;

the second network node (102) , based on the message (558) , transmitting (704) to the first network node (101) a request message (560) requesting information pertaining to the first configuration update; and

after transmitting the request message (560) to the first network node (101) , the second network node (102) receiving (706) an update message (562) transmitted by the first network node (101) in response to the request message (560) , wherein the update message (562) comprises the information pertaining to the first configuration update.
The method of claim 1, further comprising:

the second network node (102) performing a second configuration update based on the update message (562) transmitted by the first network node (101) ; and

after the second network node (102) performs the second configuration update, the second network node (102) sending an acknowledgement message (568) to the control node (105) , wherein the acknowledgement message (568) indicates that the second network node (102) has performed the second configuration update.
The method of claim 2, wherein

the information pertaining to the first configuration update comprises an updated parameter value, wherein the first configuration update performed by the first network node comprises the first network node replacing a first stored parameter value with the updated parameter value, and

the step of performing the second configuration update comprises replacing a second stored parameter value with the updated parameter value included in the update message (562) .
A method (750) performed by a first network node (101) that implements a service function of a first type, the method comprising:

performing a first configuration update (752) ;

after performing the first configuration update, sending (754) a first message (454) to a control node (105) ;

after sending the first message (454) to the control node (105) , receiving (756) a second message (456) transmitted by the control node (105) in response to the first message (454) , wherein the second message (456) includes identifier information identifying a second network node (102) to which the first network node (101) is to send information pertaining to the first configuration update, wherein the second network node (102) implements the service function of the first type; and

based on receiving the second message (456) from the control node (105) , sending (758) to the second network node (102) a first update message (458) comprising the information pertaining to the first configuration update, wherein the first update message (458) triggers the second network node (102) to initiate a second configuration update.
The method of claim 4, wherein the first update message (458) is configured to trigger the second network node (102) to send to the control node (105) a second request (474) requesting identifier information of at least one other network node that needs to perform a configuration update corresponding to the first configuration update performed by the first network node.
The method of claim 4 or 5, further comprising:

based on receiving the second message (456) transmitted by the control node (105) , sending to a third network node (103) a second update message (464) including the information pertaining to the update, the second update message triggering the third network node (103) to initiate a third configuration update, wherein

the second message (456) transmitted by the control node (105) includes identifier information identifying the third network node (103) , and

the third network node (103) implements the service function of the first type.
The method of claim 6, further comprising:

the first network node (101) sending to the control node (105) an acknowledgement message (470) after the third network node (103) has performed the third configuration update, wherein the acknowledgement message (470) indicates that the third network node (103) has performed the third configuration update and further indicates that the second network node (102) has received the first update message (458) .
The method of claim 6 or 7, wherein the second update message (464) is configured to not trigger the third network node (103) to send to the control node (105) any request message requesting identifier information of at least one other network node that needs to perform a configuration update corresponding to the first configuration update performed by the first network node.
A method (800) performed by a control node (105) , the method comprising:

receiving (802) a first message (554, 654) transmitted by a first network node (101) that implements a service function of a first type, wherein the first network node (101) transmitted the first message (554, 654) after performing a configuration update; and

based on receiving the first message (554, 654) , sending (804) a second message (558, 658) to a second network node (102) that implements the service function of the first type, wherein

the second message (558) is configured to trigger the second network node (102) to initiate a process for fetching from the first network node (101) information pertaining to the configuration update, or

the first message (654) contains the information pertaining to the configuration update and the second message (658) contains the information pertaining to the configuration update.
The method of claim 9, further comprising:

based on receiving the first message (554, 654) and prior to sending the second message (558, 658) to the second network node (102) , selecting one or more network nodes from a set of network nodes, wherein

each network node included in the set of network nodes implements the service function of the first type, and

the second network node (102) is one of the one or more selected network nodes.
The method of claim 9 or 10, wherein the second message (558) is configured to trigger the second network node (102) to initiate a process for fetching from the first network node (101) information pertaining to the configuration update.
The method of claim 9 or 10, wherein

the first message (654) includes the information pertaining to the configuration update, and

the second message (658) contains the information pertaining to the configuration update.
A method (850) performed by a control node (105) , the method comprising:

receiving (852) a first message (454) transmitted by a first network node (101) , wherein the first message (454) indicates that the first network node (101) has performed a first configuration update; and

based on receiving the first message (454) , sending (854) a second message (456) to the first network node (101) , wherein the second message (456) identifies a second network node (102) and triggers the first network node (101) to transmit to the second network node (102) a first update message (458) comprising information pertaining to the update, wherein

the first network node (101) implements a service function of a first type, and

the second network node (102) implements the service function of the first type.
The method of claim 13, further comprising:

receiving a third message (474) transmitted by the second network node (102) ; and

based on receiving the third message (474) , sending a fourth message (476) to the second network node (102) , wherein the fourth message (476) identifies a third network node (104) and triggers the second network node (102) to transmit to the third network node (104) a second update message (478) comprising information pertaining to the first configuration update performed by the first network node (101) , wherein

the third network node (104) implements the service function of the first type.
The method of claim 14, wherein the first update message (458) is configured to trigger the second network node (102) to send the third message (474) to the control node (105) .
The method of any one of claims 13-15, further comprising:

based on receiving the first message (454) and prior to sending the second message (456) to the first network node (101) , the control node (105) selecting a group of one or more network nodes (102 and 103) from a set of network nodes (203) , wherein

each network node included in the set of network nodes (203) implements the service function of the first type, and

the second message (456) identifies one or more network nodes in the group.
The method of claim 16, further comprising:

obtaining capability information pertaining to the first network node (101) , wherein a number of network nodes in the group is selected based on the obtained capability information.
The method of any one of claims 13-17, further comprising:

receiving an acknowledgement message (470) transmitted by the first network node (101) , wherein the acknowledgement message (470) indicates that the second network node (102) has received the first update message (458) .
The method of any one of the previous claims, wherein the first type of service function is a 3GPP network function.
The method of claim 19, wherein the 3GPP service function is any one of the network functions defined in 3GPP TS 23.501 v 15.3.0 section 4.2.2.
The method of claim 19 or 20, wherein the control node is a 3GPP NRF.
An apparatus (900) implementing a service function of a first type, adapted to:

receive (702) a message (558) transmitted by a control node (105) , wherein the message indicates that a first network node (101) has performed a first configuration update and further wherein the first network node (101) implements the service function of the first type;

based on the message (558) , transmit (704) to the first network node (101) a request message (560) requesting information pertaining to the first configuration update; and

after transmitting the request message (560) to the first network node (101) , receive (706) an update message (562) transmitted by the first network node (101) in response to the request message (560) , wherein the update message (562) comprises the information pertaining to the first configuration update.
An apparatus (900) implementing a service function of a first type, adapted to:

perform a first configuration update (752) ;

after performing the first configuration update, send (754) a first message (454) to a control node (105) ;

after sending the first message (454) to the control node (105) , receive (756) a second message (456) transmitted by the control node (105) in response to the first message (454) , wherein the second message (456) includes identifier information identifying a second network node (102) to which the apparatus (101) is to send information pertaining to the first configuration update, wherein the second network node (102) implements the service function of the first type; and

based on receiving the second message (456) from the control node (105) , send (758) to the second network node (102) a first update message (458) comprising the information pertaining to the first configuration update, wherein the first update message (458) triggers the second network node (102) to initiate a second configuration update.
An apparatus (900) adapted to:

receive (802) a first message (554, 654) transmitted by a first network node (101) that implements a service function of a first type, wherein the first network node (101) transmitted the first message (554, 654) after performing a configuration update; and

based on receiving the first message (554, 654) , send (804) a second message (558, 658) to a second network node (102) that implements the service function of the first type, wherein

the second message (558) is configured to trigger the second network node (102) to initiate a process for fetching from the first network node (101) information pertaining to the configuration update, or

the first message (654) contains the information pertaining to the configuration update and the second message (658) contains the information pertaining to the configuration update.
An apparatus (900) adapted to:

receive (852) a first message (454) transmitted by a first network node (101) , wherein the first message (454) indicates that the first network node (101) has performed a first configuration update; and

based on receiving the first message (454) , send (854) a second message (456) to the first network node (101) , wherein the second message (456) identifies a second network node (102) and triggers the first network node (101) to transmit to the second network node (102) a first update message (458) comprising information pertaining to the update, wherein

the first network node (101) implements a service function of a first type, and

the second network node (102) implements the service function of the first type.
Computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-21.
A carrier containing the computer program of claim 26, wherein the carrier is one of an electronic signal, optical signal, radio signal, or compute readable storage medium.