CN115277816B - Service adaptation method, device, system and computer readable medium - Google Patents
Service adaptation method, device, system and computer readable medium Download PDFInfo
- Publication number
- CN115277816B CN115277816B CN202210824161.7A CN202210824161A CN115277816B CN 115277816 B CN115277816 B CN 115277816B CN 202210824161 A CN202210824161 A CN 202210824161A CN 115277816 B CN115277816 B CN 115277816B
- Authority
- CN
- China
- Prior art keywords
- service
- channel management
- service provider
- long connection
- information
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 51
- 230000006978 adaptation Effects 0.000 title claims description 31
- 238000012795 verification Methods 0.000 claims description 24
- 230000003993 interaction Effects 0.000 claims description 22
- 230000006870 function Effects 0.000 claims description 17
- 230000015654 memory Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 11
- 230000000977 initiatory effect Effects 0.000 claims description 8
- 230000008859 change Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 8
- 230000002452 interceptive effect Effects 0.000 description 6
- 206010047289 Ventricular extrasystoles Diseases 0.000 description 4
- 230000005291 magnetic effect Effects 0.000 description 4
- 238000005129 volume perturbation calorimetry Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 1
- 230000003936 working memory Effects 0.000 description 1
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/14—Session management
- H04L67/141—Setup of application sessions
Abstract
The application provides a service adapting scheme, in the scheme, a service calling party device does not adopt an IP direct connection mode to adapt to a service provided by a service provider device, but a channel management device is added between the service provider device and the service provider device, and as the channel management device can manage service information provided by the service provider device and long connection is established between the service calling party device and the service provider device, when the service calling party device needs to call a certain service, the service calling party device does not need to pay attention to a specific address of the service, only needs to interact with the channel management device, and the channel management device can forward data to a specific service provider device according to the service required to be called, so that the service call can be completed.
Description
Technical Field
The present application relates to the field of information technologies, and in particular, to a service adaptation method, device, system, and computer readable medium.
Background
Under a classical network, since the IP address of a service provided by a service provider is globally unique, when service adaptation is implemented, a service caller can directly connect with the service by directly using the IP address of the service to complete service adaptation, thereby initiating remote invocation of the service. Fig. 1 shows that under a classical network, each device 110 providing a service is deployed in a machine room, the IP address of each device 110 is globally unique, and when an APP (Application) in a client device 120 needs to call a certain service, the device providing the service can be directly connected to the component system MGS 130 based on the IP address, so as to initiate service call to the device.
However, under the VPC (Virtual Private Cloud ) network architecture, the IP address of the device providing the service is only unique inside a single VPC, but will no longer be globally unique in the individual VPCs. For example, two DCs (Data centers) respectively correspond to two VPCs, the IP addresses are unique in the DC1 or the DC2, but repeated IP addresses may occur between the DC1 and the DC2, if the MGS still uses the direct connection of the IP addresses for service adaptation, the MGS may adapt to wrong services, resulting in service call errors, and the APP in the client device cannot implement related functions.
Content of the application
An object of the present application is to provide a service adaptation scheme for solving the problem that the service adaptation cannot be correctly implemented in the existing scheme.
The embodiment of the application provides a service adaptation method of channel management equipment, which comprises the following steps:
the channel management equipment establishes a first long connection with the service provider equipment and stores service address information provided by the service provider equipment, wherein the service address information is used for determining the service provider equipment when the service is called;
the channel management device establishes a second long connection with the service calling device, wherein the first long connection and the second long connection are used for transmitting interaction data when the service calling device conducts service calling to the service provider device.
The embodiment of the application also provides a service adaptation method of the service calling party equipment, which comprises the following steps:
the service calling party equipment and the channel management equipment establish a second long connection, wherein the channel management equipment establishes a first long connection with service provider equipment for providing service, the channel management equipment stores service address information provided by the service provider equipment, the service address information is used for determining the service provider equipment when the service calling party equipment calls service, and the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment calls service to the service provider equipment.
The embodiment of the application also provides a service adaptation method of the service provider equipment, wherein the method comprises the following steps:
the service provider device establishes a first long connection with the channel management device and provides service address information provided by the service provider device for the channel management device, wherein the service address information is used for determining the service provider device when the service is called, the channel management device also establishes a second long connection with the service calling device, and the first long connection and the second long connection are used for transmitting interaction data when the service calling device calls the service provider device.
Based on another aspect of the present application, there is also provided a channel management apparatus, including:
a provider processing means for establishing a first long connection with a service provider device and storing service address information provided by the service provider device, the service address information being used for determining the service provider device at the time of service call;
and the caller processing device is used for establishing a second long connection with the service caller device, wherein the first long connection and the second long connection are used for transmitting interaction data when the service caller device makes service call to the service provider device.
The embodiment of the application also provides a service provider device, wherein the device comprises:
the connection processing device is used for establishing a first long connection with the channel management equipment and providing service address information provided by the service provider equipment for the channel management equipment, wherein the service address information is used for determining the service provider equipment when the service is called, the channel management equipment also establishes a second long connection with the service calling equipment, and the first long connection and the second long connection are used for transmitting interactive data when the service calling equipment calls the service provider equipment.
The embodiment of the application also provides a service adaptation system, wherein the system comprises:
a service provider device for establishing a first long connection with a channel management device and providing service address information provided by the service provider device to the channel management device, wherein the service address information is used for determining the service provider device when a service is called;
the channel management device is used for establishing a first long connection between the channel management device and the service provider device and storing service address information provided by the service provider device; and establishing a second long connection with the service caller device;
and the service calling party equipment is used for establishing a second long connection with the channel management equipment, wherein the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment performs service calling to the service provider equipment.
Furthermore, an embodiment of the present application provides a computing device, where the device includes a memory for storing computer program instructions and a processor for executing the computer program instructions, where the computer program instructions, when executed by the processor, trigger the device to execute the service adaptation method.
Embodiments of the present application also provide a computer readable medium having stored thereon computer program instructions executable by a processor to implement the service adaptation method.
In the scheme provided by the embodiment of the application, the service calling party equipment does not adapt to the service provided by the service provider equipment in an IP direct connection mode, but a channel management equipment is added between the service provider equipment and the service provider equipment, the channel management equipment establishes a first long connection with the service provider equipment and stores service information provided by the service provider equipment, and simultaneously establishes a second long connection with the service calling party equipment, wherein the service information is used for determining the service provider equipment when the service is called, and the first long connection and the second long connection are used for transmitting interactive data when the service calling party equipment calls the service to the service provider equipment. Because the channel management device can manage the service information provided by the service provider device, when the service caller device needs to call a certain service, the service caller device does not need to pay attention to the specific address of the service, only needs to interact with the channel management device, and the channel management device can forward data to the specific service provider device according to the service called as required, so that the service call can be completed.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 is a schematic diagram of a service adaptation scheme under a classical network;
FIG. 2 is a schematic diagram of a system employing a service adaptation method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of a service provider device under a VPC architecture;
FIG. 4 is a flowchart of an interaction process between devices when service adaptation is performed in an embodiment of the present application;
FIG. 5 is a schematic diagram of a data structure of information storage in a channel management device according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a data structure of information storage in a coordination device according to an embodiment of the present application;
FIG. 7 is an interactive flow chart of a channel management device establishing long connections between a service provider device and a service caller device for service adaptation, respectively, in an embodiment of the present application;
FIG. 8 is an interactive flow chart of service invocation in one embodiment of the application;
FIG. 9 is a schematic diagram of a computing device for implementing service adaptation according to an embodiment of the present application;
the same or similar reference numbers in the drawings refer to the same or similar parts.
Detailed Description
The application is described in further detail below with reference to the accompanying drawings.
In one exemplary configuration of the application, the terminal, the devices of the services network each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, program devices, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device.
The embodiment of the application provides a service adaptation method, in which a service calling party device does not adapt to a service provided by a service provider device in an IP direct connection manner, but adds a channel management device between the service provider device and the service provider device, and as the channel management device can manage service information provided by the service provider device and long connection is established between the service calling party device and the service provider device, when the service calling party device needs to call a certain service, the service calling party device does not need to pay attention to a specific address of the service, only needs to interact with the channel management device, and the channel management device can forward data to a specific service provider device according to the service required to be called, so that the service call can be completed.
Fig. 2 shows a schematic diagram of a system employing a service adaptation method provided by an embodiment of the present application, where the system includes a service caller device 210, a service provider device 220, and a channel management device 230. The service provider device 210 is configured to establish a first long connection with a channel management device, and provide service information provided by the service provider device to the channel management device, where the service information is used to determine the service provider device when a service is invoked. The channel management device 220 is configured to establish a first long connection between the channel management device and the service provider device, and store service information provided by the service provider device; and establishing a second long connection with the service caller device. The service caller device 230 is configured to establish a second long connection with the path management device, where the first long connection and the second long connection are used to transmit interaction data when the service caller device makes a service call to the service provider device.
In an actual scenario, the specific implementation of the foregoing device may be a server, a network host, a user terminal, or other entity devices, or may be a virtual device running on a Cloud Computing platform, where the Cloud Computing platform is composed of a large number of hosts or network servers based on Cloud Computing (Cloud Computing). The service invoker device 210 is a device that needs to invoke a service, and may be, for example, a device that runs a component system that needs to invoke a service, such as a device that implements a component system such as MGS (mobile gateway service) and MPS (message push service). The service provider device 220 refers to a device capable of providing the invoked service, for example, may be ECS (Elastic Compute Service, elastic computing service) hosts of publishing services provided to tenants in a cloud computing platform, and under a VPC network architecture, these ECS hosts may be divided into different VPCs, and publish corresponding services for invocation. The IP address of the ECS host under a single VPC is unique but may not be globally unique, e.g. in the scenario shown in fig. 3, the same IP 1-8 exists under each VPC. The channel management device 230 is configured to construct an adaptation channel of a service, so that service call is smoothly performed in the VPC scenario.
Fig. 4 shows a process flow of interaction between devices when service adaptation is performed in the embodiment of the present application, and interaction when the service provider device 210 and the channel management device 230 establish a first long connection includes the following steps:
in step S401, the service provider device 210 initiates a connection establishment request to the channel management device 230, where verification information may be included in the connection establishment request. In a practical scenario, the service caller device 210 and the service provider device 220 may each include an SDK (Software Development Kit, software toolkit) for implementing corresponding functions, so as to implement corresponding processing in service adaptation.
For example, in the process of the service provider device 210 establishing a connection to the channel management device 230, a set of token and a set of channel addresses of the corresponding channel management device may be first obtained by the service provider SDK. the token is verification information, which may be a designated access key configured in advance, and the channel address may be provided to the service provider in advance, so that the service provider may issue a service for other users to call. After obtaining this information, the service provider SDK may initiate a request to establish a long connection to the channel address while providing the corresponding token.
In step S402, the channel management device performs security verification according to the verification information, and establishes a first long connection with the service provider device after passing the verification.
In an actual service adaptation scenario, there may be multiple channel management devices 230, and the service provider may issue a service through any one channel management device, that is, initiate a connection establishment request with any channel management device, and establish a first long connection. For example, in this embodiment, each channel management device may be understood as a channel capable of implementing service adaptation, which is denoted as mpaschannel. For one mpaschannel, after receiving a connection establishment request, verification is performed according to the transmitted token. In the verification manner provided by the embodiment of the application, the token allocated to the service provider SDK can be stored in a preset database, after the token is obtained by the mPaSChannel, the token can be used as a key, whether the token exists or not can be inquired in the database, if so, the success of verification is indicated, and the subsequent processing is carried out. When a token is queried, the token may be deleted in the database so that the token is not reusable to increase the security of the authentication mechanism. Otherwise, if the verification is not found, the verification fails, and the subsequent processing is not performed.
When a connection is established, mpaschannel may obtain service information provided by the service provider SDK, where the service information includes information such as a type of service, machine room information, and the like. The type of the service indicates what component system the service will be called by to implement what function, such as MGS, MPS, etc. The room information of the service indicates the VPC to which the service belongs, for example, in the foregoing two VPCs shown in fig. 3, DC1 and DC2, respectively, and the room information of the corresponding service may be workspace id1 and workspace id2, which indicates in which VPC the service is provided to be specifically deployed. Fig. 5 shows a schematic diagram of a data structure of a local service registry in mpaschannel, where the data structure adopts a tree structure, and nodes such as service types (e.g., MGS, MPS, etc.), machine room information (e.g., workspace 1, workspace 2, etc.) are sequentially arranged step by step.
The mpaschannel will register the service information into the local service registry for later use when the service is invoked. When implementing call, if the service type serviceType and the service room information workspace are specified, the mpaschannel can know a group of first long connections for providing a certain service in the local service registry, and after selecting one of the first long connections, a transport stream between the corresponding service provider equipment can be created for data interaction.
In step S403, the information in the local service registry of the channel management device is related information of the service published by the channel management device, and the related information is provided to the service caller device in a contracted manner. The related information of the service includes a channel address for connecting to the channel management device, and after the channel management device provides the channel address for connecting to the channel management device to the service caller device, the service caller device may initiate a connection establishment request to the channel management device according to the channel address, thereby establishing a second long connection between the channel management device and the service caller device according to the connection establishment request.
In some embodiments of the application, the coordinator device may be utilized to inform the service invoker device of the relevant information of the service. First, the path management device may synchronize the related information of the service issued through the path management device to the coordinator device such that the coordinator device stores the related information of the service. The relevant information includes at least service information of the service and a channel address for connecting the channel management device, so that the service caller device can at least learn from the coordinator device: the channel management device may provide which services and the channel address of the channel management device providing these services. For example, for one mpaschannel, a long connection may be established with a service provider device capable of providing an MGS, and then the mpaschannel may assist in completing the invocation of the MGS, where the corresponding channel management device has a channel address mpaschannel IP of 192.168.1.3.
At this time, if the service calling device subscribes to the service from the coordinator device, when the information is changed due to the synchronization process, the coordinator device notifies the service calling device subscribing to the service of the callable service information, and provides a channel address for connecting to the channel management device. Thereby, the service caller device may initiate a connection establishment request to the channel management device according to the channel address, thereby establishing a second long connection between the channel management device and the service caller device.
In some embodiments of the present application, the coordinator may use a zookeeper, and after any mPaaSChannel registers service information in the local service registry, the content of the local service registry may be synchronized in the zookeeper. Fig. 6 shows a data structure for storing related information in a zookeeper, where the data structure may also adopt a tree structure, and the related information may be installed under mpaschannel nodes, and the lower level is nodes such as service types (e.g. MGS, MPS, etc.) and channel addresses mpaschannel IP (e.g. 192.168.1.2, 192.168.1.3, etc.).
Fig. 7 shows an interactive flow in which the channel management device establishes long connections with the service provider device and the service caller device, respectively, to enable service adaptation in one embodiment of the application. In this embodiment, the service provider device and the service caller device implement corresponding processing functions through the SDK, respectively, and the processing flow when the first long connection is established includes:
In step S701, the service provider SDK obtains a set of token and a set of mpaschannel channel addresses mpaschannel IPs, and then initiates a connection establishment request to these mpaschannel IPs, and sends the corresponding token. For example, the service provider SDK corresponds to DC1 with the machine room information being workspace 1, two corresponding mpaaschannels have channel addresses mPaaSChannel IP of 192.168.1.2 and 192.168.1.3, and the service provider SDK initiates a connection establishment request to the mPaaSChannel IP and carries a corresponding token.
In step S702, after receiving the connection establishment request, the mpaschannel uses the transferred token as a key, and queries the OCS (Open Cache Service ) device, and uses the OCS device as a database for security verification. If the inquiry in the OCS equipment is not completed, the connection establishment is refused. If the token is queried, registering service information of the service to a local service registry, establishing a first long connection with the SDK of the service provider, and deleting information corresponding to the token on the OCS equipment so as to avoid the reuse of the token. Taking mpaschannel with address of 192.168.1.2 as an example, a long connection can be established with the foregoing service provider SDK, and service information of the service, for example, the service type is MGS, and the machine room information is workspace id1, so as to register to a local service registry, where the local service registry may use a data structure as shown in fig. 5.
In step S703, the mPaaSChannel synchronizes information in the local service registry to the Zookeeper, where the synchronized information is also stored in a specific data structure, for example, fig. 6 shows a data structure. In an actual scenario, the first long connection between each mpaschannel and the SDK of a different service provider will change continuously, so that the information in the local service registry of the mpaschannel will also change accordingly, and meanwhile, the mpaschannel will continuously synchronize the changing related information to the zookeeper.
In this embodiment, the process flow when the second long connection is established includes the following process steps:
in step S711, the service caller SDK subscribes to the service from the Zookeeper. The subscription process is as follows: firstly, a service calling party SDK establishes connection with a Zookeeper, and pays attention to a sub node corresponding to a required service type through a watch mechanism, for example, if the service calling party SDK needs to call an MGS, the service calling party SDK can be a watch/mPaSChannel/MGS node, and therefore when information under the MGS node changes, the Zookeeper can inform the service calling party SDK.
In step S712, after synchronizing the relevant information in the local service registry from the mPaaSChannel, the Zookeeper notifies the service caller SDK if it finds that there is an update in the relevant node of the service subscribed by the service caller SDK. For example, when information under the MGS node changes, for example, when a new mpaschannel IP is added, a mpaschannel IP list is sent to the service caller SDK.
In step S713, the service caller SDK may obtain the subscribed information from the Zookeeper, and when a new mPaaSChannel IP is obtained, the service caller SDK may initiate a connection establishment request to the service caller SDK to establish a second long connection between the service caller SDK and the mPaaSChannel. For example, the Zookeeper informs the service caller SDK that there is a new mpaschannel IP of 192.168.1.2 for the MGS, the service caller SDK may initiate a connection establishment request to the mpaschannel of 192.168.1.2 to establish the second long connection between the service caller SDK and the mpaschannel.
In some embodiments of the present application, after the channel management device establishes long connections with the service provider device and the service caller device, respectively, the first long connection and the second long connection can be used to transmit interaction data when the service caller device makes a service call to the service provider device, and a flow of the interaction processing is as follows:
and the service calling party equipment sends a service calling request to the channel management equipment based on the second long connection. Wherein the type of service that the service caller device needs to call is specified by a specific service, for example, the type of service required by the MGS component system is an MGS. The service caller device is creating a data stream based on the second long connection for transmitting the data packet of the service call request.
After receiving the service call request, the channel management device determines service address information according to the service call request. For example, the service call request at least carries information such as a required service type and machine room information, for example, the service request serviceType is MGS, and the machine room information is workspace id1, so that service address information capable of providing the service can be found in the local service registry.
The channel management device determines a service provider device providing a service according to the service address information, and sends data to be processed to the service provider device based on a first long connection with the service provider device. After the service address information capable of providing the service is obtained, one piece of service address information can be selected, the service address information points to one piece of service provider equipment, and if the machine room information in the service information is the workspaceId1, the service provider equipment is the equipment in DC1 corresponding to the workspaceId 1.
A transport stream may then be created based on the first long connection with the service provider device to forward the pending data contained in the call request. At this time, a transport stream created based on the second long connection may be associated with a transport stream created based on the first long connection to form a data transmission channel at the time of service call.
The service provider equipment obtains data to be processed from the service provider equipment based on the first long connection, calls a service to process the data to be processed to obtain a processing result, and then sends the processing result to a channel management equipment based on the first long connection. After obtaining the processing result, the channel management device sends the processing result to the service caller device based on the second long connection. Taking the service with the service type of MGS as an example, after the related service is called for processing, the processing result is written back to the transport stream established based on the second long connection, so that the processing result is transmitted to the mPaSChannel, and then the mPaSChannel can continuously find the associated transport stream established based on the first long connection, directly forward the processing result, so that the service calling party equipment can finally obtain the processing result of service calling, and service calling is completed.
FIG. 8 illustrates an interactive flow of service invocation in one embodiment of the application. In this embodiment, the service provider device and the service caller device implement corresponding processing functions through the SDK, respectively, so that service call is initiated by the component systems such as MGS/MPS, and the calling process includes the following steps:
In step S801, the component system initiates a service call. When a component system such as MGS/MPS initiates a service call, relevant parameters may be specified, for example, in the embodiment of the present application, the component system such as MGS/MPS may specify < workspace, serviceExtType, request, callbackhandler >.
In step S802, the service caller SDK sequences the request into a byte array, and determines a set of mpaschannel IPs that can provide the service according to < workspace id, serviceExtType >. In an actual scenario, one mpaschannel IP may be selected based on a service capability of the mpaschannel corresponding to the mpaschannel IP and combined with a load balancing algorithm, a transport stream is created based on a second long connection established with the mpaschannel IP, and is recorded as a second transport stream, and the data > is packaged as a data packet of a service call request, and the transport stream is associated with a callbackhandler.
In step S803, mpaschannel, after receiving the data packet of the service call request, finds a set of service address information that can provide a service in the local service routing table according to < serviceType, workspace id, serviceExtType >, where each service address information corresponds to a first long connection. The mpaschannel selects one of the first long connections according to a load balancing algorithm, creates a transport stream on it, remembers the first transport stream, and forwards the < data > directly, whereby the service provider SDK can receive the < data >. Meanwhile, the mPaSChannel associates the first transport stream with the second transport stream, if the first long connection is not selected, the service call cannot be completed correctly, corresponding error information is written back on the second transport stream, and the second transport stream is closed.
In step S804, after receiving the data < data > to be processed, the service provider SDK invokes the service to implement data processing, and obtains a processing result < response >.
In step S805, the service provider SDK sequences < response > to < data >, and then directly writes back the corresponding second transport stream. After receiving < data > written back from a service provider SDK, the mPaSChannel finds a first transport stream according to the association relation of the transport streams and forwards the first transport stream to the first transport stream; then the service caller SDK receives the < data >, and the callback handle provides the processing result to the component system.
Based on the same inventive concept, the embodiment of the application also provides a service adapting device, and the corresponding method of the device is the service adapting method implemented on the channel management device, the service provider device and the service caller device in the foregoing embodiment, and the principle of solving the problem is similar to that of the method.
The channel management device comprises a provider processing device and a caller processing device, wherein the provider processing device is used for establishing a first long connection with service provider equipment and storing service address information provided by the service provider equipment, and the service address information is used for determining the service provider equipment when a service is called.
The caller processing device is used for establishing a second long connection with the service caller device, wherein the first long connection and the second long connection are used for transmitting interaction data when the service caller device makes service call to the service provider device.
In some embodiments of the present application, the provider processing means is further configured to determine service address information according to a service call request, determine a service provider device that provides a service according to the service address information, and send data to be processed to the service provider device based on a first long connection with the service provider device; and obtaining a processing result of the service to-be-processed data in the service provider device based on the first long connection;
the caller processing means is further configured to obtain a service invocation request from the service caller device based on the second long connection, and send the processing result to the service caller device based on the second long connection.
The service calling party equipment provided by the embodiment of the application comprises a connection processing device, wherein the connection processing device is used for establishing a second long connection with the channel management equipment, the channel management equipment establishes a first long connection with service provider equipment for providing service, the channel management equipment stores service address information provided by the service provider equipment, the service address information is used for determining the service provider equipment when the service is called, and the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment calls the service provider equipment.
In some embodiments of the present application, the connection processing apparatus is further configured to send a service call request to the channel management device based on the second long connection, so that the channel management device determines service address information according to the service call request, determines a service provider device that provides a service according to the service address information, sends data to be processed to the service provider device based on a first long connection with the service provider device, and obtains a processing result of the data to be processed by the service in the service provider device; and obtaining the processing result from the channel management device based on the second long connection.
The service provider equipment provided by the embodiment of the application comprises a connection processing device. The connection processing device of the service provider equipment is used for establishing a first long connection with the channel management equipment and providing service address information provided by the service provider equipment for the channel management equipment, wherein the service address information is used for determining the service provider equipment when the service is called, the channel management equipment also establishes a second long connection with the service calling equipment, and the first long connection and the second long connection are used for transmitting interaction data when the service calling equipment calls the service provider equipment.
In some embodiments of the present application, the connection processing apparatus of the service provider device is further configured to obtain, from the service provider device, data to be processed based on the first long connection, where the data to be processed is sent by the path management device after obtaining, from the service caller device, a service call request based on the second long connection; calling a service to process the data to be processed to obtain a processing result; and transmitting the processing result to a channel management device based on the first long connection, so that the channel management device transmits the processing result to the service calling device based on the second long connection.
Furthermore, portions of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application by way of operation of the computer. Program instructions for carrying out the methods of the present application may be stored on fixed or removable recording media and/or transmitted over a data stream on a broadcast or other signal bearing medium and/or stored in a working memory of a computer device that operates in accordance with the program instructions. Herein, some embodiments according to the present application comprise a computing device as shown in fig. 9, the device comprising one or more memories 910 storing computer readable instructions and a processor 920 for executing the computer readable instructions, wherein the computer readable instructions, when executed by the processor, cause the device to perform methods and/or aspects in accordance with the various embodiments of the present application described above.
Furthermore, some embodiments of the present application provide a computer readable medium having stored thereon computer program instructions executable by a processor to implement the methods and/or aspects of the various embodiments of the present application described above.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, e.g., using Application Specific Integrated Circuits (ASIC), a general purpose computer or any other similar hardware device. In some embodiments, the software program of the present application may be executed by a processor to implement the above steps or functions. Likewise, the software programs of the present application (including associated data structures) may be stored on a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. In addition, some steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.
Claims (25)
1. A service adaptation method applied to a channel management device, comprising:
establishing a first long connection between the channel management device and a service provider device, and storing service information provided by the service provider device; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information; the channel management device is used for determining a service provider device for providing services for the service caller device based on the service type information and the service room information in the service information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function;
and establishing a second long connection between the channel management device and the service calling party device, wherein the first long connection and the second long connection are used for transmitting interaction data when the service calling party device makes service call to the service provider device.
2. The method according to claim 1, said establishing a first long connection between said channel management device and a service provider device, in particular comprising:
Acquiring a first connection establishment request from the service provider device; the first connection establishment request carries verification information distributed to the service provider equipment for use;
judging whether the verification information is stored in a preset database according to the first connection establishment request;
and if the verification information is stored in the preset database, establishing a first long connection between the channel management equipment and the service provider equipment.
3. The method of claim 2, after the establishing the first long connection between the channel management device and the service provider device, further comprising:
deleting the verification information in the preset database.
4. The method according to claim 1, said establishing a second long connection between said channel management device and said service caller device, in particular comprising:
transmitting a channel address for connecting the channel management device to the service caller device; the service calling party equipment is used for initiating a second connection establishment request to the channel management equipment according to the channel address;
and establishing a second long connection between the channel management equipment and the service calling party equipment according to the second connection establishment request.
5. The method according to claim 4, wherein the sending the channel address for connecting the channel management device to the service caller device specifically comprises:
synchronizing the service information and the channel address to a coordinating device; the coordination device is used for sending the callable service information to the service calling party device of the subscription service and triggering the service calling party device of the subscription service to initiate the second connection establishment request to the channel management device according to the channel address.
6. The method according to claim 5, wherein the coordination device is specifically configured to send the service information that is callable after the change to a service caller device of the subscription service if the service information and the channel address of the specified service in the coordination device change; the specified service is a service subscribed by the service calling party equipment of the subscribed service.
7. The method of claim 1, the service type information being used to reflect function information of a service provided by the service provider device; and the service room information is used for representing the virtual private cloud to which the service belongs.
8. The method of any of claims 1 to 7, further comprising:
Acquiring a service invocation request from the service invoker device based on the second long connection; the service call request carries data to be processed and target service information;
determining a service provider device for providing services to the service caller device according to the target service information;
transmitting the data to be processed to the service provider equipment for providing the service based on the first long connection corresponding to the service provider equipment for providing the service;
acquiring a processing result for the data to be processed based on the first long connection corresponding to the service provider equipment for providing the service; the processing result is generated by the service provider device providing the service;
and sending the processing result to the service calling party equipment based on the second long connection.
9. A service adaptation method applied to a service caller device, comprising:
initiating a second connection establishment request to the channel management device; the channel management device is configured to establish a second long connection between the service caller device and the channel management device according to the second connection establishment request;
the channel management device is further configured to establish a first long connection between the channel management device and a service provider device, store service information provided by the service provider device, and determine a service provider device that provides services to the service caller device based on service type information and service room information in the service information; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function; the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment conducts service calling to the service provider equipment.
10. The method of claim 9, further comprising, prior to initiating the second connection establishment request to the channel management device:
acquiring a channel address for connecting the channel management device;
the initiating a second connection establishment request to the channel management device specifically includes:
and initiating the second connection establishment request to the channel management equipment according to the channel address.
11. The method according to claim 10, wherein the obtaining a channel address for connecting to the channel management device specifically comprises:
subscribing to a service from a coordinator device;
receiving the channel address and the callable service information sent by the coordination equipment; the coordination device is used for sending the callable service information and the channel address to the service calling party device after the channel management device synchronizes the service information and the channel address to the coordination device.
12. The method of any of claims 9 to 11, further comprising:
sending a service call request carrying data to be processed and target service information to the channel management equipment based on the second long connection; the channel management device is used for determining service provider equipment for providing service according to the target service information, sending the data to be processed to the service provider equipment for providing service based on a first long connection corresponding to the service provider equipment for providing service, and acquiring a processing result for the data to be processed, which is fed back by the service provider equipment for providing service;
And acquiring the processing result from the channel management device based on the second long connection.
13. A service adaptation method applied to a service provider device, comprising:
sending a first connection establishment request to the channel management device; the channel management device is configured to establish a first long connection between the channel management device and the service provider device according to the first connection establishment request; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information;
sending service information provided by the service provider equipment to the channel management equipment; the channel management device is further configured to store the service information, and determine a service provider device that provides a service to a service caller device based on service type information and service room information in the service information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function;
The channel management device also establishes a second long connection with the service caller device; the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment conducts service calling to the service provider equipment.
14. The method of claim 13, wherein the first connection establishment request carries authentication information allocated for use by the service provider device;
the establishing a first long connection between the channel management device and the service provider device specifically includes:
judging whether the verification information is stored in a preset database according to the first connection establishment request;
and if the verification information is stored in the preset database, establishing a first long connection between the channel management equipment and the service provider equipment.
15. The method of claim 13, the service type information being used to reflect function information of a service provided by the service provider device; and the service room information is used for representing the virtual private cloud to which the service belongs.
16. The method of any of claims 13-15, further comprising:
acquiring data to be processed from the channel management device based on the first long connection; the channel management device is used for acquiring a service call request from the service calling party device based on the second long connection and sending the data to be processed to the service provider device; the service call request carries the data to be processed;
Calling a service to process the data to be processed to obtain a processing result;
transmitting the processing result to the channel management device based on the first long connection; the channel management device is further configured to send the processing result to the service caller device based on the second long connection.
17. A channel management device comprising:
a provider processing means for establishing a first long connection between the channel management device and a service provider device and storing service information provided by the service provider device; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information; the channel management device is used for determining a service provider device for providing services for the service caller device based on the service type information and the service room information in the service information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function;
and the caller processing device is used for establishing a second long connection between the channel management equipment and the service caller equipment, wherein the first long connection and the second long connection are used for transmitting interaction data when the service caller equipment performs service call to the service provider equipment.
18. The apparatus of claim 17, further comprising:
service call request acquisition means for acquiring a service call request from the service caller device based on the second long connection; the service call request carries data to be processed and target service information;
service provider equipment determining means for determining a service provider equipment for providing a service to the service caller equipment according to the target service information;
a to-be-processed data transmitting device, configured to transmit to the service provider device that provides the service the to-be-processed data based on the first long connection corresponding to the service provider device that provides the service;
processing result obtaining means for obtaining a processing result for the data to be processed based on the first long connection corresponding to the service provider device that provides the service; the processing result is generated by the service provider device providing the service;
and the processing result sending device is used for sending the processing result to the service calling party equipment based on the second long connection.
19. A service caller device comprising:
connection processing means for initiating a second connection establishment request to the channel management device; the second connection establishment request is used for requesting to establish a second long connection between the service calling party device and the channel management device;
The channel management device is further configured to establish a first long connection between the channel management device and a service provider device, store service information provided by the service provider device, and determine a service provider device that provides services to the service caller device based on service type information and service room information in the service information; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function; the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment conducts service calling to the service provider equipment.
20. The apparatus of claim 19, further comprising:
service call request sending means for sending a service call request carrying data to be processed and target service information to the channel management device based on the second long connection; the channel management device is used for determining service provider equipment for providing service according to the target service information, sending the data to be processed to the service provider equipment for providing service based on a first long connection corresponding to the service provider equipment for providing service, and acquiring a processing result for the data to be processed, which is fed back by the service provider equipment for providing service;
Processing result acquisition means for acquiring the processing result from the channel management device based on the second long connection.
21. A service provider device, comprising:
connection processing means for transmitting a first connection establishment request to the channel management device; the first connection establishment request is for causing a channel management device to establish a first long connection between the channel management device and a service provider device; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information;
and for sending service information provided by the service provider device to the channel management device; the channel management device is further configured to store the service information, and determine a service provider device that provides a service to a service caller device based on service type information and service room information in the service information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function;
The channel management device also establishes a second long connection with the service caller device; the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment conducts service calling to the service provider equipment.
22. A service adaptation system, comprising:
a service provider device for transmitting a first connection establishment request to a channel management device, and for transmitting service information of a service provided by the service provider device to the channel management device;
a channel management device for establishing a first long connection between the channel management device and a service provider device according to the first connection establishment request, storing the service information, and determining a service provider device providing a service to a service caller device based on service type information and service room information in the service information; the establishing a first long connection between the channel management device and a service provider device comprises: the service provider equipment initiates a connection establishment request to the channel management equipment, wherein the connection establishment request comprises verification information; the service room information represents the VPC to which the service belongs, and the service type information represents what component system the service is called to realize what function;
Service calling equipment, which is used for initiating a second connection establishment request to the channel management equipment;
the channel management device is further configured to establish a second long connection between the channel management device and the service caller device according to the second connection establishment request; the first long connection and the second long connection are used for transmitting interaction data when the service calling party equipment conducts service calling to the service provider equipment.
23. The system of claim 22, the service invoker device further configured to send a service invocation request to the channel management device based on the second long connection; the service call request carries data to be processed and target service information;
the channel management device is further configured to determine, according to the target service information, a service provider device that provides a service to the service caller device, and send the data to be processed to the service provider device that provides the service based on a first long connection corresponding to the service provider device that provides the service;
the service provider device is further configured to invoke a service to process the data to be processed after receiving the data to be processed, obtain a processing result, and send the processing result to the channel management device based on a first long connection corresponding to the service provider device that provides the service;
The channel management device is further configured to send the processing result to the service caller device based on the second long connection after the processing result is obtained.
24. A computing device, wherein the device comprises a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any one of claims 1 to 16.
25. A computer readable medium having stored thereon computer program instructions executable by a processor to implement the method of any of claims 1 to 16.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210824161.7A CN115277816B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910304734.1A CN110149365B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
| CN202210824161.7A CN115277816B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910304734.1A Division CN110149365B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115277816A CN115277816A (en) | 2022-11-01 |
| CN115277816B true CN115277816B (en) | 2023-10-20 |
Family
ID=67588327
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910304734.1A Active CN110149365B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
| CN202210824161.7A Active CN115277816B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910304734.1A Active CN110149365B (en) | 2019-04-16 | 2019-04-16 | Service adaptation method, device, system and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN110149365B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111711620B (en) * | 2020-06-05 | 2022-08-09 | 南京领行科技股份有限公司 | Method, device, equipment and storage medium for realizing bidirectional communication between applications |
| CN113032302A (en) * | 2021-04-07 | 2021-06-25 | 杭州共有科技有限公司 | Method for improving arbitration performance of chained data |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106020998A (en) * | 2016-05-24 | 2016-10-12 | 深圳市智物联网络有限公司 | Service invoke method and device |
| CN107077367A (en) * | 2014-09-19 | 2017-08-18 | 亚马逊科技公司 | Privately owned alias end points for isolating virtual network |
| CN107203877A (en) * | 2016-03-16 | 2017-09-26 | 阿里巴巴集团控股有限公司 | The method and apparatus for closely realizing business between account |
| CN107453922A (en) * | 2017-09-08 | 2017-12-08 | 北京寄云鼎城科技有限公司 | Infrastructure service collocation method, client and server |
| CN108366132A (en) * | 2018-03-13 | 2018-08-03 | 平安普惠企业管理有限公司 | Service management, device, computer equipment between server and storage medium |
| CN108600326A (en) * | 2018-03-29 | 2018-09-28 | 阿里巴巴集团控股有限公司 | Communication means, device and equipment |
| CN109451084A (en) * | 2018-09-14 | 2019-03-08 | 华为技术有限公司 | A kind of service access method and device |
| CN109561171A (en) * | 2019-01-22 | 2019-04-02 | 北京百度网讯科技有限公司 | The configuration method and device of virtual private cloud service |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2525578A1 (en) * | 2003-05-15 | 2004-12-02 | Applianz Technologies, Inc. | Systems and methods of creating and accessing software simulated computers |
| US8914497B1 (en) * | 2011-12-15 | 2014-12-16 | Amazon Technologies, Inc. | System and method for throttling service requests having non-uniform workloads |
| US20160205106A1 (en) * | 2015-01-12 | 2016-07-14 | Verisign, Inc. | Systems and methods for providing iot services |
| US10749985B2 (en) * | 2015-05-19 | 2020-08-18 | Amazon Technologies, Inc. | Custom communication channels for application deployment |
| US10154102B2 (en) * | 2016-04-20 | 2018-12-11 | Tize Technologies Inc. | System and method for cloud computing on-demand dynamic service management engine |
| CN108243079B (en) * | 2016-12-23 | 2021-04-27 | 阿里巴巴集团控股有限公司 | Method and equipment for network access based on VPC |
| CN106533890B (en) * | 2016-12-30 | 2019-12-24 | 华为技术有限公司 | Message processing method, device and system |
| CN109548006B (en) * | 2017-08-08 | 2021-04-13 | 中国移动通信有限公司研究院 | Method and device for establishing data channel and computer readable storage medium |
| CN111052686B (en) * | 2017-08-27 | 2022-03-29 | Nicira股份有限公司 | Method and machine readable medium for performing online services in a public cloud |
| CN108200018B (en) * | 2017-12-20 | 2019-11-05 | 北京百度网讯科技有限公司 | Flow forwarding method and equipment, computer equipment and readable medium in cloud computing |
| CN109327503A (en) * | 2018-08-27 | 2019-02-12 | 珠海格力电器股份有限公司 | Information management system and method, service router |
| CN109150893B (en) * | 2018-09-12 | 2021-10-26 | 山东中创软件工程股份有限公司 | Service request forwarding method and related device |
-
2019
- 2019-04-16 CN CN201910304734.1A patent/CN110149365B/en active Active
- 2019-04-16 CN CN202210824161.7A patent/CN115277816B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107077367A (en) * | 2014-09-19 | 2017-08-18 | 亚马逊科技公司 | Privately owned alias end points for isolating virtual network |
| CN107203877A (en) * | 2016-03-16 | 2017-09-26 | 阿里巴巴集团控股有限公司 | The method and apparatus for closely realizing business between account |
| CN106020998A (en) * | 2016-05-24 | 2016-10-12 | 深圳市智物联网络有限公司 | Service invoke method and device |
| CN107453922A (en) * | 2017-09-08 | 2017-12-08 | 北京寄云鼎城科技有限公司 | Infrastructure service collocation method, client and server |
| CN108366132A (en) * | 2018-03-13 | 2018-08-03 | 平安普惠企业管理有限公司 | Service management, device, computer equipment between server and storage medium |
| CN108600326A (en) * | 2018-03-29 | 2018-09-28 | 阿里巴巴集团控股有限公司 | Communication means, device and equipment |
| CN109451084A (en) * | 2018-09-14 | 2019-03-08 | 华为技术有限公司 | A kind of service access method and device |
| CN109561171A (en) * | 2019-01-22 | 2019-04-02 | 北京百度网讯科技有限公司 | The configuration method and device of virtual private cloud service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110149365B (en) | 2022-06-24 |
| CN110149365A (en) | 2019-08-20 |
| CN115277816A (en) | 2022-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11095711B2 (en) | DNS Resolution of internal tenant-specific domain addresses in a multi-tenant computing environment | |
| CN109561171B (en) | Configuration method and device of virtual private cloud service | |
| US9378042B2 (en) | Virtual machine multicast/broadcast in virtual network | |
| US20240031309A1 (en) | Data Processing Method, Apparatus, Device and Storage Medium | |
| CN110703980B (en) | File transmission method and device | |
| CN109660578B (en) | CDN back-to-source processing method, device and system | |
| KR100727993B1 (en) | Method and apparatus for data push service using data pull model | |
| JP2016530634A (en) | Method and system for dispatching requests in a content delivery network | |
| CN109521956B (en) | Cloud storage method, device, equipment and storage medium based on block chain | |
| CN108282507B (en) | Method and device for application release in CaaS environment and electronic equipment | |
| US8341285B2 (en) | Method and system for transferring files | |
| US8903972B2 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
| CN106657180B (en) | Information transmission method and device for cloud service, terminal equipment and system | |
| CN111124589B (en) | Service discovery system, method, device and equipment | |
| CN107135242B (en) | Mongodb cluster access method, device and system | |
| CN115277816B (en) | Service adaptation method, device, system and computer readable medium | |
| TW201724001A (en) | System and method for acquiring, processing and updating global information | |
| CN114040020A (en) | Cross-cluster service calling method and system | |
| US11093477B1 (en) | Multiple source database system consolidation | |
| CN113179295B (en) | Message processing method and device | |
| US10594511B2 (en) | Address system | |
| CN115242882A (en) | Method and device for accessing k8s container environment based on transport layer route | |
| CN115225606A (en) | Domain name access method and system of cross-network protocol of container cloud platform | |
| CN106209407B (en) | Method and equipment for session backup | |
| US11546405B2 (en) | Methods for exposing mainframe data as a web service and devices thereof |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240301 Address after: Guohao Times City # 20-01, 128 Meizhi Road, Singapore Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd. Guo jiahuodiqu after: Xin Jiapo Address before: 27 Hospital Road, George Town, Grand Cayman ky1-9008 Patentee before: Innovative advanced technology Co.,Ltd. Guo jiahuodiqu before: Ikujin group |
|
| TR01 | Transfer of patent right |