CN110809266A - Mobile communication control method based on time tag - Google Patents

Mobile communication control method based on time tag Download PDF

Info

Publication number
CN110809266A
CN110809266A CN201810881668.XA CN201810881668A CN110809266A CN 110809266 A CN110809266 A CN 110809266A CN 201810881668 A CN201810881668 A CN 201810881668A CN 110809266 A CN110809266 A CN 110809266A
Authority
CN
China
Prior art keywords
mobile phone
phone number
account
verification code
time
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.)
Pending
Application number
CN201810881668.XA
Other languages
Chinese (zh)
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.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to CN201810881668.XA priority Critical patent/CN110809266A/en
Publication of CN110809266A publication Critical patent/CN110809266A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • 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
    • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A mobile communication control method based on time stamp. The invention discloses a target user identification method, which is used for identifying a target user of a message. The method is characterized in that the subscription time is stored in the subscription data of the user in the HLR, and for the received message carrying the destination number and the registration time, the HLR identifies the destination user of the message by comparing the registration time with the corresponding subscription time. Based on the identification method, a mobile communication control method is also provided, which can control the call flow. Based on the control method, an SMSC query routing method is also provided, so that the SMSC can provide a mechanism for controlling the sending of the short message to the mobile phone terminal or the application server. Based on the mechanism, a short message sending method is also provided, which can avoid sending the message of the old user to a number to the new user of the number. Based on the short message sending method, an account binding method is also provided, which can avoid the short message from being sent by mistake; and also provides an account creating method and an account owner identifying method.

Description

Mobile communication control method based on time tag
Technical Field
The present invention relates to mobile communication control, and more particularly, to a mobile communication control method based on a user tag, and a corresponding SMSC query routing method, short message sending method, and account binding method.
Background
In the field of telecommunications network communications, there is a phenomenon that subscriber a gives up, for some reason, the old cell phone number being used. And the old mobile phone number of the user A is registered and used by the user B. In this case, since the mobile communication network does not know that the owner of the old mobile phone number has changed, a short message that is sent to the user a by another person using the mobile phone number is sent to the user B, for example, the user B may receive a short message sent by a friend of the user a, which may cause annoyance to the user B, and leak privacy information of the user a and the friend of the user a, thereby bringing about a potential safety hazard to the user a and the friend of the user a. For example, there is often a reaction that the mobile phone receives a call from a friend of the user or a business related person who has used the current mobile phone number, or a short message.
For example, when a customer transacts a bank card or a credit card, a mobile phone number is registered, and for some reason, the customer changes the mobile phone number, but the mobile phone number registered in the bank forgets to be changed, and the original mobile phone number of the customer is registered and used by other users. In this case, when the bank for some reason wants to send information to the client by short message, the information will be sent to the other mobile phone users. Similar situations exist with various figure eight membership cards.
For example, the user a registers or binds an internet account number or a WeChat account number or a Paibao account number with a mobile phone number, or other online payment account numbers, or an account number of a 12306 train ticket booking system. When the user a forgets the login password of an account registered with a certain service provider, for example, a wechat account, the login password can be reset by inputting the mobile phone number. For example, after the user fails to log in the WeChat, the user can retrieve the password through a mobile phone: the method comprises the steps that a mobile phone number is input, a WeChat client sends the mobile phone number to a WeChat server, a corresponding server generates a verification code for identity verification according to the mobile phone number, the verification code is sent to a user, and the user logs in or modifies a login password by using the verification code received by the mobile phone. For example, the user sends the verification code received by the mobile phone to the server, and after the server passes the verification, the user is allowed to log in and modify the login password.
Particularly, some accounts can log in by directly using the mobile phone number, and when the password is unknown, the verification code generated by the server is directly obtained through the bound mobile phone number, and the password is reset through the verification code
The above fact is a kind of proof that the user's mobile phone number is used as the user's identity. The method and the system are convenient for users to use to a great extent, are convenient for service operation of service providers and reduce operation cost.
However, the above convenience poses a potential safety hazard. When the user a changes the mobile phone number for some reason, for example, the user a learns in Beijing and works in Shanghai after graduation, the old number used by the user a is released, and the user B can log in the corresponding account or payment system of the user a by using the old number according to the above-mentioned convenient service process after registering the old number which is logged out by the user a, unless the user a logs out the old number and immediately logs out or releases all binding services related to the old number, for example, releasing the binding between the old number and the WeChat account, releasing the binding between the old number and the Payment treasure account, releasing the binding between the old number and the booking system account, and the like. This is a distracting thing for user A! Moreover, the operation of unbinding a certain account is often missed because the account is sparse, so that a security risk is brought to the user A.
Disclosure of Invention
In view of the above, the present invention discloses a destination user identification method for identifying a destination user of a message. The method is characterized in that the subscription time is stored in the subscription data of the user, and for the received message carrying the destination number and the registration time, the HLR identifies the destination user of the message by comparing the registration time with the corresponding subscription time. Based on the identification method, a mobile communication control method is also provided, so that the HLR controls the route inquiry operation carrying the registration time in the calling process, thereby controlling the calling flow. Based on the control method, an SMSC query routing method is also provided, so that the SMSC can provide a mechanism for controlling the sending of the short message for the mobile phone terminal or the application server, and based on the mechanism, a short message sending method can be further provided. Based on the mechanism, a short message sending method is also provided, and the method is characterized in that the registration time of the corresponding mobile phone number is preserved in advance, and when the short message is sent, the short message is sent according to the destination number of the short message and the correspondingly preserved registration time, so that the message to be sent to an old user of a number is prevented from being sent to a new user of the number, the disturbance to a receiver is eliminated, and the message sender and the privacy of the old user of the number are protected. Based on the short message sending method, an account binding method is also provided, which can avoid the communication safety problems of short message missending and the like in a series of reality; based on the short message sending method, an account creating method and an account owner identification method are also provided, so that a new user with a mobile phone number can not enter an account registered by an old user of the mobile phone number, and the service capability of the new user for creating the own account according to the mobile phone number is provided.
Based on the series of technical means provided by the invention, the problems can be at least partially solved, or the solution of the corresponding problems can be pushed forward one step.
A destination subscriber identification method is used for an HLR to identify a destination subscriber of a message. According to the method, the subscription time of the mobile phone number is stored in the HLR, and for the message which is received by the HLR and carries the destination number and the registration time, the method comprises the following steps:
a. acquiring the signing time of the destination number;
b. comparing the registration time with the subscription time; if the number of the target number is smaller than the preset number, the target user of the message is a historical subscriber of the target number; otherwise, the destination user of the message is the current subscriber of the destination number.
A mobile communication control method, keep the subscription time of the mobile phone number in HLR, for route inquiry message carrying registration time that HLR receives, said method includes the following steps:
a. acquiring the signing time of the destination number of the message;
b. comparing the registration time with the subscription time; if the value is less than the preset value, processing according to a normal flow; otherwise, processing according to the abnormal flow.
Optionally, the processing according to the normal flow is: acquiring routing information corresponding to the destination number, and replying a query result to the requester; the processing according to the abnormal flow is as follows: an exception report is returned to the requestor.
An SMSC query routing method, comprising the steps of:
a. SMSC receives short message carrying destination number and registration time;
b. and the SMSC sends a routing query request to the HLR according to the destination number of the short message, wherein the request carries the registration time.
A short message sending method, the method preserves the registration time of the corresponding mobile phone number in advance, the method includes the following steps:
a. acquiring the registration time of the target number of the stored short message;
b. and taking the registration time of the destination number as the registration time of the message, and sending the short message to the SMSC according to the destination number.
A binding method is used for binding a mobile phone number to an account; the method comprises the following steps:
a. the application server receives a mobile phone number to be bound of a current account;
b. the application server generates a verification code; taking the current time value or date value as the registration time of the message, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the message carries the generated verification code;
c. the application server receives the verification code returned from the client, compares the verification code with the generated verification code, if the verification code is consistent with the generated verification code, establishes the corresponding relation between the corresponding account and the mobile phone number, and takes the current time value or date value as the registration time to be stored in the corresponding relation record.
An account creating method is used for creating an internet account according to a mobile phone number; the method comprises the following steps:
c. the server generates a verification code; according to the mobile phone number, the current time value is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
d. the server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code and the generated verification code are consistent, executes the step g: and creating an account, and storing the mobile phone number and the corresponding registration time in the account.
Optionally, the mobile phone number is carried in a registration request received by the server; further comprising step b before step c: the server searches the account bound by the mobile phone number, and if the account exists, the server enters an account owner confirmation process; otherwise, executing step c;
the account owner confirmation process comprises the following steps:
{
the server generates a verification code; according to the mobile phone number, the registration time value stored in the account is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
when the server receives an abnormal report which indicates that the signed user is changed and is returned by the mobile communication network, the server freezes or cancels the existing account, and then the step c is carried out;
when the server receives the verification code returned from the client, the server compares the received verification code with the generated verification code, and if the verification code is consistent with the generated verification code, the server confirms that the existing account is registered by the current subscriber of the mobile phone number
}；
Or, the account owner confirmation process includes:
{
the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
the server receives an abnormal report which carries the signing time of the mobile phone number and is returned by the mobile communication network; receiving a verification code returned from the client; comparing with the generated verification code, and if the verification code and the generated verification code are not consistent, ending the process; if the two are consistent, executing { comparing the registration time of the existing account with the signing time of the mobile phone number, { freezing or logging out the existing account if the registration time of the existing account is less than the signing time of the mobile phone number, { creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, flow in the process of confirming that the existing account is registered by the current signed user of the mobile phone number
}。
Optionally, the mobile phone number is carried in a registration request received by the server; step c is further: the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
in step d, the server further receives an exception report carrying the subscription time of the mobile phone number, which is returned by the mobile communication network;
step g is further:
g01, the server searches the account bound by the mobile phone number, and if the account exists, the server enters an account owner confirmation process; otherwise, creating an account, and storing the mobile phone number and the corresponding registration time in the account;
the account owner confirmation process comprises the following steps: comparing the registration time of the existing account with the signing time of the mobile phone number, if the registration time of the existing account is less than the signing time of the mobile phone number, freezing or logging off the existing account, creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, confirming that the existing account is registered by the current subscriber of the mobile phone number.
An owner identification method for identifying an owner of an existing account of a mobile phone number, the method comprising the steps of:
a. the server generates a verification code; according to the mobile phone number, the registration time value stored in the account is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
b. when the server receives an abnormal report which indicates that the subscriber is changed and is returned by the mobile communication network, the server freezes or logs off the existing account, and then executes an account creating process: { according to the mobile phone number, taking the current time value as the registration time of the message, and sending the generated verification code to the mobile communication network through the short message; receiving a verification code returned from the client, comparing the verification code with the generated verification code, if the verification code and the generated verification code are consistent, creating an account, and storing the mobile phone number and the corresponding registration time in the account };
and when receiving the verification code returned from the client, the server compares the received verification code with the generated verification code, and if the received verification code is consistent with the generated verification code, the server confirms that the existing account is registered by the current subscriber of the mobile phone number.
An owner identification method for identifying an owner of an existing account of a mobile phone number, the method comprising the steps of:
a. the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
b. the server receives the abnormal report which carries the signing time of the mobile phone number and is returned by the mobile communication network; receiving the verification code returned from the client, comparing the verification code with the generated verification code, and ending the process if the verification code and the generated verification code are not consistent; if the two are consistent, executing step c;
c. comparing the registration time of the existing account with the signing time of the mobile phone number, if the registration time of the existing account is less than the signing time of the mobile phone number, freezing or logging off the existing account, creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, confirming that the existing account is registered by the current subscriber of the mobile phone number.
In the technical solution provided in the above embodiment, the subscription time is saved in the user subscription data, so that the target user of the message carrying the registration time can be effectively identified, and thus, in the call process, the call flow is controlled by controlling the route query operation carrying the registration time. Based on the method, the corresponding SMSC query routing method can be further realized, so that the SMSC can provide a mechanism for controlling the sending of the short message like a mobile phone terminal or an application server; based on the mechanism, the method can further provide a short message sending method, which sends the short message according to the destination number of the short message and the corresponding stored registration time when sending the short message by pre-storing the registration time of the corresponding mobile phone number, thereby avoiding sending the message to be sent to an old user of a number to a new user of the number, eliminating harassment to a receiver, protecting the message sender and the privacy of the old user of the number, and improving the overall security of the communication between a telecommunication network and the internet.
In the technical solution provided in the foregoing embodiment, because a registration time factor is introduced into the binding relationship, messages can be filtered through the subscription time of a mobile phone number, and then a short message that an application server wants to send to an old user of a mobile phone number bound to a corresponding account is not sent to a new user of the mobile phone number, so that a phenomenon of missending of a verification code can be avoided, and security risks caused when a user changes a mobile phone number, such as a mobile phone number logging in WeChat, a mobile phone number logging in a Payment treasure, a mobile phone receiving verification code sent by an application server, and the like, which widely exist at present, can be effectively eliminated.
In the technical scheme provided by the embodiment, because the registration time factor is introduced into the binding relationship, when a user creates an account according to a mobile phone number, the safety of an old user of the mobile phone number can be guaranteed, and the new user of the mobile phone number is not influenced to create the own account.
Drawings
Fig. 1 is a flowchart of a general embodiment of a user identification method according to the present invention.
Fig. 2 is a flowchart of a general embodiment of a communication control method according to the present invention.
Fig. 3 is a flowchart illustrating a communication control method according to an embodiment of the present invention.
Fig. 4 is a flowchart of an embodiment of the communication control method of the present invention considering compatibility.
Fig. 5 is a flowchart illustrating a short message sending method according to an embodiment of the present invention.
Fig. 6 is a flowchart of an embodiment of a method for establishing a binding relationship.
FIG. 7 is a flowchart of an embodiment of a method for account registration.
Fig. 8 is a flowchart of an embodiment of creating a new account.
FIG. 9 is a flowchart of an embodiment of a method for account registration.
FIG. 10 is a flowchart of an embodiment of account owner validation.
Fig. 11 is a flowchart of an embodiment of the communication control method of the present invention considering special values.
FIG. 12 is a flow diagram illustrating an embodiment of considering special values for account owner validation.
FIG. 13 is a flowchart of an embodiment of a method for account registration.
Acronyms
ESME: (External Short Message Entity);
HLR: (Home Location Register );
MSC: (Mobile Switching Center);
GMSC: (Gateway Mobile Switching Center);
SME (simple substance extraction) is as follows: (Short Message Entity);
SMSC: (Short Message Service Center);
and (4) UUS: (User-to-User signaling);
VLR: (Visitor Location Register ).
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following detailed description is given in various aspects in conjunction with the embodiments.
For convenience of description, the SMSC is considered to be part of the mobile communication network.
In the invention, the account can be an internet account or a bank account.
In the invention, a user who signs a contract and uses a mobile phone number is called a current signing user of the mobile phone number, and a user who signs a contract and uses the mobile phone number before the current signing user of the mobile phone number is called a historical signing user of the mobile phone number. As can be seen, the current subscriber and the historical subscriber are for a certain point in time.
Obviously, there may be a plurality of historical subscribers for one mobile phone number.
According to the prior art, when a user calls a mobile phone number, a mobile communication network cannot identify an actual destination user that the calling user wants to call, namely, cannot identify an expected destination user of the call. For example, for a call message carrying a destination number, whether the current subscriber of the destination number of the call message, for example, the subscriber b, or a history subscriber of the destination number of the call message, for example, the subscriber a, the mobile communication network is not clear with only one destination number, which may result in the occurrence of a phenomenon that a message to be sent to an old subscriber (history subscriber) of a mobile phone number is sent to a new subscriber (current subscriber) of the mobile phone number.
In order to prevent the message to be sent to the old user of a mobile phone number from being sent to the new user of the mobile phone number, the invention firstly proposes to assign a label, called user label (userlale), to the user for distinguishing different users who sign (or register) successively and use the same mobile phone number.
For a mobile phone number, the user label assigned to a user is also called the user label of the mobile phone number.
The user may be assigned a userllabel when the user signs up to handle the mobile phone number.
Or the user can request to change the UserLabel, for example, when the mobile phone number between family members is transferred and used, the corresponding user can request to change the UserLabel.
The invention is explained by taking { user Label is assigned to a user when the user signs up to transact a mobile phone number } as an example, but is not limited.
In the invention, in order to simplify the assignment of the UserLabel of the mobile phone number, the signing time when the user signs a contract and transacts the mobile phone number is taken as the UserLabel assigned to the user.
For example, the subscription time is the current time value obtained by the telecom business hall system when the user subscribes to transact the mobile phone number.
For example, the subscription time is a current date value acquired by the telecom business office system when the user subscribes to transact the mobile phone number. In this case, after a mobile phone number is logged off by a user and deactivated, the mobile phone number should preferably not be allowed to be used by other users after the next day.
The following description will take { the signing time is the current time value obtained by the telecom business office system when the user signs a contract to transact the mobile phone number }, but the invention is not limited thereto.
The current UserLabel of the mobile phone number, namely the signing time of the mobile phone number, can be saved at one side of the HLR according to the corresponding mobile phone number. For example, a subscription time item is added to the subscription data of the subscriber in the HLR to store the subscription time of the subscriber, that is, the userleel assigned to the subscriber.
In order to make the mobile communication network side able to identify the target user of a message, the invention proposes that a registration time is carried in the call message, so that the mobile communication network side can identify the real target user of the message according to the stored signing time of the corresponding mobile phone number.
For a mobile terminal, generally, the registration time is the time when a user adds a new contact to a corresponding mobile phone number. A registration time field may be added to the existing mobile phone number codebook for saving the registration time of the corresponding mobile phone number. For example, when a user adds a new contact, the terminal system time when the corresponding contact record is added is saved in the contact record as the registration time.
For the application server, the registration time is the time when the application server registers a mobile phone number for the user account when the user binds the mobile phone number to the corresponding account, and the time may be the server system time when the mobile phone number is registered.
The application server may be a banking system server and the account may accordingly be a bank account. The application server may be an internet account server, and accordingly, the account is an internet account number.
For a mobile phone number in a contact record in a mobile terminal and a corresponding registration time, or for a mobile phone number of an account binding band in an application server and a corresponding registration time, if the signing time of the mobile phone number is after the registration time, that is, the registration time is less than the signing time, it is indicated that the registered mobile phone number has no meaning, because the corresponding registration operation occurs before the signing time of the mobile phone number, when the mobile phone number is registered, a true signing user corresponding to the mobile phone number has been changed. Otherwise, that is, the registration time is greater than or equal to the subscription time, it indicates that when the mobile phone number is registered, the true subscriber corresponding to the mobile phone number is not changed at present, and is the current subscriber of the mobile phone number at present.
Thus, the mobile communication network side can identify the target user of the message by comparing the registration time of the message with the contract time of the target number of the message.
Based on the above idea, the present invention provides a destination user identification method for identifying a destination user of a message. The method firstly saves the signing time of the corresponding mobile phone number at the HLR side. For example, the corresponding subscription time is stored in an independently configured subscription time server according to the mobile phone number, and the HLR can access the subscription time server according to the mobile phone number to obtain the subscription time corresponding to the corresponding mobile phone number. Preferably, the subscription data of the subscriber in the HLR stores the subscription time corresponding to the corresponding mobile phone number, which is taken as an example in the following embodiments of the present invention, but is not limited thereto.
Fig. 1 is a flowchart of a general embodiment of a user identification method according to the present invention. In the figure, when receiving the query message carrying the destination number and the registration time, the HLR executes the following procedures:
and step 01, acquiring the signing time of the destination number.
For example, the corresponding subscription time is obtained from the subscription data of the destination number.
Step 02, comparing the registration time with the signing time; if the number of the target number is smaller than the preset number, the target user of the message is a historical subscriber of the target number; otherwise, the destination user of the message is the current subscriber of the destination number.
The HLR may reply the query result to the query requester. For example, the HLR provides an inquiry operation to the application server, so that the application server can know whether the mobile phone number bound to an account is valid through inquiry.
Or the HLR may perform corresponding operation according to the query result, i.e., the comparison result in step 02. For example, the query message is a routing query message, that is, the routing query message also carries a corresponding registration time.
According to the target user identification method, the invention further provides a communication control method, so that the HLR can control the call aiming at the user through the signing time of the user, namely the UserLabel assigned to the user. The call may be a voice call, or a short message call, or other form of call.
Fig. 2 is a flowchart of a general embodiment of a communication control method according to the present invention. In the figure, the HLR executes the following procedures for the received route query message carrying the registration time sent by the requester:
and step 11, obtaining the signing time of the destination number of the message. For example, the corresponding subscription time is obtained from the subscription data of the destination number.
Step 12, comparing the registration time with the signing time; if the number is less than the preset number, the destination user of the message is the history subscriber of the destination number, and then, the step 15 is executed: processing according to an abnormal flow; otherwise, it indicates that the destination user of the message is the current subscriber of the destination number, and then, step 13 is executed: processing according to normal flow.
In step 15, the processing by exception flow may be returning an exception report to the requester. The exception report may carry information indicating that "the subscriber has changed". The corresponding requester can know that the subscriber of the destination number has changed according to the reply message.
In step 13, the processing according to the normal flow may be: and acquiring the routing information of the called user and replying the result to the requester.
In the current network, the step of acquiring the routing information of the called user and returning the result to the requester is as follows: HLR requests roaming number to MSC/VLR where the called user is located, and returns the route information returned by MSC/VLR to the requester.
Generally, the routing information returned by the HLR contains a roaming number (MSRN) of a mobile station corresponding to a corresponding called party. For example, the HLR forwards the roaming number returned by the MSC/VLR to the requester.
The following explanation is repeated for operations like "obtaining the routing information of the called subscriber and returning the result to the requester" which will not appear any more.
It should be noted that, if the privacy of the user subscription time is not considered, in all the embodiments, the carrying of the information indicating that "the subscriber has changed" in the exception report may also be directly: and carrying the signing time of the corresponding destination number in the abnormal report. Thus, for the mobile terminal sending the short message, after finally receiving the abnormal report, the corresponding registration time in the own contact record is compared with the signing time carried in the abnormal report, if the registration time is smaller than the signing time, the destination user of the short message is the historical signing user of the destination number of the short message, otherwise, the destination user of the short message is the current signing user of the destination number of the short message, and the abnormal report may be caused by other reasons.
The requester can be an MSC, a GMSC, or an SMSC.
The following is an example where the requestor is an SMSC, but is not intended to limit the invention.
In order to solve the practical problem by using the communication control method of the present invention, when the SME or the ESME such as the mobile terminal or the application server sends the short message to the SMSC, the registration time is further carried in the message. According to the method provided by the invention, the control of communication is implemented in the HLR of the mobile communication network side. The HLR controls the route query operation, so that the mobile communication network side does not send the short message of the old subscriber (for the duration of the subscriber) to be sent to a mobile phone number to the new subscriber (the current subscriber) of the mobile phone number. For example, when the SMSC sends the routing query message to the corresponding HLR according to the destination number of the short message, the SMSC also carries the registration time of the short message in the message, so that the HLR can control the corresponding routing query operation according to the stored subscription time of the destination number, and further control the sending of the short message.
Fig. 3 is a flow chart of the communication control method according to the embodiment of the present invention, which includes the following steps:
step 100, the SMSC receives the short message carrying the registration time.
Step 101, the SMSC sends a routing query request to the HLR according to the destination number of the short message, wherein the request carries the registration time.
Step 102, after receiving the query request, the HLR acquires the subscription time of the destination number; comparing the registration time with the subscription time; if less, go to step 109: returning an exception report to the SMSC; otherwise, step 103 is executed: and acquiring the routing information corresponding to the destination number, and replying the result to the SMSC.
In step 103, generally, the HLR sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests a roaming number to the MSC/VLR where the destination number is currently located, receives a return message of the MSC/VLR, and sends the received roaming number to the SMSC.
After receiving the route message replied by the HLR, the SMSC can send the short message out according to the replied route message.
The SMSC may not include the registration time when transmitting the short message according to the routing information, thereby maintaining full compatibility with the existing network. This will not be repeated in the following.
In step 109, information indicating that "the subscriber has changed" may be carried in the exception report. After receiving the exception report, the SMSC may reply the exception report to the short message sender. Thus, the short message sender can know that the current subscriber of the destination number has changed according to the abnormal report, that is, the destination subscriber of the short message has become the subscriber of the destination number for the duration.
According to the current situation, after the mobile phone number registered in the bank account by the user A is stopped, if the user A forgets to change the mobile phone number bound to the bank account, the user B receives a short message which is sent by the bank according to the number registered in the bank account of the user A and is originally sent to the user A after the user B applies to use the number.
According to the technical scheme provided by the invention, when a user A transacts a mobile phone number, a UserLabel assigned to the user A by a telecom operator is the signing time when the user A signs a mobile phone number, such as UserLabel-A; when the bank registers (i.e. binds) the mobile phone number of the user A, the bank also saves the time for registering (or binding) the mobile phone number, i.e. the registration time. Normally, the registration time is greater than the user A subscription time.
When a bank needs to send a short message to a user A, the bank sends the short message through a mobile phone number registered by the user A, and corresponding registration time is taken as the registration time of the message; after receiving the short message, the corresponding SMSC sends a routing query message to the HLR to which the mobile phone number belongs, and the registration time is carried in the message, namely the registration time of the short message; the HLR acquires the signing time of the mobile phone number, namely UserLabel-A, compares the signing time with the registration time value carried in the short message, and finds that the registration time value is greater than the UserLabel-A, so that the execution can be performed according to a normal flow, namely, the routing information corresponding to the mobile phone number is acquired from the MSC/VLR where the mobile phone number is currently roaming, and the result is replied to the SMSC, so that the SMSC can send the short message to a user A according to the routing information.
And after the user A stops using the mobile phone number, the user B starts signing and using the mobile phone number, and when the user B handles the mobile phone number signing procedure, the UserLabel assigned to the user B by the telecom operator is the signing time of the user B, such as UserLabel-B. Under normal conditions, the registration time of the user A in the bank account is less than the subscription time of the user B.
At this time, when the bank needs to send the short message to the user A, the bank sends the short message through the mobile phone number registered by the user A, and the corresponding registration time is taken as the registration time of the message; after receiving the short message, the corresponding SMSC sends a routing query message to the HLR to which the mobile phone number belongs, and the registration time is carried in the message, namely the registration time of the short message; the HLR acquires the signing time of the mobile phone number, namely UserLabel-B, and compares the signing time with the registration time value carried in the short message to find that the registration time value is smaller than the UserLabel-B, so that the execution is carried out according to an abnormal flow, namely an abnormal report is replied to the SMSC, the SMSC receives the abnormal report, and the corresponding short message is prevented from being sent, namely the short message cannot reach the user B. Thus, the embarrassing situation that the user B is disturbed and the user A is divulged is eliminated.
When sending a route query request to the HLR, carrying the registration time value can be done by using some idle cell of the existing protocol. In existing networks, if a cell is not utilized, the cell is typically set to 0. In implementing the present invention, 0 can be regarded as a registration time compatible value. In this case, when the HLR determines that the registration time is compatible with the value 0, the SMSC is not upgraded, that is, the routing query message is not sent according to the method of the present invention, for example, the routing query message does not carry the corresponding registration time value, and thus, the corresponding cell is set to 0 by default. If the HLR determines that the registration time is a compatible value of 0, it proceeds as in the prior art, e.g., to step 103.
As shown in fig. 4, a flowchart of an embodiment of the communication control method considering compatibility according to the present invention, in this diagram, before the step 109, further includes a step 104B: judging whether the registration time is a compatible value of 0, if so, processing according to a compatible existing protocol mode, namely, turning to step 103; otherwise, step 109 is performed.
In practice, the HLR may also be instructed to perform compatibility processing by different protocol version identifiers.
Of course, if the compatibility problem is not considered, the communication control method of the present invention can be directly realized by modifying the corresponding protocol.
In the following use cases, compatibility is not described again in order to highlight the characteristics of the present invention.
As described above, when the mobile phone number of the user a is deactivated, the user b signs a contract to use the mobile phone number again, and in this case, when the bank system sends a short message to the user a, and the corresponding SMSC sends a routing query request to the HLR, because the subscription time of the current subscriber of the mobile phone number stored in the HLR, that is, the user label assigned to the mobile phone number, has changed, an abnormal flow is triggered, thereby blocking the sending of the short message.
Based on the communication blocking security mechanism provided by the mobile communication control method disclosed by the embodiment, the existing network can be modified, so that the mobile communication network side (including the SMSC) can control a call or communication flow based on the userllabel assigned to a user. Based on the modified mobile communication network, the invention also provides a new short message sending method, so that according to the method, the short message of the old user to be sent to a mobile phone number can be effectively prevented from being sent to the new user of the mobile phone number. The method prestores the registration time of the corresponding mobile phone number.
See the registration schedule as shown in table 2.
TABLE 2
Mobile phone number Time of registration
Mobile phone number 1 Registration time 1
Mobile phone number 2 Registration time 2
Mobile phone number 3 Registration time 3
According to the table, the corresponding registration time can be acquired based on a mobile phone number.
For the mobile terminal, a registration time field can be added in the existing mobile phone number codebook for storing the registration time of the corresponding mobile phone number. For example, when a user adds a new contact, the time when the corresponding contact record is added is saved in the record of the contact as the registration time.
For application servers (including bank system servers), the invention provides a new binding relationship between a mobile phone number and a corresponding internet account number: on the basis of the binding relationship that the mobile phone number is stored only according to the internet account, the registration time element is added, namely when the registered (or bound) mobile phone number is stored according to the internet account, the time for registering (or binding) the mobile phone number is also stored as the registration time. For example, when a user binds a mobile phone number to a corresponding account, the time for executing binding is also saved in the corresponding binding relationship record as the registration time. In this case, the registration schedule as shown in table 2 is typically embedded in the corresponding account record table. Thus, the account record table has a corresponding relation table of the account number, the mobile phone number and the registration time.
See the binding relationship table as shown in table 3.
TABLE 3
Internet account Mobile phone number Time of registration
Internet Account number 1 Mobile phone number 1 Registration time 1
Internet Account 2 Mobile phone number 2 Registration time 2
Internet Account number 3 Mobile phone number 3 Registration time 3
According to the table, the mobile phone number and the registration time which are correspondingly bound can be obtained according to an internet account. Also, the bound internet account and registration time can be obtained according to a mobile phone number.
As a specific example, if there is a corresponding relationship between an internet account and a corresponding mobile phone number, and a related mobile phone number can be obtained from the internet account, the internet account is called as an internet account based on a mobile phone number, which is referred to as a code-based internet account for short, or the internet account is referred to as a code-based internet account. A code-based internet account is a code-based account.
For example, the internet account 13316882017@163.com has a correspondence with the cell phone number 13316882017: the associated cell phone number is obtained from the name portion of the internet account number.
Accordingly, an internet account with a code-based internet account number is referred to as a code-based internet account, or the internet account is code-based. A code-based internet account is a code-based account.
In the binding relationship table shown in table 3, if the corresponding internet account is code-based, the mobile phone number in the corresponding binding relationship record may be omitted.
If the internet account number is code-based in each binding relationship record, the mobile phone number field in the binding relationship table shown in table 3 may be omitted. See the binding relationship table as shown in table 3-a.
TABLE 3-A
Code-based internet account Time of registration
13316882017@163.com Registration time 1
13823755663@163.com Registration time 2
13513556789@163.com Registration time 3
According to the binding relationship table shown in table 3-a, the corresponding bound mobile phone number can be obtained from the corresponding internet account in the binding relationship record. For example, a mobile phone number registers 163 mailbox, and the user name corresponding to the email address is the mobile phone number, and then the mobile phone number can be used as a login account to log in 163 mailbox.
The following description will be given by taking the binding relationship table shown in table 3 as an example, but not by way of limitation.
When sending short message, firstly obtaining the stored registration time of the destination number, then using the registration time of the destination number as the registration time of the message, and sending the short message to SMSC according to the destination number. The SMSC is then able to proceed to step 100 and the corresponding flow thereafter.
As shown in fig. 5, a flowchart of an embodiment of a method for sending a short message according to the present invention is shown, where the flowchart includes the following steps:
and step 21, acquiring the registration time of the destination number of the stored short message.
And step 22, taking the registration time of the destination number as the registration time of the message, and sending the short message to the SMSC according to the destination number.
For the mobile terminal, when step 21 is executed, the corresponding saved registration time is directly obtained from the corresponding contact record according to the destination number.
When the registration time in the contact record corresponding to the destination number is less than the signing time of the destination number, it indicates that the operation of saving the corresponding contact record is before the latest signing time of the mobile phone number, so that the short message will be filtered in the process of step 100 and later. Otherwise, the short message can be transmitted to the mobile phone terminal corresponding to the destination number through the mobile communication network.
For the application server, when step 21 is executed, the corresponding registration time is directly obtained from the corresponding binding relationship record.
When the registration time in the binding relationship record corresponding to the destination number is less than the signing time of the mobile phone number, it indicates that the corresponding registration or binding operation is before the latest signing time of the mobile phone number, so that the short message will be filtered in the process of step 100 and later. Otherwise, the short message can be transmitted to the mobile phone terminal corresponding to the destination number through the mobile communication network.
For example: after receiving the short message sent by the application server, the corresponding SMSC sends a routing query request to the corresponding HLR according to the destination number of the short message, wherein the request carries the registration time of the short message; otherwise, processing according to the normal flow.
For example, the processing according to the normal flow is: and the HLR sends a roaming number query request to the MSC/VLR of the current roaming destination number, namely, requests a roaming number to the MSC/VLR of the current destination number, receives a return message of the MSC/VLR and sends the received roaming number to the SMSC. Thus, the SMSC can send the short message to the corresponding MSC/VLR according to the routing information returned by the HLR.
For example, the processing according to the exception flow is: a reply message indicating "subscriber changed" is returned to the SMSC through an exception report. It will be appreciated that the SMSC may reply the exception report to the sender of the short message, for example the mobile terminal or the application server. According to the reply message, it can be known that the current subscriber of the destination number has changed, that is, the destination subscriber of the short message has become the historical subscriber of the destination number.
When the application server needs to send the short message according to the mobile phone number in one binding relation record, the application server also carries the registration time in the binding relation record in the message. Therefore, when the signed user of the mobile phone number in the binding relation record does not change, the short message can be sent to the corresponding mobile phone number user through the mobile communication network; otherwise, if the subscription of the mobile phone number in the binding relationship record changes, for example, the subscription is changed from the user a to the user b, the subscription time of the mobile phone number in the mobile communication network changes, so that the corresponding SMSC is abnormal when querying the routing information from the HLR according to the corresponding mobile phone number by using the registration time in the binding relationship record as the registration time of the message, and the corresponding short message cannot be transmitted to the current subscription of the mobile phone number, namely, the user b, through the mobile communication network. Thereby ensuring the privacy and the safety of the user A and avoiding the disturbance of the user B.
According to the invention, the short message of the old user to be sent to a mobile phone number can be effectively prevented from being sent to the new user of the mobile phone number. Therefore, the problems that when an application server such as a bank server sends a short message to a mobile phone number bound by a corresponding account, the short message is sent to a new user B under the condition that the mobile phone number is logged off by an old user A and is registered and used by the new user B, and the like can be effectively solved.
It is known that when a user transacts business in a bank business hall, a counter generally registers a mobile phone number to be bound to a bank account, and under the condition, an operating end of the bank counter can directly send the mobile phone number and the registration time registered by the user to a bank background server for storage, so that the binding operation is completed.
However, the internet service provider does not have so many business halls, and many users directly perform corresponding mobile phone number binding operations through the mobile phone APP provided by the internet service provider. In this case, when the user binds the mobile phone number, the mobile phone number may be mistakenly input, and the mobile phone number provided by the user may be maliciously tampered. How to ensure the correctness of the mobile phone number to be bound by the user?
As mentioned above, based on the communication blocking security mechanism provided by the mobile communication control method disclosed in the above embodiment, the existing network can be modified, so that the mobile communication network side (also including SMSC) can control the call or communication flow based on the userllabel assigned to a user. Based on the modified mobile communication network, the invention also provides a new binding method for binding a mobile phone number to an account. The account may be an internet account, a bank account, or other type of account. The account is taken as an internet account, but is not limited in the invention.
Generally, when a user establishes a binding relationship, the user logs in a corresponding account first, and then performs a binding operation.
As shown in fig. 6, a flowchart of an embodiment of a method for establishing a binding relationship is shown, where the method includes the following steps:
and step 31, the application server receives the mobile phone number to be bound of the current account.
Step 32: the application server generates a verification code; and taking the current time value or date value as the registration time of the message, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the message carries the generated verification code. It can be understood that, normally, the current time value or date value is greater than or equal to the subscription time of the mobile phone number.
Step 38, the application server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code and the generated verification code are not consistent, the process is ended; if the two are identical, step 39 is executed.
And 39, the application server establishes a corresponding relation between the corresponding account and the mobile phone number, and stores the current time value or the current date value as registration time in the corresponding relation record. For example, the application server stores the mobile phone number and the current time value in the binding relationship table shown in table 3 according to the corresponding account.
As mentioned above, according to the communication control method provided by the present invention, the sending of the short message can be controlled according to the subscription time of a mobile phone number, so that when the registration time carried by the short message is less than the subscription time of the destination number of the short message, the short message will be blocked by the mobile communication network and cannot be sent to the mobile phone terminal corresponding to the destination number; otherwise, the short message can be smoothly sent to the corresponding mobile phone terminal through the mobile communication network.
For example, after said step 32, the following sub-flows are performed on the mobile communication network side:
after receiving the short message, the corresponding SMSC sends a route inquiry message carrying the registration time value to the corresponding HLR according to the destination number of the short message. After receiving the route query message, the HLR acquires the signing time of the destination number, compares the registration time with the signing time, and because the registration time is greater than or equal to the signing time, the HLR sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests a roaming number to the MSC/VLR where the destination number is currently located, receives a return message of the MSC/VLR, and sends the received roaming number to the SMSC, and the SMSC sends the verification code to the mobile terminal of the destination number through a short message via the corresponding MSC/VLR according to the roaming number.
Based on the new binding relationship, when a short message needs to be sent according to a mobile phone number, the registration time in the binding relationship record is taken as the registration time of the message. The mobile communication network side can execute a UserLabel verification operation: and comparing the registration time in the binding relation record with the signing time of the mobile phone number, if the registration time is less than the signing time, no corresponding short message is sent, otherwise, the verification is passed, and a subsequent short message sending process is executed. Thus, the short message of the old user to be sent to a mobile phone number can be effectively prevented from being sent to the new user of the mobile phone number. Therefore, the problem that when the bank server sends a short message to a mobile phone number user bound to a corresponding account, the mobile phone number is registered and used by a new user because the old user logs off the mobile phone number, and the short message is sent to the new user can be effectively solved.
According to the corresponding method provided by the invention, after the mobile phone number of the user is cancelled, even if other people register to use the mobile phone number, the current signing user of one mobile phone number is blocked from acquiring the verification code of the account bound by the historical signing user of the mobile phone number according to the mobile phone number because the following user is assigned with a new UserLabel, namely in a mobile communication network, the signing time of the mobile phone number changes, so that the safety of the account of the old user is ensured, and the trouble that the old user unbinds the cancelled mobile phone number one by one aiming at each Internet account is avoided.
As mentioned above, based on the communication blocking security mechanism provided by the mobile communication control method provided in the above embodiment, the existing network can be modified, so that the mobile communication network side (also including SMSC) can control the call or communication flow based on the userllabel assigned to a user. Based on the modified mobile communication network, the invention also provides an account registration method, which directly creates an account according to a mobile phone number and binds the mobile phone number to the created account. The account may or may not be a code-based account.
The following description will be given by taking the registered account as an example of a non-code-based account, but the registered account is not limited thereto.
As shown in fig. 7, a flowchart of an embodiment of a method for account registration includes the following steps:
step 41, the server receives the registration request carrying the mobile phone number.
Step 42, the server searches for the account bound by the mobile phone number, and if the account exists, the process is ended; otherwise, entering a new account creation process.
As shown in fig. 8, a flowchart of an embodiment of creating a new account is shown, in which the following steps are included:
step 51, the server generates a verification code; and according to the mobile phone number, taking the current time value as the registration time of the message, and sending the generated verification code to a mobile communication network through a short message so as to be sent to a corresponding mobile terminal by the mobile communication network. It can be understood that, normally, the current time value or date value is greater than or equal to the subscription time of the mobile phone number.
Step 52, the server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code and the generated verification code are not consistent, the process is ended; if the two are identical, step 53 is executed.
Step 53, the server creates an account, and stores the mobile phone number and the corresponding registration time in the account. The registration time here may be a time value at the time of creating the account, or may be the registration time value described in step 51. For example, the server stores the mobile phone number and the corresponding registration time value in the binding relationship table shown in table 3 according to the account number corresponding to the created account.
For example, after said step 51, the following sub-flows are executed on the mobile communication network side:
after receiving the short message, the corresponding SMSC sends a route inquiry message carrying the registration time value to the corresponding HLR according to the destination number of the short message. After receiving the route query message, the HLR acquires the signing time of the destination number, compares the registration time with the signing time, and because the registration time is greater than or equal to the signing time, the HLR sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests a roaming number to the MSC/VLR where the destination number is currently located, receives a return message of the MSC/VLR, and sends the received roaming number to the SMSC, and the SMSC sends the verification code to the mobile terminal of the destination number through a short message via the corresponding MSC/VLR according to the roaming number.
In step 42, if there is already a corresponding account, there are generally two cases:
in case one, the existing account is registered by a historical subscriber of the mobile phone number, for example, before the current subscriber of the mobile phone number, one or more users have signed up to use the mobile phone number respectively, and a plurality of accounts are registered according to the mobile phone number respectively. In this case, it is preferable to freeze or log out the account so as to prevent the current subscriber who affects the mobile phone number from registering his or her account according to the mobile phone number.
In case two, this already existing account is registered by the current subscriber of the mobile phone number. For example, the current subscriber has forgotten that he has registered with the account. In this case, it is preferable to let the current subscriber of the mobile phone number know: it has registered the corresponding account according to the mobile phone number.
In step 42, if the corresponding account already exists, an owner verification process of the account is further preferably performed to determine whether the account is created by the current subscriber of the mobile phone number or the historical subscriber of the mobile phone number.
As shown in fig. 9, a flowchart of an embodiment of the account registration method is shown, in which step 42 further includes: the server searches for the account bound by the mobile phone number, and if the account exists, the server enters the owner confirmation process of the existing account; otherwise, entering the new account creating process.
For the server to determine the owner of an existing account, there are two ways:
method one, judging by mobile communication network side
And the server sends a short message to the mobile communication network side by taking the registration time value stored in the account as the registration time of the message according to the mobile phone number. According to the step 100 and the subsequent processes, when the server receives an abnormal report carrying information indicating that the subscriber has changed, which is returned from the mobile communication network side, the server can know that the account is created by the historical subscriber of the mobile phone number.
Second, judging by the server side
The server can obtain the signing time of the mobile phone number, compare the registration time saved by the account with the signing time, if the registration time is less than the signing time, the account is created by the historical signing user of the mobile phone number, otherwise, the account is created by the current signing user of the mobile phone number. The following is a use case of how to query the subscription time of a mobile phone number.
As shown in fig. 10, a flowchart of an embodiment of account owner confirmation is shown, in which the following steps are included:
step 61, the server generates a verification code; and according to the mobile phone number, taking the registration time value stored in the account as the registration time of the message, and sending the generated verification code to a mobile communication network through a short message so as to be sent to a corresponding mobile terminal by the mobile communication network. The mobile phone number is the mobile phone number bound to the existing account.
The mobile communication network acquires the signing time of the mobile phone number and compares the registration time with the signing time; if the answer is less than the answer, returning an exception report to the server, wherein the exception report carries information indicating that the signed user is changed, and then entering step 62; otherwise, the verification code is sent to the corresponding mobile terminal, and then step 63 is entered.
For example, the transmitting of the generated authentication code to the mobile communication network is transmitting the generated authentication code to a corresponding SMSC. The SMSC receives a short message which is sent by the server and carries a destination number and registration time; sending a route query request to an HLR according to the destination number of the short message, wherein the request carries the registration time; after receiving the query request, the HLR acquires the signing time of the destination number; comparing the registration time with the subscription time; if the number of the signed users is smaller than the preset number, returning an abnormal report to the SMSC, wherein the abnormal report carries information indicating that the signed users are changed; the SMSC replies the exception report to the server; then go to step 62; otherwise, obtaining the routing information corresponding to the destination number, and replying the result to the SMSC, wherein the SMSC sends the verification code to the corresponding mobile phone through a short message according to the routing information returned by the HLR; then step 63 is entered.
The step 62 is: the server receives the exception report returned by the mobile communication network, e.g., the server receives the exception report returned by the respective SMSC.
And the server learns that the subscriber of the mobile phone number has changed according to the abnormal report, so as to confirm that the existing account is registered by the historical subscriber of the mobile phone number. In this case, the server may freeze or log out the existing account.
After the server freezes or logs off the existing account, the server can also enter the new account creating process to create a corresponding new account for the current subscriber of the mobile phone number. It will be appreciated that the authentication code generated by the server in step 61 may be reused in the incoming new account creation process. That is, in the step 51 of the new account creation process, the verification code that has been generated in the step 61 is reused.
The step 63 is: the server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code and the generated verification code are not consistent, the process is ended; and if the two are consistent, confirming that the existing account is registered by the current subscriber of the mobile phone number.
In step 63, after confirming that the account is registered by the current subscriber of the mobile phone number, the registration requester may be informed of information indicating that "you have registered a corresponding account". For example, a message indicating that "you have registered a corresponding account" is replied to the registration requester, or the registration requester is directly put into a login state, so that the registration requester immediately enters an account that is already registered by itself and thus knows that "the corresponding account is already registered".
It should be noted that, if the privacy of the user subscription time is not considered, in all the above related embodiments, the carrying of the information indicating that the "subscription user has changed" in the exception report may also be directly: and carrying the signing time of the corresponding destination number in the abnormal report. Therefore, the signing time of one mobile phone number can be inquired by triggering the mobile communication network to return an abnormal report. It will be appreciated that since the normal time values are all greater than 1, setting the corresponding registration time to 1 when sending a short message may trigger the mobile communication network to return such an exception report. In this case, for the mobile terminal sending the short message, after receiving such an abnormal report replied by the SMSC, the registration time in the contact record is compared with the subscription time carried by the abnormal report, and if the registration time is smaller than the subscription time carried by the abnormal report, it is indicated that the destination user of the short message is a historical subscriber of the destination number of the short message, otherwise, the destination user of the short message is a current subscriber of the destination number of the short message, and the abnormal report may be caused by other reasons.
Of course, the exception report in which the subscription time of the corresponding destination number carried in the exception report is not 0 may be regarded as an exception report indicating "the subscriber has changed".
In the account owner confirmation process, after step 62, if a new account creation process is entered, since the telephone number is also confirmed by the verification code in the new account creation process, the verification code is also transmitted once, which prolongs the execution time of the registration service.
Based on this, it is preferable to agree on a special value of 1, before the step 109, further comprising the step 104C: judging whether the registration time is a compatible value 1, if so, returning an abnormal report to the SMSC, carrying the signing time of the corresponding destination number in the abnormal report, and then turning to step 103; otherwise, step 109 is performed.
Fig. 11 is a flow chart of an embodiment of the communication control method of the present invention considering a special value.
The invention also provides an account owner confirmation process based on the mobile communication network implementing the communication control method embodiment considering the special value. In the process, the number of times of sending short messages by the application server can be reduced, and the service execution efficiency can be improved.
As shown in FIG. 12, a flow chart of an embodiment for considering special values for account owner validation includes the following steps in the diagram:
step 71, the server generates a verification code; and according to the mobile phone number, taking the special value 1 as the registration time of the message, and sending the generated verification code to a mobile communication network through a short message so as to be sent to a corresponding mobile terminal by the mobile communication network.
The mobile communication network acquires the signing time of the mobile phone number, returns an abnormal report to the server when judging that the registration time is a special value 1, carries the signing time of the mobile phone number in the abnormal report, sends the verification code to the corresponding mobile terminal, and then enters step 72.
Step 72, the server receives the abnormal report carrying the subscription time of the mobile phone number returned by the mobile communication network; receiving the verification code returned from the client, comparing the verification code with the generated verification code, and ending the process if the verification code and the generated verification code are not consistent; if they are the same, step 73 is performed.
And 73, comparing the registration time of the existing account with the signing time of the mobile phone number, and if the registration time of the existing account is less than the signing time of the mobile phone number, confirming that the existing account is registered by a historical signing user of the mobile phone number. In this case, the server may freeze or log out the existing account. After freezing or logging off the existing account, an account can be created, and the mobile phone number and the corresponding registration time are saved in the account. For example, the registration time is a current time value or a day-ahead value of the system.
For example, after said step 71, the following sub-flows are executed on the mobile communication network side:
after receiving the short message, the corresponding SMSC sends a route inquiry message carrying the registration time value to the corresponding HLR according to the destination number of the short message. After receiving the route query message, the HLR acquires the signing time of the destination number, compares the registration time with the signing time, and if the result is less than the result, further determines whether the registration time is 1, and if the registration time is 1, returns the signing time of the destination number to the SMSC through an exception report, and then sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests a roaming number to the MSC/VLR where the destination number is currently located, receives a return message of the MSC/VLR, sends the received roaming number to the SMSC, and the SMSC sends the verification code to the mobile terminal of the destination number through a short message via the corresponding MSC/VLR according to the roaming number. The SMSC replies the exception report to the application server.
In step 73, if the registration time of the existing account is greater than or equal to the signing time of the mobile phone number, it is confirmed that the existing account is registered by the current signing user of the mobile phone number.
In step 73, after confirming that the account is registered by the current subscriber of the mobile phone number, the registration requester may be informed of information indicating that "you have registered a corresponding account". For example, a message indicating that "you have registered a corresponding account" is replied to the registration requester, or the registration requester is directly put into a login state, so that the registration requester immediately enters an account that is already registered by itself and thus knows that "the corresponding account is already registered".
When a user registers an account according to a mobile phone number, according to the above preferred embodiment, whether the account exists, that is, whether the user enters a new account creation process or an account owner confirmation process, the server verifies the identity of the user, that is, whether the registration requester owns the mobile phone number. Generally, the server will send a generated verification code to the mobile communication network, receive the verification code returned from the registration requester client, compare the verification code with the generated verification code, and consider the owner identity to be legal when the two are consistent.
It can be understood that the operations for the owner identity verification in the new account creation process and the account owner confirmation process can be extracted and executed in a unified manner.
As shown in fig. 13, a flowchart of an embodiment of a method for account registration is shown, in which the following steps are included:
step 81, the server receives the registration request carrying the mobile phone number.
Step 82, the server generates a verification code; and according to the mobile phone number, taking the special value 1 as the registration time of the message, and sending the generated verification code to a mobile communication network through a short message so as to be sent to a corresponding mobile terminal by the mobile communication network.
Step 83, the server receives an abnormal report carrying the subscription time of the mobile phone number, which is returned by the mobile communication network; receiving the verification code returned from the client, comparing the verification code with the generated verification code, and ending the process if the verification code and the generated verification code are not consistent; if the two are consistent, step 84 is performed.
Step 84, the server searches for the account bound by the mobile phone number, and if the account exists, step 85 is executed; otherwise, step 87 is performed.
Step 85, comparing the registration time of the existing account with the signing time of the mobile phone number, and if the registration time of the existing account is less than the signing time of the mobile phone number, executing step 86; otherwise, the registration requester is put into the login state and then ends.
Step 86, freeze or log out the existing account.
And 87, creating an account, and storing the mobile phone number and the corresponding registration time in the account. For example, the registration time is a current time value or a day-ahead value of the system.
For example, after said step 82, the following sub-flows are performed on the mobile communication network side:
after receiving the short message, the corresponding SMSC sends a route inquiry message carrying the registration time value to the corresponding HLR according to the destination number of the short message. After receiving the route query message, the HLR acquires the signing time of the destination number, compares the registration time with the signing time, and if the result is less than the result, further determines whether the registration time is 1, and if the registration time is 1, returns the signing time of the destination number to the SMSC through an exception report, and then sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests a roaming number to the MSC/VLR where the destination number is currently located, receives a return message of the MSC/VLR, sends the received roaming number to the SMSC, and the SMSC sends the verification code to the mobile terminal of the destination number through a short message via the corresponding MSC/VLR according to the roaming number. The SMSC replies the exception report to the application server.
In the invention, when the short message is sent, the registration time is carried in the message, the registration time can be carried by utilizing an idle cell of the existing protocol or expanding a cell of the existing protocol or increasing a cell of the existing protocol, or the registration time can be carried by the content of the short message.
For example, when the application server sends a short message to the corresponding SMSC, when the SMSC sends a route query message to the corresponding HLR, etc., the registration time can be carried by using the idle cell or the extended cell, or adding a cell.
In particular, when the application server sends the short message to the corresponding SMSC, the registration time can also be carried by the content part of the short message.
For the network entities mentioned in the present invention, such as SME, ESME, HLR, MSC, SMSC, VLR, etc., more detailed descriptions can be found in the relevant technical specification documents of 3GPP (3 GPP (3 GPP tarshirp Project: 3G partnership Project).
The sending of the verification code or other information through the short message mentioned in various places of the present invention, for example, the scenario of sending the verification code through the short message, may be actually performed by other means. For example, by means of a UUS-from-user message. For UUS, reference is made to the telecommunications specification ITU-T i.257.1 user-to-user signaling (UUS), which is not further described here.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, improvement, equivalent replacement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A destination subscriber identifying method for an HLR to identify a destination subscriber of a message, wherein a subscription time of a mobile phone number is stored in the HLR, and for a message carrying the destination number and a registration time received by the HLR, the method comprising the steps of:
a. acquiring the signing time of the destination number;
b. comparing the registration time with the subscription time; if the number of the target number is smaller than the preset number, the target user of the message is a historical subscriber of the target number; otherwise, the destination user of the message is the current subscriber of the destination number.
2. A mobile communication control method, characterized in that, the subscription time of the mobile phone number is stored in the HLR, and for the route inquiry message which carries the registration time and is received by the HLR, the method comprises the following steps:
a. acquiring the signing time of the destination number of the message;
b. comparing the registration time with the subscription time; if the value is less than the preset value, processing according to a normal flow; otherwise, processing according to the abnormal flow.
3. An SMSC query routing method, comprising the steps of:
a. SMSC receives short message carrying destination number and registration time;
b. and the SMSC sends a routing query request to the HLR according to the destination number of the short message, wherein the request carries the registration time.
4. A short message sending method, the method preserves the registration time of the corresponding mobile phone number in advance, characterized by that, the method includes the following steps:
a. acquiring the registration time of the target number of the stored short message;
b. and taking the registration time of the destination number as the registration time of the message, and sending the short message to the SMSC according to the destination number.
5. A binding method is used for binding a mobile phone number to an account; the method is characterized by comprising the following steps:
a. the application server receives a mobile phone number to be bound of a current account;
b. the application server generates a verification code; taking the current time value or date value as the registration time of the message, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the message carries the generated verification code;
c. the application server receives the verification code returned from the client, compares the verification code with the generated verification code, if the verification code is consistent with the generated verification code, establishes the corresponding relation between the corresponding account and the mobile phone number, and takes the current time value or date value as the registration time to be stored in the corresponding relation record.
6. An account creating method is used for creating an internet account according to a mobile phone number; the method is characterized by comprising the following steps:
c. the server generates a verification code; according to the mobile phone number, the current time value is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
d. the server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code and the generated verification code are consistent, executes the step g: and creating an account, and storing the mobile phone number and the corresponding registration time in the account.
7. The method of claim 6, wherein the cell phone number is carried in a registration request received by the server; further comprising step b before step c: the server searches the account bound by the mobile phone number, and if the account exists, the server enters an account owner confirmation process; otherwise, executing step c;
the account owner confirmation process comprises the following steps:
{
the server generates a verification code; according to the mobile phone number, the registration time value stored in the account is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
when the server receives an abnormal report which indicates that the signed user is changed and is returned by the mobile communication network, the server freezes or cancels the existing account, and then the step c is carried out;
when the server receives the verification code returned from the client, the server compares the received verification code with the generated verification code, and if the verification code is consistent with the generated verification code, the server confirms that the existing account is registered by the current subscriber of the mobile phone number
}；
Or, the account owner confirmation process includes:
{
the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
the server receives an abnormal report which carries the signing time of the mobile phone number and is returned by the mobile communication network; receiving a verification code returned from the client; comparing with the generated verification code, and if the verification code and the generated verification code are not consistent, ending the process; if the two are consistent, executing { comparing the registration time of the existing account with the signing time of the mobile phone number, { freezing or logging out the existing account if the registration time of the existing account is less than the signing time of the mobile phone number, { creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, flow in the process of confirming that the existing account is registered by the current signed user of the mobile phone number
}。
8. The method of claim 6, wherein the cell phone number is carried in a registration request received by the server; step c is further: the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
in step d, the server further receives an exception report carrying the subscription time of the mobile phone number, which is returned by the mobile communication network;
step g is further:
g01, the server searches the account bound by the mobile phone number, and if the account exists, the server enters an account owner confirmation process; otherwise, creating an account, and storing the mobile phone number and the corresponding registration time in the account;
the account owner confirmation process comprises the following steps: comparing the registration time of the existing account with the signing time of the mobile phone number, if the registration time of the existing account is less than the signing time of the mobile phone number, freezing or logging off the existing account, creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, confirming that the existing account is registered by the current subscriber of the mobile phone number.
9. An owner identification method for identifying an owner of an existing account of a mobile phone number, the method comprising the steps of:
a. the server generates a verification code; according to the mobile phone number, the registration time value stored in the account is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
b. when the server receives an abnormal report which indicates that the subscriber is changed and is returned by the mobile communication network, the server freezes or logs off the existing account, and then executes an account creating process: { according to the mobile phone number, taking the current time value as the registration time of the message, and sending the generated verification code to the mobile communication network through the short message; receiving a verification code returned from the client, comparing the verification code with the generated verification code, if the verification code and the generated verification code are consistent, creating an account, and storing the mobile phone number and the corresponding registration time in the account };
and when receiving the verification code returned from the client, the server compares the received verification code with the generated verification code, and if the received verification code is consistent with the generated verification code, the server confirms that the existing account is registered by the current subscriber of the mobile phone number.
10. An owner identification method for identifying an owner of an existing account of a mobile phone number, the method comprising the steps of:
a. the server generates a verification code; according to the mobile phone number, the special value 1 is used as the registration time of the message, and the generated verification code is sent to a mobile communication network through a short message;
b. the server receives the abnormal report which carries the signing time of the mobile phone number and is returned by the mobile communication network; receiving the verification code returned from the client, comparing the verification code with the generated verification code, and ending the process if the verification code and the generated verification code are not consistent; if the two are consistent, executing step c;
c. comparing the registration time of the existing account with the signing time of the mobile phone number, if the registration time of the existing account is less than the signing time of the mobile phone number, freezing or logging off the existing account, creating an account, and storing the mobile phone number and the corresponding registration time in the account; otherwise, confirming that the existing account is registered by the current subscriber of the mobile phone number.
CN201810881668.XA 2018-08-05 2018-08-05 Mobile communication control method based on time tag Pending CN110809266A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810881668.XA CN110809266A (en) 2018-08-05 2018-08-05 Mobile communication control method based on time tag

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810881668.XA CN110809266A (en) 2018-08-05 2018-08-05 Mobile communication control method based on time tag

Publications (1)

Publication Number Publication Date
CN110809266A true CN110809266A (en) 2020-02-18

Family

ID=69486828

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810881668.XA Pending CN110809266A (en) 2018-08-05 2018-08-05 Mobile communication control method based on time tag

Country Status (1)

Country Link
CN (1) CN110809266A (en)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620166A (en) * 2003-11-21 2005-05-25 华为技术有限公司 Method of identifying legalness of mobile terminal user
CN101790159A (en) * 2009-01-24 2010-07-28 丁聚岗 Method for binding and protecting network account by using telephone
CN102752292A (en) * 2012-06-21 2012-10-24 宇龙计算机通信科技(深圳)有限公司 Method and system for registering application account
CN103152400A (en) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 Method and system for logging in through mobile terminal and cloud server
CN103781054A (en) * 2012-10-19 2014-05-07 华为终端有限公司 Method and device for stopping contract signing of terminal
CN104754136A (en) * 2015-04-15 2015-07-01 上海斐讯数据通信技术有限公司 Method and system for managing account numbers relevant to mobile phone numbers on basis of intelligent terminals
CN104883259A (en) * 2015-06-11 2015-09-02 郑存粮 Method for automatic registration by using mobile phone number as network application account number
CN104917749A (en) * 2015-04-15 2015-09-16 腾讯科技（深圳）有限公司 Account registration method and device
CN106888446A (en) * 2015-12-15 2017-06-23 中国电信股份有限公司 For the methods, devices and systems of checking information recipient's property right identity
CN107872787A (en) * 2016-09-26 2018-04-03 中国电信股份有限公司 Number is nullified, bound, unbinding method and carrier server and application platform
CN108243404A (en) * 2016-12-23 2018-07-03 中国移动通信集团四川有限公司 Ratification method, device and the equipment of phone number binding state
CN110545526A (en) * 2018-05-28 2019-12-06 王正伟 Mobile communication control method
CN110740096A (en) * 2018-07-21 2020-01-31 王正伟 Mobile communication control method based on time tag

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1620166A (en) * 2003-11-21 2005-05-25 华为技术有限公司 Method of identifying legalness of mobile terminal user
CN101790159A (en) * 2009-01-24 2010-07-28 丁聚岗 Method for binding and protecting network account by using telephone
CN102752292A (en) * 2012-06-21 2012-10-24 宇龙计算机通信科技(深圳)有限公司 Method and system for registering application account
CN103781054A (en) * 2012-10-19 2014-05-07 华为终端有限公司 Method and device for stopping contract signing of terminal
CN103152400A (en) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 Method and system for logging in through mobile terminal and cloud server
CN104917749A (en) * 2015-04-15 2015-09-16 腾讯科技（深圳）有限公司 Account registration method and device
CN104754136A (en) * 2015-04-15 2015-07-01 上海斐讯数据通信技术有限公司 Method and system for managing account numbers relevant to mobile phone numbers on basis of intelligent terminals
CN104883259A (en) * 2015-06-11 2015-09-02 郑存粮 Method for automatic registration by using mobile phone number as network application account number
CN106888446A (en) * 2015-12-15 2017-06-23 中国电信股份有限公司 For the methods, devices and systems of checking information recipient's property right identity
CN107872787A (en) * 2016-09-26 2018-04-03 中国电信股份有限公司 Number is nullified, bound, unbinding method and carrier server and application platform
CN108243404A (en) * 2016-12-23 2018-07-03 中国移动通信集团四川有限公司 Ratification method, device and the equipment of phone number binding state
CN110545526A (en) * 2018-05-28 2019-12-06 王正伟 Mobile communication control method
CN110740096A (en) * 2018-07-21 2020-01-31 王正伟 Mobile communication control method based on time tag

Similar Documents

Publication Publication Date Title
EP2454898B1 (en) Method and apparatus for verification of a telephone number
US20080281737A1 (en) System and Method for Authenticating the Identity of a User
CN108737366B (en) Binding method
US20140172712A1 (en) Transaction Authorisation
US20160021532A1 (en) Method for preventing fraud or misuse based on a risk scoring approach when using a service of a service provider, system for preventing fraud or misuse, and mobile communication network for preventing fraud or misuse
CN105898001B (en) Communication information processing method and device and server
CN110636505A (en) Method and system for protecting account security
CN103782564A (en) Authentication system and method therefor
CN110545526A (en) Mobile communication control method
CN111212392B (en) Forward call filtering method, device, equipment and medium
CN108134771B (en) Method for verifying identity of mobile phone numbers
EP1478196A2 (en) Module and method for detecting at least one event in a cellular mobile telephony subscriber equipment, a computer program to carry out the method and a card and terminal with the module.
CN110740096A (en) Mobile communication control method based on time tag
CN110809266A (en) Mobile communication control method based on time tag
EP2797348B1 (en) Subscriber data management
KR20170037439A (en) System and method of Safe Message Advising
CN107920346B (en) Method for controlling communication of mobile terminal, mobile terminal and computer-readable storage medium
EP2903234A1 (en) Network signalling message verification
US20230056017A1 (en) Method and apparatus for detecting abnormal roaming request
KR20170016114A (en) Caller authentication method and authentication server
KR20120106265A (en) Identity theft protection service that provides communication systems
EP1829325A1 (en) Method of opening a connection in a mobile network
WO2008004989A1 (en) Mobile messaging system and methods of operating such a mobile messaging system
KR20170016115A (en) Caller authentication application and program
SE525779C2 (en) Subscriber positioning data forwarding system for wireless communication network, receives position enquiry for user, based on which the desired fixing data is collected and forwarded according to set specifications

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20200218