How to log in to the web system and member site

Abstract

To make the registration process for logging into member sites safe and easy. [Solution] In the Web system 100, the Web server 10 has a function to obtain the phone number of the user terminal 30 as the minimum necessary information for member registration and pass it to the backend 20, and a function to obtain an authentication code from the browser of the user terminal 30 and pass it to the backend 20. The backend 20 has a function to send an authentication code to the phone number received from the Web server 10 when a login to the member site is requested and the customer profile linked to the cookie does not contain a phone number, a function to add the phone number received from the Web server 10 to the customer profile linked to the cookie if the authentication code received from the Web server 10 is correct, and a function to approve login to the member site when a login to the member site is requested and the customer profile linked to the cookie contains a phone number or 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 to conduct 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] Having to register both a user ID and password when logging into a member site for the first time is somewhat cumbersome for users. Therefore, if users avoid registering due to this inconvenience, companies will miss out on potential customers. On the other hand, omitting the password and only requiring a user ID significantly reduces the security of the member site.

[0006] Therefore, the objective of the present invention is to enable safe and easy member registration when logging into a member site in a web system. [Means for solving the problem]

[0007] A Web system according to one aspect of the present invention is a Web system including a Web server that provides a website and cookies to the browser of a user terminal, and a backend that manages customer profiles, wherein the Web server has the following functions: a function to obtain cookies and Web transactions from the browser of the user terminal and pass them to the backend; a function to issue a new cookie and pass it to the browser of the user terminal and the backend if the browser of the user terminal has not saved a cookie or if the expiration date of the cookie obtained from the browser of the user terminal has expired; a function to obtain the telephone number of the user terminal as the minimum necessary information for member registration for logging into the member site and pass it to the backend; a function to obtain an authentication code from the browser of the user terminal and pass it to the backend; and a function to provide the member site to the browser of the user terminal when the login to the member site is approved by the backend. The backend has the following functions: to search for a customer profile associated with a cookie received from the web server; to create a new customer profile by associating the cookie and web transaction received from the web server if no customer profile is associated with the cookie; to send an authentication code to the phone number received from the web server when login to the member site is requested and the customer profile associated with the cookie does not contain a phone number; to add the phone number received from the web server to the customer profile associated with the cookie if the authentication code received from the web server is correct; and to approve login to the member site when login to the member site is requested and the customer profile associated with the cookie contains a phone number or the authentication code received from the web server is correct.

[0008] A member site login method according to one aspect of the present invention is a login method to a member site in a web system including a web server that provides a website and cookies to the browser of a user terminal and a backend that manages customer profiles, wherein the web server performs the following steps: obtaining cookies and web transactions from the browser of the user terminal and passing them to the backend; issuing a new cookie and passing it to the browser of the user terminal and the backend if the browser of the user terminal has not saved a cookie or if the cookie obtained from the browser of the user terminal has expired; obtaining the telephone number of the user terminal as the minimum necessary information for member registration for login to the member site and passing it to the backend; obtaining 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. The backend then performs the following steps: search for a customer profile associated with a cookie received from the web server; create a new customer profile by associating the cookie and web transaction received from the web server if no customer profile is found associated with the cookie; send an authentication code to the phone number received from the web server if a login to the member site is requested and the customer profile associated with the cookie does not contain a phone number; add the phone number received from the web server to the customer profile associated with the cookie if the authentication code received from the web server is correct; and authorize the login to the member site if a customer profile associated with the cookie contains a phone number or if the authentication code received from the web server is correct. [Effects of the Invention]

[0009] According to this invention, users can register to log in to a member site by providing only the minimum necessary information, such as the phone number of their user terminal. Therefore, users can register safely and easily, and companies can expect to improve the effectiveness of lead generation by reducing the number of potential customers who are reluctant to go through the hassle of registration. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram of a web system according to one embodiment of the present invention. [Figure 2] This figure shows an example of an authentication form for unregistered members, an authentication code input screen, and a screen displaying successful authentication. [Figure 3] This is a schematic diagram illustrating the process of first logging into a member site by entering a phone number in a form. [Figure 4] This is a schematic diagram illustrating the process of initial login to a member site using a phone number obtained from an external social networking service. [Figure 5] This is a schematic diagram illustrating the process of initial login to a member site after obtaining a phone number through an external messaging service. [Figure 6] This is a schematic diagram illustrating the login process for the member site from the second time onwards. [Modes for carrying out the invention]

[0011] The embodiments of the present invention will be described in detail below, with reference to the drawings as appropriate. However, unnecessary details may be omitted. For example, detailed explanations of already well-known matters and redundant explanations of substantially identical configurations may be omitted. This is to avoid the following explanation becoming unnecessarily verbose and to facilitate understanding by those skilled in the art. The inventors provide the accompanying drawings and the following explanation so that those skilled in the art can fully understand the present invention, and do not intend to limit the subject matter described in the claims by means of these.

[0012] System Configuration Figure 1 is a schematic diagram of a web system according to one 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, as well as various external services and servers, such as various SNS servers 40 and mail servers 50, are also connected to the network 200. The user terminals 30, SNS servers 40, and mail servers 50 can communicate with each other via the network 200.

[0013] The web server 10 consists of one or more computer devices having a processor, memory, storage, and interfaces. The main role of the web server 10 is to communicate with the browser of the user terminal 30, provide the browser with the website requested by the user, and retrieve the data entered 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 consists of one or more computer devices having a processor, memory, storage, and interfaces. The main roles of the backend 20 are to manage customer profiles stored in the customer database 22 and to control login authentication to the member site.

[0015] The customer database 22 stores customer profiles, which are collections of various user-specific information. For example, a customer profile includes: 1) user terminal information such as the type and version of the user terminal's OS, browser type, IP address, and the user terminal's telephone number; 2) user personal information such as the user's name, address, email address, age, and gender; 3) web transactions such as the date and time of website visits and website activity history; and 4) cookies issued by the web server 10.

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

[0017] ≪Member Site Login≫ The website provided by the web server 10 includes a member site that cannot be accessed without logging in as a member. When a user attempts to log in to a member site, the web system 100 allows the user to log in to the member site if the user is already registered as a member, i.e., if a customer profile exists in the customer database 22. Even if the user is an unregistered member without a customer profile, if the user terminal 30 provides the minimum necessary information for member registration, the web system 100 will create a new customer profile and allow the user to log in to the member site.

[0018] Figure 2 is a diagram showing examples of (a) an authentication form, (b) authentication code input, and (c) successful authentication screen for unregistered members. As the route for obtaining the phone number 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 into the form, 2) an SNS login route where the phone number is automatically obtained from an external SNS service, and 3) a message service route where the phone number is obtained through an external message service. The user selects 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 enters 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 that includes the phone number of the user terminal 30, and if certain conditions are met, another service can obtain a part of that user profile. 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 using the above three routes will be described.

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

[0023] (S11) When the browser on user terminal 30 requests access to a website of any domain, the web server 10 responds to the request and provides the website. At this time, if the browser on user terminal 30 has saved a cookie issued by the web server 10, it sends the cookie to the web server 10. On the other hand, if the browser on user terminal 30 does not have a cookie saved, or if the saved cookie has expired, the web server 10 issues a new cookie and sends it to the browser on user terminal 30, and the browser on user terminal 30 saves the cookie sent from the web server 10. The web server 10 also obtains user terminal information such as the OS type, version, browser type, and IP address of user terminal 30, as well as web transaction information such as the date and time of website visit and the history of activity on the website, from the browser on user terminal 30.

[0024] (S12) The web server 10 passes cookies obtained from or newly issued by the browser of the user terminal 30, 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 the customer database 22 for a customer profile associated with the cookie received from the web server 10. 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 uses the cookie as a key to link this information, creates a new customer profile, and registers it in the customer database 22.

[0025] When a login request to the member site is received 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 a 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 member is not registered.

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

[0027] (S14) When the user selects the "Authenticate with phone number" radio button in the authentication form displayed in the browser of user terminal 30, enters the phone number of 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 a customer profile associated with that phone number. Since no such customer profile is found, the application server 21 generates an authentication code and sends a short message via API 23 from the external mail server 50 to the phone number informing it of the authentication code, and also notifies the web server 10 that the authentication code has been sent.

[0029] (S16) When the web server 10 is notified that it has received an authentication code from the application server 21, it provides the user terminal 30's browser with an authentication code input screen.

[0030] (S17) When the user enters an authentication code on the authentication code input screen, the web server 10 obtains the authentication code and passes it to the application server 21. Once 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 linked to the cookie and approves the login to the member site.

[0031] (S18) Once login to the member site is approved, the web server 10 provides the browser of the user terminal 30 with a screen indicating successful authentication. From this point onward, when the browser of the user terminal 30 requests access to any site or page within the member site, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0032] [SNS login route] Figure 4 is a schematic diagram illustrating the process of initial login to a member site after obtaining a phone number from an external social networking service.

[0033] (S21) When the browser on user terminal 30 requests access to a website of any domain, the web server 10 responds to the request and provides the website. At this time, if the browser on user terminal 30 has saved a cookie issued by the web server 10, it sends the cookie to the web server 10. On the other hand, if the browser on user terminal 30 does not have a cookie saved, or if the saved cookie has expired, the web server 10 issues a new cookie and sends it to the browser on user terminal 30, and the browser on user terminal 30 saves the cookie sent from the web server 10. The web server 10 also obtains user terminal information such as the OS type, version, browser type, and IP address of user terminal 30, as well as web transactions such as the date and time of website visit and the history of activity on the website, from the browser on user terminal 30.

[0034] (S22) The web server 10 passes cookies obtained from or newly issued by the browser of the user terminal 30, 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 the customer database 22 for a customer profile associated with the cookie received from the web server 10. 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 uses the cookie as a key to link this information, creates a new customer profile, and registers it in the customer database 22.

[0035] When a login request to the member site is received 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 a 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 member is not registered.

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

[0037] (S24) When the user selects the "Authenticate with LINE" radio button on the authentication form displayed in the browser of user terminal 30, and taps or clicks the "Log in with LINE" button and agrees to the privacy policy, the LINE login screen will be displayed in the browser of user terminal 30. LINE is a social networking service that has a user profile including the phone number of user terminal 30.

[0038] (S25) When a user logs into LINE using the browser on user terminal 30, the web server 10 retrieves the phone number of user terminal 30 from the user profile held by LINE, using LINE's SNS server 40, 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 also approves the login to the member site.

[0040] Once login to the member site is approved, the web server 10 provides the browser of the user terminal 30 with a screen indicating successful authentication. From this point onward, when the browser of the user terminal 30 requests access to any site or page within the member site, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0041] Thus, with the SNS login route, users can register as members and access the member site without code authentication.

[0042] [Message service route] Figure 5 is a schematic diagram illustrating the process of initial login to a member site after obtaining a phone number through an external messaging service.

[0043] (S31) When the browser on user terminal 30 requests access to a website of any domain, the web server 10 responds to the request and provides the website. At this time, if the browser on user terminal 30 has saved a cookie issued by the web server 10, it sends the cookie to the web server 10. On the other hand, if the browser on user terminal 30 does not have a cookie saved, or if the saved cookie has expired, the web server 10 issues a new cookie and sends it to the browser on user terminal 30, and the browser on user terminal 30 saves the cookie sent from the web server 10. The web server 10 also obtains user terminal information such as the OS type, version, browser type, and IP address of user terminal 30, as well as web transactions such as the date and time of website visit and the history of activity on the website, from the browser on user terminal 30.

[0044] (S32) The web server 10 passes cookies obtained from or newly issued by the browser of the user terminal 30, 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 the customer database 22 for a customer profile associated with the cookie received from the web server 10. 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 uses the cookie as a key to link this information, creates a new customer profile, and registers it in the customer database 22.

[0045] When a login request to the member site is received 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 a 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 member is not registered.

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

[0047] (S34) When the user selects the "Authenticate with other SNS" radio button in the authentication form displayed in the browser of user terminal 30, taps or clicks the icon of their choice of SNS, and agrees to the privacy policy, the selected SNS app will launch, and a message will be sent to the business account of the website the user is currently viewing.

[0048] (S35) When application server 21 receives an SNS message, it connects to SNS server 40 via API 23. This allows application server 21 to exchange messages with the user through the SNS application on user terminal 30. For example, application server 21 sends a message to the user asking them to enter the phone number of user terminal 30, and the user responds by providing the phone number.

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

[0050] (S37) When the web server 10 is notified that it has received an authentication code from the application server 21, it provides the user terminal 30's browser with an authentication code input screen.

[0051] (S38) When the user enters an authentication code on the authentication code input screen, the web server 10 obtains the authentication code and passes it to the application server 21. Once 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 linked to the cookie and approves the login to the member site.

[0052] (S39) Once login to the member site is approved, the web server 10 provides the browser of the user terminal 30 with a screen indicating successful authentication. From this point onward, when the browser of the user terminal 30 requests access to any site or page within the member site, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0053] [Second login or later] Figure 6 is a schematic diagram illustrating the login process for the member site from the second time onward.

[0054] (S41) When the browser on user terminal 30 requests access to a website of any domain, the web server 10 responds to the request and provides the website. Since this is the second or subsequent visit to the website, the browser on user terminal 30 has saved the cookie issued by the web server 10 and sends the cookie back to the web server 10. If the cookie saved by the browser on user terminal 30 has expired, the web server 10 issues a new cookie and sends it to the browser on user terminal 30, and the browser on user terminal 30 saves the cookie sent from the web server 10. The web server 10 also obtains user terminal information such as the OS type, version, browser type, and IP address of user terminal 30, as well as web transaction information such as the date and time of the website visit and the history of actions on the website, from the browser on user terminal 30.

[0055] (S42) The web server 10 passes cookies obtained from or newly issued by the browser of the user terminal 30, 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 the customer database 22 for customer profiles associated with the cookies received from the web server 10. In the case of newly issued cookies, there is no customer profile associated with the cookie in the customer database 22, so the application server 21 uses the cookie as a key to link this information, creates a new customer profile, and registers it in the customer database 22.

[0056] When a login request to the member site is received 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. If the phone number of the user terminal 30 is registered in the customer profile found, the application server 21 notifies the web server 10 that the user is already registered. 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 user is not yet registered.

[0057] (S43) When the web server 10 is notified by the application server 21 that the user has registered, it provides the member site to the browser of the user terminal 30. From then on, when the browser of the user terminal 30 requests access to any site or page within the member site, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0058] (S44) Meanwhile, when the web server 10 is notified by the application server 21 that a user is not registered, it provides an authentication form to the browser of the user terminal 30.

[0059] (S45) In the authentication form displayed in the browser of the user terminal 30, the user provides the phone number of the user terminal 30 via one of the form input route, SNS login route, or message service route, and the application server 21 obtains 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 with the new cookie received from the web server 10 and approves the login to the member site without sending an authentication code to the user terminal 30.

[0061] Once login to the member site is approved, the web server 10 provides an authentication form to the browser of the user terminal 30, as in step S43. From this point onward, whenever the browser of the user terminal 30 requests access to any site or page within the member site, the web server 10 provides the requested site or page to the browser of the user terminal 30.

[0062] On the other hand, if a user has never registered as a member, the phone number of the user terminal 30 will not be registered in the customer profile linked to the expired cookie. In this case, if the application server 21 obtains the phone number of the user terminal 30 via the form input route or the message service route, similar to the initial login to the member site, it will send an authentication code to the user terminal 30 to perform code authentication and then approve the login. If the phone number of the user terminal 30 is obtained via the SNS login route, the login will be approved without sending an authentication code to the user terminal 30.

[0063] <Effects> According to this embodiment, users can register to log in to the member site simply by providing the phone number of their user terminal 30 as the minimum necessary information in the case of the form input route or the message service route, or by simply logging into the SNS in the case of the SNS login route. As a result, users can register safely and easily, and companies can expect to improve the effectiveness of lead generation by reducing the number of potential customers who are reluctant to go through the complicated registration process.

[0064] Furthermore, if a user has previously registered by providing the phone number of their user terminal 30, code authentication will not be required for subsequent logins, reducing the hassle of re-registering.

[0065] As described above, embodiments have been explained as examples of the technology in the present invention. For this purpose, accompanying drawings and a detailed description have been provided. Therefore, among the components described in the accompanying drawings and detailed description, there may be not only components that are essential for solving the problem, but also components that are not essential for solving the problem, in order to illustrate the above technology. For this reason, the mere fact that these non-essential components are described in the accompanying drawings and detailed description should not be immediately assumed to be essential. Furthermore, since the above embodiments are for the purpose of illustrating the technology in the present invention, various changes, substitutions, additions, omissions, etc., can be made within the scope of the claims or equivalents. [Explanation of symbols]

[0066] 100 Web Systems 10 Web Servers 20 backends 21. Application Server (Backend) 22. Customer Database (Backend) 23 API (Backend) 30 User terminals 40 SNS Servers (SNS Services)

Claims

1. A web system including a web server that provides websites and cookies to the user's terminal browser, and a backend that manages customer profiles, The web server, A function that retrieves cookies and web transactions from the user's device browser and passes them to the backend. A function that issues a new cookie and passes it to the user's browser and the backend when the user's browser does not have a cookie saved or when the cookie obtained from the user's browser has expired. A function to obtain the user's phone number as the minimum necessary information for member registration and login to the member site, and pass it to the backend. A function to obtain an authentication code from the user's device browser and pass it to the backend, and It has the function of providing the member site to the user's device browser when login to the member site is approved by the backend. The backend is A function to search for customer profiles linked to cookies received from a web server. A function to create a new customer profile by linking cookies and web transactions received from the web server when no customer profile is associated with a cookie. A function that sends an authentication code to a phone number received from the web server when a customer profile linked to a cookie does not contain a phone number when login to a member site is requested. A function to add the phone number received from the web server to the customer profile linked to the cookie if the authentication code received from the web server is correct, and This system has a function that, when a user is requested to log in to a member site, will authorize the login if the customer profile linked to the cookie contains a phone number or if the authentication code received from the web server is correct. A web system characterized by the following:

2. The Web system according to claim 1, wherein the Web server has a function to automatically obtain the phone number of the user terminal through user login to an external SNS service where the phone number of the user terminal is registered and pass it to the backend.

3. The backend is A function to obtain the user's phone number through message exchange with the user via an external messaging service. A function to notify the user of an authentication code via an external messaging service if a phone number is obtained, and The web system according to claim 1, which has a function to approve login to a member site if the authentication code received from the web server is correct, and to add the acquired telephone number to the customer profile linked to the cookie.

4. The backend is A function to search for customer profiles linked to acquired phone numbers, and A web system according to any one of claims 1 to 3, which has the function of approving login to a member site when a customer profile linked to a telephone number exists, and updating the cookie linked to said customer profile with a cookie received from a web server.

5. A method for logging into a member site in a web system that includes a web server that provides a website and cookies to the user's terminal browser, and a backend that manages customer profiles, The web server, Steps include obtaining cookies and web transactions from the user's device browser and passing them to the backend. The steps include issuing a new cookie and passing it to the user's browser and the backend if the user's browser does not have a cookie saved or if the cookie obtained from the user's browser has expired. The step of obtaining the user's phone number as the minimum necessary information for member registration to log in to the member site and passing it to the backend. The steps include obtaining an authentication code from the user's device browser and passing it to the backend, and If the login to the member site is approved by the backend, the following step is performed to provide the member site to the user's device browser: The backend is Steps to search for customer profiles linked to cookies received from a web server, A step to create a new customer profile by linking cookies and web transactions received from a web server when no customer profile is associated with a cookie. When a login to a member site is requested, if the customer profile linked to the cookie does not contain a phone number, the Web server sends an authentication code to the phone number received. The steps include adding the phone number received from the web server to the customer profile associated with the cookie if the authentication code received from the web server is correct, and When a login to the member site is requested, the system will execute a step to authorize the login to the member site if the customer profile linked to the cookie contains a phone number or if the authentication code received from the web server is correct. This describes how to log in to the member site.

6. The member site login method according to claim 5, wherein the web server performs the step of automatically obtaining the user terminal's phone number through user login to an external SNS service where the user terminal's phone number is registered and passing it to the backend.

7. The backend is The step of obtaining the user's phone number through message exchange with the user via an external messaging service. The steps include: notifying the user of an authentication code via an external messaging service if a phone number is obtained, and The member site login method according to claim 5, further comprising the steps of approving login to the member site if the authentication code received from the web server is correct, and adding the acquired telephone number to the customer profile linked to the cookie.

8. The backend is Steps include searching for customer profiles linked to the acquired phone numbers, and A method for logging into a member site according to any one of claims 5 to 7, wherein if a customer profile linked to a telephone number exists, the method includes the steps of approving login to the member site and updating the cookie linked to the customer profile with a cookie received from the web server.

Images