CN110022260B - Cross-environment receipt message processing method and system - Google Patents
Cross-environment receipt message processing method and system Download PDFInfo
- Publication number
- CN110022260B CN110022260B CN201910106680.8A CN201910106680A CN110022260B CN 110022260 B CN110022260 B CN 110022260B CN 201910106680 A CN201910106680 A CN 201910106680A CN 110022260 B CN110022260 B CN 110022260B
- Authority
- CN
- China
- Prior art keywords
- environment
- client
- receipt message
- cross
- identifier
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A cross-environment receipt message processing method and system are disclosed. A method of cross-environment receipt message processing, the method comprising: when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located; if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server; the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier; and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a cross-environment receipt message processing method and system.
Background
At present, for the operating environment of a client (here, a client of an application program), a separation is performed by using an environment isolation scheme, which may be divided into a test environment, a pre-release environment, a grayscale environment, and an online environment, for example, the purpose of using the environment isolation scheme is to keep the mutual isolation among the operating environments, and ensure that the client operates normally in different operating environments, for example, for the client a, the environment isolation scheme may operate normally in the test environment, the pre-release environment, the grayscale environment, and the online environment, respectively.
However, for some service scenarios, complete environment isolation cannot be achieved, for example, for a service scenario in which a part of clients invoke a next-level client, it is easy to cause a response piece message of a client in a certain operating environment to be acquired by a client in another operating environment, so that different operating environments are spanned when the response piece message is received. For example, for a client a running in a grayscale environment, a next-level client B is called, a receipt message returned by the client B is acquired by the client a running in an online environment, and is forwarded to the client a running in the grayscale environment by the client a running in the online environment, so that different running environments are spanned when the receipt message is returned, environment isolation cannot be strictly achieved, and application scenes based on environment isolation, such as grayscale verification, and the like, are affected.
Disclosure of Invention
To solve the foregoing technical problems, an embodiment of the present specification provides a method and a system for processing a cross-environment receipt message, where the technical solution is as follows:
a cross-environment receipt message processing method is applied to a cross-environment receipt message processing system, the system comprises a plurality of clients and a server under different operating environments, the plurality of clients under different operating environments share the server, and any client under different operating environments is a cross-environment initiator client or a cross-environment receiver client, and the method comprises the following steps:
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
A cross-environment receipt message processing method is applied to a cross-environment initiator client, and comprises the following steps:
when receiving a receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment of a cross-environment initiator client;
if not, the received receipt message, the target environment identifier and the client identifier are forwarded to the server, so that the server receives the forwarded receipt message, the target environment identifier and the client identifier, and the received receipt message is called back to the client of the cross-environment receiver in the target operation environment according to the target environment identifier and the client identifier.
A cross-environment receipt message processing method is applied to a server side and comprises the following steps:
receiving a receipt message, a target environment identifier and a client identifier which are forwarded by a client of an environment initiator;
and calling back the received receipt message to a cross-environment receiver client under the target operation environment according to the target environment identifier and the client identifier.
A cross-environment receipt message processing system, the system comprising: the system comprises a plurality of clients and a server under different operating environments, wherein the clients under the different operating environments share the server, and any client under the different operating environments is a cross-environment initiator client or a cross-environment receiver client;
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
A cross-environment receipt message processing device applied to a cross-environment initiator client side comprises the following components:
the identification analysis module is used for analyzing the target environment identification carried in the receipt message when the receipt message is received;
the judging module is used for judging whether the environment identification is consistent with the environment identification of the running environment of the cross-environment initiator client;
and if not, forwarding the received receipt message, the target environment identifier and the client identifier to the server, so that the server receives the forwarded receipt message, the target environment identifier and the client identifier, and calling back the received receipt message to the cross-environment receiver client in the target operation environment according to the target environment identifier and the client identifier.
A cross-environment receipt message processing device applied to a server side comprises:
the receiving module is used for receiving the receipt message, the target environment identifier and the client identifier which are forwarded by the client of the cross-environment initiator;
and the message callback module is used for calling back the received receipt message to the client of the cross-environment receiver in the target operation environment according to the target environment identifier and the client identifier.
According to the technical scheme provided by the embodiment of the specification, for the cross-environment initiator client, when the receipt message is received, the target environment identifier carried in the receipt message is analyzed, whether the target environment identifier is consistent with the environment identifier of the operating environment where the target environment identifier is located is judged, whether the received receipt message, the target environment identifier and the client identifier are forwarded to the server is determined, and for the server, the receipt message forwarded by the client, the target environment identifier and the client identifier are received, and the received receipt message is called back to the cross-environment receiver client under the target operating environment according to the target environment identifier and the client identifier. Therefore, the receipt message delivered in a cross-environment error mode can be automatically called back to the client side under the corresponding environment, different operation environments cannot be crossed when the receipt message is returned, and the influence on application scenes based on environment isolation such as gray level verification is avoided.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.
In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
Fig. 1 is a schematic diagram of connection between a client and a server according to an embodiment of the present disclosure;
FIG. 2 is an interaction flow diagram of a cross-environment receipt message processing method in an embodiment of the present description;
FIG. 3 is a schematic structural diagram of a cross-environment receipt message processing apparatus applied to a cross-environment initiator client according to an embodiment of the present specification;
FIG. 4 is a block diagram of a cross-environment receipt message processing apparatus applied to a server according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an apparatus for configuring a device according to an embodiment of the present disclosure.
Detailed Description
At present, the operating environments of a client (referred to as an application client in this specification) are distinguished by using an environment isolation scheme (physical isolation), which may be divided into a test environment, a pre-release environment, a grayscale environment, an online environment, and the like. For example, for a client a of an application, the environment isolation scheme may be used to operate normally in a test environment, a pre-release environment, a grayscale environment, and an online environment.
However, for some service scenarios, complete environmental isolation cannot be achieved at present, for example, for a client a operating in a grayscale environment, a next-stage client B is called, a receipt message returned by the client B is acquired by the client a operating in an online environment, and because the receipt message acquired by the client a operating in the online environment does not belong to the client a, the client a operating in the online environment forwards the receipt message to the client a operating in the grayscale environment, so that different operating environments are spanned when the receipt message is received, environmental isolation cannot be achieved strictly, and an application scenario based on environmental isolation, such as grayscale verification, is affected.
In view of the above technical problems, embodiments of the present disclosure provide a technical solution, where for a cross-environment initiator client, when receiving a receipt message, a target environment identifier carried in the receipt message is analyzed, and whether the received receipt message, the target environment identifier, and a client identifier of the cross-environment initiator client are forwarded to a server by determining whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located, and for the server, the receipt message, the target environment identifier, and the client identifier forwarded by the client are received, and the received receipt message is callback to a cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier. Therefore, the receipt message delivered in a cross-environment error mode can be automatically called back to the client side under the corresponding environment, different operation environments cannot be crossed when the receipt message is returned, and the influence on application scenes based on environment isolation such as gray level verification is avoided.
Specifically, the technical solutions provided in the embodiments of the present specification are as follows:
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located; if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server; the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier; and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
In this specification, a client refers to a client of an application, and a plurality of clients under different operating environments share one server, where a connection diagram of a plurality of clients under different operating environments and one server is shown in fig. 1, and the server is respectively connected with a client a under a pre-release environment, a client a under a grayscale environment, and a client a under an online environment. The server may be in the form of a specific server or a server cluster, and the client and the server may implement communication connection through various forms of networks, which is not limited in this specification.
For the convenience of subsequent distinction, any client in different operating environments can be a cross-environment initiator client or a cross-environment receiver client.
In addition, in this specification, a response receipt message refers to a response to a certain request, for example, the client a calls the client B to make a request, and the response receipt message returned by the client B is a response to the request.
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
Referring to fig. 2, an interaction flow diagram of a cross-environment receipt message processing method provided in the embodiment of the present specification is shown, where the method specifically includes the following steps:
s201, when a cross-environment initiator client receives a receipt message, analyzing a target environment identifier carried in the receipt message;
s202, judging whether the environment identification is consistent with the environment identification of the running environment of the cross-environment initiator client;
for any request sent by any cross-environment initiator client connected with the server, a downstream is called, and finally, the receipt message can be returned across different operating environments, for example, the request sent by the cross-environment initiator client A in a gray level environment calls the downstream client B, and finally, the receipt message returned by the client B can be returned across different operating environments when the receipt message is returned. Therefore, when receiving a response piece message across the environment initiator client, it is necessary to determine whether the received response piece message belongs to the current operating environment, and specifically, determining whether the received response piece message belongs to the current operating environment may be implemented by:
analyzing a target environment identifier carried in the received receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment of the cross-environment initiator client; if the target environment identifier is consistent with the environment identifier of the operating environment of the cross-environment initiator client, the received receipt message belongs to the current operating environment, and the service process can be continuously processed; if the target environment identifier is inconsistent with the environment identifier of the operating environment of the cross-environment initiator client, the received receipt message does not belong to the current operating environment, and additional processing is required.
In this specification, for any cross-environment initiator client under different operating environments, an environment identifier of the operating environment where the client is located needs to be determined, and the operating environment where the client is located can be further determined by the environment identifier. There are many implementations of determining the environment identifier of the operating environment where the user is located, and one implementation is as follows:
corresponding environment identifiers are preset for different operating environments, and the environment identifiers may be IDs (e.g. 1, 2, 3, 4, A, B, C, D), environment names (e.g. pre-release, gray scale, on-line), and the like, although the environment identifiers may also be in other forms, which is not limited in this specification. Meaning that the same environment identifier is shared for all cross-environment initiator clients in the same operating environment, for example, the same environment identifier is shared (pre-release) for cross-environment initiator client a, cross-environment initiator client B, cross-environment initiator client C in the pre-release environment. For the cross-environment initiator client, a user can inform the cross-environment initiator client of the environment identifier corresponding to the operating environment where the cross-environment initiator client is located in advance in a mode of inputting an instruction, so that the cross-environment initiator client can determine the environment identifier corresponding to the operating environment where the cross-environment initiator client is located, and then can determine the operating environment where the cross-environment initiator client is located.
Through the above, the environment identifier of the operating environment of the cross-environment initiator client can be determined, the target environment identifier carried in the receipt message is analyzed, the two identifiers are compared, and then whether the received receipt message belongs to the current operating environment or not is judged. For example, for the cross-environment initiator client a, the operating environment in which the client is located is a pre-release environment, the determined environment identifier of the operating environment in which the client is located is a pre-release, if the target environment identifier carried by the client is analyzed from the receipt message and is a pre-release, the two are consistent, the received receipt message belongs to the current operating environment, and if the target environment identifier carried by the client is analyzed from the receipt message and is a gray level, the two are not consistent, the received receipt message does not belong to the current operating environment, the client forwarding component is awakened, and the received receipt message, the analyzed target environment identifier (gray level), and the client identifier (a) are forwarded to the server through the client forwarding component.
S203, if not, the client forwards the received receipt message, the target environment identifier and the client identifier to the server;
for the determination result in S202, if the target environment identifier carried in the receipt message is consistent with the environment identifier of the operating environment in which the cross-environment initiator client is located, the service flow continues to be processed, which is not described in detail herein in this specification; if the target environment identifier carried in the receipt message is not consistent with the environment identifier of the operating environment of the cross-environment initiator client, the client needs to forward the received receipt message, the target environment identifier, and the client identifier (the client identifier, such as a client ID, a client name, or other forms, which are not limited in this specification) to the server, and specifically, the receipt message, the target environment identifier, and the client identifier may be forwarded by the client forwarding component, so that the server receives the receipt message, the target environment identifier, and the client identifier, and then the server may call back the receipt message to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier.
S204, the server receives the receipt message, the target environment identifier and the client identifier which are forwarded by the cross-environment initiator client;
s205, the server side calls back the received receipt message to the client side of the cross-environment receiver in the target operation environment according to the target environment identification and the client side identification.
And the server receives the receipt message, the target environment identifier and the client identifier forwarded by the cross-environment initiator client, and calls back the receipt message to the cross-environment receiver client in the target operation environment according to the target environment identifier and the client identifier. For example, for the received receipt message forwarded by the client, the target environment identifier (gray scale) and the client identifier (a), the server may call back the receipt message to the cross-environment receiving client a in the gray scale environment according to the target environment identifier (gray scale) and the client identifier (a).
As a preferred embodiment, the server may summarize the received receipt message, the target environment identifier, and the client identifier forwarded across the environment initiator client, and subsequently may call back the received receipt message forwarded across the environment initiator client to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier, which is specifically as follows:
after receiving the receipt message, the target environment identifier, and the client identifier forwarded by the cross-environment initiator client, the server stores the received receipt message, the target environment identifier, and the client identifier locally, and may store the received receipt message, the target environment identifier, and the client identifier in a persistent device, such as a database, so that the receipt message may be subsequently recalled to the cross-environment receiver client in the target operating environment, which means that the cross-environment receiver client in the target operating environment is consistent with the cross-environment initiator client in the current operating environment.
When the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back, and the subsequent server side can call back the acquired receipt message to the cross-environment receiver client side under the target operation environment according to the target environment identifier and the client side identifier.
In addition, as a preferred embodiment, after receiving the response piece message, the target environment identifier and the client identifier forwarded across the environment initiator client, the server records the receiving time of the response piece message, for example, the receiving time of the response piece message is 10:00, which means that at any time after the receiving time (10:00), the response piece message can be called back to the cross-environment receiver client in the target operating environment. In addition, it is also required to determine that the scheduling status of the receipt message is schedulable, for example, the scheduling status of the receipt message is READY, so that the receipt message is called back to the cross-environment receiver client in the target operating environment.
As a preferred embodiment, when the receipt message callback condition is triggered, the server side obtains the receipt message that is not currently callback, or when the receipt message callback condition is triggered, the server side obtains the receipt message that is not currently callback and whose scheduling state is schedulable. For example, when the receipt message callback condition is triggered, the server side obtains the receipt message which is not currently called back and has a dispatch status READY, and subsequently, the obtained receipt message can be called back to the client side of the cross-environment receiver in the target operation environment according to the target environment identifier and the client side identifier. The receipt message which is not called back currently and the scheduling state of which is schedulable refers to the receipt message which can be called back currently by the server.
Before the server side calls back the receipt message to the cross-environment receiver client side in the target operation environment according to the target environment identifier and the client side identifier, as a preferred embodiment, the server side updates the scheduling state corresponding to the obtained receipt message from schedulable to scheduling, and after the server side updates the scheduling state corresponding to the obtained receipt message from schedulable to scheduling, the server side calls back the obtained receipt message to the cross-environment receiver client side in the target operation environment according to the target environment identifier and the client side identifier. For example, the scheduling state of the obtained receipt message is updated from READY to RUNNING, and after the scheduling state of the obtained receipt message is updated from READY to RUNNING, the server side calls back the obtained receipt message to the cross-environment receiver side client side according to the target environment identifier and the client side identifier.
In this specification, the above-mentioned callback condition of the receipt message may be the following callback condition:
one callback condition is: the server sets a timer, sets a callback period in advance, and can acquire the current callback-free and schedulable receipt message in the scheduling state according to the preset callback period. For example, every 30 minutes, the server obtains a receipt message which is not called back currently and whose scheduling status is schedulable.
Another callback condition is: the method comprises the steps that a timing server corresponding to each operation environment exists, a sending period of a receipt message callback request is preset, the receipt message callback request is sent to a server according to the preset sending period, the server represents callback condition triggering after receiving the receipt message callback request, and the receipt messages which are not called back currently and are schedulable in scheduling state can be obtained, wherein the sending period preset by the timing server corresponding to each operation environment can be consistent or inconsistent. For example, for a timing server corresponding to a gray scale environment, a receipt message callback request is sent to a server every 20 minutes, after the server receives the receipt message callback request, the server obtains a receipt message which is not currently callback and whose scheduling state is schedulable, for a timing server corresponding to a pre-release environment, a receipt message callback request is sent to the server every 15 minutes, and after the server receives the receipt message callback request, the server obtains a receipt message which is not currently callback and whose scheduling state is schedulable.
Based on the above steps, as a preferred embodiment, the server determines whether the obtained receipt message is successfully recalled within a preset time period (for example, 15S, where the preset time period is an effective time of the obtained receipt message in the callback process); if the obtained receipt message is successfully recalled, the server updates the scheduling status corresponding to the obtained receipt message to scheduling end, for example, to FINISHED scheduling (where the scheduling end may be updated from schedulable, or the scheduling end may be updated from scheduling, which is not limited in this specification); if the callback of the obtained receipt message fails, the server side renews the scheduling state corresponding to the obtained receipt message to be schedulable (wherein the renewal in the scheduling can be schedulable, or the renewability in the scheduling can be schedulable, which means a renewed refresh, which is not limited in the specification), and additionally adds a time period based on the receipt time of the receipt message to facilitate the next callback, wherein the additionally added time period can be increased along with the increase of the number of the scheduling times, so that the influence of the accumulation of abnormal callbacks on the callbacks of other normal receipt messages is prevented, and the number of the scheduling times of the receipt message also needs to be recorded.
As a preferred embodiment, the server calls back the obtained receipt message to the cross-environment receiver client under the target operating environment according to the target environment identifier and the client identifier, receives the receipt message called back by the server on the side of the cross-environment receiver client, simulates receipt message receipt by using local message middleware to receive the receipt message called back by the server through the message middleware again, and sends a message that the receipt message is successfully received to the server after the cross-environment receiver client receives the receipt message called back by the server through the message middleware again. On the side of the server, in a preset time period, whether the obtained receipt message is successfully recalled or not can be judged by judging whether the receipt message which is sent by the client of the cross-environment receiver is successfully received or not: if a message that the receipt message sent by the cross-environment receiver client is successfully received is received, the obtained receipt message is judged to be successfully recalled, and if the message that the receipt message sent by the cross-environment receiver client is successfully received is not received, the obtained receipt message is judged to be unsuccessfully recalled.
The method includes that a callback of an acquired receipt message fails within a preset time period due to abnormal interruption of a server, a schedulable state of the schedulable state is in scheduling, the schedulable state is required to be periodically processed as the receipt message in scheduling, a specific processing mode of the method is similar to a mode of processing the acquired receipt message under the condition that the callback of the acquired receipt message fails, and details are not repeated here.
Through the above description of the technical solution provided in this specification, for the cross-environment initiator client, when receiving the receipt message, the target environment identifier carried in the receipt message is analyzed, and it is determined whether to forward the received receipt message, the target environment identifier, and the client identifier to the server by determining whether the target environment identifier is consistent with the environment identifier of the operating environment where the target environment identifier is located, and for the server, the receipt message forwarded by the client, the target environment identifier, and the client identifier are received, and the received receipt message is callback to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier. Therefore, the receipt message delivered in a cross-environment error mode can be automatically called back to the client side under the corresponding environment, different operation environments cannot be crossed when the receipt message is returned, and the influence on application scenes based on environment isolation such as gray level verification is avoided.
In order to more clearly explain the technical solutions provided by the embodiments of the present disclosure, the following describes the executed methods from a single-side perspective:
for the cross-environment initiator client, the tasks to be performed are mainly as follows:
a, when receiving a receipt message, analyzing a target environment identifier carried in the receipt message;
b, judging whether the environment identification is consistent with the environment identification of the operation environment of the cross-environment initiator client;
if not, forwarding the received receipt message, the target environment identifier and the client identifier to a server;
for the server, the tasks to be executed are mainly as follows:
a, receiving a receipt message forwarded across an environment initiator client, the target environment identifier and the client identifier;
and b, calling back the received receipt message to a cross-environment receiver client under the target operation environment according to the target environment identifier and the client identifier.
Compared with the above method embodiment, an embodiment of the present disclosure further provides a cross-environment receipt message processing apparatus, applied to a cross-environment initiator client, and as shown in fig. 3, the apparatus may include: an identifier parsing module 310, a determining module 320, and a forwarding module 330.
The identifier analyzing module 310 is configured to, when receiving a receipt message, analyze a target environment identifier carried in the receipt message;
the judging module 320 is configured to judge whether the environment identifier is consistent with the environment identifier of the operating environment where the cross-environment initiator client is located;
and the forwarding module 330 is configured to forward the received receipt message, the target environment identifier, and the client identifier to the server if the receipt message, the target environment identifier, and the client identifier are not received, so that the server receives the forwarded receipt message, the target environment identifier, and the client identifier, and call back the received receipt message to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier.
An embodiment of the present specification further provides a cross-environment receipt message processing apparatus, which is applied to a server, and as shown in fig. 4, the apparatus may include: a receiving module 410, and a message callback module 420.
A receiving module 410, configured to receive a response piece message forwarded across an environment initiator client, a target environment identifier, and a client identifier;
and the message callback module 420 is configured to callback the received receipt message to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier.
An embodiment of the present specification further provides a cross-environment receipt message processing system, including: the system comprises a plurality of clients and a server under different operating environments, wherein the clients under the different operating environments share the server, and any client under the different operating environments is a cross-environment initiator client or a cross-environment receiver client;
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Through the above description of the technical solution provided in this specification, for the cross-environment initiator client, when receiving the receipt message, the target environment identifier carried in the receipt message is analyzed, and it is determined whether to forward the received receipt message, the target environment identifier, and the client identifier to the server by determining whether the target environment identifier is consistent with the environment identifier of the operating environment where the target environment identifier is located, and for the server, the receipt message forwarded by the client, the target environment identifier, and the client identifier are received, and the received receipt message is callback to the cross-environment receiver client in the target operating environment according to the target environment identifier and the client identifier. Therefore, the receipt message delivered in a cross-environment error mode can be automatically called back to the client side under the corresponding environment, different operation environments cannot be crossed when the receipt message is returned, and the influence on application scenes based on environment isolation such as gray level verification is avoided.
Embodiments of the present specification further provide a computer device, as shown in fig. 5, the computer device may include: a processor 510, a memory 520, an input/output interface 530, a communication interface 540, and a bus 550. Wherein processor 510, memory 520, input/output interface 530, and communication interface 540 are communicatively coupled to each other within the device via bus 550.
The processor 510 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.
The Memory 520 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 520 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 520 and called by the processor 510 for execution.
The input/output interface 530 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 540 is used for connecting a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 510, the memory 520, the input/output interface 530, the communication interface 540 and the bus 550, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification also provide a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the aforementioned cross-environment receipt message processing method. The method at least comprises the following steps:
a cross-environment receipt message processing method is applied to a cross-environment receipt message processing system, the system comprises a plurality of clients and a server under different operating environments, the plurality of clients under different operating environments share the server, and any client under different operating environments is a cross-environment initiator client or a cross-environment receiver client, and the method comprises the following steps:
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
Computer-readable media, which include both non-transitory and non-transitory, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media 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 magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a specific embodiment of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, a plurality of modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as the protection scope of the embodiments of the present disclosure.
Claims (20)
1. A cross-environment receipt message processing method is applied to a cross-environment receipt message processing system, the system comprises a plurality of clients and a server under different operating environments, the plurality of clients under different operating environments share the server, any client under different operating environments is a cross-environment initiator client or a cross-environment receiver client, and the same client has the same client identification under different operating environments, the method comprises the following steps:
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
2. The method of claim 1, further comprising:
after receiving the receipt message, the target environment identifier and the client identifier forwarded by the client of the cross-environment initiator, the server stores the received receipt message, the target environment identifier and the client identifier to the local;
when the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back;
the server side callbacks the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification, and the method comprises the following steps:
and the server side calls back the acquired receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
3. The method of claim 2, further comprising:
after receiving the receipt message forwarded by the client of the cross-environment initiator, the target environment identifier and the client identifier, the server determines that the scheduling state of the received receipt message is schedulable;
when the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back, and the method comprises the following steps:
when the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back and the scheduling state of which is schedulable.
4. The method of claim 3, wherein the server, according to the target environment identifier and the client identifier, recalls the obtained response piece message to a cross-environment receiver client in the target operating environment, and the method comprises:
the server side updates the scheduling state corresponding to the acquired receipt message from schedulable to scheduling;
and after updating the scheduling state corresponding to the obtained receipt message into scheduling from schedulable by the server, calling back the obtained receipt message to the cross-environment receiver client under the target operation environment according to the target environment identifier and the client identifier.
5. The method of any of claims 3 to 4, further comprising:
the server side judges whether the callback of the acquired receipt message is successful or not within a preset time period;
and if the callback is successful, the server side updates the scheduling state corresponding to the acquired receipt message to be scheduling end.
6. The method of claim 5, further comprising:
and if the callback fails, the server side renews the scheduling state corresponding to the acquired receipt message into schedulable state.
7. The method of claim 5, further comprising:
receiving the receipt message called back by the server by the cross-environment receiver client, and simulating the receipt message receipt by using the local message middleware so as to receive the receipt message called back by the server again through the message middleware;
after receiving the receipt message called back by the server through the message middleware again, the cross-environment receiver client sends a message that the receipt message is successfully received to the server;
the step of judging whether the callback of the acquired receipt message is successful or not by the server side in a preset time period comprises the following steps:
the server side judges whether a message of successful receipt message receiving sent by a cross-environment receiver client side is received or not within a preset time period;
if a message of successfully receiving the receipt message sent by the client of the cross-environment receiving party is received, judging that the callback of the obtained receipt message is successful;
and if the message of successful receipt of the receipt message sent by the cross-environment receiver client is not received, judging that the callback of the acquired receipt message fails.
8. A cross-environment receipt message processing method is applied to a cross-environment initiator client in a cross-environment receipt message processing system, and the system comprises: the method comprises the following steps that a plurality of clients and a server under different operation environments share the server, any client under different operation environments is a cross-environment initiator client or a cross-environment receiver client, and the same client has the same client identification under different operation environments, and the method comprises the following steps:
when receiving a receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment of a cross-environment initiator client;
if not, the received receipt message, the target environment identifier and the client identifier are forwarded to the server, so that the server receives the forwarded receipt message, the target environment identifier and the client identifier, and the received receipt message is called back to the client of the cross-environment receiver in the target operation environment according to the target environment identifier and the client identifier.
9. A cross-environment receipt message processing method is applied to a server side in a cross-environment receipt message processing system, and the system comprises: the method comprises the following steps that a plurality of clients and a server under different operation environments share the server, any client under different operation environments is a cross-environment initiator client or a cross-environment receiver client, and the same client has the same client identification under different operation environments, and the method comprises the following steps:
receiving a receipt message, a target environment identifier and a client identifier which are forwarded by a client of an environment initiator;
and calling back the received receipt message to a cross-environment receiver client under the target operation environment according to the target environment identifier and the client identifier.
10. A cross-environment receipt message processing system, the system comprising: the client sides under different operation environments share the server side, any client side under different operation environments is a cross-environment initiator client side or a cross-environment receiver client side, and the client sides of the same client side under different operation environments have the same client side identification;
when the cross-environment initiator client receives the receipt message, analyzing a target environment identifier carried in the receipt message, and judging whether the target environment identifier is consistent with an environment identifier of an operating environment where the cross-environment initiator client is located;
if not, the cross-environment initiator client forwards the received receipt message, the target environment identifier and the client identifier to the server;
the server receives a receipt message forwarded by a client of a cross-environment initiator, the target environment identifier and the client identifier;
and the server side calls back the received receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
11. The system of claim 10, further comprising:
after receiving the receipt message, the target environment identifier and the client identifier forwarded by the client of the cross-environment initiator, the server stores the received receipt message, the target environment identifier and the client identifier to the local;
when the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back;
the server side specifically calls back the receipt message in the following way:
and the server side calls back the acquired receipt message to a cross-environment receiver client side under the target operation environment according to the target environment identification and the client side identification.
12. The system of claim 11, further comprising:
after receiving the receipt message forwarded by the client of the cross-environment initiator, the target environment identifier and the client identifier, the server determines that the scheduling state of the received receipt message is schedulable;
the server side can specifically acquire the receipt message in the following manner:
when the receipt message callback condition is triggered, the server side acquires the receipt message which is not currently called back and the scheduling state of which is schedulable.
13. The system of claim 12, wherein the server is configured to callback the obtained response piece message to the cross-environment recipient client in the target operating environment by:
the server side updates the scheduling state corresponding to the acquired receipt message from schedulable to scheduling;
and after updating the scheduling state corresponding to the obtained receipt message into scheduling from schedulable by the server, calling back the obtained receipt message to the cross-environment receiver client under the target operation environment according to the target environment identifier and the client identifier.
14. The system of any of claims 12 to 13, further comprising:
the server side judges whether the callback of the acquired receipt message is successful or not within a preset time period;
and if the callback is successful, the server side updates the scheduling state corresponding to the acquired receipt message to be scheduling end.
15. The system of claim 14, further comprising:
and if the callback fails, the server side renews the scheduling state corresponding to the acquired receipt message into schedulable state.
16. The system of claim 14, further comprising:
receiving the receipt message called back by the server by the cross-environment receiver client, and simulating the receipt message receipt by using the local message middleware so as to receive the receipt message called back by the server again through the message middleware;
after receiving the receipt message called back by the server through the message middleware again, the cross-environment receiver client sends a message that the receipt message is successfully received to the server;
the server side specifically judges whether the callback of the acquired receipt message is successful or not through the following modes:
the server side judges whether a message of successful receipt message receiving sent by a cross-environment receiver client side is received or not within a preset time period;
if a message of successfully receiving the receipt message sent by the client of the cross-environment receiving party is received, judging that the callback of the obtained receipt message is successful;
and if the message of successful receipt of the receipt message sent by the cross-environment receiver client is not received, judging that the callback of the acquired receipt message fails.
17. A cross-environment receipt message processing device applied to a cross-environment initiator client side comprises the following components:
the identification analysis module is used for analyzing the target environment identification carried in the receipt message when the receipt message is received;
the judging module is used for judging whether the environment identification is consistent with the environment identification of the running environment of the cross-environment initiator client;
and if not, forwarding the received receipt message, the target environment identifier and the client identifier to the server, so that the server receives the forwarded receipt message, the target environment identifier and the client identifier, and calling back the received receipt message to the cross-environment receiver client in the target operation environment according to the target environment identifier and the client identifier.
18. A cross-environment receipt message processing device applied to a server side comprises:
the receiving module is used for receiving the receipt message, the target environment identifier and the client identifier which are forwarded by the client of the cross-environment initiator;
and the message callback module is used for calling back the received receipt message to the client of the cross-environment receiver in the target operation environment according to the target environment identifier and the client identifier.
19. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of claim 8 when executing the program.
20. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of claim 9 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910106680.8A CN110022260B (en) | 2019-02-02 | 2019-02-02 | Cross-environment receipt message processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910106680.8A CN110022260B (en) | 2019-02-02 | 2019-02-02 | Cross-environment receipt message processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110022260A CN110022260A (en) | 2019-07-16 |
| CN110022260B true CN110022260B (en) | 2021-12-24 |
Family
ID=67188920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910106680.8A Active CN110022260B (en) | 2019-02-02 | 2019-02-02 | Cross-environment receipt message processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110022260B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110995803B (en) * | 2019-11-22 | 2022-04-19 | 用友网络科技股份有限公司 | Upstream and downstream service processing method and system, computer readable storage medium |
| CN111538602B (en) * | 2020-04-17 | 2022-12-02 | 上海万物新生环保科技集团有限公司 | Message forwarding method and device for message queue |
| CN113763094A (en) * | 2020-11-23 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Service information processing method, device, server, medium and system |
| CN112363946B (en) * | 2020-11-24 | 2024-04-16 | 上海万物新生环保科技集团有限公司 | Message forwarding method and device based on service system |
| CN115334150B (en) * | 2022-08-15 | 2024-01-19 | 北京分贝通科技有限公司 | Data forwarding method, device, system, electronic equipment and medium |
| CN115842749A (en) * | 2022-11-24 | 2023-03-24 | 中电信数智科技有限公司 | Test environment switching method, device and system |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1890942A (en) * | 2003-12-10 | 2007-01-03 | 国际商业机器公司 | Method of redirecting client requests to web services |
| CN104426868A (en) * | 2013-08-28 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Request processing method and processing apparatus |
| CN105791324A (en) * | 2016-05-12 | 2016-07-20 | 腾讯科技（深圳）有限公司 | Account login method and device |
| CN106570685A (en) * | 2015-10-13 | 2017-04-19 | 阿里巴巴集团控股有限公司 | Service processing method and device |
| CN106878045A (en) * | 2016-10-11 | 2017-06-20 | 阿里巴巴集团控股有限公司 | Service calling method and device |
| CN107656860A (en) * | 2017-10-18 | 2018-02-02 | 北京奇虎科技有限公司 | Performance test methods, apparatus and system |
| CN107920112A (en) * | 2017-11-01 | 2018-04-17 | 重庆金融资产交易所有限责任公司 | Support configuration file method for pushing, central server and the storage medium of grayscale mode |
| CN108255708A (en) * | 2017-12-14 | 2018-07-06 | 海尔优家智能科技（北京）有限公司 | Method, apparatus, storage medium and the equipment of production file are accessed in test environment |
| CN108334340A (en) * | 2017-07-17 | 2018-07-27 | 阿里巴巴集团控股有限公司 | A kind of Cross-environment data communications method, device and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7539705B2 (en) * | 2006-08-18 | 2009-05-26 | International Business Machines Corporation | System and method for managing profiles in communications devices based on a computer application environment |
| CN102130845B (en) * | 2010-01-19 | 2016-09-28 | 中兴通讯股份有限公司 | The sending method of return receipt report and processing system |
-
2019
- 2019-02-02 CN CN201910106680.8A patent/CN110022260B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1890942A (en) * | 2003-12-10 | 2007-01-03 | 国际商业机器公司 | Method of redirecting client requests to web services |
| CN104426868A (en) * | 2013-08-28 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Request processing method and processing apparatus |
| CN106570685A (en) * | 2015-10-13 | 2017-04-19 | 阿里巴巴集团控股有限公司 | Service processing method and device |
| CN105791324A (en) * | 2016-05-12 | 2016-07-20 | 腾讯科技（深圳）有限公司 | Account login method and device |
| CN106878045A (en) * | 2016-10-11 | 2017-06-20 | 阿里巴巴集团控股有限公司 | Service calling method and device |
| CN108334340A (en) * | 2017-07-17 | 2018-07-27 | 阿里巴巴集团控股有限公司 | A kind of Cross-environment data communications method, device and system |
| CN107656860A (en) * | 2017-10-18 | 2018-02-02 | 北京奇虎科技有限公司 | Performance test methods, apparatus and system |
| CN107920112A (en) * | 2017-11-01 | 2018-04-17 | 重庆金融资产交易所有限责任公司 | Support configuration file method for pushing, central server and the storage medium of grayscale mode |
| CN108255708A (en) * | 2017-12-14 | 2018-07-06 | 海尔优家智能科技（北京）有限公司 | Method, apparatus, storage medium and the equipment of production file are accessed in test environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110022260A (en) | 2019-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110022260B (en) | Cross-environment receipt message processing method and system | |
| CN109995877B (en) | Information pushing method and device | |
| CN109710394A (en) | Timing task processing system and method | |
| CN109145238B (en) | Card display method and device and mobile device | |
| CN109359118B (en) | Data writing method and device | |
| CN111290866A (en) | Service processing method and device | |
| US9407586B2 (en) | Method and system for cross device notification | |
| CN111694757B (en) | Application program testing method and device, electronic equipment and computer readable storage medium | |
| CN107948048B (en) | Method and device for forwarding chat information and electronic equipment | |
| CN110007936B (en) | Data processing method and device | |
| CN112953791B (en) | Network detection method and device, electronic equipment and computer readable storage medium | |
| CN111597065A (en) | Method and device for collecting equipment information | |
| CN112291325A (en) | Message processing method and device and computer system | |
| CN110620806B (en) | Information generation method and device | |
| CN114978945A (en) | Network dial testing method, device, system, electronic equipment and storage medium | |
| CN108984417B (en) | Software testing method, device, terminal and storage medium | |
| CN110781153A (en) | Cross-application information sharing method and system based on block chain | |
| CN109218338B (en) | Information processing system, method and device | |
| CN112838980A (en) | Message processing method, system, device, electronic equipment and storage medium | |
| CN110020264B (en) | Method and device for determining invalid hyperlinks | |
| CN108390770B (en) | Information generation method and device and server | |
| CN108681558B (en) | Data rollback method, device and terminal | |
| CN107168648B (en) | File storage method and device and terminal | |
| CN110545296A (en) | Log data acquisition method, device and equipment | |
| CN110035108B (en) | Information pushing method and system |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220413 Address after: Room 602, No. 618, Wai Road, Huangpu District, Shanghai 200010 Patentee after: Ant fortune (Shanghai) Financial Information Service Co.,Ltd. Address before: Ky1-9008 Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands, ky1-9008 Patentee before: Innovative advanced technology Co.,Ltd. |
|
| TR01 | Transfer of patent right |