CN113778568A - Service control method and device - Google Patents
Service control method and device Download PDFInfo
- Publication number
- CN113778568A CN113778568A CN202111057255.8A CN202111057255A CN113778568A CN 113778568 A CN113778568 A CN 113778568A CN 202111057255 A CN202111057255 A CN 202111057255A CN 113778568 A CN113778568 A CN 113778568A
- Authority
- CN
- China
- Prior art keywords
- service
- service object
- access
- message
- successfully
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 142
- 230000008569 process Effects 0.000 claims abstract description 88
- 238000012544 monitoring process Methods 0.000 claims abstract description 20
- 238000013507 mapping Methods 0.000 claims description 40
- 238000004590 computer program Methods 0.000 claims description 17
- 238000003860 storage Methods 0.000 claims description 6
- 238000011161 development Methods 0.000 abstract description 10
- 230000006378 damage Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 11
- 230000004044 response Effects 0.000 description 10
- 230000001419 dependent effect Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 125000004122 cyclic group Chemical group 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000010845 search algorithm Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 125000002015 acyclic group Chemical group 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/01—Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- Evolutionary Computation (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Artificial Intelligence (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a method and a device for controlling service, wherein the method comprises the following steps: the service management object responds to a first event, creates a first service object on a first process, and starts a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the start of the first service object depends on the start of the second service object, and the second service access object is used for monitoring the running state of the second service object; when the second service access object detects that the second service object is successfully started, a first message is sent to the first service object; the first service object starts the service upon receiving the first message. The embodiment of the invention realizes the automatic control of the starting and stopping of the service object, improves the expansibility and maintainability of the dependency relationship, has low learning cost and high development efficiency for developers, and indirectly increases the safety and stability of the application.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a method and an apparatus for controlling services.
Background
With the continuous evolution of equipment, technology and the like, the requirements for function richness, high quality and the like of applications such as games and the like are higher and higher at present, taking games as an example, in order to enrich game playing methods and improve game quality, a game designer needs to design more complex logics and more game objects, and in the face of complex and dependent game objects, the dependency relationship directly influences the development progress and maintainability of the games, even the dependency maintenance among the game objects directly influences the performance of a server.
In the prior art, log output is usually performed after objects are successfully started, another platform controls the starting of dependent objects according to logs, and the interdependent relationship between the objects becomes complex with the increase of the objects, and this way becomes abnormally complex, and both the increase and the deletion of the dependency relationship require extra work, so that the expansibility and the maintainability are poor, the learning cost for developers is high, and the development efficiency is influenced.
Disclosure of Invention
In view of the above, it is proposed to provide a method and apparatus for service control that overcomes or at least partially solves the above mentioned problems, comprising:
a method of service control, the method comprising:
the method comprises the steps that a service management object responds to a first event, creates a first service object on a first process, and starts a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the starting of the first service object depends on the starting of the second service object, and the second service access object is used for monitoring the running state of the second service object;
when the second service access object detects that the second service object is successfully started, a first message is sent to the first service object;
and the first service object starts service when receiving the first message.
Optionally, the method further comprises:
the service management object responds to a first event, creates a second service object on a second process, and starts a first service access object aiming at a first service object on the second process according to the dependency configuration information, wherein the first service access object is used for monitoring the running state of the first service object;
the service management object responds to a second event and sends a stop control message to the second service object;
when the first service access object detects that the first service object stops successfully, a second message is sent to the second service object;
and the second service object stops service when receiving the stop control message and receiving the second message.
Optionally, the method further comprises:
after the second service object is started successfully, registering the second service object to an application management object;
the application management object distributes the registration information of the second service object;
when the second service access object receives the registration information of the second service object, constructing access mapping information aiming at the second service object;
the second service access object detecting that the second service object is successfully started comprises:
and the second service access object judges that the second service object is successfully started under the condition that the access mapping information of the second service object is successfully constructed.
Optionally, the registration information of the second service object includes routing information of the second service object, and the access mapping information for the second service object includes a mapping relationship between a service identifier of the second service object and the routing information.
Optionally, the method further comprises:
after the first service object is successfully stopped, the first service object logs out of the application management object;
the application management object distributes a logout message of the first service object;
the first service access object deletes access mapping information for the first service object when receiving a logout message of the first service object;
the first service access object detecting that the first service object stops successfully comprises:
and when the access mapping information of the first service object is deleted successfully, the first service access object judges that the first service object stops successfully.
Optionally, the dependency configuration information is generated according to a dependency relationship link between a plurality of service objects, and the dependency configuration information includes a starting sequence between the plurality of service objects.
Optionally, the first event includes an event that an application is opened, and the second event includes an event that an application is closed.
An apparatus for service control, the apparatus comprising a service management object, a first service object, a second service object, and a second service access object for the second service object, wherein:
the service management object is used for responding to a first event, creating a first service object on a first process, and starting a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the starting of the first service object depends on the starting of the second service object, and the second service access object is used for monitoring the running state of the second service object;
the second service access object is used for sending a first message to the first service object when detecting that the second service object is successfully started;
the first service object is used for starting service when the first message is received.
An electronic device comprising a processor, a memory and a computer program stored on the memory and being executable on the processor, the computer program, when executed by the processor, implementing a method of service control as described above.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of service control as set forth above.
The embodiment of the invention has the following advantages:
in the embodiment of the invention, a first service object is created on a first process through a service management object in response to a first event, a second service access object aiming at a second service object is started on the first process according to preset dependency configuration information, the first service object is started depending on the starting of the second service object, the second service access object can monitor the running state of the second service object, and when the second service object is detected to be successfully started, a first message is sent to the first service object, and the first service object starts service when receiving the first message, so that the starting and stopping of the service object are automatically controlled, the expansibility and maintainability of dependency relationship are improved, the learning cost for developers is low, the development efficiency is high, and the safety and stability of applications are indirectly increased.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic diagram of a service architecture according to an embodiment of the present invention;
FIG. 2a is a flowchart illustrating steps of a method for controlling services according to an embodiment of the present invention;
FIG. 2b is a directed acyclic graph of dependency links according to an embodiment of the present invention;
FIG. 2c is a schematic diagram of a service initiation sequence according to an embodiment of the present invention;
FIG. 2d is a schematic diagram of a service termination sequence according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating steps of a service initiation instance according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating steps of an example service suspension provided by an embodiment of the present invention;
fig. 5 is a flowchart illustrating steps of another method for controlling services according to an embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In order to realize automatic control of starting and stopping of a Service object, a new Service architecture is proposed according to a dependency relationship between the starting and stopping of the Service object, the Service architecture logically encapsulates various Service objects in a server (such as a game server) and provides a structure of starting and stopping control, state maintenance and Service access of the Service object for the encapsulated Service object, as shown in fig. 1, the Service architecture may be provided with an application management object (AppManager), a Service management object (ServiceManager), a Service access object (serviceaccess), and a Service object (Service).
The application management object may be a game management object (GameManage), and the application management object mainly handles collection and distribution of process information and service object information, and when the application is started, the application may be connected to the service management object, as shown in step 102 in fig. 1, and packages the process information of the application and sends the package to the service management object, and may obtain the process information from the service management object.
The service management object mainly handles creation of the service object and changes of the monitoring service object, and is responsible for starting, stopping, state maintenance and disaster recovery management of a single service, as in step 104 in fig. 1, and the service management object may select a designated process to create a corresponding service object according to process information provided by the application management object, as in step 102 in fig. 1.
The state maintenance is mainly used for recording the creation record of a specific service object and the state of whether the service object is started correctly, and the disaster recovery management is mainly operated based on the state maintenance, for example, if one service object exits abnormally, the service management object can select a process to re-create the service object when detecting the abnormal exit.
The service object mainly handles specific service functions, provides specific application logic functions, and registers information of the service object with the application management object after the start is successful, as shown in step 101 in fig. 1.
The service access object mainly handles access to the service object, maintains specific routing information of a plurality of service objects, and after starting, acquires information of a corresponding service object from the application management object, as in step 103 in fig. 1, and constructs an access map, which may be used for accessing the service object, as in step 105 in fig. 1.
The service access object has ready (on _ ready, namely starting) and destroy (on _ destroy, namely stopping) callback methods corresponding to the service object, the ready and destroy of the service object can inform the service management object, the service management object can inform the corresponding service access object, the service access object can acquire the state of a certain service object, the change of the service access object can be packaged at the bottom layer, the ready method is called when the service access object is ready, and the destroy method is called when the service access object is destroyed.
The following describes the embodiments of the present invention in detail on the basis of the above service architecture:
referring to fig. 2a, a flowchart illustrating steps of a method for controlling a service according to an embodiment of the present invention is shown, which may specifically include the following steps:
As an example, the first event includes an event that an application is open, such as a game show.
When a first event is detected, the service management object may create a first service object on a first process, and may also create other service objects on other processes according to actual requirements when the first event is detected, for example, create a second service object on a second process, and at the same time, in order to prevent a single point of performance upper limit, the same service may start multiple service objects.
In an example, a corresponding process identifier may be configured when a process is started, and a process on which a specific service object is created may be identified by the process identifier, for example, the processes may be classified according to the process identifier, and the process creating a certain service object may be a process of a specified type.
Because there is a dependency relationship between the start and stop of the service objects, the dependency configuration information between the service objects may be generated in advance, for example, the dependency configuration information may record that the start of the service object a depends on the service object B, and the stop of the service object B depends on the service object a. According to the preset dependency configuration information, it can be determined that the starting of the first service object depends on the starting of the second service object, that is, the first service object can be started only after the second service object is started, and correspondingly, the stopping of the second service object depends on the stopping of the first service object, that is, the second service object can be stopped only after the first service object is stopped.
Moreover, since the first service object is a service object created on the first process, and the second service object is a service object created on the second process, that is, a service object which is dependent across processes is between the first service object and the second service object, a second service access object for the second service object can be started on the first process creating the first service object, and the second service access object can be used for monitoring the running state of the second service object, such as a starting situation and a stopping situation.
In an embodiment of the present invention, the dependency configuration information is generated according to a dependency relationship link between a plurality of service objects, and the dependency configuration information may include a starting sequence between the plurality of service objects.
In a specific implementation, there may be multiple sequential dependency links between different Service objects, where each link is a Directed Acyclic Graph (DAG), as shown in fig. 2b, that is, a Directed Acyclic Graph of a dependency link between multiple Service objects (Service _ A, Service _ B, Service _ C, Service _ D, Service _ E, Service _ F).
For each directed acyclic graph, the starting sequence between a plurality of Service objects can be converted, and a plurality of dependency links can be finally integrated into one starting sequence, as shown in fig. 2C, the starting sequence is Service _ B → Service _ a and Service _ E → Service _ F → Service _ C → Service _ D.
In practical applications, the dependency configuration information may be obtained according to the starting sequence among a plurality of Service objects, as shown in fig. 2C, the start of Service _ D depends on Service _ C and Service _ F, the start of Service _ F depends on Service _ E and Service _ a, the start of Service _ a depends on Service _ B, and the dependency configuration information may be as follows:
Service_D：[Service_C，Service_F]
Service_F：[Service_E，Service_A]
Service_A：[Service_B]
because of the dependency relationship, when triggering the start Service, it is necessary to ensure that all the Service objects are started in the start sequence one by one, as shown in fig. 2C, Service _ B → Service _ a and Service _ E → Service _ F → Service _ C → Service _ D, and when triggering the stop Service, it is necessary to ensure that the stop work is performed in the reverse direction of the start sequence, as shown in fig. 2D, Service _ B ← Service _ a and Service _ E ← Service _ F ← Service _ C ← Service _ D.
In an example, for a dependency relationship of a service object with possible complexity, a concise starting sequence can be obtained by converting and merging multiple directed acyclic graphs through a Depth First Search (DFS) algorithm. Specifically, the depth-first search algorithm searches along a dependent path from a starting point until a node without dependency is found, as shown in fig. 2c, the paths of the depth-first search algorithm are respectively:
Service_D->Service_C
Service_D->Service_F->Service_E
Service_D->Service_F->Service_A->Service_B
moreover, whether cyclic dependency exists can be conveniently judged through a depth-first search algorithm, because of the dependency configuration information, detection of the cyclic dependency is triggered when Service starting is triggered, if the cyclic dependency exists, starting failure is prompted, for example, the starting of Service _ a depends on Service _ B, the starting of Service _ B depends on Service _ C, and the starting of Service _ C depends on Service _ a, then such a set of dependency relationship is cyclic dependency, that is, a path of the depth search is as follows:
Service_A->Service_B->Service_C->Service_A
For the second service object, the service management object may create, in response to the first event, the second service object in the second process, and may control the starting of the second service object according to preset dependency configuration information, and the starting process of the second service object may refer to the starting process of the first service object, and may be started only after it is required to ensure that all service objects depended on by the second service object are successfully started.
Because the second service access object for monitoring the second service object is started on the first process for creating the first service object, the second service access object can monitor the starting condition of the second service object on which the first service object depends in real time under the requirement of starting the first service object.
Since a plurality of service objects may be started by the same service in order to prevent a single point of performance upper limit, that is, one or more second service objects may be started, a first message for notifying that all the second service objects have been successfully started may be sent to the first service object only when all the second service objects are successfully started, specifically, the service access object may have a ready (on _ ready, i.e., started) callback method corresponding to the service object, and the first message may be an on _ ready message.
In an embodiment of the present invention, the method may further include the following steps:
and S11, the second service object registers to the application management object after the second service object is successfully started.
The service management object may create a second service object at a second process in response to the first event, and may control the launching of the second service object according to preset dependency configuration information.
The second service object may register information related to the second service object with the application management object after the second service object is successfully started, and the registration information of the second service object may include routing information of the second service object.
Specifically, the routing information may be access addresses of service objects, each service object has a unique access address, which may include IP, PORT, and ID (identification), where IP and PORT can uniquely identify a process, and ID can access a specific service object in the process.
S12, the application management object distributes the registration information of the second service object.
After the second service object is successfully registered, the application management object may distribute registration information of the second service object, so that the second service access object for the second service object is known.
S13, the second service access object constructs access mapping information for the second service object when receiving the registration information of the second service object.
Wherein, the access mapping information may include a mapping relationship between the service identifier and the routing information.
Specifically, each service object may have a service identifier, such as a service Number (NO), when being started, where the service identifier is allocated by a service management object, and when the service access object receives registration information, the registration information carries routing information of the service object, so that it may locally construct a mapping relationship between the service identifier of the service object and the routing information.
For example, the ServiceManager _ C needs to create 2 services, and there are two corresponding mapping relationships on the local serviceaccess _ C:
NO_1：(IP_1，PORT_1，ID_1)
NO_2：(IP_2，PORT_2，ID_2)
where NO _1 and NO _2 are the creation numbers of two services assigned by the ServiceManager, and (IP, PORT, ID) is the routing information of the Service.
Accordingly, the detection by the second service access object that the second service object was successfully initiated may include:
and the second service access object judges that the second service object is successfully started under the condition that the access mapping information of the second service object is successfully constructed.
For each second service object, the second service access object may determine whether the corresponding access mapping information is successfully constructed locally, and if the construction is successful, it may determine that the second service object is successfully started, and if a plurality of second service objects exist, it may determine that the second service object is successfully started when all the access mapping information of the second service objects are constructed in the second service access object, and may send the first message to the first service object.
When the first message is received, all the second service objects which characterize the dependence of the first service object are successfully started, and then the first service object can start the service.
After the successful start, the first service object may also register with the application management object in a manner of S11-S13, so that when the first service access object for the first service object receives the registration information of the first service object, the access mapping information for the first service object is constructed, and further, the start condition of the first service object can be known to other service objects depending on the first service object.
In an example, when it is determined that the starting of a certain service object is not dependent on other service objects according to preset dependency configuration information, the logical starting may be directly performed.
In the embodiment of the invention, a first service object is created on a first process through a service management object in response to a first event, a second service access object aiming at a second service object is started on the first process according to preset dependency configuration information, the first service object is started depending on the starting of the second service object, the second service access object detects the starting condition of the second service object, and sends a first message to the first service object when all the second service objects are started successfully, and the first service object starts service when receiving the first message, so that the starting and stopping of the service object are automatically controlled, the expansibility and maintainability of dependency relationship are improved, the learning cost for developers is low, the development efficiency is high, and the safety and stability of application are indirectly increased.
The method comprises the following specific steps:
for the expansibility and maintainability of the dependency relationship:
by abstracting a set of general structures for the dependence between the service objects, the starting and stopping of the service objects are automatically controlled, the service objects can be more conveniently added and deleted, and the expansibility and the maintainability are high.
The method has low learning cost and high development efficiency for developers:
the method has the advantages that the better structure brings higher development efficiency, because the bottom layer is packaged, functional developers do not need to pay attention to the realization of the bottom layer any more, only the dependent configuration items are added in the specified files, the services with complex dependency relationships can be developed quickly, and the method is low in learning cost and high in development efficiency for developers.
For indirectly increasing the safety and stability of the application:
through the start and stop handing over of service object by general module processing, compare solitary service object and handle, can improve the stability of service, and through the dependence structurization with between the service object, conveniently carry out wrong check more, like circulation dependence for the mistake can just expose in the development process, great promotion the security and the stability of applications such as games.
An embodiment of the invention is illustrated below with reference to fig. 3:
the game management object, the Service management object, and three Service objects (Service _ A, Service _ B, Service _ C) are provided, and the dependency relationship of the three Service objects is: service _ a- > Service _ B- > Service _ C, that is, the start of Service _ a depends on the success of the start of Service _ B, and the start of Service _ B depends on the success of the start of Service _ C, that is, the start sequence should be: service _ C- > Service _ B- > Service _ a.
Due to the existence of the dependency relationship, a plurality of Service access objects (Service access _ B, ServiceAccessor _ C) are arranged, the Service access _ B is started on the process of the Service _ a for monitoring the start of the Service _ B, and the Service access _ C is started on the process of the Service _ B for monitoring the start of the Service _ C.
Step 302, when the game server is started, the ServiceManager initiates the process of the specified type to create the specified number of Service _ bs.
And step 306, directly starting logic after the Service _ C unit is created because of no dependence.
Step 307, after the logic of Service _ C is successfully started, the Service related information of Service _ C is registered to the GameManager.
Step 308, the GameManager distributes the registration information of the Service _ C, and the corresponding serviceaccesser _ C receives the corresponding registration information and constructs access mapping information locally.
In step 310, after the logic of the Service _ B unit is successfully started, the Service-related information of the Service _ B is registered with the GameManager.
Step 311, the GameManager distributes the registration information of the Service _ B, and the corresponding serviceaccesser _ B receives the corresponding registration information and constructs the access hidden information locally.
Step 313, after the logic of the Service _ a unit is successfully started, the Service-related information of the Service _ a is registered with the GameManager.
Referring to fig. 5, a flowchart illustrating steps of another method for controlling services according to an embodiment of the present invention is shown, which may specifically include the following steps:
in step 501, the service management object creates a first service object on a first process and a second service object on a second process in response to a first event.
As an example, the first event includes an event that an application is open, such as a game show.
When a first event is detected, the service management object may create a first service object on a first process and may also create a second service object on a second process, and at the same time, to prevent a single point of performance ceiling, the same service may start multiple service objects.
Step 502, the service management object starts a second service access object for a second service object on the first process according to preset dependency configuration information, and starts a first service access object for a first service object on the second process, wherein the start of the first service object depends on the start of the second service object, the first service access object is used for monitoring the running state of the first service object, and the second service access object is used for monitoring the running state of the second service object.
Because there is a dependency relationship between the start and stop of the service objects, the dependency configuration information between the service objects may be generated in advance, for example, the dependency configuration information may record that the start of the service object a depends on the service object B, and the stop of the service object B depends on the service object a. According to the preset configuration information, it can be determined that the starting of the first service object depends on the starting of the second service object, that is, the first service object can be started only after the second service object is started, and correspondingly, the stopping of the first service object depends on the opposite direction of the starting dependence, that is, the stopping of the second service object depends on the stopping of the first service object, that is, the second service object can be stopped only after the first service object is stopped.
Moreover, since the first service object is a service object created on the first process, and the second service object is a service object created on the second process, that is, a service object which is dependent across processes is between the first service object and the second service object, a second service access object for the second service object may be started on the first process creating the first service object, and the second service access object may be used to monitor the running state of the second service object, such as the starting condition and the stopping condition, and may be used to start the first service access object for the first service object on the second process creating the second service object, and the first service access object may be used to monitor the running state of the first service object, such as the starting condition and the stopping condition.
For the second service object, the service management object may create, in response to the first event, the second service object in the second process, and may control the starting of the second service object according to preset dependency configuration information, and the starting process of the second service object may refer to the starting process of the first service object, and may be started only after it is required to ensure that all service objects depended on by the second service object are successfully started.
Because the second service access object for monitoring the second service object is started on the first process for creating the first service object, the second service access object can monitor the starting condition of the second service object on which the first service object depends in real time under the requirement of starting the first service object.
Since a plurality of service objects may be started by the same service in order to prevent a single point of performance upper limit, that is, one or more second service objects may be started, a first message for notifying that all the second service objects have been successfully started may be sent to the first service object only when all the second service objects are successfully started, specifically, the service access object may have a ready (on _ ready, i.e., started) callback method corresponding to the service object, and the first message may be an on _ ready message.
When the first message is received, all the second service objects which characterize the dependence of the first service object are successfully started, and then the first service object can start the service.
In step 505, the service management object sends a stop control message to the second service object in response to the second event.
As an example, the second event may include an event of application shutdown, such as a game of chance.
When the second event is detected, the service management object may trigger stopping of the second service object that is previously created and opened, that is, may send a stop control message to the second service object, and the triggering of stopping of the service object may be triggering of destroying the service object, and the stop control message may be a destroy control message.
Because the stop of the first service object is also triggered when the detected second event occurs, that is, the stop control message may also be sent to the first service object, and according to the preset dependency configuration information, it is known that the start of the first service object depends on the start of the second service object, that is, the second service object may be started only after waiting for the start of the second service object, and accordingly, the stop of the second service object depends on the opposite direction of the start dependency, and the stop of the second service object depends on the stop of the first service object, that is, the second service object may be stopped only after waiting for the stop of the first service object.
It should be noted that the stopping of the first service object may also be triggered by other events, and is not limited to the same event as the second event that triggers the stopping of the second service object, and the stopping process of the first service object may also refer to the stopping process of the second service object, and it is necessary to ensure that all the service objects that depend on the stopping process are stopped successfully before stopping.
Since the first service access object for monitoring the first service object is also started on the second process for creating the second service object, the stop condition of the first service object can be detected by the first service access object under the requirement of stopping the second service object.
Since, in order to prevent a single point of performance upper limit, the same service may start multiple service objects, that is, the first service objects may be one or more, and when all the first service objects stop successfully, a second message for notifying that all the first service objects stop successfully may be sent to the second service object, specifically, the service access object may have a callback method of destruction (on _ destruction, i.e., stop) of the corresponding service object, and the second message may be an on _ destruction message.
In an embodiment of the present invention, the method may further include:
s21, the first service object logs off the application management object after the stop succeeds.
Since the first service object is already registered with the application management object when the first service object is created, the registration information of the first service object may include the routing information of the first service object, and the first service object may perform logout, such as deleting the registration information, to the application relationship object after the first service object stops successfully.
Specifically, the routing information may be access addresses of service objects, each service object has a unique access address, which may include IP, PORT, and ID (identification), where IP and PORT can uniquely identify a process, and ID can identify a specific service object in the process.
S22, the application management object distributes the logout message of the first service object.
Since the application management object distributes the registration information during registration, when the first service object is logged out, the registration information stored in the application management object can be destroyed, and a logging-out message for the first service object can be distributed outwards.
S23, the first service access object deletes the access mapping information for the first service object when receiving the logout message of the first service object.
Wherein, the access mapping information may include a mapping relationship between the service identifier and the routing information.
Specifically, each service object may have a service identifier, such as a service Number (NO), when being started, where the service identifier is allocated by a service management object, and when the service access object receives the registration information, a mapping relationship between the service identifier of the service object and the routing information may be locally constructed.
For example, the ServiceManager _ C needs to create 2 services, and there are two corresponding mapping relationships on the local serviceaccess _ C:
NO_1：(IP_1，PORT_1，ID_1)
NO_2：(IP_2，PORT_2，ID_2)
where NO _1 and NO _2 are the creation numbers of two services assigned by the ServiceManager, and (IP, PORT, ID) is the routing information of the Service.
Upon receiving a deregistration message of the first service object, the first service access object may delete previously constructed access mapping information for the first service object.
In an embodiment of the present invention, the detecting, by the first service access object, that the first service object is successfully stopped may include:
and the first service access object judges that the first service object stops successfully under the condition that the access mapping information of the first service object is deleted successfully.
For each first service object, the first service access object may determine whether the corresponding access mapping information is deleted successfully locally, and in the case that the deletion is successful, it may determine that the first service object is started successfully, and in the case that a plurality of first service objects exist, when the access mapping information of all the second service objects is deleted in the first service access object, it may determine that the first service object is stopped successfully, and may send a second message to the second service object.
In step 507, the second service object receives the stop control message and stops the service when receiving the second message.
After receiving the stop control message, the second service object may further determine a stop condition of the first service object that the second service object depends on when the second service object is to stop, and when the second message is received, the second service object may stop the service if all the first service objects that represent that the second service object depends on have successfully stopped.
After the stop is successful, the second service object may also log out to the application management object in the manner of S21-S23, so that when the second service access object for the second service object receives the log-out message of the second service object, the access mapping information for the second service object is deleted, and further, the stop condition of the second service object can be known to other service objects depending on the second service object.
An embodiment of the invention is illustrated below with reference to fig. 4:
the game management object, the Service management object, and three Service objects (Service _ A, Service _ B, Service _ C) are provided, and the dependency relationship of the three Service objects is: service _ a- > Service _ B- > Service _ C, since the Service stopping needs to be performed in the reverse direction of the starting sequence, that is, the Service _ C stopping depends on the Service _ B stopping success, the Service _ B stopping depends on the Service _ a stopping success, that is, the stopping sequence should be: service _ A- > Service _ B- > Service _ C.
Because of the existence of the dependency relationship, a plurality of Service access objects (serviceaccess _ A, ServiceAccessor _ B) are provided, the serviceaccess _ a is started on the process where the Service _ B is located for monitoring the logout of the Service _ a, and similarly, the serviceaccess _ B is started on the process where the Service _ C is located for monitoring the logout of the Service _ B.
Step 401, when the game server is closed, the ServiceManager initiates to destroy all units of the specified Service _ C type.
Step 402, when the game server is closed, the ServiceManager initiates to destroy all units of the specified Service _ B type.
Step 403, when the game server is closed, the ServiceManager initiates to destroy all units of the specified Service _ a type.
Step 407, after the Service _ a is destroyed successfully, the corresponding Service-related information of the Service _ a is logged out to the GameManager.
Step 408, the GameManager distributes the logout message of the Service _ a, and the corresponding serviceaccesser _ a receives the corresponding logout message and deletes the access mapping information locally.
Step 410, after the Service _ B unit is successfully logged out, it will log out the Service related information of the corresponding Service _ B to the GameManager.
Step 411, the GameManager distributes the logout message of the Service _ B, and the corresponding serviceaccesser _ B receives the corresponding logout message and deletes the access hidden information locally.
In step 413, after the Service _ C unit is successfully logged out, it will log out the Service related information of the corresponding Service _ C to the GameManager.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
An embodiment of the invention further provides a service control device.
The apparatus may include a service management object, a first service object, a second service object, and a second service access object for the second service object, wherein:
the service management object is used for responding to a first event, creating a first service object on a first process, and starting a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the starting of the first service object depends on the starting of the second service object, and the second service access object is used for monitoring the running state of the second service object;
the second service access object is used for sending a first message to the first service object when detecting that the second service object is successfully started;
the first service object is used for starting the service when receiving the first message.
In an embodiment of the present invention, the service management object is further configured to create a second service object on a second process in response to the first event, and start a first service access object for the first service object on the second process according to the dependency configuration information, where the first service access object is used to monitor a running state of the first service object;
the service management object is also used for responding to a second event and sending a stop control message to the second service object;
the apparatus may further include a first service access object for the first service object, the first service access object configured to send a second message to the second service object when detecting that the first service object stops successfully;
and the second service object is also used for stopping the service when the stop control message is received and the second message is received.
In an embodiment of the present invention, the second service object is further configured to register with the application management object after the start is successful;
the apparatus may further include an application management object for distributing registration information of the second service object;
the second service access object is also used for constructing access mapping information aiming at the second service object when the registration information of the second service object is received;
when the second service access object detects that the second service object is successfully started, the second service access object is specifically configured to:
and in the case that the access mapping information construction aiming at the second service object is successful, judging that the second service object is successfully started.
In an embodiment of the present invention, the registration information of the second service object includes routing information of the second service object, and the access mapping information for the second service object includes a mapping relationship between a service identifier of the second service object and the routing information.
In an embodiment of the present invention, the first service object is further configured to log out the application management object after the stop is successful;
the application management object is also used for distributing logout messages of the first service object;
the first service access object is also used for deleting the access mapping information aiming at the first service object when a logout message of the first service object is received;
when the first service access object detects that the first service object is successfully stopped, the first service access object is specifically configured to:
and in the case that the deletion of the access mapping information aiming at the first service object is successful, judging that the first service object stops successfully.
In an embodiment of the present invention, the dependency configuration information is generated according to a dependency relationship link between a plurality of service objects, and the dependency configuration information includes a starting sequence between the plurality of service objects.
In an embodiment of the present invention, the first event includes an event that the application is opened, and the second event includes an event that the application is closed.
In the embodiment of the invention, a first service object is created on a first process through a service management object in response to a first event, a second service access object aiming at a second service object is started on the first process according to preset dependency configuration information, the starting of the first service object depends on the starting of the second service object, the second service access object can monitor the running state of the second service object, and sends a first message to the first service object when the second service object is successfully started, and the first service object starts service when receiving the first message, so that the starting and stopping of the service object are automatically controlled, the expansibility and maintainability of the dependency relationship are improved, the learning cost for developers is low, the development efficiency is high, and the safety and stability of the application are indirectly increased.
An embodiment of the present invention also provides an electronic device, which may include a processor, a memory, and a computer program stored on the memory and capable of running on the processor, and when executed by the processor, the computer program implements the method for service control as described above.
An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, the computer program, when executed by a processor, implementing the above method for service control.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The method and apparatus for controlling services provided above are described in detail, and the principle and the implementation of the present invention are explained in detail by applying specific examples, and the description of the above examples is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A method of service control, the method comprising:
the method comprises the steps that a service management object responds to a first event, creates a first service object on a first process, and starts a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the starting of the first service object depends on the starting of the second service object, and the second service access object is used for monitoring the running state of the second service object;
when the second service access object detects that the second service object is successfully started, a first message is sent to the first service object;
and the first service object starts service when receiving the first message.
2. The method of claim 1, further comprising:
the service management object responds to a first event, creates a second service object on a second process, and starts a first service access object aiming at a first service object on the second process according to the dependency configuration information, wherein the first service access object is used for monitoring the running state of the first service object;
the service management object responds to a second event and sends a stop control message to the second service object;
when the first service access object detects that the first service object stops successfully, a second message is sent to the second service object;
and the second service object stops service when receiving the stop control message and receiving the second message.
3. The method of claim 1 or 2, further comprising:
after the second service object is started successfully, registering the second service object to an application management object;
the application management object distributes the registration information of the second service object;
when the second service access object receives the registration information of the second service object, constructing access mapping information aiming at the second service object;
the second service access object detecting that the second service object is successfully started comprises:
and the second service access object judges that the second service object is successfully started under the condition that the access mapping information of the second service object is successfully constructed.
4. The method of claim 3, wherein the registration information of the second service object comprises routing information of the second service object, and the access mapping information for the second service object comprises a mapping relationship between a service identifier and the routing information of the second service object.
5. The method of claim 2, further comprising:
after the first service object is successfully stopped, the first service object logs out of the application management object;
the application management object distributes a logout message of the first service object;
the first service access object deletes access mapping information for the first service object when receiving a logout message of the first service object;
the first service access object detecting that the first service object stops successfully comprises:
and when the access mapping information of the first service object is deleted successfully, the first service access object judges that the first service object stops successfully.
6. The method of claim 1, wherein the dependency configuration information is generated according to a dependency link between a plurality of service objects, and wherein the dependency configuration information includes a starting sequence between the plurality of service objects.
7. The method of claim 2, wherein the first event comprises an application open event and the second event comprises an application close event.
8. An apparatus for service control, the apparatus comprising a service management object, a first service object, a second service object, and a second service access object for the second service object, wherein:
the service management object is used for responding to a first event, creating a first service object on a first process, and starting a second service access object aiming at a second service object on the first process according to preset dependency configuration information, wherein the starting of the first service object depends on the starting of the second service object, and the second service access object is used for monitoring the running state of the second service object;
the second service access object is used for sending a first message to the first service object when detecting that the second service object is successfully started;
the first service object is used for starting service when the first message is received.
9. An electronic device comprising a processor, a memory, and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing a method of service control according to any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of service control according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111057255.8A CN113778568A (en) | 2021-09-09 | 2021-09-09 | Service control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111057255.8A CN113778568A (en) | 2021-09-09 | 2021-09-09 | Service control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113778568A true CN113778568A (en) | 2021-12-10 |
Family
ID=78842095
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111057255.8A Pending CN113778568A (en) | 2021-09-09 | 2021-09-09 | Service control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778568A (en) |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100318780A1 (en) * | 2009-06-10 | 2010-12-16 | International Business Machines Corporation | Hierarchical services startup sequencing |
| US20140121509A1 (en) * | 2012-10-31 | 2014-05-01 | Volcano Corporation | Dependency-Based Startup In A Multi-Modality Medical System |
| CN104010034A (en) * | 2014-05-28 | 2014-08-27 | 浪潮电子信息产业股份有限公司 | Management method for group dependence of high-availability cluster |
| CN104660694A (en) * | 2015-02-09 | 2015-05-27 | 北京博雅立方科技有限公司 | Method and apparatus for calling service |
| CN107885588A (en) * | 2017-11-21 | 2018-04-06 | 广东欧珀移动通信有限公司 | Control method, device and the storage medium and mobile terminal of application service |
| CN108121577A (en) * | 2017-12-29 | 2018-06-05 | 北京安云世纪科技有限公司 | A kind of method, equipment and mobile terminal for being optimized to system operation |
| CN108196997A (en) * | 2017-12-29 | 2018-06-22 | 北京安云世纪科技有限公司 | A kind of device, method and mobile terminal for being used to carry out application dynamic control |
| CN108418854A (en) * | 2018-01-22 | 2018-08-17 | 郑州云海信息技术有限公司 | A kind of dependence implementation method based on kubernetes |
| CN110333932A (en) * | 2019-06-13 | 2019-10-15 | 上海金融期货信息技术有限公司 | Service orchestration and relationship managing method and system based on container cloud |
| CN110704050A (en) * | 2019-10-10 | 2020-01-17 | 北京无限光场科技有限公司 | Module initialization method, device, electronic equipment and computer readable storage medium |
| CN110968327A (en) * | 2018-09-29 | 2020-04-07 | 中国电信股份有限公司 | Service system and deployment method thereof |
| CN111651319A (en) * | 2020-05-14 | 2020-09-11 | 许昌许继软件技术有限公司 | Synchronous start-stop method for monitoring system application service |
| CN111752641A (en) * | 2020-06-29 | 2020-10-09 | 深圳壹账通智能科技有限公司 | Method, device, equipment and storage medium for starting service between micro-service containers |
| CN112988281A (en) * | 2021-04-25 | 2021-06-18 | 浙江口碑网络技术有限公司 | Application starting method and device |
| CN113098960A (en) * | 2021-03-31 | 2021-07-09 | 北京三快在线科技有限公司 | Service operation method, device, server and storage medium |
| CN113127089A (en) * | 2019-12-27 | 2021-07-16 | 深圳市华胜软件技术有限公司 | Starting control method of module of service architecture and computer equipment |
-
2021
- 2021-09-09 CN CN202111057255.8A patent/CN113778568A/en active Pending
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100318780A1 (en) * | 2009-06-10 | 2010-12-16 | International Business Machines Corporation | Hierarchical services startup sequencing |
| US20140121509A1 (en) * | 2012-10-31 | 2014-05-01 | Volcano Corporation | Dependency-Based Startup In A Multi-Modality Medical System |
| CN104010034A (en) * | 2014-05-28 | 2014-08-27 | 浪潮电子信息产业股份有限公司 | Management method for group dependence of high-availability cluster |
| CN104660694A (en) * | 2015-02-09 | 2015-05-27 | 北京博雅立方科技有限公司 | Method and apparatus for calling service |
| CN107885588A (en) * | 2017-11-21 | 2018-04-06 | 广东欧珀移动通信有限公司 | Control method, device and the storage medium and mobile terminal of application service |
| CN108121577A (en) * | 2017-12-29 | 2018-06-05 | 北京安云世纪科技有限公司 | A kind of method, equipment and mobile terminal for being optimized to system operation |
| CN108196997A (en) * | 2017-12-29 | 2018-06-22 | 北京安云世纪科技有限公司 | A kind of device, method and mobile terminal for being used to carry out application dynamic control |
| CN108418854A (en) * | 2018-01-22 | 2018-08-17 | 郑州云海信息技术有限公司 | A kind of dependence implementation method based on kubernetes |
| CN110968327A (en) * | 2018-09-29 | 2020-04-07 | 中国电信股份有限公司 | Service system and deployment method thereof |
| CN110333932A (en) * | 2019-06-13 | 2019-10-15 | 上海金融期货信息技术有限公司 | Service orchestration and relationship managing method and system based on container cloud |
| CN110704050A (en) * | 2019-10-10 | 2020-01-17 | 北京无限光场科技有限公司 | Module initialization method, device, electronic equipment and computer readable storage medium |
| CN113127089A (en) * | 2019-12-27 | 2021-07-16 | 深圳市华胜软件技术有限公司 | Starting control method of module of service architecture and computer equipment |
| CN111651319A (en) * | 2020-05-14 | 2020-09-11 | 许昌许继软件技术有限公司 | Synchronous start-stop method for monitoring system application service |
| CN111752641A (en) * | 2020-06-29 | 2020-10-09 | 深圳壹账通智能科技有限公司 | Method, device, equipment and storage medium for starting service between micro-service containers |
| CN113098960A (en) * | 2021-03-31 | 2021-07-09 | 北京三快在线科技有限公司 | Service operation method, device, server and storage medium |
| CN112988281A (en) * | 2021-04-25 | 2021-06-18 | 浙江口碑网络技术有限公司 | Application starting method and device |
Non-Patent Citations (1)
| Title |
|---|
| 吴晟: "《Apache SkyWalking实战》", 北京机械工业出版社, pages: 130 - 131 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5110315B2 (en) | Virtual machine management apparatus, virtual machine management method and program | |
| CN106528224B (en) | Content updating method, server and system for Docker container | |
| JP5684946B2 (en) | Method and system for supporting analysis of root cause of event | |
| CN110941528B (en) | Log buried point setting method, device and system based on fault | |
| CN109213667B (en) | Exception handling method of Android system and electronic equipment | |
| CN111428208B (en) | Application software authorization method, device and storage medium | |
| US20110099548A1 (en) | Method, apparatus and system for making a decision about virtual machine migration | |
| CN111324423B (en) | Method and device for monitoring processes in container, storage medium and computer equipment | |
| CN106330599B (en) | Android application program network flow multithreading acquisition system and method | |
| CN109995523B (en) | Activation code management method and device and activation code generation method and device | |
| CN111711623A (en) | Data verification method and device | |
| KR102242219B1 (en) | Method and device for preventing the server from being attacked | |
| CN109543457B (en) | Method and device for controlling calling between intelligent contracts | |
| JP2016099857A (en) | Fraudulent program handling system and fraudulent program handling method | |
| KR102157208B1 (en) | Smart contract excution apparatus and vulnerability detection method | |
| CN106529281A (en) | Executable file processing method and device | |
| CN111245897A (en) | Data processing method, device, system, storage medium and processor | |
| US20140123234A1 (en) | User terminal, reliability management server, and method and program for preventing unauthorized remote operation | |
| CN108650123A (en) | Fault message recording method, device, equipment and storage medium | |
| CN113778568A (en) | Service control method and device | |
| KR20210132545A (en) | Apparatus and method for detecting abnormal behavior and system having the same | |
| CN113268206B (en) | Network target range resource hot plug implementation method and system | |
| CN116561743A (en) | Business process management method and device, storage medium and electronic equipment | |
| CN108776611B (en) | Cloud host management method and device based on cloud management platform | |
| CN117009626A (en) | Service processing method, device, equipment and storage medium of game scene |
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 |