CN106970878B - A kind of debugging event monitoring method and debugging event monitoring system - Google Patents

A kind of debugging event monitoring method and debugging event monitoring system Download PDF

Info

Publication number
CN106970878B
CN106970878B CN201710187477.9A CN201710187477A CN106970878B CN 106970878 B CN106970878 B CN 106970878B CN 201710187477 A CN201710187477 A CN 201710187477A CN 106970878 B CN106970878 B CN 106970878B
Authority
CN
China
Prior art keywords
terminal
debugging
data
debugging event
monitoring
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
CN201710187477.9A
Other languages
Chinese (zh)
Other versions
CN106970878A (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.)
Beijing Senseshield Technology Co Ltd
Original Assignee
Beijing Senseshield 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 Beijing Senseshield Technology Co Ltd filed Critical Beijing Senseshield Technology Co Ltd
Priority to CN201710187477.9A priority Critical patent/CN106970878B/en
Publication of CN106970878A publication Critical patent/CN106970878A/en
Application granted granted Critical
Publication of CN106970878B publication Critical patent/CN106970878B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/3644Software debugging by instrumenting at runtime
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services

Abstract

The present invention provides a kind of debugging event monitoring method, comprising: during connection exception occurs between first terminal and second terminal or disconnects, monitors the debugging event on first terminal and stores monitoring information;When restoring normal connection between first terminal and second terminal, second terminal is sent for the data including the monitoring information by first terminal.The invention also discloses a kind of debugging event monitoring systems.Debugging event monitoring method and debugging event monitoring system through the invention can monitor the debugging event occurred during first terminal connect exception with second terminal or disconnects, and implement respective handling to the first terminal that debugging event occurs.

Description

A kind of debugging event monitoring method and debugging event monitoring system
Technical field
The present invention relates to information protection field more particularly to a kind of debugging event monitoring method and debugging event monitoring systems System.
Background technique
As computer technology is universal and applies, computer software is developed rapidly with hardware industry.Utilize computer When technology communicates, attacker can be by utilizing the conversed analysis skills such as static disassembly tool or Dynamic Debugging Tool Art carries out analysis to communication protocol and cracks, to be distorted communication protocol to obtain unlawful interests.
Conversed analysis technology includes two parts of dis-assembling technology and inverse compiling technique.
Dis-assembling technology is that executable binary machine code dis-assembling is become substantially readable assembly language program(me) generation The method of code, generally comprises static disassembly technology and dynamic dis-assembling technology.Static disassembly is that binary code is primary Property be all translated as assembly code, when using the technology, handle the time-consuming of binary file with the size of binary file at just Than.Dynamic dis-assembling is the binary program that disassembler is loaded by analyzing, and captures operation characteristic instruction, is translated into Readable assembly code.
It is readable stronger higher-level language code that inverse compiling technique, which is the further decompiling of assembler,.The prior art In, tamper-resistance techniques and anti-debug technology are generallyd use to resist illegal use.Tamper-resistance techniques are to prevent from being maliciously tampered, If it find that being maliciously tampered, then executing corresponding punitive measures.Anti-debug is that debugging software is detected or confused, and is made Debugging software analysis mistake is not normally functioning.
In the prior art, there are this problems: since communication abnormality or disconnection occurring between request end and requested end When, the behaviors such as local debugging occur for request end, and when request end communicates again with requested end, requested end is still Meeting normal response, requested end can not punish request end at this time.
Summary of the invention
The present invention provides a kind of methods for debugging event monitoring, and the behaviors such as local debugging can be carried out to request end and are carried out Monitoring, and punitive measures is implemented according to debugging behavior.
To solve the above-mentioned problems, the present invention provides a kind of debugging event monitoring methods, comprising steps of
During connection exception occurs between first terminal and second terminal or disconnects, the tune on first terminal is monitored Examination event simultaneously stores monitoring information;
It will include the monitoring information by first terminal when restoring normal connection between first terminal and second terminal Data be sent to second terminal.
Preferably, whether debugging software is run according to first terminal to determine whether debugging event occurs.
Preferably, whether request to execute specific operation relevant to debugging according to first terminal or be requested according to first terminal The interval time of the specific operation is executed to determine whether debugging event occurs.
Preferably, second terminal believes the monitoring in the data after the first terminal reception data Breath is checked.
Preferably, second terminal is that first terminal executes predetermined measures when debugging event has occurred in inspection result.
Preferably, second terminal carries out the validity of the data after receiving the data from the first terminal It checks.
Preferably, the second terminal by the signing messages for generating time and/or the data to the data into Row checks the validity to determine the data.
Preferably, the content of the monitoring information includes about whether identification information, the debugging process that debugging event occurs The IP information of information, debug time and/or first terminal.
Preferably, the predetermined measures include implementing locking to first terminal or refusing to provide first terminal to first terminal Required data or information.
The invention also discloses a kind of debugging event monitoring system, including monitoring device and second terminal, the monitoring dress It sets and is connected to first terminal or is mounted in first terminal, the first terminal includes first communication module, the second terminal Including state verification module and second communication module;
The monitoring device is configured to, and connection exception occurs between first communication module and second communication module or disconnects During connection, monitors the debugging event on first terminal and store monitoring information;
The first communication module or the monitoring device are configured to, when between first communication module and second communication module When restoring normal connection, the second communication module is sent by the data including the monitoring information;
The second communication module is configured to receive the data;
The state verification module is configured to check the monitoring information in the data.
Preferably, second terminal further includes execution module, be configured to be in the inspection result of the state verification module First terminal executes predetermined measures when debugging event has occurred.
Preferably, the state verification module is further configured to check the validity of the data.
Preferably, the state verification module is configured to the signature for generating time and/or the data to the data Information is checked the validity to determine the data.
Preferably, the monitoring device is configured to, whether debugging software is run according to the first terminal to determine whether Debugging event occurs.
Preferably, whether the monitoring device is configured to, requested to execute specific behaviour relevant to debugging according to first terminal Make or the interval time of the specific operation is executed according to first terminal request to determine whether debugging event occurs.
Compared with prior art, the beneficial effects of the present invention are: can monitor first terminal connect with second terminal it is different The debugging event often or during disconnecting occurred, and punitive measures is implemented to the first terminal that debugging event occurs.
Detailed description of the invention
Fig. 1 is the schematic flow chart of the debugging event monitoring method of the embodiment of the present invention;
Fig. 2 is the schematic block diagram of the debugging event monitoring system of the embodiment of the present invention;
Fig. 3 is the schematic block diagram of the debugging event monitoring system of another embodiment of the present invention.
Specific embodiment
Present invention is further described in detail in the following with reference to the drawings and specific embodiments, but not as to limit of the invention It is fixed.
Fig. 1 shows the schematic flow chart of debugging event monitoring method of the invention.As shown in Figure 1, tune of the invention Event monitoring method is tried, is included the following steps:
S1 is monitored on first terminal during connection exception occurs between first terminal and second terminal or disconnects Debugging event and store monitoring information;
S2 will include monitoring information by first terminal when restoring normal connection between first terminal and second terminal Data be sent to second terminal.
By using the debugging event monitoring method of the embodiment of the present invention, when the user of first terminal is in first terminal and Data or association during connection exception occurs between two terminals or disconnects, by the interaction in first terminal analysis unilateral side View, so that the tune on first terminal can be monitored when gradually detecting the data interactive mode between first terminal and second terminal Examination event simultaneously stores monitoring information, when restoring normal connection between first terminal and second terminal, second terminal can be made to obtain Take the monitoring information.
The embodiment of the present invention efficiently solves the first terminal in the prior art that is unable to monitor and connect exception with second terminal Or during disconnecting the debugging event occurred on first terminal the problem of.
In embodiments of the present invention, it during first terminal keeps normally connecting with second terminal, also can be monitored in real time Debugging event on first terminal simultaneously stores monitoring information, then periodically or non-periodically sends second terminal for monitoring information.
In an embodiment of the invention, in S2, when restoring normal connection between first terminal and second terminal, can lead to It crosses first terminal and monitoring information is individually sent to second terminal, can also be believed monitoring information and business by first terminal Breath transmits second terminal together.
It in an alternative embodiment of the invention,, can be with when restoring normal connection between first terminal and second terminal in S2 Second terminal is not sent data to by first terminal, but data are passed through into monitoring debugging event or the dress of storage monitoring information It sets and is sent directly to second terminal.
In one embodiment of the invention, in S1, connection exception or the company of disconnection occur between first terminal and second terminal During connecing, debugging event whether occurs on monitoring first terminal can judge according to whether first terminal runs debugging software. For example, the identification information of some common debugging softwares can be prestored, by will run on the identification information and first terminal The identification information of software is compared to determine whether debugging event has occurred.
In another embodiment, in S1, it is abnormal or disconnected that connection occurs between first terminal and second terminal During opening connection, monitor whether occur whether debugging event can request to execute and debugging phase according to first terminal on first terminal The specific operation of pass requests the interval time for executing specific operation to judge according to first terminal.For example, can prestore The value range of common debugging operations instruction or specific operating instructions and its execution interval, by will be instructed performed by first terminal It compares with the instruction prestored, or by determining that whether first terminal executes the time interval of specific instruction in the value range prestored Within judge that debugging event whether has occurred on first terminal.
In further embodiment of the present invention, second terminal believes the monitoring in data after first terminal reception data Breath is checked.When individually sending monitoring information, second terminal is checked monitoring information not only include believing monitoring The content of breath is checked, further includes checking the validity of monitoring information.It include that monitoring information and business are believed when sending When the data packet of breath, only the content of monitoring information can be checked.
In embodiments of the present invention, second terminal is to execute to make a reservation for when debugging event has occurred in first terminal in inspection result Measure.Therefore, even if being deposited on first terminal during connection exception occurs between first terminal and second terminal or disconnects In debugging event, second terminal also can execute predetermined measures to first terminal.That is, second terminal can be directed to always The behavior that debugging event occurs for first terminal executes predetermined measures, which is likely to be delayed execution.
In various embodiments of the present invention, the predetermined measures that second terminal executes first terminal may include to first terminal Implement locking or refuses to provide data or information required by first terminal to first terminal.The predetermined measures can be according to monitoring The difference of information and it is different, that is, if showing that first terminal debugs the relevant information of A business in monitoring information, Then can choose only refusal provides A business relevant information, and other business unrelated with A business can be provided to first terminal Business information.
In an embodiment of the invention, second terminal is after receiving data from first terminal, to the validity of data into Row checks.Wherein, data can be the data including monitoring information and business information.Believe when second terminal is received including monitoring The data packet with business information is ceased, second terminal can check the validity of data entirety, can also be to monitoring information Validity check is carried out respectively with business information.
In embodiments of the present invention, second terminal can by data generate the time, data signing messages or this The two is checked the validity to determine data.Second terminal can be after determining the validity of data, then in data Appearance is checked.For example, after the monitoring information for determining first terminal is effective, then the content of the monitoring information is checked, To ensure information security, and determine information from monitored first terminal.
In embodiments of the present invention, the content of monitoring information may include about whether the mark letter that debugging event occurs The IP information of breath, debugging process information, debug time and/or first terminal.Second terminal can be according to the content of monitoring information Reservation measure is executed to first terminal, for example, when determining that debugging event, second terminal repeatedly occur for first terminal according to IP information The first terminal can be locked, makes first terminal that can not carry out data interaction with second terminal.Furthermore it is possible to pass through first terminal IP information realize locating and tracking, event can also be debugged according to debugging process information tracing.In addition, second terminal can be with Store predetermined measures relevant information corresponding with the content of monitoring information.
Fig. 2 is the schematic block diagram of the debugging event monitoring system of the embodiment of the present invention.
As shown in Fig. 2, debugging event monitoring system of the invention, including monitoring device 1 and second terminal 2, monitoring device 1 It is connected to first terminal 3 or is mounted in first terminal 3, first terminal 3 includes first communication module 4, and second terminal 2 includes shape State authentication module 5 and second communication module 6.
Monitoring device 1 is configured to that connection exception or the company of disconnection occur between first communication module 4 and second communication module 6 During connecing, monitors the debugging event on first terminal 3 and store monitoring information.
First communication module 4 is configurable to when the normal connection of recovery between first communication module 4 and second communication module 6 When, second communication module 6 is sent by the data including monitoring information.First communication module 4 can individually send out monitoring information It is sent to the second communication module 6 of second terminal 2, monitoring information and business information can also be transmitted together to second eventually End 2.
During the first communication module 4 of first terminal 3 keeps normally connecting with the second communication module 6 of second terminal 2, By the debugging event on 1 real-time monitoring first terminal 3 of monitoring device and it can be sent to second terminal 2, can also be filled by monitoring It sets 1 and first stores monitoring information when monitoring debugging event, then periodically or non-periodically send second terminal for monitoring information 2。
In some embodiments of the invention, monitoring device 1 has communication function, can will directly be monitored by monitoring device 1 Information is sent to second communication module 6.
In embodiments of the present invention, monitoring device 1 whether debugging software can be run according to first terminal 3 to determine whether Debugging event occurs, or whether can also request to execute relevant to debugging specific operation according to first terminal 3 or according to the One terminal 3 requests to execute the interval time of specific operation to determine whether debugging event occurs.
Second communication module 6 is configured to receive from first communication module 4 or the monitoring device 1 for having communication function including prison The data of measurement information.
State verification module 5 is configured to check the monitoring information in data.
In the embodiment of the present invention, state verification module 5 can be further configured to the number received to second communication module 6 According to validity checked that the data that second communication module 6 receives can be the number including monitoring information and business information According to the data for either only including monitoring information.State verification module 5 is configurable to examine the validity of data entirety It looks into, validity check can also be carried out respectively to monitoring information and business information.State verification module 5 can be pair with concrete configuration The generation time of data and/or the signing messages of data are checked the validity to determine data.
By using the debugging event monitoring system of the embodiment of the present invention, when first terminal 3 user first terminal 3 with Connection exception occurs between second terminal 2 or during disconnecting, by analyzed in first terminal 3 unilateral interaction data or Agreement, to can be supervised by monitoring device 1 when gradually detecting the data interactive mode between first terminal 3 and second terminal 2 The debugging event surveyed on first terminal 3 simultaneously stores monitoring information, when restoring normal connection between first terminal 3 and second terminal 2 When, the monitoring information can be sent to second terminal 2 by monitoring device 1 or first terminal 3.
Using the system above of the embodiment of the present invention, it can effectively detect whether first terminal 3 has occurred local debugging Event, and corresponding measure can be executed restoring the first time after connection with second terminal 2, having prevents from distorting and accurately punish The advantages of penalizing.
In embodiments of the present invention, first terminal 3 can be the PC machine as client, be also possible to secure hardware The PC machine of equipment, second terminal 2 can be the server as server-side, for example, Cloud Server.
Fig. 3 is the schematic block diagram of the debugging event monitoring system of another embodiment of the present invention.
As shown in figure 3, second terminal 2 further includes execution module 7 in the present embodiment, it is configured in state verification module 5 Inspection result be that first terminal 3 executes predetermined measures when debugging event has occurred.For example, when monitoring device 1 is believed according to monitoring IP information in breath determines that more than 3 generation debugging events of first terminal, execution module 7 can lock the first terminal 3, pass through example As the mode of message of the shielding from the IP address makes first terminal 3 that can not carry out data interaction with second terminal 2.
Therefore, even if occurring to connect exception between second communication module 6 in first communication module 4 or disconnecting the phase Between, there are when debugging event on first terminal 3, second terminal 2 also be can be realized to the execution predetermined measures of first terminal 3.Also It is to say, second terminal 2 can execute predetermined measures for the behavior for the debugging event that first terminal 3 occurs always, this makes a reservation for arrange It applies and is likely to be delay.
Above embodiments are only exemplary embodiment of the present invention, are not used in the limitation present invention, protection scope of the present invention It is defined by the claims.Those skilled in the art can within the spirit and scope of the present invention make respectively the present invention Kind modification or equivalent replacement, this modification or equivalent replacement also should be regarded as being within the scope of the present invention.

Claims (11)

1. a kind of debugging event monitoring method, which is characterized in that comprising steps of
During connection exception occurs between first terminal and second terminal or disconnects, the debugging thing on first terminal is monitored Part simultaneously stores monitoring information;
When restoring normal connection between first terminal and second terminal, second is sent by the data including the monitoring information Terminal,
The second terminal examines the monitoring information in the data after the first terminal reception data It looks into, also, predetermined measures is executed based on inspection result,
Second terminal is that first terminal executes predetermined measures when debugging event has occurred in inspection result,
The predetermined measures include implementing locking to first terminal or refusing to provide number required by first terminal to first terminal According to or information.
2. debugging event monitoring method according to claim 1, which is characterized in that whether run debugging according to first terminal Software is to determine whether occur debugging event.
3. debugging event monitoring method according to claim 1, which is characterized in that whether request to execute according to first terminal Specific operation relevant to debugging executes the interval time of the specific operation to determine whether hair according to first terminal request Raw debugging event.
4. debugging event monitoring method according to claim 1, which is characterized in that second terminal is from the first terminal After receiving the data, the validity of the data is checked.
5. debugging event monitoring method according to claim 4, which is characterized in that the second terminal passes through to the number According to generation time and/or the signing messages of the data checked the validity to determine the data.
6. debugging event monitoring method according to any one of claim 1 to 3, which is characterized in that the monitoring information Content include about whether occur debugging event identification information, debugging process information, debug time and/or first terminal IP information.
7. a kind of debugging event monitoring system, which is characterized in that including monitoring device and second terminal, the monitoring device connection It to first terminal or is mounted in first terminal, the first terminal includes first communication module, and the second terminal includes shape State authentication module and second communication module;
The monitoring device is configured to, and connection exception occurs between first communication module and second communication module or disconnects Period monitors the debugging event on first terminal and stores monitoring information;
The first communication module or the monitoring device are configured to, when restoring between first communication module and second communication module When normal connection, the second communication module is sent by the data including the monitoring information;
The second communication module is configured to receive the data;
The state verification module is configured to check the monitoring information in the data,
Second terminal further includes execution module, and the inspection result for being configured to the state verification module executes predetermined arrange It applies,
Execution module is configured in the inspection result of the state verification module be execution when debugging event has occurred in first terminal Predetermined measures,
The predetermined measures include implementing locking to first terminal or refusing to provide number required by first terminal to first terminal According to or information.
8. debugging event monitoring system according to claim 7, which is characterized in that the state verification module is further matched It is set to and the validity of the data is checked.
9. debugging event monitoring system according to claim 8, which is characterized in that the state verification module is configured to pair The generation time of the data and/or the signing messages of the data are checked the validity to determine the data.
10. debugging event monitoring system according to claim 7, which is characterized in that the monitoring device is configured to, according to Whether the first terminal runs debugging software to determine whether debugging event occurs.
11. debugging event monitoring system according to claim 7, which is characterized in that the monitoring device is configured to, according to Whether first terminal requests to execute specific operation relevant to debugging or executes the specific operation according to first terminal request Interval time is to determine whether occur debugging event.
CN201710187477.9A 2017-03-27 2017-03-27 A kind of debugging event monitoring method and debugging event monitoring system Active CN106970878B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710187477.9A CN106970878B (en) 2017-03-27 2017-03-27 A kind of debugging event monitoring method and debugging event monitoring system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710187477.9A CN106970878B (en) 2017-03-27 2017-03-27 A kind of debugging event monitoring method and debugging event monitoring system

Publications (2)

Publication Number Publication Date
CN106970878A CN106970878A (en) 2017-07-21
CN106970878B true CN106970878B (en) 2019-11-12

Family

ID=59335411

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710187477.9A Active CN106970878B (en) 2017-03-27 2017-03-27 A kind of debugging event monitoring method and debugging event monitoring system

Country Status (1)

Country Link
CN (1) CN106970878B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108549602B (en) * 2018-03-30 2022-03-08 深圳市江波龙电子股份有限公司 Software debugging method

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7660412B1 (en) * 2005-12-09 2010-02-09 Trend Micro Incorporated Generation of debug information for debugging a network security appliance
CN102713858B (en) * 2011-01-12 2015-11-25 丰田自动车株式会社 The on-line debugging system of signal conditioning package and on-line debugging method
CN104503907B (en) * 2014-12-15 2017-08-29 深圳市盛弘电气股份有限公司 A kind of application program remote adjustment method and system based on Linux system
CN106021024B (en) * 2016-05-20 2019-07-19 Oppo广东移动通信有限公司 A kind of user terminal stops response reminding method and user terminal

Also Published As

Publication number Publication date
CN106970878A (en) 2017-07-21

Similar Documents

Publication Publication Date Title
US10594589B2 (en) Systems and methods for automated determination of network device transiting data attributes
CN107294808B (en) Interface test method, device and system
US9639456B2 (en) Network-based testing service and method of testing in a network
CN111984975B (en) Vulnerability attack detection system, method and medium based on mimicry defense mechanism
US20060064598A1 (en) Illegal access preventing program, apparatus, and method
US10574671B2 (en) Method for monitoring security in an automation network, and automation network
CN108347361B (en) Application program testing method and device, computer equipment and storage medium
CN106998323B (en) Application layer network attack simulation method, device and system
CN110943984B (en) Asset safety protection method and device
CN114301673A (en) Vulnerability detection method and device, electronic equipment and storage medium
CN107168844B (en) Performance monitoring method and device
CN113468075A (en) Security testing method and system for server-side software
CN106970878B (en) A kind of debugging event monitoring method and debugging event monitoring system
CN112116997B (en) Remote diagnosis method, device and system, electronic equipment and computer readable storage medium
CN117061384A (en) Fuzzy test method, device, equipment and medium
US11108800B1 (en) Penetration test monitoring server and system
EP2911362A2 (en) Method and system for detecting intrusion in networks and systems based on business-process specification
Kenchaiah TRACEABILITY AND TROUBLESHOOTING IN WIRELESS CLUSTER DEPLOYMENTS USING PROVENANCE METADATA AND HYPER LEDGER
Marhefka et al. Dfuzzer: A D-bus service fuzzing tool
CN110225543B (en) Mobile terminal software quality situation perception system and method based on network request data
CN115827395A (en) Office software exception handling method and device
JP2024000043A (en) Inspection apparatus, inspection program, and inspection method
WO2013065087A1 (en) Diagnostic device
WO2015015572A1 (en) Data processing device, data communication device, communication system, data processing method, data communication method, and program
CN117651010A (en) Asset detection method and system based on 4G module

Legal Events

Date Code Title Description
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
CP01 Change in the name or title of a patent holder
CP01 Change in the name or title of a patent holder

Address after: 100193 5th floor 510, No. 5 Building, East Yard, No. 10 Wangdong Road, Northwest Haidian District, Beijing

Patentee after: Beijing Shendun Technology Co.,Ltd.

Address before: 100193 5th floor 510, No. 5 Building, East Yard, No. 10 Wangdong Road, Northwest Haidian District, Beijing

Patentee before: BEIJING SENSESHIELD TECHNOLOGY Co.,Ltd.