CN106874076B - Distributed transaction processing method - Google Patents
Distributed transaction processing method Download PDFInfo
- Publication number
- CN106874076B CN106874076B CN201710043404.2A CN201710043404A CN106874076B CN 106874076 B CN106874076 B CN 106874076B CN 201710043404 A CN201710043404 A CN 201710043404A CN 106874076 B CN106874076 B CN 106874076B
- Authority
- CN
- China
- Prior art keywords
- subtransaction
- issued transaction
- transaction node
- node
- message
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- 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/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- 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/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
- Multi Processors (AREA)
Abstract
The invention discloses a kind of distributed transaction processing methods, comprising: one of issued transaction node in multiple issued transaction nodes receives affairs starting request, and affairs corresponding with affairs starting request are divided into several subtransactions；One of issued transaction node executes scheduled one of subtransaction, and remaining subtransaction is written to local data base, and the subtransaction in local data base is distributed to message queue；Message queue pushes subtransaction to remaining issued transaction node, corresponding subtransaction is written to the local data base of remaining issued transaction node, and after receiving success flag from remaining issued transaction node, corresponding subtransaction is deleted from queue；Remaining issued transaction node obtains from respective local data base and executes corresponding subtransaction, and after the completion of execution, corresponding subtransaction is deleted from local data base.The present invention can quickly be handled affairs, and can guarantee the consistency of affairs.
Description
Technical field
The present invention relates to data processing techniques, more specifically, it relates to distributed transaction processing method.
Background technique
SaaS platform is the platform for runing saas software.SaaS provider is that all nets required for informationization are built by enterprise
Network infrastructure and software, hardware operate platform, and are responsible for a series of services such as the implementation of all early periods, the maintenance in later period, look forward to
Industry does not need to buy software and hardware, construction computer room, recruitment IT personnel, can pass through internet use information system.SaaS is a kind of soft
Part placement model, application aim at network and deliver and design, and pass through internet trustship, deployment and access convenient for user.
It is big for saas platform service amount, it needs underlying services to be deployed on multiple servers respectively, but due to more
It not will do it communication between platform server, therefore, and the problem of inconsistency of affairs can be generated.
Summary of the invention
In view of the deficiencies of the prior art, the present invention intends to provide a kind of distributed transaction processing method, energy
It is enough that affairs are quickly handled, and can guarantee the consistency of affairs.
To achieve the above object, the present invention provides the following technical scheme that
A kind of distributed transaction processing method includes:
One of issued transaction node in multiple issued transaction nodes receives affairs starting request, and will be with the thing
Business starting requests corresponding affairs to be divided into several subtransactions；
One of issued transaction node executes scheduled one of subtransaction, and remaining subtransaction is written
To local data base；
One of issued transaction node inquires the subtransaction in local data base after having executed subtransaction, and
Subtransaction in local data base is distributed to message queue, and deletes corresponding sub- thing from local data base after distribution
Business；
The message queue pushes subtransaction to remaining issued transaction node, and connects from remaining issued transaction node
After receiving success flag, corresponding subtransaction is deleted from queue；
Respective local number is written after receiving corresponding subtransaction, by subtransaction in remaining described issued transaction node
According to library；
Remaining described issued transaction node obtains from respective local data base and executes corresponding subtransaction, and
After the completion of execution, corresponding subtransaction is deleted from local data base.
Preferably, the message queue uses RabbitMQ message queue.
Preferably, one of issued transaction node is sent out after the corresponding subtransaction of successful execution to message queue
Send confirmation message；After message queue receives confirmation message, message queue pushes subtransaction to remaining issued transaction node；Institute
One of issued transaction node is stated when executing corresponding subtransaction not successfully, is sent to message queue and cancels message；Message
After queue receives cancellation message, message queue does not push subtransaction to remaining issued transaction node.
Preferably, further includes: message status confirm the queue of server query messages in subtransaction, if it exists be confirmed or
The subtransaction being cancelled then inquires the message status that subtransaction is corresponded in one of issued transaction node, if corresponding
Message status has been identified, then sends confirmation message to message queue.
Preferably, further includes:
The subtransaction is written to respective affairs after having handled corresponding subtransaction by remaining described issued transaction node
State table；
When remaining described issued transaction node receives subtransaction from message queue, the transaction status table is inquired, if
In the presence of then the subtransaction received not being written to local data base；If it does not exist, then local data base is written to wait locate
Reason.
Preferably, further includes:
One of issued transaction node when being divided to affairs, from mark processing server acquisition include
The unique identification string of several unique identifications, and unique identification therein is added to each subtransaction correspondingly；When corresponding
Issued transaction node after having executed corresponding subtransaction, which is sent to mark processing server；
The mark processing server inquires the reception of corresponding unique identification after the predetermined time for issuing unique identification string
State；At least one unique identification is not received if it exists, then inquires corresponding issued transaction node, and according to query result into
The corresponding processing of row.
Preferably, the mark processing server record queries are as a result, work as in same issued transaction querying node to uniquely
When the number of mark is more than preset value, then the information of the issued transaction node is sent to monitoring server；The monitoring service
Device is transferred corresponding issued transaction node from spare issued transaction node repository and is replaced after receiving corresponding information
It changes.
Compared with prior art, the invention has the advantages that
1, each issued transaction node is only after being successfully processed corresponding subtransaction, then deletes the affairs, to guarantee
The consistency of entire affairs；
2, each subtransaction being pushed to by corresponding issued transaction node by message queue, one side processing speed is fast,
On the other hand, it can guarantee that each issued transaction node can be accurately received subtransaction；
3, there is function for monitoring, by monitoring server and identify the cooperation between processing server, realize to each thing
The monitoring of the processing capacity of business processing node, when some issued transaction node frequently occurs the problem of handling slow or failure,
It then transfers corresponding issued transaction node from library to be replaced, to guarantee the smooth of issued transaction.
Detailed description of the invention
Fig. 1 is the system block diagram of distributing real time system system in embodiment 1；
Fig. 2 is the system block diagram of distributing real time system system in embodiment 2；
Fig. 3 is the system block diagram of distributing real time system system in embodiment 3；
Fig. 4 is the system block diagram of distributing real time system system in embodiment 4.
Specific embodiment
Below with reference to examples and drawings, the present invention is described in further detail, but embodiments of the present invention are not
It is only limitted to this.
Embodiment 1:
Distributing real time system system shown in FIG. 1, including several issued transaction nodes and message queue 130, in figure only
Issued transaction node 110, issued transaction node 120 are shown, and with the two as an example, the function to this system carries out specifically
It is bright.Wherein, issued transaction node 110 is configured with application server 111, database 112 and transaction server 113, thing
Business processing node 120 is configured with affairs receiver 121, local data base 122 and transaction server 113.Remaining thing
Business processing node is identical as the configuration of issued transaction node 120, therefore repeats no more.
Application server 111 in issued transaction node 110 will start with affairs and ask after receiving affairs starting request
It asks corresponding affairs to be divided into several subtransactions, and subtransaction is written to local data base 112；Later, transaction services
Device 113 executes scheduled one of subtransaction (this subtransaction is the top priority in entire affairs), and by remaining sub- thing
Business is distributed to message queue 130；After message queue 130 receives subtransaction, returns to transaction server 113 and successfully mark
Know, transaction server 113 deletes corresponding subtransaction after receiving mark from local data base 112.
RabbitQ message queue can be used in the message queue in the present embodiment, after message queue 130 receives subtransaction,
Server 121 is received to the affairs that subtransaction is pushed to issued transaction node 120, affairs receive server 121 and successfully connecing
After receiving subtransaction, success flag is returned to message queue 130；After message queue 130 receives mark, phase is deleted from queue
The subtransaction answered.Affairs reception server 121 will arrive subtransaction and be written to local data base 122；The thing of issued transaction node 120
The subtransaction that business processing server 123 is inquired by turns in local data base 122 is held when inquiring pending subtransaction
The row subtransaction.After transaction server 123 has been successfully processed subtransaction, then corresponding sub- thing is deleted from local data base
Business.
Therefore, the entire issued transaction process of this system can be summarized as:
One of issued transaction node in multiple issued transaction nodes receives affairs starting request, and will open with affairs
It is dynamic that corresponding affairs is requested to be divided into several subtransactions；
One of issued transaction node executes scheduled one of subtransaction, and remaining subtransaction is written to this
Ground database；
One of issued transaction node inquires the subtransaction in local data base after having executed subtransaction, and incite somebody to action this
Subtransaction in ground database is distributed to message queue, and deletes corresponding subtransaction from local data base after distribution；
Message queue pushes subtransaction to remaining issued transaction node, and receives from remaining issued transaction node
After success flag, corresponding subtransaction is deleted from queue；
Respective local data is written after receiving corresponding subtransaction, by subtransaction in remaining issued transaction node
Library；
Remaining issued transaction node obtains from respective local data base and executes corresponding subtransaction, and is executing
After the completion, corresponding subtransaction is deleted from local data base.
Embodiment 2:
A kind of distributing real time system system based on embodiment 1, the difference from embodiment 1 is that: work as issued transaction
Transaction server 213 in node 210 sends confirmation to message queue 230 and disappears after the corresponding subtransaction of successful execution
Breath；After message queue 230 receives confirmation message, subtransaction is pushed to issued transaction node 220.Work as transaction server
213 when executing corresponding subtransaction not successfully, sends to message queue 230 and cancels message；Message queue receives cancellation and disappears
After breath 230, then subtransaction is not pushed to issued transaction node 220.
In addition, in order to avoid transaction server 213 fails normally to send confirmation message to message queue 230 or takes
Message, and message queue 230 is caused to hang up subtransaction for a long time, this system is also additionally arranged message status confirmation server 240,
Message status confirmation server 240 is configurable for the subtransaction in query messages queue, is confirmed or is taken if it exists
The subtransaction to disappear then corresponds to the message status of subtransaction in inquiry transaction processing server 213, if corresponding message status by
Confirmation then sends confirmation message to message queue 230.In this way, server 240 is confirmed by setting message status, so that message
Data can separate storage, reduce the coupling between issued transaction and Message Processing, avoid messaging failure and lead to affairs not
The case where capable of being handled in time appearance.
Embodiment 3:
A kind of distributing real time system system based on embodiment 1 or embodiment 2, the difference from embodiment 1 is that: this
In system, issued transaction node 320 is additionally arranged transaction status table 324, which is configurable for storing each
The processing of subtransaction records；Specifically, the transaction server 323 in issued transaction node 320 is handling corresponding son
After affairs, which is written to transaction status table 324, to generate corresponding historical record in transaction status table 324.
In this way, the transaction status table 324 is inquired, if when affairs receive server 321 and receive subtransaction from message queue 330
In the presence of subtransaction in the same manner, then not by the subtransaction received be written to local data base (but equally to message queue 330 return
Success flag)；If it does not exist, then local data base is written to be processed.
Embodiment 4:
A kind of distributing real time system system based on embodiment 1 or embodiment 2 or embodiment 3, the area with embodiment 1
Be not: this system is also additionally arranged mark processing server 440, which is configured with N number of unique identification
It goes here and there, includes several unique identifications in each unique identification string.Application server 411 in issued transaction node 410 exists
When dividing to affairs, the unique identification string is obtained from mark processing server 440, and unique identification one therein is a pair of
It is added to each subtransaction with answering, after the completion of addition, then the subtransaction for being added unique identification is sent to mark processing and is taken
Business device 440 is recorded.
When transaction server 413, transaction server 423 are after having executed corresponding subtransaction, acquisition is corresponded to
Unique identification included in subtransaction, and by the unique identification be sent to mark processing server 440(send when, only for this
One mark addition " processed label ").The identification server is when sending the unique identification string to application server 411, to this
Unique identification string starts timing program；And after counting the full predetermined time, the reception state of corresponding unique identification is inquired；If it exists
At least one unique identification is not received, then inquires all issued transaction nodes, as an example, inquiry transaction handles node
410, issued transaction node 420.For example, first inquiring the local data base 422 in issued transaction node 420, if inquiry
The subtransaction not being performed to this is still trapped in local data base 422, it tries sends thing to transaction server 423
Business triggering message, to notify transaction server 423 to obtain subtransaction from local data base 422 and execute.If not from local
Subtransaction is inquired in database 422, then is sent directly to affairs to the subtransaction for being added unique identification and receives server
421, to be written to local data base 422 again.In this way, can be avoided subtransaction in treatment process by above technical scheme
In there are problems that subtransaction processing interrupt or lose.
In addition, this system is also configured with spare issued transaction node repository 460, the spare issued transaction node repository 460
In include N number of issued transaction node, processing capacity issued transaction node 420 or remaining issued transaction node are identical.Meanwhile
Mark processing server 440 is additionally configured to record queries as a result, when in same issued transaction node, such as issued transaction node
420, when inquiring the number of unique identification more than preset value, then the information of the issued transaction node 420 is sent to monitoring clothes
Business device 450；Server 450 is monitored after receiving corresponding information, is transferred from spare issued transaction node repository 460 corresponding
Issued transaction node be replaced.
Claims (5)
1. a kind of distributed transaction processing method, characterized in that include:
One of issued transaction node in multiple issued transaction nodes receives affairs starting request, and will open with the affairs
It is dynamic that corresponding affairs is requested to be divided into several subtransactions；
One of issued transaction node executes scheduled one of subtransaction, and remaining subtransaction is written to this
Ground database；
One of issued transaction node inquires the subtransaction in local data base after having executed subtransaction, and incite somebody to action this
Subtransaction in ground database is distributed to message queue, and deletes corresponding subtransaction from local data base after distribution；
The message queue pushes subtransaction to remaining issued transaction node, and receives from remaining issued transaction node
After success flag, corresponding subtransaction is deleted from queue；
After receiving corresponding subtransaction respective local data is written in subtransaction by remaining described issued transaction node
Library；
Remaining described issued transaction node obtains from respective local data base and executes corresponding subtransaction, and is executing
After the completion, corresponding subtransaction is deleted from local data base；
One of issued transaction node sends confirmation message after the corresponding subtransaction of successful execution, to message queue；
After message queue receives confirmation message, message queue pushes subtransaction to remaining issued transaction node；It is described one of them
Issued transaction node sends to message queue when executing corresponding subtransaction not successfully and cancels message；Message queue receives
After cancelling message, message queue does not push subtransaction to remaining issued transaction node；
Message status confirms the subtransaction in the queue of server query messages, the subtransaction for being confirmed or being cancelled if it exists, then
The message status that subtransaction is corresponded in one of issued transaction node is inquired, if corresponding message status has been identified,
Then confirmation message is sent to message queue.
2. distributed transaction processing method according to claim 1, characterized in that the message queue uses RabbitMQ
Message queue.
3. distributed transaction processing method according to claim 1, characterized in that further include:
The subtransaction is written to respective transaction status after having handled corresponding subtransaction by remaining described issued transaction node
Table；
When remaining described issued transaction node receives subtransaction from message queue, the transaction status table is inquired, if existing,
Then the subtransaction received local data base is not written to；If it does not exist, then local data base is written to be processed.
4. distributed transaction processing method according to claim 1, characterized in that further include:
One of issued transaction node includes several from mark processing server acquisition when dividing to affairs
The unique identification string of unique identification, and unique identification therein is added to each subtransaction correspondingly；When corresponding thing
The unique identification is sent to mark processing server after having executed corresponding subtransaction by business processing node；
The mark processing server inquires the reception shape of corresponding unique identification after the predetermined time for issuing unique identification string
State；At least one unique identification is not received if it exists, then inquires corresponding issued transaction node, and carry out according to query result
Corresponding processing.
5. distributed transaction processing method according to claim 4, characterized in that the mark processing server record is looked into
It askes as a result, when the number in same issued transaction querying node to unique identification is more than preset value, then by the issued transaction section
The information of point is sent to monitoring server；The monitoring server is after receiving corresponding information, from spare issued transaction
Corresponding issued transaction node is transferred in node repository to be replaced.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710043404.2A CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710043404.2A CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106874076A CN106874076A (en) | 2017-06-20 |
| CN106874076B true CN106874076B (en) | 2019-08-30 |
Family
ID=59158867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710043404.2A Active CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106874076B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108229909B (en) * | 2017-12-14 | 2022-01-18 | 四川虹信软件股份有限公司 | Resident transaction processing method |
| CN108900356A (en) * | 2018-07-25 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of cloud service dispositions method and system |
| CN108965457A (en) * | 2018-08-02 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of message delivery method of distributed cluster system, device, equipment and medium |
| CN110134735A (en) * | 2019-04-10 | 2019-08-16 | 阿里巴巴集团控股有限公司 | The storage method and device of distributed transaction log |
| CN111078451B (en) * | 2019-08-05 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Distributed transaction processing method and device, computer equipment and storage medium |
| US20230058475A1 (en) * | 2020-02-04 | 2023-02-23 | Honeywell International Inc. | Transaction based processing using asynchronous microservices |
| CN111679892A (en) * | 2020-06-04 | 2020-09-18 | 中国建设银行股份有限公司 | Distributed transaction processing method, device, equipment and medium |
| CN113961639A (en) * | 2020-06-22 | 2022-01-21 | 金篆信科有限责任公司 | Distributed transaction processing method, terminal and computer readable storage medium |
| CN112492019B (en) * | 2020-11-24 | 2023-07-18 | 度小满科技(北京)有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN113268449A (en) * | 2021-03-03 | 2021-08-17 | 浪潮云信息技术股份公司 | Distributed file migration method and system based on object storage |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183879A (en) * | 2015-09-22 | 2015-12-23 | 浪潮集团有限公司 | Method for distributed database to keep transactional consistency under cloud computation |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
| CN106325978A (en) * | 2015-06-19 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and apparatus |
-
2017
- 2017-01-21 CN CN201710043404.2A patent/CN106874076B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN106325978A (en) * | 2015-06-19 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and apparatus |
| CN105183879A (en) * | 2015-09-22 | 2015-12-23 | 浪潮集团有限公司 | Method for distributed database to keep transactional consistency under cloud computation |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106874076A (en) | 2017-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106874076B (en) | Distributed transaction processing method | |
| EP0467546A2 (en) | Distributed data processing systems | |
| US20050004952A1 (en) | Transaction processing method, transaction control apparatus and program thereof | |
| CN105468450A (en) | Task scheduling method and system | |
| CN102687144A (en) | Managing queries | |
| CN110706069A (en) | Exception handling method, device, server and system for order payment request | |
| JP2012234333A (en) | Cluster system, synchronization control method, server device and synchronization control program | |
| CN106790422A (en) | A kind of data buffer storage cluster and data retrieval method for WEB application | |
| JP2013097548A (en) | Information processing system, information processing device, client terminal, information processing method and program | |
| CN110019469A (en) | Distributed data base data processing method, device, storage medium and electronic device | |
| JP5065259B2 (en) | Apparatus, system, method, and computer program useful for communication between enterprise information system and client (device, system, and method useful for communication between enterprise information system and client) | |
| CN106777085A (en) | A kind of data processing method, device and data query system | |
| CN112181627A (en) | Timing task scheduling method, device and system | |
| CN108108416A (en) | The method and apparatus of the expired processing of redis data | |
| CN109710679B (en) | Data extraction method and device | |
| CN110737510A (en) | Block device management system | |
| CN110825505B (en) | Task scheduling method, device, computer equipment and storage medium | |
| CN110750350B (en) | Large resource scheduling method, system, device and readable storage medium | |
| CN103312623B (en) | Task cooperation device and method | |
| CN104680307B (en) | A kind of item transaction treating method and apparatus | |
| CN108959468A (en) | A kind of monitoring method of data base directory, storage medium and server | |
| CN108287878A (en) | A kind of dynamic buffering data failure dispatching method, device and caching system | |
| CN110764697B (en) | Data management method and device | |
| CN109189813A (en) | A kind of data sharing method and device | |
| CN113986505A (en) | Task scheduling method, system, storage medium and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200409 Address after: 310051 Room 902, Building B, 459 Yanmai Road, Xixing Street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Botu Shandao Network Technology Co.,Ltd. Address before: 310012, room 121, No. 8004, Xixi street, Xihu District, Zhejiang, Hangzhou, Wensanlu Road Patentee before: ZHEJIANG PEIHONG NETWORK TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |