CN110753040B - Request processing method and device - Google Patents

Request processing method and device Download PDF

Info

Publication number
CN110753040B
CN110753040B CN201910940869.7A CN201910940869A CN110753040B CN 110753040 B CN110753040 B CN 110753040B CN 201910940869 A CN201910940869 A CN 201910940869A CN 110753040 B CN110753040 B CN 110753040B
Authority
CN
China
Prior art keywords
protocol stack
network
network protocol
thread
socket
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
CN201910940869.7A
Other languages
Chinese (zh)
Other versions
CN110753040A (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.)
Maipu Communication Technology Co Ltd
Original Assignee
Maipu Communication 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 Maipu Communication Technology Co Ltd filed Critical Maipu Communication Technology Co Ltd
Priority to CN201910940869.7A priority Critical patent/CN110753040B/en
Publication of CN110753040A publication Critical patent/CN110753040A/en
Application granted granted Critical
Publication of CN110753040B publication Critical patent/CN110753040B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms

Abstract

The embodiment of the invention discloses a request processing method and a device, which relate to the technical field of network equipment, can simultaneously run a non-standard network protocol stack and a Linux network protocol stack on network equipment such as a router/a switch and the like, and comprises the following steps: receiving a calling request sent by a network application from a default socket docking interface; acquiring the thread ID of the network application from a Linux operating system, and judging whether a user thread ID table contains the thread ID, if so, processing the calling request; if not, calling a socket docking interface of the Linux network protocol stack to enable the Linux network protocol stack to process the calling request.

Description

Request processing method and device
Technical Field
The present invention belongs to the technical field of network devices, and in particular, to a request processing method and apparatus.
Background
With the development of network technology, a Linux network protocol stack (i.e., a network protocol stack carried by a Linux operating system, also referred to as a standard network protocol stack) cannot meet the expansion requirement of network applications, and a network device manufacturer generally develops a set of non-standard network protocol stack independently to perform compatible processing with the Linux network protocol stack. Therefore, many network device manufacturers are beginning to research how to comply with the non-standard network protocol stack and the Linux network protocol stack in the Linux operating system to meet the expansion requirement of the network application.
The current implementation methods mainly comprise the following steps:
the first method is to reform the non-standard network protocol stack of the equipment manufacturer, so as to blend the Linux network protocol stack into the non-standard network protocol stack based on the Linux operating system;
the second is to improve the network application to be merged into the non-standard network protocol stack of the equipment manufacturer, and the two implementation modes have the problems of large modification amount, poor expansibility and the like.
And thirdly, determining a target network protocol stack according to the indication information of the network application. The network application realizes the calling of the target network protocol stack by adapting the uniform interface function, and the method can realize the switching between the nonstandard network protocol stack and the Linux network protocol stack only by adjusting the socket interface or using a new uniform interface. The openness of network applications suffers.
Therefore, how to simply and efficiently realize that the extension requirement of the network application is met in the Linux operating system is a technical problem to be solved urgently.
Disclosure of Invention
The embodiment of the invention provides a method and a device for using a heterogeneous network protocol stack, which are used for solving the technical problem of meeting the expansion requirement of network application in a Linux operating system.
In view of the foregoing, in a first aspect, an embodiment of the present invention provides a method for request processing, where the method includes:
receiving a calling request sent by a network application from a default socket docking interface;
acquiring the thread ID of the network application from a Linux operating system, and judging whether a user thread ID table contains the thread ID, if so, processing the calling request; if not, calling a socket docking interface of the Linux network protocol stack to enable the Linux network protocol stack to process the calling request.
In a second aspect, an embodiment of the present invention provides an apparatus for request processing, where the apparatus includes:
the receiving module is used for receiving a calling request sent by the network application from a default socket docking interface;
the processing module is used for acquiring the thread ID of the network application from a Linux operating system and judging whether a user thread ID table contains the thread ID, if so, the calling request is processed; if not, calling a socket docking interface of the Linux network protocol stack to enable the Linux network protocol stack to process the calling request.
In a third aspect, an embodiment of the present invention provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores program instructions, and when the processor reads and executes the program instructions, the method for processing a request according to the first aspect is performed.
In a fourth aspect, an embodiment of the present invention provides a readable storage medium, where computer program instructions are stored, and when the computer program instructions are read and executed by a processor, the method for processing a request according to the first aspect is performed.
The embodiment of the invention provides a request processing method and a request processing device, which can simultaneously run a nonstandard network protocol stack and a Linux network protocol stack on network equipment such as a router/a switch and the like, network applications can find the applicable network protocol stack according to requirements, all the network applications carry out information interaction with the network protocol stack through the same socket interface, and the Linux network protocol stack does not need to be improved. The method of the embodiment of the invention enhances the openness and compatibility of the network equipment and ensures that the expansion requirement of the network application can be directly operated on the network equipment such as a router/switch and the like.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a method for processing a request according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a connection relationship between a network protocol stack and a socket interface according to an embodiment of the present invention;
FIG. 3 is a block diagram of a request processing apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a request processing apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The system architecture and the service scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the system architecture and the appearance of a new service scenario.
The above method is described in detail with reference to specific examples.
In the embodiment of the invention, the network application can complete the network function only through a network protocol stack running in an operating system such as Linux and the like, the network application completes the network message transceiving and the network function control by calling a socket interface (a network function interface defined by a standard C library, wherein the socket interface comprises a plurality of functions such as socket (), bin (), list (), recvfrom (), sendto () and the like, and the socket docking interface of the network protocol stack is docked with the socket interface to realize the function of the socket interface. The socket interface can only be connected with the socket interface of one network protocol stack, so that when the network equipment such as a router/switch and the like has both a nonstandard network protocol stack and a Linux network protocol stack, the nonstandard network protocol stack and the Linux network protocol stack need to coexist to ensure that the expansion requirement of the network application can directly run on the network equipment such as the router/switch and the like
An embodiment of the present invention provides a method for processing a request, as shown in fig. 1, where the method includes:
step 101, receiving a call request sent by a network application from a default socket docking interface.
In the embodiment of the invention, before the network application needs to send the call request to the network protocol stack, the network application calls the socket interface, and the socket interface calls the socket docking interface of the network protocol stack so as to send the call request to the network protocol stack. The socket docking interface of the network protocol stack is an interface used by the network protocol stack for docking with the socket interface. Socket docking interfaces of the network protocol stack correspond to socket interfaces one to one. On the Linux operating system, the network protocol stack must register the socket docking interface of the network protocol stack with the Linux system call table. When the network application calls the socket interface, the Linux operating system finds the socket docking interface corresponding to the network protocol stack through the Linux system call table and calls the socket docking interface.
In the embodiment of the invention, due to the expansion requirement of the network application, part of the network application can directly use the Linux network protocol stack, but part of the network application needs to use the nonstandard network protocol stack, so that the nonstandard network protocol stack and the Linux network protocol stack exist in the Linux operating system at the same time.
Optionally, the call request sent by the network application is received from a default socket docking interface, and may be the call request sent by the network application through calling a socket interface of the Linux operating system, and received from a socket docking interface of the Linux network protocol stack.
Preferably, the receiving, from the default socket docking interface, a call request sent by the web application includes:
and receiving the call request sent by the network application through calling the socket interface of the Linux operating system from the socket docking interface of the nonstandard network protocol stack.
In the embodiment of the invention, the Linux operating system is started, the nonstandard network protocol stack is initialized, the socket interface of the nonstandard network protocol stack is in butt joint with the socket interface of the Linux operating system, and the proc file is created. And the Linux network protocol stack completes initialization, and the socket docking interface of the Linux network protocol stack is not docked with the socket interface because the nonstandard network protocol stack is already docked with the socket interface. To ensure that the socket interface only interfaces with one network protocol stack. Therefore, the socket interface does not need to be changed or adjusted. As shown in fig. 2, an embodiment of the present invention provides a schematic diagram of a connection relationship between a non-standard network protocol stack and a Linux network protocol stack and a socket interface.
In the embodiment of the invention, if the network application needs to use the non-standard network protocol stack, the network application acquires the unique thread ID of the network application from the Linux operating system and writes the thread ID into a proc file created by the non-standard network protocol stack, wherein the proc file is a file supported by the Linux operating system and can be accessed by both the network application and the network protocol stack. Through the file, the network application can issue control information to the network protocol stack. The thread ID is a unique ID assigned by the Linux operating system to each network application. The nonstandard network protocol stack records the thread ID into a user thread ID table, wherein the user thread ID table records the thread IDs of all network applications needing to use the nonstandard network protocol stack.
In an embodiment of the present invention, before receiving, from a default socket docking interface, a call request sent by a web application, the method further includes:
after the network application is started, writing the thread ID of the network application, which is acquired by the network application from a Linux operating system, into a proc file created by a non-standard network protocol stack;
and the nonstandard network protocol stack records the thread ID into a user thread ID table, wherein the user thread ID table records the thread IDs of all network applications needing to use the nonstandard network protocol stack.
Preferably, before the thread ID of the web application acquired by the web application from the Linux operating system after the web application is started is written into a proc file created by a non-standard network protocol stack, the method further includes:
and docking the socket docking interface of the non-standard network protocol stack with the socket interface of the Linux operating system, and creating a proc file.
102, acquiring a thread ID of the network application from a Linux operating system, and judging whether a user thread ID table contains the thread ID, if so, processing the calling request; if not, calling a socket docking interface of the Linux network protocol stack to enable the Linux network protocol stack to process the calling request. The Linux network protocol stack is a network protocol stack carried by a Linux operating system, and is suitable for network application, such as NETCONF. The nonstandard network protocol stack is mainly a network protocol stack which is customized and developed by network equipment manufacturers such as a router/a switch and the like according to the characteristics of the network protocol stack, and compared with a Linux network protocol stack with a Linux operating system, the nonstandard network protocol stack has higher performance and lower resource consumption. The nonstandard network protocol stack works in a Linux operating system, and the nonstandard network protocol stack is used by the expansion requirement of network application, such as a routing protocol.
For example, a Linux operating system is started, a nonstandard network protocol stack is initialized, a socket interface of the nonstandard network protocol stack is connected with a socket interface of the Linux operating system, and a proc file is created. And the Linux network protocol stack completes initialization, and a socket docking interface of the Linux network protocol stack is not docked with the socket interface.
When a certain network application is started and the network application needs to use a non-standard network protocol stack, the network application acquires a unique thread ID of the network application from a Linux operating system and writes the thread ID into a proc file created by the non-standard network protocol stack. The nonstandard network protocol stack responds to the write proc file of the network application and records the thread ID to a user thread ID table of the nonstandard network protocol stack. The network application generates a socket interface call, such as a bind () function call, which calls a socket docking interface of the non-standard network protocol stack, thereby sending a call request to the non-standard network protocol stack. The nonstandard network protocol stack acquires the thread ID of the network application from the Linux operating system according to the call request of the network application, and the thread ID exists in a user thread ID table at the moment, so the call request is processed by the nonstandard network protocol stack.
For example, when a certain network application is started, the network application needs to use a Linux network protocol stack, and a socket interface call, such as a bind () function call, is generated during the running process, and the socket interface calls a socket docking interface of a non-standard network protocol stack, so that a call request is sent to the non-standard network protocol stack. The nonstandard network protocol stack acquires the thread ID of the network application from the Linux operating system according to the call request of the network application, and the nonstandard network protocol stack calls the socket docking interface of the Linux network protocol stack because the thread ID of the network application is not in the user thread ID table of the nonstandard network protocol stack, so that the Linux network protocol stack processes the call request of the network application.
The embodiment of the invention provides a request processing method, which can simultaneously run a nonstandard network protocol stack and a Linux network protocol stack on network equipment such as a router/a switch and the like, network applications can find the applicable network protocol stack according to requirements, all the network applications carry out information interaction with the network protocol stack through the same socket interface, and the Linux network protocol stack does not need to be improved. The method of the embodiment of the invention enhances the openness and compatibility of the network equipment and ensures that the expansion requirement of the network application can be directly operated on the network equipment such as a router/switch and the like.
An embodiment of the present invention provides a device for processing a request, as shown in fig. 3, where the device 30 includes:
a receiving module 301, configured to receive, by a default socket docking interface, a call request sent by a network application;
a processing module 302, configured to obtain a thread ID of the network application from a Linux operating system, and determine whether a user thread ID table includes the thread ID, if so, process the call request; if not, calling a socket docking interface of the Linux network protocol stack to enable the Linux network protocol stack to process the calling request.
The processing module 302 is further configured to, after the network application is started, write the thread ID of the network application, which is obtained by the network application from the Linux operating system, into a proc file;
the processing module is further configured to record the thread ID into a user thread ID table, where the user thread ID table records all thread IDs of network applications that need to use a non-standard network protocol stack.
As shown in fig. 4, the apparatus 30 further includes a creating module 303, configured to interface a socket interface of the non-standard network protocol stack with a socket interface of a Linux operating system, and create a proc file.
The receiving module 301 is specifically configured to receive, from a socket docking interface of a non-standard network protocol stack, the call request sent by the network application through a socket interface of a Linux operating system.
The embodiment of the invention provides a request processing device, which can simultaneously run a nonstandard network protocol stack and a Linux network protocol stack on network equipment such as a router/a switch and the like, network applications can find the applicable network protocol stack according to requirements, all the network applications carry out information interaction with the network protocol stack through the same socket interface, and the Linux network protocol stack does not need to be improved. The method of the embodiment of the invention enhances the openness and compatibility of the network equipment and ensures that the expansion requirement of the network application can be directly operated on the network equipment such as a router/switch and the like.
The embodiment of the invention also provides electronic equipment, which comprises a memory and a processor, wherein the memory stores program instructions, and the processor executes the request processing method provided by the embodiment when reading and running the program instructions.
The embodiment of the present invention further provides a readable storage medium, where the readable storage medium stores computer program instructions, and when the computer program instructions are read and run by a processor, the computer program instructions execute a plurality of processes of the method for request processing provided in the foregoing embodiment, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is omitted here. Examples of the computer-readable storage medium include a Random-Access Memory (RAM), a Read-Only Memory (ROM), a Flash Memory (Flash Memory), a Hard Disk Drive (HDD), a Solid-State Drive (SSD), and an optical disc.
It should be noted that, in a specific implementation process, each step executed in the method flow shown in the foregoing embodiment may be implemented by a processor in a hardware form executing a computer execution instruction in a software form stored in a memory, and details are not described here to avoid repetition.
The memory above may include volatile memory, such as random access memory; non-volatile memory, such as read-only memory, flash memory, hard disks, solid state disks, etc.; combinations of the above categories of memory may also be included.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the present invention.

Claims (8)

1. A method of request processing, the method comprising:
receiving a calling request sent by a network application from a default socket docking interface;
acquiring the thread ID of the network application from a Linux operating system, and judging whether a user thread ID table contains the thread ID, if so, processing the calling request; if not, calling a socket docking interface of a Linux network protocol stack to enable the Linux network protocol stack to process the calling request;
the receiving of the call request sent by the network application from the default socket docking interface includes:
and receiving the call request sent by the network application through calling the socket interface of the Linux operating system from the socket docking interface of the nonstandard network protocol stack.
2. The method of claim 1, wherein before receiving the call request sent by the web application from the default socket docking interface, the method further comprises:
after the network application is started, writing the thread ID of the network application, which is acquired by the network application from a Linux operating system, into a proc file created by the nonstandard network protocol stack;
and the nonstandard network protocol stack records the thread ID into a user thread ID table, wherein the user thread ID table records the thread IDs of all network applications needing to use the nonstandard network protocol stack.
3. The method according to claim 2, wherein after the web application is started, before the thread ID of the web application acquired by the web application from the Linux operating system is written into the proc file created by the non-standard network protocol stack, the method further comprises:
and docking the socket docking interface of the non-standard network protocol stack with the socket interface of the Linux operating system, and creating a proc file.
4. An apparatus for request processing, the apparatus comprising:
the receiving module is used for receiving a calling request sent by the network application from a default socket docking interface;
the processing module is used for acquiring the thread ID of the network application from a Linux operating system and judging whether a user thread ID table contains the thread ID, if so, the calling request is processed; if not, calling a socket docking interface of a Linux network protocol stack to enable the Linux network protocol stack to process the calling request;
the receiving module is specifically configured to receive, from a socket docking interface of a non-standard network protocol stack, the call request sent by the network application through a socket interface of a Linux operating system.
5. The apparatus according to claim 4, wherein the processing module is further configured to write, after the network application is started, the thread ID of the network application, which is obtained by the network application from a Linux operating system, into a proc file;
the processing module is further configured to record the thread ID into a user thread ID table, where the user thread ID table records all thread IDs of network applications that need to use the non-standard network protocol stack.
6. The apparatus according to claim 5, further comprising a creating module, configured to interface a socket interface of the non-standard network protocol stack with a socket interface of a Linux operating system, and create a proc file.
7. An electronic device, comprising a memory having stored therein program instructions and a processor that, when read and executed, performs the method of request processing according to any of claims 1-3.
8. A readable storage medium having stored thereon computer program instructions which, when read and executed by a processor, perform the method of request processing according to any one of claims 1-3.
CN201910940869.7A 2019-09-30 2019-09-30 Request processing method and device Active CN110753040B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910940869.7A CN110753040B (en) 2019-09-30 2019-09-30 Request processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910940869.7A CN110753040B (en) 2019-09-30 2019-09-30 Request processing method and device

Publications (2)

Publication Number Publication Date
CN110753040A CN110753040A (en) 2020-02-04
CN110753040B true CN110753040B (en) 2022-02-22

Family

ID=69277572

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910940869.7A Active CN110753040B (en) 2019-09-30 2019-09-30 Request processing method and device

Country Status (1)

Country Link
CN (1) CN110753040B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111835770B (en) * 2020-07-14 2021-01-29 全时云商务服务股份有限公司 Data processing method, device, server and storage medium
CN112422411A (en) * 2020-11-09 2021-02-26 天津卓越信通科技有限公司 Message distribution mechanism based on large-scale communication system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6128653A (en) * 1997-03-17 2000-10-03 Microsoft Corporation Method and apparatus for communication media commands and media data using the HTTP protocol
US8141100B2 (en) * 2006-12-20 2012-03-20 International Business Machines Corporation Identifying attribute propagation for multi-tier processing
US8799378B2 (en) * 2010-12-17 2014-08-05 Microsoft Corporation Non-greedy consumption by execution blocks in dataflow networks
CN108540333A (en) * 2017-03-02 2018-09-14 中兴通讯股份有限公司 The method of measurement network side handling capacity, home gateway, apparatus and system
CN107317816B (en) * 2017-07-05 2020-06-12 北京信息职业技术学院 Network access control method based on client application program authentication

Also Published As

Publication number Publication date
CN110753040A (en) 2020-02-04

Similar Documents

Publication Publication Date Title
CN107832100B (en) APK plug-in loading method and terminal thereof
CN109710317B (en) System starting method and device, electronic equipment and storage medium
CN107493180B (en) Upgrading method and device of virtual switch
CN110753040B (en) Request processing method and device
JP2021524104A (en) Master / Standby Container System Switching
CN110704161A (en) Virtual machine creation method and device and computer equipment
CN112860322B (en) Operating system switching method, device, equipment and storage medium
CN103888491A (en) Diskless workstation start system and method
CN106997313B (en) Signal processing method and system of application program and terminal equipment
JP4322240B2 (en) Reboot method, system and program
EP2835737A1 (en) Data terminal running mode switching method, device, and data terminal
CN111475435A (en) Storage medium sharing method and device, electronic equipment and storage medium
US20220374256A1 (en) Information processing system, information processing apparatus, method of controlling the same, and storage medium
KR20100050098A (en) Image processing apparatus and control method thereof
CN115268950A (en) Mirror image file importing method and device
WO2023279875A1 (en) Bootloader startup procedure monitoring method and apparatus, embedded device, and storage medium
US10257037B2 (en) Method and device for implementing seamless switching between northbound Corba interface specifications
CN108304200B (en) Method and device for upgrading driving program and electronic equipment
WO2017096889A1 (en) Method and device for upgrading and downgrading system
CN110704160B (en) Dual-computer hot standby test method and device
CN112559565A (en) Abnormity detection method, system and device
CN112463228A (en) Storage pool hybrid deployment method and device
CN111405313A (en) Method and system for storing streaming media data
CN111381942A (en) Method and device for realizing APP background resident
US8799616B2 (en) Method and system for preferred CPU binding on virtual partitions

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
CP02 Change in the address of a patent holder
CP02 Change in the address of a patent holder

Address after: 610041 nine Xing Xing Road 16, hi tech Zone, Sichuan, Chengdu

Patentee after: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd.

Address before: 610041 15-24 floor, 1 1 Tianfu street, Chengdu high tech Zone, Sichuan

Patentee before: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd.