CN106897299B - Database access method and device - Google Patents
Database access method and device Download PDFInfo
- Publication number
- CN106897299B CN106897299B CN201510958414.XA CN201510958414A CN106897299B CN 106897299 B CN106897299 B CN 106897299B CN 201510958414 A CN201510958414 A CN 201510958414A CN 106897299 B CN106897299 B CN 106897299B
- Authority
- CN
- China
- Prior art keywords
- access request
- database
- task
- user
- database access
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a database access method and device. A database access method, the method comprising: receiving a user access request sent by a user side; according to the received user access request, sending a database access request to a database side by using an NIO (network information object) mode; after the data access request is confirmed to be successfully sent, generating a database access request task, and adding the task to a work queue, wherein the database access request task carries the user access request identifier and the database access request identifier; the current processing thread is released. By applying the scheme, the response time-consuming stage of the database does not need to occupy the thread of the application server, so that the thread exhaustion cannot be caused to influence the actual service processing capacity of the application server, and the CPU resource of the application server can be fully used for processing the service.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a database access method and apparatus.
Background
In a JAVA environment, each thread consumes memory, and if the number of threads running simultaneously is too large, the performance of the system is greatly affected, so in a Web application developed based on JAVA, a thread pool is generally set for an application server, and the performance of the application server is ensured by limiting the number of threads.
According to the existing database access method, after an application server receives a data access request from a user side, a processing thread needs to be allocated to the request, and the thread is occupied during the period from the time when the application server initiates the data access request to the database side to the time when the database returns data. Therefore, the internal processing speed of the database can greatly influence the thread occupation condition of the application server, and once the database has a problem and the response speed becomes slow, the thread of the application server is easily exhausted, so that the actual service processing capacity of the application server is reduced.
Disclosure of Invention
In order to solve the technical problems, the application provides a database access method and a database access device, and the technical scheme is as follows:
according to a first aspect of the present application, there is provided a database access method, the method comprising:
receiving a user access request sent by a user side;
according to the received user access request, sending a database access request to a database side by using an NIO (network information object) mode;
after the data access request is confirmed to be successfully sent, generating a database access request task, and adding the task to a work queue, wherein the database access request task carries the user access request identifier and the database access request identifier;
the current processing thread is released.
According to a second aspect of the present application, there is provided a database access apparatus comprising:
the user access request receiving module is used for receiving a user access request sent by a user side;
the database access request sending module is used for sending a database access request to the database side by using an NIO (network information input) mode according to the received user access request;
the database access request task adding module is used for generating a database access request task after the data access request is successfully sent, and adding the task to a work queue, wherein the database access request task carries the current user access request identifier and the database access request identifier;
and the thread releasing module is used for releasing the current processing thread.
According to the technical scheme, the application server processes the access request to the database by using the asynchronous IO mode, meanwhile, the task queue is used for storing the connection between the application server and the database, and the connection is not bound with the thread.
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 the application.
Drawings
In order to more clearly illustrate the embodiments of the present application 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 present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic flow diagram of a prior art database access method;
FIG. 2 is a flow chart illustrating an access phase of the database access method of the present application;
FIG. 3 is a schematic flow chart of a response phase of the database access method of the present application;
FIG. 4 is a schematic diagram of a complete flow chart of the database access method of the present application;
FIG. 5 is a first schematic diagram of a database access device of the present application;
fig. 6 is a second structure diagram of the database access device of the present application.
Detailed Description
According to the prior art implementation scheme, the application server interacts with the database in a synchronous call manner, as shown in fig. 1, the application server needs to allocate a processing thread to each access request sent from the user side, and the thread is occupied during a period from the time when the application server sends a data access request to the Database (DB) side until the database returns data.
Assuming that an average database time consumption is 200 ms in one data reading process, under the condition of ignoring other time occupation such as internal processing of an application server and data interaction, it can be approximately considered that each thread needs to be occupied for 200 ms, that is, 1 thread can process 5 threads in 1 second at most. If the design requirement of the application server is to be able to support 500 accesses per second, the size of the thread pool may be set to 100. However, once a problem occurs in the database, for example, the average elapsed time in a certain period of time is increased from 200 milliseconds to 1 second, the thread of the application server is exhausted by the request amount of 100 times/second, so that the supportable access amount of the application server is reduced from 500 times/second to 100 times/second, and the service processing capability is seriously reduced. In addition, other resources such as the CPU of the application server do not reach the upper limit of use at this time, and thus the problem of resource waste is also serious.
In order to solve the above problems, the present application proposes a scheme that: the application server processes the access request to the database by using an asynchronous IO mode, and simultaneously stores the connection between the application server and the database by using the task queue, so that the connection is not bound with the thread.
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be described in detail below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.
Fig. 2 is a flowchart of a data access request method provided in the present application, where the method may be executed by an application server, and includes the following steps:
s101, receiving a user access request sent by a user side;
s102, according to the received user access request, sending a database access request to a database side by using an NIO mode;
the application server firstly determines a target database/table according to the access content of the user, constructs a data access instruction, then establishes long connection with target database equipment, and sends the data access instruction through the long connection.
And S103, after the data access request is successfully sent, generating a database access request task, and adding the task to the work queue.
In the generated database access request task, the following information needs to be carried:
the identifier of the database access request has the function of finding the corresponding task from the task queue after the database returns an access result.
The identifier of the user access request is used for determining corresponding user access request information according to the binding relation between the database access request and the user access request after the database returns an access result
Carrying the user access request identification and the database access request identification;
and S104, releasing the current processing thread.
NIO is an IO API provided in JAVA version 1.4 that can replace the standard JAVA IO API, and is capable of supporting an asynchronous IO mode, compared to standard IO. In the scheme provided by the application, the application server processes the access request to the database by using the asynchronous IO mode, and simultaneously, the task queue is used for storing the connection information between the application server and the database. Based on the NIO characteristic, after the application server sends the data access request to the database, the current processing thread can be released, and the thread does not need to be set to monitor the database side. When the time consumption of the database rises, the number of tasks in the work queue is only increased, the occupation of the thread of the application server is not influenced, and the reduction of the service processing capacity of the application server is not caused. On the other hand, the CPU resource of the application server can be fully used for processing the service.
In an improved embodiment of the present application, the interaction between the application server and the user side may also use an NIO method, and specifically, in S101 to S102, the application server receives a user access request sent by the user side using the NIO method; generating a user access request task according to a received user access request, and adding the task to a work queue; and subsequently, acquiring a user access request task from the work queue, and then sending a database access request to the database side by using an NIO (network information object) mode aiming at the acquired user access request task.
On the basis of the above data access request method, the present application further provides a data access response method, where the method is executed by an application server, and as shown in fig. 3, the method may include the following steps:
s201, receiving a database access response sent by a database side by using an NIO mode;
s202, according to the database access request identification carried in the database access response, obtaining a database access request task with the same identification from a work queue;
and S203, sending a user access response to the user side according to the user access request identifier carried in the acquired database access request task.
According to the data access request method provided by the application, the task queue is used for storing the connection information between the application server and the database, and the processing thread can be released after the application server sends the data access request to the database, without setting a thread to monitor the database side. And after the database returns the access result to the application server, the application server firstly finds the corresponding task from the work queue according to the database access request identifier carried in the database access response, and then further feeds the access result back to the user side which originally sends the access request according to the user access request identifier carried in the task, thereby completing the whole access operation.
In the database access response process, the interaction between the application server and the user side can also use an NIO mode, specifically, in S202-S203, the application server generates a database access response task according to a user access request identifier carried in the acquired database access request task, and puts the task into a work queue; and subsequently, acquiring a database access response task from the work queue, and then sending a user access response to the user side by using an NIO mode aiming at the acquired database access response task.
Fig. 4 shows a schematic flow chart of a method including a complete data access request and data access response process, and to facilitate understanding of the interaction process inside the application server, the inside of the application server is divided into 5 interaction units: the system comprises a user side NIO module, a user interaction task queue, a work thread pool, a database driving layer NIO module and a database interaction task queue, and has the following basic functions:
the user side NIO module and the database driver layer NIO module: the two modules can use threads independent of the working thread pool and both adopt an NIO mode to communicate with external equipment.
The user interaction task queue and the database interaction task queue are equivalent to the logical division of the "work queue" from the perspective of the "user side" and the "database side" in the previous embodiment, and the division is only for convenience of explanation, and the actual function is the same as the "work queue" described above.
A working thread pool: the function is the same as that of the working thread pool in the prior art, and the service supporting capacity of the application server is directly determined.
The steps in fig. 4 are explained below:
a data request stage:
s301, the NIO module of the user side receives the user access request sent by the user side in the NIO mode.
S302, generating a user access request task, adding the task to a user interaction task queue, and marking the task as a to-be-processed state.
S303-S304, the working thread pool asynchronously reads all the user access request tasks in the state to be processed, and forwards the read tasks to the NIO module of the database driving layer after necessary processing; and modifying the state of the user access request task which is read from the user interaction task queue into processed state correspondingly.
S305, the database driving layer NIO module determines a target database/table and constructs a data access instruction according to the user access request task, then long connection is established with target database equipment, and the data access instruction is sent through the long connection.
S306, after the data access request is successfully sent, generating a database access request task, adding the task to a database interaction task queue, and marking the task as a to-be-processed state;
in the generated database access request task, the following information needs to be carried:
the identifier of the database access request has the function of finding the corresponding task from the task queue after the database returns an access result.
And S307, the work thread pool releases the current task, because the access connection information is stored after the task is added to the database interaction task queue, and the thread is not required to be used for monitoring all the time, the resource can be released for processing the next task after the current task is added to the database interaction task queue.
And a data response stage:
and S308, receiving the database access response sent by the database side by the NIO module of the database side.
S309, updating the database interaction task queue:
firstly, according to a database access request identifier carried in a database access response, a database access request task which has the same identifier and is in a state of waiting for processing is read from a database interaction task queue. And reading the finished tasks from the database interaction task queue, and correspondingly modifying the state into processed state.
And further, generating a database access response task according to the user access request identifier carried in the acquired database access request task, putting the task into a database interaction task queue, and marking the task as a to-be-processed state.
S310-S311, the working thread pool asynchronously reads all database access response tasks in the state to be processed, and transfers the read tasks to the NIO module at the user side after necessary processing; and modifying the state of the database access response task which is read from the database interaction task queue into processed state correspondingly.
S312, the NIO module of the user side sends the user access response to the user side by using the NIO mode according to the acquired database access response task.
According to the scheme, after the application server sends the access request to the database, the processing thread is released, if the time consumption of the database side is increased, the number of tasks in the work queue is increased, the occupation of the thread of the application server is not affected, the thread of the application server is not exhausted, the service access amount is not affected, and the CPU resource of the application server can be fully used for processing the service. Further, since the number of working threads is independent of the traffic access, the number of threads actually consumed can be maintained at a relatively small number, thereby reducing thread switching overhead.
Corresponding to the above method embodiment, the present application further provides a database access apparatus, as shown in fig. 5, the apparatus may include:
a user access request receiving module 110, configured to receive a user access request sent by a user side;
a database access request sending module 120, configured to send a database access request to a database side in an NIO manner according to the received user access request;
a database access request task adding module 130, configured to generate a database access request task after it is confirmed that the data access request is successfully sent, and add the task to the work queue, where the database access request task carries the current user access request identifier and the database access request identifier;
and a thread releasing module 140, configured to release the current processing thread.
In a specific embodiment of the present application, the user access request receiving module 110 may be specifically configured to: and receiving a user access request sent by a user side by using an NIO mode, generating a user access request task according to the received user access request, and adding the task to a work queue.
Correspondingly, the database access request sending module 120 may be specifically configured to: and acquiring a user access request task from the work queue, and sending a database access request to a database side by using an NIO (network information object) mode aiming at the acquired user access request task.
Referring to fig. 6, in an embodiment of the present application, the database access device may further include:
a database access response receiving module 210, configured to receive a database access response sent by a database side in an NIO manner;
a database access request task obtaining module 220, configured to obtain, according to a database access request identifier carried in a database access response, a database access request task with the same identifier from a work queue;
and the user access response sending module 230 is configured to send a user access response to the user side according to the user access request identifier carried in the acquired database access request task.
In a specific embodiment of the present application, the user access response sending module 230 may be specifically configured to: and sending a user access response to the user side by using an NIO mode.
Specifically, the database access request task obtaining module 220 may further generate a database access response task according to a user access request identifier carried in the obtained database access request task, and add the task to the work queue; accordingly, the user access response sending module 230 obtains the database access response task from the work queue, and sends the user access response to the user side in the NIO manner for the obtained database access response task.
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.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application 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 method according to the embodiments or some parts of the embodiments of the present application.
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 solution of the present application. 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 directed to embodiments of the present application and it is noted that numerous modifications and adaptations may be made by those skilled in the art without departing from the principles of the present application and are intended to be within the scope of the present application.
Claims (12)
1. A database access method, the method comprising:
receiving a user access request sent by a user side;
distributing a processing thread for the user access request according to the received user access request, and sending a database access request to a database side by using an NIO (network input/output) mode;
after the data access request is confirmed to be successfully sent, generating a database access request task, and adding the task to a work queue, wherein the database access request task carries the user access request identifier and the database access request identifier;
the current processing thread is released.
2. The method according to claim 1, wherein the receiving the user access request sent by the user side comprises:
and receiving a user access request sent by a user side by using an NIO mode, generating a user access request task according to the received user access request, and adding the task to a work queue.
3. The method according to claim 1, wherein the sending the database access request to the database side by using the NIO method according to the received user access request comprises:
and acquiring a user access request task from the work queue, and sending a database access request to a database side by using an NIO (network information object) mode aiming at the acquired user access request task.
4. The method according to any one of claims 1 to 3, further comprising:
receiving a database access response sent by a database side by using an NIO mode;
according to the database access request identification carried in the database access response, acquiring a database access request task with the same identification from a work queue;
and sending a user access response to the user side according to the user access request identifier carried in the acquired database access request task.
5. The method of claim 4, wherein sending the user access response to the user side comprises:
and sending a user access response to the user side by using an NIO mode.
6. The method according to claim 4, wherein the sending a user access response to the user side according to the user access request identifier carried in the acquired database access request task includes:
generating a database access response task according to a user access request identifier carried in the acquired database access request task, and adding the task to a work queue;
and acquiring the database access response task from the work queue, and sending a user access response to the user side by using an NIO mode aiming at the acquired database access response task.
7. A database access apparatus, the apparatus comprising:
the user access request receiving module is used for receiving a user access request sent by a user side;
the database access request sending module is used for distributing a processing thread for the user access request according to the received user access request and sending the database access request to a database side in an NIO mode;
the database access request task adding module is used for generating a database access request task after the data access request is successfully sent, and adding the task to a work queue, wherein the database access request task carries the current user access request identifier and the database access request identifier;
and the thread releasing module is used for releasing the current processing thread.
8. The apparatus of claim 7, wherein the user access request receiving module is specifically configured to:
and receiving a user access request sent by the user side by using an NIO mode.
9. The apparatus according to claim 7, wherein the database access request sending module is specifically configured to:
generating a user access request task according to a received user access request, and adding the task to a work queue;
and acquiring a user access request task from the work queue, and sending a database access request to a database side by using an NIO (network information object) mode aiming at the acquired user access request task.
10. The apparatus of any one of claims 7 to 9, further comprising:
the database access response receiving module is used for receiving the database access response sent by the database side in an NIO mode;
the database access request task acquisition module is used for acquiring database access request tasks with the same identification from a work queue according to the database access request identification carried in the database access response;
and the user access response sending module is used for sending the user access response to the user side according to the user access request identifier carried in the acquired database access request task.
11. The apparatus of claim 10, wherein the user access response sending module is specifically configured to:
and sending a user access response to the user side by using an NIO mode.
12. The apparatus of claim 10, wherein:
the database access request task acquisition module is also used for generating a database access response task according to the user access request identifier carried in the acquired database access request task and adding the task to a work queue;
the user access response sending module is specifically configured to acquire a database access response task from the work queue, and send a user access response to the user side in an NIO manner for the acquired database access response task.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510958414.XA CN106897299B (en) | 2015-12-17 | 2015-12-17 | Database access method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510958414.XA CN106897299B (en) | 2015-12-17 | 2015-12-17 | Database access method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106897299A CN106897299A (en) | 2017-06-27 |
| CN106897299B true CN106897299B (en) | 2020-03-10 |
Family
ID=59189816
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510958414.XA Active CN106897299B (en) | 2015-12-17 | 2015-12-17 | Database access method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106897299B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107562538B (en) * | 2017-08-22 | 2020-01-07 | 中国铁道科学研究院电子计算技术研究所 | Data extraction multitask management method and system in railway transportation statistics |
| CN110493891B (en) * | 2018-05-14 | 2021-05-11 | 杭州海康威视系统技术有限公司 | Resource allocation method, device and system |
| CN109951560B (en) * | 2019-03-27 | 2023-11-14 | 努比亚技术有限公司 | Method, terminal and storage medium for improving concurrency and application speed of application service |
| CN110673931A (en) * | 2019-09-06 | 2020-01-10 | 平安普惠企业管理有限公司 | Distributed calculation method for document synthesis, document synthesis system and control device thereof |
| CN110704415A (en) * | 2019-10-08 | 2020-01-17 | 加和数康(北京)信息科技有限公司 | Lightweight data acquisition method and system |
| CN111651279A (en) * | 2020-02-20 | 2020-09-11 | 中国银联股份有限公司 | Method and system for processing business process |
| CN113592470A (en) * | 2021-08-03 | 2021-11-02 | 北京百度网讯科技有限公司 | Service processing method and device, electronic equipment and storage medium |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1277196C (en) * | 2004-06-09 | 2006-09-27 | 中兴通讯股份有限公司 | Method for applied server of computer system |
| CN101969456B (en) * | 2010-09-17 | 2014-10-01 | 深圳市融创天下科技股份有限公司 | Geographical map displaying system and method |
| US8661448B2 (en) * | 2011-08-26 | 2014-02-25 | International Business Machines Corporation | Logical partition load manager and balancer |
| US9189257B2 (en) * | 2011-11-08 | 2015-11-17 | Pivotal Software, Inc. | Computer device and method of providing configuration files in a computer device |
| US20150347447A1 (en) * | 2014-05-27 | 2015-12-03 | Acer Cloud Technology Inc. | Method and architecture for synchronizing files |
| CN105824866A (en) * | 2015-12-14 | 2016-08-03 | 广东亿迅科技有限公司 | Distributed type relational database shared connection pool achieved on basis of NIO |
| CN106250559A (en) * | 2016-08-17 | 2016-12-21 | 浪潮电子信息产业股份有限公司 | The method that the asynchronous non-obstruction of network I/O is applied to database middleware |
-
2015
- 2015-12-17 CN CN201510958414.XA patent/CN106897299B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106897299A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106897299B (en) | Database access method and device | |
| EP3073374B1 (en) | Thread creation method, service request processing method and related device | |
| CN109451051B (en) | Service request processing method and device, electronic equipment and storage medium | |
| US20170353397A1 (en) | Offloading Execution of an Application by a Network Connected Device | |
| CN110704177B (en) | Computing task processing method and device, computer equipment and storage medium | |
| JP2014520346A5 (en) | ||
| CN110659131B (en) | Task processing method, electronic device, computer equipment and storage medium | |
| CN109819023B (en) | Distributed transaction processing method and related product | |
| CN111078353A (en) | Operation method of storage equipment and physical server | |
| CN111104219A (en) | Binding method, device, equipment and storage medium of virtual core and physical core | |
| CN112286688A (en) | Memory management and use method, device, equipment and medium | |
| CN106775975B (en) | Process scheduling method and device | |
| CN109818977B (en) | Access server communication optimization method, access server and communication system | |
| CN111586140A (en) | Data interaction method and server | |
| CN105677481B (en) | A kind of data processing method, system and electronic equipment | |
| CN111052083B (en) | Method and apparatus for managing scheduling of services during startup | |
| CN111177032A (en) | Cache space application method, system, device and computer readable storage medium | |
| CN111913792B (en) | Service processing method and device | |
| CN110489356B (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN111625344B (en) | Resource scheduling system, method and device in application system | |
| CN116881003A (en) | Resource allocation method, device, service equipment and storage medium | |
| CN116483570A (en) | Dynamic capacity expansion and contraction method, device and equipment for stateful service and storage medium | |
| JP5981050B2 (en) | Application program management apparatus and management method | |
| CN109634721B (en) | Method and related device for starting communication between virtual machine and host |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200921 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200921 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |