Web System and Member Site Login Method

Abstract

Enable safe and easy membership registration when logging in to the membership site. 【Solution】In the Web system 100, the Web server 10 has the functions of obtaining the phone number of the user terminal 30 as the minimum necessary information for membership registration and passing it to the backend 20, and obtaining an authentication code from the browser of the user terminal 30 and passing it to the backend 20. When a login to the membership site is requested, the backend 20 has the function of sending an authentication code to the phone number received from the Web server 10 when there is no phone number in the customer profile associated with the cookie, the function of adding the phone number received from the Web server 10 to the customer profile associated with the cookie when the authentication code received from the Web server 10 is correct, and the function of approving the login to the membership site when there is a phone number in the customer profile associated with the cookie or when the authentication code received from the Web server 10 is correct.

Description

Technical Field

[0001] The present invention relates to a Web system composed of a Web server and a backend, and particularly to a method for logging in to a member site provided in the Web system.

Background Art

[0002] Companies are opening their own Web sites and conducting various marketing activities. Consumers (users) can access the Web sites of companies they are interested in and freely obtain the necessary information. However, some companies may provide member sites where information cannot be obtained without member registration. By providing such member sites, companies can effectively obtain consumers' personal information and acquire potential customers (leads), and can utilize the obtained personal information in subsequent marketing activities.

[0003] Generally, to log in to a member site, a user ID and a password are entered. Therefore, at least a user ID and a password need to be registered for new member registration. To enhance security further, after the first authentication using the user ID and password, a second authentication may be performed where a one-time password is notified from the server to the user terminal and entered, and only then is the login to the member site approved (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When trying to log in to a membership site for the first time, it is a bit cumbersome for users to register both a user ID and a password. Therefore, if users dislike this cumbersome process and do not register as members, the company will miss out on potential customers. On the other hand, if the password is omitted and only the user ID is used, the security of the membership site will be greatly reduced.

[0006] Therefore, an object of the present invention is to enable secure and easy membership registration when logging in to a membership site in a Web system.

Means for Solving the Problem

[0007] A Web system according to an aspect of the present invention is a Web system including a Web server that provides a website and cookies to a browser of a user terminal, and a backend that manages customer profiles. The Web server has functions of acquiring cookies and Web transactions from the browser of the user terminal and passing them to the backend, issuing new cookies and passing them to the browser of the user terminal and the backend when the browser of the user terminal does not store cookies or the expiration date of the cookies acquired from the browser of the user terminal has expired, acquiring the telephone number of the user terminal as the minimum necessary information for member registration for logging in to the member site and passing it to the backend, acquiring an authentication code from the browser of the user terminal and passing it to the backend, and providing the member site to the browser of the user terminal when the login to the member site is approved by the backend. And the backend has functions of searching for a customer profile associated with the cookies received from the Web server, creating a new customer profile by associating the cookies and Web transactions received from the Web server when there is no customer profile associated with the cookies, sending an authentication code to the telephone number received from the Web server when there is no telephone number in the customer profile associated with the cookies when a login to the member site is requested, adding the telephone number received from the Web server to the customer profile associated with the cookies when the authentication code received from the Web server is correct, and approving the login to the member site when there is a telephone number in the customer profile associated with the cookies or when the authentication code received from the Web server is correct when a login to the member site is requested.

[0008] A membership site login method according to an aspect of the present invention is a method for logging in to a membership site in a web system including a web server that provides a website and cookies to a browser of a user terminal and a backend that manages customer profiles. The web server obtains cookies and web transactions from the browser of the user terminal and passes them to the backend. When the browser of the user terminal does not store cookies or the expiration date of the cookies obtained from the browser of the user terminal has expired, new cookies are issued and passed to the browser of the user terminal and the backend. The phone number of the user terminal is obtained as the minimum necessary information for membership registration for logging in to the membership site and passed to the backend. An authentication code is obtained from the browser of the user terminal and passed to the backend. And when the login to the membership site is approved by the backend, the membership site is provided to the browser of the user terminal. Then, the backend searches for a customer profile associated with the cookies received from the web server. When there is no customer profile associated with the cookies, a customer profile is newly created by associating the cookies and web transactions received from the web server. When a login to the membership site is requested and there is no phone number in the customer profile associated with the cookies, an authentication code is sent to the phone number received from the web server. When the authentication code received from the web server is correct, the phone number received from the web server is added to the customer profile associated with the cookies. And when a login to the membership site is requested and there is a phone number in the customer profile associated with the cookies or the authentication code received from the web server is correct, the login to the membership site is approved.

Advantages of the Invention

[0009] According to the present invention, a user can register as a member to log in to a membership site by simply providing the phone number of the user terminal as the minimum necessary information. Therefore, for the user, membership registration can be done safely and easily, and for the company, it is expected to reduce the omission of potential customers who dislike the complexity of membership registration and improve the effect of lead generation.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Modes for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings as appropriate. However, a more detailed description than necessary may be omitted. For example, a detailed description of well-known matters and a redundant description of substantially the same configuration may be omitted. This is to avoid making the following description unnecessarily redundant and to facilitate the understanding of those skilled in the art. Note that the inventor provides the accompanying drawings and the following description so that those skilled in the art can fully understand the present invention, and does not intend to limit the subject matter described in the claims thereby.

[0012] ≪System Configuration≫ Figure 1 is a schematic configuration diagram of a Web system according to an embodiment of the present invention. The Web system 100 according to this embodiment includes a Web server 10 and a backend 20, which are connected to a network 200. The network 200 is a network that integrates public networks such as the Internet and carrier communication networks, and private networks such as WANs and LANs. User terminals 30 such as personal computers, tablets, and smartphones, and various external services and servers, such as various SNS servers 40 and mail servers 50, are also connected to the network 200. The user terminal 30, the SNS server 40, and the mail server 50 can communicate with each other via the network 200.

[0013] The Web server 10 is composed of one or more computer devices having a processor, a memory, a storage, and an interface. The main role of the Web server 10 is to communicate with the browser of the user terminal 30, provide the Web site requested by the user to the browser, and obtain the data input through the browser and pass it to the backend 20.

[0014] The backend 20 includes an application server 21 and a customer database 22. The application server 21 is composed of one or more computer devices having a processor, a memory, a storage, and an interface. The main role of the backend 20 is to manage the customer profiles stored in the customer database 22 and control the login authentication to the membership site.

[0015] The customer database 22 stores customer profiles, which are aggregates of various types of information for each user. For example, the customer profiles include: 1) user terminal information such as the OS type, version, browser type, IP address, and phone number of the user terminal; 2) user personal information such as the user's name, address, email address, age, and gender; 3) web transactions such as the web site visit date and time and the behavior history on the web site; and 4) cookies issued by the web server 10, etc.

[0016] The customer database 22 may be incorporated into the application server 21 or may be located outside the application server 21. In the latter case, the application server 21 exchanges data with the customer database 22 through the API 23. Also, the application server 21 can access the mail server 50 through the API 23 to send short messages to the user terminal 30 or exchange data with the SNS server 40.

[0017] ≪Member Site Login≫ The web site provided by the web server 10 includes a member site that cannot be accessed without member login. When a user attempts to log in to the member site, the web system 100 permits the login to the member site if the user is a registered member, i.e., there is a customer profile in the customer database 22. Even for an unregistered member without a customer profile, if the phone number of the user terminal 30 is provided as the minimum necessary information for member registration, the web system 100 creates a new customer profile and permits the login to the member site.

[0018] FIG. 2 is a diagram showing example screen displays of (a) an authentication form, (b) authentication code input, and (c) authentication success for unregistered members. As phone number acquisition routes of the user terminal 30 when the user first logs in to the membership site, there are three routes: 1) a form input route where the user directly enters the phone number in the form, 2) an SNS login route where the phone number is automatically acquired from an external SNS service, and 3) a message service route where the phone number is acquired through an external message service. The user selects any one of the three routes shown in the authentication form and provides the phone number of the user terminal 30.

[0019] In the case of the form input route or the message service route, the user inputs the authentication code notified to the provided phone number, and upon successful authentication, a customer profile is newly created and the user can log in to the membership site. In the case of the SNS login route, the user can log in to the membership site with a newly created customer profile without code authentication.

[0020] Some SNS services become available by registering the phone number of the user terminal 30. The SNS service used in the SNS login route has a user profile including the phone number of the user terminal 30, and another service can acquire a part of the user profile if certain conditions are met. Since the phone number of the user terminal 30 obtained from such an SNS service can be judged as reliable information, code authentication is omitted in the case of the SNS login route.

[0021] Next, various functions and operations of the web server 10 and the backend 20 when the user first logs in to the membership site through the above three routes will be described.

[0022] [Form Input Route] FIG. 3 is a schematic diagram explaining the flow of the first login to the membership site by form input of the phone number.

[0023] (S11) When the browser of the user terminal 30 requests access to a website of any domain, the web server 10 provides the website in response to the request. At this time, if the browser of the user terminal 30 stores a cookie issued by the web server 10, it sends the cookie to the web server 10. On the other hand, if the browser of the user terminal 30 does not store a cookie or the stored cookie has expired, the web server 10 issues a new cookie and sends it to the browser of the user terminal 30, and the browser of the user terminal 30 stores the cookie sent from the web server 10. In addition, the web server 10 obtains user terminal information such as the OS type, version, browser type, and IP address of the user terminal 30, and web transactions such as the website access date and time and the action history on the website from the browser of the user terminal 30.

[0024] (S12) The web server 10 passes the cookie obtained from or newly issued to the browser of the user terminal 30, and the user terminal information and web transactions obtained from the user terminal 30 to the application server 21 of the backend 20. The application server 21 searches for a customer profile associated with the cookie received from the web server 10 in the customer database 22. Since there is no customer profile associated with the cookie in the customer database 22 because the user is an unregistered member, the application server 21 creates a new customer profile by associating this information with the cookie as a key and registers it in the customer database 22.

[0025] When there is a request to log in to the membership site from the browser of the user terminal 30, the Web server 10 requests login authentication from the application server 21. Upon receiving the login authentication request, the application server 21 searches the customer database 22 for the customer profile associated with the cookie received from the Web server 10. Since the customer profile found at this time does not have the phone number of the user terminal 30 registered, the application server 21 notifies the Web server 10 that the user is not registered as a member.

[0026] (S13) When the Web server 10 is notified by the application server 21 that the user is not registered as a member, it provides an authentication form to the browser of the user terminal 30.

[0027] (S14) In the authentication form displayed on the browser of the user terminal 30, when the user selects the "Authenticate by phone number" radio button, enters the phone number of the user terminal 30 in the text input field, and agrees to the privacy policy, the Web server 10 obtains the phone number entered in the form and passes it to the application server 21.

[0028] (S15) When the application server 21 receives the phone number of the user terminal 30 from the Web server 10, it searches the customer database 22 for the customer profile associated with the phone number. Since no such customer profile is found, the application server 21 generates an authentication code and sends a short message notifying the authentication code to the external mail server 50 for the phone number via the API 23, and also notifies the Web server 10 that the authentication code has been notified.

[0029] (S16) When the Web server 10 is notified by the application server 21 that the authentication code has been notified, it provides an authentication code input screen to the browser of the user terminal 30.

[0030] (S17) On the authentication code input screen, when the user enters the authentication code, the Web server 10 acquires the authentication code and passes it to the application server 21. When the application server 21 confirms that the authentication code received from the Web server 10 is correct, it adds the phone number of the user terminal 30 to the customer profile associated with the cookie and approves the login to the membership site.

[0031] (S18) When the login to the membership site is approved, the Web server 10 provides a screen indicating successful authentication to the browser of the user terminal 30. Thereafter, when a request is made from the browser of the user terminal 30 to access any site or page within the membership site, the Web server 10 provides the requested site or page to the browser of the user terminal 30.

[0032] [SNS Login Route] FIG. 4 is a schematic diagram illustrating the process of the first login to the membership site by obtaining a phone number from an external SNS service.

[0033] (S21) When the browser of the user terminal 30 requests access to a website of any domain, the Web server 10 provides the website in response to the request. At this time, if the browser of the user terminal 30 has saved the cookie issued by the Web server 10, it sends the cookie to the Web server 10. On the other hand, if the browser of the user terminal 30 has not saved the cookie or the saved cookie has expired, the Web server 10 issues a new cookie and sends it to the browser of the user terminal 30, and the browser of the user terminal 30 saves the cookie sent from the Web server 10. In addition, the Web server 10 acquires user terminal information such as the OS type, version, browser type, and IP address of the user terminal 30, and Web transactions such as the website access date and time and the action history on the website, from the browser of the user terminal 30.

[0034] (S22) The Web server 10 passes the cookies obtained from the browser of the user terminal 30 or newly issued, as well as the user terminal information and Web transactions obtained from the user terminal 30, to the application server 21 of the backend 20. The application server 21 searches for a customer profile associated with the cookie received from the Web server 10 in the customer database 22. Since the customer database 22 does not have a customer profile associated with the cookie because the user is an unregistered member, the application server 21 creates a new customer profile by associating this information with the cookie as the key and registers it in the customer database 22.

[0035] When there is a request to log in to the membership site from the browser of the user terminal 30, the Web server 10 requests login authentication from the application server 21. Upon receiving the login authentication request, the application server 21 searches for a customer profile associated with the cookie received from the Web server 10 in the customer database 22. Since the telephone number of the user terminal 30 is not registered in the customer profile found at this time, the application server 21 notifies the Web server 10 that the user is not registered as a member.

[0036] (S23) When the Web server 10 is notified by the application server 21 that the user is not registered as a member, it provides an authentication form to the browser of the user terminal 30.

[0037] (S24) In the authentication form displayed on the browser of the user terminal 30, when the user selects the radio button of "Authenticate with La○n" and taps or clicks the "Log in with La○n" button and agrees to the privacy policy, a La○n login screen is displayed on the browser of the user terminal 30. Note that La○n is an SNS service that has a user profile including the telephone number of the user terminal 30.

[0038] (S25) When the user logs in to Ron on the browser of the user terminal 30, the Web server 10 obtains the phone number of the user terminal 30 from the user profile held by Ron from the SNS server 40 of Ron and passes it to the application server 21.

[0039] (S26) The application server 21 adds the phone number of the user terminal 30 received from the Web server 10 to the customer profile associated with the cookie and approves the login to the membership site.

[0040] When the login to the membership site is approved, the Web server 10 provides a screen of successful authentication to the browser of the user terminal 30. Thereafter, when a request is made from the browser of the user terminal 30 to access any site or page within the membership site, the Web server 10 provides the requested site or page to the browser of the user terminal 30.

[0041] In this way, in the case of the SNS login route, the user can register as a member without code authentication and access the membership site.

[0042] [Message Service Route] Figure 5 is a schematic diagram for explaining the flow of the first login to the membership site by obtaining a phone number through an external message service.

[0043] (S31) When the browser of the user terminal 30 requests access to a website of an arbitrary domain, the web server 10 provides the website in response to the request. At this time, if the browser of the user terminal 30 has stored the cookie issued by the web server 10, it sends the cookie to the web server 10. On the other hand, if the browser of the user terminal 30 does not store the cookie, or if the stored cookie has expired, the web server 10 newly issues a cookie and sends it to the browser of the user terminal 30, and the browser of the user terminal 30 stores the cookie sent from the web server 10. Further, the web server 10 acquires user terminal information such as the OS type, version, browser type, and IP address of the user terminal 30, and web transactions such as the website access date and time and the action history on the website from the browser of the user terminal 30.

[0044] (S32) The web server 10 passes the cookie acquired from or newly issued to the browser of the user terminal 30, and the user terminal information and web transactions acquired from the user terminal 30 to the application server 21 of the backend 20. The application server 21 searches for a customer profile associated with the cookie received from the web server 10 in the customer database 22. Since there is no customer profile associated with the cookie in the customer database 22 because the user is an unregistered member, the application server 21 creates a new customer profile by associating this information with the cookie as a key and registers it in the customer database 22.

[0045] When there is a request from the browser of the user terminal 30 to log in to the membership site, the web server 10 requests the application server 21 for login authentication. The application server 21 receives the login authentication request and searches for a customer profile associated with the cookie received from the web server 10 in the customer database 22. At this time, since the customer profile found does not have the phone number of the user terminal 30 registered, the application server 21 notifies the web server 10 that the membership is not registered.

[0046] (S33) When the web server 10 is informed by the application server 21 that the user is not registered, it provides an authentication form to the browser of the user terminal 30.

[0047] (S34) In the authentication form displayed on the browser of the user terminal 30, when the user selects the radio button of "Authenticate with other SNS" and taps or clicks on the icon of an arbitrary SNS and agrees to the privacy policy, the selected SNS application is launched, and a message is notified to the business account of the website that the user is browsing.

[0048] (S35) When the application server 21 receives the SNS message, it connects to the SNS server 40 via the API 23. As a result, the application server 21 can communicate with the user through the SNS application of the user terminal 30. For example, the application server 21 sends a message asking the user to enter the phone number of the user terminal 30, and the user responds by informing the phone number.

[0049] (S36) When the application server 21 obtains the phone number of the user terminal 30 through message communication, it searches the customer database 22 for the customer profile associated with the phone number. Since no such customer profile is found, the application server 21 notifies the user of the authentication code and also notifies the web server 10 that it has notified the authentication code.

[0050] (S37) When the web server 10 is informed by the application server 21 that the authentication code has been notified, it provides an authentication code input screen to the browser of the user terminal 30.

[0051] (S38) On the authentication code input screen, when the user enters the authentication code, the Web server 10 acquires the authentication code and passes it to the application server 21. When the application server 21 confirms that the authentication code received from the Web server 10 is correct, it adds the phone number of the user terminal 30 to the customer profile associated with the cookie and approves the login to the membership site.

[0052] (S39) When the login to the membership site is approved, the Web server 10 provides a screen indicating successful authentication to the browser of the user terminal 30. Thereafter, when a request is made from the browser of the user terminal 30 to access any site or page within the membership site, the Web server 10 provides the requested site or page to the browser of the user terminal 30.

[0053] [Login for the second time and later] FIG. 6 is a schematic diagram for explaining the process of login for the second time and later to the membership site.

[0054] (S41) When the browser of the user terminal 30 requests access to a website of any domain, the Web server 10 provides the website in response to the request. Since this is the second time and later to access this website, the browser of the user terminal 30 has saved the cookie issued by the Web server 10 and sends the cookie to the Web server 10. If the cookie saved by the browser of the user terminal 30 has expired, the Web server 10 issues a new cookie and sends it to the browser of the user terminal 30, and the browser of the user terminal 30 saves the cookie sent from the Web server 10. In addition, the Web server 10 obtains user terminal information such as the OS type, version, browser type, and IP address of the user terminal 30, and Web transactions such as the website access date and time and the action history on the website from the browser of the user terminal 30.

[0055] (S42) The Web server 10 passes cookies obtained from the browser of the user terminal 30 or newly issued, as well as user terminal information and Web transactions obtained from the user terminal 30, to the application server 21 of the backend 20. The application server 21 searches for a customer profile associated with the cookie received from the Web server 10 in the customer database 22. In the case of a newly issued cookie, since there is no customer profile associated with the cookie in the customer database 22, the application server 21 creates a new customer profile by associating this information using the cookie as a key and registers it in the customer database 22.

[0056] When there is a request to log in to the membership site from the browser of the user terminal 30, the Web server 10 requests login authentication from the application server 21. Upon receiving the login authentication request, the application server 21 searches for a customer profile associated with the cookie received from the Web server 10 in the customer database 22. If the phone number of the user terminal 30 is registered in the found customer profile, the application server 21 notifies the Web server 10 that the membership registration has been completed. On the other hand, if the phone number of the user terminal 30 is not registered in the customer profile, the application server 21 notifies the Web server 10 that the membership has not been registered.

[0057] (S43) When the Web server 10 is notified by the application server 21 that the membership registration has been completed, it provides the membership site to the browser of the user terminal 30. Thereafter, when a request is made to access any site or page within the membership site from the browser of the user terminal 30, the Web server 10 provides the requested site or page to the browser of the user terminal 30.

[0058] (S44) On the other hand, when the Web server 10 is notified by the application server 21 that the membership has not been registered, it provides an authentication form to the browser of the user terminal 30.

[0059] (S45) In the authentication form displayed on the browser of the user terminal 30, the user provides the phone number of the user terminal 30 via any of the form input route, SNS login route, and message service route, and the application server 21 acquires the phone number of the user terminal 30.

[0060] The application server 21 searches the customer database 22 for a customer profile associated with the acquired phone number. If the user has previously registered as a member, the phone number of the user terminal 30 is registered in the customer profile associated with the expired cookie. In this case, the application server 21 updates the cookie associated with the customer profile to the new cookie received from the web server 10 and approves the login to the membership site without sending an authentication code to the user terminal 30.

[0061] When the login to the membership site is approved, the web server 10 provides an authentication form to the browser of the user terminal 30 in the same manner as in step S43. Thereafter, when access from the browser of the user terminal 30 to any site or page within the membership site is requested, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0062] On the other hand, if the user has not registered as a member, the phone number of the user terminal 30 is not registered in the customer profile associated with the expired cookie. In this case, the application server 21, similar to the first login to the membership site, when the phone number of the user terminal 30 is acquired via the form input route or the message service route, sends an authentication code to the user terminal 30, performs code authentication, and then approves the login. When the phone number of the user terminal 30 is acquired via the SNS login route, the login is approved without sending an authentication code to the user terminal 30.

[0063] <<Effect>> According to this embodiment, a user can register as a member to log in to the member site simply by providing the phone number of the user terminal 30 as the minimum necessary information in the case of the form input route or message service route, or by logging in to the SNS in the case of the SNS login route. This allows users to register as a member safely and easily, and companies can expect to improve the effectiveness of lead generation by reducing the loss of potential customers who dislike the hassle of member registration.

[0064] Furthermore, if the user has registered as a member by providing the telephone number of the user terminal 30, code authentication is not required the second time he logs in or thereafter, reducing the hassle of registering as a member again.

[0065] As described above, the embodiments have been described as examples of the technology of the present invention. For this purpose, the accompanying drawings and detailed description have been provided. Therefore, the components described in the accompanying drawings and detailed description may include not only components essential for solving the problem, but also components that are not essential for solving the problem in order to exemplify the above technology. Therefore, the fact that these non-essential components are described in the accompanying drawings or detailed description should not be interpreted as immediately indicating that these non-essential components are essential. Furthermore, because the above-described embodiments are intended to exemplify the technology of the present invention, various modifications, substitutions, additions, omissions, etc. may be made within the scope of the claims or their equivalents. [Explanation of symbols]

[0066] 100 Web Systems 10 Web Server 20 Backend 21 Application Server (Backend) 22 Customer database (backend) 23 API (Backend) 30 User terminals 40 SNS server (SNS service)

Claims

1. A Web system including a Web server that provides a website and cookies to a browser of a user terminal, and a backend that manages customer profiles, wherein the Web server has a function of obtaining cookies and Web transactions from the browser of the user terminal and passing them to the backend, a function of issuing new cookies and passing them to the browser of the user terminal and the backend when the browser of the user terminal does not store cookies or the expiration date of the cookies obtained from the browser of the user terminal has expired, a function of obtaining the phone number of the user terminal as the minimum necessary information for member registration for logging in to the member site and passing it to the backend, a function of obtaining an authentication code from the browser of the user terminal and passing it to the backend, and a function of providing the member site to the browser of the user terminal when the login to the member site is approved by the backend, and the backend has a function of searching for a customer profile associated with the cookies received from the Web server, a function of newly creating a customer profile by associating the cookies and Web transactions received from the Web server when there is no customer profile associated with the cookies, a function of sending an authentication code to the phone number received from the Web server when a login to the member site is requested and there is no phone number in the customer profile associated with the cookies, a function of adding the phone number received from the Web server to the customer profile associated with the cookies when the authentication code received from the Web server is correct, and a function of approving the login to the member site when there is a phone number in the customer profile associated with the cookies or when the authentication code received from the Web server is correct when a login to the member site is requested. A Web system characterized by the above.

2. A Web system including a Web server that provides a website and cookies to a browser of a user terminal, and a backend that manages customer profiles, wherein the Web server has a function of obtaining cookies and Web transactions from the browser of the user terminal and passing them to the backend, A function that issues a new cookie and passes it to the browser of the user terminal and the backend when the browser of the user terminal does not save cookies or the expiration date of the cookies obtained from the browser of the user terminal has expired. A function that automatically obtains the phone number of the user terminal as the minimum necessary information for member registration for logging in to the membership site through user login to an external SNS service where the phone number of the user terminal is registered and passes it to the backend, and It has a function of providing the membership site to the browser of the user terminal when the login to the membership site is approved by the backend. The backend Has a function of searching for a customer profile associated with the cookie received from the Web server. Has a function of creating a new customer profile by associating the cookie received from the Web server and the Web transaction when there is no customer profile associated with the cookie. When a login to the membership site is requested, it has a function of adding the phone number of the user terminal obtained by the Web server through user login to an external SNS service to the customer profile associated with the cookie and approving the login to the membership site. A Web system characterized by this.

3. A Web system including a Web server that provides a Web site and cookies to the browser of the user terminal and a backend that manages customer profiles, The Web server Has a function of obtaining cookies and Web transactions from the browser of the user terminal and passing them to the backend. A function that issues a new cookie and passes it to the browser of the user terminal and the backend when the browser of the user terminal does not save cookies or the expiration date of the cookies obtained from the browser of the user terminal has expired. Has a function of obtaining an authentication code from the browser of the user terminal and passing it to the backend. It has a function of providing the membership site to the browser of the user terminal when the login to the membership site is approved by the backend. The backend Has a function of searching for a customer profile associated with the cookie received from the Web server. Has a function of creating a new customer profile by associating the cookie received from the Web server and the Web transaction when there is no customer profile associated with the cookie. A function to obtain the phone number of the user terminal as the minimum necessary information for membership registration for logging in to the membership site through message exchanges with the user by an external messaging service, A function to notify the user of an authentication code through an external messaging service when the phone number has been obtained, and When a login to the membership site is requested, if the authentication code received from the Web server is correct, approve the login to the membership site and add the phone number of the user terminal obtained through message exchanges with the user by an external messaging service to the customer profile associated with the cookie. It has such a function. A Web system characterized by this.

4. A method for logging in to a membership site in a Web system including a Web server that provides a website and a cookie to the browser of the user terminal, and a backend that manages customer profiles. The Web server Steps to obtain a cookie and a Web transaction from the browser of the user terminal and pass them to the backend, Steps to issue a new cookie and pass it to the browser of the user terminal and the backend when the browser of the user terminal does not save the cookie or the expiration date of the cookie obtained from the browser of the user terminal has expired, Steps to obtain the phone number of the user terminal as the minimum necessary information for membership registration for logging in to the membership site and pass it to the backend, Steps to obtain an authentication code from the browser of the user terminal and pass it to the backend, and Execute the step of providing the membership site to the browser of the user terminal when the login to the membership site is approved by the backend, The backend Steps to search for the customer profile associated with the cookie received from the Web server, Steps to newly create a customer profile by associating the cookie and the Web transaction received from the Web server when there is no customer profile associated with the cookie, Steps to send an authentication code to the phone number received from the Web server when there is no phone number in the customer profile associated with the cookie when a login to the membership site is requested, Steps to add the phone number received from the Web server to the customer profile associated with the cookie when the authentication code received from the Web server is correct, and When a login to the membership site is requested, execute the step of approving the login to the membership site if there is a phone number in the customer profile associated with the cookie or if the authentication code received from the web server is correct. A membership site login method characterized by the above.

5. A method for logging in to a membership site in a web system including a web server that provides a website and a cookie to the browser of a user terminal, and a backend that manages customer profiles, wherein the web server obtains a cookie and a web transaction from the browser of the user terminal and passes them to the backend; when the browser of the user terminal does not store the cookie or the expiration date of the cookie obtained from the browser of the user terminal has expired, issues a new cookie and passes it to the browser of the user terminal and the backend; automatically obtains the phone number of the user terminal as the minimum necessary information for membership registration for logging in to the membership site through a user login to an external SNS service where the phone number of the user terminal is registered and passes it to the backend, and when the backend approves the login to the membership site, executes the step of providing the membership site to the browser of the user terminal, wherein the backend searches for a customer profile associated with the cookie received from the web server; when there is no customer profile associated with the cookie, creates a new customer profile by associating the cookie and the web transaction received from the web server; and when a login to the membership site is requested, adds the phone number of the user terminal obtained by the web server through a user login to an external SNS service to the customer profile associated with the cookie, and executes the step of approving the login to the membership site. A membership site login method characterized by the above.

6. A method for logging in to a membership site in a web system including a web server that provides a website and a cookie to the browser of a user terminal, and a backend that manages customer profiles, wherein the web server obtains a cookie and a web transaction from the browser of the user terminal and passes them to the backend; Steps of issuing a new cookie and passing it to the browser of the user terminal and the backend when the browser of the user terminal does not save cookies or the expiration date of the cookies obtained from the browser of the user terminal has expired, Steps of obtaining an authentication code from the browser of the user terminal and passing it to the backend, and When the login to the membership site is approved by the backend, executing the step of providing the membership site to the browser of the user terminal, The backend Steps of searching for a customer profile associated with the cookie received from the Web server, Steps of creating a new customer profile by associating the cookie received from the Web server and the Web transaction when there is no customer profile associated with the cookie, Steps of obtaining the phone number of the user terminal as the minimum necessary information for membership registration for logging in to the membership site through the message exchange with the user by an external message service, Steps of notifying the user of the authentication code through an external message service when the phone number can be obtained, and When a login to the membership site is requested and the authentication code received from the Web server is correct, approving the login to the membership site and adding the phone number of the user terminal obtained through the message exchange with the user by an external message service to the customer profile associated with the cookie A membership site login method characterized by the above.

Images