CN112511607A - Edge node system of content distribution network - Google Patents
Edge node system of content distribution network Download PDFInfo
- Publication number
- CN112511607A CN112511607A CN202011294018.9A CN202011294018A CN112511607A CN 112511607 A CN112511607 A CN 112511607A CN 202011294018 A CN202011294018 A CN 202011294018A CN 112511607 A CN112511607 A CN 112511607A
- Authority
- CN
- China
- Prior art keywords
- plug
- ins
- distribution network
- content distribution
- edge node
- 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
Images
Classifications
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the present application provides a content delivery network edge node system, including a gateway, a cache system, a source return system, and further including: the plug-in script programming unit is used for editing the script codes and generating plug-ins according to the script codes; the plug-in running unit is used for the environment of plug-in running; the plug-in pool manages all plug-ins loaded by one http connection; and the plug-in configuration unit is used for configuring and managing the plug-ins in the visual interface. According to the system disclosed by the invention, the functional module is operated in a plug-in mode, and a user can realize different requirements by configuring and loading different plug-ins.
Description
Technical Field
The application relates to the technical field of CDN (content delivery network) networks, in particular to a content delivery network edge node system.
Background
Existing content distribution network edge nodes typically have some common functions, such as timestamp hotlists, IP blacklists, Referer hotlists, custom request headers, response headers, and so on. Obviously, the content distribution network edge node with more powerful functions cannot completely meet the requirements of all customers, and if the customers have special requirements, the general content distribution network edge node cannot be competent, and the system functions need to be expanded. The existing content distribution network edge node technical scheme often needs to develop and upgrade node module software in function extension to meet the requirements of customers, however, upgrade development has the defects of long release period and high development and maintenance cost, so that the existing content distribution network edge node technical scheme often only serves large customers, meanwhile, as the requirements of customers and service duration are changed, the requirements of different customers are often different, manufacturers are required to do a large amount of repeated development work for customized requirements of different customers, codes are disordered, the maintenance amount of the codes is large, the maintenance and management cost of the codes is gradually increased, and meanwhile, the iteration of a system is also very inexhaustible.
In summary, the existing technical solutions of the content distribution network edge node have the problems of long development period, large code maintenance amount, high maintenance cost, and the like.
Disclosure of Invention
In order to solve the above-mentioned defects existing in the prior art, the present invention aims to provide a user-customizable content distribution network edge node system, wherein a user can customize its own functional requirements into modules, and different requirements are realized by configuring and loading different modules.
The invention discloses a content distribution network edge node system, which comprises a gateway, a cache system and a source returning system, and also comprises: a plug-in script programming unit: the plug-in board is used for providing editing of script codes and generating plug-ins according to the script codes; a plug-in running unit: an environment for plug-in operation; plug-in component pool: the plug-in pool manages all plug-ins loaded by http connection; a plug-in configuration unit: the method is used for configuring and managing the plug-in the visual interface.
Further, the system also comprises a plug-in library which is used for storing and managing all plug-ins for use.
Furthermore, the plug-in library comprises a general plug-in library and a user plug-in library, the general plug-in library comprises a plurality of plug-ins provided by default by the system, and the user plug-in library comprises all user-defined plug-ins.
Further, the universal plug-in library comprises: listen plug-in: the device is used for monitoring and processing Listen Hooks events; caching the key value plug-in: the method comprises the steps of monitoring and processing Hooks events of cache key values; caching the validity plug-in: the method is used for monitoring and processing the cached Hooks event; returning a source plug-in: the method is used for monitoring and processing the homeks events and carrying out corresponding processing.
Furthermore, the user-defined plug-in supports script code development.
Further, the plug-ins include a Hooks plug-in, wherein the Hooks plug-in is formed based on the processing unit of the event definition of the content distribution network.
Further, the plug-in also comprises a middleware plug-in, and the middleware plug-in is a customized function module based on the events of the content distribution network.
Further, the operation sequence of the middleware plug-in is related to the weight setting of the middleware.
Further, the plug-in running unit includes: production and operation environments are as follows: an environment provided for the user to use for installing and running the plug-in; simulating an operation environment: the function is consistent with the production running environment, and the environment is used for verifying the running quality of the plug-in.
The system further comprises a plug-in sharing unit, wherein the plug-in sharing unit is used for sharing the plug-in defined by the user to a third party for use.
As described above, the content distribution network edge node system provided by the invention supports plug-in operation of the functional module, the user plugs in the required script code, and the plug-in of the user is installed in the processing flow through the plug-in configuration of the system, thereby realizing the personalized requirements of the user.
In summary, the system disclosed by the present invention has the following obvious advantages in terms of satisfying the personalized requirements of users for the content distribution network edge node system:
1. the development cost is reduced: the user codes are plugged in and separated from a system core function module, and meanwhile, the development of each plug-in is independent, and manual operations such as cooperation, communication and the like are not needed, so that the user can develop customized plug-ins according to the self requirements, and the development cost is reduced.
2. The maintenance cost is reduced: the code of each plug-in is maintained by the user independently, so that the maintenance cost is reduced, and the influence of the modification of the code of the individual user on the functions of the whole system is greatly reduced.
3. Easy upgrading and expanding: because the plug-in is relatively independent and does not affect the whole system framework and other functions, the function extension and maintenance of the plug-in at the later stage are only related to the requirements of users, and the upgrading extension work is more agile.
In order that the invention may be more clearly and fully understood, specific embodiments of the disclosed method, network, system and electronic device are described in detail below with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
Fig. 1 is a schematic architecture diagram of an edge node system of a content distribution network according to an embodiment.
Fig. 2 is a schematic diagram of a configuration issuing process in an embodiment.
FIG. 3 is a flow diagram that illustrates a request for resources from a content distribution network in one embodiment.
Detailed Description
Embodiments and examples of the present invention will be described in detail below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a schematic diagram of an architecture of a content distribution network edge node system according to an embodiment, and as shown in the diagram, the system 10 includes: the system comprises a gateway 100, a plug-in script programming unit 101, a plug-in running unit 102, a plug-in pool 103, a plug-in configuration unit 104, a cache system 105 and a back-to-source system 106, wherein:
the plug-in script programming unit 101: the plug-in module is used for providing editing of script codes and generating plug-ins according to the script codes.
The plug-in operation unit 102: the method is used for the environment of plug-in operation.
The plug-in pool 103: the plug-in pool manages all plug-ins loaded by one http connection.
Plug-in configuration unit 104: the method is used for configuring and managing the plug-in the visual interface.
The plug-in of the system 10 refers to a configurable plug-in module formed by separating the functional module of the user from the system main body frame, and determines whether to load the system for operation or not through configuration.
In one embodiment, the plug-ins of the system include a Hooks plug-in that is formed based on processing units defined by events of the content distribution network and a middleware plug-in that is based on a customized function module outside the events of the content distribution network, such as a timestamp hotlink, an IP blacklist, a Referer hotlink, a custom request header, a response header, and the like.
In one embodiment, the system provides by default some generic plug-ins, including:
listen plug-in: the device is used for monitoring and processing Listen Hooks events;
caching the key value plug-in: the method comprises the steps of monitoring and processing Hooks events of cache key values;
caching the validity plug-in: the method is used for monitoring and processing the cached Hooks event;
returning a source plug-in: the method is used for monitoring and processing the homeks events and carrying out corresponding processing.
In addition, the user can customize his own plug-in through the plug-in script programming unit 101, and the user-defined plug-in supports script code development, such as a customized authentication logic plug-in, a customized request header response header control, a customized rewriting redirection plug-in, a customized cache control plug-in, a customized speed limit plug-in, and the like.
The plug-ins developed by the plug-in script programming unit 101 are further configured into the service by the plug-in configuration unit 104, and the system loads and runs the plug-ins according to the configuration.
The system provides a plug-in execution unit 102 for executing a plug-in, and in one embodiment, the plug-in execution unit 102 is divided into a simulation execution environment and a production execution environment, wherein the production execution environment: an environment provided for the user to use for installing and running the plug-in; simulating an operation environment: the function is consistent with the production running environment, and the environment is used for verifying the running quality of the plug-in. The plug-in unit can be ensured to reliably operate in the production environment through the verification step of the plug-in unit in the simulation environment.
In one embodiment, the system further includes a plug-in library for storing and managing all plug-ins for use. The plug-in library comprises a general plug-in library and a user plug-in library, the general plug-in library comprises a plurality of system default provided plug-ins, and the user plug-in library comprises all user-defined plug-ins. After the user-defined plug-ins are written, the user plug-in library is stored, and the stored user plug-in library can be set in a shared state for other users to use.
Referring to fig. 2, fig. 2 is a schematic diagram of a configuration issuing process in an embodiment, which specifically includes steps S21 to S24:
step S21: a domain name is created.
The domain name is the smallest unit of the content distribution network configuration. The domain name configuration of the invention can be divided into basic configuration and plug-in configuration, and the domain name, namely the basic configuration of the domain name, is created.
Step S22: a Hooks plugin is configured.
In one embodiment, after the domain name is created, basic attributes of the Hooks plug-in are required to be configured, the system provides a default Hooks plug-in, such as a Listen Hooks plug-in, and the attributes of the plug-in are required to be configured, such as whether the domain name is required to open https, whether the https is open, and the domain name certificate and the private key are required to be configured.
Step S23: and configuring the middleware plug-in.
In one embodiment, after configuration of the Hooks plug-in, the middleware plug-in needs to be configured. The middleware plug-in is not necessary for the system, and the content distribution network does not require a default middleware plug-in after the domain name is created.
Users can customize and add the middleware plug-in according to the needs of the users. The middleware plug-in represents the characteristics of a content distribution network, such as a timestamp anti-theft chain, an IP black and white list, a refer anti-theft chain, a custom request header, a response header and the like, and the requirements of some users are different from the general requirements, so that the users need to write the middleware plug-in which meets the requirements of the users, such as customized authentication logic, customized request header response header control, customized rewriting redirection, customized cache control, customized speed limit and the like.
Step S24: and operating the plug-in.
When the configuration of the plug-in is completed, the plug-in needs to be operated, and the operation of the plug-in needs to be in an isolated container environment so as to prevent the whole content distribution network from being overwhelmed due to the exception of the operation process of the plug-in.
The operation environment of the plug-in can be divided into a simulation operation environment and a production operation environment, and when the plug-in runs in the simulation operation environment for a period of time to ensure no problem, the configured plug-in can be issued to the production operation environment.
Referring to fig. 3, fig. 3 is a schematic flow chart illustrating a process of requesting resources from a content distribution network in an embodiment, which specifically includes steps S31 to S35:
step S31: the gateway receives a request instruction for requesting content.
First, the gateway receives an http request instruction for requesting content.
Step S32: and the gateway inquires the configured plug-in according to the request and executes the obtained plug-in.
In one embodiment, the gateway triggers the Listen Hooks event according to the received request, queries the plug-in corresponding to the Listen Hooks event configured by the domain name through the configuration center, runs the plug-in, queries whether the domain name is configured with the middleware plug-in through the configuration center, and if the middleware plug-in is configured, executes the process in sequence from big to small according to the weight of the middleware plug-in.
Step S33: and the cache module triggers the corresponding plug-in to execute the plug-in to acquire the resource content.
In one embodiment, the gateway forwards the request to the cache module, which specifically includes the following implementation steps:
1) the gateway forwards the request to a cache module, and the cache module triggers a cache key value Hooks event;
2) the cache module executes the plug-in corresponding to the cache key value Hooks event and acquires the cache key value according to the execution result of the plug-in;
3) the cache module inquires a cache result according to the cache key value;
4) starting a cache module to cache the dates Hooks event and executing the corresponding plug-in;
5) the cache module judges whether the cache is overdue or not according to the execution result of the plug-in with the validity period;
6) if the cache is overdue, the cache content is deleted, and the request is not forwarded to the back source module.
Step S34: and the source returning module triggers the corresponding plug-in to execute the plug-in to acquire the resource content.
In one embodiment, if the resource is not obtained in the previous step, the cache module forwards the request to the back-to-source module, and after the back-to-source module receives the request, the following steps are specifically executed:
1) triggering a source returning Hooks event by the source returning module, and executing a corresponding plug-in;
2) and the back-source plug-in unit forwards the request to the source station according to the own strategy of the plug-in unit and obtains the resource content returned by the source station.
Step S35: and returning the acquired resources.
In one embodiment, the step of returning the resource is as follows:
1) if the back source module obtains the resource, the back source module returns the resource content obtained by the back source plug-in unit to the cache module;
2) if the cache module obtains the resources, the cache module stores the resources and returns the resources to the gateway;
3) and if the gateway obtains the resources, the gateway returns the resource result to the client.
It should be noted that, all or part of the steps in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, which may include, but is not limited to: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A content distribution network edge node system comprises a gateway, a cache system and a back source system, and is characterized by further comprising:
a plug-in script programming unit: the plug-in board is used for providing editing of script codes and generating plug-ins according to the script codes;
a plug-in running unit: an environment for plug-in operation;
plug-in component pool: the plug-in pool manages all plug-ins loaded by http connection;
a plug-in configuration unit: the method is used for configuring and managing the plug-in the visual interface.
2. A content distribution network edge node system as claimed in claim 1 further comprising a plug-in library for storing and managing all plug-ins for use.
3. The content distribution network edge node system of claim 2, wherein the plug-in library comprises a generic plug-in library and a user plug-in library, the generic plug-in library comprising a plurality of system default provided plug-ins, the user plug-in library comprising all user-customized plug-ins.
4. A content distribution network edge node system as claimed in claim 3 wherein said generic plug-in library comprises:
listen plug-in: the device is used for monitoring and processing Listen Hooks events;
caching the key value plug-in: the method comprises the steps of monitoring and processing Hooks events of cache key values;
caching the validity plug-in: the method is used for monitoring and processing the cached Hooks event;
returning a source plug-in: the method is used for monitoring and processing the homeks events and carrying out corresponding processing.
5. A content distribution network edge node system as claimed in claim 3 wherein said user-defined plug-ins support scripting code development.
6. The content distribution network edge node system of claim 1, wherein the plug-ins comprise hookes plug-ins, wherein a Hooks plug-in is a plug-in formed based on an event defined processing unit of the content distribution network.
7. The content distribution network edge node system of claim 6, wherein the plug-ins further comprise middleware plug-ins, the middleware plug-ins being off-event customized function modules based on the content distribution network.
8. The method of claim 7, wherein the order in which the middleware plug-ins are run is dependent on the weight settings of the middleware.
9. A content distribution network edge node system as claimed in claim 1, wherein said plug-in execution unit comprises:
production and operation environments are as follows: an environment provided for the user to use for installing and running the plug-in;
simulating an operation environment: the function is consistent with the production running environment, and the environment is used for verifying the running quality of the plug-in.
10. The content distribution network edge node system of claim 1, further comprising a plug-in sharing unit for sharing a user-defined plug-in to a third party for use.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011294018.9A CN112511607A (en) | 2020-11-18 | 2020-11-18 | Edge node system of content distribution network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011294018.9A CN112511607A (en) | 2020-11-18 | 2020-11-18 | Edge node system of content distribution network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112511607A true CN112511607A (en) | 2021-03-16 |
Family
ID=74956829
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011294018.9A Pending CN112511607A (en) | 2020-11-18 | 2020-11-18 | Edge node system of content distribution network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112511607A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120281649A (en) * | 2025-06-05 | 2025-07-08 | 天翼云科技有限公司 | Service updating method, device, computer equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100313029A1 (en) * | 2009-06-03 | 2010-12-09 | Microsoft Corporation | Add-ins dynamically extending display targets and business-logic programming model |
| US8751466B1 (en) * | 2014-01-12 | 2014-06-10 | Machine Intelligence Services, Inc. | Customizable answer engine implemented by user-defined plug-ins |
| CN104991760A (en) * | 2014-12-23 | 2015-10-21 | 广州亦云信息技术有限公司 | PaaS platform service management system based on distributed modular technology and realization method |
| CN105893413A (en) * | 2015-11-26 | 2016-08-24 | 乐视云计算有限公司 | Service extension method and extension system for server |
| CN107102877A (en) * | 2017-04-26 | 2017-08-29 | 国网辽宁省电力有限公司信息通信分公司 | A kind of adaptive approach of browser-cross plug-in unit |
| CN107491308A (en) * | 2017-08-15 | 2017-12-19 | 成都民航空管科技发展有限公司 | Utilize script and the system and method for plug-in unit fast custom multipoint positioning monitoring system |
| CN109542445A (en) * | 2017-08-01 | 2019-03-29 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus that Android plug-in unit melts hair |
-
2020
- 2020-11-18 CN CN202011294018.9A patent/CN112511607A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100313029A1 (en) * | 2009-06-03 | 2010-12-09 | Microsoft Corporation | Add-ins dynamically extending display targets and business-logic programming model |
| US8751466B1 (en) * | 2014-01-12 | 2014-06-10 | Machine Intelligence Services, Inc. | Customizable answer engine implemented by user-defined plug-ins |
| CN104991760A (en) * | 2014-12-23 | 2015-10-21 | 广州亦云信息技术有限公司 | PaaS platform service management system based on distributed modular technology and realization method |
| CN105893413A (en) * | 2015-11-26 | 2016-08-24 | 乐视云计算有限公司 | Service extension method and extension system for server |
| CN107102877A (en) * | 2017-04-26 | 2017-08-29 | 国网辽宁省电力有限公司信息通信分公司 | A kind of adaptive approach of browser-cross plug-in unit |
| CN109542445A (en) * | 2017-08-01 | 2019-03-29 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus that Android plug-in unit melts hair |
| CN107491308A (en) * | 2017-08-15 | 2017-12-19 | 成都民航空管科技发展有限公司 | Utilize script and the system and method for plug-in unit fast custom multipoint positioning monitoring system |
Non-Patent Citations (1)
| Title |
|---|
| 杨为禄等: "基于.NET的开放平台的体系结构研究", 《工业控制计算机》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120281649A (en) * | 2025-06-05 | 2025-07-08 | 天翼云科技有限公司 | Service updating method, device, computer equipment and storage medium |
| CN120281649B (en) * | 2025-06-05 | 2025-09-05 | 天翼云科技有限公司 | Service update method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112000348B (en) | Control method, device and computer equipment for service gray level release | |
| US9936005B1 (en) | Systems and methods for distributed API gateways | |
| CN112612629B (en) | Method and system for realizing component type data interface | |
| US20220103613A9 (en) | Auto-documentation for application program interfaces based on network requests and responses | |
| CN103209223B (en) | distributed application session information sharing method, system and application server | |
| CN101515926B (en) | Device management method for device management system | |
| CN103297275B (en) | Web network management client module Dynamic Discovery and loading method | |
| US20190034210A1 (en) | Systems and methods for distributed api gateways | |
| CN111371679A (en) | Method for realizing API gateway based on kubernets and Kong | |
| CN102355500B (en) | Service push method and device | |
| CN113595788B (en) | API gateway management method and device based on plug-in | |
| CN112764751B (en) | Interface generation method and device, interface request method and device and storage medium | |
| CN109948356A (en) | One kind is based on service call authority control method under micro services framework | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| CN115220874B (en) | Kubernetes cluster deployment method, device, equipment and storage medium | |
| WO2020238344A1 (en) | Rapid sdk integration method and apparatus based on block chain, device and device and storage medium | |
| CN111556488A (en) | OTA (over the air) upgrading method and system for terminal equipment | |
| CN109451014B (en) | WebService agent system and transparent agent method thereof | |
| CN114036236B (en) | Multi-gateway cluster system | |
| CN108351923A (en) | Threshold value related with the script that unified Extensible Firmware Interface system is executable | |
| CN102437998A (en) | Application store system and method by utilizing same to develop | |
| CN115794445B (en) | Data processing method, device and equipment based on flink and rule expression | |
| CN112511607A (en) | Edge node system of content distribution network | |
| US20250158888A1 (en) | Address library construction method and apparatus applied to cdn, device, and medium | |
| US20100218202A1 (en) | Method and Apparatus for Case-Based Service Composition |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210316 |