CN103747433B - Method for realizing root request management through manufacturer server and mobile terminal - Google Patents
Method for realizing root request management through manufacturer server and mobile terminal Download PDFInfo
- Publication number
- CN103747433B CN103747433B CN201310630685.3A CN201310630685A CN103747433B CN 103747433 B CN103747433 B CN 103747433B CN 201310630685 A CN201310630685 A CN 201310630685A CN 103747433 B CN103747433 B CN 103747433B
- Authority
- CN
- China
- Prior art keywords
- mobile terminal
- root authority
- root
- manufacturer server
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The invention provides a method and a mobile terminal for realizing root request management through a manufacturer server, wherein the mobile terminal pushes an SU program to a system/bin directory after authorizing a user root authority through the manufacturer server, and is provided with an improved version of Superuser. The server feeds back evaluation information of the security of the authority lifting request to the mobile terminal for reference when the terminal user judges; and the information agreeing to the lifting authority is sent to the server for final determination, and the mobile terminal executes a corresponding authority lifting command after obtaining the fed back determination information. The method and the system can not only enable the user to obtain the opening of the root authority, but also enable the root environment of the user to be controlled and effectively reminded by a manufacturer server.
Description
Technical Field
The invention relates to the field of mobile communication equipment, in particular to a method and a mobile terminal for realizing root request management through a manufacturer server.
Background
Google's android system administrator user is called root, which has the most up right of the whole system, can access and modify almost all files in your mobile phone, and only the root has the highest level of management authority. The process of root mobile phone is the process of obtaining the highest usage authority of the mobile phone. Meanwhile, in order to prevent bad software from obtaining the authority of the root user, when the user is in the root process, a program is loaded to the system to serve as an operation prompt, and the user determines whether the highest authority is given or not. The name of this program is super. When some program execution su instructions want to obtain the highest authority of the system, the Superuser will automatically start, intercept the action and make a query, when the user thinks the program can be safely used, we choose to allow, otherwise, the program can be prohibited from obtaining the highest authority.
Generally, a mobile phone user acquires a root authority of the mobile phone by a certain method, and the behavior is a one-way behavior of the user and is not interfered or assisted by the outside. But the method has the disadvantages that once the root authority which is released cannot be effectively controlled, unnecessary damage can be caused to the mobile phone system or the mobile phone system is attacked by rogue software, and the user at this time can be helpless, and finally, the method still requires help for the mobile phone manufacturer.
There are two technical approaches:
1. the user can acquire the root authority, one is that the user can acquire the root password by himself and then upgrade the root authority through one-key root software, and the principle of the one-key root software is that the SU program is pushed to the system/bin, and the Super program is installed in the system to manage the root authority.
2. And after the authentication is carried out by the manufacturer server, an SU program push is issued to the system/bin, and Superuser.
The principle of the two methods is the same, but the Superuser apk is a single-machine version software, and can only interact with users, and once the software makes a wrong judgment, unnecessary damage is caused to the software system.
The second method described above, after granting the root right, the vendor server almost loses control of the end user, and once the user encounters unnecessary system damage or rogue software attack because of the opening of the root right, the vendor server cannot provide any help.
Disclosure of Invention
The invention provides a method for realizing root request management through a manufacturer server, aiming at enabling the manufacturer server to be involved in the root authority management of a mobile phone, so that a user can be opened with the root authority, and the root environment of the user can be managed and effectively reminded by the manufacturer server.
The first technical scheme of the invention is to provide a method for realizing root request management through a manufacturer server, which comprises the following steps:
s1, the user of the mobile terminal obtains root authority promotion authorized by a manufacturer, and a root authority management module is arranged in the mobile terminal; the information interaction between the mobile terminal and a manufacturer server is realized through a sending component and a receiving component contained in the root authority management module;
s2, when prompting that the APP program requests to be promoted to the root authority, a sending component of the root authority management module on the mobile terminal sends a request message to a manufacturer server through a network;
s3, the manufacturer server receives and analyzes the request message, and establishes a record file special for the mobile terminal according to the unique identification information of the mobile terminal contained in the request message, so as to manage all root authority requests and information of corresponding results in the mobile terminal through the record file;
s4, the manufacturer server evaluates the safety of the APP program which sends out the request, packages the conclusion of the safety evaluation and the introduction of the APP program into a message and sends the message back to the root authority management module on the mobile terminal through the network;
s5, the mobile terminal analyzes the message fed back by the manufacturer server through the receiving component of the root authority management module and then presents the analyzed message to the user, and prompts the mobile terminal user to confirm whether the APP program is approved to promote the root authority;
s6, the user confirms the information of agreeing to promote the root authority, the information is sent to a record file of a manufacturer server through a sending component of the root authority management module for archiving, and the APP program is added to a white list allowing the root authority to be promoted in the record file;
s7, the manufacturer server sends the successful archiving information to the root authority management module on the mobile terminal through the network, and the root authority management module executes the corresponding command to promote the root authority of the APP program.
Preferably, the root authority management module is Superuser. When the mobile terminal obtains root authority promotion authorized by a manufacturer and pushes the SU program to a system/app directory of the mobile terminal in step S1, installing advanced version Superuser.
Apk, a manufacturer's modified version of Superuser, further comprising:
the SuperUSRequestActivity component is used as the sending component, so that the mobile terminal can send information to the manufacturer server; and the number of the first and second groups,
the SuperuseAnaswerActivity component is used as the receiving component, so that the mobile terminal can receive and analyze the information fed back by the manufacturer server and display the information to the mobile terminal user.
Preferably, in step S2, when it is prompted that the APP requests to promote to the root right, the mobile terminal first checks whether the network is unblocked, and if not, prompts the user to open data traffic or wifi to start the network, so that the root right management module starts the sending component to send the request message to the vendor server after receiving the broadcast; if the network is not started, the root authority is prompted to be unsuccessfully promoted.
Preferably, the unique identification information of the mobile terminal in step S3 is the IMEI field of the mobile terminal.
Preferably, in step S3, the record file created by the vendor server for each mobile terminal is a sqlite database file.
Preferably, in step S4, the vendor server performs the security evaluation by parsing the process name of the APP program requested in the request message, and determining whether the APP program is security software by searching the rogue software library and the security software library.
Preferably, in step S6, if the user does not agree with the APP program to promote the root right after viewing the information fed back by the vendor server, the mobile terminal sends a message to the record file of the vendor server through the sending component to be archived, and adds the APP program to a blacklist that does not allow the root right to be promoted; and prompting that the root authority is unsuccessfully promoted in the mobile terminal, and executing corresponding operation to forbid the APP program to obtain the root authority.
The second technical scheme of the invention is to provide a mobile terminal for realizing root request management through a manufacturer server, wherein the mobile terminal comprises a root authority management module, and the root authority management module is arranged in the mobile terminal after the mobile terminal obtains the root authority of a user through the authorization of the manufacturer server;
the root authority management module further enables the mobile terminal and the manufacturer server to perform information interaction through a network through the following components:
a sending component that enables the mobile terminal to send the following information to the vendor server: the method comprises the steps that an APP program in the mobile terminal requests for information of APP permission improvement, and a mobile terminal user determines information of a root permission improvement request to be approved or not according to feedback of a manufacturer server;
a receiving component enabling the mobile terminal to receive and parse the following information fed back by the manufacturer server: the manufacturer server adds the detailed introduction and safety evaluation information of the APP program, and the manufacturer server adds the APP program into a white list or a black list of the root authority request according to the user decision;
and the root authority management module executes a command for promoting the root authority to the APP after receiving the confirmation message fed back by the manufacturer server and adding the APP to the white list.
Preferably, the manufacturer server establishes a corresponding record file according to the unique identification information of the mobile terminal, and archives and manages a white list and/or a black list of the root permission request through the record file.
Compared with the prior art, the method changes the original function of the Superuser, apk, sends the SuperUserActivities with the decisive management function to the manufacturer cloud server to execute filtering judgment, and changes the SuperUserRequestActivities which originally inquire the client into the SuperUserRequestActivities and the SuperUserAnswerActivities. The improved SuperuseRequestActivity is mainly characterized in that a terminal mobile phone sends a request to a manufacturer cloud server; the improved SuperuseAnaswervice is mainly used for receiving feedback of a manufacturer cloud server and displaying the feedback to an end user.
Therefore, the method for realizing root request management through the manufacturer server and the mobile terminal have the following advantages:
A. apk has the interactivity of communicating with the vendor server instead of a standalone version of the software.
B. The vendor server has the function of searching the rogue software library and the security software library;
C. the manufacturer server stores information of all root requests of the user, and once the mobile phone system has a fault caused by root authority, the manufacturer server also has a certain tracing direction for the manufacturer after sale.
D. The vendor server can provide the suggestion message to the terminal client instead of the terminal client to singly and blindly promote the root authority of the APP.
Drawings
FIG. 1 is a flowchart of a method for implementing root request management via a vendor server according to the present invention.
Detailed Description
The invention provides a method for realizing root request management through a manufacturer server and a mobile terminal.
In a preferred example, the root rights management module is a manufacturer improved version of super application package, where super request activity is set as a sending component and super answer activity is set as a receiving component.
Specifically, the mobile terminal authorizes the root authority of the user through a manufacturer server, pushes (pushes) an SU program to a mobile phone system/bin, installs an improved version of Superuser.apk of the manufacturer to the mobile terminal, the APK has the capability of interacting with a manufacturer cloud server, sends various requests for improving the root authority on the mobile phone to the manufacturer server, and the manufacturer server establishes a split qe database file or a recording file with other formats according to unique identification information (such as an IMEI number of the mobile terminal) of the mobile terminal so as to manage a white list and a black list of the root authority requests. The server evaluates the security of the request, feeds the security back to Superuser.apk of the mobile terminal through a network, receives and displays the security to the terminal user through SuperAnswerActivity, and finally judges the security by the terminal user; and returning the information agreeing to the permission to be promoted to the server through SuperUserRequestActivity, and finally executing a corresponding permission promotion command after the information that the server determines to be added into the white list is obtained.
As shown in fig. 1, a specific application example of the method of the present invention includes the following steps:
and S1, the end user obtains the root authority promotion allowed by the manufacturer through multiple paths, wherein the promotion action mainly comprises the steps of pushing the SU program to the mobile system/app and installing the manufacturer improved version Superuser.
S2, once APP (third party application) wants to upgrade to root authority, the Superuser.
In view of the fact that the method of the present invention needs to be implemented by means of multiple interactions between the terminal and the manufacturer server through the network, when the third party APP request root permission prompt is received in step S2, it is checked whether the network is unblocked first, and if not, the user is prompted to open data traffic or wifi to start the network.
S3, the manufacturer server receives and analyzes the message, and establishes a special sqlite database file according to the IMEI field in the message, thereby facilitating subsequent repeated application actions and centralized management.
S4, the cloud server analyzes the request APP process name in the message, judges whether the request APP process name is the security software by searching the rogue software library and the security software library, packages the detailed functions of the APP into a message, and sends the message back to Superuser.
And S5, starting Superuser Answervity by the Superuser on the terminal, analyzing the message fed back by the cloud server, presenting the analyzed message to the user, and popping up a prompt box to ensure that the terminal user confirms whether to promote the root authority.
S6, the SuperuseRequestActivity captures the confirmation message of the user again and sends the message to the manufacturer server for final archiving, and the APP is added to the white list.
And S7, after successful archiving, the manufacturer server sends a confirmation message to the Superuser.
Similarly, according to the information fed back by the manufacturer, if the user does not agree with the APP program to promote the root authority, the corresponding information can be sent to the server to be filed; and corresponding operation is executed in the mobile terminal to prompt that the root authority is unsuccessfully promoted.
While the present invention has been described in detail with reference to the preferred embodiments, it should be understood that the above description should not be taken as limiting the invention. Various modifications and alterations to this invention will become apparent to those skilled in the art upon reading the foregoing description. Accordingly, the scope of the invention should be determined from the following claims.
Claims (9)
1. A method for realizing root request management through a manufacturer server is characterized by comprising the following steps:
s1, the user of the mobile terminal obtains root authority promotion authorized by a manufacturer, and a root authority management module is arranged in the mobile terminal; the information interaction between the mobile terminal and a manufacturer server is realized through a sending component and a receiving component contained in the root authority management module;
s2, when prompting that the APP program requests to be promoted to the root authority, a sending component of the root authority management module on the mobile terminal sends a request message to a manufacturer server through a network;
s3, the manufacturer server receives and analyzes the request message, and establishes a record file special for the mobile terminal according to the unique identification information of the mobile terminal contained in the request message, so as to manage all root authority requests and information of corresponding results in the mobile terminal through the record file;
s4, the manufacturer server evaluates the safety of the APP program which sends out the request, packages the conclusion of the safety evaluation and the introduction of the APP program into a message and sends the message back to the root authority management module on the mobile terminal through the network;
s5, the mobile terminal analyzes the message fed back by the manufacturer server through the receiving component of the root authority management module and then presents the analyzed message to the user, and prompts the mobile terminal user to confirm whether the APP program is approved to promote the root authority;
s6, the user confirms the information of agreeing to promote the root authority, the information is sent to a record file of a manufacturer server through a sending component of the root authority management module for archiving, and the APP program is added to a white list allowing the root authority to be promoted in the record file;
s7, the manufacturer server sends the successful archiving information to the root authority management module on the mobile terminal through the network, and the root authority management module executes the corresponding command to promote the root authority of the APP program.
2. The method of claim 1,
the root authority management module is Superuser. When the mobile terminal obtains root authority promotion authorized by a manufacturer and pushes the SU program to a system/app directory of the mobile terminal in step S1, installing advanced version Superuser.
Apk, a manufacturer's modified version of Superuser, further comprising:
the SuperUSRequestActivity component is used as the sending component, so that the mobile terminal can send information to the manufacturer server; and the number of the first and second groups,
the SuperuseAnaswerActivity component is used as the receiving component, so that the mobile terminal can receive and analyze the information fed back by the manufacturer server and display the information to the mobile terminal user.
3. The method of claim 1 or 2,
in step S2, when it is prompted that the APP requests to promote to the root right, the mobile terminal first checks whether the network is unblocked, and if not, prompts the user to open data traffic or wifi to start the network, so that the root right management module starts the sending component to send the request message to the vendor server after receiving the broadcast; if the network is not started, the root authority is prompted to be unsuccessfully promoted.
4. The method of claim 1,
the unique identification information of the mobile terminal in step S3 is the IMEI field of the mobile terminal.
5. The method of claim 1,
in step S3, the record file created by the vendor server for each mobile terminal is a sqlite database file.
6. The method of claim 1,
in step S4, the vendor server analyzes the process name of the APP program that is requested in the request message, and determines whether the APP program is security software by retrieving the rogue software library and the security software library.
7. The method of claim 1 or 2,
in step S6, if the user does not agree with the APP program to promote the root right after checking the information fed back by the vendor server, the mobile terminal sends a message to a record file of the vendor server through the sending component to be filed, and adds the APP program to a blacklist that does not allow the root right to be promoted; and prompting that the root authority is unsuccessfully promoted in the mobile terminal, and executing corresponding operation to forbid the APP program to obtain the root authority.
8. A mobile terminal for implementing root request management through a manufacturer server is characterized in that,
the mobile terminal comprises a root authority management module, and the root authority management module is arranged in the mobile terminal after the mobile terminal obtains the root authority of the user through the authorization of a manufacturer server;
the root authority management module further enables the mobile terminal and the manufacturer server to perform information interaction through a network through the following components:
a sending component that enables the mobile terminal to send the following information to the vendor server: the method comprises the steps that an APP program in the mobile terminal requests for information of APP permission improvement, and a mobile terminal user determines information of a root permission improvement request to be approved or not according to feedback of a manufacturer server;
a receiving component enabling the mobile terminal to receive and parse the following information fed back by the manufacturer server: the manufacturer server adds the detailed introduction and safety evaluation information of the APP program, and the manufacturer server adds the APP program into a white list or a black list of the root authority request according to the user decision;
and the root authority management module executes a command for promoting the root authority to the APP after receiving the confirmation message fed back by the manufacturer server and adding the APP to the white list.
9. The mobile terminal of claim 8,
and the manufacturer server establishes a corresponding record file according to the unique identification information of the mobile terminal, and archives and manages a white list and/or a black list of the root authority request through the record file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310630685.3A CN103747433B (en) | 2013-12-02 | 2013-12-02 | Method for realizing root request management through manufacturer server and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310630685.3A CN103747433B (en) | 2013-12-02 | 2013-12-02 | Method for realizing root request management through manufacturer server and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103747433A CN103747433A (en) | 2014-04-23 |
| CN103747433B true CN103747433B (en) | 2020-03-20 |
Family
ID=50504413
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310630685.3A Active CN103747433B (en) | 2013-12-02 | 2013-12-02 | Method for realizing root request management through manufacturer server and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103747433B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105095742A (en) * | 2014-05-15 | 2015-11-25 | 宇龙计算机通信科技(深圳)有限公司 | Root detection and recovery method for mobile terminal and mobile terminal |
| US9787685B2 (en) | 2014-06-24 | 2017-10-10 | Xiaomi Inc. | Methods, devices and systems for managing authority |
| CN104125335B (en) * | 2014-06-24 | 2017-08-25 | 小米科技有限责任公司 | Right management method, apparatus and system |
| CN104063303B (en) * | 2014-06-30 | 2019-07-16 | 上海斐讯数据通信技术有限公司 | A method of obtaining and discharge root authority |
| CN105243325A (en) * | 2015-09-29 | 2016-01-13 | 北京奇虎科技有限公司 | Method for residual process file in mobile terminal, mobile terminal and server |
| CN106169042A (en) * | 2016-06-30 | 2016-11-30 | 北京壹人壹本信息科技有限公司 | The method and device of administration authority |
| CN106529312B (en) * | 2016-10-25 | 2019-08-06 | Oppo广东移动通信有限公司 | A kind of authority control method of mobile terminal, device and mobile terminal |
| CN108134956B (en) * | 2016-12-01 | 2020-09-25 | 腾讯科技（深圳）有限公司 | Updating method, terminal and system for hard solution adaptive white list |
| CN108334788B (en) * | 2017-01-20 | 2023-01-06 | 腾讯科技（深圳）有限公司 | File tamper-proofing method and device |
| CN111062006B (en) * | 2018-10-17 | 2023-01-10 | 福建天泉教育科技有限公司 | Android system control method and terminal |
| CN113419880B (en) * | 2021-07-19 | 2024-04-09 | 北京百度网讯科技有限公司 | Cloud mobile phone root authority acquisition method, related device and computer program product |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102186167A (en) * | 2011-04-11 | 2011-09-14 | 中兴通讯股份有限公司 | Method and system for monitoring applications |
| CN102819715A (en) * | 2012-08-15 | 2012-12-12 | 腾讯科技（深圳）有限公司 | API (application programming interface) monitoring method and device |
| CN103065083A (en) * | 2013-01-31 | 2013-04-24 | 晨风云（北京）科技有限公司 | Method and system for monitoring application program interface of intelligent mobile terminal |
| CN103218564A (en) * | 2013-04-01 | 2013-07-24 | 广东欧珀移动通信有限公司 | Mobile terminal protection method and mobile terminal protection device |
-
2013
- 2013-12-02 CN CN201310630685.3A patent/CN103747433B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102186167A (en) * | 2011-04-11 | 2011-09-14 | 中兴通讯股份有限公司 | Method and system for monitoring applications |
| CN102819715A (en) * | 2012-08-15 | 2012-12-12 | 腾讯科技（深圳）有限公司 | API (application programming interface) monitoring method and device |
| CN103065083A (en) * | 2013-01-31 | 2013-04-24 | 晨风云（北京）科技有限公司 | Method and system for monitoring application program interface of intelligent mobile terminal |
| CN103218564A (en) * | 2013-04-01 | 2013-07-24 | 广东欧珀移动通信有限公司 | Mobile terminal protection method and mobile terminal protection device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103747433A (en) | 2014-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103747433B (en) | Method for realizing root request management through manufacturer server and mobile terminal | |
| US10972467B2 (en) | Certificate based profile confirmation | |
| US11295004B2 (en) | Unlock and recovery for encrypted devices | |
| WO2015184891A1 (en) | Security management and control method, apparatus, and system for android system | |
| EP2993603B1 (en) | Permission determining method and device for application program | |
| US9607156B2 (en) | System and method for patching a device through exploitation | |
| CN103179124A (en) | Method for certifying third-party application program, mobile terminal and cloud server | |
| CN111079091A (en) | Software security management method and device, terminal and server | |
| CN109863475A (en) | The upgrade method and relevant device of a kind of application in safety element | |
| CN111966422A (en) | Localized plug-in service method and device, electronic equipment and storage medium | |
| CN112749088A (en) | Application program detection method and device, electronic equipment and storage medium | |
| WO2023072817A1 (en) | Control of access to computing resources implemented in isolated environments | |
| CN108259163B (en) | Authorization method of terminal equipment | |
| CN112398787B (en) | Mailbox login verification method and device, computer equipment and storage medium | |
| CN111095206B (en) | Method for verifying medical application program, end user device and medical system | |
| CN110196741A (en) | Method for setting basic input/output system, terminal and computer storage medium | |
| WO2017220014A1 (en) | System permission management method and apparatus, and intelligent terminal | |
| CN106485104B (en) | Automatic restoration method, device and system for terminal security policy | |
| KR20150030047A (en) | Method and system for application authentication | |
| CN111814137A (en) | Operation and maintenance method and system of terminal and storage medium | |
| CN113297595A (en) | Method and device for processing right-offering, storage medium and electronic equipment | |
| KR101351243B1 (en) | Method and system for application authentication | |
| KR101420383B1 (en) | Method for managing secure access of mobile application | |
| CN116170808A (en) | Trusted security protection method and system for mobile terminal and electronic equipment | |
| CN115391783A (en) | Method and equipment for remotely starting computer by client and cloud desktop client |
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: 20201030 Address after: 318015 no.2-3167, zone a, Nonggang City, no.2388, Donghuan Avenue, Hongjia street, Jiaojiang District, Taizhou City, Zhejiang Province Patentee after: Taizhou Jiji Intellectual Property Operation Co.,Ltd. Address before: 201620 Shanghai city Songjiang District Guangfulin road 4855 Lane 20, No. 90 Patentee before: Phicomm (Shanghai) Co.,Ltd. |
|
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20140423 Assignee: Hangzhou Bolian Intelligent Technology Co.,Ltd. Assignor: Taizhou Jiji Intellectual Property Operation Co.,Ltd. Contract record no.: X2021330000763 Denomination of invention: A method of root request management through manufacturer server and mobile terminal Granted publication date: 20200320 License type: Common License Record date: 20211117 Application publication date: 20140423 Assignee: ZHEJIANG SUPCON TECHNOLOGY Co.,Ltd. Assignor: Taizhou Jiji Intellectual Property Operation Co.,Ltd. Contract record no.: X2021330000764 Denomination of invention: A method of root request management through manufacturer server and mobile terminal Granted publication date: 20200320 License type: Common License Record date: 20211117 |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230419 Address after: 300456 Tianjin Binhai New Area Tianjin Pilot Free Trade Zone (Central Business District) Baoyuan Building, No. 3699 Xinhua Road, Tianjin YO-16097 Patentee after: Tianjin Huizhi Network Technology Co.,Ltd. Address before: 318015 no.2-3167, area a, nonggangcheng, 2388 Donghuan Avenue, Hongjia street, Jiaojiang District, Taizhou City, Zhejiang Province Patentee before: Taizhou Jiji Intellectual Property Operation Co.,Ltd. |