CN111740862A - Design method and system for defining communication flow based on event driving - Google Patents
Design method and system for defining communication flow based on event driving Download PDFInfo
- Publication number
- CN111740862A CN111740862A CN202010565039.3A CN202010565039A CN111740862A CN 111740862 A CN111740862 A CN 111740862A CN 202010565039 A CN202010565039 A CN 202010565039A CN 111740862 A CN111740862 A CN 111740862A
- Authority
- CN
- China
- Prior art keywords
- event
- flow
- publisher
- acquiring
- calling
- 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 98
- 230000006854 communication Effects 0.000 title claims abstract description 43
- 238000004891 communication Methods 0.000 title claims abstract description 32
- 238000013461 design Methods 0.000 title claims abstract description 16
- 238000012545 processing Methods 0.000 claims description 18
- 238000012544 monitoring process Methods 0.000 claims description 7
- 238000003672 processing method Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a design method for defining a communication flow based on event driving, which belongs to the technical field of communication and comprises the following contents: s1, calling an event publisher to publish the flow events, wherein each initial event is assigned with a flow identifier; s2, calling an event listener to monitor an event and appointing an event handler; s22, updating and storing the service process state information after acquiring the corresponding information; s3, calling a corresponding event handler to process the event; and S4, calling the corresponding event publisher to process the event, judging whether the event of the next flow exists after the event of the next flow is acquired, if not, ending the flow, and if so, executing the programs S1-S4. Based on the event and the process identification, the invention gradually calls the event publisher, the event handler and the event listener to perform corresponding operations on the event publisher, the event handler and the event listener to complete the communication process, and can quickly add or change the communication process.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a design method for defining a communication flow based on event driving.
Background
In the communication process defined by the existing hardware equipment, if a function needs to be added or the process needs to be changed, the equipment needs to be upgraded or replaced, and the resource cost is very high; however, the current software-defined communication flow has much lower cost of changed resources than hardware, but lacks flexibility and requires higher labor cost and time cost.
Disclosure of Invention
The invention aims to provide a design method for defining a communication flow based on event driving, aiming at the scenes needing to rapidly add or change the communication flow, reducing the labor cost and time cost required by development and increasing the reusability of functional flow nodes.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a design method for defining a communication flow based on event driving comprises the following steps:
s1, calling an event publisher to publish the flow events, wherein each initial event is assigned with a flow identifier;
s2, invoking the event listener to monitor the event and designate an event handler, which specifically includes: s21, judging whether the event has a flow identification, if so, acquiring a corresponding event handler, and if not, acquiring the flow identification and the corresponding event handler; s22, updating and storing the service process state information after acquiring the corresponding information;
s3, invoking the corresponding event handler to process the event, which specifically includes: s31, acquiring a corresponding event publisher according to the process identification and the event; s32, updating the business process state information after acquiring the corresponding event publisher information;
s4, calling the corresponding event publisher to process the event, specifically comprising: s41, acquiring an event of the next process according to the process identification and the event; and S42, after acquiring the event of the next flow, judging whether the event of the next flow exists, if not, ending the current flow, and if so, executing the programs S1-S4.
The flow events comprise parent events and child events, and the parent events define communication main flow nodes; and the subclass event is used as an extension of the parent class event and defines a communication sub-process node.
As an option, step S2 further includes the following:
and S23, judging whether a corresponding event handler exists, if not, ending the current process, and if so, executing the next program.
As an option, step S3 further includes the following:
and S33, judging whether a corresponding event publisher exists or not, if not, ending the process, and if so, executing the next program.
Due to the adoption of the technical scheme, the invention has the following beneficial effects:
the invention defines each process node in the communication process through the event based on the event and the process identification, gradually calls the event publisher, the event handler and the event listener to perform corresponding operation on the event to complete the communication process, reduces the labor cost and the time cost required by development and increases the reusability of the functional process nodes aiming at the scenes needing to rapidly increase or change the communication process.
Drawings
FIG. 1 is a flow chart of the method of the present invention.
Fig. 2 is a state diagram of the present invention.
FIG. 3 is a process flow diagram of the present invention.
Fig. 4 is a process flow of a call example of the present invention.
Detailed Description
The following further describes the embodiments of the present invention with reference to the drawings.
Example 1
As shown in fig. 1, a design method for defining a communication flow based on event-driven according to this embodiment includes the following steps:
step S1, calling an event publisher to publish the flow events, wherein each initial event is assigned with a flow identifier;
step S2, invoking the event listener to monitor the event and designate the event handler, which specifically includes: s21, judging whether the event has a flow identification, if so, acquiring a corresponding event handler, and if not, acquiring the flow identification and the corresponding event handler; s22, updating and storing the service process state information after acquiring the corresponding information;
step S3, invoking the corresponding event handler to process the event, which specifically includes: s31, acquiring a corresponding event publisher according to the process identification and the event; s32, updating the business process state information after acquiring the corresponding event publisher information;
step S4, invoking the corresponding event publisher to process the event, which specifically includes: s41, acquiring an event of the next process according to the process identification and the event; and S42, after acquiring the event of the next flow, judging whether the event of the next flow exists, if not, ending the current flow, and if so, executing the programs S1-S4.
The flow events comprise parent events and child events, and the parent events define communication main flow nodes; and the subclass event is used as an extension of the parent class event and defines a communication sub-process node.
As an option, on the basis of the above example, in this example, step S2 further includes the following steps:
and S23, judging whether a corresponding event handler exists, if not, ending the current process, and if so, executing the next program.
As an option, on the basis of the above example, in this example, step S3 further includes the following steps:
and S33, judging whether a corresponding event publisher exists or not, if not, ending the process, and if so, executing the next program.
Please refer to fig. 2 and fig. 3, which are a specific exemplary state and processing flow diagram. The business process state is stored in a process state database. The flow configuration center configures corresponding operations of an event publisher, an event handler and an event listener respectively, and each initial event is assigned with a flow identifier. Based on the event and the process identifier, the event publisher, the event handler and the event listener are gradually called to perform corresponding operations on the event publisher, the event handler and the event listener, so as to form the processing flow shown in fig. 3. The process configuration center returns the corresponding event handler, the corresponding process identifier and the corresponding event handler, so that the monitor acquires the corresponding information; the monitoring person receives the returned updating state and the returned storage state of the flow state database before judging whether the corresponding event processing person exists. The flow configuration center returns the corresponding event publisher, so that the event handler acquires the corresponding event publisher; the processor receives the return updating state of the flow state database before judging whether the corresponding event publisher exists. And the flow configuration center returns the event of the next flow, so that the publisher acquires the event of the next flow.
As described above, the method gradually calls the event publisher, the event handler and the event listener to perform corresponding operations on the event publisher, the event handler and the event listener based on the event and the process identifier, completes the communication process, and reduces the labor cost and the time cost required for development and increases the reusability of the functional process nodes for the scene requiring rapid addition or change of the communication process.
Example 2
Based on the above embodiment 1, a system for defining a communication flow based on event-driven according to the present embodiment will be described below, and please refer to the above embodiment 1 for detailed description.
The design system for defining the communication flow based on event driving in the embodiment comprises the following contents:
a release module: the system comprises a flow identifier, a flow publisher and a flow publisher, wherein the flow identifier is used for calling the flow events to be published by the event publisher, and each initial event is assigned with a flow identifier;
a monitoring module: the method is used for calling an event listener to listen to an event and appointing an event handler, and the specific processing flow comprises the following steps: judging whether the event has a process identifier, if so, acquiring a corresponding event handler, and if not, acquiring the process identifier and the corresponding event handler; updating and storing the service process state information after acquiring the corresponding information;
a processing module: the event handler is used for calling a corresponding event handler to handle an event, and the specific processing flow comprises the following steps: acquiring a corresponding event publisher according to the process identification and the event; updating the business process state information after acquiring the corresponding event publisher information;
an end module: the event processing method is used for calling a corresponding event publisher to process an event, and the specific processing flow comprises the following steps: acquiring an event of the next process according to the process identifier and the event; and after the event of the next process is obtained, judging whether the event of the next process exists or not, if not, ending the process, and if so, executing the operation from the issuing module to the ending module.
The flow events comprise parent events and child events, the parent events define communication main flow nodes, and the child events define communication child flow nodes.
As an option, the processing flow of the monitoring module further includes the following contents: and judging whether a corresponding event handler exists or not, if not, ending the process, and if so, executing the operation of a processing module to be described later.
As an option, the processing module processing flow further includes the following: and judging whether a corresponding event publisher exists or not, if not, ending the process, and if so, executing the operation of an ending module, which is described later.
As described above, the system defines each process node in the communication process through the event based on the event and the process identifier, and gradually invokes the event publisher, the event handler, and the event listener to perform corresponding operations on the event publisher, the event handler, and the event listener, thereby completing subscription, publication, and monitoring of the event and completing the communication process.
Example 3
Based on the above embodiment 1, the following will be explained with reference to specific examples.
Referring to fig. 4, this embodiment is an example of a call flow, which sequentially processes node events such as IAM, APM, ACM, CPG, ANM, REL, and RLC, and completes a staged call progress. Each process node in the communication process is defined through events, the communication processing logic is decoupled from the process nodes, and the dependency is reduced, so that the effects of easy expansion and easy maintenance are achieved.
Initial Address Message (IAM): initializing an address message, initiating by a calling party, and dialing an intermediate number (roaming number); then, the called number (roaming number) is dialed by the initiation of the intermediate number
Application Transport Message (APM): three-party multi-interaction APM
Address Complete Message (ACM): after confirming that the called party starts ringing, the intermediate number confirms that the calling party starts ringing; if necessary, the intermediate number platform customized ring back tone is played; if the default of the middle number is with the ring-back tone of the group ring-back tone platform, the ring-back tone of the group ring-back tone platform cannot be covered
Call Progress Message (CPG): call state change message
Answer Message (ANM): off-hook message
Release Message (REL): on-hook message
Release Complete Message (RLC)
The foregoing description is directed to the details of preferred and exemplary embodiments of the invention, and not to the limitations defined thereby, which are intended to cover all modifications and equivalents of the invention as may come within the spirit and scope of the invention.
Claims (8)
1. A design method for defining a communication flow based on event driving is characterized by comprising the following steps:
s1, calling an event publisher to publish the flow events, wherein each initial event is assigned with a flow identifier;
s2, calling an event listener to monitor an event and appointing an event handler;
s3, calling a corresponding event handler to process the event;
s4, calling the corresponding event publisher to process the event, specifically comprising: s41, acquiring an event of the next process according to the process identification and the event; and S42, after acquiring the event of the next flow, judging whether the event of the next flow exists, if not, ending the current flow, and if so, executing the programs S1-S4.
2. The design method for defining communication flow based on event-driven according to claim 1, wherein: the process events comprise parent events and child events, the parent events define communication main process nodes, and the child events define communication sub process nodes.
3. The design method for defining communication flow based on event-driven according to claim 1, wherein: the step S2 specifically includes the following steps:
s21, judging whether the event has a flow identification, if so, acquiring a corresponding event handler, and if not, acquiring the flow identification and the corresponding event handler;
s22, updating and storing the service process state information after acquiring the corresponding information;
and S23, judging whether a corresponding event handler exists, if not, ending the current process, and if so, executing the next program.
4. The design method for defining communication flow based on event-driven according to claim 1, wherein: the step S3 specifically includes the following steps:
s31, acquiring a corresponding event publisher according to the process identification and the event;
s32, updating the business process state information after acquiring the corresponding event publisher information;
and S33, judging whether a corresponding event publisher exists or not, if not, ending the process, and if so, executing the next program.
5. A design system for defining communication flow based on event driving is characterized by comprising the following contents:
a release module: the system comprises a flow identifier, a flow publisher and a flow publisher, wherein the flow identifier is used for calling the flow events to be published by the event publisher, and each initial event is assigned with a flow identifier;
a monitoring module: the event monitoring system is used for calling an event listener to monitor an event and appointing an event handler;
a processing module: the event handler is used for calling a corresponding event handler to process the event;
an end module: the event processing method is used for calling a corresponding event publisher to process an event, and the specific processing flow comprises the following steps: acquiring an event of the next process according to the process identifier and the event; and after the event of the next process is obtained, judging whether the event of the next process exists or not, if not, ending the process, and if so, executing the operation from the issuing module to the ending module.
6. The design system for defining communication flow based on event-driven according to claim 5, wherein: the process events comprise parent events and child events, the parent events define communication main process nodes, and the child events define communication sub process nodes.
7. The design system for defining communication flow based on event-driven according to claim 5, wherein: the specific processing flow of the monitoring module comprises the following steps: judging whether the event has a process identifier, if so, acquiring a corresponding event handler, and if not, acquiring the process identifier and the corresponding event handler; updating and storing the service process state information after acquiring the corresponding information; and judging whether a corresponding event handler exists or not, if not, ending the process, and if so, executing the operation of a processing module to be described later.
8. The design system for defining communication flow based on event-driven according to claim 5, wherein: the specific processing flow of the processing module comprises the following steps: acquiring a corresponding event publisher according to the process identification and the event; updating the business process state information after acquiring the corresponding event publisher information; and judging whether a corresponding event publisher exists or not, if not, ending the process, and if so, executing the operation of an ending module, which is described later.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010565039.3A CN111740862A (en) | 2020-06-19 | 2020-06-19 | Design method and system for defining communication flow based on event driving |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010565039.3A CN111740862A (en) | 2020-06-19 | 2020-06-19 | Design method and system for defining communication flow based on event driving |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111740862A true CN111740862A (en) | 2020-10-02 |
Family
ID=72650368
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010565039.3A Pending CN111740862A (en) | 2020-06-19 | 2020-06-19 | Design method and system for defining communication flow based on event driving |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111740862A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090222789A1 (en) * | 2008-02-29 | 2009-09-03 | International Business Machines Corporation | Compiler for a Declarative Event-Driven Programming Model |
| US20140328189A1 (en) * | 2011-08-18 | 2014-11-06 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for determining an event instance |
-
2020
- 2020-06-19 CN CN202010565039.3A patent/CN111740862A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090222789A1 (en) * | 2008-02-29 | 2009-09-03 | International Business Machines Corporation | Compiler for a Declarative Event-Driven Programming Model |
| US20140328189A1 (en) * | 2011-08-18 | 2014-11-06 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for determining an event instance |
Non-Patent Citations (1)
| Title |
|---|
| FW19940314: "Springboot事件机制整合EventBus应用（事件驱动模型）", 《CSDN HTTPS://BLOG.CSDN.NET/FW19940314/ARTICLE/DETAILS/100010397》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6181927B1 (en) | Sponsored call and cell service | |
| CN101296387B (en) | Method and system for implementing speech called service and calling service | |
| CN101874383A (en) | Systems, methods, and computer program products for providing service interaction and mediation in a communications network | |
| JP5946467B2 (en) | Telecommunications service broker for orchestration of services in telecommunications networks | |
| JP4824291B2 (en) | Call category for calls that are connected to the announcement server component | |
| US6453161B1 (en) | Agile service interaction manager for intelligent network services | |
| JP2009525689A (en) | System and method for integrating policy management into a centralized prepaid / postpaid (CONVERGEDPREPAID / POSTPAID) communication service | |
| US7145996B2 (en) | Subscriber service management | |
| CN102144386B (en) | Methods and devices for providing a ring signal to a called party terminal | |
| CN1391768A (en) | Feature interactions | |
| EP1727377B1 (en) | Telecommunications services | |
| US7224783B2 (en) | Subscriber service management | |
| CN111740862A (en) | Design method and system for defining communication flow based on event driving | |
| US7412045B2 (en) | Telecommunications service program | |
| CN104125552A (en) | Network transmission principle based number transmission achieving method and system | |
| US20050097512A1 (en) | Telecommunications service program | |
| US7796745B2 (en) | Systems and methods for automatic call completion | |
| CN110545527B (en) | Call forwarding method, video communication server and calling terminal | |
| CN1218602C (en) | Method for implementing operational control of ringing back tone | |
| US7792267B2 (en) | Automatic call completion in a directory assistance system | |
| CN114785883B (en) | Dialing processing method and device | |
| US7542560B2 (en) | Guest services management service | |
| CN100553271C (en) | In computer system, set up the method for collaboration services | |
| US20050135582A1 (en) | Subscriber service management | |
| US8548150B2 (en) | Location relevant directory assistance |
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 |
Application publication date: 20201002 |
|
| RJ01 | Rejection of invention patent application after publication |