CN100394828C - How to automatically log in to business - Google Patents

Abstract

The present invention relates to a method for automatic login service, comprising: a user starts a terminal client; the terminal client prefills the login identifier; the terminal client judges whether to bind the user's identifier in the mobile network with the The login ID, if bound, the terminal client binds the user's ID in the mobile network with the login ID, and the network side authenticates the user according to the login ID and the login password; Login is complete. The present invention binds the user's identification in the mobile network with the login identification during the process of the user's login service; by adopting the present invention, the user can directly log in to the service without manually inputting the login identification in the future, which simplifies the process of logging into the service and shortens the It shortens the time for the user to log in to the service, and enhances the security of the traffic fee generated by the user due to the use of the service, improves the service experience of the user, and greatly increases the attractiveness of the communication service.

Description

How to automatically log in to business

technical field

The present invention relates to a method for automatically logging in to a service, in particular to a terminal client that can automatically fill in a login ID, and when logging in to a service, the terminal client or the network side realizes the user's ID in the mobile network (such as MSI SDN) and the login identifier are bound to enable the user to directly log in to the automatic login service using the service.

Background technique

With the rapid development of mobile communication technology, the mobile network gradually provides a variety of services for mobile terminal users. At present, many value-added services require users to register for the service before logging in to use the service. In the prior art, the method for a user to register and use a certain service is as follows: the user first applies for opening the service through SMS, WAP, business hall or customer service call, etc., and the service operator assigns the user a login account for the service when opening the service. user name and login password, each time the user logs in to use the service, he needs to manually enter the user name and login password assigned by the service operator on the terminal, and only when the user name and login password entered by the user are correct. You can log in to use this service.

The above-mentioned way for the user to enter the user name and login password to log in to the business is manual input, which brings great inconvenience to the user, and in this way the process of the user's business login is very cumbersome and lengthy, and consumes a lot of time and energy for the user , It has brought extremely bad business experience to some users, and it is not conducive to the promotion of business.

Contents of the invention

The purpose of the present invention is to provide a method for automatically logging in to the service in view of the defects and insufficiencies of the method for the user to log in to the service in the manual mode in the prior art. When the user logs in to use the service, the terminal client automatically prefills the Login ID, and bind the user's ID in the mobile network with the login ID used when the user logs in, so that the user does not need to manually enter the login ID in the process of logging in to the service in the future, and solves the traffic charges caused by the user's use of the service aspects of security issues.

In order to achieve the above object, the present invention adopts a method for automatic login service, the method includes realizing the binding of the identification of the user in the mobile network and the login identification by the terminal client and realizing the identification of the user in the mobile network by the network side Two methods of automatically logging in to the business that are bound to the login ID.

A method for realizing an automatic login service in which a user's identification in a mobile network is bound to a login identification by a terminal client includes the following steps:

Step 11. The user starts the terminal client for logging in to the business;

Step 12. The terminal client prefills a login ID;

Step 13. The terminal client judges whether to bind the user's identity in the mobile network with the login identity, if bound, execute step 14; otherwise, skip to execute step 15;

Step 14. The terminal client binds the user's identity in the mobile network with the login identity, and jumps to step 16;

Step 15. The user uses the login ID or enters a new login ID;

Step 16. The user inputs the login password set when registering the service, or the terminal client invokes the login password saved when the user successfully logged in to the service last time;

Step 17. The user sends login request information to the network side, and the login request information includes the login ID or the new login ID pre-filled by the client;

Step 18. The network side authenticates the user according to the login ID pre-filled by the client or the new login ID and the login password;

Step 19. Login is complete.

In the above technical solution, the following steps are further arranged between the step 11 and the step 12:

Step 111. The terminal client queries whether there is a corresponding relationship between the current user card identifier and the user's identifier in the mobile network and the login identifier in the login history list. If not, perform step 112; otherwise, skip to Execute step 12;

Step 112. The network side returns a user login identifier to the terminal client.

In the step 112, the network side registers the service for the user and assigns a login ID, and its operation includes the following steps:

Step 1121. The terminal client sends information to the network side, reporting the identity of the user in the mobile network;

Step 1122. The network side judges whether the user's identity in the mobile network has registered the service, if not, execute step 1123; otherwise, skip to execute step 1130;

Step 1123. The network side sends registration information prompting to register the service to the terminal client;

Step 1124. The terminal client prompts the user to set the login password of the service according to the registration information;

Step 1125. The user enters the login password;

Step 1126. The terminal client registers the service with the network side;

Step 1127. The network side registers the service for the user;

Step 1128. The network side sends information including the mobile network identification and login identification of the user to the terminal client;

Step 1129. The terminal client records the user's identifier in the mobile network and the login identifier sent by the network side;

Step 1130. Exit the registration process. The operation of authenticating the user in the step 18 specifically performs the following steps:

Step 181. The network side judges whether the login ID pre-filled by the client or the new login ID and the login password are correct, and if correct, execute step 182; otherwise, skip to step 183;

Step 182. The network side sends login success information to the terminal client;

Step 183. The network side sends login failure information to the user.

The following steps are arranged between the step 182 and the step 183:

Step 1821. The terminal client records the user card ID used by the user to log in to the service, the user's ID in the mobile network, the login ID or the new login ID pre-filled by the client, and saves it in Login history list.

Between the step 182 and the step 183, there is also an operation of the terminal client saving the login password in the login history list.

The method for realizing the automatic login service in which the user's identification in the mobile network is bound with the login identification by the network side includes the following steps:

Step 21. The user starts the terminal client for logging in to the service;

Step 22. The terminal client pre-fills a login ID;

Step 23. The user inputs the login password set when registering the service, or the login password saved when the terminal client calls the service when the last login was successful;

Step 24. The user sends login request information to the network side, and the login request information includes the user's identification in the mobile network and the login identification;

Step 25. The network side judges whether to bind the identity of the user in the mobile network and the login identity, if bound, execute step 26; otherwise, skip to execute step 27;

Step 26. The network side judges whether the identification of the user in the mobile network corresponds to the login identification, and if so, proceed to step 27; otherwise, skip to step 29;

Step 27. The network side judges whether the login ID and the login password are correct, and if correct, execute step 28; otherwise, skip to execute step 29;

Step 28. The network side sends login success information to the terminal client, and jumps to step 210;

Step 29. The network side sends login failure information to the terminal client;

Step 210. Login ends.

In the technical solution for realizing the automatic login service in which the user's identification in the mobile network is bound to the login identification on the network side, the following steps are further arranged between the step 21 and the step 22:

Step 211. The terminal client queries whether there is a corresponding relationship between the current user card ID and the user's ID in the mobile network and the login ID in the login history list, if not, execute step 212; otherwise, skip Execute step 22;

Step 212. The network side returns a user login identifier to the terminal client.

In the step 212, the network side registers the service for the user and assigns a login ID, and its operation includes the following steps:

Step 2121. The terminal client sends information to the network side, reporting the identity of the user in the mobile network;

Step 2122. The network side judges whether the user's identity in the mobile network has registered the service, if not, execute step 2123; otherwise, skip to execute step 2130;

Step 2123. The network side sends registration information prompting to register the service to the terminal client;

Step 2124. The terminal client prompts the user to set the login password of the service according to the registration information;

Step 2125. The user enters the login password;

Step 2126. The terminal client registers the service with the network side;

Step 2127. The network side registers the service for the user;

Step 2128. The network side sends information including the mobile network identification and login identification of the user to the terminal client;

Step 2129. The terminal client records the user's identifier in the mobile network and the login identifier sent by the network side;

Step 2130. Exit the registration process.

Between said step 22 and said step 23, there is also an operation for the user to input a new login ID. At this time, in said step 24, the user sends a login request message to the network side, and the login request message includes the user's An identifier in the mobile network and the new login identifier.

In the step 26, the network side judges through the service server whether the identification of the user in the mobile network corresponds to the login identification.

The following steps are arranged between the step 28 and the step 29:

Step 281. The network side checks whether the user card ID used by the user to log in to the service, the user's ID in the mobile network, and the login ID are saved in the login history list. If not saved, perform step 282. Otherwise, jump to step 210;

Step 282. The terminal client adds an entry in the login history list, and records in the entry the user card identifier used by the user to log in to the service, the user's identifier in the mobile network, and the The above login ID.

Between the step 28 and the step 29, there is also an operation of the terminal client saving the login password in the login history list.

When realizing the technical solution of the present invention, communication is carried out between the terminal and the network side through the mobile communication network; the network side is provided with a service server, a short message access device and a packet data access device, wherein the short message access device is used for Provide short message routing and delivery functions between terminals and service servers, such as short message centers and short message gateways in GSM/3G networks; packet data access equipment is used to provide packet data access functions in mobile communication networks, Complete the packet data access between the terminal and the service server when the user logs in to the service, such as SGSN and GGSN in the GPRS/3G network in GSM; the service server is connected to the short message access device, and the short message access device communicates with the The terminal realizes information exchange, which is mainly used to accept the user's service request, such as service opening, service use, service cancellation, etc., and the network side binds the current user's identification and login identification in the mobile network and realizes it through the service server immediately , the service server is also connected to the packet data access device, and the terminal login and logout are completed through the packet data access device.

In the present invention, when a user logs in to use a service, the terminal client automatically prefills the login ID for the user, and binds and saves the mobile station MSISDN and the login ID used when the user logs in, so that the user can log in to the service later. You can directly log in to the service without manually entering the login ID during the process, which simplifies the service registration process, shortens the time for users to log in to the service, and enhances the security of the user's traffic charges caused by using the service, and improves the user's service life. experience, which greatly increases the attractiveness of communication services.

It will be further described below in conjunction with specific embodiments of the present invention and accompanying drawings.

Description of drawings

Fig. 1 is the system structural representation realizing the present invention;

Fig. 2 is the flow chart of an embodiment of the terminal client automatic login service method in which the terminal client binds the MSISDN and the login identifier in the present invention;

Fig. 3 is a flow chart of an embodiment of the method for automatically logging in a terminal client by binding an MSISDN and a login ID on the network side according to the present invention.

Detailed ways

Referring to Fig. 1, Fig. 1 shows a schematic structural diagram of a specific system for realizing the present invention, the system includes a user terminal 1, a short message access device 2, a service server 3 and a packet data access device 4, wherein the terminal 1 is provided with There is a terminal client 10, and the terminal client 10 is provided with a login history list 101 for recording information related to user login services.

Referring to Fig. 2, Fig. 2 shows a specific process of the terminal client automatic login service of the terminal client binding MSISDN and login identification in the present invention, and performs the following steps:

Step 201. The user starts the terminal client 10 for logging in to the service;

Step 202. The terminal client 10 pre-fills a login ID;

Step 203. The terminal client 10 judges whether to bind the current MSISDN and the login ID, if bound, execute step 204; otherwise, skip to execute step 205;

Step 204. The terminal client 10 binds the current MSISDN and the login ID, the login ID pre-filled by the terminal client 10 cannot be changed in the future, and jumps to step 206;

Step 205. The user adopts the login ID pre-filled by the terminal client 10 or enters a new login ID;

Step 206. The user inputs the login password set when registering the service, or the terminal client 10 invokes the login password saved when the user successfully logged in to the service last time;

Step 207. The terminal client 10 sends a request message for logging in to the service server 3 through the packet data access device 4, and the log-in request message includes the login ID pre-filled by the terminal client 10 or a new login ID;

Step 208. The service server 3 judges whether the login ID and login password used by the user to log in to the service are correct, and if correct, execute step 209; otherwise, skip to execute step 210;

Step 209. The business server 3 sends login success information to the terminal client 10 through the packet data access device 4, and then jumps to step 211;

Step 210. The service server 3 sends login failure information to the terminal client 10 through the packet data access device 4;

Step 211. Login ends.

Wherein, between step 201 and step 202, there are also:

Step 20101. The terminal client 10 sends a "+TCMS" short message to the short message access device 2, and reports the current MSISDN of the terminal;

Step 20102. The short message access device 2 forwards the MSISDN to the service server 3;

Step 20103. The service server 3 judges whether the MSISDN has registered a service, if not, execute step 20104; otherwise, skip to execute step 20114;

Step 20104. The service server 3 sends information including the current MSISDN of the terminal to the short message access device 2, prompting the terminal to register the service;

Step 20105. The short message access device 2 forwards to the terminal client 10 the prompt information prompting the terminal to register the service;

Step 20106. The terminal client 10 prompts the user to input the login password of the service;

Step 20107. The user enters the login password;

Step 20108. The terminal client 10 sends the message "+TCKT password" to the short message access device 2 to apply for registration of the service;

Step 20109. The short message access device 2 forwards the "+TCKT password" information to the service server 3;

Step 20110. The service server 3 registers the service for the user;

Step 20111. The service server 3 sends information including the user's current MSISDN and login ID to the short message access device 2;

Step 20112. The short message access device 2 forwards the information including the user's current MSISDN and login ID to the terminal client 10;

Step 20113. The terminal client 10 records the MSISDN and login ID.

Step 20114. Exit the registration process.

In addition, between step 209 and step 210, there are also:

Step 2091. The terminal client 10 records the user card ID, MSISDN and login ID used by the user to log in to the service, and saves it in the login history list;

Step 2092. The terminal client 10 records the login password used by the user to log in to the service and saves it in the login history list.

Referring to Fig. 3, Fig. 3 shows that the present invention binds a specific process of the terminal client 10 automatic login service of MSISDN and login identification by service server 3, and performs the following steps:

Step 301. The user starts the terminal client 10;

Step 302. The terminal client 10 pre-fills the login ID. If the user does not agree to use the login ID, go to step 303; otherwise, go to step 304;

Step 303. The user inputs a new login ID;

Step 304. The user inputs the login password, or the terminal client 10 invokes the login password saved when the user successfully logged in to the service last time;

Step 305. The terminal client 10 sends a request message for logging in to the service server 3 through the packet data access device 4, and the log-in request message includes the current MSISDN and the log-in ID;

Step 306. The service server 3 judges whether to bind the current MSISDN and the login ID, if bound, execute step 307; otherwise, skip to execute step 308;

Step 307. The service server 3 judges whether the current MSISDN corresponds to the login ID, and if so, executes step 308; otherwise, skips to execute step 310;

Step 308. The network side judges whether the login ID and the login password are correct, and if they are correct, execute step 309; otherwise, skip to execute step 310;

Step 309. The service server 3 sends login success information to the terminal client 10 through the packet data access device 4, and then jumps to step 311;

Step 310. The service server 3 sends login failure information to the terminal client 10 through the packet data access device 4;

Step 311. Login ends.

Wherein, the following steps are also arranged between step 301 and step 302:

Step 30101. The terminal client 10 sends a "+TCMS" short message to the short message access device 2, and reports the current MSISDN of the terminal;

Step 30102. The short message access device 2 forwards the MSISDN to the service server 3;

Step 30103. The service server 3 judges whether the MSISDN has registered a service, if not, execute step 30104; otherwise, skip to execute step 30114;

Step 30104. The service server 3 sends information including the current MSISDN of the terminal to the short message access device 2, prompting the terminal to register the service;

Step 30105. The short message access device 2 forwards the information prompting the terminal to register the service to the terminal client 10;

Step 30106. The terminal client 10 prompts the user to input the login password of the service;

Step 30107. The user enters the login password;

Step 30108. The terminal client 10 sends "+TCKT password" information to the short message access device 2, and applies for registration of the service;

Step 30109. The short message access device 2 forwards the "+TCKT password" information to the service server 3;

Step 30110. The service server 3 registers the service for the user;

Step 30111. The service server 3 sends information including the user's current MSISDN and login ID to the short message access device 2;

Step 30112. The short message access device 2 forwards the information including the user's current MS ISDN and login ID to the terminal client 10;

Step 30113. The terminal client 10 records the MSISDN and login ID.

Step 30114. Exit the registration process.

In addition, the following steps are also arranged between step 309 and step 310:

Step 3091. The network side checks whether the user card ID, MSISDN and login ID used by the user to log in to the service are saved in the login history list, if not saved, go to step 3092, otherwise, go to step 311;

Step 3092. The terminal client 10 adds an entry in the login history list, and records the user card identifier, MSISDN and login identifier used by the user when logging in to the service in the entry.

Between step 310 and step 311, the terminal client 10 saves the login password input by the user in the login history list.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them; although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that: Modifications to the specific implementation of the present invention or equivalent replacement of some technical features; without departing from the spirit of the technical solution of the present invention, should be included in the scope of the technical solution claimed in the present invention.

Claims (13)

1. realize the sign of user in the mobile network and the method for the automatically registering service of login banner binding by client terminals for one kind, wherein, carry out following steps:

Step 11. user starts client terminals, is used for registering service;

The described client terminals of step 12. is filled out a login banner in advance;

The described client terminals of step 13. judges whether sign and the described login banner of described user in the mobile network bound, if binding, execution in step 14; Otherwise, redirect execution in step 15;

The described client terminals of step 14. is bound redirect execution in step 16 to the sign and the described login banner of described user in the mobile network;

Step 15. user uses described login banner or imports new login banner;

Step 16. user imports the described login password of setting when professional of registration, or the described login password of being preserved when professional of described client terminals invoke user last login success;

Step 17. user sends landing request information to network side, comprises described login banner or described new login banner that client is filled out in advance in the described landing request information;

Described login banner that the described network side of step 18. is filled out in advance according to client or described new login banner and described login password carry out authentication to the user;

Step 19. login finishes.

2. the method for automatically registering service according to claim 1 wherein, also is provided with following steps between described step 11 and the step 12:

Whether exist in the tabulation of the described client terminals of step 111. inquiry log in history the active user block sign and described user in the mobile network sign and the corresponding relation between the login banner, as if there not being execution in step 112; Otherwise, redirect execution in step 12;

Step 112. network side returns user's login banner to described client terminals.

3. the method for automatically registering service according to claim 2, wherein, the concrete following steps of carrying out of described step 112:

The described client terminals of step 1121. sends information to network side, reports the sign of described user in the mobile network;

The described network side of step 1122. judges whether the sign of described user in the mobile network has registered described business, if unregistered, execution in step 1123; Otherwise, redirect execution in step 1130;

The described network side of step 1123. sends the log-on message of the described business of prompting registration to described client terminals;

The described client terminals of step 1124. is according to described log-on message, and the prompting user sets the login password of described business;

Step 1125. user imports login password;

The described client terminals of step 1126. is registered described business to described network side;

The described network side of step 1127. is described business for the user registers;

The described network side of step 1128. sends to described client terminals and comprises the sign of described user in the mobile network and the information of login banner;

The described client terminals of step 1129. writes down the sign of described user in the mobile network and the described login banner of network side transmission;

Step 1130. withdraws from register flow path.

4. the method for automatically registering service according to claim 1, wherein, following steps are specifically carried out in the operation that the user is carried out authentication in the described step 18:

The described network side of step 181. judges whether described login banner that client is filled out in advance or described new login banner and described login password be correct, if correct, execution in step 182; Otherwise, redirect execution in step 183;

The described network side of step 182. sends login successful information, redirect execution in step 19 to described client terminals;

The described network side of step 183. sends login failure information to described client terminals.

5. the method for automatically registering service according to claim 4 wherein, is provided with following steps between described step 182 and the step 183:

The described subscriber card sign of using when professional of the described client terminals recording user of step 1821. login, described user sign and client described login banner or the described new login banner filled out in advance in the mobile network, and be kept in the log in history tabulation.

6. the method for automatically registering service according to claim 4 wherein, also is provided with described client terminals described login password is kept at operation in the log in history tabulation between described step 182 and the step 183.

7. realize the sign of user in the mobile network and the method for the automatically registering service of login banner binding by network side for one kind, wherein, carry out following steps:

Step 21. user starts client terminals, is used for registering service;

The described client terminals of step 22. is filled out a login banner in advance;

Step 23. user imports the described login password of setting when professional of registration, or described client terminals calls the described login password of being preserved when professional of last login success;

Step 24. user sends landing request information to network side, comprises sign and the described login banner of described user in the mobile network in this landing request information;

The described network side of step 25. judges whether sign and the described login banner of described user in the mobile network bound, if binding, execution in step 26; Otherwise, redirect execution in step 27;

The described network side of step 26. judges whether the sign of described user in the mobile network be corresponding with described login banner, if corresponding, execution in step 27; Otherwise, redirect execution in step 29;

The described network side of step 27. judges whether described login banner and described login password be correct, if correct, execution in step 28; Otherwise, redirect execution in step 29;

The described network side of step 28. sends login successful information, redirect execution in step 210 to client terminals;

The described network side of step 29. sends login failure information to client terminals;

Step 210. login finishes.

8. the method for automatically registering service according to claim 7 wherein, also is provided with following steps between described step 21 and the step 22:

Whether exist in the tabulation of the described client terminals of step 211. inquiry log in history the active user block sign and described user in the mobile network sign and the corresponding relation between the login banner, as if there not being execution in step 212; Otherwise, redirect execution in step 22;

Step 212. network side returns user's login banner to described client terminals.

9. the method for automatically registering service according to claim 8, wherein, the concrete following steps of carrying out of described step 212:

The described client terminals of step 2121. sends information to network side, reports the sign of described user in the mobile network;

The described network side of step 2122. judges whether the sign of described user in the mobile network has registered described business, if unregistered, execution in step 2123; Otherwise, redirect execution in step 2130;

The described network side of step 2123. sends the log-on message of the described business of prompting registration to described client terminals;

The described client terminals of step 2124. is according to described log-on message, and the prompting user sets the login password of described business;

Step 2125. user imports login password;

The described client terminals of step 2126. is registered described business to described network side;

The described network side of step 2127. is described business for the user registers;

The described network side of step 2128. sends to described client terminals and comprises the sign of described user in the mobile network and the information of login banner;

The described client terminals of step 2129. writes down the sign of described user in the mobile network and the described login banner of network side transmission;

Step 2130. withdraws from register flow path.

10. the method for automatically registering service according to claim 7, wherein, also be provided with the operation that the user imports a new login banner between described step 22 and the described step 23, in the described step 24 when the user when network side sends landing request information, comprise sign and the described new login banner of described user in the mobile network in this landing request information.

11. the method for automatically registering service according to claim 7, wherein, whether network side described in the described step 26 is corresponding with described login banner by the sign of the described user of service server judging in the mobile network.

12. the method for automatically registering service according to claim 7 wherein, is provided with following steps between described step 28 and the step 29:

The described network side of step 281. checks that the user logins the described subscriber card sign of using when professional and described user sign and the described login banner in the mobile network and whether is kept at during described log in history tabulates, if do not preserve, execution in step 282, otherwise, redirect execution in step 210;

The described client terminals of step 282. is newly-increased clauses and subclauses in log in history tabulation, described described subscriber card sign and sign and the described login banner of described user in the mobile network that uses when professional of recording user login in these clauses and subclauses.

13. the method for automatically registering service according to claim 7 wherein, also is provided with described client terminals described login password is kept at operation in the log in history tabulation between described step 28 and the step 29.

Images