# US 2023/0054562 A1 · Method for Configuring Service Node, Service Node Pool Registrars, and System > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2023/0054562 A1 - Document ID: US20230054562A1 - Status: Published application - Kind: A1 - Application number: 17/975,340 - Filed: 2022-10-27 - Published: 2023-02-23 - Earliest claimed: 2013-07-05 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Hongguang Guan; Yang Wang; Feng Li - Web page: https://patentgrep.com/patent/US20230054562A1 ## CPC - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - G06F 3/0635: {by changing the path, e.g. traffic rerouting, path reconfiguration} - G06F 16/9537: Spatial or temporal dependent retrieval, e.g. spatiotemporal queries - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0897: by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities - H04L 41/12: Discovery or management of network topologies - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 41/5051: Service on demand, e.g. definition and deployment of services in real time - H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components - H04L 41/5058: {Service discovery by the service manager} - H04L 43/00: Arrangements for monitoring or testing data switching networks - H04L 43/0805: by checking availability - H04L 45/026: {Details of "hello" or keep-alive messages} - H04L 63/02: {for separating internal from external traffic, e.g. firewalls} - H04L 67/1001: for accessing one among a plurality of replicated servers - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 41/0894: Policy-based network configuration management - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 41/5096: {wherein the managed service relates to distributed or central networked applications} - H04L 43/0817: by checking functioning - H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route - H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV - H04L 63/1416: {Event detection, e.g. attack signature detection} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for configuring a service node, a service node pool registrar, and a system are provided. In certain embodiments, the method includes receiving a service node query request sent by a management configuration device. The service node query request includes a service requirement. The service requirement is from a user or caused by a network change. The method further includes searching a service node database, to obtain service node information that matches the service node query request. The method further includes sending the matching service node information to the management configuration device, causing the management configuration device to perform network and service configuration on the matching service node according to network topology information that has been obtained and the matching service node information. ## Claims ### Claim at position 1 -18. (canceled) ### Claim 19 A method, comprising: receiving a message of a first service node, wherein the message is a registration message or an update message or a deregistration message; forming a service node database in response to the message; receiving a service node query request sent by a management configuration device for the management configuration device to request a service node of a plurality of service nodes according to a service requirement, wherein the service node query request comprises the service requirement, wherein the service requirement is from a user or caused by a network change; searching, in response to the service node query request and according to the service requirement, the service node database to obtain service node information that matches the service node query request, and obtaining the service node information that matches the service node query request, wherein the service node information that matches the service node query request comprises one or more of: an identifier, location information, and status information of a service node that matches the service node query request, the service node that matches the service node query request being a second service node, the second service node being the first service node or another service node; and a service chain path that meets the service requirement; sending the service node information that matches the service node query request to the management configuration device for configuring the second service node according to the service node information that matches the service node query request. ### Claim 20 (depends on 19) The method according to claim 19, wherein receiving the service node query request sent by the management configuration device comprises: receiving an extended Aggregate Server Access Protocol (ASAP) message or a newly-defined message that is absent from ASAP. ### Claim 21 (depends on 19) The method according to claim 19, wherein receiving the message comprises receiving an extended Aggregate Server Access Protocol (ASAP) message, or a newly-defined message that is absent from ASAP. ### Claim 22 (depends on 19) The method according to claim 19, further comprising: performing keep-alive detection on the second service node; monitoring a status of the second service node; and performing troubleshooting according to the monitoring of the status. ### Claim 23 (depends on 19) The method according to claim 19, further comprising: synchronizing the message with the management configuration device. ### Claim 24 (depends on 23) The method according to claim 23, wherein synchronizing the message with the management configuration device comprises: extending an Aggregate Server Access Protocol (ASAP) message or defining a new message that is absent from ASAP; and synchronizing the extended ASAP message or the new message with the management configuration device. ### Claim 25 (depends on 19) The method according to claim 19, further comprising: receiving a new service node query request sent by the management configuration device, wherein the new service node query request is a service node relocation request and comprises a service node relocation constraint, wherein the service node relocation constraint is from a new user or caused by a new network change, wherein the new user is the user or another user or the new network change is the network change or another network change; searching the service node database to obtain new service node information that matches the new service node query request, wherein the new service node information that matches the new service node query request comprises an identifier and location information of a source node that meets the service node relocation constraint and an identifier and location information of a destination node that meets the service node relocation constraint; and sending the new service node information that matches the new service node query request to the management configuration device, causing the management configuration device to instruct, according to network topology information and the new service node information, the source node to perform a deregistration operation, and to activate and enable the destination node to serve the new user. ### Claim 26 (depends on 19) The method according to claim 19, wherein: the service node that matches the service node query request comprises a virtual node. ### Claim 27 (depends on 19) The method according to claim 19, wherein: the service node that matches the service node query request comprises one or more of the following: a virtual firewall (vFW), a virtual load balancer (vLB), a virtual wide area network optimization controller (vWoC), a virtual intrusion detection system (vIDS), a virtual intrusion protection system (vIPS), or a virtual network address translation (vNAT). ### Claim 28 (depends on 19) The method according to claim 19, wherein the service node information that matches the service node query request is used to configure the service node that matches the service node query request. ### Claim 29 A service node pool registrar, comprising: a transceiver, configured to: receive a message of a first service node, wherein the message is a registration message or an update message or a deregistration message; and receive a service node query request sent by a management configuration device for the management configuration device to request a service node of a plurality of service nodes according to a service requirement, wherein the service node query request comprises the service requirement, wherein the service requirement is from a user or caused by a network change; a processor; and a non-transitory memory storing program instructions executable by the processor, the program instructions including instructions to: form a service node database in response to the message; and search, in response to the service node query request and according to the service requirement, the service node database to obtain service node information that matches the service node query request, and obtain the service node information that matches the service node query request, wherein the service node information that matches the service node query request comprises one or more of: an identifier, location information, and status information of a service node that matches the service node query request, the service node that matches the service node query request being a second service node, the second service node being the first service node or another service node; and a service chain path that meets the service requirement; wherein the transceiver is further configured to send the service node information that matches the service node query request to the management configuration device for configuring the second service node according to the service node information that matches the service node query request. ### Claim 30 (depends on 29) The service node pool registrar according to claim 29, wherein the transceiver is configured to: receive the service node query request sent by the management configuration device by receiving an extended Aggregate Server Access Protocol (ASAP) message or a newly-defined message that is absent from ASAP. ### Claim 31 (depends on 29) The service node pool registrar according to claim 29, wherein the transceiver is configured to: receive the message by receiving an extended Aggregate Server Access Protocol (ASAP) message or a newly-defined message that is absent from ASAP. ### Claim 32 (depends on 29) The service node pool registrar according to claim 29, the program instructions further including instructions to: perform keep-alive detection on the second service node; monitor a status of the second service node; and perform troubleshooting according to the monitoring of the status. ### Claim 33 (depends on 29) The service node pool registrar according to claim 29, wherein the program instructions further include instructions to synchronize the message with the management configuration device. ### Claim 34 (depends on 33) The service node pool registrar according to claim 33, wherein synchronizing the message with the management configuration device comprises: extending an Aggregate Server Access Protocol (ASAP) message or defining a new message that is absent from ASAP; and synchronizing the extended ASAP message or the new message with the management configuration device. ### Claim 35 (depends on 29) The service node pool registrar according to claim 29, wherein: the service node query request is a request to relocate the service node that matches the service node query request, and comprises a constraint of relocation of the service node that matches the service node query request; and the service node information that matches the service node query request comprises an identifier and location information of a matching source node that meets the constraint and an identifier and location information of a matching destination node that meets the constraint. ### Claim 36 A management configuration device, comprising: a processor; and a non-transitory computer-readable storage medium storing a program executable by the processor, the program including instructions to: send, to a service node pool registrar, a service node query request to request a service node of a plurality of service nodes according to a service requirement, wherein the service node query request comprises the service requirement, wherein the service requirement is from a user or caused by a network change; receive, from the service node pool registrar in response to sending the service node query request, service node information that matches the service node query request, wherein the service node information that matches the service node query request comprises one or more of: an identifier, location information, and status information of a matching service node; and a service chain path that meets the service requirement; and perform network and service configuration on the matching service node according to the service node information that matches the service node query request. ### Claim 37 (depends on 36) The management configuration device according to claim 36, wherein the matching service node comprises one or more of the following: a virtual firewall (vFW), a virtual load balancer (vLB), a virtual wide area network optimization controller (vWoC), a virtual intrusion detection system (vIDS), a virtual intrusion protection system (vIPS), or a virtual network address translation (vNAT). ### Claim 38 (depends on 36) The management configuration device according to claim 36, wherein the service requirement comprises location information, tenant information, a function of the service node, and specifications and performance attributes of the service node.