CN111770151A - Processing method and device for user-defined flow, electronic equipment and storage medium - Google Patents
Processing method and device for user-defined flow, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111770151A CN111770151A CN202010588841.4A CN202010588841A CN111770151A CN 111770151 A CN111770151 A CN 111770151A CN 202010588841 A CN202010588841 A CN 202010588841A CN 111770151 A CN111770151 A CN 111770151A
- Authority
- CN
- China
- Prior art keywords
- user
- flow
- configuration information
- management
- defined flow
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 17
- 238000000034 method Methods 0.000 claims abstract description 71
- 238000012545 processing Methods 0.000 claims abstract description 57
- 230000008569 process Effects 0.000 abstract description 28
- 230000003993 interaction Effects 0.000 abstract description 27
- 238000012423 maintenance Methods 0.000 abstract description 14
- 229920006235 chlorinated polyethylene elastomer Polymers 0.000 description 11
- 238000000136 cloud-point extraction Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007429 general method Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The disclosure relates to a processing method and device for a user-defined flow, an electronic device and a storage medium, which are applied to a management device, and developers of the management device and manufacturers of the terminal device can process logic user-defined flow data based on the service of the terminal device; the management equipment can generate configuration information of the custom flow, such as events, parameter models and combination relations thereof, and corresponding relations between the terminal equipment and the combination relations, based on the custom flow data, and generate configuration information of the management equipment, such as business processing logic; the management equipment further combines the two kinds of configuration information to generate user-defined flow information, dynamic configuration of the user-defined flow is achieved, requirements of different service scenes and differentiated processing of service interaction flows of different terminal equipment are met, different service interaction flows are customized, and operation and maintenance efficiency is improved. Developers of the management equipment do not need to carry out hard coding, and the operation and maintenance cost is reduced.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a processing method and apparatus for a user-defined process, an electronic device, and a non-transitory computer-readable storage medium.
Background
With the development of mobile internet and internet of things, more and more terminal devices are developed and applied in a large scale, monitoring and maintenance of the terminal devices by the management devices are urgently needed, and particularly with continuous deepening of application, deep problems and requirements arise, most of the problems and requirements are differentiated processing of service interaction flows of the terminal devices, so that developers of the management devices have to modify and test large-scale codes to meet various service scenes, and time and labor are wasted.
The general method for processing the service interaction flows is to solidify each service interaction flow in the management device in a hard coding mode, so that the method is only suitable for specific terminal devices and specific service scenes, but additional judgment and function development are needed for other terminal devices. As the types of the accessed terminal devices increase, similar additional processing is increased, which results in increased maintenance difficulty, and the docking capability and flexibility of different terminal devices are lacked, thereby increasing the operation and maintenance cost of the management device.
The above description of the discovery process of the problems is only for the purpose of aiding understanding of the technical solutions of the present disclosure, and does not represent an admission that the above is prior art.
Disclosure of Invention
In order to solve at least one problem existing in the prior art, embodiments of the present disclosure provide a processing method and apparatus for a custom flow, an electronic device, and a non-transitory computer-readable storage medium.
According to a first aspect of the present disclosure, a processing method for a custom flow is provided, which is applied to a management device, where the management device is at least used for interacting with a terminal device, and the method includes:
receiving user-defined flow data, wherein the user-defined flow data is generated based on the service processing logic of the terminal equipment;
generating first configuration information of a user-defined flow and second configuration information of the management equipment based on the user-defined flow data;
generating custom flow information, wherein the custom flow information includes the first configuration information and the second configuration information.
According to a second aspect of the present disclosure, there is provided a processing apparatus for customizing a flow, which is applied to a management device, where the management device is at least used for interacting with a terminal device, and the apparatus includes:
the receiving unit is used for receiving user-defined flow data, wherein the user-defined flow data is generated based on the service processing logic of the terminal equipment;
the first generating unit is used for generating first configuration information of a custom flow and second configuration information of the management equipment based on the custom flow data;
and the second generating unit is used for generating custom flow information, wherein the custom flow information comprises the first configuration information and the second configuration information.
According to a third aspect of the present disclosure, there is provided an electronic device comprising: a processor and a memory; the processor is adapted to perform the steps of the method according to the first aspect by calling a program or instructions stored by the memory.
According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing a program or instructions for causing a computer to perform the steps of the method according to the first aspect.
In at least one embodiment of the disclosure, developers of the management device and manufacturers of the terminal device can customize flow data based on the service processing logic of the terminal device; the management equipment can generate configuration information of the custom flow, such as events, parameter models and combination relations thereof, and corresponding relations between the terminal equipment and the combination relations, based on the custom flow data, and generate configuration information of the management equipment, such as business processing logic; the management equipment further combines the two kinds of configuration information to generate user-defined flow information, dynamic configuration of the user-defined flow is achieved, and requirements of different service scenes are met. After the terminal equipment is connected with the management equipment, the personalized service interaction process of the terminal equipment can be realized based on the user-defined process information, the differentiated processing of the service interaction processes of different terminal equipment (different manufacturers, different types, different standards and different versions) can be met, the different service interaction processes can be customized, the compatibility of different terminal equipment is achieved, and the operation and maintenance efficiency of the management equipment is improved. Developers of the management equipment do not need to carry out hard coding in the management equipment, and the operation and maintenance cost of the management equipment is reduced.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in more detail embodiments of the present disclosure with reference to the attached drawings. The accompanying drawings are included to provide a further understanding of the embodiments 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 principles of the disclosure and not to limit the disclosure. In the drawings, like reference numbers generally represent like parts or steps.
FIG. 1 is an exemplary application scenario diagram.
Fig. 2 is a signaling diagram of an exemplary traffic interaction flow.
Fig. 3 is an exemplary block diagram of a management device provided in an exemplary embodiment of the present disclosure.
Fig. 4 is an exemplary block diagram of a processing device for customizing a flow according to an exemplary embodiment of the present disclosure.
Fig. 5 is an exemplary block diagram of an electronic device provided in an exemplary embodiment of the present disclosure.
Fig. 6 is a flowchart illustrating a processing method for customizing a flow according to an exemplary embodiment of the disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure can be more clearly understood, the present disclosure will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. The specific embodiments described herein are merely illustrative of the disclosure and are not intended to be limiting. All other embodiments derived by one of ordinary skill in the art from the described embodiments of the disclosure are intended to be within the scope of the disclosure.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The embodiment of the disclosure provides a processing method and device for a user-defined flow, an electronic device and a storage medium, which are applied to a management device, and by carrying out user-defined dynamic configuration on a service interaction flow of a terminal device, the differentiated processing of the service interaction flows of different terminal devices (different manufacturers, different types, different systems and different versions) is met, different service interaction flows are customized, the compatibility of different terminal devices is achieved, and the operation and maintenance efficiency of the management device is improved. In some embodiments, the management device belongs to a core device in a terminal device management system, and in actual implementation, the management device may be implemented as a server or a server group, where the server group may be centralized or distributed. The developer of the management device may also be understood as a developer of the terminal device management system or a system developer, and the system developer may perform maintenance on other devices in the system in addition to the management device. In some embodiments, the management device may be applied to different scenarios, such as mobile internet, internet of things, and the like. In different application scenarios, the management device may use different communication protocols. Taking a wide area network scenario as an example, the management device uses a TR069 protocol, and accordingly, the terminal device managed by the management device also uses the TR069 protocol. It is understood that the application scenarios of the embodiments of the present disclosure are only examples of the present disclosure, and those skilled in the art will be able to apply the present disclosure to other similar scenarios without the exercise of inventive faculty. In order to make clearer and error-free description, the embodiments of the present disclosure use a management device and a terminal device based on a TR069 protocol as an example to describe the processing method, apparatus, electronic device, and storage medium for the customized flow.
The TR069(Technical Report-069) Protocol is called a "client terminal device wide area network Management Protocol (CWMP)", is a communication Technical specification established by a Technical standard establishment organization of the DSL (Digital Subscriber Line) forum, is a network Management Protocol, is applicable to a remote terminal Management technology, and is a TR069, short for TR069, document number for carrying the Protocol in the DSL forum. With the popularization of a large number of IP-based terminal devices such as VoIP and IPTV (especially in homes), the configuration and maintenance of the terminal devices become more and more difficult, the traditional SNMP protocol cannot meet the corresponding management and maintenance requirements, and the TR069 protocol is more suitable for the application on the terminal devices of the wide area network. The TR069 protocol defines a new set of network management architecture, including management models, interactive interfaces and basic management parameters. The TR069 protocol is used for remote management of CPE (Customer Premise Equipment) by an ACS (Auto-Configuration Server). In this scenario, the management device described above may be understood as an ACS, and the end devices may be understood as CPEs.
Fig. 1 is a diagram of an exemplary application scenario based on the TR069 protocol. As shown in fig. 1, the application scenario includes: management device 100, local area network device, gateway device, and operator's system.
The management apparatus 100 is an ACS for managing end devices (CPEs). In some embodiments, the management device 100 may issue a configuration file to a specific CPE or a group of CPEs, so as to implement automatic configuration of the CPEs (e.g., CPE "zero configuration installation" function) and dynamic configuration of services of the CPEs (e.g., controlling dynamic changes of service parameters from the network side). In some embodiments, the management device 100 may perform a remote management upgrade on the firmware and software of the CPE, for example, the management device 100 may identify a version number of the CPE, decide whether to remotely update the software version of the CPE, and know whether the upgrade is successful after the update is completed. In some embodiments, the management device 100 may monitor the status and performance of the CPE, and TR069 defines a means for the ACS to monitor the status and performance of the CPE, which includes some general performance parameters that may reflect the current status of the CPE; TR069 additionally provides a standard syntax, and the developer of the management device 100 can define additional parameters. In some embodiments, the management device 100 may instruct the CPE to perform a diagnosis of the communication fault, and then simply locate the fault based on the diagnosis result, and perform corresponding processing.
The LAN Device includes a plurality of terminal devices, each of which uses the TR069 protocol, and each of the terminal devices may be a Managed LAN Device (Managed LAN Device) or may be understood as the CPE mentioned above. The CPE may be of various types, for example, a smartphone, a smart television, a laptop, a tablet, a desktop computer, a router, a set-top box, a portable wearable device, etc. In some embodiments, the CPE may automatically request configuration information in the ACS after being powered on, or receive configuration information actively issued by the ACS, so as to implement automatic configuration of the CPE. In some embodiments, the CPE may automatically request to download a file or upgrade a file when new software needs to be loaded to implement a new service function, or when a bug needs to be repaired by current software. In some embodiments, the CPE may detect connectivity, bandwidth, etc. between the CPE and a network service providing point via ping or other means under the direction of the ACS, and the detection result is returned to the ACS.
The gateway device can provide a function of an IP network security tunnel for Managed Internet gateway devices (Managed Internet gateway devices), a support part of a TR069 protocol establishes IPsec with each terminal device (CPE), and distributes different IPsec IP addresses for each CPE, and each CPE adopts different IPsec IP to interact with the ACS. The operator's system may be various, such as a charging system (OSS/BSS), a network management system, a service management system, etc. The management device 100 is connected with the CPE through a southbound interface; the management device 100 is connected to the operator's system via a northbound interface.
Fig. 2 is a signaling diagram of an exemplary service interaction flow, which is suitable for the application scenario shown in fig. 1. The current TR-069_ attribute-5 requires in section 3.2.2: the ACS REQUESTs the CPE to initiate a Request 6CONNECTION Request to the ACS at any time, an HTTP Get (CONNECTIONREQUEST URL, note: TR069 protocol defines URL of ACS CONNECTION Request CPE, URL: Uniform Resource Locator) is required, the CPE receives the Request CONNECTION URL, the CPE initiates the 6CONNECTION Request at Inform Request, at this time, the ACS may execute an RPC (remote procedure Call) method to the CPE, as shown in fig. 2, the flow is described in detail as follows:
(1) the ACS initiates an HTTP GET (URL) connection request to the CPE, wherein the connection request does not carry any data;
(2) the CPE responds to a correct connection request by HTTP status code "200(OK) or 204(Not Content);
(3) the CPE initiates a 6CONNECTION REQUEST REQUEST and indicates that the session is established by ACS requirements;
(4) the ACS returns an Inform Response;
(5) the CPE initiates an empty Http Post request;
(6) the ACS initiates a GetRPCHodes requirement;
(7) the CPE responds to GetRPCSmethods Response and carries the method supported by the CPE to the ACS;
(8) the ACS sends an empty Http Post response to the CPE;
(9) the CPE disconnects and the session ends.
The ACS and the CPE are interoperated through an RPC method specific to the TR069 protocol, but in the TR069 protocol, the RPC method is usually fixed, such as a registration method, a restart method, a parameter setting method, a parameter query method and the like, but when the manufacturer realizes the CPE, the manufacturer is flexible and usually more complex than the RPC method in the TR069 protocol, for example, when some CPE is registered, the ACS issues a set of parameters to the CPE to realize automatic configuration of the CPE; when some CPEs are registered, the ACS does not issue parameters to the CP, but only issues the parameters when the CPEs are restarted; for another example, when the ACS issues the parameters, the parameters are issued in batches, and after each parameter issue, the ACS waits for the CPE to complete configuration, and then issues the parameters again. It can be seen that, different CPE manufacturers set the service interaction flow according to their own service scenarios, which is not completely implemented according to the flow specified in the TR069 protocol, so that the service interaction flow is currently fixed in the ACS in a hard coding manner, and is only applicable to specific terminal devices and specific service scenarios, and the different terminal devices lack docking capability and flexibility, which increases the operation and maintenance cost of the ACS.
Taking CPE upgrading as an example, the TR069 protocol specification only defines a download event and a parameter model, but how to apply events and a flow sequence is not clearly defined, so that differences of service interaction flows exist among CPEs of different manufacturers, different types, and different systems, and the differences are described as follows:
(1) differences between different manufacturers:
for the upgrading process, the method comprises the following three steps:
firstly, self-defining preparation work before upgrading time, and possibly synchronizing and setting parameters P1-Pn and the like;
secondly, issuing a file downloading event (the rule of file issuing is self-defined by each manufacturer, so that the manufacturers are inconsistent);
and customizing the upgrading result verification process after the file transmission is finished, wherein parameters P1 to Pn and the like may need to be searched.
According to the characteristics of the service of each manufacturer, the three steps are customized, so that the large-scale code development and test are compatible with other manufacturers.
(2) The different types of differences:
for the upgrading process, the method comprises the following three steps:
firstly, self-defining a preparation work flow before the upgrading time, and possibly synchronizing and setting parameters P1 to Pn and the like;
secondly, issuing a file downloading event;
and customizing the upgrading result verification process after the file transmission is finished, wherein parameters P1 to Pn and the like may need to be searched.
Different types of CPEs may differ from the above three steps to be incompatible.
(3) Differences between different systems:
2G equipment upgrading process:
setting a parameter A;
secondly, issuing a file downloading event;
finding version parameter a 1.
3G equipment upgrading process:
setting a parameter B;
secondly, issuing a file downloading event;
finding version parameter B1.
4G equipment upgrading process:
setting a parameter C;
secondly, issuing a file downloading event;
finding version parameter C1.
The different systems differ in that the parameter models of the systems differ. Since the parameter models of the systems are different, the parameters are fixed in the codes conventionally, so that when a device of a new system is added, the codes need to be modified for compatibility, for example, a 5G device is added.
For a special service interaction process, such as multi-module upgrade, there is dependency between modules that need to be upgraded, resulting in an unfixed service process, so that the conventional hard coding method cannot be compatible with such a flexible service interaction process.
To this end, as shown in fig. 3, an embodiment of the present disclosure provides a management device 300. In some embodiments, the management device 300 may be implemented as the management device 100 or a portion of the management device 100 shown in fig. 1 for monitoring and remote management of end-point devices (CPEs). The management device 300 may include, but is not limited to: processing means 301 for a default flow and processing means 302 for a custom flow.
The processing device 301 for the default flow can implement a method flow currently solidified in the management device 300 in a hard coding manner, such as a service interaction flow shown in fig. 2, and for example, an RPC method flow (including a registration method flow, a restart method flow, a parameter setting method flow, a parameter query method flow, and the like) specified in a TR069 protocol.
The processing device 302 for the user-defined process performs user-defined dynamic configuration on the service interaction process of the terminal device, thereby satisfying the differentiated processing of the service interaction processes of different terminal devices (different manufacturers, different types, different standards, and different versions), customizing different service interaction processes, achieving the compatibility of different terminal devices, and improving the operation and maintenance efficiency of the management device.
In the embodiment of the present disclosure, all the service interaction flows may be executed by embedding the processing device 302 for the user-defined flow in a dynamic configuration manner, and are not solidified into the management device 300 in a hard coding manner, so that the operation and maintenance cost is reduced. Therefore, no matter the manufacturer a or the manufacturer B, as long as the CPE performs the customization of the service interaction process, the management device 300 provided by the embodiment of the present disclosure can flexibly implement the customization process, and is suitable for any CPE based on the TR069 protocol, for example, may be suitable for CPEs of different manufacturers, different types, different systems, and different versions, and has better compatibility.
In some embodiments, after the management device 300 establishes a connection with a terminal device, the processing apparatus 302 for a customized flow searches whether there is customized flow information related to the terminal device; if the user-defined flow exists, the user-defined flow is interacted with the terminal equipment based on the searched user-defined flow information; if not, the processing device 301 for the default flow interacts with the terminal device based on the default flow.
In some embodiments, the functions of the processing device 302 for the custom flow may be integrated into the processing device 301 for the default flow, and the processing device 302 for the custom flow may be a software module, a hardware module, or a module combining software and hardware. For example, the processing means 302 for custom flow is a software module running on an operating system.
Fig. 4 is an exemplary block diagram of a processing apparatus 400 for customizing a flow according to an embodiment of the present disclosure. The processing means 400 for custom flow is applied to managing a device, such as an ACS. In some embodiments, processing apparatus 400 for a custom flow may be implemented as, or as part of, processing apparatus 302 for a custom flow in FIG. 3. As shown in fig. 4, the processing device 400 for the custom flow may include, but is not limited to, the following elements: a receiving unit 401, a first generating unit 402 and a second generating unit 403. The units are specifically described as follows:
the receiving unit 401 is configured to receive custom flow data, where the custom flow data is generated based on a service processing logic of a terminal device, and the service processing logic of the terminal device may understand flow steps and a sequence of the steps required to complete a service, for example, a certain terminal device has A, B, C three modules that need to be upgraded, and the service processing logic of the terminal device may be: firstly, upgrading the module A; the B module can be upgraded after the A module is upgraded; the module C can be upgraded after the module B is upgraded. In some embodiments, the custom flow data may include identification information of the terminal device, service processing logic of the terminal device, parameter data required for service processing, and the like. In some embodiments, the custom flow data may be generated by a vendor of the terminal device, a developer of the management device, or a general user. In some embodiments, the management device may provide a User Interface (UI), and the receiving unit 401 receives the custom flow data through the UI, where the UI may be local or remote.
The first generating unit 402 is configured to generate first configuration information of a custom flow based on the custom flow data received by the receiving unit 401. Wherein the first configuration information may include at least one event, such as: the upgrading method comprises three events of an upgrading A module, an upgrading B module and an upgrading C module. The first configuration information may further include at least one parameter model, for example, a parameter model required for upgrading the a module, a parameter model required for upgrading the B module, and a parameter model required for upgrading the C module. In some embodiments, the parametric model includes a name and a functional description of at least one parameter, such as the parametric model of the standard Inform method of Table 1:
TABLE 1 Parametric model of the Standard Inform method
| Parameter name | Description of the parameters |
| DeviceID | Data structure identification CPE |
| Event | Identifying the reason for this Inform initiation |
| MaxEnvelopes | HTTP Response can carry the number of SOAP envelopes |
| CurrentTime | Current time of CPE |
| RetryCount | Maximum number of repeated connections for this Session |
| ParameterList | The parameters that this Inform needs to carry |
In some embodiments, the first configuration information may further include a combination relationship between the at least one event and the at least one parameter model, for example, there is a combination relationship between the upgrade a module and the parameter model required for upgrading the a module; the upgrading B module and a parameter model required by the upgrading B module have a combination relation; the upgrading C module and a parameter model required by the upgrading C module have a combination relation; the upgrade B module and the upgrade A module have a combination relation; the upgrade C module and the upgrade B module have a combined relationship.
In some embodiments, the first configuration information may further include a correspondence between the terminal device and the combination relationship, for example, an identifier of the terminal device corresponds to the combination relationship, and after the terminal device having the identifier establishes a connection with the management device, the management device may determine that the terminal device and the combination relationship have a correspondence.
In some embodiments, the first generating unit 402 may generate the second configuration information of the management device based on the custom flow data received by the receiving unit 401. The second configuration information may be understood as a service processing logic of the management device, for example, after the parameter model is configured, monitoring, alarming, and other processing are performed on the CPE, which belongs to the service processing logic of the management device, that is, in addition to the custom flow, additional interaction between the management device and the terminal device is required; for another example, to complete an event, the management device needs to interact with the terminal device, and the interaction process can also be understood as a service processing logic; for another example, after configuring an event and a parameter model, it is also the service processing logic that the parameter is issued immediately or the parameter is issued after the event is issued first.
The second generating unit 403 is configured to generate custom flow information, where the custom flow information includes the first configuration information and the second configuration information. In some embodiments, the second generating unit 403 may associate the first configuration information with the second configuration information, and use the associated information as the custom flow information. In some embodiments, the second generating unit 403 does not actually perform the generating action, and only stores the first configuration information and the second configuration information. In some embodiments, the second generating unit 403 may store the custom flow information to a specified location in a database; the specified position is used for the management equipment to search whether the user-defined flow information exists. In some embodiments, the second generating unit 403 may store the custom flow information in a cache, which is beneficial to improving efficiency of searching for the custom flow information.
In some embodiments, after the management device establishes a connection with a terminal device, the processing apparatus 400 for a customized flow searches, through the identifier of the terminal device, from a location or a cache specified in a database, whether customized flow information related to the terminal device exists; if the user-defined flow exists, the user-defined flow is interacted with the terminal equipment based on the searched user-defined flow information; and if the current flow does not exist, the management equipment interacts with the terminal equipment based on a default flow.
In some embodiments, the division of each unit in the processing apparatus 400 for the custom flow is only one logical function division, and there may be another division manner when actually implementing, for example, at least two units of the receiving unit 401, the first generating unit 402, and the second generating unit 403 may be implemented as one unit; the receiving unit 401, the first generating unit 402, or the second generating unit 403 may also be divided into a plurality of sub-units. It will be understood that the various units or sub-units may be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application.
Fig. 5 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. The electronic device may be implemented as the management device 100 shown in fig. 1. As shown in fig. 5, the electronic apparatus includes: at least one processor 501, at least one memory 502, and at least one communication interface 503. The various components in the electronic device are coupled together by a bus system 504. A communication interface 503 for information transmission with an external device. Understandably, the bus system 504 is used to enable connective communication between these components. The bus system 504 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, the various buses are labeled as bus system 504 in fig. 5.
It will be appreciated that the memory 502 in this embodiment can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
In some embodiments, memory 502 stores elements, executable units or data structures, or a subset thereof, or an expanded set thereof as follows: an operating system and an application program.
The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application programs include various application programs such as a media player (MediaPlayer), a Browser (Browser), etc. for implementing various application services. The program for implementing the processing method for the custom flow provided by the embodiment of the present disclosure may be included in an application program.
In the embodiment of the present disclosure, the processor 501 is configured to execute the steps of the embodiments of the processing method for the custom flow provided by the embodiment of the present disclosure by calling a program or an instruction stored in the memory 502, specifically, a program or an instruction stored in an application program.
The processing method for the custom flow provided by the embodiment of the present disclosure may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The processor 501 may be a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The steps of the processing method for the user-defined flow provided by the embodiment of the present disclosure may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software units in the decoding processor. The software elements may be located in ram, flash, rom, prom, or eprom, registers, among other storage media that are well known in the art. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and performs the steps of the method in combination with its hardware.
Fig. 6 is an exemplary flowchart of a processing method for a custom flow provided by an embodiment of the present disclosure. The execution subject of the method is a management apparatus, which is applicable to the management apparatus 100 shown in fig. 1. For convenience of description, the flow of the processing method for the custom flow is described with the management apparatus as the execution subject in the following embodiments.
As shown in fig. 6, in step 601, the management device receives a custom flow data, where the custom flow data is generated based on a service processing logic of the terminal device, and the service processing logic of the terminal device may understand a flow step and a sequence of steps required to complete a service, for example, a certain terminal device has A, B, C three modules that need to be upgraded, and the service processing logic may be: firstly, upgrading the module A; the B module can be upgraded after the A module is upgraded; the module C can be upgraded after the module B is upgraded. In some embodiments, the custom flow data may include identification information of the terminal device, service processing logic of the terminal device, parameter data required for service processing, and the like. In some embodiments, the custom flow data may be generated by a vendor of the terminal device, a developer of the management device, or a general user. In some embodiments, the management device provides a user interface through which the management device receives custom flow data.
For example, a certain terminal device has A, B, C three modules to be upgraded, and the service processing logic of the terminal device may be: firstly, upgrading the module A; the B module can be upgraded after the A module is upgraded; the module C can be upgraded after the module B is upgraded.
In step 602, the management device generates first configuration information of a custom flow and second configuration information of the management device based on the custom flow data. In some embodiments, the first configuration information comprises: at least one event and at least one parametric model of the custom flow; a combined relationship of the at least one event and the at least one parametric model; and the corresponding relation between the terminal equipment and the combination relation. In some embodiments, the parametric model includes a name and a functional description of at least one parameter. In some embodiments, the second configuration information comprises: a service processing logic of the management device.
For example, the first configuration information may include: the upgrading method comprises the following steps of upgrading an A module, an upgrading B module and an upgrading C module, wherein the three events are three events; accordingly, there are three parametric models: the parameter model required by the upgrading module A, the parameter model required by the upgrading module B and the parameter model required by the upgrading module C.
Accordingly, the first configuration information may further include: the upgrading A module and a parameter model required by the upgrading A module have a combination relation; the upgrading B module and a parameter model required by the upgrading B module have a combination relation; the upgrading C module and a parameter model required by the upgrading C module have a combination relation; the upgrade B module and the upgrade A module have a combination relation; the upgrade C module and the upgrade B module have a combined relationship.
Correspondingly, the first configuration information may further include a corresponding relationship between the terminal device and the combination relationship, for example, an identifier of the terminal device corresponds to the combination relationship, and after the terminal device having the identifier establishes a connection with the management device, the management device may determine that the terminal device and the combination relationship have the corresponding relationship.
For example, the second configuration information may include: after configuring the parametric model, monitoring, alarming, and other processing is performed on the CPE. The second configuration information may further include: to complete an event, a process of interaction between the management device and the terminal device is required. The second configuration information may further include: after configuring an event and a parameter model, the parameters are issued immediately or the event is issued first and then the parameters are issued.
In step 603, the management device generates custom flow information, where the custom flow information includes the first configuration information and the second configuration information. In some embodiments, the management device may associate the first configuration information with the second configuration information, and use the associated information as the custom flow information. In some embodiments, the management device may not actually perform the generating action, and only store the first configuration information and the second configuration information.
In some embodiments, the management device stores the custom flow information to a specified location in a database; the specified position is used for the management equipment to search whether the user-defined flow information exists. In some embodiments, the management device may store the custom flow information in a cache, which is beneficial to improving efficiency of searching for the custom flow information.
In some embodiments, after the management device establishes a connection with a terminal device, whether user-defined flow information related to the terminal device exists is searched for in a specified position or a cache in a database through an identifier of the terminal device; if the user-defined flow exists, the user-defined flow is interacted with the terminal equipment based on the searched user-defined flow information; and if not, interacting with the terminal equipment based on a default flow.
It is noted that, for simplicity of description, the foregoing method embodiments are described as a series of acts or combination of acts, but those skilled in the art will appreciate that the disclosed embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently with other steps in accordance with the disclosed embodiments. In addition, those skilled in the art can appreciate that the embodiments described in the specification all belong to alternative embodiments.
Embodiments of the present disclosure also provide a non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores a program or an instruction, where the program or the instruction causes a computer to execute steps of each embodiment of the processing method for the user-defined flow, and details are not repeated here to avoid repeated description.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than others, combinations of features of different embodiments are meant to be within the scope of the disclosure and form different embodiments.
Those skilled in the art will appreciate that the description of each embodiment has a respective emphasis, and reference may be made to the related description of other embodiments for those parts of an embodiment that are not described in detail.
Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A processing method for self-defining a flow is applied to a management device, wherein the management device is at least used for interacting with a terminal device, and the method comprises the following steps:
receiving user-defined flow data, wherein the user-defined flow data is generated based on the service processing logic of the terminal equipment;
generating first configuration information of a user-defined flow and second configuration information of the management equipment based on the user-defined flow data;
generating custom flow information, wherein the custom flow information includes the first configuration information and the second configuration information.
2. The method of claim 1, wherein the management device provides a user interface; and receiving user-defined flow data through the user interface.
3. The method of claim 1, wherein the first configuration information comprises:
at least one event and at least one parametric model of the custom flow;
a combined relationship of the at least one event and the at least one parametric model;
and the corresponding relation between the terminal equipment and the combination relation.
4. The method of claim 3, wherein the parametric model comprises a name and a functional description of at least one parameter.
5. The method of claim 1, wherein the second configuration information comprises: a service processing logic of the management device.
6. The method of claim 1, further comprising:
storing the self-defined flow information to a designated position in a database; the specified position is used for the management equipment to search whether the user-defined flow information exists.
7. The method of claim 6, further comprising:
after establishing connection with terminal equipment, searching whether user-defined flow information related to the terminal equipment exists or not from the specified position;
if the user-defined flow exists, the user-defined flow is interacted with the terminal equipment based on the searched user-defined flow information;
and if not, interacting with the terminal equipment based on a default flow.
8. A processing apparatus for customizing a flow is applied to a management device, the management device is at least used for interacting with a terminal device, and the apparatus comprises:
the receiving unit is used for receiving user-defined flow data, wherein the user-defined flow data is generated based on the service processing logic of the terminal equipment;
the first generating unit is used for generating first configuration information of a custom flow and second configuration information of the management equipment based on the custom flow data;
and the second generating unit is used for generating custom flow information, wherein the custom flow information comprises the first configuration information and the second configuration information.
9. An electronic device, comprising: a processor and a memory;
the processor is adapted to perform the steps of the method of any one of claims 1 to 7 by calling a program or instructions stored in the memory.
10. A non-transitory computer-readable storage medium storing a program or instructions for causing a computer to perform the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010588841.4A CN111770151B (en) | 2020-06-24 | 2020-06-24 | Processing method and device for custom flow, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010588841.4A CN111770151B (en) | 2020-06-24 | 2020-06-24 | Processing method and device for custom flow, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111770151A true CN111770151A (en) | 2020-10-13 |
| CN111770151B CN111770151B (en) | 2024-03-15 |
Family
ID=72722422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010588841.4A Active CN111770151B (en) | 2020-06-24 | 2020-06-24 | Processing method and device for custom flow, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111770151B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542272A (en) * | 2021-07-14 | 2021-10-22 | 芯河半导体科技(无锡)有限公司 | Method for automatically adapting to remote management platform of operator |
| CN114612065A (en) * | 2022-03-07 | 2022-06-10 | 东莞市金田纸业有限公司 | Associated equipment combination method, device, equipment and medium for process papermaking |
| WO2024060965A1 (en) * | 2022-09-20 | 2024-03-28 | 长城汽车股份有限公司 | Method for dynamically configuring business logic, cloud platform, vehicle, and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859160A (en) * | 2005-04-30 | 2006-11-08 | 华为技术有限公司 | Method and its system for managing user stationed equipment configuration |
| US20080298444A1 (en) * | 2005-10-04 | 2008-12-04 | Cioffi John M | Dsl System |
| CN101483543A (en) * | 2008-01-11 | 2009-07-15 | 华为技术有限公司 | Network management method and system, terminal and automatic configuration server |
| US20090225681A1 (en) * | 2006-11-20 | 2009-09-10 | Huawei Technologies Co., Ltd. | Method and apparatus for configuring and managing customer premises equipment |
| US20090254613A1 (en) * | 2006-12-15 | 2009-10-08 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for acquiring and providing cpe function configuration information |
| CN101635642A (en) * | 2009-08-04 | 2010-01-27 | 中兴通讯股份有限公司 | Method and system for remotely managing personal terminal |
| CN101772003A (en) * | 2009-12-31 | 2010-07-07 | 中兴通讯股份有限公司 | Terminal unit management device and method |
| CN102318268A (en) * | 2009-02-10 | 2012-01-11 | 阿尔卡特朗讯公司 | Alarm notification between customer premises equipment and a remote management server |
| CN103560918A (en) * | 2013-11-13 | 2014-02-05 | 迈普通信技术股份有限公司 | Method and system for managing CPE port |
| CN105357059A (en) * | 2015-12-08 | 2016-02-24 | 中国建设银行股份有限公司 | Business event processing method and apparatus |
| CN105574150A (en) * | 2015-12-15 | 2016-05-11 | 北京奇虎科技有限公司 | Data processing method and device |
| CN108881209A (en) * | 2018-06-11 | 2018-11-23 | 京信通信系统（中国）有限公司 | Long-range processing method, apparatus and system |
| CN111080243A (en) * | 2019-12-05 | 2020-04-28 | 北京百度网讯科技有限公司 | Service processing method, device, system, electronic equipment and storage medium |
-
2020
- 2020-06-24 CN CN202010588841.4A patent/CN111770151B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859160A (en) * | 2005-04-30 | 2006-11-08 | 华为技术有限公司 | Method and its system for managing user stationed equipment configuration |
| US20080298444A1 (en) * | 2005-10-04 | 2008-12-04 | Cioffi John M | Dsl System |
| US20090225681A1 (en) * | 2006-11-20 | 2009-09-10 | Huawei Technologies Co., Ltd. | Method and apparatus for configuring and managing customer premises equipment |
| US20090254613A1 (en) * | 2006-12-15 | 2009-10-08 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for acquiring and providing cpe function configuration information |
| CN101483543A (en) * | 2008-01-11 | 2009-07-15 | 华为技术有限公司 | Network management method and system, terminal and automatic configuration server |
| CN102318268A (en) * | 2009-02-10 | 2012-01-11 | 阿尔卡特朗讯公司 | Alarm notification between customer premises equipment and a remote management server |
| CN101635642A (en) * | 2009-08-04 | 2010-01-27 | 中兴通讯股份有限公司 | Method and system for remotely managing personal terminal |
| CN101772003A (en) * | 2009-12-31 | 2010-07-07 | 中兴通讯股份有限公司 | Terminal unit management device and method |
| CN103560918A (en) * | 2013-11-13 | 2014-02-05 | 迈普通信技术股份有限公司 | Method and system for managing CPE port |
| CN105357059A (en) * | 2015-12-08 | 2016-02-24 | 中国建设银行股份有限公司 | Business event processing method and apparatus |
| CN105574150A (en) * | 2015-12-15 | 2016-05-11 | 北京奇虎科技有限公司 | Data processing method and device |
| CN108881209A (en) * | 2018-06-11 | 2018-11-23 | 京信通信系统（中国）有限公司 | Long-range processing method, apparatus and system |
| CN111080243A (en) * | 2019-12-05 | 2020-04-28 | 北京百度网讯科技有限公司 | Service processing method, device, system, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| LING ZHENG等: "Research and Application of CWMP in Distributed Network Management System", 2012 INTERNATIONAL CONFERENCE ON COMPUTER SCIENCE AND SERVICE SYSTEM * |
| 赵嫚嫚;刘学;戴琼兴;: "基于TR069的交互电视终端分组管理设计", 计算机工程与设计, no. 04 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542272A (en) * | 2021-07-14 | 2021-10-22 | 芯河半导体科技(无锡)有限公司 | Method for automatically adapting to remote management platform of operator |
| CN114612065A (en) * | 2022-03-07 | 2022-06-10 | 东莞市金田纸业有限公司 | Associated equipment combination method, device, equipment and medium for process papermaking |
| WO2024060965A1 (en) * | 2022-09-20 | 2024-03-28 | 长城汽车股份有限公司 | Method for dynamically configuring business logic, cloud platform, vehicle, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111770151B (en) | 2024-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111770151B (en) | Processing method and device for custom flow, electronic equipment and storage medium | |
| US8139509B2 (en) | Installation and management of mobile device [{S]} configuration | |
| KR101782457B1 (en) | Application upgrade method and apparatus | |
| KR20050117936A (en) | System and method of managing device for device managing technology | |
| US11726808B2 (en) | Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations | |
| WO2011082684A1 (en) | Data configuration method and apparatus | |
| CN112565439B (en) | Internet of things communication method and system | |
| US20220239547A1 (en) | Yang Module Management Method, Apparatus, and System, Device, and Storage Medium | |
| WO2016115896A1 (en) | Method and device for management of virtual network function (vnf) | |
| WO2021057605A1 (en) | Device management method, device, system and device, and storage medium | |
| US20230031952A1 (en) | Network service management system and network service management method | |
| CN115357308A (en) | Docker-based edge Internet of things proxy device, system and application method | |
| CN101212346B (en) | Software version management method and device for network element management system | |
| CN112217845B (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN109495298B (en) | Method and device for managing nodes in OpenStack system | |
| CN109274715A (en) | The platform resource management system of vehicle-mounted multi-channel communication systems | |
| CN110650071B (en) | Access management method and device of user equipment and management server | |
| CN107181629B (en) | Component upgrading method and system | |
| KR100981381B1 (en) | Device manegement agent and method | |
| CN110943975A (en) | Service registration method, device, computer equipment and storage medium | |
| WO2015117294A1 (en) | Information binding method and device | |
| EP4075731A1 (en) | Data management method and apparatus, and device, computer-readable storage medium, and system | |
| CN110943968A (en) | Equipment access control method and equipment access assembly | |
| CN112187482B (en) | Device management method, system, electronic device and storage medium | |
| CN113590341B (en) | Service component calling method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 510663 Shenzhou Road, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangdong, 10 Applicant after: Jingxin Network System Co.,Ltd. Address before: 510663 Shenzhou Road, Guangzhou Science City, Guangzhou economic and Technological Development Zone, Guangdong, 10 Applicant before: COMBA TELECOM SYSTEMS (CHINA) Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |