CN110740096A - Mobile communication control method based on time tag - Google Patents
Mobile communication control method based on time tag Download PDFInfo
- Publication number
- CN110740096A CN110740096A CN201810807625.7A CN201810807625A CN110740096A CN 110740096 A CN110740096 A CN 110740096A CN 201810807625 A CN201810807625 A CN 201810807625A CN 110740096 A CN110740096 A CN 110740096A
- Authority
- CN
- China
- Prior art keywords
- mobile phone
- userlabel
- phone number
- short message
- message
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L45/507—Label distribution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
- H04L61/2553—Binding renewal aspects, e.g. using keep-alive messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses mobile communication control methods, which saves the currently assigned UserLabel in the user contract data, and controls the route inquiry operation carrying the target UserLabel in the calling process, based on the method, SMSC inquiry route methods are also disclosed, so that the SMSC can provide mechanisms for controlling the sending of short messages like a mobile phone terminal or an application server, based on the mechanisms, short message sending methods are also disclosed, the method sends the short messages according to the target number of the short message and the correspondingly saved registration time when sending the short messages, thereby avoiding sending the messages to the old users of numbers to the new users of the numbers, based on the mechanism, also discloses binding account methods, and when establishing the binding relationship, the registration time factor is introduced, thereby being helpful to avoid the wrong sending of the short messages.
Description
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 telecommunication field of telecommunication network, there are phenomena that user A abandons the old mobile phone number being used and applies for a new mobile phone number for some reason, and the old mobile phone number of user A is registered and used by user B, in this case, user B may receive the short message sent by the friend of user A, thus causing harassment to user B and leaking the privacy information of user A and user A's friend, bringing safety hazard to user A and user A's friend.
For example, when a customer transacts a bank card or a credit card, the customer registers a mobile phone number, the customer changes the mobile phone number for some reason, 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.
For example, after the user A forgets a login password of an account registered in a certain service provider, such as a WeChat account, the login password can be reset by inputting the mobile phone number, the password can be retrieved through the mobile phone after the user logs in the WeChat, the WeChat client sends the mobile phone number to the WeChat server, the corresponding server generates verification codes for identity verification according to the mobile phone number and sends the verification codes to the user, and the user logs in or modifies the login password by utilizing the verification codes received by the mobile phone.
Particularly, some internet accounts can directly log in by 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 fact that the mobile phone number of the user is used as certificates of the identity of the user is already provided, so that the use of the user is facilitated to a great extent, the service operation of a service provider is facilitated, and the operation cost is reduced.
However, when the user a changes the mobile phone number for some reason, for example, learns in beijing and works in Shanghai after graduation, the old number used by the user a is released, and the user B logs in the old number that the user a logged off, and then logs in the corresponding account or payment system of the user a using the old number according to the above-mentioned convenient business process, unless the user a logs out the old number and immediately logs out or releases all the binding business related to the old number, for example, the old number and the WeChao account, the old number and the payment account, the old number and the ticket booking system account, and so on.
Disclosure of Invention
The present invention discloses kinds of mobile communication control method, which can at least partially solve the above problems, by saving the currently assigned UserLabel in the user subscription data, and controlling the route inquiry operation carrying the target UserLabel during the call process, thereby achieving the control of the call flow.A corresponding SMSC inquiry route method can be realized based on the method, so that the SMSC can provide mechanisms for controlling the sending of short messages like a mobile phone terminal or an application server, based on the mechanisms, short message sending methods can be provided in steps, by saving the registration time of the corresponding mobile phone number in advance, and when sending short messages, sending short messages according to the target number of short messages and the correspondingly saved registration time, thereby avoiding sending the messages to be sent to old users to the number to new users of the number, eliminating the disturbance to the receiver, and protecting the message sender and the privacy of the old users of the number.
mobile communication control method, which saves the currently assigned UserLabel in the user subscription data, and controls the call flow by controlling the route inquiry operation carrying the target UserLabel during the call process.
A mobile communication control method, which stores the current UserLabel in HLR according to the mobile phone number, and for the route inquiry message which carries the target UserLabel and is received by HLR, the method includes the following steps:
a. acquiring a current UserLabel of a destination number of a message;
b. comparing the target UserLabel of the message with the current UserLabel, if the target UserLabel of the message and the current UserLabel are , processing according to a normal flow, otherwise, processing according to an abnormal flow;
the "destination userllabel of the message is identical to the current userllabel " means that the destination userllabel of the message is not smaller than the current userllabel.
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.
SMSC query routing methods, so that the SMSC can provide mechanisms for controlling the sending of short messages like a mobile phone terminal or an application server.
A SMSC query routing method, comprising the steps of:
a. SMSC receives the short message carrying the destination number and the destination UserLabel;
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 destination UserLabel.
short message transmitting method, which pre-stores the registration time of corresponding handset number, when transmitting short message, transmitting short message according to the destination number of short message and the corresponding stored registration time, thereby avoiding the message to be transmitted to old users to be transmitted to the new users of the number.
A method for sending short message, which pre-stores the registration time of corresponding mobile phone number, when sending short message according to destination mobile phone numbers, the method includes the following steps:
a. acquiring the registration time of the stored target mobile phone number;
b. and taking the registration time of the target mobile phone number as a target UserLabel of the message, and sending the short message to an SMSC (short message service center) according to the target mobile phone number.
binding methods introduce a registration time factor when establishing the binding relationship, thereby helping to avoid the short message sending error.
binding method for binding mobile phone numbers to Internet accounts, the method includes the following steps:
a. the application server receives a mobile phone number to be bound by an internet account;
b. the application server generates a verification code; taking the current time value or date value as a target UserLabel, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the short 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 and the generated verification code are , establishes the corresponding relation between the corresponding internet 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.
The technical scheme provided by the embodiment is that the currently assigned UserLabel is saved in the user subscription data, the call flow is controlled by controlling the route query operation carrying the target UserLabel in the calling process, based on the method, the corresponding SMSC query route method can be realized by steps, so that the SMSC can provide mechanisms for controlling the sending of short messages like a mobile phone terminal or an application server, based on the mechanism, short message sending methods can be provided by steps, and the method sends the short messages according to the target number of the short message and the correspondingly saved registration time when sending the short messages, thereby avoiding sending the messages to be sent to number old users to new users of the number, eliminating harassment to the receiver, protecting the message sender and the privacy of the number old users, and improving the overall security of the communication between the telecommunication network and the Internet.
In the technical solution provided in the above embodiment, because a registration time factor is introduced into the binding relationship, the message can be filtered through the latest userllabel of mobile phone numbers, so that the short message of the old user to be sent to the mobile phone number bound by the corresponding internet account (for convenience of description, the bank account is also regarded as an internet account) is not sent to the new user of the mobile phone number, thereby avoiding the phenomenon of wrong sending of the verification code, and effectively eliminating the security risks caused when the user changes the mobile phone number, such as entering WeChat of the mobile phone number, logging in a Paibao by the mobile phone number, receiving the verification code sent by a bank through the mobile phone, and the like, which are widely existed in the current .
Drawings
FIG. 1 is a flow chart of the general embodiment of the present invention.
FIG. 2 is a flow chart illustrating an embodiment of the present invention.
Fig. 3 is a flowchart of a specific embodiment of the present invention considering compatibility.
Fig. 4 is a flow chart of a short message sending method according to the present invention.
Fig. 5 is a flowchart of an embodiment of a method for establishing a binding relationship.
Acronyms
ESME: (External Short Message Entity);
HLR: (Home Location Register );
MSC: (Mobile Switching Center);
GMSC: (Gateway Mobile Switching Center);
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.
In order to prevent messages to be sent to old users of mobile numbers from being sent to new users of the mobile numbers, the invention proposes to assign tags, called user tags (userlarel), to the users in order to distinguish between different users who have registered (or signed up) one after the other using the same mobile numbers.
For cell phone numbers, the userllabel assigned to users is also referred to as the userllabel for that cell phone number.
The operation of assigning the UserLabel to the user can be carried out when the user signs up to transact 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.
For example, when a user signs up to transact a mobile phone number, the telecom business hall obtains the current time value of the system, and the time value is used as a UserLabel assigned to the user.
For example, when a user signs up to transact mobile phone numbers, the current date of the system is acquired, and the date value is used as a UserLabel assigned to the user, in this case, when mobile phone numbers are logged off and stopped by users, the mobile phone numbers should be allowed to sign up for use by other users after the next day.
In the following, it is described by taking { when a user transacts a mobile phone number, the telecom business office obtains the current time value of the system, and takes the time value as a userleel assigned to the user }, but the invention is not limited thereto.
For example, a UserLabel item is added in the subscription data of the user in the HLR for storing the UserLabel assigned to the corresponding user.
The HLR controls calls to subscribers through the userllabel assigned to that subscriber.
Based on the above thought, the present invention proposes kinds of communication control methods, for the route query message carrying the destination userllabel sent by the requester received by the HLR, the method executes the following procedures:
and 11, acquiring the current UserLabel of the destination number of the message, namely the newest UserLabel of the destination number. For example, the latest userllabel is acquired from the subscription data of the destination number.
And 12, performing UserLabel verification, namely comparing the target UserLabel of the message with the current UserLabel, if the target UserLabel of the message and the current UserLabel are , performing step 13, namely processing according to a normal flow, and otherwise, performing step 15, namely processing according to an abnormal flow.
In step 12, when the destination userllabel of the message is greater than or equal to the current userllabel, both result, otherwise, when the destination userllabel of the message is less than the current userllabel, both do not result.
Referring to fig. 1, a flow chart of the general embodiment of the invention is shown.
In step 15, the processing by exception flow may be returning an exception report to the requester. Information indicating that "UserLabel has been updated" may be carried in the exception report. The requester can know that the current UserLabel of the destination number is changed according to the reply message, namely that the subscriber corresponding to the destination number is changed.
In step 13, the normal process may be that the HLR requests a roaming number from the MSCS/VLR where the called subscriber is currently located, and then returns corresponding routing information to the requester, , the routing information returned by the HLR contains a roaming number (MSRN) of the mobile station corresponding to the corresponding destination number.
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.
When the ESME sends short messages to SMSC, according to the method provided by the invention, the control of communication is implemented in the HLR of the mobile communication network side, and the HLR controls the route inquiry operation, so that the mobile communication network side can not send the short messages to the old users of mobile phone numbers to the new users of the mobile phone numbers.
According to the invention, when SMSC sends route inquiry message to corresponding HLR according to the destination number of short message, the SMSC also carries the destination UserLabel of short message in the message, thus, the HLR can control the corresponding route inquiry operation according to the current UserLabel of the stored destination number, and further control the sending of short message.
As shown in fig. 2, a flowchart according to an embodiment of the present invention includes the following steps:
and step 100, receiving the short message carrying the destination number and the destination UserLabel by the SMSC.
Step 101, the SMSC sends a route query request to the HLR according to the destination number of the short message, wherein the request carries the destination UserLabel.
102, after receiving the query request, the HLR acquires the current UserLabel of the destination number, executes UserLabel verification, compares the destination UserLabel of the message with the current UserLabel, if the destination UserLabel of the message and the current UserLabel are , executes 103, acquires the routing information corresponding to the destination number, and replies the query result to the SMSC, otherwise, executes 105, and returns an abnormal report to the SMSC.
In step 102, both result when the destination userllabel of the message is greater than or equal to the current userllabel, otherwise, both result when the destination userllabel of the message is less than the current userllabel.
In step 103, , the HLR sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests roaming numbers to the MSCs/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.
When the SMSC sends the short message according to the routing information, the destination UserLabel can not be included any more, so that the complete compatibility with the current network is maintained. This will not be repeated in the following.
In step 105, information indicating that "UserLabel updated" may be carried in the exception report. Thus, according to the reply message, the user can know that the current subscriber of the destination number has changed.
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 when the mobile phone number is registered, i.e., the registration time (or binding 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 a corresponding short message through a mobile phone number registered by the user A, and the registration time is used as a destination UserLabel 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 destination UserLabel of the short message; the HLR acquires the current UserLabel (UserLabel-A) of the mobile phone number, and compares the current UserLabel (UserLabel-A) with a target UserLabel value carried in a short message to find that the target UserLabel value is larger than the UserLabel-A, so that the execution can be performed according to a normal flow, namely, the routing information corresponding to the target number is acquired from the MSCS/VLR of the current roaming of the mobile phone number, and the query 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 saved in the bank account is less than the contract time of the user B.
At the moment, when a bank needs to send a short message to a user A, the bank sends a corresponding short message through a mobile phone number registered by the user A, and the registration time is used as a target UserLabel 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 destination UserLabel of the short message; the HLR acquires the current UserLabel (namely UserLabel-B) of the mobile phone number, and compares the current UserLabel (namely UserLabel-B) with a target UserLabel value carried in the short message to find that the target UserLabel value is smaller than the UserLabel-B, so that the SMSC receives an 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.
In the present network, if a cell is not utilized, the cell is set to 0 in the case of , in the present invention, 0 can be regarded as a UserLabel compatible value, in this case, when the HLR judges that the destination UserLabel is a compatible value of 0, the SMSC is not updated, that is, the routing query message is not sent according to the method of the present invention, for example, the corresponding destination UserLabel value is not carried in the routing query message, and thus, the corresponding cell is set to 0 by default, if the HLR judges that the destination UserLabel is a compatible value of 0, the processing is performed according to the prior art, for example, step 103 is turned to.
As shown in fig. 3, a flowchart of a specific embodiment of the present invention considering compatibility is shown, in which before the step 105, a step 104 is further included: judging whether the target UserLabel is a compatible value of 0, if so, processing according to the compatible existing protocol mode, namely, turning to step 103; otherwise, step 105 is performed.
In practice, the HLR may also be instructed to perform compatibility processing by different protocol version identifiers.
Of course, the present invention can also be implemented by directly modifying the corresponding protocol regardless of the compatibility problem.
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 again to use the mobile phone number, and in this case, when the banking system sends a short message to the user a and sends a routing query request to the HLR, since the user label assigned to the current user of the mobile phone number stored in the HLR has changed, an abnormal flow may be caused: an exception report is returned to the SMSC, blocking the sending of the short message.
Based on the communication blocking security guarantee 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 (also comprising an SMSC) can control the calling or communication flow based on the UserLabel assigned to users, 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 to be sent to old users of mobile phone numbers can be effectively prevented from being sent to new users of the mobile phone numbers, the method saves the registration time of the corresponding mobile phone numbers in advance, and the method refers to the registration time table shown in Table 2.
TABLE 2
According to the table, from mobile phone numbers, the corresponding registration time can be acquired.
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 the internet application server (including the bank system platform server), the invention proposes new binding relations between mobile phone numbers and corresponding internet account numbers, on the basis of binding relations that only the mobile phone numbers are stored according to the internet account numbers originally, a registration time element is added, namely the mobile phone numbers which are registered (or bound) and the registration time when the mobile phone numbers are registered (or bound) are stored according to the internet account numbers, for example, when a user binds mobile phone numbers to corresponding bank accounts or internet accounts, the time for executing binding is also stored as the registration time in a corresponding binding relation record when boarding the corresponding mobile phone numbers, in this case, the registration time table as shown in table 2 is usually embedded into the corresponding account record table, so that corresponding relation tables of 'account numbers-mobile phone numbers-registration time' exist in the account record table, see the binding relation 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, according to internet accounts, a corresponding bound mobile phone number and a registration time when the binding is performed can be acquired, and also, according to mobile phone numbers, a bound internet account and a registration time when the binding is performed can be acquired.
As specific cases, if there is an implicit correspondence 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 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 code-based.
For example, there are implicit correspondences between the Internet account number 13316882017@163.com and the cell phone number 13316882017, where the related cell phone number is available from the name part 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.
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 records, the mobile phone number field in the binding relationship table shown in table 3 may be omitted, see the binding relationship table 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 internet account number in the binding relationship record can be used to obtain the corresponding bound mobile phone number. For example, a WeChat is registered by a mobile phone number, or a 163 mailbox is registered by a mobile phone number, and then the mobile phone number can be used as a login account to log in the WeChat or the 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 the short message, firstly obtaining the registration time of the stored target mobile phone number, then taking the registration time of the target mobile phone number as the target UserLabel of the message, and sending the short message to the SMSC according to the target mobile phone number. The SMSC is then able to proceed to step 100 and the corresponding flow thereafter.
Referring to fig. 4, it is a flow chart of the method for sending short message in the present invention, and the flow chart includes the following steps:
and step 41, acquiring the registration time of the stored destination mobile phone number.
And step 42, taking the registration time of the target mobile phone number as a target UserLabel of the message, and sending the short message to the SMSC according to the target mobile phone number.
For the mobile terminal, when step 41 is executed, the registration time stored correspondingly is directly obtained from the corresponding contact record according to the destination mobile phone number.
When the registration time in the contact record corresponding to the destination mobile phone number is less than the current userllabel of the mobile phone 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 target mobile phone number through the mobile communication network.
For internet application servers (including banking system platform servers), the corresponding saved registration time is directly obtained from the corresponding binding relationship record when step 41 is executed.
When the registration time in the binding relationship record corresponding to the destination mobile phone number is less than the current userllabel of the mobile phone number, it indicates that the corresponding registration or binding operation is before the latest subscription 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 target mobile phone 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 also carries the destination UserLabel of the short message; otherwise, processing according to the normal flow.
For example, the processing according to the normal flow includes that the HLR sends a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requests roaming numbers to the MSCs/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.
For example, the processing according to the exception flow is: a reply message indicating "UserLabel updated" is returned to the SMSC via an exception report. According to the reply message, the current subscriber of the destination number can be known to have changed. It will be appreciated that the SMSC may reply with the exception report to the sender of the short message, for example the mobile terminal or an internet application server.
When an internet application server (including a bank system) needs to send a short message according to mobile phone numbers in binding relationship records, the short message also carries registration time in the binding relationship records as a destination UserLabel of the message, so that when the signed user of the mobile phone number in the binding relationship records does not change, the short message can be sent to a corresponding mobile phone number user through a mobile communication network, otherwise, if the signed user of the mobile phone number in the binding relationship records sends a change, for example, the user A changes into the user B, the corresponding SMSC can inquire routing information from the HLR according to the corresponding mobile phone number because the UserLabel currently assigned to the mobile phone number in the mobile communication network changes, so that the corresponding SMSC can not transmit the registration time in the binding relationship records as the destination UserLabel of the message, so as to ensure the security of the user A and avoid the privacy disturbance of the user B.
According to the invention, the short message of the old user to be sent to mobile phone numbers can be effectively prevented from being sent to the new user of the mobile phone number, thus the problem that when an internet application server such as a bank server sends the short message to the mobile phone number bound by the corresponding account number, the short message is sent to the new user B under the condition that the mobile phone number is logged off by the old user A and is registered and used by the new user B, and the like can be effectively solved.
As known, when a user transacts business in a bank business hall, registers the mobile phone number to be bound of the own bank account on the counter, in this case, the bank counter operating end can directly send the mobile phone number and the registration time registered by the user to the bank background server for storage, thereby completing the binding operation.
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 may 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 users.
Generally, when a user establishes a binding relationship, the user logs in a corresponding internet account first, and then performs a binding operation.
As shown in fig. 5, a flowchart of an embodiment of a method for establishing a binding relationship is shown, where the method includes the following steps:
step 51, the application server receives a mobile phone number to be bound to the current internet account.
Step 52: the application server generates a verification code; and taking the current time value or date value as a target UserLabel, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the short message carries the generated verification code.
Step 58, 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 not , the process is ended, and if the verification code is , step 59 is executed.
And step 59, the application server establishes a corresponding relation between the corresponding internet 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 a binding relationship table shown in table 3 according to the corresponding internet 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 current userllabel of mobile phone numbers, so that when the destination userllabel carried by the short message is smaller than the latest userllabel of the destination number of the short message, the short message is 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 the step 52, the following sub-process is executed on the mobile communication network side, and in the sub-process, the following steps are included:
and step T11, after the corresponding SMSC receives the short message, sending a route query message carrying the destination UserLabel value to the corresponding HLR according to the destination number of the short message.
Step T12, after receiving the route inquiry message, the HLR acquires the current UserLabel of the destination number, judges whether the destination UserLabel carried by the short message is smaller than the current UserLabel, if yes, executes step T14; otherwise, step T13 is executed.
And step T13, sending a roaming number query request to the MSC/VLR where the destination number is currently roaming, that is, requesting roaming numbers to the MSCS/VLR where the destination number is currently located, receiving a return message of the MSC/VLR, sending the roaming numbers to the SMSC, and sending the verification codes to the user terminal of the destination number by short messages through the corresponding MSC/VLR according to the roaming numbers by the SMSC.
Step T14, by exception reporting, returns a reply message to the SMSC indicating "userllabel updated".
After step T14, the SMSC may reply with the exception report to the application server.
Based on the new binding relationship, when short messages need to be sent according to mobile phone numbers, a destination UserLabel (mobile communication network) side which can take the registration time in the binding relationship record as a message can execute UserLabel verification operation, namely, whether the UserLabel in the binding relationship record is smaller than the current UserLabel of the mobile phone number is judged, if so, the corresponding short message is not sent any more, otherwise, the verification is passed, and a subsequent short message sending process is executed, thus, the short message of an old user which needs to be sent to mobile phone numbers can be effectively prevented from being sent to a new user of the mobile phone number, and therefore, the problem that when a bank server sends the short message to a mobile phone number user which is bound to a corresponding account number, the mobile phone number is logged out by the old user and is registered and used by the new user, 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 following user is assigned with a new UserLabel, namely in the mobile communication network, the current UserLabel of the mobile phone number is changed, so that the following user is blocked from obtaining the verification code of the internet account bound by the previous old user according to the mobile phone number through the signed mobile phone number, the safety of the internet account of the old user is ensured, and the trouble that the old user unbinds the cancelled mobile phone number for each internet account is avoided.
In the invention, when the short message is sent, the message carries the target UserLabel, the UserLabel can be carried by using 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 UserLabel can be carried by the content of the short message.
For example, when the internet application server sends a short message to the corresponding SMSC, when the SMSC sends a route query message to the corresponding HLR, and so on, the destination userlail can be carried by using the idle cell or the extended cell, or adding the cell.
Particularly, when the internet application server sends the short message to the corresponding SMSC, the target userllabel can be carried by the content part of the short message.
For the network entities mentioned in the present invention, such as ESME, HLR, MSC, SMSC, VLR, etc., more detailed descriptions can be found in the relevant technical specification documents of 3GPP (3 GPP gprs 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.
For ease of description, the SMSC is considered part of the mobile communications network (in practice, SMSC is often considered to be a device outside of the mobile communications network.)
The invention treats the bank account as an internet account for convenience of description.
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 (5)
1, kinds of mobile communication control method, characterized by that, keep the present UserLabel in HLR according to the mobile phone number correspondence, for the route inquiry message that the HLR received carried the purpose UserLabel, said method comprises the following steps:
a. acquiring a current UserLabel of a destination number of a message;
b. comparing the target UserLabel of the message with the current UserLabel, if the target UserLabel of the message and the current UserLabel are , processing according to a normal flow, otherwise, processing according to an abnormal flow;
the "destination userllabel of the message is identical to the current userllabel " means that the destination userllabel of the message is not smaller than the current userllabel.
2. The method of claim 1, wherein 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.
3, SMSC query routing method, characterized in that the method comprises the following steps:
a. SMSC receives the short message carrying the destination number and the destination UserLabel;
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 destination UserLabel.
4, short message transmission method, which pre-stores the registration time of the corresponding mobile phone number, characterized in that, when transmitting short message according to destination mobile phone numbers, the method comprises the following steps:
a. acquiring the registration time of the stored target mobile phone number;
b. and taking the registration time of the target mobile phone number as a target UserLabel of the message, and sending the short message to an SMSC (short message service center) according to the target mobile phone number.
5, binding method for binding mobile phone numbers to internet accounts, characterized in that the method comprises the following steps:
a. the application server receives a mobile phone number to be bound by an internet account;
b. the application server generates a verification code; taking the current time value or date value as a target UserLabel, sending a short message to a corresponding SMSC according to the mobile phone number, wherein the short 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 and the generated verification code are , establishes the corresponding relation between the corresponding internet 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810807625.7A CN110740096A (en) | 2018-07-21 | 2018-07-21 | Mobile communication control method based on time tag |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810807625.7A CN110740096A (en) | 2018-07-21 | 2018-07-21 | Mobile communication control method based on time tag |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110740096A true CN110740096A (en) | 2020-01-31 |
Family
ID=69235578
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810807625.7A Pending CN110740096A (en) | 2018-07-21 | 2018-07-21 | Mobile communication control method based on time tag |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110740096A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110809266A (en) * | 2018-08-05 | 2020-02-18 | 王正伟 | Mobile communication control method based on time tag |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0428254A2 (en) * | 1989-09-20 | 1991-05-22 | Matsushita Graphic Communication Systems, Inc. | Circuitry for verifying communicants in a communication apparatus |
| CN1662076A (en) * | 2004-02-27 | 2005-08-31 | 华为技术有限公司 | Method for implementing transfer of short message |
| CN105809052A (en) * | 2014-12-31 | 2016-07-27 | 小米科技有限责任公司 | Binding information recording method and apparatus |
| CN106303099A (en) * | 2015-05-12 | 2017-01-04 | 中国移动通信集团公司 | A kind of verify the method for telex network number effectiveness, Apparatus and system |
| CN107846679A (en) * | 2016-09-20 | 2018-03-27 | 中国电信股份有限公司 | The telephone number secondary processing method distributed telephone numbers, system and business system |
| CN108243404A (en) * | 2016-12-23 | 2018-07-03 | 中国移动通信集团四川有限公司 | Ratification method, device and the equipment of phone number binding state |
-
2018
- 2018-07-21 CN CN201810807625.7A patent/CN110740096A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0428254A2 (en) * | 1989-09-20 | 1991-05-22 | Matsushita Graphic Communication Systems, Inc. | Circuitry for verifying communicants in a communication apparatus |
| CN1662076A (en) * | 2004-02-27 | 2005-08-31 | 华为技术有限公司 | Method for implementing transfer of short message |
| CN105809052A (en) * | 2014-12-31 | 2016-07-27 | 小米科技有限责任公司 | Binding information recording method and apparatus |
| CN106303099A (en) * | 2015-05-12 | 2017-01-04 | 中国移动通信集团公司 | A kind of verify the method for telex network number effectiveness, Apparatus and system |
| CN107846679A (en) * | 2016-09-20 | 2018-03-27 | 中国电信股份有限公司 | The telephone number secondary processing method distributed telephone numbers, system and business system |
| CN108243404A (en) * | 2016-12-23 | 2018-07-03 | 中国移动通信集团四川有限公司 | Ratification method, device and the equipment of phone number binding state |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110809266A (en) * | 2018-08-05 | 2020-02-18 | 王正伟 | Mobile communication control method based on time tag |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8874110B2 (en) | Method and apparatus for verification of a telephone number | |
| US8280373B2 (en) | Terminal device control server and method for controlling access to a mobile communication network | |
| CN108737366B (en) | Binding method | |
| CN110248321B (en) | Method and system for managing number portability number | |
| 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 | |
| CN108933789B (en) | Method for preventing personal information leakage and third-party application server | |
| US20140032493A1 (en) | Method, apparatus and system for synchronizing contact information | |
| CN105704640A (en) | Information processing method, device, supporting platform and system | |
| CN110545526A (en) | Mobile communication control method | |
| CN110740096A (en) | Mobile communication control method based on time tag | |
| CN101867918B (en) | Real-name system registration state acquiring method, device and terminal | |
| CN102056104A (en) | SM (Short Message) sending control method as well as device and system | |
| CN101330393B (en) | Method, terminal and network for providing service customization and customization service | |
| CN104754546B (en) | A kind of foreign countries' network registering method and device | |
| CN110809266A (en) | Mobile communication control method based on time tag | |
| FI113437B (en) | Checking the validity of a subscriber connection in a telecommunications system | |
| US20210385296A1 (en) | Method for configuring an internet service provider | |
| US20230262167A1 (en) | Method for processing a request from a communication terminal | |
| WO2024217991A1 (en) | Method and system for creating user accounts and establishing a communication link between two users | |
| CN111294788B (en) | Message processing method, device, gateway and computer storage medium | |
| KR100851582B1 (en) | Method and device for transmitting long message to roamed terminal | |
| KR101051021B1 (en) | Incoming call history providing method and system | |
| JP4769317B2 (en) | Exchange, message transmission system, and message transmission method | |
| CN118802908A (en) | Authentication resource sharing method, device, equipment, storage medium and program product | |
| CN116017326A (en) | Short message trusted method and short message trusted platform |
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: 20200131 |