CN117527579A - Method and device for configuring and realizing service docking - Google Patents
Method and device for configuring and realizing service docking Download PDFInfo
- Publication number
- CN117527579A CN117527579A CN202311612608.5A CN202311612608A CN117527579A CN 117527579 A CN117527579 A CN 117527579A CN 202311612608 A CN202311612608 A CN 202311612608A CN 117527579 A CN117527579 A CN 117527579A
- Authority
- CN
- China
- Prior art keywords
- api
- docking
- plug
- different
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003032 molecular docking Methods 0.000 title claims abstract description 74
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000006243 chemical reaction Methods 0.000 claims abstract description 55
- 238000004891 communication Methods 0.000 claims abstract description 30
- 230000007246 mechanism Effects 0.000 claims abstract description 17
- 239000008186 active pharmaceutical agent Substances 0.000 claims abstract description 10
- 238000007726 management method Methods 0.000 claims description 26
- 230000008569 process Effects 0.000 claims description 11
- 230000003993 interaction Effects 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 abstract description 3
- 238000012546 transfer Methods 0.000 abstract description 3
- 238000011161 development Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 210000001503 joint Anatomy 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
- H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/2866—Architectures; Arrangements
- H04L67/2871—Implementation details of single intermediate entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method and a device for realizing service docking by configuration, comprising the following steps: realizing API docking, docking system expansion mechanism and different communication protocol conversion mechanism by configuration; after the three steps are completed, a plug-in type extensible framework is formed, APIs of different systems can be quickly docked, so that the systems have higher maintainability and expansibility, and therefore, a developer can simply and efficiently customize and develop own products, and the development efficiency is improved; in order to meet the docking requirements of different fields and types of services, the API docking is realized by adopting modes of unified authentication, parameter configuration, parameter conversion and the like, so that a user can easily realize the API docking with different service providers through configuration, and the universality and the flexibility of the API docking are ensured; the device also has other functions such as unified authentication, data transfer, logging and monitoring alarms, etc. to ensure stability and reliability of the API connection.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for realizing service docking by configuration.
Background
With the advancement of technology and the development of technology, more and deeper cooperation and communication are needed among different fields, different scenes and different service providers to realize more efficient and specialized services. Therefore, there is an increasing need to interface with a plurality of different external systems in different enterprise customers and different business scenarios, and the importance of service interfacing is becoming increasingly apparent. How to quickly and effectively dock different system APIs in order to bring more efficient and convenient service docking experience to service providers and users has become a focus of research. However, the existing service docking method and device still have some problems that affect the implementation efficiency of service docking:
(1) Existing service docking methods and apparatus generally require significant time and labor costs and are inefficient.
(2) Due to the differences among service providers, the docking methods among services of different architectures are different, and applicability, universality and flexibility are lacking.
(3) Existing service docking methods and apparatus still have certain limitations in terms of performance and functionality.
Disclosure of Invention
The invention aims to provide a method and a device for realizing service docking by configuration, which are used for solving the problems in the background technology.
In order to solve the technical problems, the invention provides the following technical scheme: a method for configuring an implementation of service docking, comprising the steps of:
s1, realizing API docking through configuration: realizing API (application program interface) docking in a configuration-based mode, and ensuring universality, flexibility and safety by configuring and docking services provided by different service providers to interact data with other systems under the condition of not changing codes;
s2, docking system expansion mechanism: according to the requirements of users, updating and expanding of a system are realized by modifying or adding an expansion plug-in, and the specific method is to realize a plug-in type and expandable architecture by using a strategy mode and a factory mode of the device, wherein the strategy mode can flexibly select different algorithms according to the difference of the requirements so as to realize different targets; the factory mode can create various different examples according to the difference of the input parameters, so that the function expansion is realized, and by using the two design modes, the docking system can freely increase or decrease the implementation of the plug-in and select the implementation of the plug-in according to the change of the requirement, so that the flexibility and the expandability of the system are enhanced.
S3, different communication protocol conversion mechanisms: different communication protocols are converted through a protocol conversion plug-in which can be compatible with multiple protocols.
According to the technical scheme, the method for realizing API docking through configuration comprises the following steps:
s1, unified authentication: before API docking, unified authentication is carried out on an API management platform, authority division is carried out on the API, user authentication is carried out on a docking calling party, and only users passing authentication are allowed to carry out API calling, otherwise, the user is refused;
s2, API allocation: in order to ensure that different APIs can be used between the systems, different API interfaces are allocated to different systems, and interface calling cannot conflict in the data interaction process between the systems;
s3, preparing and releasing API addresses and parameters: the method comprises the steps of exposing an API interface to other systems for use by configuring a release API address and parameters, and designating the format and the delivery mode of the parameters of the API, so that the other systems can accurately call the API and acquire a return result;
s4, configuring a docking API address and parameter conversion: according to different API interface requirements, configuring address and parameter conversion information of a docking API, realizing compatibility and conversion of parameters between different systems, and ensuring normal operation of the interfaces;
s5, service authentication: before service call is carried out, safety authentication is carried out on an interface caller according to the requirement of an interface issuing party, so that a system for calling an API is ensured to have legal authority;
s6, service calling: and sending the request to the target system, and acquiring a returned result, wherein in the process, the whole calling process is completed through configuration.
According to the technical scheme, the second docking system expansion mechanism is mainly embodied on three modules, namely plug-in management, product management and API management.
According to the technical scheme, the plug-in management is to expand the number of the system to be docked by adding, deleting or updating plug-ins, and the plug-in management is a pluggable module which can be developed and deployed independently of the docking system, and a user can freely select plug-ins provided by different service providers.
According to the technical scheme, the product management comprises the functions of inquiring, deleting and updating the product, and when the product is newly added, a developer can select a proper plug-in according to own requirements without re-developing the whole API docking system for a specific function.
According to the technical scheme, the API management comprises the functions of adding, deleting and updating the API interface, and a user flexibly configures and manages the API interface through the API management according to different service requirements, so that the seamless butt joint of the system and other systems is realized, and the expandability and maintainability of a program are improved.
According to the technical scheme, the operation principle of the protocol conversion plug-in applied in the third different communication protocol conversion mechanisms is as follows:
when the calling system needs to communicate with the called system, the calling system sends a request to a protocol conversion plug-in, the protocol conversion plug-in converts the request according to a communication protocol used by the called system and sends the converted request to the called system, the called system sends a result back to the protocol conversion plug-in after receiving the request, and the protocol conversion plug-in converts the result and then returns the converted result to the calling system.
An apparatus for configuring and implementing service docking, which adopts a method for configuring and implementing service docking as described above.
Compared with the prior art, the invention has the following beneficial effects:
(1) In order to meet the requirements of docking services in different fields and types, the API docking is realized by adopting modes of unified authentication, parameter configuration, parameter conversion and the like, so that a user can easily realize the API docking with different service providers through configuration, and the universality and the flexibility of the API docking are ensured.
(2) The plug-in type extensible architecture realized by adopting the strategy mode and the factory mode can effectively realize the rapid and convenient extension of the functions of the docking system.
(3) The protocol conversion plug-in can realize the conversion of communication protocols among different platforms so as to realize the data sharing and communication among the platforms.
(4) The device also has other functions such as unified authentication, data transfer, logging and monitoring alarms, etc. to ensure stability and reliability of the API connection.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
FIG. 1 is a schematic block diagram of an API release flow of the present invention;
FIG. 2 is a schematic block diagram of the operation flow of the docking system expansion mechanism of the present invention;
FIG. 3 is a schematic illustration of the operational flow of the present invention;
FIG. 4 is a schematic block diagram of the protocol conversion plug-in operation flow of the present invention;
fig. 5 is a general frame diagram of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1-5, the present invention provides the following technical solutions: a method for configuring an implementation of service docking, comprising the steps of:
s1, realizing API docking through configuration: realizing API (application program interface) docking in a configuration-based mode, and ensuring universality, flexibility and safety by configuring and docking services provided by different service providers to interact data with other systems under the condition of not changing codes;
in practical applications, data needs to be docked with a third party system, the systems usually all have independent API interfaces, the basic principle of API docking is to realize data transmission and call through interface specifications, so as to realize cooperative work between the systems, however, due to the differences and complexities existing between the systems, realizing API docking often faces some technical and configuration difficulties, firstly, data format and structure between the different systems may have differences, so that data conversion is needed to realize interactive operation, secondly, security mechanisms and authentication modes of the different systems may also be different, identity verification and authorization are needed, and furthermore, interface protocols and communication modes of the different systems may also be different, so that protocol adaptation and establishment of communication channels are needed.
S2, docking system expansion mechanism: according to the requirements of users, updating and expanding of a system are realized by modifying or adding an expansion plug-in, and the specific method is to realize a plug-in type and expandable architecture by using a strategy mode and a factory mode of the device; the strategy mode can flexibly select different algorithms according to the difference of requirements so as to realize different targets; the factory mode can create various different examples according to the difference of the input parameters, so that the expansion of functions is realized, and by using the two design modes, the docking system can freely increase and decrease components according to the change of requirements, so that the flexibility and the expandability of the system are enhanced.
S3, different communication protocol conversion mechanisms: different communication protocols are converted through a protocol conversion plug-in which can be compatible with multiple protocols.
In computer networks, communication protocols are a set of rules for standardizing and agreeing on data transmission, but in a multi-platform environment, protocols may vary from service provider to service provider or between software, which results in differences in communication protocols being a widespread problem. The main function of the protocol conversion plug-in is to solve the conversion problem between different communication protocols through one protocol conversion plug-in which can be compatible with multiple protocols.
According to the technical scheme, the method for realizing API docking through configuration comprises the following steps:
s1, unified authentication: before the API is in butt joint, unified authentication is carried out on an API management platform, the authentication is a mechanism for solving the security risk of an API interface, and the API interface is directly exposed on the Internet to have the security risk, so that the API is required to be subjected to authority division, the user authentication is carried out on an interface calling party, and only the user passing the authentication is allowed to carry out the API call, otherwise, the user passing the authentication is refused, so that malicious attack can be effectively prevented, and the security of the API interface is ensured.
S2, API allocation: in order to ensure that different APIs can be used between the systems, different API interfaces are allocated to different systems, and interface calling cannot conflict in the data interaction process between the systems;
s3, preparing and releasing API addresses and parameters: the address of the API refers to the URL address of the API, the parameters refer to input parameters required by the API, the API is exposed to other systems for use by configuring and releasing the API address and the parameters, and the format and the transmission mode of the parameters of the API are specified, so that the other systems can be ensured to call the API correctly and obtain a return result;
s4, configuring a docking API address and parameter conversion: according to different API interface requirements, configuring the address and parameter conversion information of a docking API, wherein the docking API address refers to the API address of a third party system to be docked, the parameter conversion refers to the conversion of parameters of a current system into a parameter format required by the docking system, and the compatibility and conversion of parameters among different systems are realized by configuring the docking API address and the parameter conversion, so that the normal operation of the interface is ensured;
s5, service authentication: only an authorized system can call an API interface, and before service call, safety authentication is carried out on an interface caller according to the requirement of an interface publisher, so that the system for calling the API is ensured to have legal authority;
s6, service calling: and sending the request to the target system, and acquiring a returned result, wherein in the process, the whole calling process is completed through configuration.
According to the technical scheme, the second docking system expansion mechanism is mainly embodied on three modules, namely plug-in management, product management and API management.
According to the technical scheme, the plug-in management is to expand the number of the system to be docked by adding, deleting or updating plug-ins, and the plug-in management is a pluggable module which can be developed and deployed independently of the docking system, and a user can freely select plug-ins provided by different service providers.
According to the technical scheme, the product management comprises the functions of inquiring, deleting and updating the product, and when the product is newly added, a developer can select a proper plug-in according to own requirements without re-developing the whole API docking system for a specific function.
According to the technical scheme, the API management comprises the functions of adding, deleting and updating the API interface, and a user flexibly configures and manages the API interface through the API management according to different service requirements, so that the seamless butt joint of the system and other systems is realized, and the expandability and maintainability of a program are improved.
According to the technical scheme, the operation principle of the protocol conversion plug-in applied in the third different communication protocol conversion mechanisms is as follows:
when the calling system needs to communicate with the called system, the calling system sends a request to a protocol conversion plug-in, the protocol conversion plug-in converts the request according to a communication protocol used by the called system and sends the converted request to the called system, the called system sends a result back to the protocol conversion plug-in after receiving the request, and the protocol conversion plug-in converts the result and then returns the converted result to the calling system.
The protocol conversion plug-in can solve the compatibility problem between different communication protocols, a user can communicate with the system through a communication protocol familiar to the user without knowing a specific communication protocol used by a called system, the called system only needs to send a request to the protocol conversion plug-in, the called system does not need to consider the communication protocol used by the protocol conversion plug-in, and only needs to receive the request of the protocol conversion plug-in and return a corresponding result.
The system has the advantages that the system has the capability of unified interfaces, so that the system integration becomes more convenient and flexible, both the cross-system communication and the communication between different modules in the same system can be realized by using the protocol conversion plug-in, the complexity of the system integration can be greatly simplified, and a developer does not need to pay attention to various different communication protocols and only needs to interact with the protocol conversion plug-in.
An apparatus for configuring and implementing service docking, which adopts a method for configuring and implementing service docking as described above.
Working principle:
in order to meet the docking requirements of different fields and types of services, the invention adopts modes of unified authentication, parameter configuration, parameter conversion and the like to realize API docking, so that a user can easily realize the API docking with different service providers through configuration, thereby ensuring that the user has universality and flexibility; the plug-in type expandable architecture realized by adopting the strategy mode and the factory mode can effectively realize the rapid and convenient expansion of the functions of the docking system; the protocol conversion plug-in is adopted, so that the conversion of communication protocols among different platforms can be realized, and the data sharing and communication among the platforms can be realized; the device also has other functions such as unified authentication, data transfer, logging and monitoring alarms, etc. to ensure stability and reliability of the API connection.
It is noted that relational terms such as first and second, and the like are 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, 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.
Finally, it should be noted that: the foregoing description is only a preferred embodiment of the present invention, and the present invention is not limited thereto, but it is to be understood that modifications and equivalents of some of the technical features described in the foregoing embodiments may be made by those skilled in the art, although the present invention has been described in detail with reference to the foregoing embodiments. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method for configuring to implement service interfacing, comprising the steps of:
s1, realizing API docking through configuration: realizing API (application program interface) docking in a configuration-based mode, and ensuring universality, flexibility and safety by configuring and docking services provided by different service providers to interact data with other systems under the condition of not changing codes;
s2, docking system expansion mechanism: according to the requirements of users, updating and expanding of a system are realized by modifying or adding an expansion plug-in, and the specific method is to realize a plug-in type and expandable architecture by using a strategy mode and a factory mode of the device;
s3, different communication protocol conversion mechanisms: different communication protocols are converted through a protocol conversion plug-in which can be compatible with multiple protocols.
2. The method for implementing service interfacing according to claim 1, wherein the step of implementing API interfacing by configuration comprises the steps of:
s1, unified authentication: before API docking, unified authentication is carried out on an API management platform, authority division is carried out on the API, user authentication is carried out on a docking calling party, and only users passing authentication are allowed to carry out API calling, otherwise, the user is refused;
s2, API allocation: in order to ensure that different APIs can be used between the systems, different API interfaces are allocated to different systems, and interface calling cannot conflict in the data interaction process between the systems;
s3, preparing and releasing API addresses and parameters: the method comprises the steps of exposing an API interface to other systems for use by configuring a release API address and parameters, and designating the format and the delivery mode of the parameters of the API, so that the other systems can accurately call the API and acquire a return result;
s4, configuring a docking API address and parameter conversion: according to different API interface requirements, configuring address and parameter conversion information of a docking API, realizing compatibility and conversion of parameters between different systems, and ensuring normal operation of the interfaces;
s5, service authentication: before service call is carried out, safety authentication is carried out on an interface caller according to the requirement of an interface issuing party, so that a system for calling an API is ensured to have legal authority;
s6, service calling: and sending the request to the target system, and acquiring a returned result, wherein in the process, the whole calling process is completed through configuration.
3. The method of claim 1, wherein the second docking system extension mechanism is implemented on three modules, namely plug-in management, product management and API management.
4. A method of configuring a service interface as claimed in claim 3, wherein: the plug-in management is to expand the number of the system to be docked by adding, deleting or updating plug-ins, is a pluggable module, can be developed and deployed independently of the docking system, and can be freely selected by users for plug-ins provided by different service providers.
5. A method of configuring a service interface as claimed in claim 3, wherein: the product management comprises the steps of inquiring, deleting and updating the product functions, and when a product is newly added, a developer can select a proper plug-in according to own requirements without re-developing the whole API docking system for a specific function.
6. A method of configuring a service interface as claimed in claim 3, wherein: the API management comprises the functions of adding, deleting and updating the API interface, and a user flexibly configures and manages the API interface through the API management according to different service requirements, so that the seamless connection between the system and other systems is realized, and the expandability and maintainability of the program are improved.
7. The method for implementing service docking according to claim 1, wherein the protocol conversion plug-in applied in the third different communication protocol conversion mechanism operates according to the following principle:
when the calling system needs to communicate with the called system, the calling system sends a request to a protocol conversion plug-in, the protocol conversion plug-in converts the request according to a communication protocol used by the called system and sends the converted request to the called system, the called system sends a result back to the protocol conversion plug-in after receiving the request, and the protocol conversion plug-in converts the result and then returns the converted result to the calling system.
8. An apparatus for configuring to implement service interfacing, characterized by: a method of implementing service interfacing using a configuration as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311612608.5A CN117527579A (en) | 2023-11-29 | 2023-11-29 | Method and device for configuring and realizing service docking |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311612608.5A CN117527579A (en) | 2023-11-29 | 2023-11-29 | Method and device for configuring and realizing service docking |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117527579A true CN117527579A (en) | 2024-02-06 |
Family
ID=89764318
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311612608.5A Pending CN117527579A (en) | 2023-11-29 | 2023-11-29 | Method and device for configuring and realizing service docking |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117527579A (en) |
-
2023
- 2023-11-29 CN CN202311612608.5A patent/CN117527579A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2621243B1 (en) | Method and system for configuring and managing third party software, and management server | |
| CN111797173B (en) | Alliance chain sharing system, method and device, electronic equipment and storage medium | |
| JP2012090281A (en) | Communications network | |
| CN102866925B (en) | Communication method and system for middleware and user interface | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN111258723B (en) | Transaction processing method, device, system, medium and equipment of distributed system | |
| US5615351A (en) | Method and system for correlating usage data in a distributed architecture | |
| CN113826424A (en) | Entity for providing external services to a network | |
| CN114244654B (en) | URL forwarding method, device, equipment and computer storage medium | |
| CN115225493A (en) | Wiraguard-based configuration generation method and equipment for networking nodes | |
| CN113010238A (en) | Permission determination method, device and system for micro application call interface | |
| KR100818962B1 (en) | Method for managing remote mobile device | |
| US8498302B2 (en) | System and method for exposing third party call functions of the intelligent network application part (INAP) as a web service interface | |
| CN117527579A (en) | Method and device for configuring and realizing service docking | |
| CN111008023A (en) | Instance deployment method and system | |
| CN110943975B (en) | Service registration method, device, computer equipment and storage medium | |
| CN108055337A (en) | The method and apparatus that multiple service platform docks public platform | |
| WO2021103644A1 (en) | Data structure, communication method and apparatus, storage medium and device | |
| CN110545527B (en) | Call forwarding method, video communication server and calling terminal | |
| CN102694670A (en) | Three-network integration widget management platform, realizing method thereof and system thereof | |
| JP2004362591A (en) | Service provision method of server to user by controlling user's confidential id | |
| CN111934928A (en) | Terminal equipment upgrading method, device, management platform, system and equipment | |
| CN109525660A (en) | A kind of method and system of ROS news release and subscription registration | |
| CN118175464B (en) | FTTR gateway upgrading method, gateway equipment, system and computer readable storage medium | |
| CN116389252B (en) | Method, device, system, electronic equipment and storage medium for updating container network |
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 |