WO2013097673A1 - 数据调用方法和装置 - Google Patents
数据调用方法和装置 Download PDFInfo
- Publication number
- WO2013097673A1 WO2013097673A1 PCT/CN2012/087296 CN2012087296W WO2013097673A1 WO 2013097673 A1 WO2013097673 A1 WO 2013097673A1 CN 2012087296 W CN2012087296 W CN 2012087296W WO 2013097673 A1 WO2013097673 A1 WO 2013097673A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- name
- mobile terminal
- user
- data
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
- H04W8/205—Transfer to or from user equipment or user record carrier
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a data calling method for private data.
- mobile terminals such as mobile phones have become a necessity for people's daily lives.
- mobile terminal manufacturers and mobile service providers have also provided more and more application services.
- application services collect user privacy information without the user's knowledge, and threaten users' security.
- mobile terminals which have more and more existing applications and functions, because there are many users' private data, they need to be protected.
- the operating system has certain requirements for each APP (application). If an application needs to read the user's private data (such as address book, SMS, etc.), it will pop up a prompt to inform the user that the application needs to use the user's private data when the application is installed. Then you can install the application. However, after installation, the application will not be interrupted at any time during the use of private data, nor will the user be prompted to inform the user that the private data is being used.
- APP application
- the present invention has been made in order to provide a data calling method and apparatus for overcoming the above problems or at least partially solving or slowing down the above-mentioned problems.
- a data invocation method comprising: receiving a service request requesting to use a first service, the first service requiring use of privacy data of a mobile terminal, wherein the service request includes the first a service name of the service; sending, according to the service name, a prompt to the user of the mobile terminal whether to allow the first service to use the private data; determining, according to the input of the user, allowing the requested first The service uses the private data; determines a jump service name corresponding to the service name, and invokes the first service according to the jump service name, where the jump service name is the mobile terminal each time service 5 list maintained by the system in the first service of the service name is the name of the modified service start, the service name is different from the jump list of services in addition to the other of said first and services The service name of the service.
- a data call apparatus comprising: a receiving module for receiving a request to use the service of a first service request of the first service requires the use of 5 private data of the mobile terminal, the service request
- the service module includes the service name of the first service
- the prompting module is configured to send, according to the service name, a prompt to the user of the mobile terminal whether the first service uses the private data, and a confirmation module, Determining, according to the input of the user, that the requested first service is allowed to use the private data
- the calling module configured to: after the confirming module determines to allow the requested first service to use the private data, Determining a jump service name corresponding to the service name, and calling the first service according to the jump service name 5 , wherein the jump service name is 5 pairs of systems each time the mobile terminal starts The service name of the first service in the maintained service list is modified, and the jump service name is different from the service list except the first service Other service name
- a computer program comprising computer readable code 5, when said computer readable code is run on a server, causing said server to perform according to any of claims 1-9 The data invocation method described in the item.
- a computer readable medium storing the computer program according to claim 18 is provided.
- the beneficial effects of the invention are:
- a mobile terminal by modifying the private data service (a first service) name service, upon receiving a request to use the service (a first service) 5 to ask the user whether to allow the use of private data of the mobile terminal, the user is charged in the In the case of the case, the service (first service) is called by the modified service name (jump service name).
- the service (first service) is called by the modified service name (jump service name).
- jump service name the modified service name
- each access and use of the mobile terminal's private data by the application can be known by the user, and then the user decides whether to allow the application to use the private data, thereby solving the problem that the user's private data cannot be effectively protected in the prior art.
- the problem that the user uses the application security is not high, and the security of the privacy data of the mobile terminal is improved.
- FIG. 1 is a flow chart of steps of a data invoking method according to Embodiment 1 of the present application
- FIG. 2 is a flow chart of steps of a data invoking method according to Embodiment 2 of the present application
- FIG. 3 is a flowchart according to Embodiment 3 of the present application
- FIG. 4 is a block diagram showing the structure of a data invoicing apparatus according to Embodiment 4 of the present application
- FIG. 5 is a block diagram schematically showing a server for executing the method according to the present invention. as well as
- Fig. 6 schematically shows a memory unit for holding or carrying a program code implementing a method according to the invention.
- Embodiment 1 Referring to FIG. 1, a flow chart of steps of a data calling method according to Embodiment 1 of the present application is shown.
- Step S102 Receive a service request requesting to use the first service.
- the first service needs to use the privacy data of the mobile terminal, and the service request includes the service name of the first service.
- the first service may be an existing service, such as a short message service, and the service name of the first service is the original service name of the existing service, such as ISMS.
- a service request for requesting use of the privacy data of the mobile terminal may be received by a service (or called a service process) of the system.
- a service is an abstract wrapper.
- a service (or multiple) can correspond to a process. This process is dedicated to something, so it is called a service process.
- a service process Take android system as an example, the difference between a service process and a normal process is that the service process has an android-specific interface (service interface).
- Similar android system services can be divided into two categories according to different startup methods, which are started by the android dalvik virtual machine. And not launched by the android daivik virtual machine, the latter can be called native service. Services initiated by non-system android virtual machine programs (such as the 360cailback service mentioned later) cannot be registered to the system service list through the system interface.
- Step S104 Send, according to the service name, a prompt to the user of the mobile terminal whether to allow the first service to use the private data.
- the privacy data related to the service in the mobile terminal is used because the first service requirement is used. Therefore, the system server sends a prompt to the user of the mobile terminal whether to allow the use of the privacy data related to the service, and on the other hand, prompts the user to have the service to use the privacy. Data; on the other hand, it is up to the user to decide whether the privacy data is willing to be used by the service.
- Step S W6 allows the requested first service to use the privacy data according to the user's input.
- Step S108 Determine a jump service name corresponding to the service name, and invoke the first service according to the jump service name.
- the jump service name is used to repair the service name of the first service in the service list maintained by the system (the service list maintained by the ServiceManager) each time the mobile terminal starts up.
- the changed service name, the jump service name is different from the ⁇ ⁇ " name of the service other than the first service in the service list.
- the jump service name is a new service name modified by the original service name of the first service, and the original service name is modified to a new service name, so that when the service is invoked, the service is not directly called, but is first sent to the user.
- the use of privacy data prompts the service only if the user is allowed to use the private data, thus avoiding the disclosure and use of private data without the user's knowledge.
- the service name of the service (first service) using the privacy data of the mobile terminal is modified, and when the request for using the service (the first service) is received, the user is first asked whether to permit the use of the privacy data of the mobile terminal.
- the service (first service) is called by the modified service name (jump service name).
- the application can be known to the user for each access and use of the mobile terminal's private data, and then the user decides whether to allow the application to use the private data, and the person can solve the problem that the user's private data cannot be effectively valid in the prior art. Protection, the problem of low security of the user's application, improves the security of the privacy data of the mobile terminal.
- FIG. 2 a flow chart of a step of a data invoking method according to a second embodiment of the present application is shown.
- the mobile terminal is configured to use the Android operating system 5 to set the first service as a short message service, and the mobile terminal needs to use the privacy data 5 of the mobile terminal to set the service name of the first service to be the ISMS o.
- the data invocation method of this implementation includes the following steps:
- Step S202 When the mobile terminal starts, modify the service name of the first service in the service list maintained by the system, and modify the service name to the jump service name.
- the 'system' in this embodiment means that the jump service name of the first service modified by the ServiceManager service tube in the Android system is different from the original service name, and is different from the service of other services except the first service in the list. Name.
- the present step 5 the service name can be modified to a short message service ISMS ISMO, "ISMO" is merely illustrative, and those skilled in the art can modify the service name to any suitable name under the foregoing principles.
- the modified jump service name is the same as the length of the service name.
- the service names are the same length before and after the repair, and can not damage the data structure inside the program, and will not cause overflow or other problems of the program storage stack, and minimize the impact of the modification on the existing process.
- Step S204 Send an instruction to register the second service and/or intercept the service to the system.
- the second service is configured to send a prompt to the user of the mobile terminal whether to allow the first service to use the private data, and determine, according to the input of the user, whether the requested first service is allowed to use the private data; or the second service is used for
- the interception service is invoked, and the interception service sends a prompt to the user of the mobile terminal whether to allow the first service to use the private data, and after the user returns the processing result, the interception service returns the processing result to the second service.
- interception and prompting of the invoking of the private data may also be implemented by other persons in the appropriate manner according to actual needs by those skilled in the art, without having to register a new service, such as using a command or a program to transfer.
- Step S206 the system determines the second service and / or interception services if there privilege 5 if registered, proceed to step S208; if not, then refused registration process ends.
- This step is an optional step, mainly for restricted users, to avoid mis-repair or illegal modification to ensure system security.
- Step S208 Register the second service with the service name, and / or , register the interception service.
- a new service called ISMS is registered, and / or intercepted.
- Registering a new service with the original service name can effectively guarantee the stability of the system, so that the system can directly find the original service name when calling the original service.
- the new service is executed, it will not cause the original service name to be found.
- the service could not be executed, or other problems such as system crashes or crashes.
- the second service interceptor or service may be implemented separately transmitted to allow the use of private data presented to the user of the mobile terminal, and in the end set 3 ⁇ 4 allow or disallow the user to input the first service usage data privacy functions can be registered separately of 5 Second service or interception service; it is also possible to split some functions from the above functions, such as sending a prompt to the user of the mobile terminal whether or not the user is allowed to use the private data, and the function of receiving the input of the user is separated, by the intercepting service
- the service is completed, and the second service invokes the interception service, and receives the input information of the user returned by the interception service, and then determines according to the input information of the user: ft the first service uses the private data, and implements the interception and prompting of the private data call.
- the interception and prompting of the private data call are effectively realized, and the registration of the new service using the original service name also effectively ensures the stability of the system.
- the service functions can be made clearer and the existing service functions can be effectively utilized, such as the function of the existing display interception interface.
- the second service is further configured to: after the disease is allowed to use the privacy data by the first service, the jump service name corresponding to the service name is invoked, and the first service corresponding to the jump service name is invoked.
- the second service determines the jump service name, and then calls the first service, which ensures the consistency and consistency of the service call.
- the jump service name may also be determined in other ways, and then the first service is invoked.
- the second service is set to be registered, and the second service separately sends a prompt to the user of the mobile terminal whether to allow the use of the private data, and determines whether the first service is allowed or not using the private data according to the input of the user.
- the current service of the short message service is named ISM0, and the original service name ISMS points to a new service (second service) for intercepting and prompting the use of private data.
- Step S210 The system receives a service request requesting to use the first service.
- the first service needs to use the privacy data of the mobile terminal, and the service name of the first service can be obtained through the service request.
- the system server receives the service request for requesting to use the short message service, and obtains the service name of the short message service as ISMS.
- Step S212 Invoking the second service according to the service name, and sending a prompt to the user of the mobile terminal whether to allow the first service to use the private data.
- the second service After the second service is registered by using the service name, when the system receives the service name, it searches the service list maintained by the system, and the service name corresponds to the second service. Therefore, the second service 5 is called to send the user to the mobile terminal. A hint that allows the first service to use private data.
- Step S214 Receive user input, and the second service determines whether to allow the first service to use the privacy data of the mobile terminal according to the user input. If the permission is sufficient, step S216 is performed; if the service is not allowed to end.
- Step S216 The second service is determined by the jump service name corresponding to the service name, and the first service corresponding to the jump service name is called.
- the correspondence between the service name and the jump service name is stored in the system.
- the second service determines that the user: 3 ⁇ 4 the first service uses its private data, directly finds the new service name corresponding to the original service name (ie, the service name) (ie, jumps the service name), and then calls the original corresponding to the new service name. Service (ie the first service).
- the second service determines a new service name corresponding to the original service name ISMS.
- ISM0 searches for the service name ISM0 in the service list, and then uses the service name ISM0 to call the short message service according to the original process and use the privacy data of the mobile terminal.
- the service name of the first service may be used to modify the first service to be used to instruct the mobile terminal to Sending a prompt for allowing the first service to use the private data, and determining whether to allow the requested first service to use the private data according to the user's input : and, by the user, the jump service name corresponding to the service name of the first service.
- the service name is modified in the memory, the modification is for the parameter level modification, not for the system function or file level modification, the system changes are smaller, not only the privacy data is safely used. It also makes the modified system very stable. Moreover, the new service is registered with the original service name, and the original service name is modified to a new service name whose length is consistent, which further improves the stability of the system.
- the present embodiment only uses the short message service as an example, but is not limited thereto. Any other service that needs to use private data, 3 ⁇ 4 ⁇ telephone service, data upload service, etc., can implement the mobile terminal with reference to the embodiment. Data call for privacy data.
- Embodiment 3 Referring to FIG. 3, a flow chart of steps of a data invoking method according to Embodiment 3 of the present application is shown.
- the short message service that uses the privacy data of the mobile terminal is used as an example.
- the mobile terminal in this embodiment uses a mobile phone, and the operating system of the mobile phone adopts an Android operating system.
- an ISMS service is automatically started in the system server process of the dalvik, and all the Android systems are processed through the Binder mechanism, and the data call processing of the application is performed on the ISMS service, and the sending SMS request is filtered.
- 3 ⁇ 4 ⁇ is. "f day ⁇ 3 ⁇ 4 mesh &3 ⁇ 4 ⁇
- Step S302 The Android operating system starts the process.
- Step S3022 The mobile phone isms (message) service is started.
- Step S3024 Running the native program of Android, thereby starting the tampering program, automatically suspending the servicemanager process by using trace, and repairing the isms keyword of the female svrlist object is ismOo
- Step S3026 Android native program starts 360 service main program 5 automatically registers two services, 360service hesso
- the system uses the 360 service to control the registration of related services through the 360service service.
- the tampering program is started by applying the root privilege to the system, so you can also use the privilege of the application to start the 360service service native.
- 3 ⁇ 4 isms EK ⁇ native ) j3 ⁇ 4like 360service
- This service has root rights.
- the 360serviee service has the right to approve the registration of 360cailbad dalvik jffi.
- 360callbac3 ⁇ 4 dalvik is a Java program, and Java is not allowed to register to this service list by default. Thus five example embodiments, it registered by 360service service list to the service system.
- Step S3028 Start the 360 user interface through the Android dalvik program, obtain the servicemanager service through the reflection mechanism, and obtain the 360service service.
- Step S30210 Register the 360callback service through the 360service service for display Column interface.
- the 360cal]baek service is registered through the 360service service because
- Service manager does not: t i no non system and root identity of the order registration service.
- Step S304 The data invokes the workflow.
- Step S3042 The program sends a short message.
- Step S3044 The registered isms service receives the sendiext call.
- the newly registered isms service obtains the SMS service request of the program.
- Step S3046 The isms service invokes the 360callback service, and sends the short message sending number, the content, the pid (process ID) of the sending process, and the uid (user ID).
- Step S3048 360cal]
- the baek service receives the data, and the pop-up interface asks the user whether the prompt information of the pop-up interface includes a prompt for using the private data.
- the whitelist mechanism for sending SMS messages can be implemented through appropriate existing means.
- Step S30410 360callback waits for the user to process the result, and returns the step S30412 to the isms service: the registered iss service returns a result according to the 360callback, determines whether it is necessary to call the ism service, and sends a short message; if necessary, invokes the ism service to send a short message; If not, the flow of this call is ended.
- the servicemanager is used to change the android native order
- 360service Woisms registration android native Wo 360callback service and intercept interface program ( apk )
- implemented tampering servicemanager implemented tampering servicemanager, registered 360service service, pseudo isms service and 360caUback service, and intercepted SMS, pulled out the interception interface, and according to interception
- the result is the ability to send or not send text messages.
- Any mobile terminal that adopts the Android system can use the data calling method of the implementation.
- other systems similar to the Android operating system can also implement the data calling method of this embodiment.
- the mobile terminal using the 360 service is not limited to the mobile terminal using the 360 service, and the data call using the other similar service can also implement the data call with reference to the embodiment.
- FIG. 4 a block diagram of a data calling device according to Embodiment 4 of the present application is shown.
- the data invoking device of this embodiment includes: a receiving module 402, configured to receive a service request for requesting to use the first service, where the first service needs to use the privacy data of the mobile terminal, where the service request includes the service name of the first service ; prompt module 404, according to the service name is transmitted to the user of the mobile terminal is first prompted many charging service usage data privacy; confirming module 406 for a first service according to a user's input 5 3 ⁇ 4 fixed charge requested Xu using private data; calling module 408, and fixed for 5 3 ⁇ 4 service name corresponding to a given disease after confirmation module 406 allows the first data service using the privacy requested jump according to the jump service name service name 5, the first service call
- the jump service name is a service name modified by the service name of the first service in the service list maintained by the system each time the mobile terminal starts, and the jump service name is different from the service list except the first service.
- the service name of other services is a service name modified by the service name of the first service in the service list maintained by the system each
- the data invoking device of the present embodiment further includes: a registration module 410, configured to: after the mobile terminal starts, change the service name of the first service in the service list maintained by the system to the jump service name, and then use The service name is registered with the second service, and the second service is configured to send a prompt to the user of the mobile terminal whether the first service is allowed to use the private data, and according to the input of the user, whether to allow the requested first service to use the privacy. data.
- the prompting module 404 is configured to invoke the second service according to the service name, and send a prompt to the user of the mobile terminal via the second service whether the first service uses the private data.
- the second service is further configured to: after the disease is allowed to use the privacy data by the first service, the jump service name corresponding to the service name is determined, and the first service corresponding to the jump service name is invoked.
- the registration module 410 is further configured to register the interception service before or after registering the second service by using the service name; the second service is used to invoke the interception service to send a prompt to the user of the mobile terminal whether to allow the first service to use the private data. And determining whether to allow the requested first service to use the private data according to the information input by the user returned by the interception service.
- the data invoking device of this embodiment further includes: a determining module 412, configured to determine whether the second service and the intercepting service have registration authority before the registration module 410 registers the second service and the intercepting service, and if yes, allow registration ; If not, registration is not allowed.
- a determining module 412 configured to determine whether the second service and the intercepting service have registration authority before the registration module 410 registers the second service and the intercepting service, and if yes, allow registration ; If not, registration is not allowed.
- the data invoking device of this embodiment further includes: a modifying module (not shown), configured to use the service name of the first service for calling before the receiving module 402 receives the service request for using the first service.
- the first service is modified to prompt the mobile terminal to send to the user whether to allow the first service to use the private data, and according to the input of the user, determine whether to allow the requested first service to use the private data, and The name of the jump service corresponding to the service name of a service.
- the length of the service name is the same as the length of the jump service name.
- the mobile terminal uses an Android operating system.
- the first service comprises at least one of the following: a short message service, an IP telephone service, and a data upload service.
- the data invoking device of the present embodiment is used to implement a plurality of corresponding data invoking methods of the foregoing method embodiments, and has the beneficial effects of the corresponding method embodiments, and details are not described herein again.
- the various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof.
- Those skilled in the art will appreciate that some or all of the components of the data invoking device in accordance with embodiments of the present invention may be implemented in practice using a chirp processor or digital signal processor (DSP).
- DSP digital signal processor
- the invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein.
- a program implementing the present invention may be stored on a computer readable medium 5 or may have the form of one or more signals. Such signals can be downloaded from the Internet website.
- Figure 5 illustrates a server, such as an application server, that can implement a data invocation method in accordance with the present invention.
- the server conventionally includes a processor 510 and a computer program product or computer readable medium in the form of a memory 520.
- the memory 520 may be a type 0 electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM.
- Memory 520 has a memory space 530 for program code 531 for performing any of the method steps described above.
- storage space 530 for program code may include various program code 531 for implementing various steps in the above methods, respectively.
- the program code can be read from or written to one or more computer program products.
- These computer program products include program code carriers such as a hard disk 5 compact 5 disk (CD), a memory card or a floppy disk. Such computer program products are typically unloaded with the portable or fixed storage unit described with reference to FIG.
- the storage unit may have a storage section, a storage space, and the like arranged similarly to the storage 520 in the server of FIG.
- the program code can be compressed, for example, in an appropriate form.
- the storage unit includes computer readable code 53 ⁇ , ie, code that can be read by a processor, such as 510, which, when executed by a server, causes the server to perform each of the methods described above. step.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
Description
Claims
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/368,550 US9628939B2 (en) | 2011-12-27 | 2012-12-24 | Data calling method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110444060.9A CN102572804B (zh) | 2011-12-27 | 2011-12-27 | 数据调用方法和装置 |
| CN201110444060.9 | 2011-12-27 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2013097673A1 true WO2013097673A1 (zh) | 2013-07-04 |
Family
ID=46417016
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2012/087296 Ceased WO2013097673A1 (zh) | 2011-12-27 | 2012-12-24 | 数据调用方法和装置 |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US9628939B2 (zh) |
| CN (1) | CN102572804B (zh) |
| WO (1) | WO2013097673A1 (zh) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102572804B (zh) * | 2011-12-27 | 2014-11-26 | 奇智软件(北京)有限公司 | 数据调用方法和装置 |
| US9565181B2 (en) | 2013-03-28 | 2017-02-07 | Wendell D. Brown | Method and apparatus for automated password entry |
| CN103544447B (zh) * | 2013-05-30 | 2016-10-12 | Tcl集团股份有限公司 | 一种基于安卓系统的防止机密信息泄露的方法和终端 |
| CN104580155A (zh) * | 2014-12-11 | 2015-04-29 | 深圳市金立通信设备有限公司 | 一种安全防护方法 |
| CN104581705A (zh) * | 2014-12-11 | 2015-04-29 | 深圳市金立通信设备有限公司 | 一种终端 |
| CN104778415B (zh) * | 2015-02-06 | 2018-02-27 | 北京北信源软件股份有限公司 | 一种基于计算机行为的数据防泄露系统及方法 |
| CN106127063A (zh) * | 2016-06-12 | 2016-11-16 | 乐视控股(北京)有限公司 | 一种移动设备导航管理方法及装置 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1484926A (zh) * | 2001-01-04 | 2004-03-24 | ��˹��ŵ�� | 一种调用隐私的方法 |
| US20090320090A1 (en) * | 2008-06-21 | 2009-12-24 | Microsoft Corporation | Deploying privacy policy in a network environment |
| CN102186167A (zh) * | 2011-04-11 | 2011-09-14 | 中兴通讯股份有限公司 | 一种对应用进行监控的方法及系统 |
| CN102572804A (zh) * | 2011-12-27 | 2012-07-11 | 奇智软件(北京)有限公司 | 数据调用方法和装置 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4127497B2 (ja) * | 2002-09-27 | 2008-07-30 | 富士フイルム株式会社 | ディジタル・サービス・システム |
| EP2235713A4 (en) * | 2007-11-29 | 2012-04-25 | Oculis Labs Inc | METHOD AND APPARATUS FOR SECURE VISUAL CONTENT DISPLAY |
| US20100223579A1 (en) * | 2009-03-02 | 2010-09-02 | Schwartz Gerry M | Iphone application disguiser |
| US8812868B2 (en) * | 2011-03-21 | 2014-08-19 | Mocana Corporation | Secure execution of unsecured apps on a device |
| CN102238037B (zh) * | 2011-07-20 | 2014-01-08 | 复旦大学 | 协作式目标策略细化方法 |
-
2011
- 2011-12-27 CN CN201110444060.9A patent/CN102572804B/zh active Active
-
2012
- 2012-12-24 WO PCT/CN2012/087296 patent/WO2013097673A1/zh not_active Ceased
- 2012-12-24 US US14/368,550 patent/US9628939B2/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1484926A (zh) * | 2001-01-04 | 2004-03-24 | ��˹��ŵ�� | 一种调用隐私的方法 |
| US20090320090A1 (en) * | 2008-06-21 | 2009-12-24 | Microsoft Corporation | Deploying privacy policy in a network environment |
| CN102186167A (zh) * | 2011-04-11 | 2011-09-14 | 中兴通讯股份有限公司 | 一种对应用进行监控的方法及系统 |
| CN102572804A (zh) * | 2011-12-27 | 2012-07-11 | 奇智软件(北京)有限公司 | 数据调用方法和装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| US20140378100A1 (en) | 2014-12-25 |
| US9628939B2 (en) | 2017-04-18 |
| CN102572804A (zh) | 2012-07-11 |
| CN102572804B (zh) | 2014-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103514000B (zh) | 浏览器插件安装方法和装置 | |
| CN103744686B (zh) | 智能终端中应用安装的控制方法和系统 | |
| CN102801688B (zh) | 一种数据访问的方法、装置及支持数据访问的终端 | |
| CN104036019B (zh) | 网页链接的开启方法及装置 | |
| WO2015096695A1 (zh) | 一种应用程序的安装控制方法、系统及装置 | |
| WO2013182005A1 (zh) | 一种用于拦截应用程序对服务的调用的方法和装置 | |
| WO2015109668A1 (zh) | 应用程序管理方法、装置、终端及计算机存储介质 | |
| WO2017071207A1 (zh) | 一种应用安装方法、相关装置及应用安装系统 | |
| CN104572263A (zh) | 一种页面数据交互方法、相关装置及系统 | |
| CN103713904A (zh) | 在移动终端工作区内安装应用的方法、相关装置和系统 | |
| CN106663174A (zh) | 使用受保护存储限制系统调用 | |
| CN109474600B (zh) | 一种账号绑定方法、系统、装置及其设备 | |
| CN105550595A (zh) | 用于智能通信设备的隐私数据访问方法及系统 | |
| CN105207775A (zh) | 验证信息的读取方法及装置 | |
| CN102904869A (zh) | 用于远程认证的方法和设备 | |
| CN105095788B (zh) | 隐私数据保护的方法、装置及系统 | |
| WO2015058574A1 (zh) | 实现扩展应用程序的推送通知的方法及装置 | |
| CN103023976B (zh) | 一种浏览器应用插件扩展的装置和方法 | |
| CN102404706A (zh) | 一种管理资费安全的方法及移动终端 | |
| US9628939B2 (en) | Data calling method and device | |
| WO2012051894A1 (zh) | 一种widget应用保护方法及装置 | |
| CN108664805A (zh) | 一种应用程序安全校验方法及系统 | |
| CN104168536B (zh) | 一种移动终端之间的数据复制方法及系统 | |
| CN104573506A (zh) | 基于虚拟机对进程行为实时监控的方法及装置 | |
| WO2014106391A1 (zh) | 一种应用安装的方法、设备及系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12862657 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 14368550 Country of ref document: US |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 12862657 Country of ref document: EP Kind code of ref document: A1 |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 12862657 Country of ref document: EP Kind code of ref document: A1 |