CN108960773B - Service management method, computer device, and storage medium - Google Patents
Service management method, computer device, and storage medium Download PDFInfo
- Publication number
- CN108960773B CN108960773B CN201810686358.2A CN201810686358A CN108960773B CN 108960773 B CN108960773 B CN 108960773B CN 201810686358 A CN201810686358 A CN 201810686358A CN 108960773 B CN108960773 B CN 108960773B
- Authority
- CN
- China
- Prior art keywords
- task
- identifier
- service
- target
- execution
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application relates to a service management method, a computer device and a storage medium, because different services can access a request through a unified task to request the unified management of the service as a task, in the process of taking the service as the task to carry out the unified management, firstly, a new task object is created according to the task access request, and then a target device identifier of a target execution device is determined according to the current load information of a device type corresponding to the service identifier; and finally, the task identifier and the scheduling parameter are sent to the target execution equipment corresponding to the target equipment identifier, so that the target execution equipment executes the service corresponding to the service identifier according to the scheduling parameter. Therefore, different services do not need to be managed and scheduled respectively, and different service management methods do not need to be developed aiming at different services, so that the human resources can be saved.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a service management method, a computer device, and a storage medium.
Background
The scheduling of traditional background services is based on a streaming scheduling. Taking the live broadcast system as an example, the broadcast needs to schedule a pull stream service, a package service, a definition service, a transit service, and the like. Because each service interface is different, each interface needs to be butted, namely different services need different interfaces, and different management modules are adopted for scheduling management of different services, so that corresponding scheduling management needs to be carried out every time a new service needs to be scheduled, and the labor is repeated.
Therefore, the traditional business management method has the problem of large human resource consumption.
Disclosure of Invention
In view of the above, it is necessary to provide a business management method, a computer device and a storage medium capable of saving human resources in view of the above technical problems.
A method of traffic management, the method comprising:
receiving a task access request, wherein the task access request carries a service identifier and a scheduling parameter;
creating a task object according to the task access request, wherein the information carried by the task object comprises: the task identifier, the service identifier and the scheduling parameter;
determining a target equipment identifier of target execution equipment according to the service identifier and the current load information of equipment of the equipment type corresponding to the service identifier;
and sending the task identifier and the scheduling parameter to the target execution equipment corresponding to the target equipment identifier.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
receiving a task access request, wherein the task access request carries a service identifier and a scheduling parameter;
creating a task object according to the task access request, wherein the information carried by the task object comprises: the task identifier, the service identifier and the scheduling parameter;
determining a target equipment identifier of target execution equipment according to the service identifier and the current load information of equipment of the equipment type corresponding to the service identifier;
and sending the task identifier and the scheduling parameter to the target execution equipment corresponding to the target equipment identifier.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
receiving a task access request, wherein the task access request carries a service identifier and a scheduling parameter;
creating a task object according to the task access request, wherein the information carried by the task object comprises: the task identifier, the service identifier and the scheduling parameter;
determining a target equipment identifier of target execution equipment according to the service identifier and the current load information of equipment of the equipment type corresponding to the service identifier;
and sending the task identifier and the scheduling parameter to the target execution equipment corresponding to the target equipment identifier.
According to the service management method, the computer equipment and the storage medium, because different services can access the request through the unified task to request the unified management of the service as a task, in the process of taking the service as the task to carry out the unified management, firstly, a new task object is created according to the task access request, and then the target equipment identifier of the target execution equipment is determined according to the current load information of the equipment type corresponding to the service identifier; and finally, the task identifier and the scheduling parameter are sent to the target execution equipment corresponding to the target equipment identifier, so that the target execution equipment executes the service corresponding to the service identifier according to the scheduling parameter. Therefore, different services do not need to be managed and scheduled respectively, and different service management methods do not need to be developed aiming at different services, so that the human resources can be saved.
Drawings
FIG. 1 is a diagram of an application environment of a method for service management in one embodiment;
FIG. 2 is a flow diagram illustrating a method for service management in one embodiment;
FIG. 3 is a basic business flow diagram of a live system in one embodiment;
fig. 4 is a timing diagram illustrating a live link implemented by a service management method in an embodiment;
FIG. 5 is a diagram of the operation of a conventional service management system;
fig. 6 is a diagram illustrating a subtask iteration in a service management method according to an embodiment;
FIG. 7 is a system architecture diagram of a method for business management, in accordance with an embodiment;
fig. 8 is a system configuration diagram of a service management method according to an embodiment;
fig. 9 is a service access timing diagram of a service management method according to an embodiment;
FIG. 10 is a timing diagram illustrating exception handling for a method of service management according to an embodiment;
FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The service management method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The service management method of the embodiment of the application can be operated on the server 104, the terminal 102 can send a task access request to the server 104 through a network, the server 104 receives the task access request, and creates a task object according to the task access request, wherein information carried by the task object includes: task identification, service identification and scheduling parameters; determining a target equipment identifier of target execution equipment according to the service identifier and the current load information of the equipment type corresponding to the service identifier; and sending the task identifier and the scheduling parameter to target execution equipment corresponding to the target equipment identifier. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, there is provided a traffic management method, including the steps of:
s202, receiving a task access request. The task access request carries a service identifier and a scheduling parameter.
The execution terminal of the service management method receives the task access request through a unified external Interface, which may be represented by an API (Application Program Interface). When the execution terminal of the service management method and the service access party are different devices, the task access request can be sent by the task access party through a uniform format, and the task access request can follow an RPC (Remote Procedure Call Protocol); when the execution terminal is a service access party, the service access party calls the service management method through a uniform format, and the step of calling the service management method is the step of receiving the task access request. The unified format includes a field representing a service identity and a field representing a scheduling parameter. The field of the scheduling parameter may be denoted by msg, and the format of the msg field may be json format.
In this embodiment, the service includes services corresponding to various services in live broadcast, such as a streaming service, a transcoding and packaging service, a transcoding and definition service, a forwarding service, a distribution service, and a forwarding and broadcasting service. These services can be implemented by a pull streaming service, a connect streaming service, a transcoding service, a convert encapsulation service, a convert definition service, a relay service, a distribution service, and a convert on demand service, respectively. The services can be respectively deployed on different servers, can be partially or completely deployed on one server, and can be deployed on at least two different servers by the same service.
A task is a basic unit of computer execution. In this embodiment, each service is regarded as a task, and is accessed to the task management system through the task access request. Therefore, the services can be managed uniformly, and a set of corresponding service management method does not need to be correspondingly developed for each service. Thus, human resources can be saved.
A service identity is an identity that uniquely identifies a service. For example, the pull service, the connect service, the transcoding service, the forward encapsulation service, the forward definition service, the forwarding service, the distribution service and the forward multicast service have a service identifier respectively. The scheduling parameters may be passed through to the task object and then to the target execution device. The scheduling parameters may be parameters that are needed for the execution of a service. For example, the scheduling parameter in the pull service may be a pull address; the scheduling parameter in the logo service can be information such as an upper layer return source address port and the like required by the logo service; the scheduling parameter in the template service may be specific information of the template.
And S204, creating a task object according to the task access request.
After receiving the task access request, a task object may be created based on the task access request. A task object refers to an instance of a task data structure type. The information carried by the task object comprises a task identifier, a service identifier and a scheduling parameter. The task identifier can be automatically generated according to a preset rule when the task object is created. The task identifier is an identifier for uniquely identifying a task, and the task identifier may be represented by a task _ id. The service identifier may be obtained from a task access request, and the scheduling parameter may also be obtained from the task access request.
S206, determining the target equipment identification of the target execution equipment according to the service identification and the current load information of the equipment type corresponding to the service identification.
The device types comprise a stream pulling server, a stream receiving server, a transcoding server, a conversion packaging server, a conversion definition server, a transfer server, a distribution server and a conversion point broadcasting server, which respectively correspond to service identifiers for identifying a stream pulling service, a stream receiving service, a transcoding service, a conversion packaging service, a conversion definition service, a transfer service, a distribution service and a conversion point broadcasting service. The current load information of the devices may be sent by each device to the execution terminal of the service management method of this embodiment at a preset time. The number of devices of each device type may be at least 1, or a plurality of device types may be one device. The preset time may be every fixed time, or every time the load information is updated, or every fixed time, or every time the load information is updated. The service required to be completed by the task object can be determined according to the service identifier of the task object, and then the resource required to complete the task object can be determined, or the resource required to complete the service corresponding to the task object can be determined. And then, the target device identifier of the target execution device can be determined according to the required resources and the current load information of the device type corresponding to the service identifier. The target execution device refers to a device that executes the task object. The target device identifier is a device identifier of the target execution device, and the device identifier is an identifier that can uniquely identify the device, such as a network address, or a network address + port number. In this way, an execution device is allocated to the task object, that is, an execution allocation device for the service.
And S208, sending the task identifier and the scheduling parameter to the target execution equipment corresponding to the target equipment identifier.
By means of sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier, the target execution device can execute the service of the task object corresponding to the task identifier according to the scheduling parameter. In a specific embodiment, the task identifier and the scheduling parameter may be sent to the target execution device corresponding to the target device identifier through the scheduler, and the scheduler may be determined according to the service identifier. In a specific embodiment, after receiving the task identifier and the task scheduling parameter, the target execution device may store the information of the task object corresponding to the task identifier in a local file, a shared memory, a database, or the like, so that the target execution device can recover the task object information after being restarted.
According to the service management method, because different services can request to be uniformly managed as a task through uniform task access requests, in the process of uniformly managing the services as the task, firstly, a new task object is created according to the task access requests, and then, a target equipment identifier of target execution equipment is determined according to current load information of equipment types corresponding to the service identifier; and finally, the task identifier and the scheduling parameter are sent to the target execution equipment corresponding to the target equipment identifier, so that the target execution equipment executes the service corresponding to the service identifier according to the scheduling parameter. Therefore, different services do not need to be managed and scheduled respectively, and different service management methods do not need to be developed aiming at different services, so that the human resources can be saved.
In one embodiment, the device types include: at least one of a stream receiving device, a stream pulling device, a transcoding device, a stream re-broadcasting device, a distribution device, a stream definition changing device and a stream encapsulation changing device. Therefore, the service management method is applied to the live broadcast system, so that the live broadcast system has better expansibility, and meanwhile, when a new service is expanded, human resources can be saved without repeatedly developing a management method corresponding to the new service.
The basic service flow of the live broadcast system is shown in fig. 3, the front end may push the live broadcast stream from the stream source to the stream receiving server, or pull the live broadcast stream in a stream pulling manner by the stream pulling server, or obtain the live broadcast stream through the application, so as to access the live broadcast stream to the relay hub of the live broadcast system. The background can schedule various services such as a stream pulling service, a stream receiving service, a conversion packaging service, a distribution service, a transcoding service, a conversion definition service, a conversion on-demand service and the like, and finally the Content Delivery Network (CDN) is entered, and the player feeds back to the live stream to be played through the CDN to play.
In one embodiment, after accessing the service management method in the service management method of the present application, the services in the live broadcast system can be regarded as a task, and the service management method of the present application performs unified management. The live chain of the live system can be implemented by several task access requests as shown in fig. 4. Firstly, a pull service can be accessed into a service management method, then a transfer service is accessed into the service management method, then a transcoding service is accessed into the service management method, then a resolution service is accessed into the service management method, and finally a packaging service is accessed into the service management method. In the live broadcast chain, when each service is accessed to the service management method, a feedback message may be returned to the service access party.
For comparison of effects, if the service management method shown in fig. 5 is adopted, each service needs to perform service scheduling management and resource management, for example, transcoding service, a scheduler needs to select a transcoding server for task allocation, and after allocation, transcoding service needs to report current load information so that the service scheduling management can select a proper transcoding server. After the pull service, the stream receiving service, the transcoding service and the transfer service are all established, the whole live broadcast link is completed. In the service management method shown in fig. 5, each service logic needs to separately develop corresponding issuing logic and polling check logic, and when the service is increased, each service logic adopts different interfaces, so that the service logic becomes extremely complex; when the business is increased, similar new development and labor are repeated, and human resources are consumed; resource load information is calculated independently for each service, and the measurement dimension of each service is calculated independently, so that the resources and the performance of each device are difficult to be comprehensively evaluated and utilized, and material resources are wasted.
In one embodiment, in order to facilitate allocation of the task object, the method sends the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier, and then further includes: and receiving the load information of the target execution device, and updating the current load information of the target execution device according to the load information.
Based on the technical solution of this embodiment, after allocating an executing device, i.e., a target executing device, to a task object and scheduling the target executing device, the target executing device needs to report load information thereof, so as to be used as a basis for allocating the executing device to a subsequent task object. Therefore, the execution device of this embodiment needs to receive the load information reported by the target execution device, and update the current load information of the target device according to the load information. The load new information may include at least one of cpu utilization, memory utilization, network bandwidth, and number of task object bearers. Therefore, a resource management mode is provided for service management, and task objects are conveniently distributed.
In one preferred embodiment, the adaptive device obtains the load information of the target execution device, and reports the load information to the execution terminal of the service management method. That is, the execution terminal of the service management method in this embodiment receives the load information of the target execution device reported by the adaptation device, and updates the current load information of the target execution device according to the load information. The adaptive device is another device different from the target execution device, and can collect and report load information of the target execution device. The adaptive device plays a role of an intermediate agent, can collect load information of target execution equipment in an active query mode, and then reports the load information. Therefore, the function of reporting the load information can be provided for the target execution equipment which cannot report the load information autonomously, and the task objects are conveniently distributed while the stability of the system is improved.
In one embodiment, in order to facilitate allocation of the task object, the method sends the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier, and then further includes: and receiving the execution state information of each task object in the target execution equipment, and updating the current load information of the target execution equipment according to the execution state information.
Based on the technical solution of this embodiment, after allocating an executing device, that is, a target executing device, to a task object and scheduling the target executing device, the target executing device needs to report execution state information of each task object, where the execution state information includes an execution state, and the execution state includes states of task initialization, task in progress, task end, task deletion, and the like. When the execution state of the execution state information is updated from the task in progress to the task end, the target execution device releases resources required for executing the service corresponding to the task object, so that the current load information of the target execution device needs to be updated, and the subsequent task object is convenient to allocate the execution device for reference.
In one preferred embodiment, the adaptive device obtains the execution state information of each task object in the target execution device, and reports the execution state information of each task object to the execution terminal of the service management method.
In one preferred embodiment, in order to facilitate the assignment of the task object, the method sends the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier, and then further includes: receiving load information of the target execution equipment, and updating current load information of the target execution equipment according to the load information; and receiving the execution state information of each task object in the target execution equipment, and updating the current load information of the target execution equipment according to the execution state information.
In one embodiment, when the current load information of the device type corresponding to the service identifier cannot meet the resource requirement of the service corresponding to the service identifier, a new device corresponding to the device type is created, so that the number of devices of the device type is increased. And when the current load information of the equipment type corresponding to the service identifier can determine that the equipment with the quantity larger than the first preset quantity meets the resource requirement of the service corresponding to the service identifier, deleting the equipment with the second preset quantity in the equipment type so as to release the equipment with the second preset quantity, wherein the equipment with the second preset quantity can be used by the service corresponding to other equipment types. Thus, the utilization rate of resources can be improved.
In one embodiment, the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: and receiving a task execution result of the task object returned by the target execution equipment, and deleting the task object or sending the task execution result to the task access party according to the task execution result and the task identifier.
Based on the technical solution of this embodiment, after the target execution device executes the service corresponding to the task object, the target execution device needs to return an execution result of the service corresponding to the task, which is referred to as a task execution result in this embodiment. The task execution result can be determined by the target execution device according to the result obtained by the service execution. The task execution result includes a normal end and an abnormal end. When the normal operation is finished, the execution terminal of the service management method needs to delete the task object; when the abnormal end occurs, the execution terminal of the service management method needs to call the task object again for execution, and the task execution result is the abnormal end and is sent to the task access party, so that the service access party sends the task access request again, and the task object which is abnormally ended is called again. Therefore, the execution terminal of the service management method receives the task execution result of the task object returned by the target execution device, and deletes the task object according to the task identifier when the task execution result is normally finished; and when the task execution result is abnormally finished, sending the task execution result to the task access party according to the task identifier, so that the service access party resends the task access request, thereby realizing the recall of the task object which is abnormally finished.
In a preferred embodiment, in order to ensure that the task execution result of the task object returned by the target execution device can be received certainly, when the task execution result of the task object returned by the target execution device is received, the confirmation information is sent to the target execution device, so that the target execution device does not need to continue to return the task execution result. And if the target execution equipment does not receive the confirmation information, after the task execution is finished, sending a task execution result at preset time intervals until the confirmation information is received.
In one preferred embodiment, the task state and task execution result of the task state information can be represented by a field. If it is agreed that the field can use "0" to indicate that the task status is task initialization, "1" to indicate that the task status is in progress, "2" and "3" to indicate that the task status is task end, and "4" to indicate task deletion. Wherein "2" further indicates that the task is normally finished, i.e. the task execution result is normally finished; "3" indicates that the task is abnormally ended, i.e., the task execution result is an abnormal result.
It is to be understood that, in one embodiment, the creating a task object according to the task access request further includes: and returning the task identifier to the service access party. Therefore, the service access party can establish the corresponding relation between the service identifier and the task identifier, and the efficiency of service management can be improved.
In one embodiment, to facilitate management, the method sends the task identifier and the scheduling parameter to a target execution device corresponding to the target device identifier, and then further includes: receiving a task deleting request of a service access party, wherein the task deleting request carries a task identifier; and deleting the task object corresponding to the task identifier according to the task deletion request. Therefore, a task object deletion management mode is provided, namely a task object corresponding service deletion management mode is provided, the task object service management can be facilitated, and the service management convenience can be improved. It should be noted that the deletion management method is particularly suitable for the case where the service needs to be executed all the time and the result is not obtained until the task deletion request is received. In one specific embodiment, another task deleting mode is further provided, and in the embodiment, the information carried by the task object further includes task ending time. And when the task ending time is reached, deleting the task object.
Further, deleting the task object corresponding to the task identifier according to the task deletion request, wherein the method also comprises the following steps: and sending a task stopping command to the target execution equipment according to the task deleting request, wherein the task stopping command carries a task identifier.
The stop task command is a command for the control target execution device to stop executing the task object identified by the task identifier. Based on the technical solution of this embodiment, before deleting the task object corresponding to the task identifier according to the task deletion request, the execution stop command is sent to the target execution device according to the task deletion request, so that the target execution device stops executing the service corresponding to the task object, thereby avoiding a situation that the task object is deleted on the execution terminal of the service management method and the target execution device is still executing the service corresponding to the task object, and thus improving stability of service management.
Furthermore, in order to further improve the stability of the service management, deleting the task object corresponding to the task identifier according to the task deletion request includes: and receiving a task deletion success result returned by the target execution equipment, and deleting the task object corresponding to the task identifier according to the task deletion success result.
Based on the technical solution of this embodiment, through a confirmation mechanism, after the target execution device stops executing the service corresponding to the task object according to the execution stop command, a confirmation message is returned, and in this embodiment, the confirmation message is a successful task deletion result, so that it is ensured that a situation that the task object is deleted on the execution terminal of the service management method and the target execution device is still executing the service corresponding to the task object is avoided, thereby further improving the stability of service management.
In one embodiment, to facilitate management, the method sends the task identifier and the scheduling parameter to a target execution device corresponding to the target device identifier, and then further includes: receiving a task modification request of a service access party, wherein the task modification request carries a task identifier and a modification parameter; and modifying the task object corresponding to the task identifier according to the task modification parameter. Therefore, a modification management mode of the task object is provided, namely a modification management mode of the service corresponding to the task object is provided, the management of the task object service can be facilitated, and the convenience of service management can be improved.
In one embodiment, to facilitate management, the method sends the task identifier and the scheduling parameter to a target execution device corresponding to the target device identifier, and then further includes: receiving a task query request of a service access party, wherein the task query request carries a task identifier; and inquiring the task object corresponding to the task identifier according to the task identifier. Therefore, the task object query mode is provided, namely the task object corresponding service query mode is provided, the task object service management can be facilitated, and the service management convenience can be improved.
In one embodiment, the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: when the target execution device is detected to be abnormal, determining a replacement execution device according to load information before the target execution device is abnormal; and sending the task identification and the scheduling parameter of the task object executed on the target execution equipment to the replacement execution equipment.
Based on the technical scheme of the embodiment, the device state of the target execution device can be polled at regular time, and the device state comprises a normal state and an abnormal state. When the equipment state is normal, no extra operation is needed. When the device state is abnormal, the task object executed on the abnormal device needs to be migrated to other normal devices. In this embodiment, when the target execution device is checked to be abnormal, the replacement execution device is determined according to the load information before the target execution device is abnormal, and the task identifier and the scheduling parameter of the task object executed on the target execution device are sent to the replacement execution device, so that the task object executed on the abnormal device is migrated to the normal device. Therefore, the stability of the service management method can be improved. It can be understood that the replacement execution device of this embodiment is a normal device capable of bearing the task object.
In one embodiment, the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: and when the task object is checked to have no execution state information according to the task identifier, returning current load information of the equipment type corresponding to the service identifier and the service identifier, and determining the target equipment identifier of the target execution equipment.
Based on the technical scheme of the embodiment, the execution state information of the task object corresponding to each task identifier in the task list can be periodically polled and checked. The task list is a list for recording created task objects, and information of the task objects can be added to the task list when the task objects are created, so that tasks can be recovered through the task list. In this embodiment, the step of determining the target device identifier of the target execution device by returning the current load information of the device type corresponding to the service identifier and the service identifier is performed again, so as to allocate the execution device to the task object. Thus, the stability of service management can be improved.
In one embodiment, the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: and receiving execution state information of each task object in each execution device, wherein the execution state information comprises an execution state and an actual execution device identifier, and when the execution device identifier is inconsistent with the target device identifier, sending an execution stop command to the execution device corresponding to the actual execution device identifier.
The actual execution device identification is an identification that identifies the actual execution device. The actual execution device is a device that actually executes the task object. And when the actual execution equipment identifier in the received execution state information is inconsistent with the allocated target equipment identifier, indicating that an error occurs in the allocation process, sending an execution stopping command to the execution equipment corresponding to the actual execution equipment identifier, and stopping the actual execution equipment from executing the service corresponding to the task object. The execution stopping command carries a task identifier and the actual execution equipment identifier and is used for controlling the execution equipment corresponding to the actual execution equipment identifier to stop executing the task object corresponding to the task identifier. Therefore, the execution equipment is monitored, and the stability of service management is improved.
In one embodiment, the received task access request further carries a parent task identifier. The parent task identity may be a task identity of any task object created prior to the task access request. When the service corresponding to the task object identified by the task identifier is executed on the target execution device, at least one subtask object can be separated. As shown in fig. 6, in the process of separating the subtask object, a task separation request may be sent to the service access party through the target execution device, where the task separation request carries a parent task identifier; and then the service access party sends a task access request carrying a parent task identifier to the execution terminal according to the sub-task request. And the execution terminal receives the task access request carrying the parent task identifier and creates a subtask object according to the task access request. The subtask objects can be managed uniformly according to the common task management process. Therefore, a subtask object access mode is provided, and the applicability of service management is improved.
In one embodiment, the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: receiving a task maintenance request, wherein the task maintenance request carries a task identifier and maintenance operation; and executing maintenance operation on the task object corresponding to the task identifier according to the task maintenance request.
The task maintenance request is an operation and maintenance interface provided by the service management method. The maintenance operation comprises inquiring the execution state of the task object, distributing target execution equipment for the task object, recreating the task object, deleting the task object and the like. According to the technical scheme, the operation and maintenance interface for manual intervention can be provided, operation and maintenance personnel can operate conveniently, and meanwhile, the stability of service management is improved.
In one embodiment, a system framework of the service management method may include a task access layer, a task center layer, and a task execution layer, as shown in fig. 7. The task access layer comprises a task access party. And the task center layer comprises a service interface module, a task management module, a task scheduling module and a resource management module. The task execution layer comprises a node management module, execution equipment and adaptation equipment. Receiving a task access request through a service interface module; creating a task object according to the task access request through a task management module, and recording the information of the task object in a task list; and determining the target equipment identifier of the target execution equipment through the task scheduling module according to the service identifier and the current load information of the equipment type corresponding to the service identifier. Receiving load information of the target execution equipment through a resource management module, and updating current load information of the target execution equipment according to the load information; receiving execution state information of each task object in target execution equipment, and updating current load information of the target execution equipment according to the execution state information; receiving a task execution result of a task object returned by the target execution equipment; and recording the load information of each execution device in the resource list, and recording the execution state information of each execution device in the state list. And the task management module also deletes the task object according to the task execution result and the task identifier. The task management module also determines a replacement execution device according to load information before the abnormality of the target execution device when the abnormality of the target execution device is checked. The node management module also sends the task identification and the scheduling parameter of the task object executed on the target execution equipment to the replacement execution equipment.
In one specific embodiment, a system structure of the service management method may be as shown in fig. 8, and the task access layer may further include an operation and maintenance module, where the operation and maintenance module receives a task maintenance request, and the task maintenance request carries a task identifier and a maintenance operation, and performs the maintenance operation on a task object corresponding to the task identifier according to the task maintenance request.
In one embodiment, a timing chart of service access is as shown in fig. 9, where a service access party sends a task access request, a service interface module (API) receives the task access request, a task management module (TM) creates a task object according to the task access request, and returns feedback information after the task object is successfully created. And determining the target equipment identification of the target execution equipment by a scheduling management module (TS) according to the service identification of the task object created in a task management module (TM) and the current load information of the equipment type corresponding to the service identification in a resource management module (RM). After the scheduling management module (TS) determines the target equipment identifier, the node management module (NM) sends the task identifier and the scheduling parameter to the execution Equipment (EC) corresponding to the target equipment identifier.
In one embodiment, the exception handling sequence diagram is as shown in fig. 10, and the node management module (NM) periodically sends an information request to the executing device (EC), where the information request may request load information, execution status information, task execution result, device status information, and the like. The node management module (NM) may receive load information, execution status information, task execution result, device status information, and the like returned by the execution device (EC), and then the node management module (NM) may send the load information, execution status information, task execution result, device status information, and the like to the resource management module (RM) for resource management. When the task management module (TM) finds that the abnormal condition is found, the abnormal condition processing is required according to the information such as load information, execution state information, task execution result, equipment state information and the like requested to the resource management module (RM); when abnormal processing is carried out, firstly, a task object is created again, and when the task object is created, a task scheduling module (TS) determines a target device identifier according to the service identifier and the load information of the execution device in a resource management module (RM); then, a node management module (NM) sends a task identifier and a scheduling parameter to an execution device (EC) corresponding to the target device identifier so as to schedule the target execution device; and then the node management module (NM) feeds back the task issuing completion information to the scheduling management module (TS), and the scheduling management module (TS) feeds back the task recovery success information to the task management module (TM) so as to update the task management list.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing heterogeneous data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business management method.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the service management method when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the above-mentioned traffic management method.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (14)
1. A method of traffic management, the method comprising:
receiving a task access request, wherein the task access request carries a service identifier and a scheduling parameter;
creating a task object according to the task access request, wherein the information carried by the task object comprises: the task identifier, the service identifier and the scheduling parameter;
determining a target equipment identifier of target execution equipment according to the service identifier and the current load information of equipment of the equipment type corresponding to the service identifier;
sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier;
periodically polling to check the device state of the target execution device, and when the target execution device is checked to be abnormal, determining a replacement execution device according to load information before the target execution device is abnormal;
and sending the task identification and the scheduling parameter of the task object executed on the target execution equipment to the replacement execution equipment.
2. The method of claim 1, wherein the device type comprises: at least one of a stream receiving device, a stream pulling device, a transcoding device, a stream re-broadcasting device, a distribution device, a stream definition changing device and a stream encapsulation changing device.
3. The method according to claim 1, wherein the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further comprises:
receiving load information of the target execution equipment, and updating current load information of the target execution equipment according to the load information; and/or the first and/or second light-emitting diodes are arranged in the light-emitting diode,
and receiving the execution state information of each task object in the target execution equipment, and updating the current load information of the target execution equipment according to the execution state information.
4. The method according to claim 1, wherein the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further comprises:
and receiving a task execution result of the task object returned by the target execution equipment, and deleting the task object or sending the task execution result to a task access party according to the task execution result and the task identifier.
5. The method of claim 1, wherein the creating a task object according to the task access request further comprises: returning the task identifier to a service access party;
the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes: receiving a task deleting request of the service access party, wherein the task deleting request carries the task identifier; and deleting the task object corresponding to the task identifier according to the task deleting request.
6. The method according to claim 5, wherein the deleting the task object corresponding to the task identifier according to the task deletion request further comprises:
and sending a task stopping command to the target execution equipment according to the task deleting request, wherein the task stopping command carries the task identifier.
7. The method according to claim 6, wherein deleting the task object corresponding to the task identifier according to the task deletion request comprises: and receiving a task deletion success result returned by the target execution equipment, and deleting the task object corresponding to the task identifier according to the task deletion success result.
8. The method of claim 1, wherein the information carried by the task object further includes a task end time; the method further comprises the following steps: and deleting the task object when the task ending time is reached.
9. The method according to claim 1, wherein the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further comprises:
and when the task object is checked to have no execution state information according to the task identifier, returning the current load information of the equipment type corresponding to the service identifier and the service identifier, and determining the target equipment identifier of the target execution equipment.
10. The method according to claim 1, wherein the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further comprises:
and receiving execution state information of each task object in each execution device, wherein the execution state information comprises an execution state and an actual execution device identifier, and when the execution device identifier is inconsistent with the target device identifier, sending an execution stop command to the execution device corresponding to the actual execution device identifier.
11. The method of claim 1, wherein: and the receiving task access request also carries a parent task identifier.
12. The method according to any one of claims 1 to 11, wherein the sending the task identifier and the scheduling parameter to the target execution device corresponding to the target device identifier further includes:
receiving a task maintenance request, wherein the task maintenance request carries the task identifier and maintenance operation;
and executing the maintenance operation on the task object corresponding to the task identifier according to the task maintenance request.
13. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method according to any of claims 1 to 12.
14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810686358.2A CN108960773B (en) | 2018-06-28 | 2018-06-28 | Service management method, computer device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810686358.2A CN108960773B (en) | 2018-06-28 | 2018-06-28 | Service management method, computer device, and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108960773A CN108960773A (en) | 2018-12-07 |
| CN108960773B true CN108960773B (en) | 2021-12-14 |
Family
ID=64487399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810686358.2A Active CN108960773B (en) | 2018-06-28 | 2018-06-28 | Service management method, computer device, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108960773B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656689B (en) * | 2018-12-12 | 2023-07-18 | 万兴科技股份有限公司 | Task processing system and task processing method |
| CN109495579A (en) * | 2018-12-12 | 2019-03-19 | 万兴科技股份有限公司 | Task processing method, apparatus and system |
| CN109800070A (en) * | 2019-01-02 | 2019-05-24 | 深圳壹账通智能科技有限公司 | Task processing method and system |
| CN109814995A (en) * | 2019-01-04 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Method for scheduling task, device, computer equipment and storage medium |
| JP6736733B1 (en) * | 2019-07-22 | 2020-08-05 | 日東電工株式会社 | Facility abnormality action timing determination system, facility abnormality action timing determination method, and computer program |
| CN110908778B (en) * | 2019-10-10 | 2024-03-19 | 平安科技（深圳）有限公司 | Task deployment method, system and storage medium |
| CN110795244B (en) * | 2019-10-24 | 2022-07-08 | 浙江大华技术股份有限公司 | Task allocation method, device, equipment and medium |
| CN112948201B (en) * | 2019-12-10 | 2024-05-14 | 北京神州泰岳软件股份有限公司 | Automatic operation and maintenance method and system |
| CN111240857B (en) * | 2020-01-03 | 2023-02-21 | 上海瀚之友信息技术服务有限公司 | Remote service calling system and method |
| CN111614714B (en) * | 2020-04-01 | 2024-07-02 | 视联动力信息技术股份有限公司 | Data processing method and device of service system |
| CN111866531A (en) * | 2020-07-10 | 2020-10-30 | 北京达佳互联信息技术有限公司 | Live video processing method and device, electronic equipment and storage medium |
| CN113747181A (en) * | 2020-08-06 | 2021-12-03 | 上海达龙信息科技有限公司 | Network live broadcast method, live broadcast system and electronic equipment based on remote desktop |
| CN112232751A (en) * | 2020-09-03 | 2021-01-15 | 微民保险代理有限公司 | Service data processing method, device, system, computer equipment and storage medium |
| CN113051019A (en) * | 2021-03-31 | 2021-06-29 | 北京和信融慧信息科技有限公司 | Flow task execution control method, device and equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657367A (en) * | 2016-12-30 | 2017-05-10 | 北京三快在线科技有限公司 | Service data acquisition method, device and system |
| CN106708976A (en) * | 2016-12-07 | 2017-05-24 | 安徽尚果信息科技有限公司 | Method for managing businesses via standard data interface |
| CN106850759A (en) * | 2016-12-31 | 2017-06-13 | 广州勤加缘科技实业有限公司 | MySQL database clustering methods and its processing system |
-
2018
- 2018-06-28 CN CN201810686358.2A patent/CN108960773B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106708976A (en) * | 2016-12-07 | 2017-05-24 | 安徽尚果信息科技有限公司 | Method for managing businesses via standard data interface |
| CN106657367A (en) * | 2016-12-30 | 2017-05-10 | 北京三快在线科技有限公司 | Service data acquisition method, device and system |
| CN106850759A (en) * | 2016-12-31 | 2017-06-13 | 广州勤加缘科技实业有限公司 | MySQL database clustering methods and its processing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108960773A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108960773B (en) | Service management method, computer device, and storage medium | |
| CN108958920B (en) | Distributed task scheduling method and system | |
| WO2021233391A1 (en) | Routing information sending method, routing information receiving method, network element and node device | |
| US20160275123A1 (en) | Pipeline execution of multiple map-reduce jobs | |
| CN111866191A (en) | Message event distribution method, distribution platform, system and server | |
| CN111343237A (en) | Server cluster communication method, communication device and computer storage medium | |
| JP7438355B2 (en) | Node management method, device, equipment, storage medium and system | |
| CN112948174A (en) | Message processing method and device, computer equipment and storage medium | |
| CN110768873B (en) | Distributed heartbeat detection method, system and device and computer equipment | |
| CN112910723B (en) | Edge terminal management method, device, equipment and storage medium | |
| CN102984012A (en) | Management method and system for service resources | |
| CN110995617A (en) | MQTT-based data transmission method, device, computer equipment and storage medium | |
| WO2022016969A1 (en) | Data processing method and device | |
| WO2021213365A1 (en) | Data processing method based on base station group, and base station, base station system, and computer-readable medium | |
| WO2017197983A1 (en) | Traffic processing method and system, storage medium, switch | |
| CN115509756A (en) | Multi-cluster computing task submitting method and related device and equipment | |
| CN115426361A (en) | Distributed client packaging method and device, main server and storage medium | |
| CN111835797A (en) | Data processing method, device and equipment | |
| US20150244782A1 (en) | Server for distributed controller system | |
| CN115208900B (en) | Multi-cloud architecture cloud service resource scheduling method based on blockchain and game model | |
| CN111556126B (en) | Model management method, system, computer device and storage medium | |
| CN114598662A (en) | Message queue cluster federal management system and method | |
| CN113886032A (en) | Event scheduling method and device, electronic equipment and storage medium | |
| CN114579298A (en) | Resource management method, resource manager, and computer-readable storage medium | |
| CN114816866A (en) | Fault processing method and device, electronic equipment and storage medium |
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 |