CN106327143B - Method and apparatus for nodes in a flow - Google Patents
Method and apparatus for nodes in a flow Download PDFInfo
- Publication number
- CN106327143B CN106327143B CN201610640530.1A CN201610640530A CN106327143B CN 106327143 B CN106327143 B CN 106327143B CN 201610640530 A CN201610640530 A CN 201610640530A CN 106327143 B CN106327143 B CN 106327143B
- Authority
- CN
- China
- Prior art keywords
- node
- current node
- indication
- indication message
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure discloses a method and apparatus for a node in a flow. The method applied to the process system comprises the following steps: when the flow enters the current node, sending a first inquiry message to a service system; receiving a first indication message sent by the service system in response to the first inquiry message; when the first indication message indicates that the current node is skipped, marking the current node as a finished state; and when the current node is marked as a finished state, controlling the process to enter the next node. Therefore, the flow template can be cut through communication with a service system in the process of flow operation without changing the existing flow template, and standard actions such as rollback, skip and the like of the flow are supported, so that service handling is more flexible, and user experience is improved.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to a method and apparatus for a node in a flow.
Background
Currently, more and more enterprises implement process business by using workflow products. When some nodes in the process need to be cut in business, the current workflow products can be solved by the following three methods.
In the first method, a specific node is skipped by adding a judgment condition to the flow template. The method is essentially realized by exhaustively cutting paths on the template, and is only suitable for the flow that a small number of nodes can be cut. When the number of nodes increases, the number of judgment conditions increases exponentially, and the process drawing is abnormal and difficult.
In the second method, a new flow template is created based on the existing flow, and then a service is initiated according to the new template. This approach is also an exhaustive path in nature and cannot be tailored during the run of a process instance.
In the third method, the specific service is realized by reading the flow information and by secondary development coding. The method is completely realized by hard coding, and operations such as rollback, jump and the like cannot be executed on the flow.
Disclosure of Invention
The purpose of the disclosure is to provide a simple and easy method and device for nodes in a flow.
In order to achieve the above object, the present disclosure provides a method for a node in a flow, which is applied to a flow system. The method comprises the following steps: when the flow enters the current node, sending a first inquiry message to a service system; receiving a first indication message sent by the service system in response to the first inquiry message; when the first indication message indicates that the current node is skipped, marking the current node as a finished state; and when the current node is marked as a finished state, controlling the process to enter the next node.
Optionally, the method further comprises: executing the current node when the first indication message indicates that the current node is executed; when the current node is executed, marking the current node as a completion state.
Optionally, the method further comprises: when the current node is marked as a completion state, sending a second inquiry message to the service system; receiving a second indication message sent by the service system in response to the second inquiry message; when the second indication message indicates that the current node is skipped, marking the current node as an initialization state.
Optionally, the method further comprises: and sending the node information of each node in the process to the service system.
The present disclosure also provides a method for a node in a process, which is applied to a business system. The method comprises the following steps: receiving an inquiry message which is sent by a process system and aims at a current node of the process; when the inquiry message is received, generating an indication message according to the node information of the current node and a node indication sent by a user, wherein the indication message indicates whether the current node is skipped over or not; and sending the indication message to the flow system.
Optionally, the method further comprises: and receiving the node information of each node in the process, which is sent by the process system.
The disclosure also provides a device for the nodes in the process, which is applied to the process system. The device comprises: the first inquiry sending module is used for sending a first inquiry message to a service system when the flow enters the current node; a first indication receiving module, configured to receive a first indication message sent by the service system in response to the first query message; a first marking module, configured to mark the current node as a complete state when the first indication message indicates that the current node is skipped; and the first control module is used for controlling the process to enter the next node when the current node is marked as a finished state.
The disclosure also provides a device for the node in the process, which is applied to a business system. The device comprises: the inquiry receiving module is used for receiving an inquiry message which is sent by the process system and aims at the current node of the process; an indication generating module, configured to generate, when receiving the query message, an indication message according to the node information of the current node and a node indication sent by a user, where the indication message indicates whether to skip the current node; and the indication sending module is used for sending the indication message to the flow system.
Through the technical scheme, the starting event is added in the node of the flow and used for detecting whether the node needs to be skipped or not. Therefore, the flow template can be cut through communication with a service system in the process of flow operation without changing the existing flow template, and standard actions such as rollback, skip and the like of the flow are supported, so that service handling is more flexible, and user experience is improved.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure without limiting the disclosure. In the drawings:
FIG. 1 is a flow diagram of a method for a node in a flow provided by an exemplary embodiment;
FIG. 2 is a flow chart of a method for a node in a flow provided by another exemplary embodiment;
FIG. 3 is a flow chart of a method for a node in a flow provided by yet another exemplary embodiment;
FIG. 4 is a flow chart of a method for a node in a flow provided by an exemplary embodiment;
FIG. 5 is a block diagram of an apparatus for a node in a flow provided by an example embodiment; and
FIG. 6 is a block diagram of an apparatus for a node in a flow provided by an example embodiment.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
FIG. 1 is a flow chart of a method for a node in a flow provided by an exemplary embodiment. The method is applied to a flow system. As shown in fig. 1, the method includes the following steps.
In step S11, when the flow enters the current node, a first inquiry message is sent to the service system.
That is, at the time of the flow design, a query event is added at the beginning of a node for determining whether the node needs to skip. When the process engine pushes the process to enter the current node, the start event is synchronously called, namely, the same thread sends a first inquiry message to the service system for inquiry in the start event. Wherein the first query message is used for querying the service system whether the current node skips.
In step S12, a first indication message sent by the service system in response to the first inquiry message is received.
In the business system, node information (e.g., node ID information) of each node of the flow may be stored. On this basis, the user can send an indication for determining which nodes need to be skipped to the service system according to the needs of a specific service. When receiving the first inquiry message, the service system may determine whether the current node needs to be skipped according to the node information and the indication sent by the user, and send a first indication message to the service system. The first indication message is used for indicating whether the current node is skipped.
For example, ID information of 10 nodes in a flow template is stored in the business system. And the user determines that the 8 th node needs to be skipped according to specific service requirements, and sends a message indicating that the 8 th node is skipped to the service system. When the process enters the 8 th node, the service system receives a first inquiry message aiming at the 8 th node and sends a first indication message indicating that the 8 th node is skipped to the process system.
It can be understood that node information of all nodes in the flow template may be stored in the service system, and node information of part of nodes may also be stored. For node information stored in the traffic system, the user can indicate on its basis whether it is skipped or not. For node information not stored in the service system, the user cannot indicate whether it is skipped. Therefore, for a node determined not to be able to skip, its node information may not be stored in the service system.
In step S13, when the first indication message indicates that the current node is skipped, the current node is marked as a completed state.
In step S14, when the current node is marked as the completed state, the control flow proceeds to the next node.
Typically a node is marked as completed when it is executed to completion. In this embodiment, when the first indication message indicates that the current node is to be skipped, the current node is also marked as completed without executing the current node. Thus, the node is skipped without affecting the operation of the subsequent flow.
Through the technical scheme, the starting event is added in the node of the flow and used for detecting whether the node needs to be skipped or not. Therefore, the flow template can be cut through communication with a service system in the process of flow operation without changing the existing flow template, and standard actions such as rollback, skip and the like of the flow are supported, so that service handling is more flexible, and user experience is improved.
It will be appreciated that a start event may be added to each node in the flow template, or no start event may be added to nodes where it is determined that skipping is not allowed. Therefore, some key nodes are not queried, the steps of process operation are reduced, the reliability of process operation is improved, and the operation speed is accelerated.
Fig. 2 is a flow chart of a method for a node in a flow provided by another example embodiment. As shown in fig. 2, on the basis of fig. 1, the method may further include the following steps.
In step S15, when the first indication message indicates to execute the current node, the current node is executed.
That is, the service system indicates that the current node does not skip, and then executes the current node according to the normal flow.
In step S16, when the current node is executed completely, the current node is marked as a completed state.
Typically a node is marked as completed when it is executed, and the flow engine controls the flow to go to the next node.
In the embodiment, when the current node does not jump, the next node is automatically executed and entered, so that the normal operation of the process is ensured.
Fig. 3 is a flowchart of a method for a node in a flow provided by yet another example embodiment. As shown in fig. 3, on the basis of fig. 1, the method may further include the following steps.
In step S17, when the current node is marked as the complete status, a second query message is sent to the service system.
That is, at the time of the flow design, a query event is added at the end of a node for determining whether the node needs to be skipped. When the process engine controls the process to end the current node, asynchronously calling an end event, namely, sending a first inquiry message to the service system for inquiry in the end event by using a new thread. The second query message may be the same as the first query message, and is used to query the service system whether the current node skips. However, the second inquiry message is transmitted at a different timing from the first inquiry message. That is, when the current node is marked as complete, the query is made again to the business system.
In step S18, a second indication message sent by the service system in response to the second inquiry message is received.
When the service system receives the second inquiry for the same node, the sent second indication message may be the same as or different from the first indication message, but should indicate the same result (skip or execute).
In step S19, when the second indication message indicates that the current node is skipped, the current node is marked as an initialized state.
As described above, when the second indication message indicates that the current node is to be skipped, the previous first indication message also indicates that the current node is to be skipped, indicating that the current node has not been previously executed and is marked as a completed state. The original completion state may be maintained when the second indication message indicates execution of the current node.
Nodes that are not executed but skipped are marked as initialized in this embodiment to distinguish whether the node has been executed. Like this, when examining this business, can clearly mark to do benefit to the later stage and to the verification of business, promoted user experience.
As described above, in the service system, node information of each node of the flow may be stored. The node information may be sent by the flow system. In a further embodiment, on the basis of fig. 1, the method further comprises: and sending the node information of each node in the process to a service system.
In this embodiment, the node information may be sent by the process system to the service system before the process instance is initiated. In addition, the node information may also be any link in the process instance operation, and the process system sequentially acquires the node information of the subsequent nodes and sends the node information to the service system. The user then sends a relevant indication on the basis of the node information received by the service system. Therefore, the process system directly sends the node information to the service system, so that the information transmission is more direct and simple, and the reliability of the process operation is enhanced.
The above is a method applied on the flow system side, and correspondingly, a method applied on the business system side is described below.
FIG. 4 is a flow chart of a method for a node in a flow provided by an exemplary embodiment. The method is applied to a service system. As shown in fig. 4, the method includes the following steps.
In step S21, an inquiry message for the current node of the flow sent by the flow system is received.
In step S22, when the inquiry message is received, an instruction message is generated based on the node information of the current node and the node instruction sent by the user. The indication message indicates whether the current node is skipped.
In step S23, an instruction message is sent to the flow system.
The query message may comprise a first query message and the indication message may comprise a first indication message, corresponding to the embodiment of fig. 1. As described above, the service system may store node information of each node of the flow. On this basis, the user can send an indication for determining which nodes need to be skipped to the service system according to the needs of a specific service. Upon receiving the query message, the service system may determine whether the current node skips based on the node information and the user indication and send an indication message.
The query message may include a first query message and a second query message, and the indication message may include a first indication message and a second indication message, corresponding to the embodiment of fig. 3.
Optionally, on the basis of fig. 4, the method may further include; and receiving node information of each node in the process sent by the process system.
The methods applied to the business system and the process system correspond to each other, and the related contents are not described herein again.
Through the technical scheme, the starting event is added in the node of the flow and used for detecting whether the node needs to be skipped or not. Therefore, the flow template can be cut through communication with a service system in the process of flow operation without changing the existing flow template, and standard actions such as rollback, skip and the like of the flow are supported, so that service handling is more flexible, and user experience is improved.
The disclosure also provides a device for the nodes in the process, which is applied to the process system. FIG. 5 is a block diagram of an apparatus for a node in a flow provided by an example embodiment. As shown in fig. 5, the apparatus 10 for a node in a process may include a first query sending module 11, a first indication receiving module 12, a first marking module 13, and a first control module 14.
The first query sending module 11 is configured to send a first query message to the service system when the flow enters the current node.
The first indication receiving module 12 is configured to receive a first indication message sent by the service system in response to the first query message.
The first marking module 13 is configured to mark the current node as a completed state when the first indication message indicates that the current node is skipped.
The first control module 14 is configured to control the process to enter the next node when the current node is marked as a complete state.
Optionally, the apparatus 10 for a node in a flow may further include an execution module 15 and a second marking module 16.
The executing module 15 is configured to execute the current node when the first indication message indicates that the current node is executed.
The second marking module 16 is configured to mark the current node as a completed state when the current node is executed.
Optionally, the apparatus 10 for a node in a flow may further include a second query sending module 17, a second indication receiving module 18, and a second marking module 19.
The second query sending module 17 is configured to send a second query message to the service system when the current node is marked as a complete state.
The second indication receiving module 18 is configured to receive a second indication message sent by the service system in response to the second inquiry message.
The second marking module 19 is configured to mark the current node as an initialization state when the second indication message indicates that the current node is skipped.
Optionally, the apparatus 10 for a node in a flow may further include an information sending module.
The information sending module is used for sending the node information of each node in the process to the service system.
The disclosure also provides a device for the node in the process, which is applied to a business system. FIG. 6 is a block diagram of an apparatus for a node in a flow provided by an example embodiment. As shown in fig. 6, the apparatus 20 for a node in a flow may include an inquiry receiving module 21, an indication generating module 22, and an indication sending module 23.
The query receiving module 21 is configured to receive a query message sent by the process system and addressed to the current node of the process.
The indication generating module 22 is configured to generate an indication message according to the node information of the current node and a node indication sent by the user when the query message is received, where the indication message indicates whether to skip the current node.
The indication sending module 23 is configured to send the indication message to the flow system.
Optionally, the apparatus 20 for a node in a flow may further include an information receiving module.
The information receiving module is used for receiving the node information of each node in the process, which is sent by the process system.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Through the technical scheme, the starting event is added in the node of the flow and used for detecting whether the node needs to be skipped or not. Therefore, the flow template can be cut through communication with a service system in the process of flow operation without changing the existing flow template, and standard actions such as rollback, skip and the like of the flow are supported, so that service handling is more flexible, and user experience is improved.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that the various features described in the above embodiments may be combined in any suitable manner without departing from the scope of the invention. In order to avoid unnecessary repetition, various possible combinations will not be separately described in this disclosure.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.
Claims (10)
1. A method for a node in a process, applied to a process system, the method comprising:
when the flow enters the current node, sending a first inquiry message to a service system;
receiving a first indication message sent by the service system in response to the first inquiry message;
when the first indication message indicates that the current node is skipped, marking the current node as a finished state;
when the current node is marked as a finished state, controlling the process to enter the next node;
when the current node is marked as a completion state, sending a second inquiry message to the service system;
receiving a second indication message sent by the service system in response to the second inquiry message;
when the second indication message indicates that the current node is skipped, marking the current node as an initialization state.
2. The method of claim 1, further comprising:
executing the current node when the first indication message indicates that the current node is executed;
when the current node is executed, marking the current node as a completion state.
3. The method of claim 1, further comprising:
and sending the node information of each node in the process to the service system.
4. A method for a node in a process, applied to a business system, the method comprising:
receiving a first inquiry message which is sent by a process system and aims at a current node of the process;
when the first inquiry message is received, generating a first indication message according to the node information of the current node and a node indication sent by a user, wherein the first indication message indicates whether the current node is skipped over;
sending the first indication message to the flow system;
receiving a second inquiry message which is sent by the process system and is aimed at the current node of the process after the current node is marked as a finished state when the first indication message indicates that the current node is skipped, wherein the process system controls the process to enter the next node when the current node is marked as the finished state;
when the second inquiry message is received, generating a second indication message according to the node information of the current node and a node indication sent by a user, wherein the second indication message indicates whether the current node is skipped over;
and sending the second indication message to the process system, wherein when the second indication message indicates that the current node is skipped, the process system marks the current node as an initialization state.
5. The method of claim 4, further comprising:
and receiving the node information of each node in the process, which is sent by the process system.
6. An apparatus for a node in a process, applied to a process system, the apparatus comprising:
the first inquiry sending module is used for sending a first inquiry message to a service system when the flow enters the current node;
a first indication receiving module, configured to receive a first indication message sent by the service system in response to the first query message;
a first marking module, configured to mark the current node as a complete state when the first indication message indicates that the current node is skipped;
the first control module is used for controlling the process to enter the next node when the current node is marked as a finished state;
a second query sending module, configured to send a second query message to the service system when the current node is marked as a complete state;
a second indication receiving module, configured to receive a second indication message sent by the service system in response to the second inquiry message;
and the second marking module is used for marking the current node as an initialization state when the second indication message indicates that the current node is skipped.
7. The apparatus of claim 6, further comprising:
an execution module, configured to execute the current node when the first indication message indicates that the current node is executed;
and the second marking module is used for marking the current node as a finished state when the current node is finished.
8. The apparatus of claim 6, further comprising:
and the information sending module is used for sending the node information of each node in the process to the service system.
9. An apparatus for a node in a process, applied to a service system, the apparatus comprising:
the system comprises an inquiry receiving module, an inquiry receiving module and an inquiry processing module, wherein the inquiry receiving module is used for receiving a first inquiry message which is sent by a process system and aims at a current node of a process;
an indication generating module, configured to generate, when the first query message is received, a first indication message according to the node information of the current node and a node indication sent by a user, where the first indication message indicates whether to skip the current node;
an indication sending module, configured to send the first indication message to the flow system,
the query receiving module is further configured to receive a second query message, which is sent by the process system and is directed to the current node of the process after the current node is marked as a complete state when the first indication message indicates that the current node is skipped, where when the current node is marked as a complete state, the process system controls the process to enter a next node;
the indication generating module is further configured to generate a second indication message according to the node information of the current node and a node indication sent by a user when the second query message is received, where the second indication message indicates whether to skip the current node;
the indication sending module is further configured to send the second indication message to the process system, where when the second indication message indicates that the current node is skipped, the process system marks the current node as an initialization state.
10. The apparatus of claim 9, further comprising:
and the information receiving module is used for receiving the node information of each node in the process, which is sent by the process system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610640530.1A CN106327143B (en) | 2016-08-05 | 2016-08-05 | Method and apparatus for nodes in a flow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610640530.1A CN106327143B (en) | 2016-08-05 | 2016-08-05 | Method and apparatus for nodes in a flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106327143A CN106327143A (en) | 2017-01-11 |
| CN106327143B true CN106327143B (en) | 2020-07-31 |
Family
ID=57740816
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610640530.1A Active CN106327143B (en) | 2016-08-05 | 2016-08-05 | Method and apparatus for nodes in a flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106327143B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107506247B (en) * | 2017-08-11 | 2020-07-31 | 恒丰银行股份有限公司 | Asynchronous callback-based task processing method and device |
| CN109978486A (en) * | 2017-12-28 | 2019-07-05 | 北京京东尚科信息技术有限公司 | Method, apparatus, system and medium for Row control |
| CN109784716A (en) * | 2019-01-14 | 2019-05-21 | 北京纷扬科技有限责任公司 | The processing method and processing device of task |
| CN111199384B (en) * | 2019-12-20 | 2024-01-16 | 航天信息股份有限公司企业服务分公司 | System and method for intelligently processing business document |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902574A (en) * | 2012-09-24 | 2013-01-30 | 东软集团股份有限公司 | Cooperative processing method and device of multiple information flow nodes |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| IN2014MU01265A (en) * | 2013-04-04 | 2015-09-04 | Avaya Inc |
-
2016
- 2016-08-05 CN CN201610640530.1A patent/CN106327143B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902574A (en) * | 2012-09-24 | 2013-01-30 | 东软集团股份有限公司 | Cooperative processing method and device of multiple information flow nodes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106327143A (en) | 2017-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106327143B (en) | Method and apparatus for nodes in a flow | |
| WO2017217075A1 (en) | Software update device and software update system | |
| CN104778057A (en) | Terminal system upgrading method and device, and server | |
| CN105684382A (en) | Packet control method, switch and controller | |
| CN107729014B (en) | Page jump method and structure based on Android | |
| CN112187629B (en) | Message revocation method for 5G communication, computer device and computer-readable storage medium | |
| CN105657000A (en) | Message transmission method and device | |
| CN115242689B (en) | Vehicle-mounted gateway testing method, system and computer readable storage medium | |
| CN110597706A (en) | Method and device for testing application program interface data abnormity | |
| CN109426535B (en) | Method, storage medium, equipment and system for jumping to specified position of page | |
| CN100433651C (en) | Method and system for ensuring network managment and element configuration data consistency | |
| EP3171565B1 (en) | Methods, devices and system for netconf hello packets interaction | |
| CN107734180B (en) | Information processing method | |
| CN113691455A (en) | Routing scheduling method, device, equipment and readable storage medium | |
| CN111031063B (en) | Data transmission method and device based on family education machine | |
| CN110502574B (en) | Cross-system information synchronization method, user equipment, storage medium and device | |
| US10735616B2 (en) | Information processing device for determining whether updating the firmware of an MFP is necessary | |
| CN110768811B (en) | Method, device and system for updating YANG model file library | |
| CN108595274B (en) | Program synchronization control method, device, system, computer device and storage medium | |
| CN107809418B (en) | Autonomous binding method and system for LoRa terminal equipment | |
| CN109918082A (en) | The compiling system and method for software development | |
| CN105808288A (en) | Message push control method and device of operating system | |
| US11983539B2 (en) | Method for computing device maintenance, apparatus, storage medium and program product | |
| CN107872493B (en) | Information processing method, terminal and server | |
| CN112685613B (en) | Resource package query method and device and information processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |