WO2017000483A1 - 提高充值安全性的方法和装置 - Google Patents

提高充值安全性的方法和装置 Download PDF

Info

Publication number
WO2017000483A1
WO2017000483A1 PCT/CN2015/095007 CN2015095007W WO2017000483A1 WO 2017000483 A1 WO2017000483 A1 WO 2017000483A1 CN 2015095007 W CN2015095007 W CN 2015095007W WO 2017000483 A1 WO2017000483 A1 WO 2017000483A1
Authority
WO
WIPO (PCT)
Prior art keywords
trusted
terminal
determining
information
contact information
Prior art date
Application number
PCT/CN2015/095007
Other languages
English (en)
French (fr)
Inventor
王斌
王广健
王硕
Original Assignee
小米科技有限责任公司
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 小米科技有限责任公司 filed Critical 小米科技有限责任公司
Priority to KR1020167001557A priority Critical patent/KR101736701B1/ko
Priority to RU2016111182A priority patent/RU2642407C2/ru
Priority to MX2016003766A priority patent/MX356740B/es
Priority to JP2017525670A priority patent/JP6279155B2/ja
Priority to BR112016004997-7A priority patent/BR112016004997A2/zh
Publication of WO2017000483A1 publication Critical patent/WO2017000483A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/04—Recording calls, or communications in printed, perforated or other permanent form
    • H04M15/06—Recording class or number of calling, i.e. A-party or called party, i.e. B-party
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/09—Third party charged communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/48—Secure or trusted billing, e.g. trusted elements or encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/856—Unsuccessful event
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/858—Request users acknowledgement prior to use
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H04M17/20—Prepayment of wireline communication systems, wireless communication systems or telephone systems with provision for recharging the prepaid account or card, or for credit establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H04M17/20—Prepayment of wireline communication systems, wireless communication systems or telephone systems with provision for recharging the prepaid account or card, or for credit establishment
    • H04M17/204—Prepayment of wireline communication systems, wireless communication systems or telephone systems with provision for recharging the prepaid account or card, or for credit establishment on-line recharging, e.g. cashless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/47—Fraud detection or prevention means

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method and apparatus for improving recharge security.
  • the payment method of the mobile terminal is not only paid to the counter of the operator's business hall, but more and more users choose to use the account payment method on the mobile terminal to recharge the number, thereby eliminating the need to go to the operator's business hall.
  • the trouble is very convenient and fast.
  • a user pays using a mobile terminal not only can the mobile terminal be recharged, but also other mobile terminals can be recharged.
  • the user enters the recharge interface on the mobile terminal, chooses to recharge the local number, or selects a contact number from the address book, and recharges the contact number, which is very flexible.
  • the present disclosure provides a method and apparatus for improving the security of recharging to avoid erroneous recharge and improve recharge security.
  • a method for improving recharge security comprising:
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number;
  • the first number is not a number corresponding to the first terminal.
  • the information of the first number is obtained, and whether the first number is a trusted number is determined according to the obtained information, including:
  • the information of the first number is obtained, and whether the first number is a trusted number is determined according to the obtained information, including:
  • the method further includes:
  • an apparatus for improving recharge security comprising:
  • a receiving module configured to receive a request for recharging the first number sent by the first terminal
  • An obtaining module configured to obtain information about the first number, and determine, according to the obtained information, whether the first number is a trusted number;
  • control module configured to: when determining that the first number is a trusted number, refill the first number, and when determining that the first number is not a trusted number, reminding the first terminal that the first number is not Trust number
  • the first number is not a number corresponding to the first terminal.
  • the obtaining module includes:
  • a first obtaining submodule configured to acquire a recharge history record of the first number
  • a first determining sub-module configured to determine, according to the recharge history record of the first number, whether the first number is recharged by a plurality of different users within a predetermined time range, and the number of recharges exceeds a specified number of times, and if so, Then determining that the first number is not a trusted number, otherwise determining that the first number is a trusted number.
  • the obtaining module includes:
  • a second obtaining submodule configured to acquire contact information of the first number and contact information of the first terminal
  • a second determining sub-module configured to determine, according to the contact information of the first number and the contact information of the first terminal, whether the number corresponding to the first number and the first terminal have an association relationship, if Yes, it is determined that the first number is a trusted number, otherwise, it is determined that the first number is not a trusted number.
  • the second determining submodule is configured to:
  • the control module is further configured to:
  • an apparatus for improving recharge security comprising:
  • processor executable instructions a processor and a memory for storing processor executable instructions
  • processor is configured to:
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number;
  • the first number is not a number corresponding to the first terminal.
  • the technical solution provided by the embodiment of the present disclosure may include the following beneficial effects: obtaining the information of the first number by receiving a request for recharging the first number sent by the first terminal, and determining, according to the obtained information, the first Whether the first number is a trusted number, and when the first number is a trusted number, the first number is recharged, and when the first number is not a trusted number, the first terminal is reminded to be the first
  • the number is not a trusted number, and when the number corresponding to the first terminal is recharged, it is first determined whether the number is recharged, and the recharge is performed when the number is confirmed as the trusted number, and the first terminal is alerted when the untrusted number is used.
  • FIG. 1 is a flow chart showing a method of improving recharge security according to an exemplary embodiment.
  • FIG. 2 is a flow chart showing a method of improving recharge security according to another exemplary embodiment.
  • FIG. 3 is a flow chart showing a method of improving recharge security according to another exemplary embodiment.
  • FIG. 4 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 5 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 6 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 7 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 8 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 9 is a block diagram of an apparatus for improving recharge security, according to another exemplary embodiment.
  • FIG. 1 is a flowchart of a method for improving recharge security according to an exemplary embodiment. As shown in FIG. 1 , the method is used in a server, and includes the following steps.
  • step S11 receiving a request for charging the first number sent by the first terminal
  • the first number is not the number corresponding to the first terminal.
  • the first terminal may be any type of terminal, including but not limited to: a computer, a mobile phone, a tablet computer, a notebook computer, and the like.
  • the recharge scenario in this embodiment is an application scenario in which the first terminal recharges other numbers except the own number.
  • step S12 the information of the first number is obtained, and according to the obtained information, it is determined whether the first number is a trusted number;
  • the information of the first number may be contact information or a recharge history record, etc., this embodiment does not do this. Specifically limited.
  • step S13 when it is determined that the first number is a trusted number, the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number.
  • the information about the first number is obtained, and determining whether the first number is a trusted number according to the obtained information includes:
  • the information about the first number is obtained, and determining whether the first number is a trusted number according to the obtained information includes:
  • the method further includes:
  • the user of the first terminal is asked whether to continue to recharge the first number, and after obtaining the confirmation of the user, the first number is recharged.
  • the method provided in this embodiment obtains the information of the first number by receiving the request for recharging the first number, and determines whether the first number is a trusted number according to the obtained information.
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number, and the implementation is implemented.
  • recharging a number corresponding to the first terminal it is first determined whether the number is recharged, and the recharge is performed when the number is confirmed as a trusted number, and the first terminal is remarked when the untrusted number is used, thereby greatly improving the security of recharging. Sex, avoiding the situation of incorrect recharge and preventing the user’s property from suffering loss.
  • FIG. 2 is a flowchart of a method for improving recharge security according to another exemplary embodiment. As shown in FIG. 2, the method is used in a server, and includes the following steps.
  • step S21 receiving a request for recharging the first number sent by the first terminal
  • the first number is not the number corresponding to the first terminal.
  • step S22 acquiring a recharge history record of the first number
  • each recharge record may include a plurality of information, including but not limited to: recharge time, recharge amount, payment account and many more.
  • step S23 based on the recharge history record of the first number, it is determined whether the first number is recharged by a plurality of different users within a predetermined time range and the number of recharges exceeds a specified number of times, and if yes, step S24 is performed. Otherwise, step S26 is performed;
  • the specified time can be set as needed, and the specific value is not limited in this embodiment. For example, it can be set to 10 hours, 1 day or 5 days, and so on.
  • the specified number of times may also be set as needed, and the specific value is not limited in this embodiment. For example, it can be set to 5 times, 10 times, 20 times, and the like.
  • the first number is A number is confirmed as an untrusted number.
  • step S24 it is determined that the first number is not a trusted number, and the first terminal is reminded that the first number is not a trusted number;
  • the content of the reminder can be set, for example, to remind the first terminal that the number has been recharged by a plurality of people in the near future, whether to continue (beware of being deceived), etc., etc., which is not specifically limited in this embodiment.
  • step S25 the user of the first terminal is inquired whether to continue to recharge the first number, and after obtaining the confirmation of the user, the first number is recharged, and the process ends;
  • step S26 it is determined that the first number is a trusted number, and the first number is recharged, and the process ends.
  • the method provided in this embodiment obtains a recharge history record of the first number by receiving a request for recharging the first number sent by the first terminal, and determines whether the first number is a trusted number according to the recharge history record. And determining, when the first number is a trusted number, recharging the first number, and when determining that the first number is not a trusted number, reminding the first terminal that the first number is not a trusted number, and Ask if the user of the first terminal continues The first number is recharged, and after the user is confirmed, the first number is recharged. When the number corresponding to the first terminal is recharged, it is determined whether the number is safe or not. When the number is trusted, the recharge is performed. When the number is not trusted, the first terminal is reminded, which greatly improves the security of recharging, avoids the situation of incorrect recharging, and prevents the user's property from being damaged.
  • FIG. 3 is a flowchart of a method for improving recharge security according to another exemplary embodiment. As shown in FIG. 3, the method is used in a server, and includes the following steps.
  • step S31 receiving a request for charging the first number sent by the first terminal
  • the first number is not the number corresponding to the first terminal.
  • step S32 the contact information of the first number and the contact information of the first terminal are obtained
  • the server may collect and store the contact information reported by the multiple terminals in advance, so as to obtain the required contact information when receiving the refill request.
  • the terminal will report the contact information when recharging, and optionally, the call record or the short message record, etc., so that the server can save and facilitate subsequent analysis and statistics.
  • step S33 determining, according to the contact information of the first number and the contact information of the first terminal, whether the number corresponding to the first number has an associated relationship, and if yes, executing step S34; Otherwise, step S35 is performed;
  • This step can include the following steps:
  • the contact of the second number corresponding to the first terminal includes the first number, and the first number is the contact of the second number.
  • the first terminal can confirm the first number as its own number. (ie the second number) of the friend, therefore, the first number is the trusted number.
  • the contact of any contact of the second number includes the first number, and the first number is a friend of the friend whose second number is the second number. In this case, the first terminal may also confirm the first number as a trust. number.
  • step S34 it is determined that the first number is a trusted number, and the first number is recharged, and the process ends;
  • step S35 it is determined that the first number is not a trusted number, and the first terminal is reminded that the first number is not a trusted number;
  • the content of the reminder can be set, for example, to remind the first terminal that the number is not a friend, is not a friend of the friend, does it continue?
  • step S36 the user of the first terminal is inquired whether to continue to recharge the first number. After obtaining the confirmation of the user, the first number is recharged, and the process ends.
  • the method provided in this embodiment obtains the contact information of the first number and the contact information of the first terminal by receiving a request for recharging the first number sent by the first terminal, and determining, according to the obtained information, Whether the first number is a trusted number, and when the first number is determined to be a trusted number, the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded The first number is not a trusted number, and the user of the first terminal is asked whether to continue to recharge the first number. After obtaining the confirmation of the user, the first number is recharged, and the first terminal is implemented. When the corresponding number is recharged, it is first determined whether the number is safe. If the number is confirmed as the trusted number, the first terminal is reminded, which greatly improves the security of the recharge and avoids the situation of incorrect recharge. To prevent the user's property from suffering losses.
  • FIG. 4 is a block diagram of an apparatus for improving recharge security according to another exemplary embodiment.
  • the apparatus includes a receiving module 121, an obtaining module 122, and a control module 123.
  • the receiving module 121 is configured to receive a request for recharging the first number sent by the first terminal;
  • the obtaining module 122 is configured to obtain the information of the first number, and determine, according to the obtained information, whether the first number is a trusted number;
  • the control module 123 is configured to: when determining that the first number is a trusted number, refill the first number, and when determining that the first number is not a trusted number, reminding the first terminal that the first number is not a trusted number ;
  • the first number is not the number corresponding to the first terminal.
  • the obtaining module 122 includes:
  • the first obtaining submodule 122a is configured to acquire a refill history record of the first number
  • the first determining sub-module 122b is configured to determine, according to the recharge history record of the first number, whether the first number is recharged by a plurality of different users within a predetermined time range and the number of recharges exceeds a specified number of times, and if so, Then determining that the first number is not a trusted number; otherwise, determining that the first number is a trusted number.
  • the obtaining module 122 includes:
  • the second obtaining sub-module 122c is configured to acquire the contact information of the first number and the contact information of the first terminal;
  • the second determining sub-module 122d is configured to determine, according to the contact information of the first number and the contact information of the first terminal, whether the number corresponding to the first number has an association relationship, and if yes, Then determining that the first number is a trusted number, otherwise, determining that the first number is not a trusted number.
  • the second determining submodule 122d is configured to:
  • control module 123 is further configured to:
  • the user of the first terminal is asked whether to continue to recharge the first number, and after obtaining the confirmation of the user, the first number is recharged.
  • the device provided in this embodiment obtains the information of the first number by receiving a request for recharging the first number, and determines whether the first number is a trusted number according to the obtained information.
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number, and the implementation is implemented.
  • recharging a number corresponding to the first terminal it is first determined whether the number is recharged, and the recharge is performed when the number is confirmed as a trusted number, and the first terminal is remarked when the untrusted number is used, thereby greatly improving the security of recharging. Sexuality, to avoid the occurrence of false recharge, to prevent the loss of the user's property.
  • FIG. 7 is a block diagram of an apparatus for improving recharge security according to another exemplary embodiment.
  • the apparatus includes: a processor 701 and a memory 702 for storing processor-executable instructions;
  • the processor 701 is configured to:
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number;
  • the first number is not the number corresponding to the first terminal.
  • FIG. 8 is a block diagram of an apparatus 1900 for improving refill security, according to another exemplary embodiment.
  • device 1900 can be provided as a server.
  • apparatus 1900 includes a processing component 1922 that further includes one or more processors, and memory resources represented by memory 1932 for storing instructions executable by processing component 1922, such as an application.
  • An application stored in memory 1932 can include one or more modules each corresponding to a set of instructions.
  • processing component 1922 is configured to execute instructions to perform any of the embodiments described above The method provided.
  • Apparatus 1900 can also include a power supply component 1926 configured to perform power management of apparatus 1900, a wired or wireless network interface 1950 configured to connect apparatus 1900 to the network, and an input/output (I/O) interface 1958.
  • Device 1900 can operate based on an operating system stored in memory 1932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • the device provided in this embodiment obtains the information of the first number by receiving a request for recharging the first number, and determines whether the first number is a trusted number according to the obtained information.
  • the first number is recharged, and when it is determined that the first number is not a trusted number, the first terminal is reminded that the first number is not a trusted number, and the implementation is implemented.
  • recharging a number corresponding to the first terminal it is first determined whether the number is recharged, and the recharge is performed when the number is confirmed as a trusted number, and the first terminal is remarked when the untrusted number is used, thereby greatly improving the security of recharging. Sexuality, to avoid the occurrence of false recharge, to prevent the loss of the user's property.
  • FIG. 9 is a block diagram of an apparatus 800 for improving refill security, according to another exemplary embodiment.
  • device 800 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.
  • device 800 can include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, And a communication component 816.
  • Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 802 can include one or more processors 820 to execute instructions to perform all or part of the steps of the methods provided by any of the above embodiments.
  • processing component 802 can include one or more modules to facilitate interaction between component 802 and other components.
  • processing component 802 can include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 804 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Electrically erasable programmable read only memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 806 provides power to various components of device 800.
  • Power component 806 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 800.
  • the multimedia component 808 includes a screen between the device 800 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 may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 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 810 is configured to output and/or input an audio signal.
  • the audio component 810 includes a microphone (MIC) that is configured to receive an external audio signal when the device 800 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 804 or transmitted via communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • the I/O interface 812 provides an interface between the processing component 802 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 814 includes one or more sensors for providing device 800 with a status assessment of various aspects.
  • sensor assembly 814 can detect an open/closed state of device 800, a relative positioning of components, such as the display and keypad of device 800, and sensor component 814 can also detect a change in position of one component of device 800 or device 800. The presence or absence of user contact with device 800, device 800 orientation or acceleration/deceleration, and temperature variation of device 800.
  • Sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices.
  • the device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) Technology, Bluetooth (BT) technology and other technologies to achieve.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 800 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 for performing the steps of reporting contact information to the server, receiving a recharge reminder or confirmation returned by the server upon recharge.
  • 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 for performing the steps of reporting contact information to the server, receiving a recharge reminder or confirmation returned by the server upon recharge.
  • a non-transitory computer readable storage medium comprising instructions, such as a memory 804 comprising instructions executable by processor 820 of apparatus 800 to perform reporting of contact information to a server, Receive the recharge reminder or confirmation returned by the server during recharging.
  • the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • a non-transitory computer readable storage medium when instructions in the storage medium are executed by a processor of a mobile terminal, enabling the mobile terminal to perform reporting of contact information to the server, receiving a recharge reminder returned by the server upon recharging, or Confirm the steps.
  • the non-transitory computer readable storage medium provided in this embodiment can provide data to the server for analysis and statistics, and helps the server analyze the recharge number to determine whether it is a trusted number, thereby controlling the recharge behavior and improving the recharge. Safety, to avoid the occurrence of false recharge, to prevent the loss of the user's property.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Databases & Information Systems (AREA)
  • Accounting & Taxation (AREA)
  • Business, Economics & Management (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Alarm Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本发明提供了一种提高充值安全性的方法和装置，属于通信领域。所述方法包括：接收第一终端发送的对第一号码进行充值的请求（S11）；获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码（S12）；在确定该第一号码是信任号码时，对该第一号码进行充值，在确定该第一号码不是信任号码时，提醒该第一终端该第一号码不是信任号码（S13）；其中，该第一号码不是该第一终端对应的号码。所述装置包括：接收模块、获取模块和控制模块。本发明极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。

Description

提高充值安全性的方法和装置
本申请基于申请号为201510386177.4、申请日为2015年06月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通信领域，尤其涉及一种提高充值安全性的方法和装置。
背景技术
目前，移动终端的支付方式已经不仅仅是去运营商营业厅柜台支付了，越来越多的用户选择在移动终端上使用账号支付的方式来给号码充值，从而省去了去运营商营业厅的麻烦，非常方便、快捷。用户使用移动终端支付时，不仅可以给自己的移动终端充值，也可以给其他移动终端充值。例如，用户在移动终端上进入充值界面，选择给本机号码充值，或者从通讯录中选择一个联系人号码，给该联系人号码充值，非常灵活。
发明内容
有鉴于此，本公开提供了一种提高充值安全性的方法和装置，以避免误充值，提高充值安全性。
根据本公开实施例的第一方面，提供一种提高充值安全性的方法，所述方法包括：
接收第一终端发送的对第一号码进行充值的请求；
获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
其中，所述第一号码不是所述第一终端对应的号码。
其中，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，包括：
获取所述第一号码的充值历史记录；
根据所述第一号码的充值历史记录，判断所述第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定所述第一号码不是信任号码， 否则，确定所述第一号码是信任号码。
其中，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，包括：
获取所述第一号码的联系人信息和所述第一终端的联系人信息；
根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
其中，根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码，包括：
根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一终端对应的第二号码的联系人中是否包括所述第一号码，或者所述第二号码的任一联系人的联系人中是否包括所述第一号码，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
其中，提醒所述第一终端所述第一号码不是信任号码之后，还包括：
询问所述第一终端的用户是否继续给所述第一号码充值，在得到所述用户的确认后，对所述第一号码进行充值。
根据本公开实施例的第二方面，提供一种提高充值安全性的装置，所述装置包括：
接收模块，用于接收第一终端发送的对第一号码进行充值的请求；
获取模块，用于获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
控制模块，用于在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
其中，所述第一号码不是所述第一终端对应的号码。
其中，所述获取模块包括：
第一获取子模块，用于获取所述第一号码的充值历史记录；
第一判断子模块，用于根据所述第一号码的充值历史记录，判断所述第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定所述第一号码不是信任号码，否则，确定所述第一号码是信任号码。
其中，所述获取模块包括：
第二获取子模块，用于获取所述第一号码的联系人信息和所述第一终端的联系人信息；
第二判断子模块，用于根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
其中，所述第二判断子模块用于：
根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一终端对应的第二号码的联系人中是否包括所述第一号码，或者所述第二号码的任一联系人的联系人中是否包括所述第一号码，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
其中，所述控制模块还用于：
提醒所述第一终端所述第一号码不是信任号码之后，询问所述第一终端的用户是否继续给所述第一号码充值，在得到所述用户的确认后，对所述第一号码进行充值。
根据本公开实施例的第三方面，提供一种提高充值安全性的装置，所述装置包括：
处理器及用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收第一终端发送的对第一号码进行充值的请求；
获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
其中，所述第一号码不是所述第一终端对应的号码。
本公开的实施例提供的技术方案可以包括以下有益效果：通过接收第一终端发送的对第一号码进行充值的请求，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制 本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是根据一示例性实施例示出的一种提高充值安全性的方法的流程图。
图2是根据另一示例性实施例示出的一种提高充值安全性的方法的流程图。
图3是根据另一示例性实施例示出的一种提高充值安全性的方法的流程图。
图4是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
图5是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
图6是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
图7是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
图8是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
图9是根据另一示例性实施例示出的一种提高充值安全性的装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
图1是根据一示例性实施例示出的一种提高充值安全性的方法的流程图，如图1所示，该方法用于服务器中，包括以下步骤。
在步骤S11中，接收第一终端发送的对第一号码进行充值的请求；
其中，该第一号码不是该第一终端对应的号码。
本实施例中，第一终端可以为任意类型的终端，包括但不限于：计算机、手机、平板电脑、笔记本电脑等等。
本实施例中的充值场景为第一终端给除自身号码以外的其它号码进行充值的应用场景。
在步骤S12中，获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码；
其中，第一号码的信息可以是联系人信息或者是充值历史记录等等，本实施例对此不做 具体限定。
在步骤S13中，在确定该第一号码是信任号码时，对该第一号码进行充值，在确定该第一号码不是信任号码时，提醒该第一终端该第一号码不是信任号码。
本实施例中，可选的，获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码，包括：
获取该第一号码的充值历史记录；
根据该第一号码的充值历史记录，判断该第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定该第一号码不是信任号码，否则，确定该第一号码是信任号码。
本实施例中，可选的，获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码，包括：
获取该第一号码的联系人信息和该第一终端的联系人信息；
根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一号码与该第一终端对应的号码是否具有关联关系，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码。
本实施例中，可选的，根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一号码与该第一终端对应的号码是否具有关联关系，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码，包括：
根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一终端对应的第二号码的联系人中是否包括该第一号码，或者该第二号码的任一联系人的联系人中是否包括该第一号码，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码。
本实施例中，可选的，提醒该第一终端该第一号码不是信任号码之后，还包括：
询问该第一终端的用户是否继续给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值。
本实施例提供的上述方法，通过接收第一终端发送的对第一号码进行充值的请求，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受 损失。
图2是根据另一示例性实施例示出的一种提高充值安全性的方法的流程图，如图2所示，该方法用于服务器中，包括以下步骤。
在步骤S21中，接收第一终端发送的对第一号码进行充值的请求；
其中，该第一号码不是该第一终端对应的号码。
在步骤S22中，获取该第一号码的充值历史记录；
其中，充值历史记录为服务器在第一号码每次充值时进行记录并存储，从而得到多条充值记录，每一条充值记录可以包括多种信息，包括但不限于：充值时间、充值金额、付款账户等等。
在步骤S23中，根据该第一号码的充值历史记录，判断该第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则执行步骤S24，否则，执行步骤S26；
其中，所述规定的时间可以根据需要设置，本实施例对具体数值不限定。例如，可以设置为10小时、1天或5天等等。所述指定的次数也可以根据需要设置，本实施例对具体数值不限定。例如，可以设置为5次、10次、20次等等。
其中，多个不同的用户对第一号码进行充值，有可能是该多个用户被同一个非法用户所骗，并且均向该非法用户的号码进行充值，因此，这种情况下就将该第一号码确认为非信任号码。
在步骤S24中，确定该第一号码不是信任号码，提醒该第一终端该第一号码不是信任号码；
其中，提醒的内容可以设置，如提醒第一终端“该号码近期已被多人充值，是否继续(谨防受骗)？”等，本实施例对此不做具体限定。
在步骤S25中，询问该第一终端的用户是否继续给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值，流程结束；
在步骤S26中，确定该第一号码是信任号码，对该第一号码进行充值，流程结束。
本实施例提供的上述方法，通过接收第一终端发送的对第一号码进行充值的请求，获取所述第一号码的充值历史记录，根据该充值历史记录判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，并询问该第一终端的用户是否继续 给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
图3是根据另一示例性实施例示出的一种提高充值安全性的方法的流程图，如图3所示，该方法用于服务器中，包括以下步骤。
在步骤S31中，接收第一终端发送的对第一号码进行充值的请求；
其中，该第一号码不是该第一终端对应的号码。
在步骤S32中，获取该第一号码的联系人信息和该第一终端的联系人信息；
其中，服务器可以预先收集多个终端上报的联系人信息并存储，以便在接收到充值请求时获取需要的联系人信息。相应的，终端会在充值时上报联系人信息，可选的，还可以上报通话记录或者短信记录等等，以便服务器进行保存方便后续进行分析和统计。
在步骤S33中，根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一号码与该第一终端对应的号码是否具有关联关系，如果是，则执行步骤S34；否则，执行步骤S35；
本步骤可以包括以下步骤：
根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一终端对应的第二号码的联系人中是否包括该第一号码，或者该第二号码的任一联系人的联系人中是否包括该第一号码，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码。
其中，所述第一终端对应的第二号码的联系人中包括第一号码，是指第一号码是第二号码的联系人，这种情况下第一终端可以将第一号码确认为自身号码(即第二号码)的好友，因此，该第一号码为信任号码。所述第二号码的任一联系人的联系人中包括该第一号码，是指第一号码是第二号码的好友的好友，这种情况下第一终端也可以将第一号码确认为信任号码。
在步骤S34中，确定该第一号码是信任号码，对该第一号码进行充值，流程结束；
在步骤S35中，确定该第一号码不是信任号码，提醒该第一终端该第一号码不是信任号码；
其中，提醒的内容可以设置，如提醒第一终端“该号码非好友，也非好友的好友，是否继续？”等等，本实施例对此不做具体限定。
在步骤S36中，询问该第一终端的用户是否继续给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值，流程结束。
本实施例提供的上述方法，通过接收第一终端发送的对第一号码进行充值的请求，获取该第一号码的联系人信息和该第一终端的联系人信息，并根据获取的信息判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，并询问该第一终端的用户是否继续给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
图4是根据另一示例性实施例示出的一种提高充值安全性的装置框图。参照图4，该装置包括接收模块121，获取模块122和控制模块123。
该接收模块121被配置为，接收第一终端发送的对第一号码进行充值的请求；
该获取模块122被配置为，获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码；
该控制模块123被配置为，在确定该第一号码是信任号码时，对该第一号码进行充值，在确定该第一号码不是信任号码时，提醒该第一终端该第一号码不是信任号码；
其中，该第一号码不是该第一终端对应的号码。
参见图5，本实施例中，可选的，该获取模块122包括：
第一获取子模块122a，被配置为获取该第一号码的充值历史记录；
第一判断子模块122b，被配置为根据该第一号码的充值历史记录，判断该第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定该第一号码不是信任号码，否则，确定该第一号码是信任号码。
参见图6，本实施例中，可选的，该获取模块122包括：
第二获取子模块122c，被配置为获取该第一号码的联系人信息和该第一终端的联系人信息；
第二判断子模块122d，被配置为根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一号码与该第一终端对应的号码是否具有关联关系，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码。
本实施例中，可选的，该第二判断子模块122d被配置为：
根据该第一号码的联系人信息和该第一终端的联系人信息，判断该第一终端对应的第二号码的联系人中是否包括该第一号码，或者该第二号码的任一联系人的联系人中是否包括该第一号码，如果是，则确定该第一号码是信任号码，否则，确定该第一号码不是信任号码。
本实施例中，可选的，该控制模块123还用于：
提醒该第一终端该第一号码不是信任号码之后，询问该第一终端的用户是否继续给该第一号码充值，在得到该用户的确认后，对该第一号码进行充值。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本实施例提供的上述装置，通过接收第一终端发送的对第一号码进行充值的请求，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
图7是根据另一示例性实施例示出的一种提高充值安全性的装置框图。参照图7，该装置包括：处理器701及用于存储处理器可执行指令的存储器702；
其中，该处理器701被配置为：
接收第一终端发送的对第一号码进行充值的请求；
获取该第一号码的信息，根据获取的该信息判断该第一号码是否为信任号码；
在确定该第一号码是信任号码时，对该第一号码进行充值，在确定该第一号码不是信任号码时，提醒该第一终端该第一号码不是信任号码；
其中，该第一号码不是该第一终端对应的号码。
图8是根据另一示例性实施例示出的一种提高充值安全性的装置1900的框图。例如，装置1900可以被提供为一服务器。参照图8，装置1900包括处理组件1922，其进一步包括一个或多个处理器，以及由存储器1932所代表的存储器资源，用于存储可由处理部件1922的执行的指令，例如应用程序。存储器1932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1922被配置为执行指令，以执行上述任一实施例 提供的方法。
装置1900还可以包括一个电源组件1926被配置为执行装置1900的电源管理，一个有线或无线网络接口1950被配置为将装置1900连接到网络，和一个输入输出(I/O)接口1958。装置1900可以操作基于存储在存储器1932的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
本实施例提供的上述装置，通过接收第一终端发送的对第一号码进行充值的请求，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码，实现了在对非所述第一终端对应的号码进行充值时，先确定该号码充值是否安全，确认为信任号码时才进行充值，非信任号码时对第一终端进行提醒，极大地提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
图9是根据另一示例性实施例示出的一种提高充值安全性的装置800的框图。例如，装置800可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图9，装置800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制装置800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件802可以包括一个或多个处理器820来执行指令，以完成上述任一实施例提供的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理部件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在装置800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件806为装置800的各种组件提供电力。电力组件806可以包括电源管理系统，一个或多个电源，及其他与为装置800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述装置800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当装置800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为装置800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为装置800的显示器和小键盘，传感器组件814还可以检测装置800或装置800一个组件的位置改变，用户与装置800接触的存在或不存在，装置800方位或加速/减速和装置800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于装置800和其他设备之间有线或无线方式的通信。装置800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信部件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信部件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB) 技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行向服务器上报联系人信息、在充值时接收服务器返回的充值提醒或确认等步骤。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由装置800的处理器820执行以完成向服务器上报联系人信息、在充值时接收服务器返回的充值提醒或确认等步骤。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
一种非临时性计算机可读存储介质，当所述存储介质中的指令由移动终端的处理器执行时，使得移动终端能够执行向服务器上报联系人信息、在充值时接收服务器返回的充值提醒或确认等步骤。
本实施例提供的非临时性计算机可读存储介质，能够提供数据给服务器进行分析统计，有助于服务器对充值号码进行分析以确定是否为信任号码，从而对充值行为进行控制，提高了充值的安全性，避免出现误充值的情况，防止用户的财产遭受损失。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本申请旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (11)

  1. 一种提高充值安全性的方法，其特征在于，所述方法包括：
    接收第一终端发送的对第一号码进行充值的请求；
    获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
    在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
    其中，所述第一号码不是所述第一终端对应的号码。
  2. 根据权利要求1所述的方法，其特征在于，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，包括：
    获取所述第一号码的充值历史记录；
    根据所述第一号码的充值历史记录，判断所述第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定所述第一号码不是信任号码，否则，确定所述第一号码是信任号码。
  3. 根据权利要求1所述的方法，其特征在于，获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码，包括：
    获取所述第一号码的联系人信息和所述第一终端的联系人信息；
    根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
  4. 根据权利要求3所述的方法，其特征在于，根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码，包括：
    根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一终端对应的第二号码的联系人中是否包括所述第一号码，或者所述第二号码的任一联系人的联系人中是否包括所述第一号码，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
  5. 根据权利要求1所述的方法，其特征在于，提醒所述第一终端所述第一号码不是信任号码之后，还包括：
    询问所述第一终端的用户是否继续给所述第一号码充值，在得到所述用户的确认后，对所述第一号码进行充值。
  6. 一种提高充值安全性的装置，其特征在于，所述装置包括：
    接收模块，用于接收第一终端发送的对第一号码进行充值的请求；
    获取模块，用于获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
    控制模块，用于在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
    其中，所述第一号码不是所述第一终端对应的号码。
  7. 根据权利要求6所述的装置，其特征在于，所述获取模块包括：
    第一获取子模块，用于获取所述第一号码的充值历史记录；
    第一判断子模块，用于根据所述第一号码的充值历史记录，判断所述第一号码是否在规定的时间范围内被多个不同的用户充值且充值次数超过指定的次数，如果是，则确定所述第一号码不是信任号码，否则，确定所述第一号码是信任号码。
  8. 根据权利要求6所述的装置，其特征在于，所述获取模块包括：
    第二获取子模块，用于获取所述第一号码的联系人信息和所述第一终端的联系人信息；
    第二判断子模块，用于根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一号码与所述第一终端对应的号码是否具有关联关系，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
  9. 根据权利要求8所述的装置，其特征在于，所述第二判断子模块用于：
    根据所述第一号码的联系人信息和所述第一终端的联系人信息，判断所述第一终端对应的第二号码的联系人中是否包括所述第一号码，或者所述第二号码的任一联系人的联系人中是否包括所述第一号码，如果是，则确定所述第一号码是信任号码，否则，确定所述第一号码不是信任号码。
  10. 根据权利要求6所述的装置，其特征在于，所述控制模块还用于：
    提醒所述第一终端所述第一号码不是信任号码之后，询问所述第一终端的用户是否继续给所述第一号码充值，在得到所述用户的确认后，对所述第一号码进行充值。
  11. 一种提高充值安全性的装置，其特征在于，所述装置包括：
    处理器及用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收第一终端发送的对第一号码进行充值的请求；
    获取所述第一号码的信息，根据获取的所述信息判断所述第一号码是否为信任号码；
    在确定所述第一号码是信任号码时，对所述第一号码进行充值，在确定所述第一号码不是信任号码时，提醒所述第一终端所述第一号码不是信任号码；
    其中，所述第一号码不是所述第一终端对应的号码。
PCT/CN2015/095007 2015-06-30 2015-11-19 提高充值安全性的方法和装置 WO2017000483A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020167001557A KR101736701B1 (ko) 2015-06-30 2015-11-19 요금충전 안전성을 향상시키는 방법과 장치
RU2016111182A RU2642407C2 (ru) 2015-06-30 2015-11-19 Способ и устройство для повышения безопасности при пополнении счета
MX2016003766A MX356740B (es) 2015-06-30 2015-11-19 Metodo y aparato para incrementar la seguridad en la recarga.
JP2017525670A JP6279155B2 (ja) 2015-06-30 2015-11-19 料金チャージの安全性を向上させる方法と装置
BR112016004997-7A BR112016004997A2 (zh) 2015-06-30 2015-11-19 And a method and a device for improving the safety of the recharge

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510386177.4A CN105101181B (zh) 2015-06-30 2015-06-30 提高充值安全性的方法和装置
CN201510386177.4 2015-06-30

Publications (1)

Publication Number Publication Date
WO2017000483A1 true WO2017000483A1 (zh) 2017-01-05

Family

ID=54580514

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/095007 WO2017000483A1 (zh) 2015-06-30 2015-11-19 提高充值安全性的方法和装置

Country Status (9)

Country Link
US (1) US9866705B2 (zh)
EP (1) EP3113469B1 (zh)
JP (1) JP6279155B2 (zh)
KR (1) KR101736701B1 (zh)
CN (1) CN105101181B (zh)
BR (1) BR112016004997A2 (zh)
MX (1) MX356740B (zh)
RU (1) RU2642407C2 (zh)
WO (1) WO2017000483A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11665609B2 (en) * 2020-07-29 2023-05-30 Dell Products, Lp System and method for network initiated embedded subscriber identity module profile changes

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102509223A (zh) * 2011-11-21 2012-06-20 快钱支付清算信息有限公司 一种针对移动终端刷卡收款的安全管理方法和系统
CN103096269A (zh) * 2013-01-15 2013-05-08 中国联合网络通信集团有限公司 代缴费提醒方法及装置
CN103812986A (zh) * 2012-11-14 2014-05-21 阿里巴巴集团控股有限公司 数据处理方法及装置
US20140372319A1 (en) * 2011-09-28 2014-12-18 Lionel Wolovitz Methods and apparatus for brokering a transaction
CN204347983U (zh) * 2015-01-16 2015-05-20 邵国辉 移动营业厅自助充值缴费系统

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8082210B2 (en) * 2003-04-29 2011-12-20 The Western Union Company Authentication for online money transfers
KR100648066B1 (ko) 2005-05-02 2006-11-23 주식회사 케이티프리텔 공중 전화기를 이용한 이동통신 선불 요금 충전 시스템 및방법
JP4738170B2 (ja) * 2005-12-28 2011-08-03 富士通株式会社 振込申込受付システム、振込申込受付方法、およびコンピュータプログラム
JP2007272410A (ja) * 2006-03-30 2007-10-18 Fujitsu Ltd 振込先の取引履歴に基づく振り込め詐欺注意喚起方法及び装置
US8472598B2 (en) * 2006-11-30 2013-06-25 Motorola Mobility Llc Prepaying usage time for another communication device
JP2008234300A (ja) * 2007-03-20 2008-10-02 Oki Electric Ind Co Ltd 取引管理システム、自動化機器、取引管理方法および勘定ホスト
US9557889B2 (en) * 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US8644474B2 (en) * 2009-07-01 2014-02-04 Matthew Finkle Method and system for connecting a telephone call to a third party
US20110137789A1 (en) * 2009-12-03 2011-06-09 Venmo Inc. Trust Based Transaction System
WO2012174427A2 (en) * 2011-06-16 2012-12-20 OneID Inc. Method and system for determining authentication levels in transactions
RU2479934C1 (ru) * 2011-12-16 2013-04-20 Вадим Николаевич Гуськов Способ получения информации о пополнении баланса сотового оператора пользователя и устройство для его реализации
US9867043B2 (en) * 2012-08-28 2018-01-09 Visa International Service Association Secure device service enrollment
CN104239758B (zh) * 2013-06-13 2018-04-27 阿里巴巴集团控股有限公司 一种人机识别方法及相应的人机识别系统
WO2015021336A1 (en) * 2013-08-07 2015-02-12 Lu Dat The Methods and systems for top-up

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140372319A1 (en) * 2011-09-28 2014-12-18 Lionel Wolovitz Methods and apparatus for brokering a transaction
CN102509223A (zh) * 2011-11-21 2012-06-20 快钱支付清算信息有限公司 一种针对移动终端刷卡收款的安全管理方法和系统
CN103812986A (zh) * 2012-11-14 2014-05-21 阿里巴巴集团控股有限公司 数据处理方法及装置
CN103096269A (zh) * 2013-01-15 2013-05-08 中国联合网络通信集团有限公司 代缴费提醒方法及装置
CN204347983U (zh) * 2015-01-16 2015-05-20 邵国辉 移动营业厅自助充值缴费系统

Also Published As

Publication number Publication date
KR101736701B1 (ko) 2017-05-16
KR20170012871A (ko) 2017-02-03
RU2642407C2 (ru) 2018-01-24
CN105101181B (zh) 2019-05-07
RU2016111182A (ru) 2017-09-28
JP6279155B2 (ja) 2018-02-14
EP3113469B1 (en) 2018-12-26
JP2017526317A (ja) 2017-09-07
US20170006167A1 (en) 2017-01-05
BR112016004997A2 (zh) 2020-05-12
US9866705B2 (en) 2018-01-09
CN105101181A (zh) 2015-11-25
EP3113469A1 (en) 2017-01-04
MX356740B (es) 2018-06-12
MX2016003766A (es) 2017-02-20

Similar Documents

Publication Publication Date Title
US10706173B2 (en) Method and device for displaying notification information
US10123196B2 (en) Method and device for alarm triggering
WO2016107030A1 (zh) 通知信息显示方法及装置
WO2015188588A1 (zh) 应用程序的删除提示方法和装置
US20170064182A1 (en) Method and device for acquiring image file
WO2017071078A1 (zh) 通讯模组固件和插件生成方法及装置
WO2016155232A1 (zh) 号码标记方法及装置
WO2017035994A1 (zh) 外接设备的连接方法及装置
US20160029419A1 (en) Methods and devices for connecting to wireless network
WO2016155231A1 (zh) 网络接入方法及装置
CN109669730B (zh) 一种进程保活方法、装置、电子设备及介质
WO2016119495A1 (zh) 语音提示方法及装置
EP3758400A1 (en) Prompt method, device and medium
WO2018000710A1 (zh) WiFi信号图标的展示方法、装置和移动终端
US9628966B2 (en) Method and device for sending message
WO2017088373A1 (zh) 账单处理方法、装置和终端设备
WO2016026277A1 (zh) 移动路由器的流量控制方法及装置
EP3160112B1 (en) Reminding method and device
WO2016015404A1 (zh) 呼叫转移的方法、装置及终端
CN106506808B (zh) 对通讯消息提示的方法及装置
EP3190555A1 (en) Method for operating a display device and display
US20170147593A1 (en) Contact managing method and apparatus, and storage medium
EP3032487A1 (en) Methods for granting qualification, method for acquiring qualification, and devices thereof
CN107894909B (zh) 限制Activity启动的方法、装置及存储介质
WO2017000483A1 (zh) 提高充值安全性的方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017525670

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020167001557

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/003766

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016111182

Country of ref document: RU

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: 15897010

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016004997

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112016004997

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160307

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15897010

Country of ref document: EP

Kind code of ref document: A1

ENPC Correction to former announcement of entry into national phase, pct application did not enter into the national phase

Ref country code: BR

Free format text: ANULADA A PUBLICACAO CODIGO 1.3 NA RPI NO 2430 DE 01/08/2017 POR TER SIDO INDEVIDA.

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112016004997

Country of ref document: BR

Kind code of ref document: A2

Free format text: APRESENTAR A TRADUCAO SIMPLES DA FOLHA DE ROSTO DA CERTIDAO DE DEPOSITO DA PRIORIDADE CN 201510386177.4 DE 30/06/2015 OU DECLARACAO CONTENDO, OBRIGATORIAMENTE, TODOS OS DADOS IDENTIFICADORES DESTA (DEPOSITANTE(S), INVENTOR(ES), NUMERO DE REGISTRO, DATA DE DEPOSITO E TITULO), CONFORME O PARAGRAFO UNICO DO ART. 25 DA RESOLUCAO 77/2013, UMA VEZ QUE NAO FOI POSSIVEL DETERMINAR O(S) TITULAR(ES) DA CITADA PRIORIDADE, NEM SEUS INVENTORES, INFORMACAO NECESSARIA PARA O EXAME.

ENP Entry into the national phase

Ref document number: 112016004997

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160307