CN113472644B - Path addressing method and network service system - Google Patents
Path addressing method and network service system Download PDFInfo
- Publication number
- CN113472644B CN113472644B CN202110783370.7A CN202110783370A CN113472644B CN 113472644 B CN113472644 B CN 113472644B CN 202110783370 A CN202110783370 A CN 202110783370A CN 113472644 B CN113472644 B CN 113472644B
- Authority
- CN
- China
- Prior art keywords
- controller
- function entity
- configuration information
- network function
- path
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a path addressing method and a network service system, wherein the method comprises the following steps: determining a first path associated with at least one network function entity and a first controller in the first path directly connected with the at least one network function entity; judging whether the first controller is disconnected with at least one network functional entity; if the line is broken, sending first configuration information corresponding to the first controller to a routing center; the routing center receives the first configuration information, and traverses all other controllers except the controller in the first path to determine a target controller capable of processing the target service request; the routing center distributes the target controller to at least one network function entity; at least one network function entity processes the target service request under the control of the target controller; the method reduces the steps of redistributing the paths by the routing center and improves the efficiency of redistributing the paths.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a path addressing method and a network service system.
Background
The development of network technology brings great convenience to the life and work of people, more and more users utilize the network to engage in various activities, and the users distribute service requests to network functional entities through terminal equipment to perform service processing.
The service data system in the prior art includes a plurality of network function entities and a plurality of controllers, wherein a plurality of different paths for processing service requests are formed between the plurality of network function entities and the plurality of controllers, and the paths often have a problem of disconnection.
Disclosure of Invention
The embodiment of the application provides a path addressing method and a network service system, and aims to solve the problem of service transmission interruption caused by disconnection between a network function entity and a controller in the prior art.
In one aspect, the present application provides a path addressing method, applied to a network service system, where the network service system includes a routing center, multiple controllers and at least one network function entity, where the multiple controllers are integrated into multiple different paths according to processed service requests, the paths include at least one of the controllers, and the at least one of the controllers on the paths are arranged according to a processing sequence for processing the service requests; the controllers on the paths are respectively connected with the routing centers, and the at least one network functional entity is connected with the routing centers;
the path addressing method comprises the following steps:
determining a first path associated with the at least one network function entity and a first controller in the first path directly connected to the at least one network function entity;
judging whether the first controller and the at least one network function entity are disconnected;
if the line is broken, sending first configuration information corresponding to the first controller to the routing center;
the routing center receives the first configuration information, and traverses all other controllers except the controller in the first path to determine a target controller capable of processing the target service request;
the routing center assigning the target controller to the at least one network function entity;
the at least one network function entity processes the target service request under the control of the target controller.
Further, the determining whether the first controller and the at least one network function entity are disconnected includes:
the first controller sends a first detection signal to the at least one network function entity in a timing mode;
if the first controller does not receive a first feedback signal from the at least one network function entity within a preset time period, confirming that the at least one network function entity is disconnected with the first controller;
and the first controller generates disconnection prompt information and sends the disconnection prompt information to the routing center.
The routing center determines a target controller capable of processing the target service request, and the method comprises the following steps:
the routing center confirms all second controllers which are not disconnected except the controller in the first path;
the routing center sequentially acquires second configuration information corresponding to each second controller;
and comparing the first configuration information with the second configuration information, and judging whether the second controller can process the target service request.
The routing center confirms all second controllers which are not disconnected except the controller in the first path, and comprises the following steps:
the routing center sends a second detection signal to other controllers except the controller in the first path;
and if the routing center receives second feedback signals from the other controllers in a preset time period, the other controllers are considered not to be disconnected.
Further, the comparing the first configuration information with the second configuration information and determining whether the second controller can process the target service request includes:
if the first configuration information and the second configuration information match, confirming that the second controller can process the target service request;
and if the first configuration information and the second configuration information do not match, confirming that the second controller cannot process the target service request.
Further, the method further comprises:
if the second controller can process the target service request, the routing center stops acquiring second configuration information corresponding to the second controller;
and the second controller is used as a target controller capable of processing the target service request.
Further, the routing center, receiving the first configuration information, traversing all controllers except the first path to determine a target controller capable of processing the target service request, including:
the routing center confirms the third controllers which are not disconnected except the controller in the first path in sequence;
if the third controller is not disconnected, the routing center acquires third configuration information corresponding to the third controller;
and comparing the first configuration information with the third configuration information, and judging whether the third controller can process the target service request.
In a second aspect, the present application further provides a network service system, where the network service system includes a routing center, multiple controllers and at least one network function entity, where the multiple controllers are integrated into multiple different paths according to processed service requests, the paths include at least one of the controllers, and the at least one of the controllers on the paths are arranged according to an order of processing the service requests; the controllers on the paths are respectively connected with the routing centers, and the at least one network function entity is connected with the routing centers;
determining a first path associated with the at least one network function entity and a first controller in the first path directly connected to the at least one network function entity;
judging whether the first controller and the at least one network function entity are disconnected;
if the line is broken, sending first configuration information corresponding to the first controller to the routing center;
the routing center receives the first configuration information, and traverses all other controllers except the controller in the first path to determine a target controller capable of processing the target service request;
the routing center assigning the target controller to the at least one network function entity;
the at least one network function entity processes the target service request under the control of the target controller.
Further, the determining, by the first controller, whether the connection between the first controller and the at least one network function entity is disconnected includes:
the first controller sends a first detection signal to the at least one network function entity in a timing mode;
if the first controller does not receive a first feedback signal from the at least one network function entity within a preset time period, confirming that the at least one network function entity is disconnected with the first controller;
and the first controller generates disconnection prompt information and sends the disconnection prompt information to the routing center.
Further, the determining, by the routing center, a target controller capable of processing the target service request includes: the routing center confirms all second controllers which are not disconnected except the controller in the first path;
the routing center sequentially acquires second configuration information corresponding to each second controller;
and comparing the first configuration information with the second configuration information, and judging whether the second controller can process the target service request.
The application provides a path addressing method, which judges whether the line is broken between a network function entity and a controller, if the line is broken, the network function entity forwards a service request to a routing center, and the routing center directly traverses other unbroken controllers according to the service request until an available target controller is found, so that the steps of redistributing paths by the routing center are reduced, and the efficiency of redistributing the paths is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of a network service system provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating a path addressing method according to an embodiment of the present disclosure;
fig. 3 is a flowchart illustrating an embodiment of determining whether a connection between a first controller and at least one network function entity is disconnected according to the present application;
FIG. 4 is a flowchart illustrating an embodiment of a target determination controller according to the present application;
fig. 5 is a schematic flowchart of another embodiment of a confirmation target controller according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it is to be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", and the like indicate orientations or positional relationships based on those shown in the drawings, and are used merely for convenience of description and for simplicity of description, and do not indicate or imply that the referenced device or element must have a particular orientation, be constructed in a particular orientation, and be operated, and thus should not be considered as limiting the present application. Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
In this application, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known structures and processes are not set forth in detail in order to avoid obscuring the description of the present application with unnecessary detail. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
It should be noted that, since the method in the embodiment of the present application is executed in an electronic device, processing objects of each electronic device exist in the form of data or information, for example, time, which is substantially time information, and it can be understood that, if size, number, position, and the like are mentioned in subsequent embodiments, corresponding data exist so that the electronic device performs processing, which is not described herein again specifically.
The embodiments of the present application provide a path addressing method and a network service system, which are described in detail below.
Referring to fig. 1, fig. 1 is a schematic view of a network service system according to an embodiment of the present disclosure, where the network service system may include a routing center 100, a plurality of controllers 200, and at least one network function entity 300.
In this embodiment, the routing center 100 may be an independent server, or may be a server network or a server cluster composed of servers, for example, the routing center 100 described in this embodiment includes, but is not limited to, a computer, a network host, a single network server, a plurality of network server sets, or a cloud server composed of a plurality of servers. Among them, the Cloud server is constituted by a large number of computers or web servers based on Cloud Computing (Cloud Computing).
In the embodiment of the present Application, the Network function entity may be configured to receive a service request sent by a terminal device, and may be applied to Network Address Translation (NAT), carrier/telecommunication level NAT (CGN), a Firewall (FW, firewall), an Application switching controller (ADC, application discovery controller), application Performance Monitoring (APM), a Content Distribution Network (CDN, content Distribution Network), a Uniform Resource Locator (URL) filter, which is not limited to this, of course; the network function entity is mainly used for receiving the data stream of the terminal equipment and analyzing the received data stream.
Those skilled in the art will understand that the application environment shown in fig. 1 is only one application scenario related to the present application, and does not constitute a limitation on the application scenario of the present application, and that other application environments may further include more or fewer controllers than those shown in fig. 1, for example, only 1 controller is shown in fig. 1, and it is understood that the network service system may further include one or more other services, which are not limited herein.
In addition, as shown in fig. 1, the network service system may further include a memory 400 for storing data, such as service request data.
It should be noted that the scenario diagram of the network service system shown in fig. 1 is merely an example, and the network service system and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation to the technical solution provided in the embodiment of the present application.
In the above embodiment, the routing center 100 may be configured to determine a first path connecting with at least one network function entity; and the routing center 100 may also be configured to determine a first controller in the first path that is connected to at least one network function entity.
And a first controller of the plurality of controllers 200 may be configured to determine whether the first controller is disconnected from at least one network function entity. If the line is broken, the first controller may send the first configuration information corresponding to the first controller to the routing center 100;
and the routing center 100 may be further configured to receive the first configuration information and traverse all controllers except the controller in the first path to determine a target controller that can process the target service request. While the routing center 100 may also be used to assign the target controller to at least one network function entity.
And at least one network function entity 300 processes the target service request under the control of the target controller. The embodiment of the present application provides a path addressing method, which is applied to a network service system, where the network service system may include a routing center 100, a plurality of controllers 200, and at least one network function entity 300. Wherein each controller may be pre-configured to correspond to one type of traffic, i.e. each cluster of controllers may be pre-configured to control the network function entity to handle one type of traffic.
In the above embodiments, one service request may require a plurality of different processing flows; therefore, one service request can correspond to a plurality of different controllers so as to complete different processing flows in one service request. Multiple controllers can be integrated into multiple different paths according to the processed service request, and one path comprises at least one controller; and at least one controller in the path is typically arranged in the order in which the service requests are processed.
In the above embodiment, the controller on each path is connected to the routing center, and at least one network function entity is also connected to the routing center.
As shown in fig. 2, which is a schematic flow chart of an embodiment of a path addressing method in the embodiment of the present application, the path addressing method includes:
21. a first path is determined to connect with at least one network function entity, and a first controller in the first path directly connected with the at least one network function entity.
In the embodiment of the present application, different network function entities are usually connected to only one path to process one type of service request; but the service requests processed may be the same between different paths.
Since the first path includes at least one controller, when the number of controllers is multiple, the multiple controllers are generally arranged according to the processing order of the service request, so that the first controller directly connected to at least one network function entity can be determined; the first controller corresponds to a first step in the service request processed by the first path.
22. And judging whether the first controller is disconnected with at least one network function entity.
23. And if the line is broken, sending the first configuration information corresponding to the first controller to the routing center.
If the first controller is disconnected with the network function entity connected with the first controller, the first controller cannot control the network function entity to process the service request; at this time, the first configuration information corresponding to the disconnected first controller may be sent to the routing center, and the routing center may search for a new controller according to the first configuration information to process the target service request.
24. And the routing center receives the first configuration information and traverses all other controllers except the controller in the first path according to the first configuration information so as to determine a target controller capable of processing the target service request.
In the embodiment of the application, the first controller is located in the first path, and the first path processes the service requests of the same type, because the first controller is directly connected with the network function entity, when the first controller is disconnected from the network function entity, the network function entity cannot process the target service request; i.e. all controllers in the entire first path cannot process the target service request.
At this time, the first controller forwards the first configuration information corresponding to itself to the routing center, and after receiving the first configuration information, the routing center may search for other target controllers capable of processing the target service request according to the first configuration information. In the process that the routing center actually searches for the target controller, the controller in the first path does not need to be searched; i.e. only in the other controllers than the controller in the first path.
In the above embodiment, since all the controllers in the first path are arranged according to the processing order of the service requests, that is, each controller in the first path only processes a part of the service requests, or only completes a certain step of the whole steps of processing the service requests. Therefore, when the first controller is disconnected, it indicates that the first controller cannot perform the first step of the whole steps of processing the service request, and then the other controllers in the first path cannot perform other subsequent steps of the whole steps of processing the service request. In the process that the routing center actually searches for the target controller, the routing center only needs to search for the target controller in the other controllers except for the controller in the first path. The target service request processed by the target controller may be forwarded to the first path for subsequent processing.
25. The routing center assigns the target controller to at least one network function entity.
26. At least one network function entity processes the target service request under the control of the target controller.
The application provides a path addressing method, which is characterized in that whether the disconnection between a network function entity and a controller is caused is judged, if the disconnection is caused, the network function entity forwards a service request to a routing center, and the routing center directly traverses other unbroken controllers according to the service request until an available target controller is found, so that the steps of redistributing paths by the routing center are reduced, and the efficiency of redistributing the paths is improved.
As shown in fig. 3, a schematic flowchart of an embodiment of determining whether a first controller is disconnected from at least one network function entity according to the embodiment of the present application may include:
31. the first controller sends a first detection signal to at least one network function entity in a timing mode.
32. And if the first controller does not receive the first feedback signal from the at least one network function entity within the preset time period, the disconnection between the at least one network function entity and the first controller is confirmed.
33. The first controller generates disconnection prompt information and sends the disconnection prompt information to the routing center.
In the embodiment of the present application, the controller may be utilized to determine whether the controller itself is disconnected from the network function entity. Specifically, each controller is connected with the routing center, and the controller can send a detection signal to the corresponding network function entity at regular time; if the controller receives the feedback signal fed back by the network functional entity within the preset time period, it can be determined that the controller and the network functional entity are not disconnected. Similarly, if the controller does not receive the feedback signal fed back by the network function entity within the preset time period, it may determine that the controller and the network function entity are disconnected.
In a specific embodiment of the present application, a network service system includes a network function entity, and the network function entity can process a type of target service request by using a plurality of controllers in a first path; and the plurality of controllers are arranged in a processing order of processing the target service requests. The first path comprises a plurality of different controllers to finish different steps in the whole process of processing the target service request; and a first controller of the plurality of different controllers is directly connected to the network function entity. The first controller may send the first detection signal to the network function entity at regular time, and if the network function entity is not disconnected from the first controller, the network function entity may process the first detection signal, generate the first feedback signal, and send the first feedback signal to the first controller. If the first controller receives the first feedback signal within a preset time period, it may be determined that the network function entity and the first controller are not disconnected.
Similarly, if the network function entity is disconnected from the first controller, the network function entity cannot receive the first detection signal at all, and further cannot generate a first feedback signal corresponding to the first detection signal and feed the first feedback signal back to the first controller. Therefore, if the first controller does not receive the first feedback signal from the network function entity within the preset time period, it may be considered that the network function entity is disconnected from the first controller.
In the above embodiment, if the first controller receives the first feedback signal but does not receive the first feedback signal within the preset time period, it may be considered that the network function entity is not disconnected from the first controller but has another fault, so that the transmission of the first feedback signal is delayed. At this time, the routing center may generate a prompt signal to prompt an operator to check the network service system to remove the fault.
In other embodiments of the present application, the network service system may further include a listener, and may use the listener to listen whether a line between the network function entity and the controller is disconnected. The process of monitoring whether the line between the network functional entity and the controller is disconnected by using the listener can refer to the specific step of monitoring whether the line between the network functional entity and the controller is disconnected, which is not limited herein.
In the embodiment of the present application, reference may be made to the above contents for a process of determining whether a certain controller in a certain path is disconnected, which is not limited herein.
When the disconnection between the network function entity and the first controller is determined, the network function entity can generate disconnection prompt information and send the disconnection prompt information to the routing center so as to prompt that the disconnection occurs in the network service system of the routing center.
In other embodiments of the present application, while the network functional entity generates and sends the disconnection prompting information, the network functional entity needs to send a target service request corresponding to the disconnection prompting information to the routing center; after receiving the target service request, the routing center needs to search for a target controller corresponding to the target service request, so that processing interruption of the target service request is avoided.
In the foregoing embodiment, after the routing center receives the target service request, the routing center further needs to acquire first configuration information corresponding to the disconnected first controller. And the routing center can determine a target controller capable of processing the target service request according to the first configuration information and the target service request.
As shown in fig. 4, a schematic flowchart of an embodiment of a target determination controller provided in the present application may include:
41. the routing center identifies all second controllers that are not disconnected except for the controller in the first path.
42. And the routing center sequentially acquires the second configuration information corresponding to each second controller.
43. And comparing the first configuration information with the second configuration information to confirm whether the second controller can process the target service request.
Specifically, controllers in the network service system are all configured in advance to be capable of processing different service requests; the configuration information corresponding to each controller is different, and the service requests which can be processed by the controllers are also different. After the routing center confirms that the first controller is disconnected from the network function entity, the routing center needs to search for a new controller to process a target service request in the network function entity.
In the above embodiment, the routing center needs to first determine the controllers corresponding to the paths other than the first path, and determine all the second controllers in the paths that are not disconnected. The controllers in the same path respectively correspond to a certain step in the whole process of processing the service request, that is, the processing steps of the service request corresponding to the controllers in the same path are different. Therefore, when the first controller in the first path is disconnected, the other controllers in the first path cannot perform the processing steps corresponding to the first controller; the routing center need not detect other controllers in the first path.
Specifically, after confirming the controllers corresponding to the other paths except the first path, the routing center needs to confirm all the second controllers which are not disconnected in the other paths again; only if the second controller is not disconnected, a target controller capable of processing the target service request can be searched from all the second controllers which are not disconnected.
The process of determining all the second controllers which are not disconnected may include: the routing center sends a second detection signal to other controllers except the controller in the first path; and if the routing center receives second feedback signals from other controllers in a preset time period, the other controllers are considered not to be disconnected.
Specifically, after receiving the target service request, the routing center may sequentially send the second detection signal to any other controller except the controller in the first path. If the line is not broken between the routing center and the controller, the controller can process the second detection signal, generate a second feedback signal and send the second feedback signal to the routing center. If the routing center receives the second feedback signal within a preset time period, it may be determined that the network functional entity and the routing center are not disconnected.
Similarly, if the routing center is disconnected from the controller, the controller cannot receive the second detection signal at all, and further cannot generate a second feedback signal corresponding to the second detection signal and feed the second feedback signal back to the routing center. Therefore, if the routing center does not receive the second feedback signal from the controller within the preset time period, the routing center and the controller may be considered to be disconnected.
In the foregoing embodiment, if the routing center receives the second feedback signal but does not receive the second feedback signal within the preset time period, it may be considered that the routing center and the controller are not disconnected, but another fault occurs, so that the sending of the second feedback signal is delayed. At this time, the routing center may generate a prompt signal to prompt an operator to check the network service system to remove the fault.
It should be noted that, in the above embodiment, when all the second controllers, except the controller in the first path, which are not disconnected, are confirmed, the network function entity is normally connected to the routing center before. I.e. signals can be normally received or transmitted between the network functional entity and the routing center. In the above embodiment, the specific duration of the preset duration may be changed according to the actual service condition of the network service system, and is not limited herein.
In the foregoing embodiment, after the routing center confirms all the second controllers that are not disconnected, the routing center may further sequentially obtain second configuration information corresponding to each second controller that is not disconnected, compare the first configuration information corresponding to the first controller with the second configuration information corresponding to the second controller, and determine whether the second controller can process the target service request, that is, confirm the target controller in all the second controllers.
The comparing, by the routing center, the first configuration information corresponding to the first controller and the second configuration information corresponding to the second controller, and determining whether the second controller can process the target service request may include:
if the first configuration information and the second configuration information are matched, confirming that the second controller can process the target service request; and if the first configuration information and the second configuration information do not match, confirming that the second controller can not process the target service request.
Specifically, generally, similar or identical information exists between configuration information corresponding to controllers that process the same type of service request. If the similarity between multiple pieces of configuration information corresponding to different controllers is greater than a preset value, it can be considered that the different controllers can process the same type of service request.
In a specific embodiment of the present application, the preset value may be 90%, that is, when the similarity between multiple pieces of configuration information corresponding to different controllers is greater than or equal to 90%, it may be considered that the different controllers may process the same type of service request. If the similarity between the first configuration information and the second configuration information is greater than or equal to 90%, the first configuration information and the second configuration information are matched; then, it may be considered that the first controller corresponding to the first configuration information and the second controller corresponding to the second configuration information may process service requests of the same type; that is, the second controller can process the target service request corresponding to the first controller.
If the similarity between the first configuration information and the second configuration information is less than or equal to 90%, that is, the first configuration information and the second configuration information are not matched, it may be considered that the first controller corresponding to the first configuration information and the second controller corresponding to the second configuration information may not process the same type of service request; that is, the second controller may not process the target service request corresponding to the first controller.
In the above embodiment, when the routing center sequentially obtains the second configuration information corresponding to each second controller and compares the first configuration information with the second configuration information; if the routing center judges that the second configuration information corresponding to the second controller is matched with the first configuration information, namely the second controller can process the target service request, the routing center stops acquiring the second configuration information corresponding to the second controller. At this time, the second controller corresponding to the second configuration information corresponding to the first configuration information is the target controller capable of processing the target service request. The second controller may be utilized to process the target service request that cannot be processed by the first controller, that is, the second controller is utilized to control the network function entity to process the target service request.
In the above embodiment, if the routing center confirms the target controller, the routing center stops obtaining the second configuration information corresponding to the second controller that is not disconnected.
In the above embodiment, the routing center may sequentially determine the second controller that is not disconnected, or simultaneously determine whether all the other controllers except the controller in the first path are disconnected. That is, the routing center needs to determine all the second controllers that are not disconnected except the controller in the first path, and then sequentially obtain the second configuration information corresponding to each second controller and compare the second configuration information to determine the target controller.
As shown in fig. 5, a schematic flow chart of another embodiment of the target confirmation controller provided for the embodiment of the present application, where the routing center receives the first configuration information and traverses all controllers except the first path to determine a target controller capable of processing the target service request, may include:
51. the routing center sequentially confirms the third controllers which are not disconnected except the controller in the first path.
52. And if the third controller is not disconnected, the routing center acquires third configuration information corresponding to the third controller.
53. And comparing the first configuration information with the third configuration information, and judging whether the third controller can process the target service request.
In the above embodiment, the routing center may determine whether the third controller is the target controller while determining the third controller that is not disconnected. That is, the routing center may sequentially send the third detection signal to all other controllers except the controller in the first path, and if the third controller is not disconnected, the third controller may process the third detection signal and generate third feedback information to feed back the third feedback information to the routing center. And when the third controller which is not disconnected feeds back the third feedback information to the routing center, the third controller which is not disconnected can also send the third configuration information corresponding to the third controller to the routing center. The routing center receives the third feedback information and can confirm that the third controller is not disconnected; the routing center also receives third configuration information corresponding to the third controller which is not disconnected, and compares the first configuration information with the third configuration information to determine whether the third controller is a target controller.
In the embodiment of the present application, the process of comparing the first configuration information and the third configuration information to determine whether the third controller is the target controller may refer to the process of comparing the first configuration information and the second configuration information to determine whether the second controller is the target controller, and this is not limited herein.
In the above embodiment, after the routing center confirms the target controller, the routing center does not need to determine whether the third controller is disconnected, and does not need to acquire the third configuration information corresponding to the third controller that is not disconnected.
In the embodiment of the application, if the routing center receives multiple disconnection prompt messages at the same time, that is, multiple disconnections occur in the whole network service system, the routing center can obtain multiple service requests which can be processed by multiple disconnected controllers; and judging the priorities of the plurality of service requests, and searching target controllers corresponding to different service requests according to the priorities of the plurality of service requests. The priority of the service requests may be the complexity of the service requests, the urgency of the service requests, or the processing order of the service requests.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.
In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
The path addressing method and the network service system provided in the embodiments of the present application are described in detail above, and specific examples are applied in the present application to explain the principles and embodiments of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (8)
1. A path addressing method is applied to a network service system, the network service system comprises a routing center, a plurality of controllers and at least one network function entity, the plurality of controllers are integrated into a plurality of different paths according to processed service requests, the paths comprise at least one controller, and the at least one controller on the paths is arranged according to the processing sequence of processing the service requests; the controllers on the paths are respectively connected with the routing centers, and the at least one network functional entity is connected with the routing centers;
the path addressing method comprises the following steps:
determining a first path associated with the at least one network function entity and a first controller in the first path directly connected to the at least one network function entity;
judging whether the first controller is disconnected with the at least one network function entity;
if the line is broken, sending first configuration information corresponding to the first controller to the routing center;
the routing center receives the first configuration information, and traverses all other controllers except the controller in the first path to determine a target controller capable of processing a target service request;
the routing center assigning the target controller to the at least one network function entity;
the at least one network function entity processes the target service request under the control of the target controller;
wherein, the routing center determines a target controller capable of processing the target service request, and comprises:
the routing center confirms all second controllers which are not disconnected except the controller in the first path;
the routing center sequentially acquires second configuration information corresponding to each second controller;
and comparing the first configuration information with the second configuration information, and judging whether the second controller can process the target service request.
2. The path addressing method according to claim 1, wherein the determining whether the first controller is disconnected from the at least one network function entity comprises:
the first controller sends a first detection signal to the at least one network function entity in a timing mode;
if the first controller does not receive a first feedback signal from the at least one network function entity within a preset time period, confirming that the at least one network function entity is disconnected from the first controller;
and the first controller generates disconnection prompt information and sends the disconnection prompt information to the routing center.
3. The path addressing method of claim 1, wherein the routing center validating all second controllers not disconnected except for the controller in the first path comprises:
the routing center sends a second detection signal to other controllers except the controller in the first path;
and if the routing center receives second feedback signals from the other controllers in a preset time period, the other controllers are considered not to be disconnected.
4. The path addressing method of claim 1, wherein comparing the first configuration information with the second configuration information to determine whether the second controller can process the target service request comprises:
if the first configuration information and the second configuration information match, confirming that the second controller can process the target service request;
and if the first configuration information and the second configuration information do not match, confirming that the second controller cannot process the target service request.
5. The path addressing method according to claim 4, further comprising:
if the second controller can process the target service request, the routing center stops acquiring second configuration information corresponding to the second controller;
and the second controller is used as a target controller capable of processing the target service request.
6. The path addressing method of claim 1, wherein the routing center receives the first configuration information, traverses all controllers except the first path, and determines a target controller capable of processing the target service request, comprising:
the routing center sequentially confirms the third controllers which are not disconnected except the controller in the first path;
if the third controller is not disconnected, the routing center acquires third configuration information corresponding to the third controller;
and comparing the first configuration information with the third configuration information, and judging whether the third controller can process the target service request.
7. A network service system is characterized in that the network service system comprises a routing center, a plurality of controllers and at least one network function entity, wherein the plurality of controllers are integrated into a plurality of different paths according to processed service requests, the paths comprise at least one controller, and the at least one controller on the paths is arranged according to the sequence of processing the service requests; the controllers on the paths are respectively connected with the routing centers, and the at least one network function entity is connected with the routing centers;
the routing center is used for determining a first path connected with the at least one network function entity;
the routing center is further configured to determine a first controller connected to the at least one network function entity in the first path;
the first controller is used for judging whether the first controller and the at least one network function entity are disconnected; if the line is disconnected, the at least one network function entity forwards the target service request corresponding to the at least one network function entity to the routing center;
the routing center is further configured to traverse paths other than the first path according to the target service request to determine a target path that can process the target service request;
wherein, the routing center determines a target controller capable of processing the target service request, and comprises:
the routing center confirms all second controllers which are not disconnected except the controller in the first path;
the routing center sequentially acquires second configuration information corresponding to each second controller;
and comparing the first configuration information and the second configuration information corresponding to the first controller, and judging whether the second controller can process the target service request.
8. The network service system of claim 7, wherein the determining, by the first controller, whether the connection between the first controller and the at least one network function entity is disconnected comprises:
the first controller sends a first detection signal to the at least one network function entity in a timing mode;
if the first controller does not receive a first feedback signal from the at least one network function entity within a preset time period, confirming that the at least one network function entity is disconnected from the first controller;
and the first controller generates disconnection prompt information and sends the disconnection prompt information to the routing center.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110783370.7A CN113472644B (en) | 2021-07-12 | 2021-07-12 | Path addressing method and network service system |
| PCT/CN2021/135685 WO2023284232A1 (en) | 2021-07-12 | 2021-12-06 | Path addressing method and network service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110783370.7A CN113472644B (en) | 2021-07-12 | 2021-07-12 | Path addressing method and network service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113472644A CN113472644A (en) | 2021-10-01 |
| CN113472644B true CN113472644B (en) | 2023-03-31 |
Family
ID=77879721
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110783370.7A Active CN113472644B (en) | 2021-07-12 | 2021-07-12 | Path addressing method and network service system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113472644B (en) |
| WO (1) | WO2023284232A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113472644B (en) * | 2021-07-12 | 2023-03-31 | 武汉绿色网络信息服务有限责任公司 | Path addressing method and network service system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108270669A (en) * | 2016-12-30 | 2018-07-10 | 中兴通讯股份有限公司 | Business recovery device, master controller, the system and method for SDN network |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104426789B (en) * | 2013-08-23 | 2017-08-11 | 新华三技术有限公司 | Forwarding unit control method and equipment in software defined network |
| JP6111974B2 (en) * | 2013-10-22 | 2017-04-12 | 富士通株式会社 | Transfer device, control device, and transfer method |
| US9590892B2 (en) * | 2013-12-02 | 2017-03-07 | University Of Ontario Institute Of Technology | Proactive controller for failure resiliency in communication networks |
| CN104753703A (en) * | 2013-12-27 | 2015-07-01 | 中兴通讯股份有限公司 | Method and system for controlling network topology |
| EP3257203B1 (en) * | 2015-02-09 | 2019-06-19 | Telefonaktiebolaget LM Ericsson (publ) | Method and device for handling multi path connections |
| CN108632055B (en) * | 2017-03-17 | 2020-10-09 | 华为技术有限公司 | Network control method and device and communication system |
| CN107465611A (en) * | 2017-09-05 | 2017-12-12 | 北京东土科技股份有限公司 | The pretection switch method and device of SDN controllers and Switch control link |
| CN111083718B (en) * | 2018-10-22 | 2023-07-21 | 中国移动通信有限公司研究院 | Session management method, network function and network system |
| WO2020220319A1 (en) * | 2019-04-30 | 2020-11-05 | Zte Corporation | Session management function selection |
| CN111817959A (en) * | 2020-07-16 | 2020-10-23 | 迈普通信技术股份有限公司 | Network path management method and device, SDN controller and readable storage medium |
| CN112134964B (en) * | 2020-10-28 | 2023-10-10 | 武汉绿色网络信息服务有限责任公司 | Controller distribution method, computer equipment, storage medium and network service system |
| CN113472644B (en) * | 2021-07-12 | 2023-03-31 | 武汉绿色网络信息服务有限责任公司 | Path addressing method and network service system |
-
2021
- 2021-07-12 CN CN202110783370.7A patent/CN113472644B/en active Active
- 2021-12-06 WO PCT/CN2021/135685 patent/WO2023284232A1/en unknown
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108270669A (en) * | 2016-12-30 | 2018-07-10 | 中兴通讯股份有限公司 | Business recovery device, master controller, the system and method for SDN network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113472644A (en) | 2021-10-01 |
| WO2023284232A1 (en) | 2023-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110493352B (en) | Unified gateway service system based on WEB middleware and service method thereof | |
| EP3968607B1 (en) | Service invocation methods | |
| US10313452B2 (en) | Migrating a chat message service provided by a chat server to a new chat server | |
| CN107483260B (en) | Fault processing method and device and electronic equipment | |
| CN101102288A (en) | A method and system for realizing large-scale instant message | |
| CN110365759B (en) | Data forwarding method, device, system, gateway equipment and storage medium | |
| US10476746B2 (en) | Network management method, device, and system | |
| CN109451063B (en) | Server hot standby method and system | |
| CN108156024B (en) | Method, system and storage medium for detecting availability based on distributed website | |
| CN113472644B (en) | Path addressing method and network service system | |
| CN108632355B (en) | Routing method for household appliance network, control terminal, readable storage medium and equipment | |
| CN111385324A (en) | Data communication method, device, equipment and storage medium | |
| CN104683243A (en) | Data processing method, device and system | |
| CN113328922A (en) | Communication method and device across multiple local area networks | |
| CN113472662B (en) | Path redistribution method and network service system | |
| CN109889545B (en) | Data communication method and device | |
| CN114095759B (en) | Stream media redirection method and related device | |
| CN108769151B (en) | A kind of method and device for business processing | |
| CN112968975B (en) | Service request processing method and device | |
| CN115150363B (en) | IP address updating method, gateway device, gateway down-hanging device and storage medium | |
| CN113515055B (en) | Edge computing node, terminal equipment registration method and device and intelligent home system | |
| CN110460586B (en) | In-vehicle node communication method, device, equipment and storage medium | |
| CN114124780B (en) | Route issuing method, device, electronic equipment and storage medium | |
| KR101529080B1 (en) | Method and system for providing internet connection notifying service | |
| CN107623576B (en) | Cluster analysis system and deployment method, communication connection establishment method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |