CN111741077B - Network service scheduling method and device, electronic equipment and storage medium - Google Patents
Network service scheduling method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111741077B CN111741077B CN202010478021.XA CN202010478021A CN111741077B CN 111741077 B CN111741077 B CN 111741077B CN 202010478021 A CN202010478021 A CN 202010478021A CN 111741077 B CN111741077 B CN 111741077B
- Authority
- CN
- China
- Prior art keywords
- scheduling
- network
- fault
- determining
- service
- 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
- 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
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a network service scheduling method and device, electronic equipment and a storage medium, and relates to the technical field of service scheduling, in particular to the technical field of cloud computing service scheduling. The specific implementation scheme is as follows: acquiring a service request; acquiring network service monitoring information corresponding to the service request, wherein the network service monitoring information comprises an identifier of whether the service request reaches a target server and an interrupt position of the service request; if the network fault is determined to occur according to the identifier, determining a scheduling strategy corresponding to the network fault according to the interrupt position; and controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling policy according to the scheduling policy. After the network fault is determined, the method can automatically acquire the scheduling strategy according to the interrupt position of the service request and execute the scheduling operation, has the advantages of high efficiency, high accuracy, labor cost reduction and the like, is beneficial to shortening the waiting time of a user, and improves the stability and reliability of the cloud platform network service.
Description
Technical Field
The present application relates to the technical field of service scheduling in the technical field of computers, and in particular, to the technical field of cloud computing service scheduling, and in particular, to a method and an apparatus for scheduling a network service, an electronic device, and a storage medium.
Background
At present, when a network service fails, most of the network services need to manually judge the failure reason and process the failure, the method has the disadvantages of low efficiency, high error rate, high labor cost and the like, and the user has long waiting time and has great influence on the normal use of the user, so that a method needs to be researched to ensure that when a certain network service fails, the failure processing and the service recovery can be timely performed.
Disclosure of Invention
A method, an apparatus, an electronic device and a storage medium for scheduling a network service are provided.
According to a first aspect, there is provided a method for scheduling a network service, comprising: acquiring a service request; acquiring network service monitoring information corresponding to the service request, wherein the network service monitoring information comprises an identifier of whether the service request reaches a target server and an interruption position of the service request; if the network fault is determined to occur according to the identifier, determining a scheduling strategy corresponding to the network fault according to the interruption position; and controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling strategy according to the scheduling strategy.
According to a second aspect, there is provided a scheduling apparatus for a network service, comprising: the first acquisition module is used for acquiring the service request; a second obtaining module, configured to obtain network service monitoring information corresponding to the service request, where the network service monitoring information includes an identifier of whether the service request reaches a target server and an interrupt location of the service request; a first determining module, configured to determine, if a network fault is determined to occur according to the identifier, a scheduling policy corresponding to the network fault according to the interrupt location; and the execution module is used for controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling strategy according to the scheduling strategy.
According to a third aspect, there is provided an electronic device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executable by the at least one processor to enable the at least one processor to perform the method for scheduling network services according to the first aspect of the present application.
According to a fourth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to execute the method of scheduling a network service according to the first aspect of the present application.
The embodiment provided by the application at least has the following beneficial technical effects:
according to the scheduling method, the scheduling device, the electronic equipment and the storage medium of the network service, after the network fault is determined, the scheduling strategy can be automatically obtained according to the interrupt position of the service request, and the scheduling operation is executed.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a schematic diagram of a scheduling system for network services according to a first embodiment of the present application;
FIG. 2 is a schematic diagram of a scheduling system for network services according to a second embodiment of the present application;
fig. 3 is a flowchart illustrating a scheduling method of a network service according to a first embodiment of the present application;
fig. 4 is a flowchart illustrating a scheduling method of a network service according to a second embodiment of the present application;
fig. 5 is a schematic flowchart illustrating a network device controlling a corresponding network device according to a scheduling policy to perform a scheduling operation corresponding to the scheduling policy in a scheduling method for a network service according to a third embodiment of the present application;
fig. 6 is a schematic diagram of a scheduling path in a scheduling method of a network service according to a fourth embodiment of the present application;
fig. 7 is a schematic diagram of a scheduling path in a scheduling method of a network service according to a fifth embodiment of the present application;
fig. 8 is a block diagram of a scheduling apparatus of a network service according to a first embodiment of the present application;
fig. 9 is a block diagram of a scheduling apparatus of a network service according to a second embodiment of the present application;
fig. 10 is a block diagram of an electronic device for implementing a scheduling method of a network service according to an embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a scheduling system for network services according to a first embodiment of the present application.
As shown in fig. 1, the scheduling system 100 for network services includes: user terminal 101, server 102, monitoring unit 103, and scheduling unit 104. The user terminal 101 may include a plurality of users, such as user 1 and user 2, and the server 102 may include a plurality of servers, such as server 1 and server 2. It should be noted that, a communication connection is established between the user terminal 101, the server 102, the monitoring unit 103, and the scheduling unit 104, and the communication connection may be at least one of a wireless network connection and a wired network connection. The Wireless network connection may be, for example, a communication connection performed in a mobile communication network, a bluetooth, a Zigbee (Zigbee) mode, a Wireless Fidelity (WIFI) mode, or the like. The wired network connection may be a communication connection using twisted pair, coaxial cable, optical fiber, network cable, or data cable (such as USB, IEEE1394, serial or parallel port, etc.), for example.
The user terminal 101 may directly send a service request to the server 102, or the user terminal 101 may send a service request to the scheduling unit 104 first, and the scheduling unit 104 may obtain a corresponding target server according to the service request and forward the service request to the target server in the server 102. The monitoring unit 103 is configured to monitor the network service and send monitoring information to the scheduling unit 104, and the scheduling unit 104 may determine whether the network service fails according to the monitoring information and perform scheduling operation.
Alternatively, as shown in fig. 2, the server 102 may include a plurality of Available areas, such as an Available Area (AZ) 1 and an Available area 2, where each Available area may include a plurality of servers. Optionally, a communication connection is established between the available zones. For example, the available regions may communicate with each other through an intranet, and do not need to be forwarded by the scheduling unit 104, so that the communication efficiency is high.
Optionally, a Point Of Presence (POP) Of the scheduling unit 104 is intercommunicated with an external network through a multi-line BGP (Border Gateway Protocol) network. The extranet may include at least two of telecommunications, connectivity, mobility, pennisetum, iron, century interconnections, educational, fanning broadband, hangzhou Chinese, OCN (Oriental Cable Network), and other carrier networks, without limitation.
Fig. 3 is a flowchart illustrating a scheduling method of a network service according to a first embodiment of the present application.
As shown in fig. 3, a method for scheduling a network service according to a first embodiment of the present application includes:
s301, acquiring a service request.
It should be noted that the execution subject of the scheduling method for network services according to the embodiment of the present application may be a hardware device with data information processing capability and/or software (e.g., the scheduling unit 104 in fig. 1) necessary for driving the hardware device to operate. Optionally, the execution subject may include a workstation, a server, a computer, a user terminal, and other network devices.
The service request may be a service request sent by the user terminal to the server.
As another possible implementation, taking fig. 1 as an example, the user terminal 101 may also directly send a service request to the scheduling unit 104, and the scheduling unit 104 may obtain a corresponding target server according to the service request and forward the service request to the target server in the server 102.
It is understood that a plurality of servers may be included in the server side, and different servers may provide different services. Optionally, a mapping relationship or a mapping table between the service request and the server may be pre-established, and after the service request is obtained, the mapping relationship or the mapping table is queried, so that the server corresponding to the service request can be determined, and is used as a target server of the service request to provide a network service required by the server to the user terminal.
S302, network service monitoring information corresponding to the service request is obtained, wherein the network service monitoring information comprises an identifier of whether the service request reaches a target server and an interruption position of the service request.
In an embodiment of the present application, a network service corresponding to a service request may be monitored, and specifically, an identifier of a target server, an identifier of a user terminal, an interrupt location of the service request, and the like may be monitored, where the service request reaches the identifier of the target server, and service information provided by a service terminal reaches the user terminal.
It will be appreciated that the identity may be pre-established in the server to indicate whether the service request has arrived at the server. For example, the identifier may be in the form of a number "0/1", which when identified as "0" indicates that the service request did not reach the server, and when identified as "1" indicates that the service request reached the server. The identifier may also be in other forms and is not limited herein.
It can be understood that, the user terminal may also be pre-established with an identifier for indicating whether the service information provided by the service end reaches the user terminal. For example, the identifier may be "0/1" in a digital form, and when the identifier is "0", it indicates that the service information provided by the service end does not reach the user terminal, and when the identifier is "1", it indicates that the service information provided by the service end reaches the user terminal. The identifier may also be in other forms and is not limited herein.
It should be noted that, an identifier may also be set at another node of the network service, so as to indicate whether the network service at the node fails, which is not described herein again.
Optionally, the interruption position of the service request may include a user terminal, a server, a network, and the like, which are not described herein again.
Continuing with fig. 1 as an example, the monitoring unit 103 may monitor the network service corresponding to the service request and send network service monitoring information to the scheduling unit 104. If the user terminal 101 sends a service request to the server 102 through the scheduling unit 104, the interruption position of the service request may further include the scheduling unit 104. Optionally, an identifier may be set at a point of presence, a router, a switch, or the like of the scheduling unit 104, so as to indicate whether a network service at the node fails, and for related contents of the identifier, please refer to the foregoing embodiment, which is not described herein again.
And S303, if the network fault is determined to occur according to the identifier, determining a scheduling strategy corresponding to the network fault according to the interrupt position.
In one embodiment of the present application, the determination of whether a network failure has occurred may be based on an identification of whether the service request has reached the target server. For example, when the identifier is "0/1" in a digital form, if the pre-calibrated identifier is "0", it indicates that the service request does not reach the server, and when the identifier is "1", it indicates that the service request reaches the server. If the obtained identifier of the target server is "0", it indicates that the service request does not reach the target server at this time, and it is determined that a network failure occurs; when the acquired identifier is "1", it indicates that the service request reaches the target server at this time, and it is determined that the network failure has not occurred.
In an embodiment of the present application, it may further be determined whether a network failure occurs according to an identifier indicating whether service information provided by the service end reaches the user terminal. For example, when the identifier is in a digital form of "0/1", if the pre-calibrated identifier is "0", it indicates that the service information provided by the service end does not reach the user terminal, and when the identifier is "1", it indicates that the service information provided by the service end reaches the user terminal. When the obtained identifier of the user terminal is "0", it indicates that the service information provided by the service end does not reach the user terminal at this time, and it is determined that a network fault occurs; when the obtained identifier of the user terminal is "1", it indicates that the service information provided by the service end reaches the user terminal at this time, and it is determined that the network failure does not occur.
Further, if it is determined that no network fault occurs according to the identifier, it is indicated that the current network service is normal, and the user can normally use the network service; if the network fault is determined to occur according to the identifier, the current network service is abnormal, and fault processing needs to be performed according to the network fault in order to ensure that the user can normally use the network service.
In an embodiment of the application, after the network fault is determined according to the identifier, the scheduling policy corresponding to the network fault can be automatically acquired according to the interruption position of the service request, and manual judgment of the fault reason and determination of a processing method are not needed, so that the method is flexible and convenient, and the accuracy is high.
Optionally, a mapping relation or a mapping table between the interrupt position and the scheduling policy may be pre-established, and after the interrupt position is obtained, the mapping relation or the mapping table is queried, so that the scheduling policy required at this time can be determined, and the scheduling policy is used for scheduling the network service.
And S304, controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling strategy according to the scheduling strategy.
It should be noted that, for the relevant content of the network device performing the scheduling operation, please refer to the above embodiment, which is not described herein again.
Continuing with fig. 1 as an example, if the target server corresponding to the service request is server 1 and the interrupt location is at the server, the server 1 may be identified as having a fault, and the scheduling unit 104 may remove an IP Address (Internet Protocol Address) of the faulty server 1 and switch the removed IP Address of the faulty server 1 to the standby server 2, so as to switch the communication with the faulty server 1 to the standby server 2.
Alternatively, if the interruption position is at the point of presence of the scheduling unit 104, and the user is a jiangsu telecommunication user, and the service of the telecommunication operator platform in other areas, such as Shandong telecommunication, shanghai telecommunication, etc., is normal, it may be recognized that the service of the jiangsu telecommunication operator platform is abnormal, and the scheduling unit 104 may forward the service request to the server corresponding to the Shandong telecommunication operator platform.
In summary, according to the scheduling method of the network service in the embodiment of the present application, after a network fault is determined, a scheduling policy can be automatically obtained according to an interrupt position of a service request, and a scheduling operation is executed.
Fig. 4 is a flowchart illustrating a scheduling method of a network service according to a second embodiment of the present application.
As shown in fig. 4, a method for scheduling a network service according to a second embodiment of the present application includes:
s401, acquiring a service request.
S402, network service monitoring information corresponding to the service request is obtained, wherein the network service monitoring information comprises an identifier of whether the service request reaches a target server and an interruption position of the service request.
For specific descriptions of S401 to S402, reference may be made to the description of relevant contents in the foregoing embodiments, and details are not repeated herein.
Step S303 in the previous embodiment specifically includes the following step S403.
And S403, if the network fault is determined to occur according to the identifier, determining a fault type corresponding to the network fault according to the interruption position, and determining a scheduling strategy according to the fault type.
It can be understood that, if the interruption positions of the service requests are different, the causes and types of the network failures are different, and the corresponding scheduling policies are different.
The method can determine the type of the network fault according to the interrupt position of the service request, different interrupt positions can correspond to different fault types, corresponding scheduling strategies are automatically obtained according to the fault types, manual judgment of fault reasons and determination and processing methods are not needed, and the method is flexible, convenient and high in accuracy.
Optionally, a mapping relation or a mapping table between the interrupt location, the fault type, and the scheduling policy may be pre-established, and after the interrupt location is obtained, the mapping relation or the mapping table is queried, so that the fault type at that time and the scheduling policy corresponding to the fault type can be determined, and the mapping relation or the mapping table is used for scheduling the network service.
As a possible implementation manner, the step S403 may specifically include: and if the interruption position is the user terminal, determining that the fault type is the network protocol fault, and if the fault type is the network protocol fault, determining that the scheduling strategy is to replace the current network protocol with a preset standby network protocol so as to eliminate the network protocol fault.
In one embodiment of the application, the user terminal can perform data information interaction according to a network protocol. The network Protocol may be an Internet Protocol (IP), which is not limited herein. It will be appreciated that the user terminal may pre-store multiple copies of the network protocol, such as layer 4 network protocol and layer 7 network protocol, etc., to enable timely replacement in the event of a failure of the network protocol.
As a possible implementation manner, the step S403 may specifically include: and if the interruption position is the current available area of the network, determining that the fault type is the available area fault, and if the fault type is the available area fault, determining that the scheduling strategy is to schedule the service request to other available areas under the current network operator platform of the current region so as to eliminate the available area fault.
It is understood that, as shown in fig. 2, the server may include a plurality of available areas, and a service request may correspond to a plurality of available areas. Optionally, the target available area corresponding to the service request may be determined according to a region and a network operator platform of the user terminal.
For example, if the user 1 is a user of the east China telecom, and the available region corresponding to the service request of the user 1 includes the available region 1 of the east China telecom, the available region 2 of the east China telecom, and the available region 3 of the east China telecom, when the interruption position of the service request of the user 1 is a fault of the available region 1 of the east China telecom where the user 1 is currently located, it is determined that the scheduling policy is to schedule the service request of the user 1 to other available regions of the east China telecom, for example, the available region 2 of the east China telecom, and the available region 3 of the east China telecom, and provide services to the user 1 through the other available regions of the east China telecom.
As a possible implementation manner, the step S403 may specifically include: and if the fault type is the region fault, determining a scheduling strategy to schedule the service request to the current network operator platform in the non-current region so as to eliminate the region fault.
It is understood that the point of presence of the dispatch unit 104 (shown in fig. 1) may communicate with the telecommunications, mobility, etc. networks of different regions via a multi-line BGP network. Optionally, the target network operator platform corresponding to the service request may be determined according to a region and a network operator platform of the user terminal.
For example, if the user 1 is a east china telecommunication user, and the available network operator platforms corresponding to the service request of the user 1 include the east china telecommunication platform 1, the north china telecommunication platform 2, and the south china telecommunication platform 3, when the interruption position of the service request of the user 1 is a fault of the east china telecommunication platform 1 where the user 1 is currently located, and the services of the north china telecommunication platform 2 and the south china telecommunication platform 3 are normal, it may be determined that the scheduling policy is to schedule the service request of the user 1 to telecommunication platforms in other regions (not including east china), such as the north china telecommunication platform 2 and the south china telecommunication platform 3, and the service is provided to the user 1 through the telecommunication platforms in other regions (not including east china).
As a possible implementation manner, the step S403 may specifically include: if the interruption position is the current network operator platform of the current region and the current network operator platform of the non-current region is abnormal, determining that the fault type is the network operator platform fault, and if the fault type is the network operator platform fault, determining that the scheduling strategy is to schedule the service request to the non-current network operator platform of the current region to eliminate the network operator platform fault.
For example, if the user 1 is a east china telecommunication user, and the available network operator platforms corresponding to the service request of the user 1 include the east china telecommunication platform 1, the north china telecommunication platform 2, the south china telecommunication platform 3, the east china mobile platform 4, and the east china mobile platform 5, when the interruption position of the service request of the user 1 is a fault of the east china telecommunication platform 1 where the user 1 is currently located, and the services of the north china telecommunication platform 2 and the south china telecommunication platform 3 are also abnormal, it may be determined that the scheduling policy is to schedule the service request of the user 1 to other operators (not including telecommunication), such as the east china mobile platform 4 and the east china mobile platform 5, and provide services to the user 1 through other operators (not including telecommunication) platforms.
S404, controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling strategy according to the scheduling strategy.
For a specific description of S404, reference may be made to the description of relevant contents in the above embodiments, and details are not described herein.
It should be noted that, for details that are not disclosed in the scheduling method of a network service in the second embodiment of the present application, please refer to details that are disclosed in the scheduling method of a network service in the first embodiment of the present application, and details are not described here again.
In summary, according to the scheduling method of the network service in the embodiment of the present application, the type of the network fault can be determined according to the interrupt position of the service request, different interrupt positions can correspond to different fault types, and corresponding scheduling policies are automatically obtained according to the fault types, manual judgment of the fault cause and determination of the processing method are not required, which is flexible and convenient, and the accuracy is high.
On the basis of the foregoing embodiment, as shown in fig. 5, the step S304 in the foregoing embodiment of controlling, according to the scheduling policy, the corresponding network device to perform the scheduling operation corresponding to the scheduling policy may include:
s501, determining a scheduling path corresponding to the scheduling policy according to the scheduling policy.
And S502, controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling path according to the scheduling path.
It should be noted that the dispatch path refers to a path through which the service request reaches the target server. For example, if the user 1 is a user of the east China telecom, and the available areas corresponding to the service request of the user 1 include the available area 1 of the east China telecom, the available area 2 of the east China telecom, and the available area 3 of the east China telecom, when the interruption position of the service request of the user 1 is a fault of the available area 1 of the east China telecom where the user 1 is currently located, it is determined that the scheduling policy is to schedule the service request of the user 1 to other available areas of the east China telecom, such as the available area 2 of the east China telecom and the available area 3 of the east China telecom, and the user 1 is provided with services through the other available areas of the east China telecom. And determining that the corresponding scheduling path is from the user terminal of the user 1 to other available areas of the east China telecom, such as an available area 2 of the east China telecom, an available area 3 of the east China telecom, and then from the other available areas of the east China telecom to the target server according to the scheduling policy. And controlling the available area scheduling equipment of the east China telecom to schedule the service request of the user 1 from the user terminal of the user 1 to other available areas of the east China telecom according to the scheduling path.
It can be understood that, if the type of communication between the ue and the server is different, the scheduling policy of the network failure is different, and the corresponding scheduling path is different. The type of communication may include, among others, extranet and intranet.
For example, if the ue and the server communicate through the external network, the scheduling path is shown in fig. 6. The external network DNS unit 601 (Domain Name System) is configured to resolve an IP address of the user terminal 101 corresponding to the service request, and the internal Domain Name unit 602 is configured to determine an IP address of the target server 603 according to the service request. The monitoring unit 103 is configured to monitor whether a network service at a preset node on a scheduling path fails, specifically, the monitoring unit 103 may be configured to monitor abnormal conditions of a point of presence and a target server 603, and send monitoring information to the internal domain name unit 602, where if the network service fails, the internal domain name unit 602 may determine a scheduling policy and perform a scheduling operation.
Alternatively, if the user terminal and the server communicate via an intranet, the scheduling path at this time is as shown in fig. 7. The intranet DNS unit 604 is configured to resolve an IP address of the user terminal 101 corresponding to the service request, and the internal domain name unit 602 is configured to determine an IP address of the target server 603 according to the service request. The monitoring unit 103 is configured to monitor whether a network service at a preset node on the scheduling path fails, and specifically, the monitoring unit 103 may be configured to monitor abnormal conditions of a point of presence and a target server 603, and send monitoring information to the internal domain name unit 602, where if the network service fails, the internal domain name unit 602 may determine a scheduling policy and perform a scheduling operation. Alternatively, the intranet DNS unit 604 may be SDNS (Secure Domain Name Server), and may automatically forward the service request to the VIP (host IP) of the machine room where the target Server 603 is located.
Therefore, the method can determine the corresponding scheduling path according to the scheduling strategy, and different scheduling strategies can correspond to different scheduling paths, so that the scheduling paths are closer to the actual scheduling requirement and are more flexible and accurate.
Fig. 8 is a block diagram of a scheduling apparatus of a network service according to a first embodiment of the present application.
As shown in fig. 8, a scheduling apparatus 800 for a network service according to an embodiment of the present application includes: a first obtaining module 801, a second obtaining module 802, a first determining module 803 and an executing module 804.
The first obtaining module 801 is configured to obtain a service request.
The second obtaining module 802 is configured to obtain network service monitoring information corresponding to the service request, where the network service monitoring information includes an identifier of whether the service request reaches a target server and an interrupt location of the service request.
The first determining module 803 is configured to determine, according to the interruption position, a scheduling policy corresponding to the network fault if it is determined that the network fault occurs according to the identifier.
The executing module 804 is configured to control, according to the scheduling policy, a corresponding network device to execute a scheduling operation corresponding to the scheduling policy.
In an embodiment of the present application, as shown in fig. 9, the first determining module 803 includes: a first determining unit 8031, configured to determine a fault type corresponding to the network fault according to the interruption position; and a second determining unit 8032, configured to determine the scheduling policy according to the fault type.
In an embodiment of the present application, the first determining unit 8031 is specifically configured to determine that the fault type is a network protocol fault if the interruption position is a user terminal.
In an embodiment of the application, the second determining unit 8032 is specifically configured to determine that the scheduling policy is to replace a current network protocol with a preset standby network protocol if the failure type is the network protocol failure.
In an embodiment of the present application, the first determining unit 8031 is specifically configured to determine that the fault type is an available area fault if the interruption position is a current available area of a network.
In an embodiment of the application, the second determining unit 8032 is specifically configured to determine that the scheduling policy is to schedule the service request to another available area under a current network operator platform of a current area if the failure type is the available area failure.
In an embodiment of the application, the first determining unit 8031 is specifically configured to determine that the fault type is a region fault if the interruption position is a current network operator platform in a current region, and the current network operator platform in a non-current region is normal.
In an embodiment of the application, the second determining unit 8032 is specifically configured to determine that the scheduling policy is to schedule the service request to the current network operator platform in a non-current region, if the fault type is the region fault.
In an embodiment of the application, the first determining unit 8031 is specifically configured to determine that the fault type is a network operator platform fault if the interruption position is a current network operator platform in a current region and the current network operator platform in a non-current region is abnormal.
In an embodiment of the application, the second determining unit 8032 is specifically configured to determine that the scheduling policy is to schedule the service request to a non-current network operator platform in the current region if the fault type is the network operator platform fault.
In an embodiment of the present application, as shown in fig. 9, the executing module 804 includes: a third determining unit 8041, configured to determine, according to the scheduling policy, a scheduling path corresponding to the scheduling policy; and an execution unit 8042, configured to control, according to the scheduling path, a corresponding network device to execute a scheduling operation corresponding to the scheduling path.
According to the scheduling device of the network service, after the network fault is determined, the scheduling strategy can be automatically obtained according to the interrupt position of the service request, and the scheduling operation is executed.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 10 is a block diagram of an electronic device according to an embodiment of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 10, the electronic apparatus includes: one or more processors 901, memory 902, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor 901 may process instructions for execution within the electronic device, including instructions stored in or on a memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to an interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). Fig. 10 illustrates an example of a processor 901.
The memory 902, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the scheduling method of the web service in the embodiment of the present application (for example, the first obtaining module 801, the second obtaining module 802, the first determining module 803, and the executing module 804 shown in fig. 8). The processor 901 executes various functional applications of the server and data processing, i.e., implements the scheduling method of the network service in the above method embodiment, by running non-transitory software programs, instructions, and modules stored in the memory 902.
The memory 902 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the electronic device of the scheduling method of the network service, and the like. Further, the memory 902 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 902 may optionally include a memory remotely located from the processor 901, and these remote memories may be connected to the electronic device of the scheduling method of the network service through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the scheduling method of the network service may further include: an input device 903 and an output device 904. The processor 901, the memory 902, the input device 903, and the output device 904 may be connected by a bus or other means, and fig. 10 illustrates an example of connection by a bus.
The input device 903 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the scheduling method of the network service, such as an input device of a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, etc. The output devices 904 may include a display device, auxiliary lighting devices (e.g., LEDs), tactile feedback devices (e.g., vibrating motors), and the like. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user may provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, after the network fault is determined to occur, the scheduling strategy can be automatically obtained according to the interrupt position of the service request, and the scheduling operation is executed.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (12)
1. A method of scheduling network services, comprising:
acquiring a service request, wherein the service request is sent to a server by a user terminal;
acquiring network service monitoring information corresponding to the service request, wherein the network service monitoring information comprises an identifier of whether the service request reaches a target server and an interruption position of the service request, the interruption position comprises a user terminal, a service end and a network, the user terminal comprises a pre-established identifier for indicating whether service information provided by the service end reaches the user terminal, and the service end comprises a pre-established identifier for indicating whether the service request reaches the server;
if the network fault is determined to occur according to the identifier, determining a scheduling strategy corresponding to the network fault according to the interrupt position; and
controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling policy according to the scheduling policy,
wherein, the determining the scheduling policy corresponding to the network fault according to the interruption position includes:
determining a fault type corresponding to the network fault according to the interrupt position; and
determining the scheduling policy based on the fault type,
the determining the fault type corresponding to the network fault according to the interruption position includes:
if the interrupt position is a user terminal, determining that the fault type is a network protocol fault;
if the interruption position is the current available area of the network, determining that the fault type is an available area fault;
if the interruption position is the current network operator platform of the current region and the current network operator platform of the non-current region is normal, determining that the fault type is a region fault;
if the interruption position is the current network operator platform of the current region and the current network operator platform of the non-current region is abnormal, determining that the fault type is the network operator platform fault,
the controlling, according to the scheduling policy, the corresponding network device to execute the scheduling operation corresponding to the scheduling policy includes:
determining a scheduling path corresponding to the scheduling policy according to the scheduling policy; and
controlling the corresponding network equipment to execute the scheduling operation corresponding to the scheduling path according to the scheduling path,
wherein, if the communication types between the user terminal and the service terminal are different, the scheduling strategies of network faults are different, the corresponding scheduling paths are different, the communication types comprise an outer network and an inner network,
if the communication type between the user terminal and the server is an external network, analyzing the IP address of the user terminal corresponding to the service request through an external network DNS;
and if the communication type between the user terminal and the service end is an intranet, analyzing the IP address of the user terminal corresponding to the service request through an intranet DNS.
2. The scheduling method of claim 1, wherein said determining the scheduling policy according to the fault type comprises:
and if the fault type is the network protocol fault, determining that the scheduling strategy is to replace the current network protocol with a preset standby network protocol.
3. The scheduling method of claim 1, wherein said determining the scheduling policy according to the fault type comprises:
and if the fault type is the available area fault, determining that the scheduling strategy is to schedule the service request to other available areas under the current network operator platform of the current region.
4. The scheduling method of claim 1, wherein said determining the scheduling policy according to the fault type comprises:
and if the fault type is the region fault, determining that the scheduling strategy is to schedule the service request to the current network operator platform in the non-current region.
5. The scheduling method of claim 1, wherein said determining the scheduling policy according to the fault type comprises:
and if the fault type is the network operator platform fault, determining that the scheduling strategy is to schedule the service request to a non-current network operator platform of the current region.
6. A scheduling apparatus of a network service, comprising:
the system comprises a first acquisition module, a first service module and a second service module, wherein the first acquisition module is used for acquiring a service request, and the service request is sent to a service end by a user terminal;
a second obtaining module, configured to obtain network service monitoring information corresponding to the service request, where the network service monitoring information includes an identifier of whether the service request reaches a target server and an interrupt location of the service request, where the interrupt location includes a user terminal, a server and a network, the user terminal includes a pre-established identifier for indicating whether service information provided by the server reaches the user terminal, and the server includes a pre-established identifier for indicating whether the service request reaches the server;
a first determining module, configured to determine, if a network fault is determined to occur according to the identifier, a scheduling policy corresponding to the network fault according to the interrupt location; and
an execution module, configured to control a corresponding network device to execute a scheduling operation corresponding to the scheduling policy according to the scheduling policy,
wherein the first determining module comprises:
the first determining unit is used for determining the fault type corresponding to the network fault according to the interrupt position; and
a second determining unit for determining the scheduling policy according to the fault type,
the first determining unit is specifically configured to:
if the interrupt position is a user terminal, determining that the fault type is a network protocol fault;
if the interruption position is the current available area of the network, determining that the fault type is an available area fault;
if the interruption position is the current network operator platform of the current region and the current network operator platform of the non-current region is normal, determining that the fault type is a region fault;
if the interruption position is the current network operator platform of the current region and the current network operator platform of the non-current region is abnormal, determining that the fault type is the network operator platform fault,
the execution module includes:
a third determining unit, configured to determine, according to the scheduling policy, a scheduling path corresponding to the scheduling policy; and
an execution unit, configured to control a corresponding network device to execute a scheduling operation corresponding to the scheduling path according to the scheduling path,
wherein, if the communication types between the user terminal and the service terminal are different, the scheduling strategies of network faults are different, the corresponding scheduling paths are different, the communication types comprise an outer network and an inner network,
if the communication type between the user terminal and the server is an external network, analyzing the IP address of the user terminal corresponding to the service request through an external network DNS;
and if the communication type between the user terminal and the service end is an intranet, analyzing the IP address of the user terminal corresponding to the service request through an intranet DNS.
7. The scheduling apparatus according to claim 6, wherein the second determining unit is specifically configured to:
and if the fault type is the network protocol fault, determining that the scheduling strategy is to replace the current network protocol with a preset standby network protocol.
8. The scheduling apparatus according to claim 6, wherein the second determining unit is specifically configured to:
and if the fault type is the available area fault, determining that the scheduling strategy is to schedule the service request to other available areas under the current network operator platform of the current region.
9. The scheduling apparatus according to claim 6, wherein the second determining unit is specifically configured to:
and if the fault type is the region fault, determining that the scheduling strategy is to schedule the service request to the current network operator platform in the non-current region.
10. The scheduling apparatus according to claim 6, wherein the second determining unit is specifically configured to:
and if the fault type is the network operator platform fault, determining that the scheduling strategy is to schedule the service request to a non-current network operator platform of the current region.
11. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of scheduling of network services of any of claims 1-5.
12. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the scheduling method of a network service of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010478021.XA CN111741077B (en) | 2020-05-29 | 2020-05-29 | Network service scheduling method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010478021.XA CN111741077B (en) | 2020-05-29 | 2020-05-29 | Network service scheduling method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111741077A CN111741077A (en) | 2020-10-02 |
| CN111741077B true CN111741077B (en) | 2022-10-11 |
Family
ID=72646534
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010478021.XA Active CN111741077B (en) | 2020-05-29 | 2020-05-29 | Network service scheduling method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111741077B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112804105B (en) * | 2021-01-19 | 2023-07-11 | 上海七牛信息技术有限公司 | Method and system for rapidly repairing terminal communication faults in RTC network |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110475113A (en) * | 2018-05-09 | 2019-11-19 | 视联动力信息技术股份有限公司 | Monitoring equipment fault processing method and processing device based on view networking |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8705342B2 (en) * | 2010-10-15 | 2014-04-22 | Brookhaven Science Associates, Llc | Co-scheduling of network resource provisioning and host-to-host bandwidth reservation on high-performance network and storage systems |
| CN106209411B (en) * | 2015-05-08 | 2019-06-07 | 阿里巴巴集团控股有限公司 | Distributed network system (DNS) fault-tolerance approach, device and fault tolerant type distributed network system (DNS) |
| CN106850710B (en) * | 2015-12-03 | 2020-02-28 | 杭州海康威视数字技术股份有限公司 | Data cloud storage system, client terminal, storage server and application method |
| CN107889224B (en) * | 2016-09-29 | 2020-06-16 | 华为技术有限公司 | Method, device and system for scheduling logical channel |
| CN108769242A (en) * | 2018-06-13 | 2018-11-06 | 杭州迪普科技股份有限公司 | A kind of method for dispatching message and device |
| CN108900598B (en) * | 2018-06-26 | 2021-06-11 | 杭州朗和科技有限公司 | Network request forwarding and responding method, device, system, medium and electronic equipment |
| CN110502326A (en) * | 2019-08-27 | 2019-11-26 | 珠海格力电器股份有限公司 | The method and terminal device of cloud service scheduling and recovery based on fault detection |
| CN110995519B (en) * | 2020-02-28 | 2020-06-26 | 北京信安世纪科技股份有限公司 | Load balancing method and device |
-
2020
- 2020-05-29 CN CN202010478021.XA patent/CN111741077B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110475113A (en) * | 2018-05-09 | 2019-11-19 | 视联动力信息技术股份有限公司 | Monitoring equipment fault processing method and processing device based on view networking |
Non-Patent Citations (3)
| Title |
|---|
| A preemptive scheduling technique for OBS networks with service differentiation;H.C. Cankaya;《GLOBECOM "03. IEEE Global Telecommunications Conference (IEEE Cat. No.03CH37489)》;20040114;全文 * |
| 大规模视频监控系统网管子系统的设计与实现;林建坛等;《计算机工程与设计》;20090716(第13期);全文 * |
| 微服务故障诊断相关技术研究探讨;赵建涛等;《网络新媒体技术》;20200115(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111741077A (en) | 2020-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111835856B (en) | File downloading method, device, equipment and storage medium | |
| EP3300298A1 (en) | Method and apparatus for switching vnf | |
| CN111865688B (en) | Gateway monitoring method and device, electronic equipment and storage medium | |
| CN110765024A (en) | Simulation test method, simulation test device, electronic equipment and computer-readable storage medium | |
| WO2022127504A1 (en) | Network element management method and apparatus, and storage medium | |
| CN111683139A (en) | Method and apparatus for balancing load | |
| CN111698346B (en) | Private network address conversion method and device, private network gateway and storage medium | |
| CN112737871B (en) | Link fault detection method and device, computer equipment and storage medium | |
| CN111865682A (en) | Method and apparatus for handling faults | |
| CN111049690B (en) | Equipment fault monitoring processing method, device, equipment and storage medium | |
| CN111770176B (en) | Traffic scheduling method and device | |
| CN111741077B (en) | Network service scheduling method and device, electronic equipment and storage medium | |
| CN111371629B (en) | Network construction and out-of-band management method, device, equipment, medium and cloud platform | |
| CN106341249A (en) | Redundant port switching method and device | |
| CN115412540A (en) | Remote equipment debugging method and device, electronic equipment and storage medium | |
| CN104168200A (en) | Open vSwitch-based method and system for realizing ACL function | |
| CN112532528B (en) | Message routing method and device for rule engine | |
| CN111708940B (en) | Problem processing method, device, electronic equipment and storage medium | |
| CN111193636A (en) | Method and device for testing availability of single machine | |
| Lee et al. | Fault localization in NFV framework | |
| CN112671665B (en) | Intelligent traffic scheduling method, device, equipment and storage medium | |
| CN115225634A (en) | Data forwarding method and device under virtual network and computer program product | |
| CN112527635B (en) | Fault injection method and device, electronic equipment and storage medium | |
| CN104079440A (en) | Synchronous configuration method of primary equipment and stand-by equipment and SNMP (Simple Network Management Protocol) system | |
| CN104426704A (en) | Integration network device and service integration method thereof |
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 |