CN117768924A - Network disaster recovery method, device, client and service control point - Google Patents

Network disaster recovery method, device, client and service control point Download PDF

Info

Publication number
CN117768924A
CN117768924A CN202211129958.1A CN202211129958A CN117768924A CN 117768924 A CN117768924 A CN 117768924A CN 202211129958 A CN202211129958 A CN 202211129958A CN 117768924 A CN117768924 A CN 117768924A
Authority
CN
China
Prior art keywords
information
group
scp
disaster recovery
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211129958.1A
Other languages
Chinese (zh)
Inventor
吴玲
宋月
都晨辉
窦志刚
贾思远
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN202211129958.1A priority Critical patent/CN117768924A/en
Publication of CN117768924A publication Critical patent/CN117768924A/en
Pending legal-status Critical Current

Links

Abstract

The invention provides a network disaster recovery method, a device, a client and a service control point, which relate to the technical field of core networks, wherein the network disaster recovery method is applied to the client and comprises the following steps: obtaining error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client; according to the scheme of the invention, the client can determine whether the SCP group is abnormal or the server group is abnormal according to the error response information, and the client adopts different network disaster recovery mechanisms to carry out network disaster recovery according to the SCP group abnormality or the server group abnormality.

Description

Network disaster recovery method, device, client and service control point
Technical Field
The present invention relates to the field of core networks, and in particular, to a network disaster recovery method, device, terminal, and service control point.
Background
The fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) is applied to thousands of industries, including various fields of industrial manufacturing, ports, production lines, smart cities, smart medical treatment, smart transportation and the like, and is different from consumer (to consumer, 2C) public business, and different business in different fields of enterprises (to business, 2B) has different reliability requirements, such as higher business continuity requirements of industrial control, banking transaction and the like.
Based on the current standard, the service control point (Service Control Point, SCP) returns a 5XX error, but according to the 5XX error, whether the SCP is abnormal or the Server is abnormal cannot be determined, and the processing of the client is inaccurate due to the fact that whether the SCP is abnormal or the Server is abnormal cannot be determined. For example, if the SCP is actually abnormal, the client may process according to Server unavailability (Server abnormality), which may lead to unreasonable processing.
Disclosure of Invention
The technical scheme of the invention aims to provide a network disaster recovery method, a device, a terminal and a service control point, which solve the problem that in the prior art, when an SCP returns error information to a client, whether the SCP is abnormal or a server is abnormal cannot be determined.
In order to solve the technical problems, the embodiment of the invention provides the following technical scheme:
in a first aspect, an embodiment of the present invention provides a network disaster recovery method, applied to a client, where the method includes:
obtaining error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client;
and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
Optionally, the acquiring the error response information includes:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client does not need to retry the first SCP group within a first preset duration, and the second information is further used for indicating that the client does not need to retry the server group within the first preset duration;
the network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
and modifying the routing mode between the client and the server group from a collimation routing mode to a direct routing mode.
Optionally, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
Requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group;
and accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, when the error response information includes second information for indicating that the server group is unavailable, performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
stopping sending the user request of the target user to the SCP; the target user is a user of the service end service in the non-registration state in the service end group;
and carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Optionally, the method further comprises:
and after a first preset time length, sending a user request of the target user to the SCP.
The network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, before the stopping sending the user request of the target user to the SCP, the method further comprises:
Transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
and determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
the third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the method further comprises:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
And carrying out service interaction with the first SCP group according to the notification information.
In a second aspect, an embodiment of the present invention further provides a network disaster recovery method, applied to a target service control point, where the method includes:
generating first indication information according to the link detection information, wherein the first indication information is used for indicating that a first Service Control Point (SCP) group is unavailable; the first SCP group is directly connected with the target service control point;
and adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
Optionally, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the first indication information includes:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
In a third aspect, an embodiment of the present invention further provides a client, including a processor and a transceiver:
the processor is used for acquiring error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client; and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
Optionally, the transceiver is specifically configured to:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client does not need to retry the first SCP group within a first preset duration, and the second information is further used for indicating that the client does not need to retry the server group within the first preset duration;
Wherein, the processor is specifically configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, the processor is specifically configured to:
and in the case that the error response information comprises first information for indicating that the first SCP group is not available, modifying the routing mode between the client and the service end group from a collimation routing mode to a direct routing mode.
Optionally, the processor is specifically configured to:
requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group under the condition that the error response information comprises first information for indicating that a first SCP group is unavailable;
and accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, the transceiver is specifically configured to:
stopping sending the user request of the target user to the SCP under the condition that the error response information comprises second information for indicating that the service end group is not available; the target user is a user of the service end service in the non-registration state in the service end group;
The processor is specifically configured to:
and carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Optionally, the transceiver is further specifically configured to:
after the first preset duration, sending a user request of the target user to the SCP;
wherein, the processor is specifically configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, before the transceiver stops sending the user request of the target user to the SCP, the transceiver is further specifically configured to:
transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
the processor is further specifically configured to:
and determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
The third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the transceiver is further configured to:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
the processor is further configured to:
and carrying out service interaction with the first SCP group according to the notification information.
In a fourth aspect, an embodiment of the present invention further provides a service control point, where the service control point is a target service control point, including a processor and a transceiver:
the processor is used for generating first indication information according to the link detection information, wherein the first indication information is used for indicating that a first service control point SCP group is unavailable; the first SCP group is directly connected with the target service control point; and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
Optionally, the processor is specifically configured to:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
In a fifth aspect, an embodiment of the present invention further provides a network disaster recovery device, applied to a client, where the device includes:
the information acquisition module is used for acquiring error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client;
and the first processing module is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information.
Optionally, the information acquisition module includes:
a first receiving unit, configured to receive the first information sent by the second SCP group, and/or receive the second information sent by the third SCP group;
Wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client is within a first preset duration without retrying the first SCP group, and the second information is further used for indicating that the client is within the first preset duration without retrying the server group;
wherein the first processing module comprises: a first processing unit;
and the first processing unit is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information within the first preset duration.
Optionally, the first processing module includes:
and the second processing unit is used for modifying the routing mode between the client and the service end group from a collimation routing mode to a direct routing mode in the case that the error response information comprises first information for indicating that the first SCP group is unavailable.
Optionally, the first processing module includes:
a third processing unit, configured to request service discovery from a network storage function NRF to obtain service information of a service end in the service end group if the error response information includes first information for indicating that the first SCP group is unavailable;
and the fourth processing unit is used for accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, the first processing module includes:
a fifth processing unit, configured to stop sending a user request of the target user to the SCP, if the error response information includes second information for indicating that the service-side group is unavailable; the target user is a user of the service end service in the non-registration state in the service end group;
and the sixth processing unit is used for carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Optionally, the first processing module further includes:
and the first sending unit is used for sending the user request of the target user to the SCP after the first preset time length.
Wherein the first processing module comprises: a first processing unit;
and the first processing unit is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information within the first preset duration.
Optionally, the first processing module further includes:
a second transmitting unit configured to transmit a request identifier to the NRF before the fifth processing unit stops transmitting the user request of the target user to the SCP; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
a first receiving unit, configured to receive NF template information of the network element of the server group sent by the NRF;
and the first determining unit is used for determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
The third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the apparatus further comprises:
an information sending module, configured to send subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
the information receiving module is used for receiving notification information sent by the NRF according to the subscription information after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state;
and the service interaction module is used for carrying out service interaction with the first SCP group according to the notification information.
In a sixth aspect, an embodiment of the present invention further provides a network disaster recovery device, applied to a target service control point, where the device includes:
the information generation module is used for generating first indication information according to the link detection information, wherein the first indication information is used for indicating that the SCP group of the first service control point is unavailable; the first SCP group is directly connected with the target service control point;
And the second processing module is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the first indication information.
Optionally, the second processing module includes:
a seventh processing unit, configured to directly connect with the target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
In a seventh aspect, an embodiment of the present invention further provides a client, including: a processor, a memory, and a program stored on the memory and executable on the processor, which when executed by the processor implements the network disaster recovery method according to any one of the first aspects.
In an eighth aspect, an embodiment of the present invention further provides a service control point, including: a processor, a memory, and a program stored on the memory and executable on the processor, the program implementing the network disaster recovery method according to any one of the second aspects when executed by the processor.
In a ninth aspect, an embodiment of the present invention further provides a readable storage medium, where a program is stored, where the program when executed by a processor implements the steps in the network disaster recovery method according to any one of the first aspect, or implements the network disaster recovery method according to any one of the second aspect.
At least one of the above technical solutions of the invention has the following beneficial effects:
the proposal of the invention obtains error response information, wherein the error response information comprises first information for indicating that a first SCP group is unavailable and/or second information for indicating that a server group is unavailable, namely, the client can determine whether the SCP group is abnormal or the server group is abnormal according to the error response information, and adopts a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing, namely, the client can also adopt different network disaster recovery mechanisms to carry out the network disaster recovery processing according to the SCP group abnormality or the server group abnormality.
Drawings
Fig. 1 is a schematic diagram of a network connection architecture corresponding to a mode B and a mode C provided by the present invention;
fig. 2 is a schematic diagram of a network connection architecture corresponding to the mode D provided in the present invention;
FIG. 3 is a diagram showing Server anomalies in mode D provided by the present invention;
FIG. 4 is a schematic diagram of a network connection architecture in an abnormal Server state according to the present invention;
fig. 5 is a flowchart of a network disaster recovery method applied to a client according to an embodiment of the present invention;
fig. 6 is a flowchart of a network disaster recovery method applied to a target service control point according to an embodiment of the present invention;
Fig. 7 is a schematic structural diagram of a client according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a service control point according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a network disaster recovery device applied to a client according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a network disaster recovery device applied to a target service control point according to an embodiment of the present invention;
FIG. 11 is a second schematic diagram of a client according to an embodiment of the present invention;
fig. 12 is a second schematic structural diagram of a service control point according to an embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
Before proceeding with the description of the specific embodiments of the present invention, the following description is first made:
the third generation partnership project (3rd Generation Partnership Project,3GPP) standard defines three service discovery and network connection architectures, including mode B, mode C, and mode D.
Mode B: the client requests service discovery from the network storage function NRF, and the client is directly connected to a Server (Server);
Mode C: the client requests service discovery from the NRF, and routes (via service control point (Service Control Point, SCP)) to the Server; the network connection architecture schematic diagrams corresponding to the mode B and the mode C are shown in fig. 1;
mode D: the client carries the service discovery parameter to request service from SCP, SCP discovers (standard inquiry) to NRF agent, SCP sends the request to Server; the network connection architecture corresponding to the mode D is shown in fig. 2.
In the mode D, when the Server is not available, the schematic diagram of the Server not available in the mode D is shown in fig. 3, and the SCP returns a response of some error 5XX to the client, where the client processes according to the exception.
In the prior art, if a Server is abnormal, referring to fig. 4, fig. 4 shows a schematic diagram of a network connection architecture in a Server abnormal state, a client carries a service discovery parameter to request a service from an SCP, the SCP discovers (standard query) a proxy of a network storage function (Network Repository Function, NRF), the SCP sends the request to the Server, and because the SCP acts as a proxy, the client cannot determine which Server is unavailable and which users can use the servers, so the client receives a new user request and sends the new user request to the SCP, and the SCP refuses the request after judging that the Server is unavailable, so each user request is refused after passing through a plurality of clients, the SCP and even a plurality of SCPs, the invalid signaling of the clients and the SCP is large, and the control plane processing delay is increased.
The SCP judges that the Server is abnormal (the Server is not available) and is only effective for the current user, after the client receives the user request of the new user, the Server is uncertain which servers serve the new user or the user request of the new user needs to be sent to the SCP, and a large amount of invalid signaling is generated between the client and the SCP.
Section in existing standard 3gpp TS 29.500: the various error response messages defined in Table 5.2.7.4-1:Protocol and application errors generated by the SCP/SEPP (protocol and application error generated by SCP or secure edge protection proxy (Security Edge Protection Proxies, SEPP)) represent either the current Server exception or the current Network Function (NF) exception and instruct the client to immediately attempt other servers, and in the event of a specified SCP Group (SCP Group) exception or a specified Server exception, no further invalidation attempt should be indicated by the client.
TABLE 1 error response information
In the existing standard, no code is defined for exception recovery, and relevant sections of the existing standard are as follows:
NF SERVICE users (recipients as cause codes) should stop sending subsequent requests to address resource contexts in the NF instance of the producer (for nf_failure) or NF SERVICE instance (for NF __ service_failure) to avoid large scale refusal. The NF service consumer may reselect an alternative NF service producer, such as a binding indication to use the resource context, according to the rules of clause 3GPP TS 23.527[38, clause 6.5. NF SERVICE consumers determine when and if NF producers are again available is implementation-specific, e.g., when no other alternatives are available, or when a local configuration timer expires (The NF SERVICE consumer (as receiver of the cause code) should stop sending subsequent requests addressing the resource contexts in the producer's NF instance (for nf_face) or NF SERVICE instance (for nf_service_face) to active media alternatives.the NF SERVICE consumer may reselect an alternative NF SERVICE producer as specified clause 6.5 of 3GPP TS 23.527[38], e.g.using the Binding Indication of resource context.it is implementation specific for the NF SERVICE consumer to determine when and whether the NF producer becomes available again, e.g.w there is no other alternative available or at expiry of a local configured timer).
In order to solve the problem that in the prior art, when an SCP returns error information to a client, whether the SCP is abnormal or a server is abnormal cannot be determined, the embodiment of the invention provides a network disaster recovery method, a device, a terminal and a service control point.
As shown in fig. 5, an embodiment of the present invention provides a network disaster recovery method, applied to a client, where the method includes:
step 501: obtaining error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server providing service to the client.
In this step, the client obtains error response information, where the error response information includes first information for indicating that the first SCP group is unavailable and/or second information for indicating that the service end group is unavailable, that is, the client may determine whether the first SCP group is unavailable or the service end group is unavailable according to the error response information. The first SCP group is any SCP group which is not directly connected with the client, namely the first SCP group comprises SCPs which are not directly connected with the client, and the server group is used for providing services for the client.
Alternatively, the error response information may be an error response code, where the error response code represents whether the first SCP group is unavailable or the service end group is unavailable.
Step 502: and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
In this step, after determining whether the first SCP group is unavailable or the service end group is unavailable according to the error response information, different network disaster recovery mechanisms can be correspondingly adopted to perform network disaster recovery processing.
Optionally, the acquiring the error response information includes:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
In case the error response information comprises first information representing that the concatenated SCP (first SCP group) is not available for some reason, said first information is generated by a second SCP group directly connected to the first SCP group and is sent to the client via a fourth SCP group between the second SCP group and the client, wherein the fourth SCP group comprises the SCP directly connected to the client, and may also comprise the SCP not directly connected to the client.
In case the error response information comprises second information, which represents that the service end providing the service to the client is for some reason not available, said second information is generated by a third SCP group directly connected to the service end group providing the service to the client and is sent to the client via a fifth SCP group between the third SCP group and the client, wherein the fifth SCP group comprises SCPs directly connected to the client and may also comprise SCPs not directly connected to the client.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client is within a first preset duration without retrying the first SCP group, and the second information is further used for indicating that the client is within the first preset duration without retrying the server group;
The network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
In the embodiment of the invention, a first preset time length (Retry-timer) is also defined, and the first preset time length is the time length when the client adopts the network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
In particular, in case the error response information includes the first information, the error response information may further include a hypertext transfer protocol (HyperText Transfer Protocol, HTTP) status code corresponding to the first information, and/or the first information is further used to indicate that the client does not need to retry whether the first SCP group is available within the first preset duration.
If the error response information includes the second information, the method may further include an HTTP status code corresponding to the second information, and/or the second information is further used to indicate whether the client does not need to retry whether the server group is available within the first preset duration.
Illustratively, the following sections are in the 3gpp TS 29.500 standard: table 5.2.7.4-1: protocol and application errors (Protocol and application errors generated by the SCP/SEPP) generated by the SCP or the secure edge protection proxy (Security Edge Protection Proxies, SEPP) are added with an error response code as shown in table 2 below to indicate whether the first SCP group is unavailable or the service side group is unavailable, and the client does not need to Retry within a first preset time period (Retry-timer), and after the Retry-timer time has arrived, the client can try again.
TABLE 2 error message codes
In table 2 above, "SCP Group are Unavailable" is first information and "Server Group are Unavailable" is second information.
The error response information includes an HTTP status code corresponding to the first information and an HTTP status code corresponding to the second information may represent a web hypertext server transport protocol response status.
The first information is also used for indicating whether the client does not need to retry the first SCP group in the first preset time period, and the second information is also used for indicating whether the client does not need to retry the service end group in the first preset time period, so that the client can be prevented from always trying whether the first SCP group or the service end is available, and resource consumption is reduced.
Optionally, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
and modifying the routing mode between the client and the server group from a collimation routing mode to a direct routing mode.
In the embodiment of the present invention, the network disaster recovery processing measure after the client receives the error response information of "SCP Group are Unavailable (first information)" defined in the above table 2 is defined in the 3gpp TS 23.527 or 3gpp TS 23.501 standard. The client receives "SCP Group are Unavailable" that the cascaded SCPs are not available for some reason, but not that the Server is not available, and that the user traffic should not be affected. In this case, the following network disaster recovery process should be performed:
In the case that the service is found to be in the Mode C (Mode C) as shown in fig. 2, the connection Mode between the client and the server is changed from the collimated routing Mode to the direct routing Mode, so that the client and the server can perform service interaction normally.
Optionally, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group;
and accessing the server through a direct-connection routing mode according to the service information of the server.
In the embodiment of the present invention, the network disaster recovery processing measure after the client receives the error response information of "SCP Group are Unavailable (first information)" defined in the above table 2 is defined in the 3gpp TS 23.527 or 3gpp TS 23.501 standard. The client receives "SCP Group are Unavailable" that the cascaded SCPs are not available for some reason, but not that the Server is not available, and that the user traffic should not be affected. In this case, the following network disaster recovery process should be performed:
in the Mode D (Mode D) shown in fig. 3, the client modifies the service discovery into the Mode B (Mode B), that is, the client requests the service discovery from the NRF, obtains the service information of the server, and then directly routes the service information with the server, that is, accesses the server in a direct route manner, so that the client and the server normally perform service interaction.
Optionally, when the error response information includes second information for indicating that the server group is unavailable, performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
stopping sending the user request of the target user to the SCP; the target user is a user of the service end service in the non-registration state in the service end group;
and carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
In the embodiment of the present invention, the processing measure after the client receives the error response information of "Server Group are Unavailable (second information)" as defined in the above table 2 is defined in the 3gpp TS 23.527 or 3gpp TS 23.501 standard. The client receives "Server Group are Unavailable", representing that the Server is not available for some reason, and not the SCP, in which case the Server is not already available, although the SCP is available, and it is not necessary to send the user request of each user of the abnormal Server service to the SCP for processing. In this case, the following network disaster recovery process should be performed:
in the case that the service is found to be in the Mode C (Mode C) as shown in fig. 2, the client does not send the user request (including the new user request) of the user (target user) served by the abnormal Server Group (Server Group) to the SCP any more, and the client performs the local disaster recovery policy processing, that is, performs the network disaster recovery processing according to the disaster recovery policy preset in the client. The target user is the user of the service end service in the non-registration state.
In the embodiment of the invention, under the condition that the collimation networking is available to the SCP, but the service end group is unavailable, the client side does not send the user request (including the new user request) of the target user to the SCP, namely, the client side does not perform invalid signaling forwarding with the SCP any more, and the processing time delay of the control panel signaling is reduced.
Further, the method further comprises:
after a first preset time length, sending a user request of the target user to the SCP;
the network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
And in a first preset time period (Retry-timer), adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing, wherein in the first preset time period, the client side does not try to send the user request of the target user to the SCP any more until the first preset time period is up, and trying to send the user request of the target user (including the user request of the new user) to the SCP again.
Optionally, before the stopping sending the user request of the target user to the SCP, the method further comprises:
Transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
and determining the target user according to the NF template information of the non-registered server.
In the embodiment of the present invention, the processing measure after the client receives the error response information of "Server Group are Unavailable (second information)" as defined in the above table 2 is defined in the 3gpp TS 23.527 or 3gpp TS 23.501 standard. The client receives "Server Group are Unavailable", representing that the Server is not available for some reason, and not the SCP, in which case the Server is not already available, although the SCP is available, and it is not necessary to send the user request of each user of the abnormal Server service to the SCP for processing. In this case, the following network disaster recovery process should be performed:
in the case that the service discovery is in the Mode D (Mode D) as shown in fig. 3, the client requests to the NRF to discover network element NF template (Profile) information of an abnormal Server Group (Server Group), where the NF Profile information includes NF Profile information of a service end in a non-registration state, and the client receives the NF Profile information of the network element NF of the Server Group sent by the NRF, and determines a target user (including a new user) according to the NF Profile information of the service end in the non-registration state. The client processes according to the local disaster recovery strategy, namely, network disaster recovery is performed according to the disaster recovery strategy preset in the client.
And (3) in a first preset time period (Retry-timer), carrying out network disaster recovery processing according to the error response information, wherein in the first preset time period, the client side does not try to send the user request (including the user request of the new user) of the target user to the SCP any more until the first preset time period is up, and try to send the user request (including the user request of the new user) of the target user to the SCP again.
When the client requests to find NF Profile information of the non-registered Server to the NRF, the NRF carries a newly added request identifier in a discovery parameter of the NRF discovery Server, the request identifier comprises third information, and the NRF represents NF template information of the non-registered Server to be found by the NRF according to the third information.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information; the third information indicates NF template information of unregistered servers according to NF configuration information of the server group; the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Illustratively, the following sections are in the 3gpp TS 29.510 standard: table 6.2.3.2.3.1-1: the uniform resource identifier (Uniform Resource Identifier, URI) supported by the method on this resource queries the parameter (URI query parameters supported by the GET method on this resource), adds a request identifier, as shown in table 3 below, and implements NF Profile information that the client requests to find an abnormal Server Group from the NRF according to the request identifier.
Table 3 request identification
Optionally, the method further comprises:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
and carrying out service interaction with the first SCP group according to the notification information.
In the embodiment of the invention, a recovery mechanism after an abnormality occurs is defined, a client sends a subscription information subscription state change notice to an NRF, specifically, the subscription information is used for subscribing the state of a service end group (including the state of a service end in a non-registration state) and/or the state of a first SCP group, after the service end in the non-registration state is available and/or the first SCP group recovers the available state, the client receives the notice information sent by the NRF, releases the network disaster tolerance state according to the notice information, and resumes sending the service to the SCP, namely, carries out service interaction with the first SCP group.
In the network disaster recovery method provided by the embodiment of the invention, under the collimation networking, the client can acquire the error response information and judge whether the cascaded SCP is unavailable or the Server is unavailable, so that different network disaster recovery mechanisms are adopted, and under the condition that the SCP is available and the Server is unavailable, the client does not perform invalid signaling forwarding with the SCP any more, and the control plane signaling processing time delay is reduced.
As shown in fig. 6, an embodiment of the present invention further provides a network disaster recovery method, applied to a target service control point, where the method includes:
step 601: generating first indication information according to the link detection information; the first indication information is used for indicating that the SCP group of the first service control point is unavailable; the first SCP group is directly connected with the target service control point.
It should be noted that, the network disaster recovery method in the embodiment of the present invention may be executed by a target SCP group including a plurality of target service control points SCPs, where the target SCP group may be directly connected or not directly connected to the client, and the SCP group may be directly connected or not directly connected to the server.
In this step, the target SCP generates first indication information for indicating that the first SCP group is unavailable according to the link detection information, and the first indication information does not need to be returned to the client, i.e. the target SCP does not return an error response to the client. Wherein the first SCP group is directly connected with the target SCP.
It should be further noted that the target SCP may also determine whether the first SCP group is available according to a heartbeat mechanism or the like.
Step 602: and adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
In the step, after the target SCP generates the first indication information, an error response is not returned to the client, and the target SCP adopts a corresponding network disaster recovery mechanism to carry out network disaster recovery processing.
Optionally, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the first indication information includes:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
After the target SCP generates the first indication information, the specific mode of carrying out network disaster recovery processing comprises at least one of the following steps:
the target SCP is directly connected with the service end group, namely the target SCP is directly connected with the access service end;
the target SCP skips the first SCP group and is directly connected with a second SCP group, wherein the second SCP group is directly connected with the first SCP group.
As shown in fig. 7, the embodiment of the present invention further provides a client, including a processor 701 and a transceiver 702:
the processor 701 is configured to obtain error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client; and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
Optionally, the transceiver 702 is specifically configured to:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client is within a first preset duration without retrying the first SCP group, and the second information is further used for indicating that the client is within the first preset duration without retrying the server group;
Wherein, the processor 701 is specifically configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, the processor 701 is specifically configured to:
and in the case that the error response information comprises first information for indicating that the first SCP group is not available, modifying the routing mode between the client and the service end group from a collimation routing mode to a direct routing mode.
Optionally, the processor 701 is specifically configured to:
requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group under the condition that the error response information comprises first information for indicating that a first SCP group is unavailable;
and accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, the transceiver 702 is specifically configured to:
stopping sending the user request of the target user to the SCP under the condition that the error response information comprises second information for indicating that the service end group is not available; the target user is a user of the service end service in the non-registration state in the service end group;
The processor 701 is specifically configured to:
and carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Optionally, the transceiver 702 is further specifically configured to:
after the first preset duration, sending a user request of the target user to the SCP;
wherein, the processor 701 is specifically configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, before the transceiver 702 stops sending the user request of the target user to the SCP, the transceiver 702 is further specifically configured to:
transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
the processor 701 is further specifically configured to:
and determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
The third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the transceiver 702 is further configured to:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
the processor 701 is further configured to:
and carrying out service interaction with the first SCP group according to the notification information.
It should be noted that, if the client according to the embodiment of the present invention is a client capable of executing the network disaster recovery method applied to the client, all embodiments of the network disaster recovery method applied to the client are applicable to the client, and the same or similar technical effects can be achieved.
As shown in fig. 8, the embodiment of the present invention further provides a service control point, where the service control point is a target service control point, and includes a processor 801 and a transceiver 802:
The processor 801 is configured to generate first indication information according to the link detection information, where the first indication information is used to indicate that the first service control point SCP group is unavailable; the first SCP group is directly connected with the target service control point; and adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
Optionally, the processor 801 is specifically configured to:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
It should be noted that, the service control point in the embodiment of the present invention is a service control point capable of executing the above-mentioned network disaster recovery method applied to the target service control point, so all embodiments of the above-mentioned network disaster recovery method applied to the target service control point are applicable to the service control point, and the same or similar technical effects can be achieved.
As shown in fig. 9, an embodiment of the present invention further provides a network disaster recovery device, applied to a client, where the device includes:
An information acquisition module 901, configured to acquire error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client;
the first processing module 902 is configured to perform network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information.
Optionally, the information obtaining module 901 includes:
a first receiving unit, configured to receive the first information sent by the second SCP group, and/or receive the second information sent by the third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client is within a first preset duration without retrying the first SCP group, and the second information is further used for indicating that the client is within the first preset duration without retrying the server group;
wherein the first processing module 902 includes: a first processing unit;
and the first processing unit is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information within the first preset duration.
Optionally, the first processing module 902 includes:
and the second processing unit is used for modifying the routing mode between the client and the service end group from a collimation routing mode to a direct routing mode in the case that the error response information comprises first information for indicating that the first SCP group is unavailable.
Optionally, the first processing module 902 includes:
a third processing unit, configured to request service discovery from a network storage function NRF to obtain service information of a service end in the service end group if the error response information includes first information for indicating that the first SCP group is unavailable;
And the fourth processing unit is used for accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, the first processing module 902 includes:
a fifth processing unit, configured to stop sending a user request of the target user to the SCP, if the error response information includes second information for indicating that the service-side group is unavailable; the target user is a user of the service end service in the non-registration state in the service end group;
and the sixth processing unit is used for carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Optionally, the first processing module 902 further includes:
and the first sending unit is used for sending the user request of the target user to the SCP after the first preset time length.
Wherein the first processing module 902 includes: a first processing unit;
and the first processing unit is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information within the first preset duration.
Optionally, the first processing module 906 further includes:
a second transmitting unit configured to transmit a request identifier to the NRF before the fifth processing unit stops transmitting the user request of the target user to the SCP; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
A first receiving unit, configured to receive NF template information of the network element of the server group sent by the NRF;
and the first determining unit is used for determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
the third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the apparatus further comprises:
an information sending module, configured to send subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
the information receiving module is used for receiving notification information sent by the NRF according to the subscription information after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state;
and the service interaction module is used for carrying out service interaction with the first SCP group according to the notification information.
It should be noted that, the network disaster recovery device applied to the client according to the embodiment of the present invention is a device capable of executing the network disaster recovery method applied to the client, so all embodiments of the network disaster recovery method applied to the client are applicable to the device, and the same or similar technical effects can be achieved.
As shown in fig. 10, an embodiment of the present invention further provides a network disaster recovery device, applied to a target service control point, where the device includes:
an information generating module 1001, configured to generate first indication information according to the link detection information, where the first indication information is used to indicate that the first service control point SCP group is unavailable; the first SCP group is directly connected with the target service control point;
and a second processing module 1002, configured to perform network disaster recovery processing by using a network disaster recovery mechanism corresponding to the first indication information.
Optionally, the second processing module 1002 includes:
a seventh processing unit, configured to directly connect with the target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
It should be noted that, the network disaster recovery device applied to the target service control point according to the embodiment of the present invention is a device capable of executing the network disaster recovery method applied to the target service control point, so all embodiments of the network disaster recovery method applied to the target service control point are applicable to the device, and the same or similar technical effects can be achieved.
As shown in fig. 11, an embodiment of the present invention further provides a client, including: a processor 1101; and a memory 1103 connected to the processor 1101 through a bus interface 1102, the memory 1103 being configured to store programs and data used by the processor 1101 when executing operations, the processor 1101 calling and executing the programs and data stored in the memory 1103.
Wherein the transceiver 1104 is connected to the bus interface 1102 for receiving and transmitting data under the control of the processor 1101, specifically, the processor 1101 is configured to read a program in the memory 1103, and the processor 1101 performs the following procedures:
obtaining error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client; and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
Optionally, the transceiver 1104 is configured to:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
the second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
Optionally, the error response information further includes a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client is within a first preset duration without retrying the first SCP group, and the second information is further used for indicating that the client is within the first preset duration without retrying the server group;
Wherein the processor 1101 is configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, the processor 1101 is configured to:
and in the case that the error response information comprises first information for indicating that the first SCP group is not available, modifying the routing mode between the client and the service end group from a collimation routing mode to a direct routing mode.
Optionally, the processor 1101 is configured to:
requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group under the condition that the error response information comprises first information for indicating that a first SCP group is unavailable;
and accessing the server through a direct-connection routing mode according to the service information of the server.
Optionally, the transceiver 1104 is configured to:
stopping sending the user request of the target user to the SCP under the condition that the error response information comprises second information for indicating that the service end group is not available; the target user is a user of the service end service in the non-registration state in the service end group;
the processor 1101 is configured to:
And carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
Alternatively, the process may be carried out in a single-stage,
the transceiver 1104 is further configured to:
after the first preset duration, sending a user request of the target user to the SCP;
wherein the processor 1101 is configured to:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
Optionally, before the transceiver 1104 stops sending the user request of the target user to the SCP, the transceiver 1104 is further configured to:
transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
the processor 1101 is further configured to:
and determining the target user according to the NF template information of the non-registered server.
Optionally, the request identifier further includes a data type corresponding to the third information and a radix corresponding to the third information;
The third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
Optionally, the transceiver 1104 is further configured to:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
the processor 1101 is further configured to:
and carrying out service interaction with the first SCP group according to the notification information.
Where in FIG. 11, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of the one or more processors, as represented by processor 1101, and the memory, as represented by memory 1103, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides a user interface 1105. The transceiver 1104 may be a plurality of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing the operations.
As shown in fig. 12, an embodiment of the present invention further provides a service control point, where the service control point is a target service control point, including: a processor 1201; and a memory 1203 connected to the processor 1201 through a bus interface 1202, the memory 1203 being configured to store programs and data used by the processor 1201 when performing operations, the processor 1201 calling and executing the programs and data stored in the memory 1203.
Wherein the transceiver 1204 is connected to the bus interface 1202 for receiving and transmitting data under the control of the processor 1201, specifically, the processor 1201 is configured to read the program in the memory 1203, and the processor 1201 performs the following procedures:
generating first indication information according to the link detection information, wherein the first indication information is used for indicating that a first Service Control Point (SCP) group is unavailable; the first SCP group is directly connected with the target service control point; and adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
Optionally, the processor 1201 is configured to:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
The second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
Wherein in fig. 12, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by the processor 1201 and various circuits of memory represented by the memory 1203, are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides a user interface 1205. The transceiver 1204 may be a plurality of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1201 is responsible for managing the bus architecture and general processing, and the memory 1203 may store data used by the processor 1201 in performing operations.
In addition, a specific embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, where the program when executed by a processor implements the steps in the network disaster recovery method applied to a client as set forth in any one of the above, or implements the steps in the network disaster recovery method applied to a target service control point as set forth in any one of the above.
In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform part of the steps of the transceiving method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and changes can be made without departing from the principles of the present invention, and such modifications and changes should also be considered as being within the scope of the present invention.

Claims (19)

1. A network disaster recovery method, applied to a client, the method comprising:
obtaining error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client;
and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
2. The network disaster recovery method of claim 1, wherein the obtaining error response information comprises:
receiving the first information sent by a second SCP group and/or receiving the second information sent by a third SCP group;
wherein the first information is generated by the second SCP group and sent by the second SCP group to the client via a fourth SCP group; the second SCP group is directly connected with the first SCP group; the fourth SCP group is positioned between the client and the second SCP group;
The second information is generated by the third SCP group and sent by the third SCP group to the client via a fifth SCP group; the third SCP group is directly connected with the server group; the fifth SCP group is located between the client and the third SCP group.
3. The network disaster recovery method of claim 1, wherein the error response information further comprises a hypertext transfer protocol HTTP status code corresponding to the first information and/or an HTTP status code corresponding to the second information;
and/or the number of the groups of groups,
the first information is further used for indicating that the client does not need to retry the first SCP group within a first preset duration, and the second information is further used for indicating that the client does not need to retry the server group within the first preset duration;
the network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
4. The network disaster recovery method according to claim 1, wherein, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
And modifying the routing mode between the client and the server group from a collimation routing mode to a direct routing mode.
5. The network disaster recovery method according to claim 1, wherein, in the case that the error response information includes first information for indicating that the first SCP group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
requesting service discovery from a network storage function NRF to obtain service information of a service end in the service end group;
and accessing the server through a direct-connection routing mode according to the service information of the server.
6. The network disaster recovery method according to claim 1, wherein, in the case that the error response information includes second information for indicating that the server group is unavailable, the performing network disaster recovery processing by using a network disaster recovery mechanism corresponding to the error response information includes:
stopping sending the user request of the target user to the SCP; the target user is a user of the service end service in the non-registration state in the service end group;
and carrying out network disaster recovery processing according to a disaster recovery strategy preset in the client.
7. The network disaster recovery method of claim 6, further comprising:
after a first preset time length, sending a user request of the target user to the SCP;
the network disaster recovery processing by adopting the network disaster recovery mechanism corresponding to the error response information comprises the following steps:
and in the first preset time period, adopting a network disaster recovery mechanism corresponding to the error response information to perform network disaster recovery processing.
8. The network disaster recovery method of claim 6 wherein before said stopping sending the user request of the target user to the SCP, said method further comprises:
transmitting a request identifier to the NRF; the request identifier comprises third information, wherein the third information is used for indicating the NRF to send network element NF template information of the server group to the client; the NF template information of the server side group comprises NF template information of a non-registered server side;
receiving network element NF template information of the server group sent by the NRF;
and determining the target user according to the NF template information of the non-registered server.
9. The network disaster recovery method of claim 8 wherein the request identification further comprises a data type corresponding to the third information and a radix corresponding to the third information;
The third information indicates NF template information of unregistered servers according to NF configuration information of the server group;
the NF configuration information of the server group comprises the NF configuration information of the suspended server and the NF configuration information of the undiscovered server.
10. The network disaster recovery method of claim 1, further comprising:
sending subscription information to the NRF; the subscription information is used for subscribing the available state of the server side group and/or the available state of the first SCP group; the server group comprises a non-registered server;
after the service end in the unregistered state is in an available state and/or the first SCP group is in an available state, receiving notification information sent by the NRF according to the subscription information;
and carrying out service interaction with the first SCP group according to the notification information.
11. A network disaster recovery method, applied to a target service control point, the method comprising:
generating first indication information according to the link detection information; the first indication information is used for indicating that the SCP group of the first service control point is unavailable; the first SCP group is directly connected with the target service control point;
And adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
12. The network disaster recovery method according to claim 11, wherein the performing network disaster recovery processing by using the network disaster recovery mechanism corresponding to the first indication information includes:
directly connecting with a target network node;
wherein, the target network node is a server group or a second SCP group;
the second SCP group is directly connected with the first SCP group;
the server group comprises a server for providing service for the client; and the target SCP is directly connected or not directly connected with the client.
13. A client comprising a processor and a transceiver, characterized by:
the processor is used for acquiring error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client; and adopting a network disaster recovery mechanism corresponding to the error response information to carry out network disaster recovery processing.
14. A service control point, the service control point being a target service control point, comprising a processor and a transceiver, characterized in that:
The processor is used for generating first indication information according to the link detection information; the first indication information is used for indicating that the SCP group of the first service control point is unavailable; the first SCP group is directly connected with the target service control point; and adopting a network disaster recovery mechanism corresponding to the first indication information to carry out network disaster recovery processing.
15. A network disaster recovery device, applied to a client, the device comprising:
the information acquisition module is used for acquiring error response information; the error response information comprises first information for indicating that the SCP group of the first service control point is unavailable and/or second information for indicating that the service end group is unavailable; the first SCP group comprises SCPs which are not directly connected with the client; the server group comprises a server for providing service for the client;
and the first processing module is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the error response information.
16. A network disaster recovery device, for application to a target service control point, the device comprising:
the information generation module is used for generating first indication information according to the link detection information; the first indication information is used for indicating that the SCP group of the first service control point is unavailable; the first SCP group is directly connected with the target service control point;
And the second processing module is used for carrying out network disaster recovery processing by adopting a network disaster recovery mechanism corresponding to the first indication information.
17. A client, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the network disaster recovery method according to any one of claims 1 to 10.
18. A service control point, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the network disaster recovery method according to claim 11 or 12.
19. A readable storage medium, wherein a program is stored on the readable storage medium, which when executed by a processor, implements the steps of the network disaster recovery method according to any one of claims 1 to 10, or implements the network disaster recovery method according to claim 11 or 12.
CN202211129958.1A 2022-09-16 2022-09-16 Network disaster recovery method, device, client and service control point Pending CN117768924A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211129958.1A CN117768924A (en) 2022-09-16 2022-09-16 Network disaster recovery method, device, client and service control point

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211129958.1A CN117768924A (en) 2022-09-16 2022-09-16 Network disaster recovery method, device, client and service control point

Publications (1)

Publication Number Publication Date
CN117768924A true CN117768924A (en) 2024-03-26

Family

ID=90310954

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211129958.1A Pending CN117768924A (en) 2022-09-16 2022-09-16 Network disaster recovery method, device, client and service control point

Country Status (1)

Country Link
CN (1) CN117768924A (en)

Similar Documents

Publication Publication Date Title
CN109636427B (en) Business processing method, device, medium and electronic equipment based on block chain system
US11411897B2 (en) Communication method and communication apparatus for message queue telemetry transport
US7929419B2 (en) Methods, systems, and computer program products for inhibiting message traffic to an unavailable terminating SIP server
US20100205298A1 (en) Method, system and computer program to enable semantic mediation for SIP events through support of dynamically binding to and changing of application semantics of SIP events
EP3060018B1 (en) Registration method and system for common service entity
CN102177690B (en) Methods, systems, and computer readable media for providing sedation service in a telecommunications network
CN107404512B (en) Resource subscription method, resource subscription device and resource subscription system
CN113225700B9 (en) Notification in SBA sent with indirect communication
CN111478955A (en) Microservice registration method, system, apparatus and computer readable storage medium
CN114024826B (en) Application multi-active system based on service grid technology and used in distributed ESB scene
CN113746928A (en) Cross-cloud service calling method, device and system
CN1647482B (en) System and method for network communication management
EP1575216B1 (en) Method to invoke service among devices in home network
US20040172441A1 (en) Systems and methods for defining conversation information for web-services
JP2002368781A (en) User location management domain name conversion system
CN113424608B (en) Entity for providing external services to a network
CN110768818B (en) Network management method and device
WO2019201111A1 (en) Information processing method, apparatus and device, and computer-readable storage medium
CN117768924A (en) Network disaster recovery method, device, client and service control point
WO2022083281A1 (en) Message transmission method and system, electronic device, and storage medium
US20090067600A1 (en) Method And Arrangement For Services Running On Service Execution Platform
CN114979985A (en) Indirect communication message transmission method, system and gateway equipment
CN102843255B (en) Peer-to-peer based network management method and proxy selection server
Pallickara et al. An analysis of reliable delivery specifications for Web Services
US8046419B2 (en) Method of processing open asynchronous application service event and open web service gateway implementing the same

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination