CN103927218B - Event distributing method and system - Google Patents

Event distributing method and system Download PDF

Info

Publication number
CN103927218B
CN103927218B CN201410183080.9A CN201410183080A CN103927218B CN 103927218 B CN103927218 B CN 103927218B CN 201410183080 A CN201410183080 A CN 201410183080A CN 103927218 B CN103927218 B CN 103927218B
Authority
CN
China
Prior art keywords
event
message
server
queue cluster
message queue
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
Application number
CN201410183080.9A
Other languages
Chinese (zh)
Other versions
CN103927218A (en
Inventor
陆海鹏
陈敏
苏青章
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Pinwei Software Co Ltd
Original Assignee
GUANGZHOU VIP NETWORK TECHNOLOGY Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by GUANGZHOU VIP NETWORK TECHNOLOGY Co Ltd filed Critical GUANGZHOU VIP NETWORK TECHNOLOGY Co Ltd
Priority to CN201410183080.9A priority Critical patent/CN103927218B/en
Publication of CN103927218A publication Critical patent/CN103927218A/en
Application granted granted Critical
Publication of CN103927218B publication Critical patent/CN103927218B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Computer And Data Communications (AREA)

Abstract

The present invention relates to event distributing method and system.The method includes:The subscription configuration information that message queue cluster receives the event of the registration from management server and produced by the subscription operation of user;Whole event informations and preserved in proxy server active pull message queue cluster;Whole subscription configuration informations and preserved in execute server active pull message queue cluster;Proxy server receives Client-initiated event message, and according to event and the binding information of Message Queuing server, the event message is pushed into corresponding Message Queuing server;Execute server pulls the event message in message queue cluster, and according to configuration information is subscribed to, con current control is carried out to the event message and is sent to event handling address.Can concurrently be sent this invention simplifies the exploitation of the event message transmission between cross-system, and event message, so as to improve the treatment effeciency of event message.

Description

Event distributing method and system
Technical field
The present invention relates to the supporting business technology in network, and in particular to a kind of event and the biography of message for cross-system Pass technology.
Background technology
The event and message transmission of cross-system are passed through frequently with manual realization in many companies at present, and the method for synchronization is realized simple It is reliable, but influence performance, and cause business primary and secondary flow unintelligible, asynchronous system realizes complexity, no matter using MQ (Message Queue)Or Redis is used as message queue, plan target treatment and error handle that is complicated and repeating are required to Flow.This mode realized by hand, lacks unified incident management and control of authority, mixed and disorderly and bad maintenance, event message Treatment effeciency is low.
The content of the invention
It is an object of the invention to propose a kind of event distributing method, it can be solved, and event message treatment effeciency is low to ask Topic.
In order to achieve the above object, the technical solution adopted in the present invention is as follows:
Event distributing method, it is comprised the following steps:
Step 1, message queue cluster receive the event of the registration from management server and because of the subscription operation of user The subscription configuration information of generation, the event carries out corresponding binding with a Message Queuing server in message queue cluster, The configuration information of subscribing to includes event, event handling number of concurrent and the event handling address subscribed to;
Whole event informations and preserved in step 2, proxy server active pull message queue cluster;
Whole subscription configuration informations and preserved in step 3, execute server active pull message queue cluster;
Step 4, proxy server receive Client-initiated event message, and tying up according to event and Message Queuing server Determine information, the event message is pushed into corresponding Message Queuing server;
Step 5, execute server pull the event message in message queue cluster, and according to subscription configuration information, Con current control is carried out to the event message and is sent to event handling address;
Wherein, the execution sequence of step 2 and step 3 is unrestricted.
Preferably, the event of the message queue cluster of different computer rooms and subscription configuration information actively carry out real-time synchronization behaviour Make.
Preferably, in step 1, the event of registration has important scale designation, and the important scale designation includes persistence mark Note and non-persistentization mark.It is further preferred that in step 4, if the event message pushes failure, determine whether with The corresponding event severity level mark of the event message, if the importance degree is marked labeled as persistence, the event is disappeared Breath is kept in into its database and is pushed again, if the importance degree is marked labeled as non-persistentization, abandons the thing Part message.
The present invention also proposes a kind of event distribution system for realizing above-mentioned event distributing method, and it includes following dress Put:
Message-oriented middleware, it is located at message queue cluster, for receive the registration from management server event and because A Message Queuing Services in the subscription operation of user and the subscription configuration information that produces, the event and message queue cluster Device carries out correspondence binding, and the subscription configuration information includes event, event handling number of concurrent and the event handling address subscribed to;
First pulls module, and it is located at proxy server, for event letter whole in active pull message queue cluster Cease and preserved;
Second pulls module, and it is located at execute server, matches somebody with somebody for subscription whole in active pull message queue cluster Confidence ceases and is preserved;
Pushing module, it is located at proxy server, for receiving Client-initiated event message, and according to event and message The binding information of queue server, corresponding Message Queuing server is pushed to by the event message;
Performing module, it is located at execute server, for pulling the event message in message queue cluster, and according to Configuration information is subscribed to, con current control is carried out to the event message and is sent to event handling address;
Wherein, first pull module and second pull module execution sequence it is unrestricted.
Preferably, the event of the message queue cluster of different computer rooms and subscription configuration information actively carry out real-time synchronization behaviour Make.
Preferably, in the message between in part, the event of registration has important scale designation, and the important scale designation includes lasting Change mark and non-persistentization mark.It is further preferred that in pushing module, if the event message pushes failure, entering one Step judges event severity level mark corresponding with the event message, if the importance degree is marked labeled as persistence, by institute State event message to keep in into its database and pushed again, if the importance degree is marked labeled as non-persistentization, lose Abandon the event message.
The present invention has the advantages that:
The exploitation of the event message transmission between cross-system is simplified, as long as the producer subscribes to event and sets in management server Put subscription configuration information, you can realize the transmission system of event message, development efficiency is high, and event message can concurrently send, So as to improve the treatment effeciency of event message.
Brief description of the drawings
Fig. 1 is the flow chart of the event distributing method of present pre-ferred embodiments;
Fig. 2 is the system architecture diagram of the instantiation of the event distributing method of present pre-ferred embodiments.
Specific embodiment
Below, with reference to accompanying drawing and specific embodiment, the present invention is described further.
As shown in figure 1, a kind of event distributing method, it is comprised the following steps:
Step S1, message queue cluster receive the event of the registration from management server and because of the subscription operation of user The subscription configuration information of generation, the event carries out corresponding binding with a Message Queuing server in message queue cluster, The configuration information of subscribing to includes event, the event handling number of concurrent subscribed to(For example, 5)With event handling address(That is HTTP Event handling URL).Management server can have keeper to be managed, and add event(That is the registration of event), the event is corresponding to disappear Breath queue server and brief description.In the event of addition, important scale designation can be added according to the significance level of event, it is described Important scale designation includes persistence mark and non-persistentization mark, to improve data processing performance.
Whole event informations and preserved in step S2, proxy server active pull message queue cluster.For The proxy server of initialization, all pulls all event informations in message queue cluster, after initialization, if there is newly-increased thing Part, then only pull newly-increased event, and newly-increased event is merged with the event for having preserved.
Whole subscription configuration informations and preserved in step S3, execute server active pull message queue cluster. For the execute server for initializing, all subscription configuration informations in message queue cluster are all pulled, after initialization, if having Newly-increased subscription configuration information, then only pull newly-increased subscription configuration information, and by newly-increased subscription configuration information with preserved Subscription configuration information merge.
Step S4, proxy server receive Client-initiated event message, and according to event and Message Queuing server Binding information, corresponding Message Queuing server is pushed to by the event message.If the event message pushes failure, enter One step judges event severity level mark corresponding with the event message, if the importance degree is marked labeled as persistence, will The event message is kept in into its database and is pushed again, until sending successfully, if the importance degree is labeled as non- Persistence is marked, then abandon the event message, so that guarantee information can not lose, can recover, and improves system process performance.
Step S5, execute server pull the event message in message queue cluster, and according to subscription configuration information, Con current control is carried out to the event message and is sent to event handling address.
Wherein, the execution sequence of step S2 and step S3 is unrestricted, i.e. step S2 can be performed before step S3, it is also possible to Step S3 is performed before step S2, and step S2 and step S3 can also be performed simultaneously.
In the present embodiment, message queue cluster has multiple, and configuration is in different computer rooms, the message queue of different computer rooms The event and subscription configuration information of cluster actively carry out real-time synchronization operation.
The present embodiment also proposes a kind of event distribution system for realizing above-mentioned event distributing method, and it includes following dress Put:
Message-oriented middleware, it is located at message queue cluster, for receive the registration from management server event and because A Message Queuing Services in the subscription operation of user and the subscription configuration information that produces, the event and message queue cluster Device carries out correspondence binding, and the subscription configuration information includes event, event handling number of concurrent and the event handling address subscribed to.No Real-time synchronization operation is actively carried out with the event and subscription configuration information of the message queue cluster of computer room.The event of registration has weight Wanting scale designation, the important scale designation includes persistence mark and non-persistentization mark.
First pulls module, and it is located at proxy server, for event letter whole in active pull message queue cluster Cease and preserved.
Second pulls module, and it is located at execute server, matches somebody with somebody for subscription whole in active pull message queue cluster Confidence ceases and is preserved.
Pushing module, it is located at proxy server, for receiving Client-initiated event message, and according to event and message The binding information of queue server, corresponding Message Queuing server is pushed to by the event message.If the event message Failure is pushed, then determines whether event severity level mark corresponding with the event message, if the importance degree is labeled as holding Longization is marked, then keep in into its database the event message and pushed again, if the importance degree is labeled as non- Persistence is marked, then abandon the event message.
Performing module, it is located at execute server, for pulling the event message in message queue cluster, and according to Configuration information is subscribed to, con current control is carried out to the event message and is sent to event handling address.
Wherein, first pull module and second pull module execution sequence it is unrestricted.
As shown in Fig. 2 the system architecture diagram of the concrete application for the present embodiment.Assuming that including computer room 1 and computer room 2.Two Individual computer room is equipped with message queue cluster, execute server and proxy server, and wherein computer room 1 also has management server. Message queue cluster includes multiple incremental message queue servers and multiple Message Queuing servers.The function of each device is as follows:
Management server takes, for connection message queue cluster, the increase of keeper's registered events, deletions, change and Check, by keeper register incident management information be sent to incremental message queue server and by registered events with it is corresponding Message Queuing server is bound, and incremental message queue server is the clothes for preserving the subscription of the event and increment of increment Business, the corresponding Message Queuing server of registered events is the message for preserving user's transmission, the event pair that a user subscribes to Answer a Message Queuing server for adapting to therewith.Management server is additionally operable to the displaying and analysis of state-event, mainly adjusts The http conditional codes returned with event handling URL, such as 200:Ask successfully, 404:Corresponding interface, 500 are not found:Interface Mistake etc., also event in certain moment number of processing and address, this keeper can be analyzed event handling whether into Work(, request number of times etc..Management server shows operation content with WEB page.
Proxy server, for connection message queue cluster, when starting initialization, all can be by http request management service The permission of device simultaneously obtains whole event informations, and be stored in its internal memory;Incremental message queue server is actively subscribed to, registration is received Event information after, merge with whole event informations;Persistence event, refers to the attribute that keeper is set in registered events, table The bright event is the very important message for the treatment of, if proxy server captures abnormal failure when sending event message, can be first Local data base queue is saved in, another one sends, and can recover.
Execute server, for connection message queue cluster, pulls when starting initialization and all subscribes to configuration information, actively Incremental message queue server is subscribed to, after receiving event message, message is disappeared by user in the event that management server is set The event handling URL treatment of breath;And with con current control function, it is concurrent in the maximum that management server is set by user Number, and logical operation control execute server is carried out to current number of concurrent in treatment event by overall control center of management server Enter number of passes.
In fact, also include a client, the operation for receiving user, and by proxy server and management server It is attached.
The present embodiment is using Rabbit MQ as message-oriented middleware.
The management server of the present embodiment, message queue cluster, between execute server, proxy server and client By RPC(Remote Procedure Call Protocol, remote procedure call protocol)It is attached.
For a person skilled in the art, technical scheme that can be as described above and design, make other each Plant corresponding change and deform, and all these changes and deforms the protection model that should all belong to the claims in the present invention Within enclosing.

Claims (6)

1. event distributing method, it is characterised in that comprise the following steps:
Step 1, message queue cluster receive the event of the registration from management server and are produced because of the subscription operation of user Subscription configuration information, the event carries out corresponding binding with a Message Queuing server in message queue cluster, described Subscribing to configuration information includes event, event handling number of concurrent and the event handling address subscribed to;
Whole event informations and preserved in step 2, proxy server active pull message queue cluster;
Whole subscription configuration informations and preserved in step 3, execute server active pull message queue cluster;
Step 4, proxy server receive Client-initiated event message, and are believed according to the binding of event and Message Queuing server Breath, corresponding Message Queuing server is pushed to by the event message;
Step 5, execute server pull the event message in message queue cluster, and according to configuration information is subscribed to, to institute Stating event message carries out con current control and sends to event handling address;
Wherein, the execution sequence of step 2 and step 3 is unrestricted;
The event and subscription configuration information of the message queue cluster of different computer rooms actively carry out real-time synchronization operation.
2. event distributing method as claimed in claim 1, it is characterised in that in step 1, the event of registration has importance degree Mark, the important scale designation includes persistence mark and non-persistentization mark.
3. event distributing method as claimed in claim 2, it is characterised in that in step 4, if the event message is pushed losing Lose, then event severity level mark corresponding with the event message is determined whether, if the importance degree is labeled as persistence mark Note, then keep in the event message into its database and pushed again, if the importance degree is labeled as non-persistentization Mark, then abandon the event message.
4. event distribution system, it is characterised in that including following device:
Message-oriented middleware, it is located at message queue cluster, for receiving the event of the registration from management server and because of user Subscription operation and the subscription configuration information that produces, the event enters with a Message Queuing server in message queue cluster Row correspondence binding, the configuration information of subscribing to includes event, event handling number of concurrent and the event handling address subscribed to;
First pulls module, and it is located at proxy server, for event information whole in active pull message queue cluster simultaneously Preserved;
Second pulls module, and it is located at execute server, and confidence is matched somebody with somebody for subscription whole in active pull message queue cluster Cease and preserved;
Pushing module, it is located at proxy server, for receiving Client-initiated event message, and according to event and message queue The binding information of server, corresponding Message Queuing server is pushed to by the event message;
Performing module, it is located at execute server, for pulling the event message in message queue cluster, and according to subscription Configuration information, con current control is carried out to the event message and is sent to event handling address;
Wherein, first pull module and second pull module execution sequence it is unrestricted;The message queue cluster of different computer rooms Event and subscribe to configuration information actively carry out real-time synchronization operation.
5. event distribution system as claimed in claim 4, it is characterised in that between in the message in part, the event of registration has Important scale designation, the important scale designation includes persistence mark and non-persistentization mark.
6. event distribution system as claimed in claim 5, it is characterised in that in pushing module, if the event message is pushed away Failure is sent, then event severity level mark corresponding with the event message is determined whether, if the importance degree is labeled as lasting Change mark, then the event message is kept in into its database and pushed again, if the importance degree is held labeled as non- Longization is marked, then abandon the event message.
CN201410183080.9A 2014-04-30 2014-04-30 Event distributing method and system Active CN103927218B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410183080.9A CN103927218B (en) 2014-04-30 2014-04-30 Event distributing method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410183080.9A CN103927218B (en) 2014-04-30 2014-04-30 Event distributing method and system

Publications (2)

Publication Number Publication Date
CN103927218A CN103927218A (en) 2014-07-16
CN103927218B true CN103927218B (en) 2017-07-04

Family

ID=51145447

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410183080.9A Active CN103927218B (en) 2014-04-30 2014-04-30 Event distributing method and system

Country Status (1)

Country Link
CN (1) CN103927218B (en)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104731912B (en) * 2015-03-24 2017-12-19 浪潮集团有限公司 A kind of message-oriented middleware MQ method for message transmission and device
CN105095365A (en) * 2015-06-26 2015-11-25 北京奇虎科技有限公司 Information flow data processing method and device
KR101889159B1 (en) * 2015-10-21 2018-08-17 주식회사 포스코 Mthoed and framework system for evnet service of steel process middleware
CN106126568A (en) * 2016-06-17 2016-11-16 杭州财人汇网络股份有限公司 One promotes mainly formula serializing buffer memory management method and system
CN107656778A (en) * 2016-07-25 2018-02-02 武汉票据交易中心有限公司 A kind of flow path processing method and system based on event
CN106598751B (en) * 2016-10-31 2020-02-07 武汉斗鱼网络科技有限公司 Method and system for distributing events through event bus
CN106776079B (en) * 2016-12-28 2021-04-23 Tcl科技集团股份有限公司 Method and system for managing user data
CN106656760B (en) * 2016-12-28 2018-02-06 广州赛意信息科技股份有限公司 A kind of message delivery method and system based on message queue
CN107659661A (en) * 2017-10-24 2018-02-02 宁波森浦信息技术有限公司 A kind of financial real-time bus system and its control method
CN107995026B (en) * 2017-11-16 2021-07-30 中国银行股份有限公司 Management and control method, management node, managed node and system based on middleware
CN108512943A (en) * 2018-05-07 2018-09-07 苏州德姆斯信息技术有限公司 Embedded device data store system based on message queue and store method
CN108900482B (en) * 2018-06-13 2021-04-16 平安科技(深圳)有限公司 Script execution method, server management system, and storage medium
CN108848031A (en) * 2018-06-14 2018-11-20 深圳金证引擎科技有限公司 Information transferring method and device
CN108874562B (en) * 2018-06-21 2022-08-02 北京顺丰同城科技有限公司 Distributed high-concurrency message queue pushing system
CN109660607B (en) * 2018-12-05 2021-08-27 北京金山云网络技术有限公司 Service request distribution method, service request receiving method, service request distribution device, service request receiving device and server cluster
CN109814997B (en) * 2019-01-18 2021-08-06 创新奇智(广州)科技有限公司 Distributed autonomous balanced artificial intelligence task scheduling method and system
CN112218251B (en) * 2019-07-09 2022-01-07 普天信息技术有限公司 Method and device for processing broadband cluster concurrent service
CN112217847B (en) * 2019-07-11 2024-08-20 北京京东尚科信息技术有限公司 Micro service platform, realization method thereof, electronic equipment and storage medium
CN113127162B (en) * 2019-12-31 2022-04-26 阿里巴巴集团控股有限公司 Automatic task execution method and device, electronic equipment and computer storage medium
CN111586171B (en) * 2020-05-07 2023-05-30 广州虎牙信息科技有限公司 Server operation method and device, electronic equipment and storage medium
CN111737023B (en) * 2020-05-14 2024-04-30 重庆长安汽车股份有限公司 Vehicle-mounted event processing method, cloud server and computer readable storage medium
CN111796149B (en) * 2020-06-15 2023-05-09 深圳市极致汇仪科技有限公司 Entity key touch vector network analyzer
CN112579156A (en) * 2020-12-11 2021-03-30 百果园技术(新加坡)有限公司 Processing system, processing method, processing device and processing equipment of business event
CN113726896B (en) * 2021-09-01 2022-09-27 看屋(上海)信息科技有限公司 Task distribution system based on commercial intelligent real estate industry

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202714A (en) * 2006-12-12 2008-06-18 国际商业机器公司 Method and system dispatching a message request to a service provider in a messaging environment
CN101605301A (en) * 2009-07-08 2009-12-16 中兴通讯股份有限公司 A kind of group system and request message distribution method that carries out the multinode transaction
CN101741850A (en) * 2009-12-25 2010-06-16 北京邮电大学 Multitask concurrent executive system and method for hybrid network service
CN101854338A (en) * 2009-03-31 2010-10-06 国际商业机器公司 Subscriber equipment, subscription management method thereof, and real-time communication method and system
CN102143198A (en) * 2010-09-30 2011-08-03 华为技术有限公司 Method, device and system for transferring messages
CN102457906A (en) * 2010-10-26 2012-05-16 中国移动通信集团河南有限公司 Load balancing control method and system of message queues

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7779421B2 (en) * 2005-06-30 2010-08-17 Ebay Inc. Business event processing

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202714A (en) * 2006-12-12 2008-06-18 国际商业机器公司 Method and system dispatching a message request to a service provider in a messaging environment
CN101854338A (en) * 2009-03-31 2010-10-06 国际商业机器公司 Subscriber equipment, subscription management method thereof, and real-time communication method and system
CN101605301A (en) * 2009-07-08 2009-12-16 中兴通讯股份有限公司 A kind of group system and request message distribution method that carries out the multinode transaction
CN101741850A (en) * 2009-12-25 2010-06-16 北京邮电大学 Multitask concurrent executive system and method for hybrid network service
CN102143198A (en) * 2010-09-30 2011-08-03 华为技术有限公司 Method, device and system for transferring messages
CN102457906A (en) * 2010-10-26 2012-05-16 中国移动通信集团河南有限公司 Load balancing control method and system of message queues

Also Published As

Publication number Publication date
CN103927218A (en) 2014-07-16

Similar Documents

Publication Publication Date Title
CN103927218B (en) Event distributing method and system
US11080090B2 (en) Method and system for scalable job processing
US20240267201A1 (en) Blockchain platform service
US8447881B2 (en) Load balancing for services
US10673969B2 (en) Scalable data feed system
CN102833080A (en) Process-to-process communication method of application software and system
CN103248670B (en) Connection management server and connection management method under computer network environment
WO2018077284A1 (en) Communication method and system, electronic device and computer cluster
CN111831748A (en) Data synchronization method, device and storage medium
CN110309231A (en) A kind of method of data synchronization and system across computer room
CN110476154A (en) Proxy server device and method for data collection
CN105786629A (en) Data processing method based on message queue
CN113965628B (en) Message scheduling method, server and storage medium
CN111176662B (en) Architecture implementation method capable of being freely assembled and deployed in distributed and single environment and deployment method
CN116680035A (en) GPU (graphics processing unit) method and device for realizing remote scheduling of kubernetes container
EP2756421A2 (en) Scale-out system to acquire event data
CN111475315A (en) Server and subscription notification push control and execution method
US7881336B2 (en) HTB gateway for healthcare transaction base
US20130097250A1 (en) Protocol and Method for Securely and Remotely Controlling a Plurality of Target Applications on a Server Network
CN112559472B (en) File transmission method, device, computer equipment and storage medium
US10846420B2 (en) Domain controller agent subscription to kerberos events for reliable transparent identification
CN107943541B (en) Communication method of Windows local component
US10616109B1 (en) System and method for web service atomic transaction (WS-AT) affinity routing
CN100452704C (en) Method and method for issuing blog articles
CN103269327A (en) Method for realizing general file data service based on agent mechanism

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
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: 20170817

Address after: 510000, room 314, No. 01, Fangcun Avenue, Liwan District, Guangdong, Guangzhou

Patentee after: GUANGZHOU WEIPINHUI RESEARCH INSTITUTE CO.,LTD.

Address before: 510370, No. 314, Fangcun Road, Liwan District, Guangdong, Guangzhou two

Patentee before: GUANGZHOU VIP NETWORK TECHNOLOGY Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20230209

Address after: 510000 No. 314, Fangcun Avenue, Liwan District, Guangzhou City, Guangdong Province

Patentee after: GUANGZHOU PINWEI SOFTWARE Co.,Ltd.

Address before: 510000 room 01, No.314, Fangcun Avenue middle, Liwan District, Guangzhou City, Guangdong Province

Patentee before: GUANGZHOU WEIPINHUI RESEARCH INSTITUTE CO.,LTD.