WO2017045313A1 - 短信读取方法及装置 - Google Patents

短信读取方法及装置 Download PDF

Info

Publication number
WO2017045313A1
WO2017045313A1 PCT/CN2015/099988 CN2015099988W WO2017045313A1 WO 2017045313 A1 WO2017045313 A1 WO 2017045313A1 CN 2015099988 W CN2015099988 W CN 2015099988W WO 2017045313 A1 WO2017045313 A1 WO 2017045313A1
Authority
WO
WIPO (PCT)
Prior art keywords
short message
sensitive information
information
short
party application
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
Application number
PCT/CN2015/099988
Other languages
English (en)
French (fr)
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.)
Xiaomi Inc
Original Assignee
Xiaomi Inc
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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to RU2016132970A priority Critical patent/RU2653291C2/ru
Priority to MX2016010418A priority patent/MX364614B/es
Priority to KR1020167026752A priority patent/KR101811013B1/ko
Priority to JP2016556266A priority patent/JP2017531842A/ja
Publication of WO2017045313A1 publication Critical patent/WO2017045313A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6281—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database at program execution time, where the protection is within the operating system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H04L63/0838—Network architectures or network communication protocols for network security for authentication of entities using passwords using one-time-passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H04L63/0846—Network architectures or network communication protocols for network security for authentication of entities using passwords using time-dependent-passwords, e.g. periodically changing passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • 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/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/42—User authentication using separate channels for security data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels

Definitions

  • the embodiments of the present disclosure relate to the field of information security, and in particular, to a method and device for reading a short message.
  • SMS Short Message Service
  • third-party applications can have access to read short messages. If the third-party application is a malicious application, you can obtain the permission to perform sensitive operations by reading the verification code in the short message, such as the permission to perform the payment operation, the permission to perform registration and login, and so on.
  • the embodiment of the present disclosure provides a method and device for reading a short message.
  • the technical solution is as follows:
  • a method for reading a short message comprising:
  • the short message is a short message carrying sensitive information
  • the sensitive information in the short message is invisible
  • the sensitive information in the short message is invisible, including:
  • At least the sensitive information in the short message is encrypted.
  • the method further includes:
  • the short message is a short message carrying sensitive information
  • the location of the sensitive information in the short message is recorded.
  • identifying whether the received short message is a short message carrying sensitive information includes:
  • the short message is used to identify whether the short message is short information carrying sensitive information, and the feature information includes at least one of a sender number, a short message content, and a short message template.
  • the location of the sensitive information in the short message is recorded, including:
  • the third party application receives a read request for the short message, including:
  • the operating system forwards the read request to the short message component
  • a read request forwarded by the operating system is received by the short message component.
  • the method further includes:
  • a method for reading a short message comprising:
  • the third-party application reads the ordinary short message, and the short message content of the ordinary short message is visible;
  • the third-party application reads the short message carrying the sensitive information, and the sensitive information in the short message is invisible.
  • the method further includes:
  • the default SMS application of the operating system reads the short message, and the sensitive information in the short message is visible.
  • a short message reading apparatus comprising:
  • a request receiving module configured to receive a read request of the third party application for the short message
  • the information processing module is configured to: if the short message is short information carrying sensitive information, perform invisible processing on the sensitive information in the short message;
  • the information feedback module is configured to feed back the processed short message to the third party application.
  • the information processing module is configured to replace at least the sensitive information in the short message with a predetermined symbol
  • An information processing module configured to replace at least the sensitive information in the short message with the predetermined prompt information
  • the information processing module is configured to encrypt at least the sensitive information in the short message.
  • the apparatus further comprises:
  • the short message identification module is configured to identify whether the received short message is carrying sensitive information Short message
  • the location recording module is configured to record the location of the sensitive information in the short message if the short message is short message carrying sensitive information.
  • the short message identification module is configured to identify, by using the feature information of the short message, whether the short message is short information carrying sensitive information, and the feature information includes: a sender number, a short message content, and a short message template. At least one.
  • the location recording module includes:
  • the identification submodule is configured to identify the location of the sensitive information in the short message by using the short message template
  • a recording submodule configured to record the location of sensitive information in the short message.
  • the request receiving module includes:
  • Reading the receiving submodule configured to receive a read request of the third party application for the short message through the operating system
  • the permission detection submodule is configured to detect, by the operating system, whether the third party application has the short message read permission
  • the request forwarding submodule is configured to forward the read request to the short message component through the operating system when the third party application has the short message read permission;
  • the information receiving submodule is configured to receive a read request forwarded by the operating system through the short message component.
  • the apparatus further includes:
  • a default receiving module configured to receive a read request of a short message by a default SMS application of the operating system
  • the default response module is configured to respond to read requests from the default SMS application.
  • a short message reading apparatus comprising:
  • the normal reading module is configured to read the ordinary short message by the third-party application, and the short message content of the ordinary short message is in a visible state;
  • the sensitive reading module is configured to read a short message carrying sensitive information in a third-party application, and the sensitive information in the short message is invisible.
  • the apparatus further includes:
  • the default read module configured as the operating system's default SMS application, reads short messages, and the sensitive information in the short messages is visible.
  • a short message reading apparatus comprising:
  • a memory configured to store processor executable instructions
  • processor is configured to:
  • the short message is a short message carrying sensitive information
  • the sensitive information in the short message is invisible
  • a short message reading apparatus comprising:
  • a memory configured to store processor executable instructions
  • processor is configured to:
  • the third-party application reads the ordinary short message, and the short message content of the ordinary short message is visible;
  • the third-party application reads the short message carrying the sensitive information, and the sensitive information in the short message is invisible.
  • FIG. 1 is a schematic diagram showing the composition of a mobile terminal according to an exemplary embodiment
  • FIG. 2 is a flowchart of a method for reading a short message according to an exemplary embodiment
  • FIG. 3A is a flowchart of a method for reading a short message according to another exemplary embodiment
  • FIG. 3B is a flowchart of a sub-step of a short message reading method according to another exemplary embodiment
  • FIG. 4A is a schematic diagram of an interface of a sensitive information invisible process according to an exemplary embodiment
  • FIG. 4B is a schematic diagram of an interface of a sensitive information invisible process according to another exemplary embodiment
  • FIG. 5 is a flowchart of a method for reading a short message according to another exemplary embodiment
  • FIG. 6 is a flowchart of a method for reading a short message according to still another exemplary embodiment
  • FIG. 7A is a schematic diagram of an interface for short message reading according to an exemplary embodiment
  • FIG. 7B is a schematic diagram of an interface for short message reading according to another exemplary embodiment
  • FIG. 8 is a block diagram of a short message reading apparatus according to an exemplary embodiment
  • FIG. 9 is a block diagram of a short message reading apparatus according to another exemplary embodiment.
  • FIG. 10 is a block diagram of a short message reading apparatus according to another exemplary embodiment.
  • FIG. 11 is a block diagram of a short message reading apparatus according to still another exemplary embodiment.
  • FIG. 12 is a block diagram of a short message reading apparatus according to an exemplary embodiment.
  • Android operating system A Linux-based free and open source operating system produced by Google Inc. of the United States, mainly used in mobile terminals.
  • the mobile terminal can be a mobile phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV), a motion picture expert. Compress standard audio layers 4) Players and laptops, etc.
  • an application In the Android operating system, an application usually includes at least one program component. There are four types of program components: Activity: Activity component, Service component, Content Provider component, and Broadcast Receiver component.
  • Active component A component of the Android application that is responsible for interacting with the user, providing a visual user interface for Android applications.
  • An Android app can include zero to more active components.
  • Service component A component of an Android application that runs in the background and does not provide a user interface.
  • An Android app can include zero to more service components.
  • Content Provider Component A component of an Android application that is configured to provide data to other applications or other components in the current application, such as SMS, ringtones, wallpaper, phone book, and so on. It can encapsulate data in various formats and provide it to other applications or components in standard form. Use.
  • the short message component in the embodiment of the present disclosure is one of content provider components.
  • Broadcast Receiver Component A message configured to receive and respond to broadcasts by the operating system. It can receive messages of interest to itself (or pre-defined messages of a certain message type) and then process or forward them to other components in the current application.
  • Third-party applications Applications in mobile devices that are relative to the operating system's own applications.
  • FIG. 1 shows a schematic diagram of the composition of a mobile terminal shown in an exemplary embodiment.
  • the mobile terminal includes a short message component 120, an operating system 140, and a third party application 160.
  • the operating system 140 receives the read request sent by the third party application 160 and forwards the read request to the short message component 120.
  • the mobile terminal can be a mobile phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), and an MP4 (Moving Picture Experts Group Audio Layer IV). Standard audio level 4) Players and laptops, etc.
  • the short message component 120 is one of the content provider components in the Android application that is configured to provide SMS data for other applications or other components in the current application.
  • the short message component 120 can receive the short message sent by the source and store the received short message to form a short message list.
  • a configuration file is stored in the operating system 140, and the configuration file stores the short message reading authority of the third party application 160 at the operating system level.
  • the operating system 140 stores a total configuration file, where the third-party application 160 stores the short-message read permission of the third-party application 160 at the operating system level.
  • the operating system 140 stores a plurality of configuration files, and the third-party application 160 corresponds to a respective configuration file at the operating system level.
  • the third-party application 160 can read when it has the operating system level SMS read permission. All the short messages in the short message component 120; when the third party application 160 does not have the short message read permission at the operating system level, then any short message in the short message component 120 cannot be read.
  • One or more program components may be included in the third party application 160, each of which may be any of the activity component 162, the service component 164, the content provider component 166, and the broadcast receiver component 168.
  • the third-party application 160 When the third-party application 160 needs to read the short message in the short message component 120, the third-party application 160 first sends a read request of the short message to the operating system 140, and after the operating system 140 receives the read request, it detects the first Whether the three-party application 160 exists in the short message read permission list, and if the third-party application 160 exists in the short message read permission list, the operating system 140 forwards the short message read request sent by the third-party application 160 to The short message component 120, after receiving the read request forwarded by the operating system 140, the short message component 120 searches for the short information to be read in the short message list according to the short information that needs to be read in the read request, and the short message information is found. The short message is fed back to the third party application 160 via the operating system 140.
  • FIG. 2 is a flowchart of a method for reading a short message according to an exemplary embodiment. This embodiment is illustrated by using the short message reading method in the mobile terminal shown in FIG. 1 .
  • the short message reading method includes the following steps.
  • a third party application receives a read request for short messages.
  • This third-party application is an application that belongs to the operating system's configuration file.
  • a configuration file is a file that is controlled by permissions based on the granularity of the application.
  • step 202 if the short message is short message carrying sensitive information, the sensitive information in the short message is invisible.
  • the invisible process is to encrypt at least the sensitive information in the short message to make it invisible.
  • step 203 the processed short message is fed back to the third party application.
  • the short message reading method provided in the embodiment of the present disclosure is received by a third party.
  • the program to read the short message if the short message is a short message carrying the sensitive information, the sensitive information in the short message is invisible; the processed short message is fed back to the third party application;
  • the three-party application can read the short message component in the short message component only when it has the read permission of the operating system level, thereby causing the malicious application to obtain the permission to perform the sensitive operation by reading the verification code in the short message.
  • the third-party application is prohibited from reading short messages carrying sensitive information, thereby avoiding the effect of leakage of sensitive information in the short message, and at the same time achieving the effect of controlling the granularity of a single short message.
  • FIG. 3A is a flowchart of a short message reading method according to another exemplary embodiment. This embodiment is illustrated by using the short message reading method in a mobile terminal in the implementation environment shown in FIG. 1 .
  • the short message reading method includes the following steps.
  • step 301 it is identified whether the received short message is short message carrying sensitive information.
  • Sensitive information is information related to the user's virtual property and/or control rights in the network.
  • the short message component receives the short message sent by the source of the short message, and the short message component identifies the received short message to identify whether the short message carries the sensitive information.
  • the short message component identifies the short message by using the feature information of the short message to identify whether the short message is short information carrying sensitive information, where the feature information includes at least one of a sender number, a short message content, and a short message template.
  • step 302 if the short message is not a short message carrying sensitive information, the short message is directly stored.
  • step 303 if the short message is a short message carrying sensitive information, the location of the sensitive information in the short message is recorded.
  • the short message component records the location of the sensitive information in the short message.
  • the short message component marks the short message as a short message carrying sensitive information.
  • step 303 may include the following sub-steps, as shown in FIG. 3B:
  • step 303a the location of the sensitive information in the short message is identified by the short message template.
  • the short message component can identify the location of the sensitive information in the short message according to the short message template.
  • the short message component pre-stores a plurality of short message templates carrying sensitive information, and stores the location of the sensitive information corresponding to the short message template, for example, a short message.
  • the template is "You are using Xiaomi company to make payment, the payment password is xxxxx", the SMS template is stored in the short message component, and the location where the sensitive information is stored in the location corresponding to the SMS template is the keyword "payment password is After the 6-digit information; after identifying the short message, the short message component will identify the short message carrying the sensitive information and match the stored short message template to obtain the location of the sensitive information in the short message.
  • step 303b the location of the sensitive information in the short message is recorded.
  • the short message component records the location information of the obtained sensitive information in the short message in a corresponding position of the short message.
  • step 304 a read request of the short message by the third party application is received by the operating system.
  • the operating system When the third party application needs to read the short message in the short message component, firstly, the operating system sends a read request for the short message, and correspondingly, the operating system receives the third party application to read the short message.
  • the third-party application may be a short message application, a payment application, or a registration application. Embodiments of the present disclosure do not define the types of third party applications.
  • step 305 the operating system detects whether the third party application has the short message read permission.
  • the operating system pre-stores the permission for each third-party application to read the short message.
  • the operating system receives a request for reading the short message from a third-party application
  • the operating system first acquires the pre-stored configuration file, and detects the Whether the third-party application exists in the pre-stored configuration file, and if it exists in the configuration file, the third-party application has the right to read the short message.
  • the third-party application does not have SMS read permission if it does not exist in the configuration file.
  • step 306 if the third party application does not have the short message read permission, the operating system does not forward the read request to the short message component.
  • step 307 if the third party application has the short message read permission, the read request is forwarded to the short message component by the operating system.
  • the operating system forwards the read request of the third-party application to the short message component.
  • step 308 a read request forwarded by the operating system is received by the short message component.
  • the short message component receives a read request forwarded by the operating system.
  • the third-party application "Xiaomi Mall” sends a short message to the operating system to read the "Millet Payment” payment password in the short message component.
  • the operating system After the operating system receives the read request, it detects whether the "Millet Mall” is in the operating system. The user has the right to read the short message, and when having the read permission, forwards the read request sent by the "Millet Mall" to the short message component, and the short message component receives the read request forwarded by the operating system.
  • the short message component detects whether the short message to be read by the read request is short message carrying sensitive information.
  • the short message component obtains the short message that needs to be read in the read request according to the received read request, and detects whether the short message to be read in the read request carries a mark, and if the tag is carried, the short message is carried A short message with sensitive information; if there is no tag, the short message does not carry sensitive information.
  • step 310 if the short message to be read by the read request is not the short message carrying the sensitive information, the short message component feeds the short message back to the third party application.
  • step 311 if the short message to be read by the read request is short message carrying sensitive information, the sensitive information in the short message is invisible.
  • the short message to be read in the read request is a short message carrying sensitive information, it will be short. Sensitive information in the information is invisible.
  • the invisible process is to replace at least the sensitive information in the short message with a predetermined symbol
  • the invisible process is to replace at least the sensitive information in the short message with the predetermined prompt information
  • the predetermined reminder information is used to prompt the user to view sensitive information using a specified application.
  • the predetermined prompt information may also be a hyperlink, and when the hyperlink is triggered, jump to the specified application to view the sensitive information.
  • the invisible process is to encrypt at least the sensitive information in the short message
  • step 312 the processed short message is fed back to the third party application.
  • the short message component feeds the short message carrying the sensitive information to the third party application after being invisible.
  • the short message component identifies whether the short message is a short message carrying the sensitive information. After receiving the read request forwarded by the operating system, the short message may be recognized in advance before receiving the read request forwarded by the operating system. Whether it is a short message with sensitive information.
  • the short message reading method provided in the embodiment of the present disclosure is received by a third party.
  • the program to read the short message if the short message is a short message carrying the sensitive information, the sensitive information in the short message is invisible; the processed short message is fed back to the third party application;
  • the three-party application can read the short message component in the short message component only when it has the read permission of the operating system level, thereby causing the malicious application to obtain the permission to perform the sensitive operation by reading the verification code in the short message.
  • the third-party application is prohibited from reading short messages carrying sensitive information, thereby avoiding the effect of leakage of sensitive information in the short message, and at the same time achieving the effect of controlling the granularity of a single short message.
  • the processing of the sensitive information in the short message is added only in the short message component, thereby realizing the control of the granularity of the single short message, and the effect of the operation is simple and easy to implement.
  • the method for identifying, by the short message component in step 301, whether the short message is a short message carrying sensitive information includes the following situations:
  • the short message component may identify, according to the sender number of the received short message, whether the short message carries sensitive information.
  • the short message backend server stores a list, for example, the company is stored in the list.
  • a and the SMS number corresponding to company A have SMS number 1 and SMS number 2
  • company B and SMS number corresponding to company B SMS number 3 and SMS number 4
  • company C and SMS number corresponding to company C have SMS number 5 and SMS number 6 and so on.
  • the sender number of the short message received by the short message component is the short message number 5, according to the corresponding relationship in Table 1, the source of the short message is "company C, the short message component and the short message is identified as carrying Short messages with sensitive information.
  • the short message component can identify whether the short message carries sensitive information according to the short message content of the received short message, for example, the content of the short message is “[A3 Travel ⁇ Go] 06-2207: 15 Kunming Changshui Airport --Fly -08:55 Chongqing Jiangbei Airport 2B Jiangxiang Air 8L9863, order XXXXXXXX is paying, Zhang Wuji (ticket number: XXX-XXXXXXXXXXX). Click http://tb.cn/3eXI06y client to view the itinerary details.” Then, the short message component identifies the short message as the short message carrying the sensitive information according to the keyword in the short message content [A3 Travel ⁇ Go].
  • the short message component may further identify, according to the short message template, whether the short message carries sensitive information, for example, the short message component pre-stores a plurality of short message templates carrying sensitive information, and when receiving the short message, the short message component The received short message is matched with the stored short message template. If the received short message matches a certain short message template, the short message is identified as a short message carrying sensitive information.
  • Short Message 1 Sender: 140000621 "[Company A] Order No. XXXXXXXXXX is paying, the verification code is XXXXXX. Click http://tb.cn/3eXI06y client to view the detailed information.”
  • Short Message 2 Sender: 140000622 "[Company A] Order No. XXXXXXXXXX is paying, the verification code is XXXXXX. Click http://tb.cn/3eXI06y client to view the details.”
  • Short message 1 and short message 2 are short messages sent by Jingdong Company.
  • the source party identifier of short message 1 is "140000621”
  • the source party identifier of short message 2 is "140000622”
  • the two source identifiers have the same prefix "1400062”.
  • the two short messages have the keyword "[company A]”.
  • the two short message templates constructed with the short message 1 and the short message 2 described above are as follows:
  • the correspondence between the combination of the short message source identification feature and the keyword and the extracted template is as shown in Table 2 below:
  • SMS template 14000062X+[Company A] ⁇ Payment Template 1> 14000062X+[Company A] ⁇ Payment Template 2>
  • the short message component When the short message received in the short message component carries the feature of "14000062X+[company A]", it matches the ⁇ payment template 2> in the short message template, and therefore, the short message component identifies the short message as carried. Short messages for sensitive information.
  • the third-party application "Millet Mall” sends a read request to the operating system, and the operating system forwards the read request sent by the third-party application to the short message component, and the short message component processes the content in the short message after obtaining the read request.
  • the short message component obtains the read request
  • the content in the short message is processed as “[ ⁇ ] order number 1111111 is being paid, and the verification code is abcdef, please input the verification code within 5 minutes.”
  • the three-party application "Millet Mall”.
  • the read request forwarded by the operating system to the short message component is the third.
  • the read request sent by the party application, and the default SMS application of the operating system can also read the short message component of the short message component. Please refer to the following steps, as shown in Figure 5:
  • step 501 a read request of the short message is received by the default SMS application of the operating system.
  • the short message component receives a read request sent by the default SMS application of the operating system and is configured to read the short message in the short message component.
  • step 502 a response to the default SMS application's read request is made.
  • the short message component After receiving the read request sent by the default SMS application, the short message component directly responds to the read request.
  • the default SMS application includes a messaging application that comes with the mobile terminal, or other trusted messaging application.
  • the third party application can also read the short message in the short message into two different situations. Please refer to the following steps, as shown in Figure 6.
  • step 601 the third party application reads the ordinary short message, and the short message content of the ordinary short message is in a visible state.
  • Ordinary short message refers to short messages that do not carry sensitive information, and the short message content is visible. Third-party applications can read ordinary short messages in the short message component by simply having the right to read the SMS at the operating system level.
  • the third-party application sends a read request for reading the normal short message to the operating system.
  • the operating system forwards the read request to the short message component, and the short message component will send the ordinary short message. Feedback to third-party applications. As shown in Figure 7A.
  • step 602 the third party application reads the short message carrying the sensitive information, and the sensitive information in the short message is invisible.
  • the process of the third party application reading the short information carrying the sensitive information is as shown in the embodiment of FIG. 3A. As shown, the sensitive information in the short message is invisible, and the sensitive information in the short message carrying the sensitive information read by the third-party application is invisible. As shown in Figure 7B.
  • the third-party application has two different reading conditions for the short message in the short message component, and the default SMS application of the operating system has only one reading condition for the short message in the short message component. . Please refer to the following steps (not shown in Figure 6):
  • step 603 the default SMS application of the operating system reads the short message, and the sensitive information in the short message is in a visible state.
  • the default SMS application of the operating system can directly read the short message in the short message component, and the sensitive information in the short message is visible.
  • FIG. 8 is a block diagram of a short message reading apparatus, which may be implemented as a whole or a part of a mobile terminal by software or hardware in combination, according to an exemplary embodiment.
  • the short message reading device includes but is not limited to:
  • the request receiving module 820 is configured to receive a read request of the third party application for the short message.
  • the information processing module 840 is configured to perform invisible processing on the sensitive information in the short information if the short information is short information carrying sensitive information.
  • the information feedback module 860 is configured to feed back the processed short message to the third party application.
  • the short message reading device receives the short message read request by the third party application; if the short message is the short message carrying the sensitive information, the sensitive information in the short message The information is invisible; the short message is processed back to the third-party application; and the third-party application can read all the short messages in the short message component when only the operating system-level short message reading permission is available, thereby causing A malicious application obtains the permission to perform sensitive operations by reading the verification code in the short message; The short message carrying the sensitive information is read in order, thereby avoiding the effect of the leakage of sensitive information in the short message, and at the same time achieving the effect of controlling the granularity of the single message.
  • FIG. 9 is a block diagram of a short message reading apparatus according to another exemplary embodiment, in which the short message reading apparatus can be implemented as a whole or a part of a mobile terminal by software or hardware.
  • the short message reading device includes but is not limited to:
  • the short message identification module 910 is configured to identify whether the received short message is short information carrying sensitive information.
  • the short message identification module 910 is further configured to: identify, by using the feature information of the short message, whether the short message is short information carrying the sensitive information, where the feature information includes: at least one of a sender number, a short message content, and a short message template. .
  • the location recording module 920 is configured to record the location of the sensitive information in the short message if the short message is short information carrying sensitive information.
  • the location recording module 920 includes:
  • the identification submodule 921 is configured to identify the location of the sensitive information in the short message by using the short message template
  • a record sub-module 922 is configured to record the location of the sensitive information in the short message.
  • the request receiving module 930 is configured to receive a read request of the third party application for the short message.
  • the request receiving module 930 includes:
  • the read receiving submodule 931 is configured to receive a read request of the third party application for the short message through the operating system.
  • the permission detection sub-module 932 is configured to detect, by the operating system, whether the third-party application has the short message read permission.
  • the request forwarding sub-module 933 is configured to forward the read request to the short message component through the operating system when the third-party application has the short message read permission.
  • the information receiving sub-module 934 is configured to receive a read request forwarded by the operating system through the short message component.
  • the information processing module 940 is configured to perform invisible processing on the sensitive information in the short information if the short information is short information carrying sensitive information.
  • the information processing module 940 is configured to replace at least the sensitive information in the short message with a predetermined symbol
  • the information processing module 940 is configured to replace at least the sensitive information in the short message with the predetermined prompt information
  • the information processing module 940 is configured to encrypt at least the sensitive information in the short message.
  • the information feedback module 950 is configured to feed back the processed short message to the third party application.
  • the short message reading device receives the short message read request by the third party application; if the short message is the short message carrying the sensitive information, the sensitive information in the short message The information is invisible; the short message is processed back to the third-party application; and the third-party application can read all the short messages in the short message component when only the operating system-level short message reading permission is available, thereby causing A malicious application obtains the permission to perform sensitive operations by reading the verification code in the short message; it prevents the third-party application from reading the short information carrying the sensitive information, thereby avoiding the leakage of sensitive information in the short message.
  • the effect of the authority control on the granularity of a single message is realized.
  • the processing of the sensitive information in the short message is added only in the short message component, thereby realizing the control of the granularity of the single short message, and the effect of the operation is simple and easy to implement.
  • the read request forwarded by the operating system to the short message component is the third.
  • the read request sent by the party application, and the default SMS application of the operating system can also read the short message component of the short message component. Please refer to the following module, as shown in Figure 10:
  • the default receiving module 1020 is configured to receive a read request of the short message by the default SMS application of the operating system;
  • the default response module 1040 is configured to respond to a read request by the default SMS application.
  • the third party application can also read the short message in the short message into two different situations. Please refer to the following module, as shown in Figure 11.
  • the normal reading module 1120 is configured to read a common short message by a third-party application, and the short message content of the ordinary short message is in a visible state;
  • the sensitive reading module 1140 is configured to read, by the third-party application, the short information carrying the sensitive information, and the sensitive information in the short information is in an invisible state.
  • the default SMS application of the operating system has only one case for reading ordinary short messages and short messages carrying sensitive information. Please refer to the following modules:
  • the default read module configured as the operating system's default SMS application, reads short messages, and the sensitive information in the short messages is visible. (not shown in the figure)
  • the embodiment of the present disclosure further provides a short message reading device, which may be configured to implement the short message reading method provided by the embodiment of the present disclosure.
  • the apparatus includes: a processor; a memory configured to store processor executable instructions;
  • processor is configured to:
  • the short message is a short message carrying sensitive information
  • the sensitive information in the short message is performed. Invisible processing
  • the embodiment of the present disclosure further provides a short message reading device, which may be configured to implement the short message reading method provided by the embodiment of the present disclosure.
  • the apparatus includes: a processor; a memory configured to store processor executable instructions;
  • processor is configured to:
  • the third-party application reads the ordinary short message, and the short message content of the ordinary short message is visible;
  • the third-party application reads the short message carrying the sensitive information, and the sensitive information in the short message is invisible.
  • FIG. 12 is a block diagram of a short message reading apparatus according to an exemplary embodiment.
  • device 1200 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 1200 can include one or more of the following components: processing component 1202, memory 1204, power component 1206, multimedia component 1208, audio component 1210, input/output (I/O) interface 1212, sensor component 1214, and Communication component 1216.
  • Processing component 1202 typically controls the overall operation of device 1200, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1202 can include one or more processors 1218 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 1202 can include one or more modules to facilitate interaction between component 1202 and other components.
  • processing component 1202 can include a multimedia module to facilitate interaction between multimedia component 1208 and processing component 1202.
  • Memory 1204 is configured to store various types of data to support operation at device 1200. Examples of such data include instructions for any application or method operating on device 1200, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory , flash memory, disk or CD.
  • SRAM static random Access Memory
  • EEPROM Electrically Erasable Programmable Read Only Memory
  • EPROM Erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory flash memory, disk or CD.
  • Power component 1206 provides power to various components of device 1200.
  • Power component 1206 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1200.
  • the multimedia component 1208 includes a screen between the device 1200 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1208 includes a front camera and/or a rear camera. When the device 1200 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1210 is configured to output and/or input an audio signal.
  • audio component 1210 includes a microphone (MIC) that is configured to receive an external audio signal when device 1200 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 1204 or transmitted via communication component 1216.
  • the audio component 1210 also includes a speaker configured to output an audio signal.
  • the I/O interface 1212 provides an interface between the processing component 1202 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1214 includes one or more sensors configured to provide each of device 1200 State assessment of aspects.
  • sensor assembly 1214 can detect an open/closed state of device 1200, a relative positioning of components, such as a display and a keypad of device 1200, and sensor component 1214 can also detect a change in position of a component of device 1200 or device 1200, the user The presence or absence of contact with device 1200, device 1200 orientation or acceleration/deceleration and temperature change of device 1200.
  • Sensor assembly 1214 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1214 may also include a light sensor, such as a CMOS or CCD image sensor, configured for use in imaging applications.
  • the sensor assembly 1214 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 1216 is configured to facilitate wired or wireless communication between device 1200 and other devices.
  • the device 1200 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • communication component 1216 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 1216 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 1200 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation configured to perform the above described short message reading method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation configured to perform the above described short message reading method.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1204 comprising instructions executable by processor 1218 of apparatus 1200 to perform the above described short message reading method.
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • the third-party application can read the short message component in the short message component when only the operating system level of the short message reading permission is obtained, thereby causing the malicious application to obtain the sensitive operation by reading the verification code in the short message.
  • the problem of permission; the third-party application is prohibited from reading short messages carrying sensitive information, thereby avoiding the effect of leakage of sensitive information in the short message, and at the same time achieving the effect of controlling the granularity of a single message.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • Accounting & Taxation (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Strategic Management (AREA)
  • Medical Informatics (AREA)
  • Finance (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开实施例揭示了一种短信读取方法及装置，属于信息安全领域。所述短信读取方法包括：通过接收第三方应用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息。

Description

短信读取方法及装置
本申请基于申请号为201510600885.3、申请日为2015年9月18日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开实施例涉及信息安全领域，特别涉及一种短信读取方法及装置。
背景技术
利用短信息(英文：Short Message Service，缩写：SMS)中携带的验证码进行安全验证，是目前常见的身份验证方式。
在安卓(英文：Android)操作系统中，第三方应用程序可以拥有读取短信息的权限。若第三方应用程序是一个恶意的应用程序，则可以通过读取短信息中的验证码，从而获取到执行敏感操作的权限，比如，执行支付操作的权限、执行注册和登录的权限等等。
发明内容
为了解决第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的短信内容，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题，本公开实施例提供了一种短信读取方法及装置。所述技术方案如下：
根据本公开实施例的第一方面，提供一种短信读取方法，该方法包括：
接收第三方应用程序对短信息的读取请求；
若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；
向第三方应用程序反馈处理后的短信息。
在一个可选地实施例中，将短信息中的敏感信息进行不可见处理，包括：
至少将短信息中的敏感信息替换为预定符号；
或，
至少将短信息中的敏感信息替换为预定提示信息；
或，
至少将短信息中的敏感信息进行加密。
在一个可选地实施例中，该方法还包括：
识别接收到的短信息是否为携带有敏感信息的短信息；
若短信息是携带有敏感信息的短信息，则记录敏感信息在短信息中的位置。
在一个可选地实施例中，识别接收到的短信息是否为携带有敏感信息的短信息，包括：
通过短信息的特征信息识别短信息是否为携带有敏感信息的短信息，特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
在一个可选地实施例中，记录敏感信息在短信息中的位置，包括：
通过短信模板识别敏感信息在短信息中的位置；
记录敏感信息在短信息中的位置。
在一个可选地实施例中，接收第三方应用程序对短信息的读取请求，包括：
通过操作系统接收第三方应用程序对短信息的读取请求；
通过操作系统检测第三方应用程序是否具有短信读取权限；
若第三方应用程序具有短信读取权限，则通过操作系统向短信息组件转发读取请求；
通过短信息组件接收操作系统转发的读取请求。
在一个可选地实施例中，该方法还包括：
接收操作系统的默认短信应用程序对短信息的读取请求；
对默认短信应用程序的读取请求进行响应。
根据本公开实施例的第二方面，提供一种短信读取方法，该方法包括：
第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态；
第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
在一个可选地实施例中，该方法还包括：
操作系统的默认短信应用程序读取短信息，短信息中的敏感信息为可见状态。
根据本公开实施例的第三方面，提供一种短信读取装置，该装置包括：
请求接收模块，被配置为接收第三方应用程序对短信息的读取请求；
信息处理模块，被配置为若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；
信息反馈模块，被配置为向第三方应用程序反馈处理后的短信息。
在一个可选地实施例中，信息处理模块，被配置为至少将短信息中的敏感信息替换为预定符号；
或，
信息处理模块，被配置为至少将短信息中的敏感信息替换为预定提示信息；
或，
信息处理模块，被配置为至少将短信息中的敏感信息进行加密。
在一个可选地实施例中，该装置还包括：
短信识别模块，被配置为识别接收到的短信息是否为携带有敏感信息 的短信息；
位置记录模块，被配置为若短信息是携带有敏感信息的短信息，则记录敏感信息在短信息中的位置。
在一个可选地实施例中，短信识别模块，被配置为通过短信息的特征信息识别短信息是否为携带有敏感信息的短信息，特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
在一个可选地实施例中，位置记录模块，包括：
识别子模块，被配置为通过短信模板识别敏感信息在短信息中的位置；
记录子模块，被配置为记录敏感信息在短信息中的位置。
在一个可选地实施例中，请求接收模块，包括：
读取接收子模块，被配置为通过操作系统接收第三方应用程序对短信息的读取请求；
权限检测子模块，被配置为通过操作系统检测第三方应用程序是否具有短信读取权限；
请求转发子模块，被配置为在第三方应用程序具有短信读取权限时，通过操作系统向短信息组件转发读取请求；
信息接收子模块，被配置为通过短信息组件接收操作系统转发的读取请求。
在一个可选地实施例中，该装置，还包括：
默认接收模块，被配置为接收操作系统的默认短信应用程序对短信息的读取请求；
默认响应模块，被配置为对默认短信应用程序的读取请求进行响应。
根据本公开实施例的第四方面，提供一种短信读取装置，该装置包括：
普通读取模块，被配置为第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态；
敏感读取模块，被配置为第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
在一个可选地实施例中，该装置，还包括：
默认读取模块，被配置为操作系统的默认短信应用程序读取短信息，短信息中的敏感信息为可见状态。
根据本公开实施例的第五方面，提供一种短信读取装置，该装置包括：
处理器；
配置为存储处理器可执行指令的存储器；
其中，处理器被配置为：
接收第三方应用程序对短信息的读取请求；
若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；
向第三方应用程序反馈处理后的短信息。
根据本公开实施例的第六方面，提供一种短信读取装置，该装置包括：
处理器；
配置为存储处理器可执行指令的存储器；
其中，处理器被配置为：
第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态；
第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
本公开的实施例提供的技术方案可以包括以下有益效果：
通过接收第三方应用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的短信内容，从而导致恶意的 应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并于说明书一起用于解释本公开实施例的原理。
图1是根据一示例性实施例示出的移动终端的组成示意图；
图2是根据一示例性实施例示出的一种短信读取方法的流程图；
图3A是根据另一示例性实施例示出的一种短信读取方法的流程图；
图3B是根据另一示例性实施例示出的一种短信读取方法子步骤的流程图；
图4A是根据一示例性实施例示出的一种敏感信息不可见处理的界面示意图；
图4B是根据另一示例性实施例示出的一种敏感信息不可见处理的界面示意图；
图5是根据另一示例性实施例示出的一种短信读取方法的流程图；
图6是根据再一示例性实施例示出的一种短信读取方法的流程图；
图7A是根据一示例性实施例示出的一种短信读取的界面示意图；
图7B是根据另一示例性实施例示出的一种短信读取的界面示意图；
图8是根据一示例性实施例示出的一种短信读取装置的框图；
图9是根据另一示例性实施例示出的一种短信读取装置的框图；
图10是根据另一示例性实施例示出的一种短信读取装置的框图；
图11是根据再一示例性实施例示出的一种短信读取装置的框图；
图12是根据一示例性实施例示出的一种短信读取装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
首先对本公开实施例所涉及的几个名词进行简介：
安卓操作系统：由美国谷歌公司出品的一种基于Linux的自由及开放源代码的操作系统，主要使用于移动终端。该移动终端可以是手机、平板电脑、电子书阅读器、MP3播放器(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层面4)播放器和膝上型便携计算机等等。
应用程序：在安卓操作系统中，一个应用程序通常包括至少一个程序组件。程序组件分为四种：活动(英文：Activity)组件、服务(英文：Service)组件、内容提供者(英文：Content Provider)组件和广播接收器(英文：Broadcast Receiver)组件。
活动组件：安卓应用程序中负责与用户交互的组件，它为安卓应用程序提供可视化的用户界面。一个安卓应用程序可以包括零到多个活动组件。
服务组件：安卓应用程序中运行于后台、不提供用户界面的组件。一个安卓应用程序可以包括零到多个服务组件。
内容提供者组件：安卓应用程序中配置为为其它应用或者当前应用中的其它组件提供数据的组件，比如：短信、铃声、壁纸、电话本等。它能够对各种格式的数据进行封装，以标准的形式提供给其它应用或者组件进 行使用。其中，本公开实施例中的短信息组件是内容提供者组件中的一种。
广播接收器组件：配置为接收和响应操作系统广播的消息。它能够接收自己感兴趣的消息(或者说预先定义的某种消息类型的消息)，然后进行处理或转发给当前应用中的其它组件。
第三方应用程序：移动终端中相对于操作系统自带应用程序而言的应用程序。
为了便于理解，请首先参考图1，其示出了一示例性实施例示出的移动终端的组成示意图。移动终端中包括有：短信息组件120、操作系统140和第三方应用程序160，操作系统140接收第三方应用程序160发送的读取请求，并将该读取请求转发给短信息组件120。
移动终端可以是手机、平板电脑、电子书阅读器、MP3播放器(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层面4)播放器和膝上型便携计算机等等。
短信息组件120是安卓应用程序中内容提供者组件中的一个，配置为为其它应用或者当前应用中的其它组件提供短信数据的组件。短信息组件120可以接收来源方发送的短信息，并存储接收到的短信息，形成短信息列表。
操作系统140中预先存储有配置文件，该配置文件中存储有第三方应用程序160在操作系统层面的短信读取权限。
可选的，操作系统140中存储有一个总的配置文件，该配置文件中存储有所有第三方应用程序160在操作系统层面的短信读取权限。
可选的，操作系统140中存储有多个配置文件，第三方应用程序160在操作系统层面的短信读取权限对应一个各自的配置文件。
第三方应用程序160拥有操作系统层面的短信读取权限时，可以读取 短信息组件120中的全部短信；第三方应用程序160在操作系统层面没有短信读取权限时，则不可以读取短信息组件120中的任何短信。
第三方应用程序160中可以包括一个或者一个以上的程序组件，每个程序组件可以是活动组件162、服务组件164、内容提供者组件166和广播接收器组件168中的任意一种。
当第三方应用程序160需要读取短信息组件120中的短信息时，第三方应用程序160首先向操作系统140发送短信息的读取请求，操作系统140接收到读取请求后，检测该第三方应用程序160是否存在于短信读取权限列表中，若该第三方应用程序160存在于短信读取权限列表中，则操作系统140将该第三方应用程序160发送的短信息读取请求转发给短信息组件120，短信息组件120接收到操作系统140转发的读取请求后，根据读取请求中需要读取的短信息，在短信息列表中查找需要读取的短信息，将查找到的短信息通过操作系统140反馈给第三方应用程序160。
图2是根据一示例性实施例示出的一种短信读取方法的流程图，本实施例以该短信读取方法应用于图1所示的移动终端中来举例说明。该短信读取方法包括如下几个步骤。
在步骤201中，接收第三方应用程序对短信息的读取请求。
该第三方应用程序是属于操作系统的配置文件中的应用程序。配置文件是按照应用程序粒度进行权限控制的文件。
在步骤202中，若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理。
不可见处理是至少将短信息中的敏感信息进行加密，使其为不可见状态。
在步骤203中，向第三方应用程序反馈处理后的短信息。
综上所述，本公开实施例中提供的短信读取方法，通过接收第三方应 用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的短信内容，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。
图3A是根据另一示例性实施例示出的一种短信读取方法的流程图，本实施例以该短信读取方法应用于图1所示的实施环境中的移动终端中来举例说明。该短信读取方法包括如下几个步骤。
在步骤301中，识别接收到的短信息是否为携带有敏感信息的短信息。
敏感信息是与用户在网络中的虚拟财产和/或控制权限有关的信息。
短信息组件接收短信息来源方发送的短信息，短信息组件对接收到的短信息进行识别，识别该短信息中是否携带有敏感信息。
短信息组件对短信息的识别可以通过短信的特征信息识别短信息是否为携带有敏感信息的短信息，其中，特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
在步骤302中，若短信息不是携带有敏感信息的短信息，则直接存储该短信息。
在步骤303中，若短信息是携带有敏感信息的短信息，则记录敏感信息在短信息中的位置。
若识别结果为该短信息是携带有敏感信息的短信息，则短信息组件记录敏感信息在短信息中的位置。
短信息组件标记该短信息为携带有敏感信息的短信息。
本实施例中，步骤303可以包括如下子步骤，如图3B所示：
在步骤303a中，通过短信模板识别敏感信息在短信息中的位置。
短信息组件可以根据短信模板识别敏感信息在短信息中的位置，短信息组件中预先存储有多种携带有敏感信息的短信模板，并存储有与短信模板对应的敏感信息的位置，比如：短信模板为“您正在使用小米公司进行付款，付款密码为xxxxx”，则短信息组件中存储有该短信模板，且在该短信模板对应的位置会存储有敏感信息的位置为关键字“付款密码为”之后的6位数字的信息；在识别短信息后，短信息组件将识别出携带有敏感信息的短信息与存储的短信模板进行匹配，从而获取敏感信息在短信息中的位置。
在步骤303b中，记录敏感信息在短信息中的位置。
短信息组件将获取到的敏感信息在短信息中的位置信息记录在该短信息的对应位置。
在步骤304中，通过操作系统接收第三方应用程序对短信息的读取请求。
第三方应用程序在需要读取短信息组件中的短信息时，首先向操作系统发送对短信息的读取请求，对应的，操作系统接收第三方应用程序对短信息的读取请求。
其中，第三方应用程序可以是短信息类应用、支付类应用和注册类应用等。本公开实施例不对第三方应用程序的类型进行定义。
在步骤305中，通过操作系统检测第三方应用程序是否具有短信读取权限。
操作系统中预先存储有各个第三方应用程序对短信读取的权限，在操作系统接收到某个第三方应用程序对短信息的读取请求时，操作系统首先获取预先存储的配置文件，检测该第三方应用程序是否存在于预先存储的配置文件中，若存在于配置文件中，则该第三方应用程序具有短信读取权 限；若不存在于配置文件中，则该第三方应用程序不具有短信读取权限。
在步骤306中，若第三方应用程序不具有短信读取权限，则操作系统不向短信息组件转发读取请求。
在步骤307中，若第三方应用程序具有短信读取权限，则通过操作系统向短信息组件转发读取请求。
若经过操作系统检测，第三方应用程序在操作系统层面中具有短信读取权限，则操作系统向短信息组件转发第三方应用程序的读取请求。
在步骤308中，通过短信息组件接收操作系统转发的读取请求。
短信息组件接收操作系统转发的读取请求。
比如：第三方应用程序“小米商城”向操作系统发送读取短信息组件中“小米支付”支付密码的短信息，则操作系统接收到读取请求后，检测“小米商城”在操作系统中是否具有读取短信息的权限，在具有读取权限时，将“小米商城”发送的读取请求转发给短信息组件，短信息组件接收操作系统转发的读取请求。
在步骤309中，通过短信息组件检测读取请求所要读取的短信息是否为携带有敏感信息的短信息。
短信息组件根据接收到的读取请求，获取读取请求中需要读取的短信息，检测读取请求中需要读取的短信息是否携带有标记，若携带有标记，则该短信息为携带有敏感信息的短信息；若没有标记，则该短信息未携带敏感信息。
在步骤310中，若读取请求所要读取的短信息不是携带有敏感信息的短信息，则短信息组件将短信息反馈给第三方应用程序。
在步骤311中，若读取请求所要读取的短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理。
若读取请求中需要读取的短信息是携带有敏感信息的短信息，则将短 信息中的敏感信息进行不可见处理。
可选地，不可见处理为至少将短信息中的敏感信息替换为预定符号；
比如：将短信息中的“您正在使用小米公司进行付款，付款密码为123456”处理为“您正在使用小米公司进行付款，付款密码为xxxxx”。如图4A所示
可选的，不可见处理为至少将短信息中的敏感信息替换为预定提示信息；
该预定提示信息用于提示用户使用指定应用程序查看敏感信息。
比如：将短信息中的“您正在使用小米公司进行付款，付款密码为123456”处理为：您正在使用小米公司进行付款，付款密码为“请使用系统短信应用查看”。如图4B所示
该预定提示信息还可以是超链接，该超链接被触发时，跳转至指定应用程序查看该敏感信息。
可选的，不可见处理为至少将短信息中的敏感信息进行加密；
比如：将短信息中的“您正在使用小米公司进行付款，付款密码为123456”处理为“您正在使用小米公司进行付款，付款密码为abcdef”。
在步骤312中，向第三方应用程序反馈处理后的短信息。
短信息组件将携带有敏感信息的短信息经过不可见处理后反馈给第三方应用程序。
需要说明的一点是：本实施例中对步骤301至步骤303与步骤304至步骤308之间的先后顺序不作具体限定。也即短信息组件识别短信息是否为携带有敏感信息的短信息的步骤可以在接收到操作系统转发的读取请求之后，也可以在接收到操作系统转发的读取请求之前预先识别出短信息是否为携带有敏感信息的短信息。
综上所述，本公开实施例中提供的短信读取方法，通过接收第三方应 用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的短信内容，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。
通过记录敏感信息的位置并将敏感信息的内容进行不可见处理后，避免了短信息中敏感信息的泄露；同时只针对携带有敏感信息的短信息进行不可见处理，达到了对单个短信粒度的权限控制的效果。
仅在短信息组件中增加了对短信息中的敏感信息的处理，从而实现对单个短信粒度的权限控制，达到了操作简便、易于实现的效果。
在图3A实施例中，步骤301中短信息组件识别短信息是否为携带有敏感信息的短信息的方法包括如下几种情况：
可选的，短信息组件可以根据接收到的短信息的发送方号码识别该短信息是否携带有敏感信息，通常情况下，短信息后台服务器中存储有一个列表，比如：该列表中存储有公司A和与公司A对应的短信号码有短信号码1和短信号码2、公司B和与公司B对应的短信号码有短信号码3和短信号码4以及公司C和与公司C对应的短信号码有短信号码5和短信号码6等等。
示例性的，短信息后台服务器中存储的列表如下表格一所示：
Figure PCTCN2015099988-appb-000001
Figure PCTCN2015099988-appb-000002
表一
当短信息组件接收到的短信息的发送方号码是短信号码5，则根据表一中对应的关系可知，该短信息的来源方是“公司C，短信息组件并将该短信息识别为携带有敏感信息的短信息。
可选的，短信息组件可以根据接收到的短信息的短信内容识别该短信息是否携带有敏感信息，比如：短信内容为“【阿三旅行·去啊】06-2207:15昆明长水机场--飞-08:55重庆江北机场2B降祥鹏航空8L9863，订单XXXXXXXXXXX正在付款，张无忌(票号：XXX-XXXXXXXXXX)。点击http://tb.cn/3eXI06y客户端查看行程详细信息。”则短信息组件根据短信内容中的关键字【阿三旅行·去啊】识别出该短信息为携带有敏感信息的短信息。
可选的，短信息组件还可以根据短信模板识别短信息是否携带有敏感信息，比如：短信息组件中预先存储有多种携带有敏感信息的短信模板，在接收到短信息时，短信息组件将接收到的短信息与存储的短信模板进行匹配，如果接收到的短信息与某一种短信模板相匹配，则该短信息被识别为携带有敏感信息的短信息。
比如：短信息1：发信人：140000621“【公司A】订单号XXXXXXXXXXX正在付款，验证码为XXXXXX。点击http://tb.cn/3eXI06y客户端查看详细信息。”
短信息2：发信人：140000622“【公司A】订单号XXXXXXXXXXX正在付款，验证码为XXXXXX。点击http://tb.cn/3eXI06y客户端查看详细信息。”
短信息1和短信息2是京东公司发送的短信息，短信息1的来源方标识是“140000621”，短信息2的来源方标识是“140000622”，两个来源方标识具有相同前缀“1400062”，同时，两个短信息中都有关键字“【公司A】”。
示意性地，以上述短信息1和上述短信息2构建的两个短信模板如下：
<支付模板一>→“【公司A】<订单号><验证码>。”
<支付模板二>→“【公司A】<订单号><验证码>。”
示例性地，短信息来源方标识特征和关键词两者的组合与提取模板之间的对应关系如下表二所示：
短信息的特征 短信模板
14000062X+【公司A】 <支付模板一>
14000062X+【公司A】 <支付模板二>
表二
当短信息组件中接收到的短信息中携带有“14000062X+【公司A】”的特征时，会与短信模板中的<支付模板二>相匹配，因此，短信息组件识别该短信息为携带有敏感信息的短信息。
比如：当在小米商城中选购商品后，点击提交订单，付款时选择获取手机验证码，60秒内与小米商城网站绑定的手机会接收到一条小米公司发送的验证码短信息。假定接收到的短信息为：发信人：160000621“【小米公司】订单号1111111正在付款，验证码为123456，请在5分钟内输入该验证码。”
第三方应用程序“小米商城”向操作系统发送读取请求，操作系统将第三方应用程序发送的读取请求转发给短信息组件，短信息组件获取读取请求后将短信息中的内容处理为“【小米公司】订单号1111111正在付款，验证码为XXXXXX，请在5分钟内输入该验证码。”反馈给第三方应用程序“小米商城”。
可选的，短信息组件获取读取请求后将短信息中的内容处理为“【小米公司】订单号1111111正在付款，验证码为abcdef，请在5分钟内输入该验证码。”反馈给第三方应用程序“小米商城”。
在图3A实施例中，操作系统向短信息组件中转发的读取请求都是第三 方应用程序发送的读取请求，而操作系统的默认短信应用程序也可以读取短信息组件的短信内容。请参考如下步骤，如图5所示：
在步骤501中，接收操作系统的默认短信应用程序对短信息的读取请求。
短信息组件接收操作系统的默认短信应用程序发送的读取请求，配置为读取短信息组件中的短信息。
在步骤502中，对默认短信应用程序的读取请求进行响应。
短信息组件在接收到默认短信应用程序发送的读取请求后，直接对该读取请求进行响应。
该默认短信应用程序包括移动终端自带的短信应用程序，或其它可信任的短信应用程序。
由于短信息组件中的短信息分为携带有敏感信息的短信息和普通短信息两类，所以第三方应用程序对短信息中的短信息读取也分为不同的两种情况。请参考如下步骤，如图6所示。
在步骤601中，第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态。
普通短信息是指未携带敏感信息的短信息，其短信内容处于可见状态。第三方应用程序只需拥有操作系统层面的短信读取权限，即可读取短信息组件中的普通短信息。
第三方应用程序将读取普通短信息的读取请求发送给操作系统，在第三方应用程序拥有短信读取权限时，操作系统将读取请求转发给短信息组件，短信息组件将普通短信息反馈给第三方应用程序。如图7A所示。
在步骤602中，第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
第三方应用程序读取携带有敏感信息的短信息的过程如图3A实施例 所示，短信息中的敏感信息为不可见状态，第三方应用程序读取到的携带有敏感信息的短信息中的敏感信息处于不可见状态。如图7B所示。
在图6实施例中，第三方应用程序对短信息组件中的短信息有两种不同的读取情况，而操作系统的默认短信应用程序对短信息组件中的短信息只有一种读取情况。请参考如下步骤(图6中未示出)：
在步骤603中，操作系统的默认短信应用程序读取短信息，短信息中的敏感信息为可见状态。
操作系统的默认短信应用程序可以直接读取短信息组件中的短信息，且短信息中的敏感信息为可见状态。
下述为本公开装置实施例，可以配置为执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
图8是根据一示例性实施例示出的一种短信读取装置的框图，以该短信读取装置可以通过软件或者硬件的结合实现成为移动终端的全部或一部分。该短信读取装置包括但不限于：
请求接收模块820，被配置为接收第三方应用程序对短信息的读取请求。
信息处理模块840，被配置为若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理。
信息反馈模块860，被配置为向第三方应用程序反馈处理后的短信息。
综上所述，本公开实施例中提供的短信读取装置，通过接收第三方应用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的全部短信，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程 序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。
图9是根据另一示例性实施例示出的一种短信读取装置的框图，以该短信读取装置可以通过软件或者硬件的结合实现成为移动终端的全部或一部分。该短信读取装置包括但不限于：
短信识别模块910，被配置为识别接收到的短信息是否为携带有敏感信息的短信息。
可选地，短信识别模块910，还被配置为通过短信息的特征信息识别短信息是否为携带有敏感信息的短信息，特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
位置记录模块920，被配置为若短信息是携带有敏感信息的短信息，则记录敏感信息在短信息中的位置。
可选的，位置记录模块920，包括：
识别子模块921，被配置为通过短信模板识别敏感信息在短信息中的位置；
记录子模块922，被配置为记录敏感信息在短信息中的位置。
请求接收模块930，被配置为接收第三方应用程序对短信息的读取请求。
可选地，请求接收模块930，包括：
读取接收子模块931，被配置为通过操作系统接收第三方应用程序对短信息的读取请求。
权限检测子模块932，被配置为通过操作系统检测第三方应用程序是否具有短信读取权限。
请求转发子模块933，被配置为在第三方应用程序具有短信读取权限时，通过操作系统向短信息组件转发读取请求。
信息接收子模块934，被配置为通过短信息组件接收操作系统转发的读取请求。
信息处理模块940，被配置为若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理。
可选的，信息处理模块940，被配置为至少将短信息中的敏感信息替换为预定符号；
可选的，信息处理模块940，被配置为至少将短信息中的敏感信息替换为预定提示信息；
可选的，信息处理模块940，被配置为至少将短信息中的敏感信息进行加密。
信息反馈模块950，被配置为向第三方应用程序反馈处理后的短信息。
综上所述，本公开实施例中提供的短信读取装置，通过接收第三方应用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的全部短信，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。
通过记录敏感信息的位置并将敏感信息的内容进行不可见处理后，避免了短信息中敏感信息的泄露；同时只针对携带有敏感信息的短信息进行不可见处理，达到了对单个短信粒度的权限控制的效果。
仅在短信息组件中增加了对短信息中的敏感信息的处理，从而实现对单个短信粒度的权限控制，达到了操作简便、易于实现的效果。
在图9实施例中，操作系统向短信息组件中转发的读取请求都是第三 方应用程序发送的读取请求，而操作系统的默认短信应用程序也可以读取短信息组件的短信内容。请参考如下模块，如图10所示：
默认接收模块1020，被配置为接收操作系统的默认短信应用程序对短信息的读取请求；
默认响应模块1040，被配置为对默认短信应用程序的读取请求进行响应。
由于短信息组件中的短信息分为携带有敏感信息的短信息和普通短信息两类，所以第三方应用程序对短信息中的短信息读取也分为不同的两种情况。请参考如下模块，如图11所示。
普通读取模块1120，被配置为第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态；
敏感读取模块1140，被配置为第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
操作系统的默认短信应用程序对普通短信息与携带有敏感信息的短信息的读取只有一种情况，请参考如下模块：
默认读取模块，被配置为操作系统的默认短信应用程序读取短信息，短信息中的敏感信息为可见状态。(图中未示出)
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开实施例还提供了一种短信读取装置，该装置可以配置为实现本公开实施例提供的短信读取方法。该装置包括：处理器；配置为存储处理器可执行指令的存储器；
其中，处理器被配置为：
接收第三方应用程序对短信息的读取请求；
若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行 不可见处理；
向第三方应用程序反馈处理后的短信息。
本公开实施例还提供了一种短信读取装置，该装置可以配置为实现本公开实施例提供的短信读取方法。该装置包括：处理器；配置为存储处理器可执行指令的存储器；
其中，处理器被配置为：
第三方应用程序读取普通短信息，普通短信息的短信内容为可见状态；
第三方应用程序读取携带有敏感信息的短信息，短信息中的敏感信息为不可见状态。
图12是根据一示例性实施例示出的一种短信读取装置的框图。例如，装置1200可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图12，装置1200可以包括以下一个或多个组件：处理组件1202，存储器1204，电源组件1206，多媒体组件1208，音频组件1210，输入/输出(I/O)接口1212，传感器组件1214，以及通信组件1216。
处理组件1202通常控制装置1200的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1202可以包括一个或多个处理器1218来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1202可以包括一个或多个模块，便于处理组件1202和其他组件之间的交互。例如，处理组件1202可以包括多媒体模块，以方便多媒体组件1208和处理组件1202之间的交互。
存储器1204被配置为存储各种类型的数据以支持在装置1200的操作。这些数据的示例包括用于在装置1200上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1204可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机 存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1206为装置1200的各种组件提供电力。电源组件1206可以包括电源管理系统，一个或多个电源，及其他与为装置1200生成、管理和分配电力相关联的组件。
多媒体组件1208包括在装置1200和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1208包括一个前置摄像头和/或后置摄像头。当装置1200处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1210被配置为输出和/或输入音频信号。例如，音频组件1210包括一个麦克风(MIC)，当装置1200处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1204或经由通信组件1216发送。在一些实施例中，音频组件1210还包括一个扬声器，配置为输出音频信号。
I/O接口1212为处理组件1202和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1214包括一个或多个传感器，配置为为装置1200提供各 个方面的状态评估。例如，传感器组件1214可以检测到装置1200的打开/关闭状态，组件的相对定位，例如组件为装置1200的显示器和小键盘，传感器组件1214还可以检测装置1200或装置1200一个组件的位置改变，用户与装置1200接触的存在或不存在，装置1200方位或加速/减速和装置1200的温度变化。传感器组件1214可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1214还可以包括光传感器，如CMOS或CCD图像传感器，配置为在成像应用中使用。在一些实施例中，该传感器组件1214还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1216被配置为便于装置1200和其他设备之间有线或无线方式的通信。装置1200可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1216经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件1216还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1200可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，配置为执行上述短信读取方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1204，上述指令可由装置1200的处理器1218执行以完成上述短信读取方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开实施例的其它实施方案。本申请旨在涵盖本公开实施例的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开实施例的一般性原理并包括本公开实施例未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开实施例的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开实施例并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开实施例的范围仅由所附的权利要求来限制。
工业实用性
通过接收第三方应用程序对短信息的读取请求；若短信息是携带有敏感信息的短信息，则将短信息中的敏感信息进行不可见处理；向第三方应用程序反馈处理后的短信息；解决了第三方应用程序在仅拥有操作系统层面的短信读取权限时即可读取短信息组件中的短信内容，从而导致恶意的应用程序通过读取短信息中的验证码获取执行敏感操作的权限的问题；达到了禁止第三方应用程序读取携带有敏感信息的短信息，从而避免了短信息中敏感信息泄露的效果，同时实现了对单个短信粒度的权限控制的效果。

Claims (20)

  1. 一种短信读取方法，包括：
    接收第三方应用程序对短信息的读取请求；
    若所述短信息是携带有敏感信息的短信息，则将所述短信息中的敏感信息进行不可见处理；
    向所述第三方应用程序反馈处理后的所述短信息。
  2. 根据权利要求1所述的方法，其中，所述将所述短信息中的敏感信息进行不可见处理，包括：
    至少将所述短信息中的敏感信息替换为预定符号；
    或，
    至少将所述短信息中的敏感信息替换为预定提示信息；
    或，
    至少将所述短信息中的敏感信息进行加密。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    识别接收到的短信息是否为携带有敏感信息的短信息；
    若所述短信息是携带有敏感信息的短信息，则记录所述敏感信息在所述短信息中的位置。
  4. 根据权利要求3所述的方法，其中，所述识别接收到的短信息是否为携带有敏感信息的短信息，包括：
    通过所述短信息的特征信息识别所述短信息是否为携带有敏感信息的短信息，所述特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
  5. 根据权利要求3所述的方法，其中，所述记录所述敏感信息在所述短信息中的位置，包括：
    通过短信模板识别所述敏感信息在所述短信息中的位置；
    记录所述敏感信息在所述短信息中的位置。
  6. 根据权利要求1至5任一所述的方法，其中，所述接收第三方应用程序对短信息的读取请求，包括：
    通过操作系统接收所述第三方应用程序对所述短信息的读取请求；
    通过所述操作系统检测所述第三方应用程序是否具有短信读取权限；
    若所述第三方应用程序具有短信读取权限，则通过所述操作系统向短信息组件转发所述读取请求；
    通过所述短信息组件接收所述操作系统转发的所述读取请求。
  7. 根据权利要求1至5任一所述的方法，其中，所述方法还包括：
    接收操作系统的默认短信应用程序对所述短信息的读取请求；
    对所述默认短信应用程序的所述读取请求进行响应。
  8. 一种短信读取方法，包括：
    第三方应用程序读取普通短信息，所述普通短信息的短信内容为可见状态；
    所述第三方应用程序读取携带有敏感信息的短信息，所述短信息中的所述敏感信息为不可见状态。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    操作系统的默认短信应用程序读取所述短信息，所述短信息中的所述敏感信息为可见状态。
  10. 一种短信读取装置，包括：
    请求接收模块，被配置为接收第三方应用程序对短信息的读取请求；
    信息处理模块，被配置为若所述短信息是携带有敏感信息的短信息，则将所述短信息中的敏感信息进行不可见处理；
    信息反馈模块，被配置为向所述第三方应用程序反馈处理后的所述短信息。
  11. 根据权利要求10所述的装置，其中，
    所述信息处理模块，被配置为至少将所述短信息中的敏感信息替换为预定符号；
    或，
    所述信息处理模块，被配置为至少将所述短信息中的敏感信息替换为预定提示信息；
    或，
    所述信息处理模块，被配置为至少将所述短信息中的敏感信息进行加密。
  12. 根据权利要求10所述的装置，其中，所述装置还包括：
    短信识别模块，被配置为识别接收到的短信息是否为携带有敏感信息的短信息；
    位置记录模块，被配置为若所述短信息是携带有敏感信息的短信息，则记录所述敏感信息在所述短信息中的位置。
  13. 根据权利要求12所述的装置，其中，
    所述短信识别模块，被配置为通过所述短信息的特征信息识别所述短信息是否为携带有敏感信息的短信息，所述特征信息包括：发送方号码、短信内容和短信模板中的至少一种。
  14. 根据权利要求12所述的装置，其中，所述位置记录模块，包括：
    识别子模块，被配置为通过短信模板识别所述敏感信息在所述短信息中的位置；
    记录子模块，被配置为记录所述敏感信息在所述短信息中的位置。
  15. 根据权利要求10至14任一所述的装置，其中，所述请求接收模块，包括：
    读取接收子模块，被配置为通过操作系统接收所述第三方应用程序对 所述短信息的读取请求；
    权限检测子模块，被配置为通过所述操作系统检测所述第三方应用程序是否具有短信读取权限；
    请求转发子模块，被配置为在所述第三方应用程序具有所述短信读取权限时，通过所述操作系统向短信息组件转发所述读取请求；
    信息接收子模块，被配置为通过所述短信息组件接收所述操作系统转发的所述读取请求。
  16. 根据权利要求10至14任一所述的装置，其中，所述装置，还包括：
    默认接收模块，被配置为接收操作系统的默认短信应用程序对所述短信息的读取请求；
    默认响应模块，被配置为对所述默认短信应用程序的所述读取请求进行响应。
  17. 一种短信读取装置，包括：
    普通读取模块，被配置为第三方应用程序读取普通短信息，所述普通短信息的短信内容为可见状态；
    敏感读取模块，被配置为所述第三方应用程序读取携带有敏感信息的短信息，所述短信息中的所述敏感信息为不可见状态。
  18. 根据权利要求17所述的装置，其中，所述装置，还包括：
    默认读取模块，被配置为操作系统的默认短信应用程序读取所述短信息，所述短信息中的所述敏感信息为可见状态。
  19. 一种短信读取装置，包括：
    处理器；
    配置为存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收第三方应用程序对短信息的读取请求；
    若所述短信息是携带有敏感信息的短信息，则将所述短信息中的敏感信息进行不可见处理；
    向所述第三方应用程序反馈处理后的所述短信息。
  20. 一种短信读取装置，包括：
    处理器；
    配置为存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    第三方应用程序读取普通短信息，所述普通短信息的短信内容为可见状态；
    所述第三方应用程序读取携带有敏感信息的短信息，所述短信息中的所述敏感信息为不可见状态。
PCT/CN2015/099988 2015-09-18 2015-12-30 短信读取方法及装置 Ceased WO2017045313A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
RU2016132970A RU2653291C2 (ru) 2015-09-18 2015-12-30 Способ и устройство для чтения сообщения службы коротких сообщений
MX2016010418A MX364614B (es) 2015-09-18 2015-12-30 Metodo y dispositivo para lectura de servicio de mensaje corto.
KR1020167026752A KR101811013B1 (ko) 2015-09-18 2015-12-30 단문 메시지 서비스 판독 방법 및 장치
JP2016556266A JP2017531842A (ja) 2015-09-18 2015-12-30 ショートメッセージの読取方法及び装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510600885.3A CN105260673A (zh) 2015-09-18 2015-09-18 短信读取方法及装置
CN201510600885.3 2015-09-18

Publications (1)

Publication Number Publication Date
WO2017045313A1 true WO2017045313A1 (zh) 2017-03-23

Family

ID=55100357

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099988 Ceased WO2017045313A1 (zh) 2015-09-18 2015-12-30 短信读取方法及装置

Country Status (8)

Country Link
US (1) US10021543B2 (zh)
EP (1) EP3144844B1 (zh)
JP (1) JP2017531842A (zh)
KR (1) KR101811013B1 (zh)
CN (1) CN105260673A (zh)
MX (1) MX364614B (zh)
RU (1) RU2653291C2 (zh)
WO (1) WO2017045313A1 (zh)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554745A (zh) * 2016-01-27 2016-05-04 广东欧珀移动通信有限公司 一种信息的管理方法及系统
CN106210238B (zh) * 2016-07-14 2019-11-29 北京小米移动软件有限公司 短信息存储方法及装置
CN106255077B (zh) * 2016-07-28 2019-06-14 武汉闪达科技有限公司 一种提高反馈时效及信息安全的短信发送系统及方法
CN106682485A (zh) * 2016-11-29 2017-05-17 维沃移动通信有限公司 一种验证码的处理方法和移动终端
CN106778330A (zh) * 2016-11-30 2017-05-31 维沃移动通信有限公司 一种保护短信隐私内容的方法及移动终端
CN106529277A (zh) * 2016-12-14 2017-03-22 北京小米移动软件有限公司 消息预览方法及装置
CN107347117A (zh) * 2017-08-07 2017-11-14 努比亚技术有限公司 一种短信管理方法、移动终端及计算机可读存储介质
CN107743179B (zh) * 2017-12-04 2019-11-15 维沃移动通信有限公司 信息处理方法、移动终端及操作系统
US11012435B2 (en) 2017-12-19 2021-05-18 International Business Machines Corporation Multi factor authentication
US11122033B2 (en) 2017-12-19 2021-09-14 International Business Machines Corporation Multi factor authentication
CN110022536A (zh) * 2018-01-08 2019-07-16 中国移动通信有限公司研究院 验证信息处理方法、通信设备、业务平台及存储介质
EP3756128A4 (en) * 2018-02-22 2021-08-18 Citrix Systems, Inc. SECURING MOBILE DEVICES VIA IMAGE EVALUATION OPERATIONS ELECTRONICALLY ANALYZING IMAGE DATA RECEIVED FROM MOBILE DEVICE CAMERAS
CN108763923A (zh) * 2018-03-21 2018-11-06 广东欧珀移动通信有限公司 信息处理方法、装置、终端设备及存储介质
KR102029969B1 (ko) * 2018-03-22 2019-10-08 주식회사 엘지유플러스 콘텐츠 제공 및 선호도 분석을 위한 장치 및 방법
CN109728996B (zh) * 2018-06-01 2021-05-11 平安科技（深圳）有限公司 通讯信息的展示方法、用户设备、存储介质及装置
CN110139230B (zh) * 2019-05-28 2021-11-09 北京小米移动软件有限公司 转发短信的方法、装置及智能设备
CN110601931B (zh) * 2019-09-10 2021-12-07 杭州行至云起科技有限公司 一种智能家居系统的批量配置方法及系统
US12021861B2 (en) * 2021-01-04 2024-06-25 Bank Of America Corporation Identity verification through multisystem cooperation
CN113407959B (zh) * 2021-06-11 2023-04-14 维沃移动通信（杭州）有限公司 操作执行方法、装置及电子设备
CN116975821B (zh) * 2023-04-18 2025-03-28 腾讯科技（深圳）有限公司 信息处理方法、装置、电子设备、存储介质及程序产品

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103106578A (zh) * 2012-12-13 2013-05-15 张德珍 移动互联网支付方法
CN104657674A (zh) * 2015-01-16 2015-05-27 北京邮电大学 一种手机中隐私数据的隔离保护系统及方法

Family Cites Families (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004102394A (ja) 2002-09-05 2004-04-02 Hitachi Ltd 自動券売機
US8406734B2 (en) * 2003-05-15 2013-03-26 Vodafone Group Plc Resource access control for mobile terminal
US7984488B2 (en) 2004-04-09 2011-07-19 Microsoft Corporation Credential roaming in electronic computing systems
CN100480948C (zh) 2004-06-25 2009-04-22 日本电气株式会社 移动终端、资源访问控制系统以及资源访问控制方法
US7908329B2 (en) * 2005-08-16 2011-03-15 Microsoft Corporation Enhanced e-mail folder security
JP2007164613A (ja) * 2005-12-15 2007-06-28 Hitachi Software Eng Co Ltd 電子メールの送受信方法及びプログラム
CN101072093B (zh) 2006-05-12 2010-11-24 中兴通讯股份有限公司 短信内容保护系统及方法
JP5689574B2 (ja) 2006-11-17 2015-03-25 任天堂株式会社 ゲーム装置、ゲームプログラム、ゲームシステムおよびゲーム制御方法
US9391997B2 (en) * 2007-08-23 2016-07-12 Intel Deutschland Gmbh Message processing apparatus, wireless device and method of storing a message in a wireless device
US8347396B2 (en) 2007-11-30 2013-01-01 International Business Machines Corporation Protect sensitive content for human-only consumption
CN101252748A (zh) 2008-04-11 2008-08-27 北京北纬通信科技股份有限公司 一种在移动终端上实现隐私短信的方法及其系统
US8561206B1 (en) 2008-07-01 2013-10-15 Mcafee, Inc. System, method, and computer program product for allowing access to data based on a recipient identifier included with the data
GB0816062D0 (en) * 2008-09-03 2008-10-08 Symbian Software Ltd Message storage and retrieval
US8307412B2 (en) * 2008-10-20 2012-11-06 Microsoft Corporation User authentication management
KR101277149B1 (ko) * 2008-11-06 2013-06-20 삼성전자주식회사 사용자 데이터 암호화 방법 및 장치
JP5322288B2 (ja) * 2009-05-29 2013-10-23 Ｎｅｃシステムテクノロジー株式会社 通信処理装置、通信処理方法、及びプログラム
DE102009025414A1 (de) 2009-06-16 2010-12-30 T-Mobile International Ag Verfahren zum Schützen von mit einer elektronischen Nachricht versendeten vertraulichen Daten
CN102103537A (zh) * 2009-12-17 2011-06-22 珠海市君天电子科技有限公司 一种发现安全软件之间兼容性问题的方法和装置
US20110207593A1 (en) 2010-02-25 2011-08-25 Carlos Duran Expansivity in Low Expansion Silica-Titania Glasses
WO2012046406A1 (ja) * 2010-10-04 2012-04-12 パナソニック株式会社 情報処理装置およびアプリケーション不正連携防止方法
CN102480726A (zh) 2010-11-24 2012-05-30 比亚迪股份有限公司 密码保护方法、密码保护系统及具有其的移动终端
JP5862122B2 (ja) 2010-12-03 2016-02-16 株式会社イトーキ ガラスパネルの取付構造
US20120157049A1 (en) 2010-12-17 2012-06-21 Nichola Eliovits Creating a restricted zone within an operating system
US20120192287A1 (en) * 2011-01-25 2012-07-26 Yigang Cai Text message security
US9251367B2 (en) * 2011-03-25 2016-02-02 Nec Corporation Device, method and program for preventing information leakage
US20120291103A1 (en) 2011-05-09 2012-11-15 Google Inc. Permission-based administrative controls
JP2013045384A (ja) * 2011-08-26 2013-03-04 Konica Minolta Business Technologies Inc アクセス制御システム及びアクセス制御プログラム
US20130097203A1 (en) 2011-10-12 2013-04-18 Mcafee, Inc. System and method for providing threshold levels on privileged resource usage in a mobile network environment
US9043918B2 (en) 2011-10-13 2015-05-26 Mcafee, Inc. System and method for profile based filtering of outgoing information in a mobile environment
CN103079113B (zh) 2011-10-26 2016-05-25 康佳集团股份有限公司 一种限时使用应用程序的智能电视及其控制方法
US8543821B1 (en) 2011-10-28 2013-09-24 Amazon Technologies, Inc. Scalably displaying sensitive data to users with varying authorization levels
CN103310135B (zh) 2012-03-13 2015-10-28 腾讯科技（深圳）有限公司 一种屏蔽应用权限的方法和移动终端
CN102810143B (zh) 2012-04-28 2015-01-14 天津大学 基于Android平台手机应用程序的安全检测系统及方法
US8732802B2 (en) 2012-08-04 2014-05-20 Facebook, Inc. Receiving information about a user from a third party application based on action types
JP2014039193A (ja) * 2012-08-17 2014-02-27 Ntt Docomo Inc 情報処理装置、管理装置、情報処理方法及びプログラム
KR101417334B1 (ko) 2012-08-31 2014-08-06 주식회사 팬택 모바일 디바이스 및 모바일 디바이스에서의 침입 차단 방법
CN102917346B (zh) 2012-10-17 2015-01-07 浙江大学城市学院 一种基于Android的应用程序运行时安全策略管理系统及方法
US20150220734A1 (en) 2012-10-19 2015-08-06 Mcafee, Inc. Mobile application management
US8913994B2 (en) 2012-11-02 2014-12-16 Lookout, Inc. System and method for call blocking and SMS blocking
CN103116716A (zh) 2013-01-25 2013-05-22 复旦大学 一种针对移动平台的低干扰的即时权限授予方法
WO2014172909A1 (en) * 2013-04-27 2014-10-30 Tencent Technology (Shenzhen) Company Limited Managing private information in instant messaging
CN103310169B (zh) 2013-04-28 2016-09-21 东莞宇龙通信科技有限公司 一种保护sd卡数据的方法和保护系统
CN103327492B (zh) 2013-06-04 2016-01-06 王天时 一种安卓手机入侵检测方法及其检测系统
KR101510150B1 (ko) 2013-07-05 2015-04-10 충남대학교산학협력단 메시지 가로채기 방지 방법 및 이를 이용하는 휴대 단말기
CN103514397A (zh) 2013-09-29 2014-01-15 西安酷派软件科技有限公司 一种服务器、终端及权限管理、许可方法
KR102072134B1 (ko) 2013-12-04 2020-01-31 주식회사 케이티 메시지 전송 장치, 메시지 서버 및 메시지 수신 장치
CN103686716B (zh) 2013-12-19 2017-01-11 复旦大学 安卓系统机密性完整性增强访问控制系统
KR102285850B1 (ko) 2013-12-24 2021-08-05 삼성전자주식회사 사용자 단말 장치, 통신 시스템 및 그 제어 방법
CN103761471A (zh) 2014-02-21 2014-04-30 北京奇虎科技有限公司 基于智能终端设备安装应用程序的方法与装置
CN103761472B (zh) 2014-02-21 2017-05-24 北京奇虎科技有限公司 基于智能终端设备的应用程序访问方法与装置
CN103916471A (zh) 2014-04-02 2014-07-09 小米科技有限责任公司 一种信息显示方法及装置
CN104009977B (zh) * 2014-05-09 2016-10-05 北京奇虎科技有限公司 一种信息保护的方法和系统
CN105207775B (zh) * 2014-05-30 2019-03-01 北京奇虎科技有限公司 验证信息的读取方法及装置
CN104125547B (zh) * 2014-07-18 2017-12-15 北京奇虎科技有限公司 处理短信的方法及短信处理装置
CN104202735A (zh) * 2014-08-11 2014-12-10 上海一端科技有限公司 一种隐藏短信的方法
CN104640116B (zh) * 2014-12-31 2018-05-29 广东欧珀移动通信有限公司 一种诈骗短信防护方法和通信终端
CN104768139B (zh) 2015-02-28 2019-07-12 北京奇艺世纪科技有限公司 一种短信发送的方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103106578A (zh) * 2012-12-13 2013-05-15 张德珍 移动互联网支付方法
CN104657674A (zh) * 2015-01-16 2015-05-27 北京邮电大学 一种手机中隐私数据的隔离保护系统及方法

Also Published As

Publication number Publication date
KR20170044057A (ko) 2017-04-24
MX2016010418A (es) 2017-12-07
RU2016132970A (ru) 2018-02-14
US20170086041A1 (en) 2017-03-23
EP3144844B1 (en) 2022-10-05
CN105260673A (zh) 2016-01-20
RU2653291C2 (ru) 2018-05-07
US10021543B2 (en) 2018-07-10
MX364614B (es) 2019-05-02
KR101811013B1 (ko) 2017-12-20
EP3144844A1 (en) 2017-03-22
JP2017531842A (ja) 2017-10-26

Similar Documents

Publication Publication Date Title
WO2017045313A1 (zh) 短信读取方法及装置
JP6339693B2 (ja) ショートメッセージの読取方法及び装置
EP2985975B1 (en) Method, apparatus and system for authenticating access and computer program
US10608988B2 (en) Method and apparatus for bluetooth-based identity recognition
CN106453052B (zh) 消息交互方法及装置
CN104376273A (zh) 一种数据访问控制方法和装置
WO2016155233A1 (zh) 智能场景删除方法和装置
EP3145152B1 (en) Short message service reading method and device
CN105912922A (zh) 信息的管理方法、装置及终端
CN104331672A (zh) 一种基于手环对图片进行保密处理的方法及装置
CN105681261A (zh) 安全认证方法及装置
CN109246094B (zh) 用户终端的验证方法、装置及存储介质
CN104506648B (zh) 主题分享方法和装置、智能终端和服务器
CN110139230B (zh) 转发短信的方法、装置及智能设备
CN108924136B (zh) 授权认证方法、装置及存储介质
CN106407818B (zh) 网络数据包加密方法及装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016132970

Country of ref document: RU

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/010418

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016556266

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20167026752

Country of ref document: KR

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15904000

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15904000

Country of ref document: EP

Kind code of ref document: A1