CN110545526A

CN110545526A - Mobile communication control method

Info

Publication number: CN110545526A
Application number: CN201810522467.0A
Authority: CN
Inventors: 王正伟
Original assignee: Individual
Current assignee: Individual
Priority date: 2018-05-28
Filing date: 2018-05-28
Publication date: 2019-12-06

Abstract

The invention discloses a mobile communication control method, which achieves the control of a call flow by saving a UserLabel currently assigned to a user in user subscription data and controlling a route query operation carrying a target UserLabel in a call process, thereby avoiding sending a message of an old user to be given to a number to a new user of the number, eliminating the disturbance to the new user, and protecting a message sender and the privacy of the old user. And when the binding relation is established, a UserLabel factor is introduced, so that when the message is sent to the corresponding mobile phone number based on the binding relation, the message which is about to be sent to the old user of the number can be prevented from being sent to the new user of the number. Therefore, the security problem that the mobile phone number is bound by the internet account such as a bank account, a WeChat account, a Paibao account and the like which widely exists at present can be solved.

Description

Mobile communication control method

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 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 applies for a new cell phone number. And the old mobile phone number of the user A is registered and used by the user B. Under the circumstance, the user B is likely to receive the short message sent by the friend of the user A, so that harassment is caused to the user B, privacy information of the user A and the friend of the user A is leaked, and potential safety hazards are brought to the user A and the friend of the user A. For example, there is often a reaction that the mobile phone receives the call from the friend of the user or the business related person who has used the current mobile phone number, or sends 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 telephone 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 password can be retrieved through the 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 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 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

Accordingly, the present invention is directed to a mobile communication control method that at least partially solves the above-mentioned problems. The method controls the call flow by storing the UserLabel currently assigned to the user in the user subscription data and controlling the route query operation carrying the target UserLabel in the call process, thereby avoiding the message of the old user about to be sent to a number from being sent to the new user of the number, eliminating the harassment to the receiver and protecting the message sender and the privacy of the old user of the number.

A mobile communication control method, store the present UserLabel in HLR according to the mobile phone number correspondence, for the route inquiry message that the HLR received carries the purpose UserLabel, said method comprises the following steps:

a. acquiring a current UserLabel of a destination number of a message;

b. Comparing the current UserLabel with the destination UserLabel of the message, if the current UserLabel and the destination UserLabel are consistent, executing the step c: processing according to a normal flow; otherwise, executing step d: and processing according to the exception 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.

Optionally, the step d further comprises: and returning the current UserLabel of the destination number to the requester.

Optionally, the step d further comprises: and judging whether the destination UserLabel is a special value, and if so, returning the current UserLabel of the destination number to the requester.

Optionally, the step d further comprises: and c, judging whether the destination UserLabel is a special value, if so, returning the current UserLabel of the destination number to the requester, and turning to the step c.

Optionally, the step d further comprises: and c, judging whether the target UserLabel is a compatible value, and if so, turning to the step c.

The invention also provides an account binding method, which at least partially solves the problems. The method introduces a UserLabel factor when establishing the binding relationship, thus avoiding sending the message of the old user to the number to the new user of the number when sending the message based on the bound mobile phone number. Therefore, the security problem that the mobile phone number is bound by the internet account such as a bank account, a WeChat account, a Paibao account and the like which widely exists at present can be solved.

a binding method, is used for binding a mobile phone number to an Internet account; the method comprises the following steps:

a. receiving a mobile phone number;

b. Sending a short message to a corresponding SMSC according to the mobile phone number, wherein the message carries a special UserLabel value as a target UserLabel; receiving the current UserLabel of the mobile phone number replied by the SMSC;

g. And establishing a corresponding relation among the corresponding internet account, the mobile phone number and the current UserLabel.

Optionally, the internet account is further a code-based internet account to be created;

Step g is preceded by step d: and e, judging whether a code-based internet account corresponding to the mobile phone number exists, if so, executing the step e, otherwise, executing the step f.

The step e is as follows: comparing whether the UserLabel of the code-based Internet account is consistent with the current UserLabel or not, if so, processing according to an abnormal flow, otherwise, freezing or canceling the code-based Internet account, and executing the step f;

f. Creating a code-based internet account according to the mobile phone number;

The step g further comprises: and establishing a corresponding relation between the created code-based Internet account and the current UserLabel.

optionally, step g is preceded by step c: generating a verification code, sending the verification code according to the mobile phone number, and taking the current UserLabel as a target UserLabel in a message; and g, receiving the returned verification code, judging whether the received verification code is consistent with the generated verification code, and executing the step g if the received verification code is consistent with the generated verification code.

Optionally, step b is further: generating a verification code, sending the generated verification code to a corresponding SMSC through a short message according to the mobile phone number, and carrying a special UserLabel value in the message as a target UserLabel; receiving the current UserLabel of the mobile phone number replied by the SMSC; receiving a returned verification code; and g, judging whether the received verification code is consistent with the generated verification code, and executing the step g if the received verification code is consistent with the generated verification code.

In the technical scheme provided by the embodiment, the latest UserLabel is assigned to the corresponding number, so that different processing or response can be performed on the message according to the purpose UserLabel of the message, the problem that the message which is originally sent to an old user of a number is mistakenly sent to a new user of the number can be avoided, the new user is prevented from being harassed, the privacy of the old user and friends of the old user is effectively protected, and the overall safety of the communication between a telecommunication network and the Internet is improved.

In the technical solution provided in the above embodiment, because the userllabel factor is introduced into the binding relationship, the message can be filtered through the latest userllabel of one mobile phone number, so that the short message of the old user to be sent to the bound mobile phone number is not sent to the new user of the mobile phone number. The verification code issuing method and the mobile phone number binding method provided by the invention can effectively eliminate the safety risk caused by the fact that a user replaces the mobile phone number, such as the mobile phone number logins WeChat, the mobile phone number logins Payment treasures, the verification code sent by a bank is received by a mobile phone, and the like, which are widely existed at present.

Drawings

FIG. 1 is a flow chart of the general embodiment of the present invention.

FIG. 2 is a flow chart of 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 an embodiment of the present invention.

FIG. 5 is a flowchart illustrating an embodiment of the present invention.

Fig. 6 is a flowchart illustrating a verification code issuing control method according to the present invention.

Fig. 7 is a flowchart illustrating a second verification code issuing control method according to the present invention.

FIG. 8 is a flowchart of an embodiment of a method for establishing a binding relationship.

Fig. 9 is a flowchart illustrating an embodiment of a binding method for code-based internet account registration according to the present invention.

FIG. 10 is a flowchart of an embodiment of a method for establishing a binding relationship.

Fig. 11 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 intended for an old user of a mobile phone number from being sent to a new user of the mobile phone, the invention proposes to assign a user a tag, called user tag (UserLabel), for distinguishing different users who register (or sign) one after the other using the same mobile phone number.

The user label assigned to a user is also referred to as the user label for the user's cell phone number.

the operation of assigning the UserLabel to the user can be carried out when the user transacts the mobile phone number; or when the user requests to change the userllabel, for example, when the phone number between family members is transferred and used, the corresponding user may request to change the userllabel.

For example, when a user transacts a mobile phone number, the telecom business office obtains the current time value of the system, and uses the time value as the UserLabel assigned to the user.

For example, when the user transacts the mobile phone number, the current date of the system is acquired, and the date value is used as the UserLabel assigned to the user. In this case, when a mobile phone number is logged off by a user and deactivated, the mobile phone number is allowed to be applied by other users for use after the next day.

Other ways of assigning a user to a userllabel are possible. See invention patent of communication control method with application number 201810271583.X, and here, the abstract is not repeated.

And storing the current UserLabel of the mobile phone number at one side of the HLR according to the corresponding mobile phone number. For example, a userllabel entry is added to the subscription data of the subscriber in the HLR for storing the userllabel currently assigned to the corresponding subscriber.

The HLR controls calls directed to a subscriber through a userllabel assigned to that subscriber. The call may be a voice call, or a short message call, or other form of call.

Based on the above thought, the present invention provides a communication control method, for the HLR receiving the route inquiry message carrying the destination userllabel sent by the requester, 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.

And step 12, executing UserLabel verification: comparing the current UserLabel with a destination UserLabel of the message; if the two are consistent, step 13 is executed: processing according to a normal flow; otherwise, step 14 is executed: and processing according to the exception flow.

Referring to fig. 1, a flow chart of the general embodiment of the invention is shown.

in step 13, the processing according to the normal flow may be: HLR requests roaming number to MSCS/VLR where the called user is located, then HLR returns corresponding routing information to the requester. Generally, the routing information returned by the HLR contains a roaming number (MSRN) of the mobile station corresponding to the corresponding destination number. For example, the HLR forwards the roaming number returned by the MSCS/VLR to the requester.

The requester can be an MSC, a GMSC, or an SMSC.

In step 14, 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.

In particular, the current userllabel of the destination number can also be carried in the exception report.

The following is an example where the requestor is an SMSC, but is not intended to limit the invention.

When the ESME sends the short message to the SMSC, the control of the communication is implemented in the HLR of the mobile communication network side according to the method provided by the invention. The HLR controls the route inquiring operation, so that the mobile communication network side can not send the short message of the old user to a telephone number to the new user of the telephone number.

When an SMSC sends a route inquiry message to a corresponding HLR according to the destination number of the short message, the message carries the destination UserLabel of the short message, so that the HLR can control the corresponding route inquiry operation according to the stored current UserLabel of the destination number, and further control the sending of the short message.

FIG. 2 is a flow chart of an embodiment of the present invention, which includes the following steps:

Step 100, the SMSC receives the short message carrying the destination number and the destination UserLabel.

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 a destination UserLabel.

Step 102, after receiving the query request, the HLR acquires the current UserLabel of the destination number, and compares the current UserLabel with the destination UserLabel of the message; if the two are consistent, step 103 is executed: obtaining the routing information corresponding to the destination number, replying the query result to the SMSC, and ending; otherwise, go to step 105: an exception report is returned 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 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 corresponding 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 Label with the current destination number changed can be known.

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 by the user A and is originally sent to the user A after the subsequent user B applies to use the number.

According to the technical scheme provided by the invention, when the bank registers the mobile phone number of the user A, the bank also registers the UserLabel currently assigned to the user A, such as UserLabel-A. And after the user A stops using the mobile phone number, the user B starts to register to use the mobile phone number, and when the user B handles the mobile phone number signing procedure, the currently assigned UserLabel by the telecom operator to the user B is UserLabel-B. Thus, when a bank tries to send a short message through the mobile phone number registered by the user A and the destination UserLabel value UserLabel-A, when the corresponding SMSC inquires routing information from the HLR to which the mobile phone number belongs, the current UserLabel of the mobile phone number acquired by the HLR is UserLabel-B, and is compared with the destination UserLabel value UserLabel-A carried in the short message (see step 101 and step 102), and the current UserLabel is found to be inconsistent with the destination UserLabel value UserLabel-A, so that the SMSC receives an abnormal report, and the corresponding short message is prevented from being sent, namely cannot be sent to the user B. Therefore, the embarrassing situation that the user B is disturbed and the user A is divulged of a secret is eliminated.

When the user transacts the number signing procedure, the user label currently assigned to the user can be obtained from the telecom operator. Therefore, when the mobile phone number of the user is registered in the bank account, the user Label with the currently assigned mobile phone number can be provided at the same time.

Of course, when the user registers his mobile phone number in the bank account, the user label to which his mobile phone number is currently assigned may not be provided. In this case, the banking system should query the currently assigned userllabel from the operator of the telecommunication network (for example, from the mobile communication network side) according to the mobile phone number registered by the user. Thus, great convenience can be provided for the user. As this does not require the user to remember the userllabel to which his mobile number is assigned.

in fact, in step 105, the current userllabel of the destination number may be carried in the exception report. In this case, the step 105 is further a step 105B: and returning an exception report to the SMSC, wherein the exception report carries the current UserLabel of the acquired destination number.

According to the step 105B, the user label to which the mobile phone number is currently assigned can be queried from the HLR by carrying an invalid user label value in the short message to cause an exception handling procedure.

In practice, it may be agreed that the valid UserLabel assigned to a number is greater than 0. In this case, the SMSC may query the HLR for the current userlame value of a mobile phone number by { sending a route query request to the HLR, carrying an invalid destination userlame value of 0 in the request }.

Of course, for compatibility reasons, it is also possible to specify that the valid UserLabel values assigned to a number are all greater than 1. In this case, both 0 and 1 are invalid destination UserLabel values. Thus, the SMSC can inquire the current UserLabel value of a mobile phone number from the HLR by { sending a routing inquiry request to the HLR, wherein the request carries an invalid destination UserLabel value of 1 }. Wherein an invalid UserLabel value of 0 is used to instruct the HLR to perform compatibility processing.

For example, when sending a route query to the HLR, carrying the destination userllabel value is done by using some idle cell of the existing protocol. In existing networks, the cell is not utilized, and is normally set to 0. In practicing the present invention, 0 can be considered a UserLabel compatible value. In this case, it can be agreed that the valid userlame assigned to a number is greater than 1, and the current userlame value of a mobile phone number is queried from the HLR by sending a routing query request to the HLR, carrying an invalid destination userlame value 1 in the request. In this case, when the HLR determines that the destination userlame is a compatible value of 0, the SMSC is considered not to be upgraded, that is, the routing query message is not sent according to the processing method of the present invention, for example, the routing query message does not carry the corresponding destination userlame value, and thus, the corresponding cell is set to 0 by default. If the destination UserLabel value is 1, all the effective UserLabel are larger than 1, so that the UserLabel comparison is not passed, an exception report is sent to the SMSC, and the report carries the currently assigned UserLabel of the corresponding destination number. If the HLR determines that the destination UserLabel is a compatible value of 0, then the process proceeds as in the prior art, e.g., to step 103.

As shown in fig. 3, a flowchart of a specific embodiment of the present invention considering compatibility is shown, in which before the step 105B, 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 105B is performed.

In practice, the HLR may also be instructed to perform compatibility processing by different protocol version identifiers.

In the following use cases, for the convenience of reading by technicians, details on compatibility are not repeated.

In the latter case, the valid UserLabel assigned to a given number is agreed to be greater than 1. And the appointed SMSC queries the current UserLabel value of a mobile phone number from the HLR by { carrying the invalid destination UserLabel value 1 in the request when sending a route query request to the HLR }.

For the bank system, when the bank system needs to inquire a current UserLabel of a mobile phone number, after a short message carrying a target UserLabel value of 1 is sent to an SMSC, the SMSC can send a routing inquiry request carrying the target UserLabel value of 1 to a corresponding HLR so as to inquire the currently assigned UserLabel of the corresponding mobile phone number from the HLR, and reply the current UserLabel returned by the HLR to the bank system, and the bank system stores the current UserLabel according to the mobile phone number.

When a short message is sent to a mobile phone number user, if the current UserLabel of the mobile phone number is unknown, the bank system can send the short message by setting the target UserLabel of the short message to 1, so that the current UserLabel of the mobile phone number stored in the HLR can be inquired by the SMSC. Thus, the next time the short message is sent, the correct destination UserLabel value can be filled in.

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, since the user label currently assigned to the user of the mobile phone number stored in the HLR has changed, an abnormal flow is caused: an exception report is returned to the SMSC. In this case, it is not necessary that the HLR returns to the SMSC the userllabel to which the current subscriber of the mobile number is currently assigned. Because the banking system does not have to query the userlarel to which the mobile phone number registered by the user a is assigned. Since the userllabel of user a has been previously queried and registered.

according to the step 105B, when a user label of a current mobile phone number is to be queried, there are many situations in which the destination user label value of a corresponding short message may be. E.g., 1, -2, etc., or other impossible values, e.g., a value at some time after 20 years.

in fact, in order to prevent the HLR from carrying the current userllabel of the corresponding mobile phone number in any exception report, a special value of the userllabel for query may be agreed, for example, the special value of the userllabel is agreed to be 1.

Referring now to FIG. 4, a flowchart illustrating an embodiment of the present invention, wherein step 105 is further illustrated as step 105C: judging whether the destination UserLabel is 1, if so, executing the step 106: and returning an exception report to the SMSC, wherein the exception report carries the current UserLabel value of the acquired destination number.

In step 105C, if the destination userllabel is not 1, such as the above-mentioned userllabel value userllabel-B assigned to user B, then step 107 is performed: and returning an exception report to the SMSC, wherein the exception report carries information indicating that the UserLabel is updated. Thus, the SMSC can know that the user using the corresponding mobile phone number has changed.

The inquiry of the current UserLabel of a mobile phone number and the real transmission of a short message are divided into two parts. That is, when a short message is to be sent to a mobile phone number user, if the user currently assigned userlame is unknown, the user currently assigned userlame needs to be queried first, and then the short message is sent through the obtained userlame of the user.

For the end-to-end situation that the user C sends the short message to the user a, according to step 105C, the process of sending the short message to the user a for the first time can be completed only by sending the short message twice by the user C mobile phone terminal.

preferably, in step 105C, when the destination userllabel is determined to be the special value 1, step 103 is further executed.

As shown in fig. 5, which is a flowchart of a specific embodiment of the present invention, in the step 105, a step 105D is further performed: and judging whether the destination UserLabel is 1, if so, executing the step 106, and then, turning to the step 103, otherwise, executing the step 107.

According to step 105D, the purpose of querying the current userllabel value of the corresponding destination number can be achieved by setting the destination userllabel value of the short message to a special value of 1, and the short message can be sent to the mobile phone of the user with the destination number. Two purposes are achieved at one stroke.

Based on a communication blocking security mechanism provided by a communication control method invention patent with application number 201810271583.X or a mobile communication control method provided by the above embodiment, an existing network can be modified, so that a mobile communication network side (also including an SMSC) can control a call or a communication flow based on a 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 internet account.

According to the technical scheme of the communication control method provided by the communication control method, in particular, based on the technical scheme of the control method for sending short messages provided by the related embodiment, the invention firstly provides a new binding relationship between a mobile phone number and a corresponding internet account, and based on the new binding relationship, the invention provides a new verification code issuing control process, namely a new verification code issuing control method; based on the new binding relationship, the invention also provides a new binding relationship establishing method. By implementing the technical scheme provided by the two new methods, the problem of potential safety hazards existing in the existing scheme of 'Internet account number binding mobile phone number' widely applied at present can be effectively solved.

The binding relationship between the mobile phone number and the corresponding internet account number provided by the invention is as follows: on the basis of the original binding relationship that the mobile phone number is only stored according to the internet account, UserLabel elements are added, namely the bound mobile phone number and the related UserLabel are stored according to the internet account. See the binding relationship table as shown in table 3.

TABLE 3

Internet account	mobile phone number	UserLabel
			Internet Account number 1	Mobile phone number 1	UserLabel1
Internet Account 2	Mobile phone number 2	UserLabel2
			Internet Account number 3	Mobile phone number 3	UserLabel3
Internet account 4	Mobile phone number 4	UserLabel4
			Internet account 5	mobile phone number 5	UserLabel5
Internet account number 6	Mobile phone number 6	UserLabel6
			internet account 7	Mobile phone number 7	UserLabel7

According to the table, the mobile phone number and the UserLabel thereof which are correspondingly bound can be obtained according to an Internet account. Similarly, according to a mobile phone number, the bound internet account number can be acquired, and the user label of the mobile phone number can be acquired when the binding is executed.

As a special example, if an implicit corresponding relationship exists 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 the 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 is an implicit correspondence between the internet account number 13316882017@163.com and 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.

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 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	UserLabel
		13316882017@163.com	UserLabel1
13823755663@163.com	UserLabel2
		13513556789@163.com	UserLabel3

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 an internet server (including a bank system) needs to send a short message according to a mobile phone number in a binding relationship record, the short message also carries a UserLabel registered in the binding relationship record as a destination UserLabel of the message. Therefore, when the mobile phone number user does not change in the binding relation record, the short message can be sent to the corresponding mobile phone number user through the mobile communication network; otherwise, if the mobile phone number user in the binding relationship record sends a change, for example, the user a changes into the user b, the user label currently assigned to the user in the mobile communication network changes, so that the corresponding SMSC is abnormal when inquiring the routing information from the HLR according to the mobile phone number, and the corresponding short message cannot be transmitted to the existing user 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 problem that when the bank server sends a short message to the mobile phone number bound by the corresponding account, 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 can be effectively solved.

Based on the thought, the invention also provides a verification code issuing control method, which establishes the binding relationship between the corresponding internet account and the corresponding mobile phone number in advance, and registers the UserLabel of the mobile phone number in the corresponding binding relationship record. See the binding table as shown in table 3 or the binding table as shown in table 3-a.

When the verification code issuing process is triggered, the server executes the verification code issuing process implemented according to the verification code issuing control method provided by the invention, so that the condition that the verification code of the old user to be sent to a mobile phone number is sent to the new user of the mobile phone number can be avoided.

There are many ways to trigger the server to initiate the verification code issuance process.

For example, when a user logs in an internet account, the user forgets a password, directly requests the server to send a verification code according to a mobile phone number bound in advance, and after receiving the request, the server can trigger a verification code issuing process. Here, the request carries a corresponding internet account, and the server determines a corresponding binding relationship record according to the account; or, the request carries the mobile phone number input by the user, and the server determines the corresponding binding relation record according to the mobile phone number.

For example, to enhance security or reduce server harassment, the client also requires the user to input a mobile phone number, and when requesting to send the verification code to the server, the mobile phone number input by the user is also carried. After receiving the request, the server judges whether the mobile phone number is the mobile phone number bound by the corresponding account, if not, the process is ended; otherwise, the verification code issuing process is triggered. Here, the request carries a corresponding internet account, and the server determines a corresponding binding relationship record according to the account.

Also for example, where the bundled cell phone number can be derived from an internet account, the client may only provide the cell phone number when requesting the server to send the verification code. In this case, the server may directly determine the corresponding binding relationship according to the mobile phone number, and trigger the verification code issuing process after determining the binding relationship record.

Particularly, whether the bundled mobile phone number can be derived from the internet account or not, the client only requires the user to provide the mobile phone number, and requests the server to send the verification code after acquiring the mobile phone number input by the user, wherein the verification code is carried in the request. And after receiving the request, the corresponding server determines a corresponding binding relation record according to the mobile phone number, and triggers a verification code issuing process after finding the corresponding binding relation record.

Under the condition that the bundled mobile phone number cannot be derived from the internet account, preferably, when the client requests to send a verification code to the server, the client lets the user input the corresponding internet account and the corresponding mobile phone number, when the client sends the corresponding request to the server, the client carries the corresponding internet account and the corresponding mobile phone number input by the user, after the server receives the request, the server directly determines a bundling relationship record according to the internet account and the corresponding mobile phone number, and after finding a matched record, the client triggers a verification code issuing process.

Referring to fig. 6, a flowchart of a verification code issuance control method according to the present invention is shown, where the method includes the following steps:

Step 51, the server generates a verification code.

And step 52, the server sends the generated verification code according to the mobile phone number and the UserLabel in the corresponding binding relation record.

To { step 52 is: the server sends the verification code through a short message according to the mobile phone number in the corresponding binding relationship record, and the short message carries the UserLabel in the binding relationship record as an example of a target UserLabel.

And when the UserLabel in the obtained binding relationship record is consistent with the current UserLabel of the mobile phone number, the short message can be transmitted to a corresponding mobile phone terminal through a mobile communication network, otherwise, the short message is filtered.

For example: after receiving the short message sent by the server, the corresponding SMSC sends a routing query request to the corresponding HLR according to the destination number of the short message, the request also carries the destination UserLabel of the short message, after receiving the query request, the HLR queries the current UserLabel of the destination number, compares the current UserLabel with the destination UserLabel of the short message, and processes according to a normal flow if the current UserLabel is consistent with the destination UserLabel of the short message; otherwise, processing according to the abnormal 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 MSCS/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: replying to the SMSC a reply message indicating "UserLabel updated". According to the reply message, the user that the destination number is currently changed can be known.

For example, the processing according to the exception flow is: and returning an exception report to the SMSC, wherein the exception report carries the current UserLabel of the acquired destination number.

for example, the processing according to the exception flow is: and judging whether the destination UserLabel is 1, if so, returning an exception report to the SMSC, wherein the exception report carries the current UserLabel of the destination number.

For example, the processing according to the exception flow is: judging whether the destination UserLabel is 1, if so, returning an exception report to the SMSC, wherein the exception report carries the current UserLabel of the destination number; go to step 103.

And after receiving the current UserLabel of the destination number returned by the corresponding HLR, the SMSC forwards (or replies) the current UserLabel to the server.

It should be noted that, the server side may also obtain a current userllabel of the mobile phone number from the mobile communication network side, compare the current userllabel with the userllabel of the mobile phone number registered in the binding relationship, see whether the current userllabel is consistent, and execute the step 51 and the step 52 only if the current userllabel is consistent.

Referring to fig. 7, it is a flowchart of a second verification code issuing control method according to the present invention, and the flowchart includes the following steps:

And step 61, the server acquires the current UserLabel of the mobile phone number in the corresponding binding relation record.

Based on the step 105B or the step 105C, the destination userllabel of the short message is set to a special value 1, so as to trigger a corresponding exception handling process, and through the exception handling process, the current userllabel of the destination number of the short message can be acquired. For example, the server sends a short message according to the mobile phone number and the special UserLabel value 1 in the corresponding binding relationship record, and receives the current UserLabel of the mobile phone number returned by the SMSC.

Step 62, the server compares the current UserLabel with the UserLabel in the binding relationship record, and if the current UserLabel is consistent with the UserLabel in the binding relationship record, the server executes step 63; otherwise, the flow ends.

Step 63, the server generates the verification code.

and step 64, the server sends the generated verification code according to the mobile phone number and the UserLabel in the corresponding binding relation record.

The invention also provides a method for establishing the binding relationship between the mobile phone number and the corresponding internet account, which comprises the following steps:

Based on the step 105B or the step 105C, the server can obtain the current userllabel of the corresponding mobile phone number from the mobile communication network side (including the SMSC) by using a special short message sending mechanism.

When the binding relationship is established, the server directly obtains the UserLabel of the current mobile phone number to be bound from the mobile communication network side. As described above, when the SMSC sends a route query request to the corresponding HLR according to the destination number of the short message and the special userllabel value 1, the SMSC returns the current userllabel of the destination number of the corresponding short message to the server sending the short message according to the exception report returned by the corresponding HLR.

As shown in fig. 8, a flow chart of an embodiment of a method for establishing a binding relationship is shown, in which the following steps are included:

step 71, the server receives the mobile phone number to be bound.

And 73, the server sends a short message to a corresponding SMSC according to the mobile phone number, and the short message carries a target UserLabel value 1.

and 77, the server receives the current UserLabel of the mobile phone number replied by the SMSC.

And 79, the server establishes a corresponding relation between the corresponding internet account number and the mobile phone number and the current UserLabel. For example, the server stores the mobile phone number and the current userllabel in a binding relationship table shown in table 3 according to the corresponding internet account

The binding relation established according to the binding method provided by the invention is added with the UserLabel of the corresponding mobile phone number.

Generally, when a user establishes a binding relationship, the user logs in a corresponding internet account first, and then performs a binding operation. In this case, the internet account is the internet account that the user is currently logged in to. Of course, the internet account may also be a code-based internet account to be created, which is often the case when a user registers an internet account according to a mobile phone number. In the following embodiments, details of various possible situations of the internet account similar to that in step 79 will not be described.

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 a telephone number, so that when the destination number of the short message and the userllabel carried by the short message are correct and correct, the short message can be smoothly sent to the corresponding mobile phone terminal through the mobile communication network.

Based on the step 105B or the step 105C, the destination userllabel of the short message is set to a special value 1, so as to trigger a corresponding exception handling process, and through the exception handling process, the current userllabel of the destination number of the short message can be acquired.

For example, after step 73, the following sub-flow is executed on the mobile communication network side, and in the sub-flow, 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, compares whether the current UserLabel is consistent with the destination UserLabel carried by the short message, if so, executes step T13, and ends; otherwise, step T14 is executed.

And step T13, sending a roaming number query request to the MSC/VLR where the destination number is currently roaming, namely, requesting a roaming number to the MSCS/VLR where the destination number is currently located, receiving a return message of the MSC/VLR, sending the roaming number to the SMSC, and sending the verification code to the destination number user terminal through a short message by the SMSC through the corresponding MSC/VLR according to the roaming number.

Step T14, judging whether the target UserLabel is 1, if yes, returning the current UserLabel of the target number to the SMSC through an exception report; otherwise, if the destination UserLabel is not 1, returning a reply message indicating that the UserLabel is updated to the SMSC through an exception report.

The step T14 can also be directly: and returning the current UserLabel of the destination number to the SMSC through an exception report.

after step T14, the SMSC may forward the exception report to the server.

For the case that the internet account is a code-based internet account to be created, the step 79 is further a sub-process comprising steps 7905 to 7909 as follows:

Step 7905: the server judges whether a code-based internet account corresponding to the mobile phone number exists or not, if so, step 7906 is executed, otherwise, step 7908 is executed.

The step 7906 is: comparing whether the UserLabel of the code-based Internet account is consistent with the current UserLabel, if so, ending the process, otherwise, executing the step 7907: the code based internet account is frozen and then go to step 7908.

step 7908 is: and creating a code-based internet account according to the mobile phone number.

Step 7909: and establishing a corresponding relation between the created code-based Internet account and the current UserLabel.

In the step 7906, if the userlame of the code-based internet account is consistent with the current userlame of the mobile phone number, it indicates that the code-based internet account corresponding to the mobile phone number is created by the current user of the mobile phone number, and therefore, an exception handling procedure is executed: end directly, or prompt the user to: "there is already a corresponding code-based internet account, please log in directly".

In the step 7906, if the comparison result is not consistent, it indicates that the code-based internet account corresponding to the mobile phone number is created by an old user before the mobile phone number. In order to prevent the new user of the mobile phone number from entering the code-based internet account of the corresponding old user without affecting the new user of the mobile phone number to create the own code-based internet account, the code-based internet account of the old user is frozen, and step 7908 is performed: and creating a code-based internet account belonging to the new user of the mobile phone number.

It should be noted that, in step 7907, the freezing of the old code-based internet account may be a log-out or a deletion of the old code-based internet account.

The internet operator may consider providing a mechanism for the corresponding old user to log in the old code-based internet account that the old user has frozen or logged out, so that the old user binds the frozen account to the new phone number registered by the old user. For example, the user is required to log in by inputting a mobile phone number + UserLabel + account password; or the user is required to input the mobile phone number + UserLabel + ID card for logging in.

And when an old code-based internet account corresponding to one mobile phone number is frozen or cancelled or deleted and a new code-based internet account of the mobile phone number is created, a user logs in the newly created code-based internet account when logging in the code-based internet account according to the mobile phone number subsequently.

Therefore, the binding method provided by the invention effectively ensures the security of the code-based internet account of the old user of the mobile phone number, and does not influence the new user of the mobile phone number to create the code-based internet account of the new user.

based on the new binding relationship, when a short message needs to be sent according to a mobile phone number, the UserLabel in the binding relationship record can be used as the target UserLabel of the message. The mobile communication network side can execute a UserLabel verification operation: comparing the UserLabel in the binding relation record with the current UserLabel of the mobile phone number, if the UserLabel and the current UserLabel are consistent, the verification is passed, and then the subsequent short message sending process is executed; if the two are not consistent, the corresponding short message is not sent. 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 the short message to the mobile phone number bound to the corresponding account, the mobile phone number is registered and used by the 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.

In order to avoid the user from mistaking the mobile phone number to be bound, a mobile phone number initial verification sub-process is preferably further included before step 79. In this case, the server performs step 79 only when the first pass is passed. And when the server fails in the initial check, the process is ended.

As shown in fig. 10, a flow chart of an embodiment of a method for establishing a binding relationship is shown, in which the initial sub-flow includes the following steps:

Step V31, the server generates a verification code.

And V32, the server sends the generated verification code through a short message according to the mobile phone number, wherein the short message carries a target UserLabel value as the current UserLabel of the received mobile phone number.

V33, the server receives the verification code returned from the client, compares the verification code with the generated verification code, and if the verification code is consistent with the generated verification code, the server passes the initial verification; if the two are not consistent, the initial test fails.

And after the mobile terminal receives the verification code, the corresponding user can input the verification code into the corresponding account client. And after acquiring the verification code input by the user, the client sends the verification code to the server side. After receiving the verification code, the server compares the verification code with the previously generated verification code, and if the verification code is consistent with the previously generated verification code, the server performs a binding operation by passing the first verification, for example, the server performs step 79: the server establishes a corresponding relation between the corresponding internet account, the mobile phone number and the current UserLabel; for example, according to the corresponding internet account, the mobile phone number and the current userllabel are saved in the binding relationship table shown in table 3. If the two are not consistent, the initial test fails, and the binding operation is abandoned.

for example, after step V32, the following sub-flow is executed on the mobile communication network side, in which the following steps are included:

And step T21, after the corresponding SMSC receives the short message, sending a route query message carrying a destination UserLabel to the corresponding HLR according to the destination number of the short message.

Step T22, after receiving the route inquiry message, the HLR acquires the current UserLabel of the destination number, compares whether the current UserLabel is consistent with the destination UserLabel carried by the short message, if so, executes step T23, and ends; otherwise, step T24 is executed.

and step T23, sending a roaming number query request to the MSC/VLR where the destination number is currently roaming, namely, requesting a roaming number to the MSCS/VLR where the destination number is currently located, receiving a return message of the MSC/VLR, sending the roaming number to the SMSC, and sending the verification code to the destination number user terminal through a short message by the SMSC through the corresponding MSC/VLR according to the roaming number.

Step T24, judging whether the target UserLabel is 1, if yes, returning the current UserLabel of the target number to the SMSC through an exception report; otherwise, if the destination UserLabel is not 1, returning a reply message indicating that the UserLabel is updated to the SMSC through an exception report.

The step T24 can also be directly: and returning the current UserLabel of the destination number to the SMSC through an exception report.

After step T24, the SMSC may forward the exception report to the server.

Based on the step 105D, when querying the user label of a mobile phone number, a short message can also be sent to the terminal of the mobile phone number. When the binding relationship is established, the server directly obtains the UserLabel of the current mobile phone number to be bound from the mobile communication network side. The server acquires the current UserLabel of the corresponding mobile phone number from the mobile communication network side by using a mechanism of sending the special short message, and sends the generated verification code to the terminal of the corresponding mobile phone number. Thus, according to the abnormal report returned by the corresponding HLR, the SMSC returns the current UserLabel of the destination number of the corresponding short message to the server sending the short message.

As shown in fig. 11, a flowchart of an embodiment of a method for establishing a binding relationship is further shown, in which before step 73, step 72 is further included: the server generates a verification code. Accordingly, in step 73, the generated verification code is also carried in the short message. In step 77, the server also receives the verification code returned from the client, and accordingly, before step 79, the server also includes step 78: comparing the received verification code with the generated verification code, and if the received verification code and the generated verification code are not consistent, ending the process; if they are the same, step 79 is executed.

For example, the step 73 is further a step 73B: and the server sends a short message to a corresponding SMSC according to the mobile phone number, wherein the short message carries the generated verification code and the target UserLabel value 1.

Said step 77 is further a step 77B: the server receives the current UserLabel of the mobile phone number returned by the SMSC; and receiving the verification code returned from the client.

based on the step 105D, the purpose userllabel of the short message is set to a special value 1, so as to trigger a corresponding exception handling process, and through the exception handling process, the purpose of sending the short message to the corresponding mobile phone terminal can be achieved while obtaining the current userllabel of the destination number of the short message. Thereby improving the service operation efficiency.

And step T31, after the corresponding SMSC receives the short message, sending a route query message carrying a destination UserLabel to the corresponding HLR according to the destination number of the short message.

step T32, after receiving the route inquiry message, the HLR acquires the current UserLabel of the destination number, compares whether the current UserLabel is consistent with the destination UserLabel carried by the short message, if so, executes step T33, and ends; otherwise, step T34 is executed.

And step T33, sending a roaming number query request to the MSC/VLR where the destination number is currently roaming, namely, requesting a roaming number to the MSCS/VLR where the destination number is currently located, receiving a return message of the MSC/VLR, sending the roaming number to the SMSC, and sending the verification code to the destination number user terminal through a short message by the SMSC through the corresponding MSC/VLR according to the roaming number.

Step T34, judging whether the target UserLabel is 1, if yes, returning the current UserLabel of the target number to the SMSC through an exception report, and then turning to step T33; otherwise, if the destination UserLabel is not 1, returning a reply message indicating that the UserLabel is updated to the SMSC through an exception report.

After step T34, the SMSC may forward the exception report to the server.

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 acquiring the verification code of the internet account bound by the previous old user according to the mobile phone number through the registered 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 one by one aiming at 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 an internet server sends a short message to a corresponding SMSC, the SMSC sends a routing query message to a corresponding HLR, and the SMSC returns a userlail with a current destination number to the internet server, etc., the userlail can be carried by using the idle cell or the extended cell, or by adding a cell.

Particularly, when the internet server sends the short message to the corresponding SMSC, the target userllabel can be carried by the content part of the short message.

If the user only knows the destination number and does not know the corresponding userllabel when sending the short message (for example, the user only obtains the mobile phone number from a business card, but does not know the userllabel of the mobile phone number), the user can first obtain the current userllabel of the destination number.

For example, the user sends a userllabel query message to an HLR to which a destination number belongs, the message carries the destination number, the HLR receives the query message, queries corresponding subscription data according to the destination number, acquires the current userllabel of the destination number, and returns a query result to the user, wherein the result carries the current userllabel. And after receiving the query result, the user stores the current UserLabel in an address book according to the destination number.

According to the method provided by the foregoing, the mobile phone user sending the userllabel query message to the HLR can be realized by sending a short message: for example, a short message is sent to the SMSC, carrying the destination userllabel value of 1. After receiving the short message from the user, the SMSC sends a routing query message to the corresponding HLR, wherein the message carries a destination UserLabel value 1, so that an HLR exception processing flow is triggered, the current UserLabel value of the corresponding destination number is queried from the HLR, and a query result is replied to the mobile phone of the user.

After the current userllabel value of a number is obtained, when a message is sent according to the destination number in the following, the userllabel can be carried in the message as the destination userllabel of the 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 convenience of description, the SMSC is considered to be part of the mobile communication network. (in practice, SMSC is often treated as a device outside of the mobile communication 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

1. A mobile communication control method is characterized in that a current UserLabel is correspondingly stored in an HLR according to a mobile phone number, and for a route inquiry message which carries a target UserLabel and is received by the HLR, the method comprises the following steps:

a. Acquiring a current UserLabel of a destination number of a message;

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. The method according to claim 1 or 2, wherein said step d is further: and returning the current UserLabel of the destination number to the requester.

4. The method according to claim 1 or 2, wherein said step d is further: and judging whether the destination UserLabel is a special value, and if so, returning the current UserLabel of the destination number to the requester.

5. The method according to claim 1 or 2, wherein said step d is further: and c, judging whether the destination UserLabel is a special value, if so, returning the current UserLabel of the destination number to the requester, and turning to the step c.

6. The method according to claim 1 or 2, wherein said step d is further: and c, judging whether the target UserLabel is a compatible value, and if so, turning to the step c.

7. A binding method, is used for binding a mobile phone number to an Internet account; the method is characterized by comprising the following steps:

a. receiving a mobile phone number;

8. The method of claim 7, wherein the internet account is further a code-based internet account to be created;

f. Creating a code-based internet account according to the mobile phone number;

9. The method according to claim 7 or 8, wherein step g is preceded by step c: generating a verification code, sending the verification code according to the mobile phone number, and taking the current UserLabel as a target UserLabel in a message; and g, receiving the returned verification code, judging whether the received verification code is consistent with the generated verification code, and executing the step g if the received verification code is consistent with the generated verification code.

10. The method according to claim 7 or 8, wherein step b is further: generating a verification code, sending the generated verification code to a corresponding SMSC through a short message according to the mobile phone number, and carrying a special UserLabel value in the message as a target UserLabel; receiving the current UserLabel of the mobile phone number replied by the SMSC; receiving a returned verification code; and g, judging whether the received verification code is consistent with the generated verification code, and executing the step g if the received verification code is consistent with the generated verification code.