CN114500302B

CN114500302B - ICE service arrangement method, ICE service arrangement device, terminal equipment and storage medium

Info

Publication number: CN114500302B
Application number: CN202111650264.8A
Authority: CN
Inventors: 黄举就; 肖中卿
Original assignee: Guangdong Huazhiyuan Information Engineering Co ltd; Guangzhou Huajia Software Co ltd; Guangzhou Jiadu Urban Rail Intelligent Operation And Maintenance Service Co ltd; PCI Technology Group Co Ltd; PCI Technology and Service Co Ltd
Current assignee: Guangdong Huazhiyuan Information Engineering Co ltd; Guangzhou Huajia Software Co ltd; Guangzhou Jiadu Urban Rail Intelligent Operation And Maintenance Service Co ltd; PCI Technology Group Co Ltd; PCI Technology and Service Co Ltd
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2023-06-06
Anticipated expiration: 2041-12-30
Also published as: CN114500302A

Abstract

The embodiment of the invention discloses an ICE service arrangement method, a device, terminal equipment and a storage medium, wherein the method comprises the steps of packaging ICE service components corresponding to each ICE service into proxy service; connecting each ICE service with a corresponding proxy service; arranging service flows, packaging communication functions of the service flows and proxy services into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node; receiving parameter information of a target proxy service, wherein the parameter information is used for executing a target service flow; according to the parameter information, the target custom node and the target proxy service are connected in a communication mode, when the target service flow is executed, the corresponding ICE service is called through the communication connection, and the target custom node is the custom node corresponding to the target service flow.

Description

ICE service arrangement method, ICE service arrangement device, terminal equipment and storage medium

Technical Field

The embodiment of the application relates to the field of ICE service arrangement, in particular to an ICE service arrangement method, an ICE service arrangement device, terminal equipment and a storage medium.

Background

ICE (Internet Communications Engine, internet communication engine) is a high performance middleware based on which a carrier-grade solution can be implemented. At present, an integration scheme of a client and a general monitoring ICE service in the rail transit industry is commonly realized by loading a plurality of SDKs (Software Development Kit, software development kits) of the general monitoring ICE service through the client and butting the SDKs with the general monitoring ICE service through an ICE framework. As shown in fig. 1, the method has the advantages of simpler implementation, and only the corresponding SDKs need to be adapted for different general monitoring ICE services, but the method has the disadvantages of poor compatibility and low flexibility, and when the SDKs docked for a certain general monitoring ICE service are modified, the whole client needs to be modified and compiled again.

In summary, the existing ICE service deployment method has the technical problem of poor flexibility.

Disclosure of Invention

The embodiment of the invention provides an ICE service arrangement method, an ICE service arrangement device, terminal equipment and a storage medium, which solve the technical problem of poor flexibility of the existing ICE service deployment mode.

In a first aspect, an embodiment of the present invention provides an ICE service orchestration method, including the following steps:

encapsulating ICE service components corresponding to each ICE service into proxy services;

connecting each ICE service with a corresponding proxy service;

arranging service flows, and packaging the service flows and the communication function of the proxy service into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node;

receiving parameter information of a target proxy service, wherein the parameter information is used for executing a target service flow;

and establishing communication connection between the target custom node and the target proxy service according to the parameter information, and calling the corresponding ICE service through the communication connection when the target service flow is executed, wherein the target custom node is a custom node corresponding to the target service flow.

Preferably, the specific process of establishing communication connection between the target custom node and the target proxy service is:

and establishing communication connection between the target custom node and the target proxy service through a preset interface protocol.

Preferably, the interface protocol is a unified interface protocol based on websocket/http.

Preferably, the parameter information includes an address parameter of the target proxy service.

Preferably, the specific process of establishing communication connection between the target custom node and the target proxy service according to the parameter information is:

and inputting the address parameter of the target proxy service into the target custom node so that the target custom node searches the target proxy service according to the address parameter and establishes communication connection with the target proxy service.

Preferably, the address parameter includes an IP of the target proxy service and a port of the target proxy service, and the address parameter further includes an IP of a target ICE service connected to the target proxy service and a port of the target ICE service.

Preferably, the specific process of arranging the service flow is as follows:

and in the visual arrangement interface, arranging the service flow by dragging a flow component, wherein the flow component is provided by the visual arrangement interface.

In a second aspect, an embodiment of the present invention provides an ICE service orchestration device, including an encapsulation module, a connection module, a node encapsulation module, an information receiving module, and a communication establishment module;

the encapsulation module is used for encapsulating ICE service components corresponding to each ICE service into proxy services;

the connection module is used for connecting each ICE service with a corresponding proxy service;

the node packaging module is used for arranging service flows, packaging the service flows and the communication function of the proxy service into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node;

the information receiving module is used for receiving parameter information of the target proxy service, and the parameter information is used for executing a target service flow;

the communication establishing module is used for establishing communication connection between the target custom node and the target proxy service according to the parameter information, and calling the corresponding ICE service through the communication connection when the target service flow is executed, wherein the target custom node is a custom node corresponding to the target service flow.

In a third aspect, an embodiment of the present invention provides a terminal device, where the terminal device includes a processor and a memory;

the memory is used for storing a computer program and transmitting the computer program to the processor;

the processor is configured to execute an ICE service orchestration method according to the first aspect according to instructions in the computer program.

In a fourth aspect, embodiments of the present invention provide a storage medium storing computer executable instructions which, when executed by a computer processor, are adapted to perform an ICE service orchestration method according to the first aspect.

In the foregoing, the embodiments of the present invention provide an ICE service orchestration method, an apparatus, a terminal device, and a storage medium, where the method includes encapsulating an ICE service component corresponding to each ICE service into a proxy service; connecting each ICE service with a corresponding proxy service; arranging service flows, packaging communication functions of the service flows and proxy services into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node; receiving parameter information of a target proxy service, wherein the parameter information is used for executing a target service flow; and establishing communication connection between the target custom node and the target proxy service according to the parameter information, and calling the corresponding ICE service through the communication connection when executing the target service flow, wherein the target custom node is a custom node corresponding to the target service flow.

According to the embodiment of the invention, the proxy services are separated from the client to be made into independent proxy services, the coupling between ICE services is released, each proxy service is used as an atomic service and does not affect other proxy services even if one proxy service is abnormal, and in the process of dynamically adding or deleting ICE services and corresponding proxy services, other proxy services and ICE services in the whole service flow are not affected, and the whole client does not need to be compiled again, so that a user can flexibly expand the ICE services, and the flexibility of arranging the service flow is greatly improved.

Drawings

Fig. 1 is a schematic diagram of a prior art SDK loading a plurality of generic monitoring ICE services through a client according to an embodiment of the present invention.

Fig. 2 is a flow chart of an ICE service orchestration method according to an embodiment of the present invention.

Fig. 3 is a schematic diagram of an expansion of monitoring ICE basic service combinations according to an embodiment of the present invention.

Fig. 4 is a specific usage scenario diagram of an ICE service orchestration method according to an embodiment of the present invention.

Fig. 5 is a schematic structural diagram of an ICE service arrangement device according to an embodiment of the present invention.

Fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.

Detailed Description

The following description and the drawings illustrate specific embodiments of the application sufficiently to enable those skilled in the art to practice them. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some embodiments may be included in, or substituted for, those of others. The scope of the embodiments of the present application encompasses the full ambit of the claims, as well as all available equivalents of the claims. Embodiments may be referred to herein, individually or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. 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. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or terminal device that comprises a list of elements does not include only those elements but may include other elements not expressly listed. Various embodiments are described herein in a progressive manner, each embodiment focusing on differences from other embodiments, and identical and similar parts between the various embodiments are sufficient to be seen with each other. The structures, products and the like disclosed in the embodiments correspond to the parts disclosed in the embodiments, so that the description is relatively simple, and the relevant parts refer to the description of the method parts.

Example 1

As shown in fig. 2, fig. 2 is a flowchart of an ICE service orchestration method according to an embodiment of the present invention. The ICE service arrangement method provided by the embodiment of the invention can be executed by ICE service arrangement equipment, the ICE service arrangement equipment can be realized in a software and/or hardware mode, and the ICE service arrangement equipment can be formed by two or more physical entities or one physical entity. For example, the ICE service orchestration device may be a computer, a host computer, a tablet, or the like. In this embodiment, taking the ICE general monitoring service as the ICE service and taking the ICE SDK proxy service as the proxy service as an example, the method includes the following steps:

step 101, packaging ICE service components corresponding to each ICE service into proxy services.

In this embodiment, each ICE generic monitoring service corresponds to each ICE service component, which may be a client of the ICE generic monitoring service. The ICE service components corresponding to each ICE general monitoring service are first packaged into ICE SDK proxy service, which is an upper application end (i.e. ICE client) of the ICE service.

Step 102, each ICE service is connected with a corresponding proxy service.

After the client corresponding to each ICE general monitoring service is packaged into the ICE SDK proxy service, each ICE general monitoring service is connected with the corresponding ICE SDK proxy service, so that communication can be carried out between the ICE SDK proxy service and the ICE general monitoring service. In one embodiment, the ICE general monitoring service and the ICE SDK proxy service are connected through a calling interface (Slice interface), the calling interface is realized based on an ICE intermediate platform framework, the calling interface can be set according to actual service requirements, and the calling interface is designed according to ICE programming specifications.

It should be further noted that, in this embodiment, the ICE SDK proxy service is designed to exist in the form of a plug-in service, so that the connected ICE generic monitoring service can be flexibly added or deleted as required. For example, as shown in fig. 3, one or more (combination of ICE SDK proxy service+ice generic monitoring service) monitoring ICE basic service combinations may be dynamically added, for example: adding a combination of ICE SDK proxy service 3+ICE generic monitoring service 3 may also dynamically delete one or more monitoring ICE base service combinations, such as deleting a combination of ICE SDK proxy service 4+ICE generic monitoring service 4.

Step 103, arranging service flows, packaging the communication functions of the service flows and proxy services into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node.

After each ICE general monitoring service is connected with the corresponding ICE SDK proxy service, the service flow is further arranged. It should be further noted that, the service flow is used for guiding the call collaboration, call mode, call sequence, response processing of the ICE general monitoring service to be finally returned to the data and business logic required by the requester. After the service flow is arranged, the communication function between the service flow and the ICE SDK proxy service is packaged into a custom node, and it is further required to explain that the communication function comprises a flow for establishing communication connection with the ICE SDK proxy service in the execution process of the service flow, and the flow can be specific codes and the like. In this embodiment, the number of service flows is at least one, and each service flow corresponds to at least one custom node, that is, one service flow may correspond to 2 custom nodes or multiple custom nodes. In one embodiment, the number of custom nodes corresponding to a service flow may be determined according to business logic of the service flow, and in one service flow, an A1 ICE generic monitor service and an A2 ICE generic monitor service are invoked when a condition a is satisfied, and an A3 ICE generic monitor service is invoked when a condition B is satisfied, so that the number of custom nodes corresponding to the service flow may be determined to be 3. It should be further noted that, each service flow and the custom node are in one-to-one correspondence, and the two service flows cannot share the same custom node.

Step 104, receiving parameter information of the target proxy service, wherein the parameter information is used for executing the target service flow.

And after the custom node of the service flow is packaged, receiving the parameter information of the target ICE SDK proxy service, wherein the parameter information is used for executing the target service flow. The target ICE SDK proxy service is the ICE SDK proxy service which needs to be called in the process of executing the target flow. Therefore, the parameter information of the target ICE SDK proxy service needs to be acquired to be able to execute the target service flow. It is understood that the number of target proxy services is at least one.

And 105, establishing communication connection between the target custom node and the target proxy service according to the parameter information, and calling the corresponding ICE service through the communication connection when executing the target service flow, wherein the target custom node is a custom node corresponding to the target service flow.

After the parameter information of the target ICE SDK proxy service is obtained, the target custom nodes corresponding to the target service flow are connected with the target ICE SDK proxy service according to the parameter information, and it can be understood that when a plurality of target ICE SDK proxy services exist, each target custom node is connected with the corresponding target ICE SDK proxy service, and the number of custom nodes is determined according to the service logic of the service flow, so that the number of custom nodes is generally the same as the number of target ICE SDK proxy services.

After the communication connection is established between the target custom node of the target service flow and the target ICE SDK proxy service, when the target service flow is executed subsequently, the target custom node can call ICE general monitoring service connected with the target ICE SDK proxy service through the communication connection, so that the business function of the target service flow is realized.

According to the embodiment of the invention, the proxy services are separated from the client to be made into independent proxy services, the coupling between the ICE services is released, each proxy service is not influenced by the other proxy services as an atomic service, even if one proxy service is abnormal, the other proxy services are not influenced, in the process of dynamically adding or deleting the ICE services and the corresponding proxy services, the other proxy services and the ICE services in the whole service flow are not influenced, the whole client does not need to be compiled again, so that a user can flexibly expand the ICE services, and the flexibility of arranging the service flow is greatly improved.

Based on the above embodiment, the specific process of establishing communication connection between the target custom node and the target proxy service is as follows:

In this embodiment, a communication connection is established between the target custom node and the target ICE SDK proxy service through a preset interface protocol, and it needs to be further explained that the interface protocol between the ICE SDK proxy service and the target custom node needs to meet the requirements of all the ICE SDK proxy services, and also needs to reserve a part of fields for subsequent expansion. For example, for the same command cmd, only part of parameters carried by the command in the protocol are needed by part of ICE SDK proxy services, and all parameters carried by the command in the protocol are needed by part of ICE SDK proxy services, so that the interface protocol needs to meet the requirements of all protocols of ICE SDK proxy services. In one embodiment, the interface protocol is a websocket/http-based unified interface protocol. By utilizing the characteristics supported by protocols such as a custom node pair http, websocket, tcp and a udp, a unified interface protocol based on websocket/http is designed, so that the adaptation between the custom node and the ICE SDK proxy service is realized. The traditional scheme directly integrates a mode of calling hard codes to the client by a plurality of SDKs, the adaptation process is complex, the unified interface protocol provided by the embodiment is realized based on websocket/http, the implementation is unified and flexible, and the adaptation process is more convenient.

On the basis of the above embodiment, the parameter information includes an address parameter of the target proxy service.

In this embodiment, the address parameter is a unique identifier of the ICE SDK proxy service, and the corresponding ICE SDK proxy service can be determined according to the address parameter.

Based on the above embodiment, the specific process of establishing communication connection between the target custom node and the target proxy service according to the parameter information is as follows:

and inputting the address parameters of the target proxy service into the target custom node so that the target custom node searches the target proxy service according to the address parameters and establishes communication connection with the target proxy service.

After the address parameters of the target ICE SDK proxy service are obtained, the address parameters of the target ICE SDK proxy service are input into a target custom node, and after the target custom node receives the address parameters, the corresponding target proxy service can be searched according to the address parameters, and communication connection is established between the target custom node and the target proxy service through a unified interface protocol based on websocket/http.

In one embodiment, the address parameters include an IP of the target proxy service and a port of the target proxy service, and the address parameters further include an IP of the target ICE service and a port of the target ICE service connected to the target proxy service.

It should be further noted that the address parameters include the IP of the target ICE SDK proxy service and the port of the target ICE SDK proxy service, so that the target custom node can find the target ICE SDK proxy service according to the IP and the port of the target ICE SDK proxy service; and secondly, the address parameter also comprises the IP and the port of the target ICE general monitoring service connected with the target ICE SDK proxy service, so that the target custom node can call the target ICE general monitoring service according to the IP and the port of the target ICE general monitoring service after establishing communication with the target ICE SDK proxy service.

Based on the above embodiment, the specific process of arranging the service flow is as follows:

in the visual arrangement interface, the service flow is arranged in a mode of dragging a flow component, and the flow component is provided by the visual arrangement interface.

In one embodiment, the orchestration of service flows is implemented using a service orchestration tool (e.g., a Node-Red, etc. tool), such as a Node-Red, etc. The service editing tool is realized based on a flow editor of a browser, a visual editing interface is provided in the flow editor of the browser, a flow component is provided in the visual editing interface, the editing of the service flow can be realized by dragging the flow component in the visual editing interface, meanwhile, the communication flow of the edited service flow and ICE SDK proxy service is packaged into a custom node by utilizing the expansion characteristic of the custom node, the purposes of universality and simplicity are achieved, a custom node is directly dragged, the communication can be established with the corresponding ICE SDK proxy service by filling the address parameter of the corresponding ICE SDK proxy service, and a set of packaging flow is realized. And if the certain projects do not need to integrate certain ICE general monitoring services, deleting the custom nodes corresponding to the ICE general monitoring services in the visual arrangement interface.

In one embodiment, as shown in fig. 4, the service orchestration module is configured to orchestrate a service flow, encapsulate communication functions of the service flow and the ICE SDK proxy service into custom nodes, connect each ICE generic monitoring service and the ICE SDK proxy service to each other, connect each ICE SDK proxy service to the custom nodes of the service flow through a unified interface protocol, and connect each ICE SDK proxy service to a central server, and connect the service orchestration module to a client.

When the ICE SDK proxy service is started, parameter information (IP and port of ICE general monitoring service, IP and port of ICE SDK proxy service, station name, station ID and other information) is transmitted to a central server, a client can acquire the parameter information of deployed ICE SDK proxy service through the central server, after the client establishes communication with service arrangement, the client transmits the service parameter information to a corresponding service flow, and the service flow requests the corresponding ICE SDK proxy service to call the corresponding ICE general monitoring service according to the service parameter information so as to realize the service flow. The ICE SDK proxy service is separated from the client to be made into independent proxy service, even if one ICE SDK proxy service is abnormal, other ICE SDK proxy services and clients are not affected, flexible expansion of ICE general monitoring service is supported, when a certain monitoring ICE basic service combination needs to be deleted, the monitoring ICE basic service combination is deleted, and corresponding custom nodes are deleted, if the ICE general monitoring service of a new cooperator is needed to be docked in the later period, the business function can be realized by newly creating a custom node and newly creating an ICE SDK proxy service to be docked with the ICE general monitoring service provided by the cooperator, and in the process, the client does not need to be compiled again, so that the flexibility of editing the ICE service is greatly improved.

In the embodiment of the invention, the proxy services are separated from the client to be made into independent proxy services, so that the coupling between ICE services is released, each proxy service is not affected by the other proxy services as an atomic service, even if one of the proxy services is abnormal, the other proxy services are not affected, in the process of dynamically adding or deleting the ICE services and the corresponding proxy services, the other proxy services and ICE services in the whole service flow are not affected, and the whole client does not need to compile again, so that a user can flexibly expand the ICE services, and the flexibility of arranging the service flow is greatly improved.

In addition, the embodiment of the invention realizes the connection between the custom node and the ICE SDK proxy service through the unified interface protocol based on websocket/http, is unified and flexible, and is more convenient in the adaptation process. And when the service flow is arranged, the user-defined node can establish communication with the corresponding ICE SDK proxy service by dragging the user-defined node and filling the address parameter of the corresponding ICE SDK proxy service, so that the flexibility of arranging the service flow is further improved.

Example two

As shown in fig. 5, fig. 5 is a schematic diagram of an ICE service orchestration device according to an embodiment of the present invention, where the ICE service orchestration device includes an encapsulation module 201, a connection module 202, a node encapsulation module 203, an information receiving module 204, and a communication establishment module 205;

the encapsulation module 201 is configured to encapsulate ICE service components corresponding to each ICE service into proxy services;

the connection module 202 is configured to connect each ICE service with a corresponding proxy service;

the node encapsulation module 203 is configured to orchestrate service flows, encapsulate communication functions of the service flows and proxy services into custom nodes, where the number of service flows is at least one, and one service flow at least corresponds to one custom node;

the information receiving module 204 is configured to receive parameter information of a target proxy service, where the parameter information is used to execute a target service flow;

the communication establishing module 205 is configured to establish a communication connection between the target custom node and the target proxy service according to the parameter information, and call the corresponding ICE service through the communication connection when executing the target service flow, where the target custom node is a custom node corresponding to the target service flow.

Based on the above embodiment, the communication establishment module 205 is configured to establish a communication connection between the target custom node and the target proxy service specifically:

the method is used for establishing communication connection between the target custom node and the target proxy service through a preset interface protocol.

Based on the above embodiment, the interface protocol is a unified interface protocol based on websocket/http.

Based on the above embodiment, the communication establishing module 205 is configured to establish, according to the parameter information, a communication connection between the target custom node and the target proxy service specifically as follows:

the method is used for inputting the address parameters of the target proxy service into the target custom node so that the target custom node can find the target proxy service according to the address parameters and establish communication connection with the target proxy service.

On the basis of the above embodiment, the address parameter includes the IP of the target proxy service and the port of the target proxy service, and the address parameter further includes the IP of the target ICE service and the port of the target ICE service connected to the target proxy service.

Based on the above embodiment, the node encapsulation module 203 is configured to schedule a service flow specifically as follows:

the service process is arranged in the visual arrangement interface in a mode of dragging a process component, and the process component is provided by the visual arrangement interface.

Example III

The present embodiment also provides a terminal device, as shown in fig. 6, a terminal device 30, the terminal device including a processor 300 and a memory 301;

the memory 301 is used for storing a computer program 302 and transmitting the computer program 302 to the processor;

the processor 300 is configured to perform the steps of one of the ICE service orchestration method embodiments described above according to instructions in the computer program 302.

Illustratively, the computer program 302 may be partitioned into one or more modules/units that are stored in the memory 301 and executed by the processor 300 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing the specified functions, which instruction segments are used for describing the execution of the computer program 302 in the terminal device 30.

The terminal device 30 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud ICE server, etc. The terminal device 30 may include, but is not limited to, a processor 300, a memory 301. It will be appreciated by those skilled in the art that fig. 6 is merely an example of the terminal device 30 and is not meant to be limiting of the terminal device 30, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., the terminal device 30 may also include input and output devices, network access devices, buses, etc.

The processor 300 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 301 may be an internal storage unit of the terminal device 30, such as a hard disk or a memory of the terminal device 30. The memory 301 may also be an external storage terminal device of the terminal device 30, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 30. Further, the memory 301 may also include both an internal storage unit and an external storage device of the terminal device 30. The memory 301 is used for storing the computer program and other programs and data required by the terminal device 30. The memory 301 may also be used to temporarily store data that has been output or is to be output.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution contributing to the prior art or in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, an ICE server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media in which computer programs can be stored.

Example IV

Embodiments of the present invention also provide a storage medium containing computer executable instructions which, when executed by a computer processor, are for performing an ICE service orchestration method, the method comprising the steps of:

connecting each ICE service with a corresponding proxy service;

arranging service flows, packaging communication functions of the service flows and proxy services into custom nodes, wherein the number of the service flows is at least one, and one service flow at least corresponds to one custom node;

and establishing communication connection between the target custom node and the target proxy service according to the parameter information, and calling the corresponding ICE service through the communication connection when executing the target service flow, wherein the target custom node is a custom node corresponding to the target service flow.

Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present application is not limited to the ICE service orchestration method described above, and may also perform relevant operations in the ICE service orchestration method provided in any embodiment of the present application.

The ICE service orchestration device, the terminal device, and the storage medium provided in the foregoing embodiments may perform the ICE service orchestration method provided in any embodiment of the present application, and technical details not described in detail in the foregoing embodiments may be referred to the ICE service orchestration method provided in any embodiment of the present application.

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the embodiments of the present invention are not limited to the particular embodiments described herein, but are capable of numerous obvious changes, rearrangements and substitutions without departing from the scope of the embodiments of the present invention. Therefore, while the embodiments of the present invention have been described in connection with the above embodiments, the embodiments of the present invention are not limited to the above embodiments, but may include many other equivalent embodiments without departing from the spirit of the embodiments of the present invention, and the scope of the embodiments of the present invention is determined by the scope of the appended claims.

Claims

1. An ICE service orchestration method, comprising the steps of:

connecting each ICE service with a corresponding proxy service; the ICE service is ICE general monitoring service, and the proxy service is ICE SDK proxy service;

2. The ICE service orchestration method according to claim 1, wherein the specific process of establishing the communication connection between the target custom node and the target proxy service is:

3. An ICE service orchestration method according to claim 2 wherein the interface protocol is a websocket/http based unified interface protocol.

4. An ICE service orchestration method according to claim 1 wherein the parameter information includes address parameters of the target proxy service.

5. The ICE service orchestration method according to claim 4, wherein the specific process of establishing the communication connection between the target custom node and the target proxy service according to the parameter information is:

6. The ICE service orchestration method according to claim 5, wherein the address parameters include the IP of the target proxy service and the port of the target proxy service, and the address parameters further include the IP of the target ICE service and the port of the target ICE service connected to the target proxy service.

7. The ICE service orchestration method according to claim 1, wherein the specific process of orchestrating service flows is:

8. The ICE service arrangement device is characterized by comprising an encapsulation module, a connection module, a node encapsulation module, an information receiving module and a communication establishment module;

the connection module is used for connecting each ICE service with a corresponding proxy service; the ICE service is ICE general monitoring service, and the proxy service is ICE SDK proxy service;

9. A terminal device, characterized in that the terminal device comprises a processor and a memory;

the processor is configured to execute an ICE service orchestration method according to instructions in the computer program, according to any one of claims 1-7.

10. A storage medium storing computer executable instructions which, when executed by a computer processor, are for performing an ICE service orchestration method according to any one of claims 1-7.