CN107193659A - The system and design method of upkeep operation task - Google Patents
The system and design method of upkeep operation task Download PDFInfo
- Publication number
- CN107193659A CN107193659A CN201710376492.8A CN201710376492A CN107193659A CN 107193659 A CN107193659 A CN 107193659A CN 201710376492 A CN201710376492 A CN 201710376492A CN 107193659 A CN107193659 A CN 107193659A
- Authority
- CN
- China
- Prior art keywords
- task
- component
- groups
- group
- 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.)
- Pending
Links
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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
-
- 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/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a kind of system and method for upkeep operation task, the system includes component, task and task groups；One task groups includes the task suction parameter transmission in the implementation procedure and implementation procedure of each task at least one task, task groups control group；One task includes the component that at least one order is performed, the execution of each component of task control, and the component output parameter of previous component is passed into next component；The design method includes task groups and created and Booting sequence and component, task, task groups execution flow.The present invention is packaged based on operating process triggering from component, task, three parts of task groups.User is when developing O＆M script, it is only necessary to pay close attention to the thing done required for each step, without comprehending whole service logic, is set up and the unified operation flow of service logic, implementation process and the unification of operation by task combination mode.
Description
Technical field
The present invention relates to cloud resource administrative skill field, and in particular to a kind of system of upkeep operation task and design side
Method.
Background technology
Cloud computing contains two kinds of Main Patterns of public cloud and private clound and developing direction, and for security consideration, enterprise is more
It is ready to place the data in private clound, but again wishes that the computing resource of public cloud can be obtained simultaneously, in this case
Mixed cloud is more and more used, and public cloud and private clound are mixed and matched by it, to obtain optimal effect, this
Personalized solution is planted, has reached and has not only saved money but also the purpose of safety.
At present to public cloud and self-built computer room (private clound), either way to manage and to the actual use of resource all
No small difference is there is, for example：Server resource is typically all virtualization in publicly-owned cloud platform, and actual physics environment is not
Need to be concerned about；And in private clound, while there is physical environment and virtual environment；In private clound, automated by self-built O＆M
Job platform, CMDB (Configuration Management Database, configuration management database) systems realize pipe
Reason, it is necessary to api interface (the Application Programming provided dependent on public cloud in public cloud
Interface, application programming interface) and SDK (Software Development Kit, SDK), or
Person directly operates in public cloud background system.Either private clound or public cloud, in actual use, are required for being directed to
Traffic performance is planned cloud resource and utilized.
In cloud resource management, can typically there are a variety of operative combinations, such as resource purchase, network configuration, service arrangement
Deng, cloud resource administrative staff need to set up operating process standardized management, therefore, it is necessary to which a set of can support during flow landing
The automated job platform of the flow.
In actual cloud resource management, administrative staff safeguard that operating process is dependent on individual by script, manual mode
The experience and qualification of people, it is impossible to which the just true landing for ensureing flow is performed, and after flow is changed, operation can not also be protected
Card can accomplish synchronization, if desired for modification script service logic.When making a mistake in operation, can run into operating procedure can not yet
Backtracking, the difficulty of audit
The content of the invention
The present invention devises a kind of job task encapsulation and performs device, solves and cloud resource operating process is standardized
Technical problem.
The technical solution adopted by the present invention is：
A kind of system of upkeep operation task, the system includes component, task and task groups；One task groups includes
Task entrance ginseng in the implementation procedure and implementation procedure of each task at least one task, task groups control group
Number transmission；Component that one task is performed including at least one order, the execution of each component of task control, and will be previous
The component output parameter of component passes to next component.
Further, the component is used to encapsulate O＆M operation, including consisting of part：
Component ID, it is globally unique；
The affiliated task ID of component, it is globally unique, for associated task；
Component states；
Component content, performs the entity of the component；
Component input parameter, component performs required parameter；
Component output parameter, marker assemblies need derived variable parameter after performing, and are performed for subsequent components；
Component performing module, performs and stores execution journal by pipe method, update execution state.
Further, the task performs stream, including consisting of part for creating component：
Task ID, it is globally unique, for associated task group and component；
The affiliated task groups of task, for associated task group；
Component index, one group of tactic component ID, the execution for associated component；
Task suction parameter, for receiving and sending the parameter in task required for first invocation component；
Task execution module, is performed for control assembly, updates task status.
Further, the task groups carry out packet execution, including consisting of part to task：
Task groups ID, it is globally unique, for associated task；
Task is indexed, one group of task ID list included in the task groups；
Task groups implementation strategy, the concurrent implementation strategy of control task；
Task groups suction parameter, for receiving and creating task, task groups according to the task groups suction parameter got,
Generate corresponding task；
Task groups performing module, is performed for control task, updates task groups state.
A kind of design method of upkeep operation task, task groups carry out packet execution to task, and the design method is based on
Operating process is triggered, and component, task and task groups are packaged；The execution of each task in task groups control group
Task suction parameter transmission in journey and implementation procedure；The execution of each component of task control, and by the group of previous component
Part output parameter passes to next component；Component is packaged to O＆M operation；The design method is created including task groups
Flow is performed with Booting sequence and component, task, task groups.
Further, the task groups are created and Booting sequence step is as follows：
Step S11, web console receive user request, by ask receiving interface obtain start task groups title and
Parameter；
Step S12, according to the task groups stored in configuration DB, is created and initialization task group, task and component；
Step S13, pushes task groups ID into message queue；
Step S14, returns to task groups ID to web consoles, and web console control tasks group is performed.
Further, the component, task, task groups execution process step are as follows：
Step S21, after the completion of task groups are created and initialized, task groups ID is pushed to message team by task group controller
Row；
Step S22, task group controller reacquires task groups ID from message queue, and task group controller checks task
Group state；
Step S23, task group controller reads task ID list, and corresponding task ID is pushed to message team according to strategy
In row；
Step S24, task controller receives task ID from message queue, triggers task run, task controller inspection
Task status is looked into, component ID or the affiliated task groups ID of component are pushed in message queue by reading assembly information；
Step S25, assembly controller receives component ID from message queue, and trigger assembly operation, assembly controller is held
Row determination component state, executive module and synchronization log, after the completion of execution, refresh component states, appoint while pushing belonging to component
ID be engaged in into message queue；
Step S26, repeat step S21- step S25, until whole component, task, task groups perform flow and completed.
Further, the strategy in the step S23 includes setting same in burse mode and judgment model, burse mode
When operation task quantity, it is defeated according to the component of task last component in judgment model after the completion of a tasks carrying
Go out the task that parameter judges subsequent execution.
Further, component ID is pushed in message queue when component needs to perform in the step S24；Work as group
After the completion of part operation, then the affiliated task groups ID of component is pushed in message queue.
Further, when component, task, task groups are interacted with web consoles, in component states, task status, task
Group state synchronized refreshes.
The present invention is used for the actual landing for solving flow operations, has the beneficial effect that：
1st, execution sequence can be adjusted flexibly according to reschedualing；
2nd, flow and operation can be accomplished to correspond；
3rd, each process step can be independently executed, and be easy to problem to investigate.
Brief description of the drawings
Fig. 1 is present system structure chart embodiment one.
Fig. 2 is present system structure chart embodiment two.
Fig. 3 is that task groups of the present invention are created and Booting sequence figure.
Fig. 4 is invention components, task, task groups execution flow chart.
Embodiment
The present invention is based on operating process triggering, from component (flow execution), task (path combination), task groups (flow batch
Amount combination is performed) three parts are packaged.User is when developing O＆M script, it is only necessary to required for paying close attention to each step
The thing done, without comprehending whole service logic, is set up and the unified operation flow of service logic by task combination mode,
With implementation process and the unification of operation.Hereinafter, the present invention is further elaborated in conjunction with the accompanying drawings and embodiments.
Fig. 1 and Fig. 2 is present system structure chart, and system includes component, task, three functional modules of task groups.Each
Functional module is described as follows：
Component：For encapsulating specific O＆M operation, such as one script or an interface interchange, each component is only
It is responsible for once single operating process；The part of component is as follows：
Component ID, it is globally unique；
The affiliated task ID of component, it is globally unique, for associated task；
Component states：Special key words
Component content：The entity of the component is performed, if it is to call script that component, which is type, content is exactly script
Itself；
Component input parameter：One component performs required parameter, for example：Ssh (a Secure Shell, safety
Shell protocol) remotely connect, it is necessary to host (main frame), user (logon account), password (login password)；Particular type
Component can be made up of default parameters and custom parameter；
Component output parameter：Mark the component to need derived variable parameter after performing, performed for subsequent components；
Component performing module：Perform and execution journal is stored by pipe method, update execution state；
Component classification：, can be by following a few class (as shown in table 1, nonessential, the Yong Huyi of component clustering in programming
Can voluntarily it be extended according to design).
The component classification of table 1
Task：Stream is performed for creating component, a task includes the component that multiple orders are performed, and task control is each
The execution of component, and the implementing result (component output parameter) of previous component is passed into next component, except this it
Outside, task can also control the execution of subsequent components, pause etc. to operate, when one of component performs mistake, component states meeting
Return directly to task.
The part of task is as follows：
Task ID, it is globally unique, for associated task group and component；
The affiliated task groups of task, for associated task group；
Component index：One group of tactic component ID, the execution for associating multiple components；
Task suction parameter：For receiving and sending the parameter in task required for first invocation component；
Task execution module：Performed for control assembly, update task status.
Task groups：By multiple tasks organize together composition one task groups, task groups according to default implementation strategy,
The entrance in the implementation procedure and implementation procedure of each task in packet execution, task groups control group is carried out to task
Parameter is transmitted.The typical scene of task groups one：Batch performs multiple cloud main frames, good to cloud main frame using task+component package
Concrete operations flow, N number of cloud main frame is performed and creates N number of single task role (N is at least 1), is combined and controlled using task groups
The implementation strategy of these tasks (cloud main frame)：Multiple main frames are concurrently performed simultaneously, or first carry out which cloud main frame.
The part of task groups is as follows：
Task groups ID：It is globally unique, for associated task；
Task is indexed：One group of task ID list included in the task groups；
Task groups implementation strategy：The concurrent implementation strategy of control task；
Task groups suction parameter：For receiving and creating task, task groups can generate correspondence according to the parameter got
Task.For example：The IP of N number of cloud main frame, generates N number of task to these cloud host service functions；
Task groups performing module：Performed for control task, update task groups state.
Table 2 is status indication, has arranged the status indication communicated between component, task, task groups in advance, effect is
Combined operation is triggered by the change of status indication between functional module.Each feature capability module passes through message queue (message
Transmitting procedure in preserve message container) advice method, trigger function module start, functional module is according to the shape got
State marks to judge subsequent operation.
The status indication of table 2
| Status indication | Explanation | Module scene |
| CREATE | Create successfully | Component, task, task groups |
| INIT | Task groups complete initialization (establishment Mission Success) | Task groups |
| START | Start successfully | Component, task, task groups |
| RUNNING | In operation | Component, task, task groups |
| FAIL | Perform failure | Component, task, task groups |
| PAUSE | In pause | Task, task groups |
| DONE | Complete | Component, task, task groups |
Relied in the present invention between component, task, task groups using level, after state refreshes, push higher level ID triggerings
State synchronized, three's synchronized relation because being consistent in real time.Design method of the present invention include task groups create and Booting sequence with
And component, task, task groups perform flow, wherein task groups are created and Booting sequence is as shown in figure 3, step is as follows：
Step S11, web console receive user request, by ask receiving interface obtain start task groups title and
Parameter.
Step S12, according to the task groups stored in configuration DB, creates and initializes (INIT) task groups, task and group
Part.
Step S13, pushes task groups ID (triggering task groups are performed) into message queue.
Step S14, returns to task groups ID to web consoles, and web console control tasks group is performed.
Component, task, task groups perform flow as shown in figure 4, step is as follows：
Step S21, task groups are completed after initialization (INIT), and task groups ID is pushed to message team by task group controller
Row.
Step S22, task group controller reacquires task groups ID from message queue, and task group controller checks task
Group state.
Step S23, task group controller reads task ID list, and corresponding task ID is pushed to message team according to strategy
In row.
Task group policy includes both of which：Burse mode：Setting runs how many tasks simultaneously；Judgment model：When
After the completion of one tasks carrying, which task of subsequent execution is judged according to the output parameter of task last component.Concurrently
Pattern is adapted to batch and concurrently performs cloud main frame, and judgment model is adapted to more complicated service logic, for example：Fault detect, business are patrolled
Collect test, monitoring etc..
Step S24, task controller receives task ID from message queue, triggers task run, task controller inspection
Task status is looked into, the component ID for being currently needed for performing is pushed to message queue, if assembly operating is complete by reading assembly information
Into (success or failure), then affiliated task groups ID is pushed into message queue.
Step S25, assembly controller receives component ID from message queue, and trigger assembly operation, assembly controller is held
Row determination component state, executive module and synchronization log, are performed after completion (success or failure), are refreshed component states, are pushed away simultaneously
The affiliated task ID of sending component is into message queue.
Step S26, repeat step S21- step S25, until whole component, task, task groups perform flow and completed.
Alternatively, need in terms of message queue reliability to consider information drop-out, can one module check of isolated operation enter
Journey, when module is interior for a period of time without change, manual refreshing state, retriggered higher level's module；
Alternatively, it is necessary to refresh in each functional module state synchronized when each functional module is interacted with web, including component day
Will refresh when, push state notifying into a single message queue, using websocket (based on TCP it is a kind of newly
Procotol) real-time update page info, refreshes daily record and rolls.
Development language of the present invention includes following part：
Component, task, task groups are realized concurrently to be performed more, can be disposed by docker, queue is passed through between each functional module
Interact, module at the same level is not associated, can easily start multiple calling systems on single server, increase unit is simultaneously
Send out operational capacity reduces deployment difficulty simultaneously；
Message queue：Message informing part of the present invention can be quickly realized using the simple queues of redis, is disappeared if desired for guarantee
Breath is reliable, and rabbitmq can be used；
Backstage is stored：Task name and task binding perform data and relation data (mysql) can be used to preserve, for example：It can protect
Deposit the corresponding content for script of task；Tasks carrying data are stored using mongodb, unique using mongo insertion data generations
Key characteristics, are directly pushed the key as task ID or daily record data ID；
Tasks carrying：Ssh remote scriptings, which are performed, to be preferably used Fabric, the usable rsync of transmission file or equally makes
Realized with Fabric modules, standard http components can be used in cloud interface interchange, while needing returning result doing standardized format
Definition, keeps the uniform format of interface interchange；
websocket：Preferably use nodejs realizations.
Although the present invention is disclosed as above with preferred embodiment, it is not for limiting the present invention, any this area
Technical staff without departing from the spirit and scope of the present invention, may be by the methods and techniques content of the disclosure above to this
Inventive technique scheme makes possible variation and modification, therefore, every content without departing from technical solution of the present invention, according to this
Any simple modifications, equivalents, and modifications that the technical spirit of invention is made to above example, belong to the technology of the present invention
The protection domain of scheme.
Claims (10)
1. a kind of system of upkeep operation task, it is characterised in that the system includes component, task and task groups；One is appointed
Business group includes the task in the implementation procedure and implementation procedure of each task at least one task, task groups control group
Suction parameter is transmitted；Component that one task is performed including at least one order, the execution of each component of task control, and by before
The component output parameter of one component passes to next component.
2. a kind of system of upkeep operation task as claimed in claim 1, it is characterised in that the component is used to encapsulate O＆M
Operation, including consisting of part：
Component ID, it is globally unique；
The affiliated task ID of component, it is globally unique, for associated task；
Component states；
Component content, performs the entity of the component；
Component input parameter, component performs required parameter；
Component output parameter, marker assemblies need derived variable parameter after performing, and are performed for subsequent components；
Component performing module, performs and stores execution journal by pipe method, update execution state.
3. a kind of system of upkeep operation task as claimed in claim 1, it is characterised in that the task is used to create component
Perform stream, including consisting of part：
Task ID, it is globally unique, for associated task group and component；
The affiliated task groups of task, for associated task group；
Component index, one group of tactic component ID, the execution for associated component；
Task suction parameter, for receiving and sending the parameter in task required for first invocation component；
Task execution module, is performed for control assembly, updates task status.
4. a kind of system of upkeep operation task as claimed in claim 1, it is characterised in that the task groups are carried out to task
Packet is performed, including consisting of part：
Task groups ID, it is globally unique, for associated task；
Task is indexed, one group of task ID list included in the task groups；
Task groups implementation strategy, the concurrent implementation strategy of control task；
Task groups suction parameter, for receiving and creating task, task groups are according to the task groups suction parameter got, generation pair
Answering for task；
Task groups performing module, is performed for control task, updates task groups state.
5. a kind of design method of upkeep operation task, it is characterised in that task groups carry out packet execution, the design to task
Method is triggered based on operating process, and component, task and task groups are packaged；Each task in task groups control group
Task suction parameter transmission in implementation procedure and implementation procedure；The execution of each component of task control, and by previous group
The component output parameter of part passes to next component；Component is packaged to O＆M operation；The design method includes task
Group is created and Booting sequence and component, task, task groups execution flow.
6. a kind of design method of upkeep operation task as claimed in claim 5, it is characterised in that the task groups create and
Booting sequence step is as follows：
Step S11, web console receive user's request, start the title and parameter of task groups by asking receiving interface to obtain；
Step S12, according to the task groups stored in configuration DB, is created and initialization task group, task and component；
Step S13, pushes task groups ID into message queue；
Step S14, returns to task groups ID to web consoles, and web console control tasks group is performed.
7. a kind of design method of upkeep operation task as claimed in claim 6, it is characterised in that the component, task, appoint
It is as follows that business group performs process step：
Step S21, after the completion of task groups are created and initialized, task groups ID is pushed to message queue by task group controller；
Step S22, task group controller reacquires task groups ID from message queue, and task group controller checks task groups shape
State；
Step S23, task group controller reads task ID list, and corresponding task ID is pushed into message queue according to strategy；
Step S24, task controller receives task ID from message queue, triggers task run, and task controller inspection is appointed
Component ID or the affiliated task groups ID of component are pushed in message queue by business state, reading assembly information；
Step S25, assembly controller receives component ID from message queue, and trigger assembly operation, assembly controller execution is sentenced
Disconnected component states, executive module and synchronization log, after the completion of execution, refresh component states, while pushing the affiliated task ID of component
Into message queue；
Step S26, repeat step S21- step S25, until whole component, task, task groups perform flow and completed.
8. a kind of design method of upkeep operation task as claimed in claim 7, it is characterised in that in the step S23
Strategy includes setting in burse mode and judgment model, burse mode while when one in the quantity of operation task, judgment model
After the completion of tasks carrying, the task of subsequent execution is judged according to the component output parameter of task last component.
9. a kind of design method of upkeep operation task as claimed in claim 7, it is characterised in that in the step S24 when
When component needs to perform, component ID is pushed in message queue；After the completion of assembly operating, then by the affiliated task groups ID of component
It is pushed in message queue.
10. a kind of design method of upkeep operation task as claimed in claim 7, it is characterised in that component, task, task
When group is interacted with web consoles, refresh in component states, task status, task groups state synchronized.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710376492.8A CN107193659A (en) | 2017-05-24 | 2017-05-24 | The system and design method of upkeep operation task |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710376492.8A CN107193659A (en) | 2017-05-24 | 2017-05-24 | The system and design method of upkeep operation task |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107193659A true CN107193659A (en) | 2017-09-22 |
Family
ID=59874709
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710376492.8A Pending CN107193659A (en) | 2017-05-24 | 2017-05-24 | The system and design method of upkeep operation task |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107193659A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108763003A (en) * | 2018-05-25 | 2018-11-06 | 厦门集微科技有限公司 | A kind of test method, device and system |
| CN108848150A (en) * | 2018-06-06 | 2018-11-20 | 郑州云海信息技术有限公司 | A kind of plan target method and system in cloud management platform |
| CN109347676A (en) * | 2018-11-02 | 2019-02-15 | 杭州云霁科技有限公司 | A kind of isomery, integrated mixed cloud resource management platform |
| CN112330180A (en) * | 2020-11-17 | 2021-02-05 | 深圳市智象科技有限公司 | Automatic operating system with flexible configuration |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101464810A (en) * | 2008-12-31 | 2009-06-24 | 金蝶软件（中国）有限公司 | Service program processing method and server |
| CN102508716A (en) * | 2011-09-29 | 2012-06-20 | 用友软件股份有限公司 | Task control device and task control method |
| CN105653365A (en) * | 2016-02-22 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Task processing method and device |
| CN106156939A (en) * | 2015-04-27 | 2016-11-23 | 上海宝信软件股份有限公司 | Dispatching System based on job stream and application process |
-
2017
- 2017-05-24 CN CN201710376492.8A patent/CN107193659A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101464810A (en) * | 2008-12-31 | 2009-06-24 | 金蝶软件（中国）有限公司 | Service program processing method and server |
| CN102508716A (en) * | 2011-09-29 | 2012-06-20 | 用友软件股份有限公司 | Task control device and task control method |
| CN106156939A (en) * | 2015-04-27 | 2016-11-23 | 上海宝信软件股份有限公司 | Dispatching System based on job stream and application process |
| CN105653365A (en) * | 2016-02-22 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Task processing method and device |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108763003A (en) * | 2018-05-25 | 2018-11-06 | 厦门集微科技有限公司 | A kind of test method, device and system |
| CN108848150A (en) * | 2018-06-06 | 2018-11-20 | 郑州云海信息技术有限公司 | A kind of plan target method and system in cloud management platform |
| CN109347676A (en) * | 2018-11-02 | 2019-02-15 | 杭州云霁科技有限公司 | A kind of isomery, integrated mixed cloud resource management platform |
| CN112330180A (en) * | 2020-11-17 | 2021-02-05 | 深圳市智象科技有限公司 | Automatic operating system with flexible configuration |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107193659A (en) | The system and design method of upkeep operation task | |
| CN105139139B (en) | Data processing method and device and system for O&M audit | |
| CN105577637B (en) | Calculating equipment, method and machine readable storage medium for being communicated between secured virtual network function | |
| DE60221113T2 (en) | PROCESS AND SYSTEM FOR THE REMOTE AND MANAGEMENT OF PERSONNEL SECURITY DEVICES | |
| CN102185716B (en) | Universal management method and system for communication equipment | |
| CN113360862A (en) | Unified identity authentication system, method, electronic device and storage medium | |
| CN104253810B (en) | Safe login method and system | |
| CN104079636B (en) | A kind of Mobile Campus Network based on cloud computing | |
| CN104737177B (en) | method for providing security service | |
| CN115118705B (en) | Industrial edge management and control platform based on micro-service | |
| CN106357457A (en) | Warning test method, warning test apparatus and warning test system | |
| CN106603283A (en) | Service simulation method and device, concentrated management platform | |
| US20140282046A1 (en) | Dashboard notifications on management console during a remote control session | |
| CN106302497A (en) | The authority control method of micro services and device | |
| CN106681789A (en) | Method and device for flexible authorization of network function | |
| CN109858257A (en) | Access control method and device | |
| CN104063768A (en) | Attendance check roll call statistical system | |
| CN110601907A (en) | Large-scale networking simulation test method, device and system for satellite communication system | |
| CN105577686B (en) | LAN single-point logging method based on network controller | |
| CN101090336A (en) | Command line interface authority hierarchical method for network equipment | |
| CN106127573B (en) | A kind of lightness operation system and method | |
| CN107301100A (en) | A kind of parking lot long-range control method, device and system | |
| US9961075B2 (en) | Identity based ticketing | |
| CN109150595A (en) | A kind of network O&M instruction method for pushing | |
| CN112883313B (en) | Intelligent monitoring system for business data of credit card |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170922 |