JP7442602B2 - Programs, information processing methods, terminals - Google Patents

Description

The present disclosure relates to an information processing method, an information display method, a program, a terminal, and a server.

Electronic commerce (EC) is widely known as a form of commercial transaction using the Internet. Patent Document 1 discloses a method for authenticating the identity of an electronic commerce applicant who applies for electronic commerce. However, when it comes to electronic commerce and the like, there are cases where the user experience is poor.

Japanese Patent Application Publication No. 2004-246764

According to the first aspect of the present invention, an information processing method executed by a terminal includes code information for user authentication displayed on a display device that enables acquisition of information provided by a first server. reading with the reader; based on the read code information, transmitting information related to the code reader that read the code information to the first server by the communication unit of the terminal; and based on the information related to the code reader, the user Receiving information related to a service that manages information by the communication unit from the first server; communicating with a second server of the service by the communication unit based on the information related to the service; and communicating with a second server of the service regarding authentication of the user of the terminal. processing.
According to the second aspect of the present invention, a program to be executed by a computer of a terminal transmits code information displayed on a display device for user authentication to the terminal to enable acquisition of information provided by the first server. based on the read code information, transmitting information related to the code reader that read the code information to the first server by the communication unit of the terminal, and based on the information related to the code reader. , the communication unit receives information related to a service that manages user information from the first server; the communication unit communicates with a second server of the service based on the information related to the service; This includes processing related to authentication.
According to a third aspect of the present invention, the terminal includes a reading unit that reads code information displayed on the display device for user authentication that enables acquisition of information provided by the first server using a code reader of the terminal. , based on the read code information, sends information related to the code reader that read the code information to the first server, and sends information related to the service that manages user information based on the information related to the code reader to the first server. The terminal includes a communication unit that receives information from one server, and a control unit that communicates with a second server of the service using the communication unit based on information related to the service and controls authentication of the user of the terminal.
According to the fourth aspect of the present invention, an information processing method executed by a first server that provides information includes displaying code information on a display device for user authentication that enables acquisition of information provided by the first server. 1. Based on the fact that the code information is read by the code reader of the terminal, the communication unit receives from the terminal information related to the code reader from which the code information has been read. , transmitting information related to a service that manages user information to the terminal based on information related to the code reader, and communicating between the terminal that has received the information related to the service and a second server of the service. The method includes receiving information related to user information by a communication unit based on processing related to authentication of a user of a terminal through communication.
According to the fifth aspect of the present invention, a program to be executed by a computer of a first server that provides information displays code information for user authentication that enables acquisition of information provided by the first server on a display device. Based on the fact that the code information is read by the code reader of the terminal, the communication unit receives from the terminal information related to the code reader from which the code information has been read. and transmitting information related to a service that manages user information to the terminal based on information related to the code reader, and the terminal receiving the information related to the service and a second server of the service. and receiving information related to the user information by the communication unit based on processing related to authentication of the user of the terminal through communication with the communication unit.
According to the sixth aspect of the present invention, the server that provides information transmits code information for user authentication that enables acquisition of the provided information to the display device, and the code information is read by the code reader of the terminal. Based on this, information related to the code reader from which the code information was read is received from the terminal, and information related to the service that manages user information based on the information related to the code reader is transmitted to the terminal. , a communication unit that receives information related to user information based on a process related to authentication of a user of the terminal through communication between the terminal that received the information related to the service and a server different from the server where the service is performed.

FIG. 1 is a diagram illustrating an example of a configuration of a communication system in one aspect of an embodiment. FIG. 3 is a diagram illustrating an example of functions realized by a control unit of a terminal according to the first embodiment. FIG. 3 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. FIG. 1 is a diagram showing an example of the configuration of a PC according to the first embodiment. The figure which shows an example of the structure of the EC server based on 1st Embodiment. FIG. 3 is a diagram showing an example of EC user data according to the first embodiment. The figure showing an example of login management data concerning a 1st embodiment. FIG. 3 is a diagram showing an example of communication management data according to the first embodiment. FIG. 3 is a diagram illustrating an example of functions realized by the control unit of the IMS server according to the first embodiment. The figure showing an example of information stored in the storage part of the IMS server concerning a 1st embodiment. FIG. 3 is a diagram showing an example of IMS user data according to the first embodiment. FIG. 3 is a diagram showing an example of IMS authentication management data according to the first embodiment. 1 is a flowchart illustrating an example of a PC process, an EC server process, and a terminal process according to the first embodiment. 1 is a flowchart illustrating an example of EC server processing, terminal processing, and IMS server processing according to the first embodiment. 1 is a flowchart illustrating an example of a PC process, an EC server process, and a terminal process according to the first embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The figure which shows an example of the display screen based on 1st Embodiment. The flowchart which shows an example of the process of the EC server, the process of a terminal, and the process of an IMS server based on a 1st modification. The figure which shows an example of the payment management database based on a 1st modification. The figure which shows an example of the display screen based on 2nd Embodiment. The figure which shows an example of the display screen based on 2nd Embodiment. The figure which shows an example of the display screen based on 2nd Embodiment. The figure which shows an example of the display screen based on 2nd Embodiment. FIG. 7 is a diagram illustrating an example of user-specific product category data according to the third embodiment. The figure which shows an example of product category summary data based on 3rd Embodiment. The figure which shows an example of the friend management database based on 4th Embodiment. The figure which shows an example of the display screen based on 4th Embodiment. The figure which shows an example of the display screen based on 4th Embodiment. The figure which shows an example of the display screen based on a 4th modification. FIG. 7 is a diagram showing an example of a display screen according to a fifth embodiment. FIG. 7 is a diagram showing an example of a display screen according to a fifth embodiment. FIG. 7 is a diagram showing an example of login statistical data according to the fifth embodiment.

<Compliance with legal matters>
Please note that the disclosures described herein are subject to compliance with the host country's legal requirements necessary for the implementation of the disclosures, such as confidentiality of communications.

Embodiments for implementing an information processing method, an information display method, a program, a terminal, and a server according to the present disclosure will be described with reference to the drawings.

[System configuration]
FIG. 1 shows the configuration of a communication system 1 according to an embodiment of the present disclosure. As disclosed in FIG. 1, in the communication system 1, messaging service servers (hereinafter referred to as "IMS (Instant Messaging Service) servers") 10 (IMS server 10A, IMS server 10B, IMS server 10C,...), a terminal 20 (terminal 20A, terminal 20B, terminal 20C,...), an electronic commerce server (hereinafter referred to as "EC (Electronic Commerce) server") 40, and a personal computer (hereinafter referred to as "EC (Electronic Commerce) server"). , referred to as "PC (Personal Computer)") 50 (50A, 50B, 50C, . . . ) are connected. The IMS server 10 provides the terminals 20 owned by users via the network 30 with a service that allows messages to be sent and received between the terminals 20 . Note that the number of terminals 20 connected to the network 30 is not limited.

The network 30 plays a role of connecting one or more terminals 20, one or more IMS servers 10, one or more EC servers 40, and one or more PCs 50. That is, the network 30 refers to a communication network that provides a connection path so that the various devices described above can transmit and receive data after being connected.

One or more portions of network 30 may or may not be a wired network or a wireless network. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (wireless LAN: WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more of these. Network 30 may include one or more networks 30.

The terminals 20 (terminal 20A, terminal 20B, terminal 20C, ...) (an example of a terminal, not a limitation) may be any information processing terminal that can realize the functions described in each embodiment. good. Terminal 20 may include, by way of example and not limitation, a smartphone, a mobile phone (feature phone), a computer (by way of example and not limitation, a desktop, laptop, tablet, etc.), a media computer platform (by way of example and not limitation, a cable, satellite set, etc.). top boxes, digital video recorders), handheld computing devices (by way of example and not limitation, personal digital assistants, email clients, etc.), wearables (such as eyeglasses, watch devices, etc.), or other types of computers. , or communication platform. Further, the terminal 20 may be expressed as an information processing terminal.

Since the configurations of terminal 20A, terminal 20B, and terminal 20C are basically the same, in the following description, only terminal 20 will be described. Furthermore, if necessary, the terminal used by user X will be expressed as terminal 20X, and the user information in a predetermined service associated with user X or terminal 20X will be expressed as user information X. Note that the user information is user information associated with an account used by the user in a predetermined service. User information includes, by way of example and not limitation, the user's name, the user's icon image, the user's age, the user's gender, the user's address, and the user's hobbies, entered by the user or provided by a predetermined service. It includes information associated with the user such as preferences and user identifiers, and may be any one or a combination of these, or may not be the same.

The IMS server 10 (an example of a second server without limitation) has a function of providing IMS as a predetermined service to the terminal 20. The IMS server 10 may be any information processing device that can implement the functions described in each embodiment. IMS server 10 may include, by way of example and not limitation, server equipment, computers (such as, by way of example and not limitation, desktops, laptops, tablets, etc.), media computer platforms (by way of example and not limitation, cable, satellite set-top boxes, digital video recorders), handheld computing devices (by way of example, but not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Further, the IMS server 10 may be expressed as an information processing device. If there is no need to distinguish between the IMS server 10 and the terminal 20, the IMS server 10 and the terminal 20 may or may not be each expressed as an information processing device.

In the embodiment described below, by way of example and not limitation, a business that provides IMS (an example of a service that manages user information, but not limitation), in other words, a business that operates the IMS server 10 (a business that operates a second server, but is not limited to An example of a company) is a company. The name of the operator of the IMS server 10A will be referred to as "Company X," and the name of the IMS provided by Company X will be referred to as "IMS-X." Similarly, the name of the operator of the IMS server 10B will be referred to as "Company Y," the name of the IMS provided by Company Y will be referred to as "IMS-Y," and the name of the operator of the IMS server 10C will be referred to as "Company Z." The name of the IMS provided by Company Z is "IMS-Z."

The EC server 40 (an example of a first server, not limited to this) provides and sells products, etc. (not limited to this, but is provided by the first server) on a website for electronic commerce (hereinafter referred to as an "EC site"). It has a function of providing an electronic commerce service (hereinafter referred to as "EC service") that performs (an example of information provided). The EC server 40 may be any information processing device that can implement the functions described in each embodiment. The EC server 40 may include, by way of example and not limitation, a server device, a computer (such as, by way of example and not limitation, a desktop, laptop, tablet, etc.), a media computer platform (by way of example and not limitation, a cable, satellite set-top box, digital video, etc.). recorders), handheld computing devices (by way of example, but not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Further, the EC server 40 may be expressed as an information processing device or an information management device.

In the embodiment described below, by way of example and not limitation, a business that provides an EC service, in other words, a business of the EC server 40 (an example of a business of the first server, not limited) is assumed to be a company. The name of the business operator of the EC server 40 will be referred to as "Company EEE," and the name of the EC site will be referred to as "EC Site EEE," which is the same name as the company name.

The PC 50 (an example of a display device, not limited to this) is a computer owned by the user of the terminal 20, and has the function of logging into the EC server 40 and purchasing products using the EC service provided by the EC server 40. has. PC 50 includes, by way of example and not limitation, computers such as desktops, laptops, tablets, and the like.

In order to purchase (obtain) products etc. sold (provided) by the EC server 40, it is necessary to log in to the EC server 40. This "logging in to the EC server 40" can also be referred to as "logging in to the EC site," so in the following embodiments, these terms will be explained as having the same meaning.

The following embodiment will be described, by way of example and not limitation, assuming that each user owns the terminal 20 and the PC 50 as a set. As an example and not a limitation, user A owns a set of terminal 20A and PC 50A, user B owns terminal 20B and PC 50B as a set, and user C owns terminal 20C and PC 50C. It is assumed that the set is owned.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1 will be explained.

(1) HW configuration of terminal FIG. 1 shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a display unit 24, a microphone 25, a speaker 26, and a camera 27. Be prepared. Each component of the HW of the terminal 20 is interconnected via a bus B, by way of example and not limitation. Note that it is not essential that the HW configuration of the terminal 20 includes all the components. By way of example and not limitation, terminal 20 may or may not be configured to remove individual components or components, such as microphone 25 and camera 27.

The communication I/F 22 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of communicating with various devices such as the IMS server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the IMS server 10 according to instructions from the control unit 21. Furthermore, the communication I/F 22 receives various data transmitted from various devices such as the IMS server 10 and transmits the received data to the control unit 21 . Moreover, the communication I/F 22 may be simply expressed as a communication section. In addition, when the communication I/F 22 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20 and a device for outputting processing results processed by the terminal 20. In the input/output section 23, the input section and the output section may be integrated, or may be separated into an input section and an output section, or may not be.

The input unit is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 21. The input unit includes, by way of example and not limitation, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input via voice).

The output unit is realized by any one of all types of devices capable of outputting the processing results processed by the control unit 21 or a combination thereof. The output unit includes, by way of example and not limitation, a touch panel, a touch display, a speaker (audio output), a lens (including, but not limited to, 3D (three dimensions) output or hologram output), a printer, and the like.

The display unit 24 is realized by any one or a combination of all types of devices capable of displaying data according to the display data written in the frame buffer. The display unit 24 may include, by way of example and not limitation, a touch panel, a touch display, a monitor (including, but not limited to, a liquid crystal display or an OELD (organic electroluminescence display)), a head mounted display (HDM), a projection mapping, and a hologram. , devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

When the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may have substantially the same size and shape and may be disposed facing each other.

The control unit 21 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an ASIC (application-specific integrated circuit), and a field programmable FPGA (FPGA). gate array).

The storage unit 28 has a function of storing various programs and various data necessary for the terminal 20 to operate. The storage unit 28 includes various storage media such as, by way of example and not limitation, an HDD (hard disk drive), an SSD (solid state drive), a flash memory, a RAM (random access memory), and a ROM (read only memory). Furthermore, the storage unit 28 may or may not be expressed as a memory.

In the terminal 20, the program P is stored in the storage unit 28, and by executing the program P, the control unit 21 executes processing as each unit included in the control unit 21. That is, the program P stored in the storage unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Further, this program P may or may not be expressed as a program module.

The microphone 25 is used for inputting audio data. The speaker 26 is used to output audio data. The camera 27 is used to obtain moving image data.

(2) HW configuration of IMS server FIG. 1 shows an example of the HW configuration of the IMS server 10.
The IMS server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I/F 14 (interface), an input/output unit 12, and a display 13. The HW components of the IMS server 10 are interconnected via bus B, by way of example and not limitation. Note that the HW of the IMS server 10 does not necessarily include all the constituent elements as the configuration of the HW of the IMS server 10. By way of example and not limitation, the HW of the IMS server 10 may or may not be configured to remove the display 13.

The control unit 11 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by

The control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, processor core, multiprocessor, ASIC, or FPGA. In the present disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data necessary for the operation of the IMS server 10. The storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of communicating with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. Further, the communication I/F 14 receives various data transmitted from various devices such as the terminal 20 and transmits the received data to the control unit 11. Moreover, the communication I/F 14 may be simply expressed as a communication section. Furthermore, when the communication I/F 14 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 12 is realized by a device that inputs various operations to the IMS server 10. The input/output unit 12 is realized by any one or a combination of all types of devices that can receive input from a user and transmit information related to the input to the control unit 11. The input/output unit 12 is typically implemented using hardware keys such as a keyboard or a pointing device such as a mouse. Note that the input/output unit 12 may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via moving images), and a microphone (operation input via voice). However, in the present disclosure, the input/output unit 12 is not limited to these.

The display 13 is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)). Note that the display 13 may or may not be a head mounted display (HDM). Note that these displays 13 may or may not be capable of displaying display data in 3D. In the present disclosure, the display 13 is not limited to these.

(3) HW configuration of PC FIG. 4 shows an example of the HW configuration of the PC 50.
The PC 50 includes, by way of example and not limitation, a control unit 51 (CPU), a storage unit 55, a communication I/F 54 (interface), an input/output unit 52, a display 53, and a speaker 56. Each component of the HW of the PC 50 is interconnected via a bus B, by way of example and not limitation. Note that the HW of the PC 50 does not necessarily include all the components as the configuration of the HW of the PC 50.

(4) HW configuration of EC server FIG. 5 shows an example of the HW configuration of the EC server 40.
The EC server 40 includes, by way of example and not limitation, a control unit 41 (CPU), a storage unit 45, a communication I/F 44 (interface), an input/output unit 42, and a display 43. The HW components of the EC server 40 are interconnected via bus B, by way of example and not limitation. Note that the HW of the EC server 40 does not necessarily include all the constituent elements as the configuration of the HW of the EC server 40. By way of example and not limitation, the HW of the EC server 40 may or may not be configured to remove the display 43. Furthermore, the EC server 40 may include a speaker as a sound output unit that outputs sound.

Note that the HW, parts, etc. for realizing the above-mentioned components and functional units included in the EC server 40 and the PC 50 can be configured in the same manner as the IMS server 10. Therefore, repeated explanation will be omitted.

(5) Others The IMS server 10 stores the program P in the storage unit 15, and by executing the program P, the control unit 11 executes processing as each unit included in the control unit 11. That is, the program P stored in the storage unit 15 causes the IMS server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module.
The same applies to the EC server 40 and PC 50.

In each embodiment of the present disclosure, explanation will be given assuming that the program P is implemented by the CPU of the terminal 20 and/or the IMS server 10.
The same applies to the EC server 40 and PC 50.

Note that the control unit 21 of the terminal 20 and/or the control unit 11 of the IMS server 10 is not only a CPU having a control circuit, but also an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), etc. Each process may or may not be realized by formed logic circuits (hardware) or dedicated circuits. Further, these circuits may be realized by one or more integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. Furthermore, LSIs are sometimes called VLSIs, super LSIs, ultra LSIs, etc. depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.
The same applies to the EC server 40 and PC 50.

Furthermore, the program P (by way of example, but not limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium, or It doesn't have to be done. The storage medium can store the program P in a "non-temporary tangible medium". Further, the program P may or may not be for realizing a part of the functions of each embodiment of the present disclosure. Furthermore, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded on a storage medium.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) such as, by way of example and not limitation, field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs), hard drives, etc.・Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid state (SSD), a RAM drive, a secure digital card, or any other suitable storage medium, or a suitable combination of two or more thereof. Storage media may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. Note that the storage medium is not limited to these examples, and may be any device or medium as long as it can store the program P. Further, the storage medium may or may not be expressed as a memory.

The IMS server 10 and/or the terminal 20 can realize the functions of the plurality of functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P.
The same applies to the EC server 40 and PC 50.

Further, the program P of the present disclosure may or may not be provided to the IMS server 10 and/or the terminal 20 via any transmission medium (communication network, broadcast wave, etc.) that can transmit the program. good. By way of example and not limitation, the IMS server 10 and/or the terminal 20 implement the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like.
The same applies to the EC server 40 and PC 50.

Furthermore, each embodiment of the present disclosure can also be realized in the form of a data signal embedded in a carrier wave, in which the program P is embodied by electronic transmission.
At least part of the processing in the IMS server 10 and/or the terminal 20 may or may not be realized by cloud computing configured by one or more computers.
At least part of the processing in the terminal 20 may or may not be performed by the IMS server 10. In this case, at least part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the IMS server 10.
At least part of the processing in the IMS server 10 may or may not be performed by the terminal 20. In this case, at least part of the processing of each functional unit of the control unit 11 of the IMS server 10 may or may not be performed by the terminal 20.
Unless explicitly stated, the configuration of the determination in the embodiments of the present disclosure is not essential, and a predetermined process may be performed when the determination condition is met, or a predetermined process is performed when the determination condition is not met. You may or may not.

Note that the program of the present disclosure uses, by way of example and not limitation, scripting languages such as ActionScript and JavaScript (registered trademark), object-oriented programming languages such as Objective-C and Java (registered trademark), markup languages such as HTML5, etc. It is implemented using

Moreover, although it is repeated, various programs and various data in the present disclosure can be stored (recorded) in a computer-readable storage medium (recording medium). This storage medium includes various storage media such as a magnetic disk, an optical disk, a magneto-optical disk, and a flash memory.

<First embodiment>
Currently, network services such as the aforementioned IMS (Instant Messaging Service) and SNS (Social Networking Service) are popular.

"IMS" is a service that allows messages to be sent and received between communication devices of users in order to exchange conversations between users of communication devices using the Internet, and the IMS server 10 is a server that provides this IMS. It is. In this specification, the expression "IMS", which is an abbreviation for instant messaging service, is used, but in a broad sense, it means messaging services in general, and is not limited to instant messaging services.
"SNS" is a service that allows social networks and communities to be formed on the Internet, primarily for the purpose of communication between users of communication devices. Note that IMS can also be said to be one form (one form) of SNS. Therefore, IMS and SNS may or may not be distinguished.

Users who use the above services may use the user information registered to use the above services (including, but not limited to, the user's personal information and the user's account) to A system for receiving services is being put into operation. These different services include, by way of example and not limitation, the aforementioned electronic commerce (EC).

In the first embodiment, by way of example and not limitation, the service that manages user information is "IMS", and the code for logging into the EC server or EC site is a code prepared for each operator of the IMS server 10. In this embodiment, a code common to the operators of each IMS server 10 (hereinafter referred to as a "common code") is used to realize login to the EC server.

More specifically, as a code used to log in to the EC server 40 (EC site), a login code as a common code is generated by the EC server 40 and transmitted to the PC 50. The login code displayed on the PC 50 is read by the code reader of the terminal 20, and information related to the code reader that read the login code is transmitted from the terminal 20 to the EC server 40. After the user of the terminal 20 is authenticated by the IMS server 10 of the IMS, which is identified based on the information related to the code reader transmitted from the terminal 20, the user information stored and registered in this IMS server 10 is The EC server 40 acquires from the IMS server 10, and based on the acquired user information, login from the PC 50 to the EC server 40 (EC site) is executed.
The content described in the first embodiment is applicable to any of the other embodiments.

<Functional configuration>
(1) Functional configuration of terminal FIG. 2 is a diagram showing an example of functions realized by the control unit 21 of the terminal 20 in this embodiment.
The terminal 20 includes a terminal main processing section 211, a login support processing section 213, an IMS application processing section 215, and a login code reading processing section 217 as functions realized by the control section 21.

The terminal main processing section 211 has a function of executing terminal main processing, which is processing for controlling the terminal 20 in an integrated manner, according to the terminal main processing program 281 stored in the storage section 28 . As an example and not a limitation, if the terminal 20 is a mobile phone, it may control to make a call with another mobile phone, landline phone, etc. via the communication I/F 22, or The camera 27 controls access to various websites, controls the display unit 24 to display various information, or performs processing to analyze various sound data input from the microphone 25. Performs processes such as analyzing still images and moving images taken by.

The login support processing unit 213 is a process for supporting the PC 50 owned by the user of the terminal 20 to log into the EC server 40 (EC site) according to the login support processing program 2811 stored in the storage unit 28. It has a function to execute certain login support processing.

The IMS application processing unit 215 performs processing via the IMS server 10 based on the IMS application program 2831 included in the IMS application 283 and IMS application data 2833, which have been downloaded from the IMS server 10 in advance and stored in the storage unit 28. , has a function of executing IMS application processing, which is processing for transmitting and receiving IMS-related information (for example, but not limited to, messages, images, content, etc.) with other terminals 20.

The login code reading processing unit 217 starts an IMS application code reader (an example of a code reader, not limited to this), which is a code reader started within an IMS application executed by the IMS application processing unit 215, and reads the display 53 of the PC 50. It has a function that executes the process to read the login code displayed on the screen.

FIG. 3 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this embodiment.
The storage unit 28 stores, by way of example and not limitation, a terminal main processing program 281 that is read out by the control unit 21 and executed as the terminal main processing.
The terminal main processing program 281 also includes a login support processing program 2811 as a subroutine program, which is read by the control unit 21 and executed as a login support processing. The login support process will be described in detail later using a flowchart.

Further, the storage unit 28 stores, by way of example and not limitation, a plurality of IMS applications 283 downloaded from the IMS servers 10 (10A, 10B, 10C, . . . ) of each business operator (each company).

Each IMS application 283 includes an IMS application program 2831 that is read by the control unit 21 and executed as IMS application processing, and IMS application data 2833 that stores various data related to the IMS application.

(2) Functional configuration of PC FIG. 4 shows an example of functions realized by the control unit 51 of the PC 50 in this embodiment.
The PC 50 includes a PC main processing section 511, a login processing section 513, and a polling processing section 515 as functions realized by the control section 51.

The PC main processing unit 511 has a function of executing PC main processing, which is processing for controlling the PC 50 in an integrated manner, according to a PC main processing program 551 stored in the storage unit 55.

The login processing unit 513 has a function of executing login processing, which is processing for logging into the EC server 40 (EC site), according to the login processing program 5511 stored in the storage unit 55.

The polling processing unit 515 has a function of executing a polling process, which is a process of polling the EC server 40. The polling process will be explained using the flow of the login process.

FIG. 4 shows an example of information stored in the storage unit 55 of the PC 50 in this embodiment.
The storage unit 55 stores, by way of example and not limitation, a PC main processing program 551 that is read out by the control unit 51 and executed as PC main processing.
The PC main processing program 551 also includes a login processing program 5511 as a subroutine program, which is read by the control unit 51 and executed as a login processing. The login process will be described in detail later using a flowchart.

(3) Functional configuration of EC server FIG. 5 shows an example of functions realized by the control unit 41 of the EC server 40 in this embodiment.
The EC server 40 includes an EC server main processing section 411, a login management processing section 413, a code generation section 415, and an IMS authentication information generation section 417 as functions realized by the control section 41.

The EC server main processing unit 411 has a function of executing EC server main processing, which is processing for controlling the EC server 40 in an integrated manner, according to the EC server main processing program 451 stored in the storage unit 45. There is.

The login management processing unit 413 has a function of executing login management processing, which is processing for managing login from the PC 50 in this embodiment to the EC site provided by the EC server 40 on the Internet.

The code generation unit 415 is a code generator for logging into the EC server 40 (EC site) from the PC 50 to enable the user of the terminal 20 to use the PC 50 to purchase products etc. sold by the EC server 40 on the EC site. It has a function of generating a login code (hereinafter referred to as "login code") for performing authentication (an example of user authentication, not limited).

In this embodiment, the code generation unit 415 generates a login code that is a two-dimensional code, by way of example and not limitation. A two-dimensional code is a display type code that has information in the horizontal and vertical directions, and includes a matrix code in which small squares are arranged vertically and horizontally (hereinafter referred to as "matrix code"), and a one-dimensional code. There are stacked codes (hereinafter referred to as "stacked codes") in which multiple original codes (that is, barcodes) are stacked one above the other.

In the following embodiments, to simplify the explanation, a QR code (registered trademark), which is an example of a widely used matrix code, will be described as an example of a login code.
Note that, unlike the embodiment below, as a matrix code other than a QR code, a code such as an SP code, Vericode, Maxi code, CP code, or Chameleon code may or may not be used as a login code. . Furthermore, instead of the matrix code, various stack codes may or may not be used as the login code.

When receiving a login request from the PC 50, the code generation unit 415 generates access information for accessing the EC site and information for associating the terminal 20 with the PC 50 (or associating the user of the terminal 20 with the PC 50). A QR code including certain association information and transmission request information requesting the EC server 40 to transmit information related to the code reader that read the two-dimensional code is generated as a login code.

Here, the "code reader" is a code reader for reading a two-dimensional code, and in this embodiment, a two-dimensional code (QR code in this embodiment) activated within an IMS application executed on the terminal 20. ) is equivalent to an IMS application code reader (in this embodiment, a QR code reader).

The access information includes, by way of example and not limitation, a URL (Uniform Resource Locator) indicating the address (web page address) of the EC site on the Internet.

The association information includes, by way of example and not limitation, tokens that are required to log in to the EC server 40 (EC site) and are randomly issued by the EC server 40 (hereinafter referred to as "login tokens"). ) is included.

A token is a type of authentication information issued by a certificate authority, and a login token in this embodiment is authentication information issued by the EC server 40 as a certificate authority to authenticate the terminal 20 or the user of the terminal 20. . Login tokens can also be expressed as "random tokens" or "access tokens." Since the login token is issued randomly, it becomes a different token each time the login code is displayed on the PC 50.

The transmission request information includes, by way of example and not limitation, a transmission command that is a command that requests the code reader that has read the two-dimensional code (in this embodiment, the login code) to transmit information related to the EC server 40. included. Here, the information related to the code reader includes, by way of example and not limitation, information for identifying the code reader that read the login code, and information for identifying the IMS on which the code reader that read the login code was activated. Contains information for

Note that if the terminal 20 is programmed to transmit information related to the code reader that reads the two-dimensional code, there is no need to transmit the above transmission request information (send command, etc.) to the terminal 20. . Therefore, it is not necessarily necessary to include the transmission request information in the login code, and it is not necessary to include the transmission request information in the login code.

The IMS authentication information generation unit 417 generates IMS authentication information (not limited to information related to a service that manages user information), which is information necessary for the user of the terminal 20 to receive IMS authentication by the IMS server 10, which will be described later. (for example).

FIG. 5 shows an example of information stored in the storage unit 45 of the EC server 40 in this embodiment.
The storage unit 45 stores, by way of example and not limitation, an EC server main processing program 451 that is read out by the control unit 41 and executed as the EC server main processing.
The EC server main processing program 451 also includes a login management processing program 4511 as a subroutine program, which is read by the control unit 41 and executed as login management processing. The login management process will be described in detail later using a flowchart.

Further, the storage unit 45 stores, by way of example and not limitation, EC user data 452, login management data 453, communication management data 454, and EC service database 459.

The EC server 40 stores in advance personal information of the user of the terminal 20 transmitted from the PC 50 or the like as "EC user information" in order to allow the user to use the EC service.
The data in which this EC user information is stored is EC user data 452, and an example of the data structure is shown in FIG.

The EC user data 452 includes, by way of example and not limitation, the user's name, the user's address, the user's age, the telephone number of the user's terminal 20 (hereinafter referred to as the "terminal telephone number"), and the user's name. The e-mail address of the terminal 20 (hereinafter referred to as "terminal e-mail address"), the e-mail address of the user's PC 50 (hereinafter referred to as "PC e-mail address"), and the purchase of products, etc. on the user's EC site. The history and the cumulative points, which are privilege information given to the user in response to the purchase of products, etc. on the EC site, are stored in association with each other. Note that the EC user data 452 may store any one of the above information, or may store a combination of the above information.

The login management data 453 is data for managing login to the EC server 40 (EC site), and an example of the data configuration is shown in FIG. 7.
The login management data 453 stores, by way of example and not limitation, a terminal telephone number, a terminal email address, a login ID, a login password, a login status, and a login IMS type in association with each other.

The terminal telephone number stored in the EC user data 452 is stored in the terminal telephone number.
The terminal email address stored in the EC user data 452 is stored in the terminal email address.

Login ID stores the login ID required to log in to the EC server 40 (EC site) Login password stores the login password required to log in to the EC server 40 (EC site) is memorized.

The login ID and login password are an ID as a user login account registered by the EC server 40 in order to allow the user to use EC, and a password associated with this account. These login ID and login password may be automatically issued by the EC server 40 and stored in the login management data 453 for registration at the time of first-time registration. Alternatively, at the time of first-time registration, the user may input and determine an arbitrary login ID and login password, which may be stored in the login management data 453 for registration. Furthermore, these login IDs and login passwords may be able to be reissued or reset after registration.

The login status is information indicating whether or not you are logged in to the EC server 40 (EC site). If you are logged in, "Logged in" is stored, and if you are not logged in, "- (non-)" is stored. Login)” is memorized.

The login IMS type is the user information of the user of the terminal 20 (hereinafter referred to as "IMS user information") stored in the IMS server 10, and the EC server 40 receives the IMS user information from the IMS server 10 in order to perform login authentication. This is the IMS type of the IMS server 10 that is the source of the IMS user information when the information is received. By way of example and not limitation, the name of the IMS, the ID of the company providing the IMS, etc. are stored. In the figure, a case is illustrated in which IMS names such as "IMS-Z" and "IMS-X" are stored.

In this embodiment, for all users, both the terminal phone number and the terminal email address are not necessarily stored in the EC user data 452 and the login management data 453, and depending on the user, the terminal phone number The explanation will be based on the assumption that one of the following and the terminal email address may be missing. This is because, in the method of this embodiment, in order to log in to the EC site, information on both the terminal phone number and the terminal email address is not necessarily required, and information on either one is sufficient. This is also because some users may not wish to register both the terminal telephone number and the terminal e-mail address when registering personal information.

Communication management data 454 is data for managing information related to communication with communication devices (mainly PC 50 and terminal 20) that accessed the EC site, and an example of the data structure is shown in FIG. 8.
The communication management data 454 includes, by way of example and not limitation, a communication device ID, a communication device type, communication device information, a login code generation flag, a login token, an association flag, and an association communication device ID. are stored in association with each other.

The communication device ID stores an ID that is identification information for identifying a communication device that has accessed the EC site.

The communication device type stores the type of communication device that accessed the EC site. By way of example and not limitation, "PC" is stored when the type of communication device is PC50, and "terminal" is stored when the type of communication device is terminal 20.

The communication device information stores information regarding the communication device transmitted from the communication device that accessed the EC site. This communication device information includes, by way of example and not limitation, communication information, user agent information, and other information.

Communication information includes, by way of example and not limitation, the IP address of the communication device, the host name of the communication device, the communication port of the communication device, and the information necessary to communicate with the communication device that accessed the EC site. Information such as the URL of the page requested to be displayed is stored.

User agent information stores information such as, by way of example and not limitation, the type of OS (operating system) used by the communication device, the type of browser, and the type of communication device used (PC/terminal, etc.). be done. The above communication device type is identified based on this user agent information.

Other information includes information such as the language of the communication device's browser, the character code of the browser, the browser connection method, the URL of the transition source page, information input to the page, information on the communication device's monitor, and the location of the communication device. Contains information such as information, plug-in information, etc.

The above communication device information is information that is transmitted (notified) from the communication device to the EC server 40 when the communication device accesses the EC site. The control unit 41 stores the communication device information received from the communication device in the communication management data 454 in association with the communication device ID. Note that the communication device information does not include information that can identify an individual user (personal information).

The login code generation flag is a flag indicating whether or not a login code has been generated for the communication device having the communication device ID. "ON" is stored when a login code is generated, and "OFF" is stored when a login code is not generated.

In the present embodiment, the description will be made assuming that a login code is generated only for the PC 50 (that is, a communication device of the communication device type “PC”). Therefore, for a communication device whose communication device type is "PC", the login code generation flag is set to "ON" when a login code is generated, but for communication devices whose communication device type is "terminal", the login code generation flag is set to "ON". In the device, the login code generation flag remains "OFF".

A login token included in a login code generated for a communication device whose login code generation flag is set to "ON" is stored in the login token. In the figure, the login token is shown as "T＊＊＊＊＊".

The association flag is a flag indicating whether or not a communication device whose communication device type is “PC” is associated with a communication device whose communication device type is “terminal”; if they are associated, “ "ON" is stored, and if there is no association, "OFF" is stored.

The associated communication device ID is the ID of the associated communication device. A communication device whose communication device type is “PC” is stored in association with a communication device ID of a communication device whose communication device type is “terminal,” and a communication device whose communication device type is “terminal” is stored in association with the communication device ID of a communication device whose communication device type is “terminal.” The communication device ID of a communication device whose device type is "PC" is stored in association with the communication device ID.

In this embodiment, when a login request is received from the PC 50, the code generation unit 415 generates the above-mentioned login code. Based on the communication device information received from the PC 50, the login code page including the generated login code image is sent to the communication partner's PC 50, so that the login code page is displayed on the display of the communication partner's PC 50. be done.

The login code displayed on the display 53 of the PC 50 is read by the code reader of the user's terminal 20, and the information included in the login code is identified.
Here, since the login token included in the login code is a random and unique token issued by the EC server 40, from now on, when the terminal 20 accesses the EC site, the identified login token is used as the EC server. By transmitting the information to the server 40, the EC server 40 can associate (link) the terminal 20 and the PC 50.

Specifically, when the terminal 20 communicates with the EC server 40 and a login token is sent from the terminal 20 to the EC server 40, the EC server 40 transmits the login token stored in the communication management data 454. From among them, a login token that matches the login token received from the terminal 20 is searched and identified. By doing so, the EC server 40 allows the login code displayed on the PC 50 of the communication device ID stored in the communication management data 454 in association with the specified login token to be read by the terminal 20 of the communication partner. Since it can be determined that the communication partner terminal 20 and the PC 50 are associated with each other, it is possible to associate the communication partner terminal 20 with the PC 50.

The EC service database 459 contains data related to the EC services provided by the EC server 40, such as image data of the EC site, category (classification) data of products sold on the EC site, product image data, and product price data. A stored database.

(4) Functional configuration of IMS server FIG. 9 is a diagram showing an example of functions realized by the control unit 11 of the IMS server 10 in this embodiment.
The IMS server 10 includes an IMS server main processing section 111, an IMS processing section 112, and an IMS user information provision processing section 113 as functions realized by the control section 11.

The IMS server main processing unit 111 has a function of executing IMS server main processing, which is processing for controlling the IMS server 10 in an integrated manner, according to the IMS server main processing program 151 stored in the storage unit 15. There is.

The IMS processing unit 112 performs processing for transmitting and receiving information related to IMS (for example, but not limited to, messages, images, content, etc.) between a plurality of terminals 20 according to the IMS processing program 1511 stored in the storage unit 15. It has the ability to execute certain IMS processing. By way of example and not limitation, when the IMS processing unit 112 receives a message sent from a terminal 20 in a predetermined talk room, etc., the IMS processing unit 112 transmits (forwards) the same message to the terminal 20 of another participant as the destination. .

The IMS user information provision processing unit 113 transfers the IMS user information stored and managed in the IMS user data 152 of the storage unit 15 to the network 30 according to the IMS user information provision processing program 1513 stored in the storage unit 15. It has a function of executing IMS user information providing processing, which is processing for providing to the EC server 40 via the IMS.

FIG. 10 is a diagram showing an example of information stored in the storage unit 15 of the IMS server 10 in this embodiment.
The storage unit 15 stores, by way of example and not limitation, an IMS server main processing program 151 that is read out by the control unit 11 and executed as the IMS server main processing.
The IMS server main processing program 151 also includes an IMS processing program 1511 read by the control unit 11 and executed as IMS processing, and an IMS user information read out by the control unit 11 and executed as IMS user information providing processing. The provision processing program 1513 is included as a subroutine program. The IMS user information provision process will be described in detail later using a flowchart.

The storage unit 15 also includes, by way of example and not limitation, data such as IMS user data 152, IMS authentication management data 153, communication management data 154, IMS authentication result information 155, and IMS transmission/reception history database 156. IMS content database 159 is stored.

The IMS user data 152 is data for managing IMS user information, and an example of its data structure is shown in FIG. 11.
The IMS user data 152 stores, by way of example and not limitation, a user name, a terminal telephone number, a terminal email address, a user ID, a user icon, and a profile in association with each other.

The user name is the name of the IMS user, and stores the name that the user of the terminal 20 registers when using the IMS service.
The terminal telephone number is the telephone number of the terminal 20 of the user of the user name, and stores the telephone number of the terminal 20 that the user of the terminal 20 registers when using the IMS service.
The terminal email address is the email address of the terminal 20 of the user with the user name, and stores the email address of the terminal 20 that the user of the terminal 20 registers when using the IMS service.

The user ID is an ID that functions as identification information for identifying a user with a user name, and an ID for uniquely identifying each user is stored.

The user icon is image data of an icon used by the user that is set on the terminal 20 of the user with the user name and sent to the IMS server 10, and in the IMS application, the image of this icon is displayed in association with the user name. Ru.

The profile is a user profile that is set on the terminal 20 of the user with the user name and sent to the IMS server 10, and is displayed in association with the user name in the IMS application.

In this embodiment, each user uses the IMS on the terminal 20 that he or she owns. However, in addition to or in place of the terminal 20, each user uses his own PC 50. You may or may not use IMS.

IMS authentication management data 153 is data for managing information necessary for IMS authentication. In this embodiment, the IMS server 10 authenticating that the user of the terminal 20 is a regular IMS user is referred to as "IMS authentication." The following description will be made assuming that when the IMS authentication result is OK, it becomes possible to provide IMS user information from the IMS server 10 to the EC server 40.

FIG. 12 is a diagram showing an example of the data structure of the IMS authentication management data 153.
The IMS authentication management data 153 stores, by way of example and not limitation, a user name, a user ID, a user password, and an IMS authentication code in association with each other.

The user name of each user stored in the IMS user data 152 is stored in the user name.
The user ID of each user stored in the IMS user data 152 is stored in the user ID. This user ID is used not only to identify each user but also to perform IMS authentication.
The user password is a password that is set on the terminal 20 of the user with the user ID and sent to the IMS server 10. This user password is used together with the user ID to perform IMS authentication.
The IMS authentication code (an example of information indicating that the user of the terminal has been authenticated by the service without limitation) is a code indicating that the result of IMS authentication of the user with the user ID is OK. In the figure, the IMS authentication code is shown as "C001*****".

The communication management data 154 is data for managing information related to communication with communication devices (mainly the terminal 20 and the EC server 40) that have accessed the IMS site. This communication management data 154 stores communication device information transmitted from a communication device in association with a communication device ID and a communication device type.

The IMS authentication result information 155 is information generated for each user of the terminal 20 whose IMS authentication result is OK, and is information used to notify the terminal 20 of the IMS authentication result. This IMS authentication result information 155 includes, by way of example and not limitation, an EC site URL and an IMS authentication code.

The IMS transmission/reception history database 156 is a database that stores transmission/reception history information such as messages transmitted/received between terminals 20 of users using IMS.

The IMS content database 159 is a database in which data of various contents related to IMS are stored.

<Processing>
13 to 15 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
In FIG. 13, from the left side, the login process is executed by the login processing unit 513 of the PC 50, the login management process is executed by the login management processing unit 413 of the EC server 40, and the login support process is executed by the login support processing unit 213 of the terminal 20. are shown respectively.
Further, FIG. 14 shows, in order from the left, a login management process following FIG. 13, a login support process following FIG. 13, and an IMS user information providing process executed by the IMS user information providing processing unit 113 of the IMS server 10. .
Further, in order from the left side, FIG. 15 shows a login process following FIG. 13, a login management process following FIG. 14, and a login support process following FIG. 14.
Further, each step in each process is indicated by a combination of uppercase letters and numbers, and the term "step" is omitted in this specification.

Note that the flowchart described below is just an example of the processing in this embodiment, and in the flowchart described below, some steps may not be executed, or additional steps may be inserted.

First, the login processing unit 513 accesses the EC site through the communication I/F 54 according to the EC site access operation performed on the input/output unit 52, and transmits the communication device information of its own device to the EC server 40 through the communication I/F 54. (A1).

The login management processing unit 413 determines the communication device type based on the user agent information included in the communication device information received from the PC 50 by the communication I/F 44, associates it with the communication device ID and the communication device type, and stores the information in the storage unit 45. It is stored in the communication management data 454. Then, the login management processing unit 413 transmits the EC page (electronic commerce page) of the EC site to the PC 50 via the communication I/F 44 based on the communication device information stored in the communication management data 454 (B1). As a result, the EC page is displayed on the display 53 of the PC 50 (A3).

Thereafter, the login processing unit 513 transmits login request information to the EC server 40 (EC site) to the EC server 40 via the communication I/F 54 in accordance with the user's login operation on the input/output unit 52 (A5).

Here, the timing to send the login request information is the timing when it is detected that the user has performed a login operation on the top page of the EC site, or the timing when the user logs in from the top page and on the shop page where products etc. are displayed. This can be the timing at which the operation is detected.

When the communication I/F 44 receives login request information from the PC 50 (B3), the code generation unit 415 of the EC server 40 performs login code generation processing (B5).

Specifically, by way of example and not limitation, a random token is issued as a login token using a method (algorithm) that generates a random token. Then, a login code including the EC site URL, the issued login token, and a sending command is generated. More specifically, the URL string of the EC site, the login token string (for example, a parameter starting with a "?" symbol), and the sending command string (for example, a parameter starting with a "#" symbol). The configured data is encoded and visualized to generate a login code represented by a two-dimensional code image. Further, the login code generation flag "ON" and the issued login token are stored in the communication management data 454 in association with the communication device ID of the PC 50.

Next, the login management processing unit 413 transmits a login code page including the login code generated by the code generation unit 415 to the PC 50 via the communication I/F 44 based on the communication device information stored in the communication management data 454. (B7). As a result, a login code page is displayed on the display 53 of the PC 50 (A7).

Thereafter, the polling processing unit 515 of the PC 50 starts executing polling processing (A9). Specifically, a process is started to inquire of the EC server 40 whether or not the user authentication necessary for logging into the EC server 40 (EC site) from the PC 50 has been performed. In response to this, the login management processing unit 413 starts executing a login determination process to determine whether the PC 50 is ready for login (B9).

On the other hand, the login support processing unit 213 executes an IMS application program 2831 included in any one of the IMS applications 283 out of the plurality of IMS applications 283 stored in the storage unit 28 according to the IMS application startup operation performed on the input/output unit 23. The IMS application is started by executing (C1).

Next, the login support processing unit 213 determines whether or not the IMS application code reader activation operation has been performed on the input/output unit 23 (C3), and if it is determined that the operation has been performed (C3; Yes), one of the functions of the IMS application is activated. The IMS application code reader is activated (C5).

After that, the login code reading processing unit 217 of the terminal 20 determines whether the two-dimensional code has been read by the IMS application code reader started at C5 (C7), and if it is determined that the two-dimensional code has been read (C7; Yes). ), code information identification processing is executed (C9). Specifically, data is decoded from the read two-dimensional code to identify various types of information included in the read two-dimensional code.

The login code included in the login code page displayed on the PC 50 at A7 of the login process is read, and the code information identification process is executed to identify the EC site URL, login token, and sending command. be done. If the identified information is information included in the login code, the login support processing unit 213 accesses the EC site through the communication I/F 22 based on the identified EC site URL, and accesses the EC site through the communication I/F 22. The communication device information of the own terminal is transmitted to the EC server 40 (C11).

Here, when the user taps the EC site URL on the terminal 20 and accesses the EC site from the terminal 20, a unique browser built into the IMS application (hereinafter referred to as "application browser") is used to page the EC site. can be displayed. Based on the transmission command received from the EC server 40, the login support processing unit 213 transmits the application browser information of the currently running IMS application in the user agent information, and also adds the login token identified by C9 to other information. Include and send.

The login management processing unit 413 determines the communication device type based on the user agent information included in the communication device information received from the terminal 20 by the communication I/F 44, associates it with the communication device ID and the communication device type, and stores it in the storage unit 45. It is stored in the communication management data 454 of. Additionally, the communication management data 454 is searched for a login token that matches the login token included in the received communication device information, and "ON" is stored in the association flag for each of the two communication device IDs with which the login token matches. At the same time, one communication device ID is mutually stored in the other associated communication device ID.

Thereafter, the login management processing unit 413 performs IMS type identification processing (B13). Specifically, the code reader identifies the activated IMS application (that is, IMS type) based on the application browser information of the user agent information included in the communication device information received from the terminal 20. Since the IMS type can be identified from the application browser information, the application browser information (an example of information related to the code reader that read the code information, but is not limited to this) is the IMS of the terminal 20 where the login code was read. This can be said to be information for identifying an application code reader or information for identifying an IMS in which the IMS application code reader of the terminal 20 whose login code has been read has been activated.

Note that in the above, the login support processing unit 213 transmits information about the application browser of the IMS application being executed to the EC server 40 as an example of information related to the code reader that read the code information. but not limited to. In addition, as an example of information related to the code reader that read the code information, the login support processing unit 213 may include identification information of the IMS application that started the code reader (IMS application identification information), and information related to the IMS application. Information such as the identification information of the IMS (IMS identification information) and the identification information of the operator providing this IMS (operator identification information) may also be transmitted to the EC server 40.

After that, the IMS authentication information generation unit 417 performs IMS authentication information generation processing (B15). Specifically, by way of example and not limitation, among the software packages distributed and provided by the IMS servers 10 of each business operator (each company), software packages capable of generating information regarding authentication of each IMS server 10. , IMS authentication information including, by way of example and not limitation, information such as a URL for accessing an IMS authentication site, using a software package obtained in advance from the IMS server 10 of the IMS type identified in B13. generate.

Note that the information included in the IMS authentication information is not limited to information such as the URL for accessing the IMS authentication site as described above. For example, the IMS authentication information may include information such as an authentication request command requesting the user to access an IMS authentication site and receive IMS authentication.

Next, the login management processing unit 413 transmits the IMS authentication information generated in B15 to the terminal 20 via the communication I/F 44 (B17). Then, the login support processing unit 213 receives the IMS authentication information from the EC server 40 via the communication I/F 22 (C13).

Next, the login support processing unit 213 accesses the authentication site of the IMS server 10 through the communication I/F 22 based on the URL of the authentication site included in the received IMS authentication information, and uses the communication I/F 22 to access the authentication site of the own terminal. The device information is sent to the IMS server 10 (C17). At this time, the login support processing unit 213 includes, by way of example and not limitation, the EC site URL in the other information and transmits it.

The IMS user information provision processing unit 113 stores the communication device information received from the terminal 20 through the communication I/F 14 in the communication management data 154, and creates an IMS authentication page through the communication I/F 14 based on the stored communication device information. It is transmitted to the terminal 20 (D1). As a result, the IMS authentication page is displayed on the display unit 24 of the terminal 20 (C19).

Next, the login support processing unit 213 performs a confirmation process (C21). Specifically, by way of example and not limitation, the display unit 24 displays a confirmation screen including a message confirming that the IMS user information of the user of the terminal 20 is to be transmitted from the IMS server 10 to the EC server 40. The login support processing unit 213 then transmits the confirmation result to the IMS server 10 via the communication I/F 22 based on the user's operation on the confirmation screen.

Thereafter, the login support processing unit 213 and the IMS user information provision processing unit 113 perform IMS authentication processing (an example of processing related to terminal user authentication, not limited to this) (C23, D3). As a specific example, the IMS user information provision processing unit 113 determines whether the user ID and user password transmitted from the terminal 20 match the user ID and user password stored in the IMS authentication management data 153 of the storage unit 15, respectively. Determine whether or not to do so. If they match, authentication is OK; if they do not match, authentication is rejected.

After that, the IMS user information provision processing unit 113 performs IMS authentication result information generation processing (D5). As a specific example, an IMS authentication code is generated for a user whose authentication is OK in IMS authentication processing, and the generated IMS authentication code is associated with the user ID of the user whose authentication is OK, and stored in the IMS in the storage unit 15. It is stored in the authentication management data 153. Then, the EC site URL included in the communication device information received from the terminal 20 is set as a callback URL, and IMS authentication result information including this callback URL and the generated IMS authentication code is generated.

Next, the IMS user information provision processing unit 113 transmits the generated IMS authentication result information 155 to the terminal 20 via the communication I/F 14 (D7). The login support processing unit 213 receives the IMS authentication result information 155 from the IMS server 10 via the communication I/F 22 (C25).

Thereafter, the login support processing unit 213 accesses the EC site again using the communication I/F 22 based on the callback URL included in the received IMS authentication result information 155, and updates the communication device information of the own terminal using the communication I/F 22. It is transmitted to the EC server 40 (C27). At this time, the login support processing unit 213 transmits, by way of example and not limitation, the IMS authentication code included in the IMS authentication result information received from the IMS server 10 and the login token identified by C9, along with other information. do.

The login management processing unit 413 performs terminal suitability determination processing (B19). As a specific example, the communication device ID is determined based on the communication device information received from the terminal 20, and the login token stored in the communication management data 454 in association with the determined communication device ID and the received login token are determined. Determine whether or not the token matches. Further, it is determined whether an associated communication device ID is stored in the communication management data 454 in association with the determined communication device ID. Then, if these conditions are met, the terminal 20 determines that it is appropriate.

If the terminal 20 is determined to be suitable in the terminal suitability determination process, the login management processing unit 413 transmits the IMS authentication code received from the terminal 20 to the IMS server 10 via the communication I/F 44, and the IMS server 10 The IMS user information is requested from the host (B21). In this case, by way of example and not limitation, the EC server 40 obtains information such as a URL for accessing the site of the IMS server 10 in advance, and accesses the IMS server 10 based on this URL. Then, the IMS user information can be requested.

When the IMS user information provision processing unit 113 receives a request for IMS user information from the EC server 40 via the communication I/F 14, it performs an IMS user information determination process (D9). Specifically, the IMS authentication code that matches the IMS authentication code received from the EC server 40 is searched from the IMS authentication management data 153 of the storage unit 15, and the user whose user name is stored in association with the matching IMS authentication code is searched. , the IMS user information stored in the IMS user data 152 of the storage unit 15 is determined.

Thereafter, the IMS user information provision processing unit 113 selects, by way of example and not limitation, the terminal phone number and terminal email address stored in the IMS user data 152 of the storage unit 15, out of the IMS user information determined in D9. It is transmitted to the EC server 40 via the communication I/F 14 (D11). The login management processing unit 413 receives the terminal telephone number and terminal email address from the IMS server 10 via the communication I/F 44 (B23).

The IMS user information provision processing unit 113 determines whether or not to end the process (D13), and if it is determined to continue the process (D13; No), returns the process to D1. Furthermore, if it is determined that the process should be terminated (D13; Yes), the IMS user information providing process is terminated.

Next, the login management processing unit 413 performs login determination processing (B25). Specifically, it is determined whether at least one of the terminal telephone number and the terminal email address received from the IMS server 10 at B23 is stored in the login management data 453 of the storage unit 45. If at least one of the terminal phone number and terminal email address is stored, it is determined that "Login OK" is determined, and if both the terminal phone number and terminal email address are not stored, "Login NG" is determined. ”.

Here, one of the terminal phone number and terminal email address received from the IMS server 10 is stored in the login management data 453, but if the other information is not stored in the login management data 453, the other information is stored in the login management data 453. information is stored in the login management data 453. In other words, if the terminal telephone number is missing, the terminal telephone number received from the IMS server 10 is stored in the login management data 453, and if the terminal email address is missing, the terminal email received from the IMS server 10 is stored. By storing the address in the login management data 453, missing information is supplemented. Similarly, missing information is stored in the EC user data 452 to be supplemented.

If it is determined that the login is OK (B27; OK), the login management processing unit 413 transmits a login OK notification to the terminal 20 and the PC 50 via the communication I/F 44 (B29). On the other hand, if it is determined that the login is NG (B27; NG), the login management processing unit 413 transmits a login NG notification to the terminal 20 and the PC 50 via the communication I/F 44 (B31).

When the login support processing unit 213 receives the login notification from the EC server 40 through the communication I/F 22 (C29), the login support processing unit 213 performs a login result notification process (C31). Specifically, if the received login notification is a login OK notification, a message indicating that login is OK is displayed on the display unit 24 to notify the user that login is permitted. On the other hand, if the received login notification is a login NG notification, a message indicating that the login is NG is displayed on the display unit 24 to notify the user that the login is not permitted.

Next, the login support processing unit 213 determines whether or not to terminate the running IMS application (C33), and if it is determined to continue (C33; No), the process returns to C3. On the other hand, if it is determined to terminate (C33; Yes), the IMS application being executed is terminated (C35). Then, the login support process ends.

When the login processing unit 513 receives the login notification from the EC server 40 via the communication I/F 54 (A11), the login processing unit 513 ends the polling process started in A9 (A13).

The login management processing unit 413 ends the login determination process that started in B9 (B33). Then, the login management processing unit 413 transmits the login data to the PC 50 via the communication I/F 44 (B35). Specifically, in the login management data 453, the login ID and login password that are stored in association with the same terminal telephone number and terminal email address as those received from the IMS server 10 are entered. A page is generated and a URL for accessing the login page is transmitted to the PC 50 via the communication I/F 44.

When the communication I/F 54 receives the URL from the EC server 40 (A15), the login processing unit 513 accesses the login page via the communication I/F 54 based on the received URL (A17). As a result, a login page in which the login ID and login password have been entered is displayed on the display 53 of the PC 50.

Next, the login processing unit 513 determines whether a login operation to execute login has been performed on the login page (A19), and if it is determined that a login operation has been performed (A19; Yes), the A login execution notification is sent to the EC server 40 (A21). Then, the login process ends. Upon receiving the login execution notification from the PC 50 via the communication I/F 44, the login management processing unit 413 causes the PC 50 to log in to the EC site (B37).

Next, the login management processing unit 413 determines whether or not to end the process (B39), and if it is determined to continue the process (B39; No), returns the process to B1. On the other hand, if it is determined that the process should be ended (B39; Yes), the login management process is ended.

If the login processing unit 513 determines that no login operation has been performed at A19 (A19; No), it determines whether or not to end the process (A21), and if it determines to continue the process (A21; No). ), the process returns to A19. On the other hand, if it is determined that the process should be terminated (A21; Yes), the login process is terminated.

Note that in the above process, the confirmation process that the login support processing unit 213 of the terminal 20 executes at C21 may or may not be executed after C11. In this case, the login support processing unit 213 may send, by way of example and not limitation, a message confirming login to the EC site from the PC 50 after the terminal 20 accesses the EC site at C11, and IMS user information of the user of the terminal 20. The display unit 24 may or may not display a confirmation screen including a message confirming that the IMS server 10 will send the EC server 40 from the IMS server 10 to the EC server 40.

Further, in the login process executed by the login processing unit 513 of the PC 50, steps A19 to A23 may be omitted and the EC site may be automatically logged in after accessing the login page in A17. You don't have to. In this case, the user may or may not automatically log in to the EC site after the login page is displayed once. Further, the user may or may not be able to automatically log in to the EC site without displaying the login page.

<Display screen>
FIG. 16 is a diagram showing an example of an EC page display screen displayed on the display 53 of the PC 50 in this embodiment.
This display screen shows the display screen of the shop page where products, etc. are displayed after the PC 50 accesses the EC site (A1 of the login process) and proceeds from the top page of the EC site (A1 of the login process). A3).

At the top of the screen, the name of the EC site "EEE" is displayed, and next to it is displayed a search word entry field for entering a search word. Further, below that, tags indicating categories of products to be sold are displayed, and by selecting a tag, a list of products associated with that tag is displayed. Product classifications include, but are not limited to, "food products," "daily necessities," "books," etc., and tags corresponding to these product classifications include "food tags," "Daily necessities tag", "book tag", etc. are displayed.

In the display example of FIG. 16, a state in which the "book tag" is selected is shown, and the products associated with the "book tag" include a book with the title "P", a book with the title "Q", and a book with the title "R". '' books are displayed, and details such as price and evaluation of each book are displayed. Further, a "purchase button" is displayed in association with each book, and by pressing the "purchase button" it becomes possible to add the book to a shopping cart.

In addition, the contents of the shopping cart are displayed in the purchased items column on the right side of the screen, and by pressing the "purchase procedure button" that says "Log in and proceed with purchase", it is determined that the login operation has been performed, and the PC 50 Login request information is sent from the EC server 40 (A5 of login processing).

FIG. 17 is a diagram showing an example of the display screen of the login code page displayed on the display 53 of the PC 50 (A7 of the login process).
In this display screen, a login code represented by a QR code image generated by the EC server 40 is displayed in the center of the screen. Additionally, a "return to shop button" is displayed at the bottom of the screen as a button for returning to the shop page.

FIG. 18 is a diagram showing an example of an IMS application screen displayed on the display unit 24 of the terminal 20. Here, a state is shown in which an IMS application named "IMS-Y" has been started and an IMS application function selection screen for selecting a function of "IMS-Y" is displayed.
This IMS application function selection screen displays icon images associated with multiple types of functions provided as functions of "IMS-Y", including icons associated with the IMS application code reader. Contains images.

When the user taps the icon image associated with the IMS application code reader on the IMS application function selection screen in FIG. 18, the IMS-Y code reader is activated and a reading standby screen as shown in FIG. will be displayed. In this state, by moving the terminal 20 so that the two-dimensional code is included in the frame at the center of the screen, the two-dimensional code is read by the IMS-Y code reader.

FIG. 20 is a diagram showing an example of a display screen displayed on the display unit 24 when a two-dimensional code is read by the IMS-Y code reader, and shows a login code displayed on the PC 50 by the IMS-Y code reader. indicates that it has been read.
When the login code displayed on the PC 50 is read by the IMS-Y code reader (C7 of login support processing; Yes), code information identification processing is executed (C9 of login support processing), and based on the identified information. , the EC site is accessed from the terminal 20 (C11 of login support processing). In this case, the words "Connecting..." are displayed above the login code.

FIG. 21 is a diagram showing an example of a confirmation screen displayed on the display unit 24 of the terminal 20.
This confirmation screen is a screen that is displayed when the confirmation process is executed (C21 of the login support process) on the IMS authentication page (C19 of the login process), and the IMS authentication page of "IMS-Y" is displayed at the top of the screen. "IMS-Y Authentication Page" indicating that the page is displayed is displayed. Also, below that, the message "Do you want to send your device phone number and device email address from IMS-Y to the e-commerce site EEE to log in?" is displayed, along with icons for "Do not allow" and "OK". has been done.

In FIG. 21, when the "OK" icon is tapped, a notification of "OK" is sent from the terminal 20 to the IMS server 10 as a confirmation result (C21 of the login support process). In this case, the following processing is executed. On the other hand, when the "Do not allow" icon is tapped, a notification of "NG" is sent from the terminal 20 to the IMS server 10 as a confirmation result (C21 of the login support process). In this case, the subsequent processing is not executed.

FIG. 22 is a diagram showing an example of a login result screen displayed on the display unit 24 of the terminal 20.
When the login OK notification is sent from the EC server 40 (B29 of the login management process) and the terminal 20 receives the login OK notification (C29 of the login support process), the login result notification process is executed (C31 of the login support process). The login result screen is displayed. This login result screen displays the message "Log-in to the EC site EEE has been completed" and an "OK" button.

FIG. 23 is a diagram showing an example of a login page display screen displayed on the display 53 of the PC 50.
This display screen displays a login page in which a login ID and a login password have been input (A17 of login processing). In this state, when the user presses the "login button" displayed below the login ID and login password, login from the PC 50 to the EC site is executed (A21 of login processing, B37 of login management processing). ).
Note that the display content in FIG. 23 is an example, and the display shown in FIG. 23 does not necessarily have to be performed.

FIG. 24 is a diagram showing an example of a shop page display screen displayed on the display 53 of the PC 50 after logging in to the EC site. This display screen is a screen that is displayed after the "purchase procedure button" is pressed on the shop page of FIG. 16 and the user logs in from the login page of FIG. 23.
This display screen displays information regarding the product book that the user has placed in the shopping cart as a product that the user desires to purchase. In addition, on the right side of the screen, the total amount calculated by adding up the subtotal calculated from the price of the item in the shopping cart, the cumulative points (EEE points) owned by the user, and the subtotal is displayed. is displayed. Further, a "purchase procedure button" is displayed below, and by pressing this purchase procedure button, it becomes possible to proceed to the purchase procedure.

<Effects of the first embodiment>
In the first embodiment, a code reader of the terminal 20 reads a login code displayed on a PC 50 (an example of a display device, not a limitation), and the PC 50 is connected to an EC server 40 (an example of a first server, not a limitation). This shows the configuration for logging in.
As an example of the effect of such a configuration, the user can log in to the first server based on a code common to services that manage user information, without the user having to individually select the provider of the service that manages user information. Therefore, it is possible to obtain the effect that user convenience can be improved.

In addition, in the first embodiment, the terminal 20 displays products, etc. (not limited, but limited) displayed on the PC 50 (not limited, but an example of a display device), and provided by the EC server 40 (not limited, but an example of a first server). A login code (not limited to, but not limited to, for login authentication (not limited to, but an example of user authentication) to the EC server 40 or EC site that enables acquisition of the information provided by the first server (an example of information provided by the first server) An example of code information) is read by an IMS application code reader, and based on the read login code, information on the IMS application browser that read the login code (not limited to information related to the code reader that read the code information) (an example)) is transmitted to the EC server 40 through the communication I/F 22 (not limited to this, but an example of the communication unit of the terminal).
As an example of the effect of such a configuration, information for identifying the code reader that read the code information and information for identifying the service related to the code reader that read the code information are transmitted to the first server. You can get the effect that you can.

Further, in the first embodiment, the terminal 20 performs IMS authentication by IMS (an example of a service, not a limitation) that manages IMS user information (an example of user information, not a limitation) based on information of an IMS application browser. The communication I/F 22 receives information for receiving IMS authentication from the EC server 40 (not limited to information related to a service that manages user information), and based on the received information for receiving IMS authentication, A configuration is configured to communicate with the server 10 (not limited, an example of a second server) through the communication I/F 22, and perform IMS authentication processing for the user of the terminal 20 (not limited, but an example of processing related to authentication of the terminal user). It shows.
An example of the effect of such a configuration is that the terminal can easily perform processing related to authentication of the terminal user by communicating with the second server based on information related to the service that manages user information. is obtained.

Further, in the first embodiment, based on the IMS authentication process of the user of the terminal 20 with the IMS server 10, the terminal 20 transfers IMS authentication result information (not limited to, an example of information related to user information) to the EC server 40. Based on the information received from (Example of area)
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the user has been authenticated by the first server.

Furthermore, the first embodiment shows a configuration in which the login code includes an EC site URL (not limited to this, but an example of information for the terminal to communicate with the first server) for the terminal 20 to access the EC site. ing.
As an example of the effect of such a configuration, the first server can be easily accessed from the terminal simply by reading the code information displayed on the display device with a code reader of the terminal. Further, since the terminal does not need to search for access information or acquire access information from the first server, the effect of reducing the load on the terminal can be obtained as a result.

Further, in the first embodiment, the login code is a transmission command (not limited to the code that read the code information) for causing the terminal 20 to transmit information related to the code reader that read the login code to the EC server 40. The configuration includes an example of information for causing information related to the reader to be transmitted from the terminal to the first server.
As an example of the effect of such a configuration, after reading code information with a code reader, the terminal transmits information related to the code reader that read the code information to the first server based on information included in the read code information. The effect is that it can be transmitted to

Furthermore, the first embodiment shows a configuration in which the login code includes a login token (not limited, but an example of association information) for associating the terminal 20 and the PC 50.
As an example of the effect of such a configuration, the terminal transmits association information included in the code information read by the code reader to the first server, thereby causing the first server to identify the display device that read the code information. This has the effect of being able to.

Further, in the first embodiment, when the user of the terminal 20 is IMS authenticated by the IMS server 10, the terminal 20 receives IMS authentication result information from the IMS server 10 through the communication I/F 22, and the received IMS authentication result information The configuration is shown in which the information is transmitted to the EC server 40 via the communication I/F 22.
As an example of the effect of such a configuration, an effect can be obtained in that the user of the terminal can notify the first server that the user of the terminal has been authenticated by the second server.

Further, in the first embodiment, the IMS authentication result information is an IMS authentication code indicating that the user of the terminal 20 has been IMS authenticated by the IMS, and the terminal 20 communicates the IMS authentication code and the login token with the IMS communication interface. /F22 shows a configuration for transmitting to the EC server 40.
As an example of the effect of such a configuration, the first information indicates that the terminal user has been authenticated by the second server, and that the terminal (or the user) authenticated by the second server has legitimate authority. This has the effect of being able to notify the server.

Further, in the first embodiment, the login token includes a different token each time the login code is displayed on the PC 50.
An example of the effect of such a configuration is that each terminal (or its user) that reads code information can be given a unique authority.

Further, the first embodiment shows a configuration in which the login code is information for logging into the EC server 40 in order to acquire products etc. provided by the EC server 40.
As an example of the effect of such a configuration, it is possible to easily log in to the first server by simply reading the code information displayed on the display device with a terminal. Further, since there is no need to perform any unnecessary operations on the terminal, it is possible to improve the user's convenience and reduce the number of erroneous operations performed by the user.

Further, in the first embodiment, the PC 50 displays a login code on the display 53, and indicates that the IMS authentication result information has been received by the EC server 40 based on the IMS authentication process of the user of the terminal 20 with the IMS server 10. A configuration is shown in which information indicating that login is permitted by the EC server 40 is displayed on the display 53 based on the following.
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the user has been authenticated by the first server.

Further, the first embodiment shows a configuration in which, when the login code is displayed on the display 53, the PC 50 performs a polling process to inquire of the EC server 40 whether login is permitted by the EC server 40.
As an example of the effect of such a configuration, it is possible to receive a notification from the first server that the user has been authenticated by the first server, and after receiving the notification, the information provided by the first server can be immediately transmitted. The effect is that it can be obtained.

Further, in the first embodiment, the EC server 40 uses a login code (not limited to a code) for login authentication (an example of user authentication, not limited to) that enables acquisition of products etc. provided by the EC server 40. An example of information) is transmitted to the PC 50 (an example of a display device, not a limitation) via the communication I/F 44, and the login code is read by an IMS application code reader (an example of a code reader, not a limitation) of the terminal 20. Based on this, information on the IMS application browser from which the login code was read (an example of information related to the code reader that read the code information) is transmitted from the terminal 20 to the communication I/F 44 (not limited to the information related to the code reader that read the code information). The configuration is shown in which the information is received by the communication unit (an example of the communication unit of the first server).
As an example of the effect of such a configuration, the first server can easily identify the code reader from which the code information has been read or the service associated with the code reader from which the code information has been read. It will be done.

Further, in the first embodiment, the EC server 40 is an IMS (an example of a service, not a limitation) that manages IMS user information (an example of user information, not a limitation) based on information of an application browser of the IMS. Information for receiving authentication (an example of information related to a service that manages user information, not limited to) is transmitted to the terminal 20 via the communication I/F 44, and the terminal 20 that has received the information for receiving IMS authentication , based on IMS authentication processing (not limited to, but an example of processing related to authentication of a terminal user) through communication with the IMS server 10, IMS authentication result information (not limited to, but an example of information related to user information) is sent to the communication IMS server 10. /F44 is shown.
As an example of the effect of such a configuration, the first server can easily understand that the user of the terminal has been authenticated by the second server.

In addition, in the first embodiment, the EC server 40 receives information indicating that login authentication has been performed based on receiving IMS authentication result information through the communication I/F 44 (not limited to information indicating that the user has been authenticated by the first server). An example of information indicating this is transmitted to the terminal 20 via the communication I/F 44.
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the first server has authenticated the user.

Furthermore, the first embodiment shows a configuration in which the login code includes an EC site URL (not limited to this, but an example of information for the terminal to communicate with the first server) for the terminal 20 to access the EC site. ing.
As an example of the effect of such a configuration, it is possible to easily cause the terminal to access the first server based on the login code sent to the display device.

Further, the first embodiment shows a configuration in which the login code includes a transmission command for causing the terminal 20 to transmit information related to the code reader that read the login code to the EC server 40.
As an example of the effect of such a configuration, the first server can transmit information related to the code reader that read the code information transmitted to the display device to the terminal that read the code information. In addition, since there is no need to separately notify the terminal to send information related to the code reader, the amount of communication on the first server can be reduced and the load on the first server can be reduced. is obtained.

Furthermore, the first embodiment shows a configuration in which the login code includes a login token (not limited, but an example of association information) for associating the terminal 20 and the PC 50.
As an example of the effect of such a configuration, the first server can easily identify the display device from which the code information has been read by receiving association information included in the code information read by the code reader from the terminal. This has the effect of being able to.

Further, in the first embodiment, when the user of the terminal 20 is IMS-authenticated by the IMS server 10, the EC server 40 receives IMS authentication result information from the terminal 20 based on the terminal 20 receiving IMS authentication result information from the IMS server 10. A configuration is shown in which the transmitted IMS authentication result information is received by the communication I/F 44.
An example of the effect of such a configuration is that the user of the terminal can understand that the user has been authenticated by the second server.

Further, in the first embodiment, the IMS authentication result information is an IMS authentication code indicating that the user of the terminal 20 has been IMS authenticated by IMS, and the EC server 40 receives the IMS authentication code transmitted from the terminal 20, A configuration in which a login token is received by the communication I/F 44 is shown.
As an example of the effect of such a configuration, the first server can confirm that the user of the terminal has been authenticated by the second server, and that the terminal that has been authenticated by the second server is a terminal with legitimate authority. This has the effect of being able to understand the

Further, the first embodiment shows a configuration in which the login code is information for logging into the EC server 40 (EC site) in order to acquire products etc. provided by the EC server 40.
As an example of the effect of such a configuration, it is possible to easily log in to the first server by simply having the terminal read the code information transmitted to the display device.

<First modification (1)>
In the first embodiment, the user authentication that enables the acquisition of information provided by the first server in the present disclosure has been described as authentication for logging into the EC server 40, but is not limited thereto. By way of example and not limitation, the authentication required to obtain an account such as a login ID required to use EC may or may not be the user authentication in the present disclosure.

Furthermore, in the first embodiment, the process related to authentication of the terminal user in the present disclosure was described as a process executed by the IMS server 10 to authenticate that the user of the terminal 20 is a regular user of the IMS. but not limited to. By way of example and not limitation, IDs required to use special features of the IMS, such as the ability to add users to become friends within the IMS (friends), and the ability to search for users with whom you would like to form friendships. The process for acquiring the information may or may not be related to the authentication of the terminal user in the present disclosure.

<Effects of first modification (1)>
As an example of the effect of this modification, a terminal user can simply read the code information displayed on the display device with the terminal's code reader without having to select a service provider that manages user information. The advantage is that the information necessary to obtain the information provided by the server, the information necessary to use the special function of the service of the second server, etc. can be easily obtained.

<First modification (2)>
In the first embodiment, the first server in the present disclosure is the EC server 40, but the present disclosure is not limited thereto. Any server of a business that stores user information associated with IMS user information stored by the IMS server 10 and provides some information is included in the first server in the present disclosure.

Similarly, in the first embodiment, the second server in the present disclosure is the IMS server 10, but the present disclosure is not limited thereto. If the EC server 40 stores user information associated with the stored EC user information and is a server of a business that provides some kind of service, it is included in the second server in the present disclosure.

Specifically, by way of example and not limitation, an SNS server is used as a server that stores and manages the user information (SNS user information) of users who use the SNS mentioned above, as well as information necessary for users to use SNS. This SNS server may be configured as the second server in the present disclosure.

<Effects of first modification (2)>
As an example of the effect of this modification, it is possible to make a server that provides services other than EC the first server, a server that provides services other than IMS as the second server, and have the first server perform user authentication. Effects can be obtained.

<First modification (3)>
In the first embodiment, the login code displayed on the PC 50 is read by the IMS application code reader activated on the terminal 20 to log in to the EC server 40 from the PC 50, but the present invention is not limited to this. As an example and not a limitation, a login code displayed on one terminal 20 may be read by an IMS application code reader activated on another terminal 20 to log in to the EC server 40 from one terminal 20. It's okay, and it doesn't have to be.

Furthermore, it is not necessary that the user owns the terminal 20 and the PC 50 as a set, and the login code displayed on the PC 50 that the user does not own can be used as an IMS application code that is started on the terminal 20 that the user owns. You may or may not be able to read it with a reader and log in to the EC server 40 from this PC 50.

<Effects of first modification (3)>
As an example of the effect of this modification, it is possible to obtain user authentication by accessing the first server from a communication device (display device) other than a personal computer.

<First modification (4)>
In the first embodiment, the login code is described as a two-dimensional code, but it is not limited to this. By way of example and not limitation, the login code may be a one-dimensional code (barcode) and may or may not be read by a one-dimensional code reader (barcode reader). In addition, the login code is a character code represented by a character string such as a URL, a login token, a sending command, etc., and by reading this with a camera or the like of the terminal 20 and recognizing the characters, the information contained in the login code is may or may not be identified.

<Effects of first modification (4)>
According to this modification, by simply reading a login code other than the two-dimensional code with the terminal 20, it is possible to easily log in to the EC server 40 (EC site) from the PC 50.

<First modification (5)>
In the first embodiment, the EC server 40 uses PC identification information for identifying the PC 50 (communication device ID of the PC 50) and terminal identification information for identifying the terminal 20 (the communication device ID of the terminal 20) based on the login token. Although the communication management data 454 is stored in association with the communication device ID), the communication management data 454 is not limited to this.

Specifically, the EC server 40 associates browser identification information for identifying the browser of the PC 50 with IMS application identification information for identifying the IMS application executed on the terminal 20 based on the login token. It may or may not be stored in the communication management data 454. Further, in the above combination, the EC server 40 may associate the PC identification information and the IMS application identification information and store them in the communication management data 454 based on the login token, or may not. good. Further, the browser identification information and the terminal identification information may or may not be stored in association with each other.

Furthermore, the EC server 40 uses user identification information for identifying the user of the terminal 20 as information for identifying the PC 50 instead of terminal identification information for identifying the terminal 20 (communication device ID of the terminal 20). They may be stored in association with each other.

In this case, by way of example and not limitation, at the time of initial registration, the user of the terminal 20 causes the EC server 40 to register one of the terminal telephone number and the terminal email address as user identification information. In addition to this, information such as the name and address of the user of the terminal 20 may be registered in the EC server 40 as user identification information, by way of example and not limitation.

Then, when the terminal 20 that has read the login code reader communicates with the EC server 40, in addition to the login token, information that has not been registered in the EC server 40 is transmitted to the EC server 40, by way of example and not limitation. For example, if one of the terminal phone number and terminal email address is registered, the other information, which was not registered, is sent to the EC server 40. Further, for example, if one of the user's name and address of the terminal 20 is registered, the other information that was not registered is sent to the EC server 40.

The EC server 40 stores the information received from the terminal 20 as user identification information in the communication management data 454 in association with information for identifying the PC 50 (communication device ID of the PC 50 and browser identification information of the PC 50). By doing so, the EC server 40 can associate (link) the user of the terminal 20 with the PC 50.

<Effects of first modification (5)>
As an example of the effect of this modification, the first server can associate a terminal and a display device using not only PC identification information and terminal identification information, but also browser identification information and IMS application identification information. Effects can be obtained. Furthermore, in addition to associating a terminal with a display device, it is also possible to associate a user of a terminal with a display device.

<First modification (6)>
In the first embodiment, when IMS authentication is performed by the IMS server 10, the terminal 20 transmits the IMS authentication code transmitted from the IMS server 10 to the EC server 40. That is, although it has been described that the EC server 40 indirectly receives the IMS authentication code from the IMS server 10 via the terminal 20 (this is referred to as "indirect callback"), the present invention is not limited to this.

FIG. 25 shows the processing portion of FIG. 14 extracted from the processing flow in this case. Note that the same steps as in FIG. 14 are given the same reference numerals, and repeated explanations will be omitted.

The login support processing unit 213 of the terminal 20 performs the IMS authentication process at C23, and then transmits the login token to the IMS server 10 via the communication I/F 22 (G23). By way of example and not limitation, in step G23, the terminal 20 transmits the EC site URL for accessing the EC site to the IMS server 10 in addition to the login token. Then, the IMS user information provision processing unit 113 of the IMS server 10 stores the EC site URL received from the terminal 20 in the storage unit 15.

Note that instead of transmitting the EC site URL to the IMS server 10 at step G23 as described above, the terminal 20 transmits the EC site URL to the IMS server 10 at an arbitrary timing before G23. You may also leave it there. Further, instead of having the terminal 20 transmit the EC site URL to the IMS server 10, the EC server 40 may transmit the EC site URL to the IMS server 10 and notify it in advance.

When the IMS user information provision processing unit 113 of the IMS server 10 receives the login token from the terminal 20 via the communication I/F 14, it performs a second IMS authentication result information generation process (H5). Specifically, information including the IMS authentication code and the login token received from the terminal 20 is generated as the second IMS authentication result information.

Next, the IMS user information provision processing unit 113 of the IMS server 10 accesses the EC site based on the EC site URL stored in the storage unit 15, and transmits the second IMS authentication result information generated in H5 to the communication IMS server 10. /F14 to send to the EC server 40 (H7). That is, in this case, the EC server 40 receives the IMS authentication result information directly from the IMS server 10 (this is referred to as "direct callback").

Further, in this case, after receiving the second IMS authentication result information from the IMS server 10, the login management processing unit 413 of the EC server 40 transmits the IMS authentication code included in the received second IMS authentication result information. A reply is sent to the IMS server 10 via the I/F 44 to request the IMS server 10 for IMS user information. Then, the login management processing unit 413 receives the IMS user information transmitted from the IMS server 10 and performs login determination processing (B25 in FIG. 15).

Furthermore, in this case, after the login management processing unit 413 performs the login determination process (B25 in FIG. 15), the login notification (login OK notification/login NG notification) based on the determination result may be directly sent to the terminal 20. Alternatively, a login notification (login OK notification/login NG notification) may be indirectly sent to the terminal 20 via the IMS server 10.

Specifically, after performing login determination processing (B25 in FIG. 15), the login management processing unit 413 sends a login notification (login OK notification/login NG notification) based on the determination result to the IMS via the communication I/F 44. Send to server 10. Then, the IMS user information provision processing unit 113 of the IMS server 10 transmits the login notification received from the EC server 40 via the communication I/F 14 to the terminal 20 via the communication I/F 14.

<Effects of first modification (6)>
In this modification, when the user of the terminal 20 is IMS authenticated by the IMS server 10, the terminal 20 receives the IMS authentication result information from the EC server based on the fact that the EC server 40 receives the IMS authentication result information transmitted from the IMS server 10. 40 shows a configuration in which information indicating whether the login to the terminal 40 is OK or NG (information indicating that the user has been authenticated by the first server) is displayed on the display section 24 (display area) of the terminal 20.
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the user has been authenticated by the first server.

Further, in this modification, the IMS authentication result information is an IMS authentication code indicating that the user of the terminal 20 has been IMS authenticated by IMS, and the terminal 20 sends the IMS authentication code and the login token to the EC server 40. information indicating whether the login to the EC server 40 is OK or NG (information indicating that the user has been authenticated by the first server) is displayed on the display unit 24 (display) of the terminal 20. This shows the configuration displayed in the area).
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the user has been authenticated by the first server. Additionally, since there is no need to send information indicating that the user of the terminal has been authenticated by the second server and association information from the terminal to the first server, the load on the terminal can be reduced as a result. Effects can be obtained.

Furthermore, in this modification, when the EC server 40 determines whether or not the user information is appropriate, the terminal 20 sends the EC server 4 The configuration is shown in which information indicating whether the login is OK or NG (information indicating that the user has been authenticated by the first server) is displayed on the display unit 24 (display area) of the terminal 20.
As an example of the effect of such a configuration, it is possible to notify the user of the terminal that the user has been authenticated by the first server. Furthermore, since there is no need to inquire of the first server about the result of user authentication, the result is that the load on the terminal can be reduced.

Moreover, this modification shows a configuration in which the EC server 40 receives IMS authentication result information transmitted from the IMS server 10 through the communication I/F 44 when the user of the terminal 20 is IMS authenticated by the IMS server 10. There is.
As an example of the effect of such a configuration, the first server can grasp that the user of the terminal has been authenticated by the second server without communicating with the terminal.

Further, in this modification, the IMS authentication result information is an IMS authentication code indicating that the user of the terminal 20 has been IMS authenticated by IMS, and includes an IMS authentication code sent from the IMS server 10 and an IMS authentication code sent from the IMS server 10. A configuration is shown in which the communication I/F 44 receives the login token.
As an example of the effect of such a configuration, the first server can understand that the user of the terminal has been authenticated by the second server without communicating with the terminal, and the first server can understand that the user of the terminal has been authenticated by the second server, and can also provide information specific to the terminal or the user of the terminal. This provides the effect of being able to obtain authentication information.

Moreover, this modification shows a configuration in which the EC server 40 notifies the IMS server 10 through the communication I/F 44 that the EC server 40 has performed login authentication as a login notification.
As an example of the effect of such a configuration, the first server can directly notify the second server that the user has been authenticated without going through the terminal.

<First modification (7)>
In the first embodiment, when the EC server 40 receives IMS user information for login from the IMS server 10, it performs a process of paying a predetermined amount to the operator of the IMS server 10 as compensation for the received IMS user information. It can be done. Further, processing related to setting the amount to be paid to the business operator of the IMS server 10 can be performed.

FIG. 26 is a diagram showing an example of the data structure of the payment management database 455 stored in the storage unit 45 of the EC server 40 in this case.
The payment management database 455 stores payment management data generated for each business operator of the IMS server 10.

Each payment management data stores an IMS operator, IMS user information reception history data, a total number of acquisitions, a total number of new acquisitions, and a payment setting amount.

The IMS operator stores the name of the operator (company name) that provides IMS.
The IMS user information reception history data includes the date and time of receiving IMS user information, the receiving terminal telephone number which is the receiving terminal telephone number, the receiving terminal e-mail address which is the receiving terminal e-mail address, and newly acquired information. The flag is stored in association with the flag. Here, the description will be made assuming that the EC server 40 acquires the IMS user information of one user at a time from the IMS server 10 and stores it in the IMS user information reception history data.

As described in the first embodiment, the EC server 40 stores one of the terminal telephone number and terminal email address received from the IMS server 10 in the login management data 453, but the other information is stored in the login management data 453. If it is not stored in the management data 453, the other information is stored in the login management data 453 to supplement it. The flag indicating whether or not this information has been supplemented is the newly acquired flag, which is set to "ON" when either the terminal phone number or the terminal email address is supplemented, and the information is supplemented. If not, "OFF" is set.

The total number of acquisitions stores the total number of records of data stored in the IMS user information reception history data, with one record of data stored in the IMS user information reception history data being stored as one record. . This total number of acquisitions can also be said to be the number of times the EC server 40 receives IMS user information from the IMS server 10 or the number of times the IMS server 10 transmits IMS user information to the EC server 40.

The total number of new acquisitions stores the total number of new acquisition flags that are set to "ON" in the IMS user information reception history data. This total number of new acquisitions can also be said to be the number of times the EC server 40 receives new IMS user information from the IMS server 10, or the number of times the IMS server 10 transmits new IMS user information to the EC server 40.

The payment setting amount is an amount set as the amount to be paid to the operator of the IMS server 10, and is determined based on the total number of acquisitions and the total number of new acquisitions. As an example and not a limitation, the payment setting amount is set as ``100 yen'' per acquisition and ``50 yen'' per 1 new acquisition, and ``payment setting amount = total number of acquisitions x 100 yen + total number of new acquisitions x 50 yen''. can be calculated and determined.

In addition to the terminal phone number and the terminal email address, the EC server 40 may also collect, by way of example and not limitation, the number of people the user of the terminal 20 has registered as friends in IMS, the number of times the user of the terminal 20 has used IMS, Information such as usage frequency may be received from the IMS server 10 as IMS user information, and the above payment setting amount may be determined based on the type of this IMS user information, or it may not be possible to do so. good. In this case, as an example and not a limitation, if IMS user information of a type other than the terminal phone number or terminal email address is obtained from the IMS server 10, the payment setting amount may be set by adding "50 yen" for each type. All you have to do is calculate it.

In addition, the payment setting amount is determined based on the frequency at which IMS user information is transmitted from the IMS server 10 to the EC server 40, rather than the number of times the IMS user information is transmitted from the IMS server 10 to the EC server 40. This may or may not be the case. In this case, the payment setting amount may be calculated such that the higher the frequency with which IMS user information is transmitted from the IMS server 10 to the EC server 40, the higher the amount.

Furthermore, in the above, the EC server 40 may or may not acquire the IMS user information of two or more users at a time from the IMS server 10 and store it in the IMS user information reception history data. It's okay.

<Effects of first modification (7)>
This modification shows a configuration in which the EC server 40 performs processing related to setting the amount to be paid to the operator of the IMS server 10 based on IMS user information transmitted from the IMS server 10 to the EC server 40.
As an example of the effect of such a configuration, the first server can pay an amount to the operator of the second server as compensation for the acquired user information, and can also set the amount to be paid. It will be done.

Further, in this modification, the process related to setting the amount to be paid is based on the number of times IMS user information is transmitted from the IMS server 10 to the EC server 40, the number of IMS user information transmitted from the IMS server 10 to the EC server 40, Alternatively, the configuration includes processing for determining the amount to be paid to the operator of the IMS server 10 based on the type of IMS user information transmitted from the IMS server 10 to the EC server 40.
As an example of the effect of such a configuration, the first server can optimize the amount paid to the business operator of the second server.

In the above description, the EC server 40 performs the process of paying an amount to the business operator of the IMS server 10 and the process related to setting the amount to be paid to the business operator of the IMS server 10. On the contrary, there is a process in which the IMS server 10 charges the business operator of the EC server 40 to pay an amount in exchange for the IMS user information transmitted to the EC server 40, and an amount to be charged to the business operator of the EC server 40. Processing related to the settings may or may not be performed. "Charging" means imposing payment of an amount on the other party (making the other party accept the amount).

In this case, the number of times (or frequency) of IMS user information sent from the IMS server 10 to the EC server 40, the number of IMS user information sent from the IMS server 10 to the EC server 40, or the IMS The amount to be charged to the operator of the EC server 40 may be determined based on the type of IMS user information transmitted from the server 10 to the EC server 40.

This modification shows a configuration in which the IMS server 10 performs processing related to setting the amount to be charged to the operator of the EC server 40 based on IMS user information transmitted from the IMS server 10 to the EC server 40.
As an example of the effect of such a configuration, the second server can charge the operator of the first server for the provided user information, and can also set the amount to be charged. It will be done.

In addition, in this modification, the processing related to setting the amount to be charged is based on the number of times (or frequency) that IMS user information is transmitted from the IMS server 10 to the EC server 40, and the IMS user information transmitted from the IMS server 10 to the EC server 40. The configuration includes processing for determining the amount to be charged to the operator of the EC server 40 based on the number of IMS users or the type of IMS user information transmitted from the IMS server 10 to the EC server 40.
As an example of the effect of such a configuration, the second server can optimize the amount charged to the business operator of the first server.

<Second embodiment>
The second embodiment is an embodiment accompanying the first embodiment, and is an embodiment related to login when the login code is read by a code reader other than the IMS application code reader in the terminal 20. Note that the same configurations as those in the first embodiment are given the same reference numerals and will not be described again.
The content described in the second embodiment is applicable to any of the other embodiments.

In the first embodiment, the terminal 20 reads the login code using a code reader built into the IMS application. However, if the user reads the login code using a code reader that is included in the terminal 20 from the beginning or a code reader provided by a third party other than the operator of the IMS server 10. is possible. In this case, a problem arises in that the EC server 40 cannot determine from where to obtain the IMS user information necessary for login.

Therefore, if the code reader identified from the information received from the terminal 20 is a code reader other than the IMS application code reader, the control unit 41 of the EC server 40 informs the terminal 20 that the type of IMS cannot be identified. At the same time, a screen (hereinafter referred to as "IMS selection screen for login") for allowing the user to select an IMS (IMS server 10) from which to obtain IMS user information necessary for login is sent to the terminal 20. Display. Then, the control unit 21 of the terminal 20 transmits the identification information of the IMS selected by the user on the login IMS selection screen and the login token identified from the read login code to the EC server 40.

The control unit 41 of the EC server 40 determines the IMS server 10 requesting IMS user information based on the IMS identification information received from the terminal 20. Then, IMS user information is received from the determined IMS server 10, and the PC 50 is logged into the EC site based on the received IMS user information.

<Display screen>
FIG. 27 is a diagram showing an example of a terminal function selection screen displayed on the display unit 24 of the terminal 20.
This function selection screen displays icon images associated with multiple types of functions of the terminal 20, including an icon image of a code reader. This code reader may be a code reader that is included in the terminal 20 from the beginning, or may be a code reader that is acquired from a third party other than the operator of the IMS server 10 and made available for use in the terminal 20. It may also be a code reader.

When the user taps the icon image associated with the code reader on the terminal function selection screen, the code reader of the terminal 20 is activated and a reading standby screen as shown in FIG. 28 is displayed. In this state, the two-dimensional code is read by the code reader by moving the terminal 20 so that the two-dimensional code is included in the frame at the center of the screen.

FIG. 29 is a diagram showing a state where a two-dimensional code is read by the code reader of the terminal 20, and shows a state where a login code displayed on the PC 50 is read by the code reader of the terminal 20.
When the login code displayed on the PC 50 is read by the code reader of the terminal 20 (C7 of login support processing; Yes), code information identification processing is executed (C9 of login support processing), and based on the identified information. , the EC site is accessed from the terminal 20 (C11 of login support processing). In this case, the words "Connecting..." are displayed above the login code.

FIG. 30 is a diagram showing an example of a login IMS selection screen displayed on the display unit 24 of the terminal 20. This IMS selection screen for login is a screen that is sent from the EC server 40 to the terminal 20 and displayed after the display screen of FIG. 29 is displayed.
This IMS selection screen for login displays the message "Please select an IMS for login." and the IMS corresponding to three IMSs: "IMS-X", "IMS-Y", and "IMS-Z". icon is displayed. When one of the IMS icons is tapped by the user, identification information of the IMS corresponding to the tapped IMS icon and a login token are transmitted from the terminal 20 to the EC server 40.

<Effects of the second embodiment>
In the second embodiment, when the type of IMS is not identified by the information related to the code reader that read the login code, the terminal 20 has a configuration in which the display unit 24 displays a selection of the IMS in which the user information is stored. It shows.
An example of the effect of such a configuration is that the user can decide where to obtain user information necessary for user authentication by the first server.

Further, in the second embodiment, if the code reader identified from the information received from the terminal 20 is a code reader of a business that does not store user information necessary for login, the EC server 40 Shows the configuration to receive notifications.
As an example of the effect of such a configuration, the first server can identify a source for acquiring user information necessary for user authentication, and can also acquire user information from the identified source and perform user authentication. This has the effect of being able to.

Furthermore, in the second embodiment, if the type of IMS is not identified by the information related to the code reader that read the login code, the EC server 40 notifies the terminal 20 that the type of IMS cannot be identified. It shows the configuration.
An example of the effect of such a configuration is that the user can select a service for acquiring user information used for user authentication.

<Third embodiment>
The third embodiment is an embodiment accompanying the first embodiment, in which a login code generated by the EC server 40 includes information regarding information provided by the EC server 40, and the login code is read by a code reader. This is an embodiment in which information related to information provided by the EC server 40 is aggregated based on information transmitted from the terminal 20.
The content described in the third embodiment is applicable to any of the other embodiments.

<Functional configuration>
In this embodiment, the control unit 41 of the EC server 40 includes a product information aggregation unit in addition to the functional units shown in FIG.
The product information aggregation unit detects which product category or product page among the EC pages displayed on the PC 50 is used to log in to the EC server 40 (EC site), and performs a process of aggregating the detection results. It has a function.

<Processing>
In the present embodiment, when receiving a login request from the PC 50, the code generation unit 415 of the EC server 40 generates an EC site URL (access information), a login token (association information), and a transmission command (transmission request information). , a QR code containing product category identification information for identifying the category of the product displayed when the PC 50 logs into the EC site (hereinafter referred to as "product category") is generated as a login code.

As an example and not a limitation, on the display screen of the shop page shown in FIG. 16, there are product categories sold on the EC site such as "food items", "daily necessities", "books", etc. , "Grocery tags", "Daily necessities tags", "Book tags", etc. are displayed as tags related to these product categories.

The EC server 40 stores in advance a product category ID for identifying each product category in the storage unit 45 in association with these product categories. Then, when a login request is received from the PC 50 by pressing the "login and purchase procedure button" while the shop page is displayed, the code generation unit 415 of the EC server 40 generates a message that is selected on this shop page. The product category associated with the identified tag is determined, and a login code including the product category ID stored in the storage unit 45 in association with the determined product category is generated.

When a tag related to a product category is selected on a shop page, a page listing products in the product category associated with the selected tag is displayed, so the product category identification information used to identify the product category is , can also be said to be page identification information for identifying a product category page.

FIG. 31 is a diagram showing an example of user-specific product category data 456 stored in the storage unit 45 of the EC server 40 in this embodiment.
The user-specific product category data 456 is data that is generated individually for each user who has logged in to the EC site from the PC 50, and the login ID of the user who has logged in to the EC site from the PC 50 and the product category ID are stored in association with each other. .

When the terminal 20 reads the login code displayed on the PC 50, it accesses the EC site based on the EC site URL included in the read login code, and sends the login token and product category ID to the EC server 40. Send. After logging in the PC 50 to the EC site, the product information aggregation unit of the EC server 40 associates the product category ID received from the terminal 20 with the login ID of the user of the PC 50 and stores it in the user-specific product category data 456. let

FIG. 32 is a diagram showing an example of the data structure of the product category aggregate data 457 stored in the storage unit 45 of the EC server 40 in this embodiment.
In the product category summary data 457, a product category ID, a product category name, and a total number of people are stored in association with each other.

The product information aggregation unit of the EC server 40 associates and stores a product category ID for each product category ID based on user-specific product category data 456 that is generated individually for each user who logs in to the EC site from the PC 50. Collect all login IDs. Then, the total number of logged-in IDs is stored in the product category total data 457 as the total number of people.

<Effects of the third embodiment>
The third embodiment shows a configuration in which the login code includes a product category ID for identifying the product category provided by the EC server 40.
As an example of the effect of such a configuration, the terminal can read code information including information regarding the classification of information provided by the first server using a code reader. Moreover, the first server can transmit code information including information regarding the classification of information provided by the first server to the display device and display the code information.

Further, the third embodiment shows a configuration in which the login code includes at least different information for each product category page for displaying the login code.
As an example of the effect of such a configuration, the terminal can use a code reader to read code information including at least different information for each page classified by information provided by the first server for displaying code information. This effect can be obtained. Furthermore, the first server has the advantage that it can transmit code information including at least different information for each page classified by the information provided by the first server for displaying code information to the display device and display the code information. can get.

Further, the third embodiment shows a configuration in which the EC server 40 performs aggregation regarding categories of products sold by the EC server 40 based on information included in the login code.
As an example of the effect of such a configuration, the first server is able to grasp which category of information the terminal user tends to acquire more of among the information provided by the first server. Effects can be obtained.

<Third modification (1)>
In the third embodiment, a product category ID for identifying each product category is stored in association with each product category, but the present invention is not limited to this. A product ID for identifying each product may or may not be stored in association with each product individually instead of the product category.

In this case, the code generation unit 415 generates a login code including the product ID. After logging the PC 50 into the EC site, the EC server 40 stores the product ID received earlier from the terminal 20 in association with the login ID of the user of the PC 50, and associates the product ID with the login ID of the user of the PC 50. It is only necessary to add up the stored login IDs.

Also, instead of displaying the login code on the login code page, you may display the login code on the page that displays product categories or the page that displays individual products, or you may It's okay. That is, the login code including the product category ID generated by the code generation unit 415 is displayed on the page that displays the product category of the product category ID, or the login code including the product ID generated by the code generation unit 415 is displayed. may or may not be displayed on the page that displays the product with the product ID.

<Effects of third modification (1)>
This modification shows a configuration in which the login code includes a product ID for identifying a product provided by the EC server 40.
As an example of the effect of such a configuration, the terminal can read code information including information regarding information provided by the first server using a code reader. Moreover, the first server can transmit code information including information regarding the information provided by the first server to the display device and display the code information.

Further, in this modification, the login code includes at least different information for each individual product page for displaying the login code or for each individual product page on which the login code is displayed. .
As an example of the effect of such a configuration, the terminal may display each page of information provided by the first server for displaying code information, or the terminal may display each page of information provided by the first server on which code information is displayed. An advantage is obtained that code information including at least different information for each page can be read by a code reader. Further, the first server includes at least different information for each page of information provided by the first server for displaying the code information or for each page of information provided by the first server on which the code information is displayed. This provides the advantage that the code information can be transmitted to the display device and displayed.

Moreover, this modification shows a configuration in which the EC server 40 performs aggregation regarding products sold by the EC server 40 based on information included in the login code.
As an example of the effect of such a configuration, the first server has the effect of being able to grasp which of the information provided by the first server the user of the terminal tends to acquire more of. can get.

<Third modification (2)>
In the third embodiment, it is also possible to aggregate information on websites other than EC sites. The website may be of any kind, but by way of example and not limitation, a server that provides a video site (hereinafter referred to as a "video site providing server") can be used as the first server.

The video site provided by the video site providing server is, by way of example and not limitation, a site that distributes multiple types (or multiple categories) of videos, and allows users to post comments by logging in. It can be a video site. Then, the video site providing server uses a method similar to the method described in the third embodiment to determine which video of the plurality of video types is displayed (which video page is displayed). Detects whether you are logged in to a video site (in a state where the video site is logged in) and aggregates the detection results.

Specifically, the video site providing server generates a login code using the same method as in the above embodiment. At this time, the video site providing server stores in advance a video type ID for identifying each video type in association with the video type. For example, by broad categories such as "anime," "movies," "music," "sports," and "games," or within "sports" such as "soccer," "baseball," "golf," and "basketball." Video type IDs are stored for each category in a narrow sense.

Then, when a login operation is performed while a video site is displayed on the PC 50 and a login request is received from the PC 50, the video site providing server stores the video stored in association with the type of video displayed on the PC 50. Generate a login code that includes the type ID.

When the terminal 20 reads the login code displayed on the PC 50, it accesses the video site based on the video site URL included in the read login code, and sends the login token and video type ID to the video site providing server. Send to. After logging the PC 50 into the video site, the video site providing server stores the video type ID received from the terminal 20 in association with the login ID of the user of the PC 50, and stores this stored data on the multiple terminals 20. The total number of people who logged in to the video site for each type of video is calculated by aggregating the users.

<Effects of third modification (2)>
This modification shows a configuration in which the login code includes a video type ID for identifying the type of video (or video page) provided by the video site providing server.
As an example of the effects of such a configuration, the video site providing server (not limited to this, but an example of the first server) reads the code information from a terminal that has read the code information using a code reader, and analyzes the information by type of video included in the read code information. By receiving identification information and associating it with information related to the user authentication of the device user, we can determine which types of videos the device user tends to view and often log in to video sites. can be grasped.

Note that the first server that performs the same aggregation as described above is not limited to a video site providing server that provides video sites. In addition, by way of example and not limitation, we provide an electronic bulletin board providing server that provides an electronic bulletin board called a so-called BBS (Bulletin Board System), a blog providing server that provides blogs such as personal blogs, and posting sites. The first server in this disclosure is a server that provides websites that users can view, such as a posting site providing server, which requires login for viewing, and the same as above. It is also possible to perform aggregation.

<Fourth embodiment>
The fourth embodiment is an embodiment accompanying the first embodiment, and is an embodiment in which the business operator of the EC server 40 and the user of the terminal 20 register as friends. Note that the same configurations as those in the first embodiment are given the same reference numerals and will not be described again.
The content described in the fourth embodiment is applicable to any of the other embodiments.

<Functional configuration>
In this embodiment, the control unit 11 of the IMS server 10 includes a friend management processing unit in addition to the functional units shown in FIG.
The friend management processing unit has a function of executing processing for managing information regarding other users (hereinafter referred to as "friends") with whom friendships are mutually established in the IMS.

In this embodiment, the storage unit 15 of the IMS server 10 stores a friend management database 157 in addition to the information shown in FIG.

The friend management database 157 is a database in which friend management data used by the friend management processing section of the control section 11 to manage friends is stored, and an example of the data structure is shown in FIG. 33.
The friend management database 157 stores friend management data for each user of a plurality of terminals 20 that use IMS.

Each user's friend management data includes the user's user name, user ID, user icon, which is image data of the icon registered by the user, number of friends, which is the total number of friends of the user, and friend list data. is memorized.

The friend list data is data of a list of users who have become friends with the user, and includes friend user names that are user names of users who have become friends, friend user IDs that are user IDs of users who have become friends, A friend user icon, which is image data of an icon registered by a user who became a friend, and a profile registered by the user who became a friend are stored in association with each other.

Further, in the present embodiment, the business operator (company EEE) of the EC server 40 is registered in the IMS server 10 as an IMS user in advance, and user information regarding the business operator of the EC server 40 is stored in the IMS user data 152. In addition, information for IMS authentication regarding the operator of the EC server 40 is stored in the IMS authentication management data 153.

<Processing>
In this embodiment, in step B29 of the login management process executed by the login management processing unit 413 of the EC server 40 in the first embodiment, a login OK notification is sent to the IMS server 10 in addition to the terminal 20 and the PC 50. do.

In the IMS server 10, upon receiving the login OK notification from the EC server 40, the friend management processing unit of the control unit 11 displays a friend registration confirmation screen for confirming whether or not to register as friends with the business operator of the EC server 40. It is transmitted to the terminal 20 via the communication I/F 14.

When the login support processing unit 213 of the terminal 20 receives the friend registration confirmation screen from the IMS server 10 through the communication I/F 22, it displays the friend registration confirmation screen within the running IMS application. Then, in the friend registration confirmation screen, if the user is permitted to register the business operator of the EC server 40 as a friend, the login support processing unit 213 registers the business operator of the EC server 40 as a friend through the communication I/F 22. A friend registration request requesting the same is sent to the IMS server 10 via the communication I/F 22.

When the IMS server 10 receives a friend registration request from the terminal 20 through the communication I/F 14, the friend management processing section of the control section 11 performs friend registration processing. Specifically, the user name, user ID, and user ID stored in the IMS user data 152 of the storage unit 15 in association with the IMS user information (terminal telephone number, terminal email address) received in step B23 of the IMS user information providing process; Store user icons and profiles in friend management data. In addition, the user ID, user icon, and profile included in the user information of the business operator of the EC server 40 stored in the IMS user data 152 are replaced with the friend user name, friend user ID, friend user icon, and friend profile, respectively. This is stored in the friend list data included in the above friend management data.

<Display screen>
FIG. 34 is a diagram showing an example of a friend registration confirmation screen displayed on the display unit 24 of the terminal 20 in this embodiment.
This friend registration confirmation screen is an example of a friend registration confirmation screen displayed within the "IMS-Y" application, and includes the message "Add friend" as well as the name ( ``EC site EEE'', which is the name of the EC site, and an image of a user icon registered by the business operator of the EC server 40 are displayed. Furthermore, below that, an "add icon" for adding the business operator of the EC server 40 as a friend is displayed. When this additional icon is tapped by the user of the terminal 20, the business operator of the EC server 40 is registered as a friend.

FIG. 35 is a diagram showing an example of a friend list screen displayed on the display unit 24 of the terminal 20 in this embodiment.
This friend list screen is an example of a friend list screen displayed within the "IMS-Y" application, and a profile is displayed in association with the user name "A.A" of the user of the terminal 20 at the top of the screen. There is. Further, below that, an image of the user icon of "EC site EEE" with a mark of "N (New)" indicating new is displayed as a "new official account."

<Effects of the fourth embodiment>
In the fourth embodiment, based on the terminal 20 reading the login code displayed on the PC 50 using an IMS application code reader, the IMS server 10 obtains the user ID related to the operator of the EC server 40 and the user ID of the terminal 20. A configuration is shown in which the user ID related to the user is associated as a friend. Further, in the terminal 20, information regarding friend registration between the business operator of the EC server 40 and the user of the terminal 20 is displayed on the display unit 24.
As an example of the effect of such a configuration, the terminal may store information regarding the operator of the first server and information regarding the operator of the second server of the service that manages user information used for user authentication in the first server. This has the advantage that the user of the terminal can be notified that the two have been associated.

<Fourth variation>
In the fourth embodiment, the user is allowed to select an IMS that becomes friends with the business operator of the EC server 40. Specifically, in the terminal 20, by way of example and not limitation, when receiving a login OK notification from the EC server 40, the control unit 21 displays a screen for selecting an IMS to become friends with the operator of the EC server 40 ( A "friend registration IMS selection screen" (hereinafter referred to as "friend registration IMS selection screen") is displayed on the display unit 24 to allow the user to select an IMS to be friends with the business operator of the EC server 40. Then, the control unit 21 transmits a friend registration request requesting to register the business operator of the EC server 40 as a friend to the IMS server 10 of the IMS selected by the user.

In this case, the order (priority order) of the IMS icons to be displayed on the IMS selection screen for friend registration based on which IMS application code reader was used to read the login code and log in to the EC server 40 on the terminal 20. can be changed. Specifically, the control unit 21 of the terminal 20 stores in the storage unit 28, by way of example and not limitation, history information of IMS application code readers that have read login codes in the past. Preferably, the control unit 21 displays the IMS icon at a higher position, based on the history information stored in the storage unit 28, for IMSs that have been used for login more often or more frequently.

Note that, contrary to the above, the IMS icon may be displayed at a higher position for an IMS that has been used for login less often or less frequently, or it may not be necessary to do so.

In addition, the EC server 40 targets the terminals 20 of multiple users, and identifies the IMS of the code reader from which the login code has been read based on the information sent from each terminal 20, and aggregates this information. , statistically analyze which IMS tends to be used to log in more often. Then, the results of this aggregation and analysis may be sent from the EC server 40 to each user's terminal 20 to change the order (priority order) of the IMS icons displayed on the IMS selection screen for friend registration. But it doesn't have to be that way.

FIG. 36 is a diagram showing an example of the friend registration IMS selection screen displayed on the display unit 24 of the terminal 20 in this modification.
This IMS selection screen for friend registration displays the message "Please select the IMS you want to register as a friend." and supports three IMSs: "IMS-X,""IMS-Y," and "IMS-Z." IMS icons are displayed vertically. When any IMS icon is tapped by the user, a friend registration request requesting to register the business operator of the EC server 40 as a friend is sent to the IMS server 10 of the IMS corresponding to the tapped IMS icon.

What is distinctive is that these three IMS icons are not displayed in the order of "IMS-X", "IMS-Y", and "IMS-Z" from the top, but in the order of "IMS-Y" from the top. ”, “IMS-X”, and “IMS-Z”. This means that the login code that was read the most was "IMS-Y," the next most read code was "IMS-X," and the least read code was "IMS-Z." This is because it was.

Up to this point, we have explained that friend registration is performed using "IMS," but as mentioned above, IMS can also be said to be one form of SNS, so the above method is considered as SNS rather than IMS. You may also register as a friend.

<Effects of the fourth modification>
This modification shows a configuration in which a screen is displayed on the display unit 24 of the terminal 20 that allows the user to select an IMS with which the operator of the EC server 40 becomes friends based on information related to the code reader that read the login code. ing.
As an example of the effect of such a configuration, the user of the terminal can select the operator of the second server to be associated with the operator of the first server.

Further, this modification shows a configuration in which the order (priority order) of IMSs to be displayed is changed based on an IMS application code reader that reads a login code displayed on the PC 50.
As an example of the effect of such a configuration, it is possible to preferentially display services that are frequently used by the user on the terminal, and it is possible to improve convenience for the user.

<Fifth embodiment>
The fifth embodiment is an embodiment accompanying the first embodiment, in which advertisements regarding the business operators of the EC server 40 (or advertisements regarding EC) and advertisements regarding the business operators of the IMS server 10 (or advertisements regarding IMS) are sent to terminals. In this embodiment, the information is displayed on a display area of 20 or a website provided by an EC server 40. With these combinations, four advertisement display patterns (display methods) can be considered.
The content described in the fifth embodiment is applicable to any of the other embodiments.

(A) Pattern for displaying an advertisement regarding an EC server operator (or an advertisement regarding EC) in the display area of the terminal As described above, the terminal 20 reads the login code using the code reader started from the IMS application 283. Based on this, the EC site is accessed (C11). As a result, the storage unit 28 of the terminal 20 stores an access history file including the URL of the EC site identified from the read login code.

On the other hand, the storage unit 15 of the IMS server 10 stores advertisement data associated with each company serving as an advertiser for each URL of that company. When the IMS application program 2831 is executed on the terminal 20, the control unit 21 refers to the access history file and sends the advertisement confirmation information including the URL (URL of the EC site) included in the access history file to the IMS server 10. Send to. The advertisement confirmation information is information for acquiring advertisement data of a business operator corresponding to the URL included in the access history from the IMS server 10.

The IMS server 10 selects a business operator that matches the URL included in the advertisement confirmation information based on the URL included in the received advertisement confirmation information (that is, the URL included in the access history of the terminal 20) and the URL of each business operator. identify. The advertisement data associated with the identified business operator is then transmitted to the terminal 20, which is the source of the advertisement confirmation information, in a format that can be displayed by the company's IMS application 283.

Upon receiving the advertising data transmitted from the IMS server 10, the terminal 20 displays an advertising image (also referred to as an advertising image) based on the received advertising data on the advertising page of the IMS application 283. .

FIG. 37 shows how the terminal 20 reads the login code for logging into the EC site EEE using the IMS-Y code reader, based on the fact that the terminal 20 is running the IMS-Y application. An example is shown in which an advertisement image of the EC site EEE is displayed on the advertisement page of IMS-Y displayed on the display unit 24. In this example, an image of an advertisement regarding the summer sale of the EC site EEE is displayed as the advertisement image of the EC site EEE.

(B) Pattern of displaying advertisements related to IMS server operators (or advertisements related to IMS) on a website provided by the EC server In addition, the EC server 40 displays the IMS associated with the code reader whose login code has been read. By identifying, advertisements related to the business of the identified IMS server 10 and advertisements related to IMS can be displayed on the company's EC site, for example.

FIG. 38 shows an example in which the EC server 40 displays an advertisement regarding IMS-Y on its own EC site when it identifies that the login code has been read by the code reader of IMS-Y. In this example, the IMS- An advertisement is being displayed announcing that a new function has been added to the IMS talk room function provided by Y.

(C) Pattern for displaying advertisements related to IMS server operators (advertisements related to IMS) in the display area of terminals In Figure 37, login is performed as an advertisement related to IMS associated with the code reader whose login code has been read. Although an example has been shown in which an advertisement regarding a business operator of the EC server 40 that provides an EC site (EC-related advertisement) is displayed on the advertisement page of the IMS, the present invention is not limited to this.
By way of example and not limitation, an advertisement regarding IMS associated with the code reader from which the login code was read, for example, the advertisement shown in FIG. 38, may be displayed on the IMS advertisement page on the display unit 24 of the terminal 20. .

(D) Aggregation related to advertisement display In addition, the EC server 40 calculates, for each IMS, the number of times a user logs in to the EC site using a code reader associated with that IMS, that is, a code reader started from that IMS application. It is possible to aggregate the

FIG. 39 is a diagram showing an example of the data structure of the login statistical data 458 stored in the storage unit 45 of the EC server 40 in this embodiment.
The login statistical data 458 includes the IMS type for identifying the IMS operator, the number of logins that are the number of logins based on the login code being read by a code reader corresponding to the IMS type, and A login ratio, which is the ratio of the number of logins to the total number of logins to the EC site, a ranking determined based on the login ratio, and an advertising ratio calculated based on the login ratio are stored in association with each other.

In the example shown in FIG. 39, the EC server 40 is configured to display advertisements of IMS operators only on the company's EC site for the top three IMS operators (X, Y, Z) with high login ratios. is being done. Therefore, the total advertising ratio of the top three companies is 100%. The EC server 40 displays advertisement images of each IMS operator on its own EC site based on the advertisement ratio. Advertisement images of each IMS operator are obtained in advance from the IMS server 10 and stored in the storage unit 45.

Furthermore, in the example shown in FIG. 39, the number of logins performed using the code reader of Company X, which is an IMS operator, is the largest. Since the ratio of the number of logins of company X to the total number of logins of the top three companies is 44%, the EC server 40 displays advertisements regarding company X on its own EC site at a ratio of 44%. For example, if a user logs in to his company's EC site 100 times, 44 of those times an advertisement regarding Company X will be displayed on his company's EC site.

<Effects of the fifth embodiment>
The advertisement image shown in FIG. 37 is displayed on the advertisement page of the IMS as an advertisement provided by the IMS associated with the code reader whose login code has been read. This advertisement image is an advertisement image related to the EC server operator (an advertisement image related to EC), but can also be said to be an advertisement image related to the IMS associated with the code reader.

In this manner, the fifth embodiment uses the IMS associated with the code reader from which the login code has been read to display an advertisement regarding the business operator of the EC server 40 (an advertisement regarding EC) on the display unit 24 of the terminal 20. This shows the configuration to be displayed.
As an example of the effect of such a configuration, the advertisement displayed in the display area of the terminal is an advertisement provided by a service associated with the code reader. The effect is that the chances of viewing advertisements regarding the services of the two servers can be increased.

The EC server 40 also receives from the terminal 20 information associated with the IMS application that activated the code reader as information related to the code reader that read the login code. Then, as shown in FIG. 38, an advertisement related to the IMS identified based on the information related to the code reader is displayed on the EC site.

In this way, in the fifth embodiment, when the EC server 40 identifies the IMS associated with the code reader from which the login code has been read, the operator of the IMS server 10 uses the identified IMS. A configuration is shown in which an advertisement related to IMS (an advertisement related to IMS) is displayed on a website provided by the EC server 40.
As an example of the effect of such a configuration, the advertisement displayed on the website provided by the first server is an advertisement regarding the service associated with the code reader, so that the viewers of the website provided by the first server , it is possible to increase the chances of viewing advertisements regarding the services of the second server.

Further, the fifth embodiment shows a configuration in which an advertisement related to IMS associated with a code reader whose login code has been read is displayed on an IMS advertisement page on the display unit 24 of the terminal 20.
As an example of the effect of such a configuration, since the advertisement displayed in the display area of the terminal is about a service associated with the code reader, the terminal user has no opportunity to see an advertisement about the service of the second server. The effect is that it can be increased.

The EC server 40 also receives information related to the code reader that read the login code from the terminal 20 that read the login code, and identifies the IMS based on the received information. Then, as shown in FIG. 39, for each IMS, the number of times it is associated with information related to the code reader, that is, the number of times that IMS is used for login is counted. As a result, for each IMS, the number of times advertisements related to that IMS are displayed on the EC site differs based on the number of times that IMS is used for login.

In this way, in the fifth embodiment, the EC server 40 identifies the IMS associated with the code reader from which the login code has been read. This shows a configuration for determining the number of times advertisements are displayed on the company's EC site.
As an example of the effect of such a configuration, advertisements related to IMS that are frequently used by terminal users for user authentication of the first server, that is, advertisements related to services of the second server that are highly important to the operator of the EC server 40, , it is possible to obtain the effect that it can be displayed with high frequency.

<Fifth modification (1)>
(E) Pattern for displaying advertisements related to EC server operators (EC-related advertisements) on websites provided by EC servers In addition to the advertisement display patterns (A) to (C) described in the fifth embodiment, It is also possible to display an advertisement regarding the business operator of the EC server 40 (an advertisement regarding EC) on a website provided by the EC server 40.
In this case, by way of example and not limitation, the advertisement image shown in FIG. 37 can be displayed on the EC site shown in FIG. 38.

<Effects of fifth modification (1)>
This modification shows a configuration in which an advertisement regarding a business operator of the EC server 40 (an advertisement regarding EC) is displayed on a website provided by the EC server 40.
An example of the effect of such a configuration is that viewers of the website provided by the first server can increase their chances of viewing advertisements regarding the services of the first server.

<Fifth modification (2)>
In the fifth embodiment, an example was shown in which advertisement confirmation information based on the access history file stored in the terminal 20 is transmitted to the IMS server 10 in order to display an advertisement on the terminal 20. Advertisements may be displayed.

As described above, the EC server 40 determines which IMS code reader the login code is based on having received from the terminal 20 information related to the code reader that read the login code displayed on the PC 50. It is possible to identify whether it has been read.

By way of example and not limitation, the EC server 40 displays the company's EC site on the display unit 24 of the terminal 20 based on the fact that the IMS application of the identified IMS has been executed on the terminal 20 from which the login code has been read. You can display advertisements related to

Specifically, the EC server 40 uses the terminal phone of the terminal 20 from which the login code has been read based on the EC user information stored in the storage unit 45 or the IMS user information acquired from the IMS server 10. Identify a number or device email address. The EC server 40 transmits advertisement request information to the IMS server 10 to cause the terminal 20 having the identified terminal telephone number or terminal email address to transmit advertisement data of the company's EC site. The advertisement request information includes information specifying the business entity that is the advertisement requester, and the identified terminal telephone number or terminal e-mail address.

The IMS server 10 that received the advertisement request information identifies and identifies the advertisement data associated with the business operator specified by the advertisement request information from the advertisement data of each business operator stored in advance in the storage unit 15. The advertisement data is sent to the terminal 20 of the terminal telephone number or terminal e-mail address included in the advertisement request information in a format that can be displayed by the company's IMS application.

The terminal 20 that has received the advertisement data from the IMS server 10 displays the received advertisement on the IMS advertisement page based on the execution of the IMS application of the IMS server 10 (IMS operator) that is the source of the advertisement data. Display advertising images based on data.

<Effects of fifth modification (2)>
This modification shows a configuration in which the access history to the EC site does not need to be stored in the terminal 20 in order to display the advertisement of the EC site on the terminal 20.
As an example of the effect of such a configuration, an advertisement of the website of the first server can be displayed in the display area of the terminal based on the communication between the first server and the second server. In addition, the terminal does not need to remember the access history of the e-commerce site or send advertisement confirmation information based on the access history file to the second server, which ultimately reduces the load on the terminal. Effects can be obtained.

<Fifth modification (3)>
Although FIG. 37 shows an example in which an advertisement provided by the IMS associated with the code reader that read the login code is displayed on the advertisement page of the IMS, the display form of the advertisement on the terminal 20 is as follows. It is not limited to this. By way of example and not limitation, based on the fact that the operator of the EC server 40 and the user of the terminal 20 are registered as friends by the IMS server 10 of the IMS associated with the code reader that read the login code, the IMS The server 10 may display an advertisement regarding the EC server 40 operator in a talk room between the EC server 40 operator and the user of the terminal 20.

<Effects of fifth modification (3)>
This modification shows a configuration in which an advertisement is displayed using the function of the IMS talk room used for login.
As an example of the effect of such a configuration, an effect can be obtained in that the terminal user can increase the chances of viewing advertisements related to the business operator of the first server.

<Fifth modification (4)>
Although FIG. 39 shows an example in which the EC server 40 determines, for each operator of the IMS server 10, the number of times advertisements related to the IMS are to be displayed on the EC site, the present invention is not limited to this. For each business operator of the IMS server 10, the number of times advertisements for the EC site are displayed on the user's terminal 20 using the IMS operated by that business operator may be determined.

For example, regarding FIG. 39, the number of logins for X, Y, and Z account for 44%, 33%, and 23%, respectively, of the total number of logins for the top three companies. Based on this aggregation result, the EC server 40 sends 44% of the advertisements to X's IMS advertising page (44 times if advertisements are sent 100 times a day), and Y's IMS advertising page 33% (also 33 times) and 23% (also 23 times) on Z's IMS advertising page.

<Effects of fifth modification (4)>
This modification shows a configuration in which advertisements regarding the company's EC site are frequently displayed on an IMS advertisement page that is frequently used by users for login.
An example of the effect of such a configuration is that the more frequently the service of the second server is used for user authentication by the first server, the more frequently advertisements related to the business of the first server can be displayed with priority. can get.

<Others>
Although the embodiments of the present disclosure have been described based on the drawings and examples, it should be noted that those skilled in the art can easily make various changes and modifications based on the present disclosure. Therefore, it should be noted that these variations and modifications are included within the scope of the present disclosure. As an example and not a limitation, the functions included in each means, each step, etc. can be rearranged so as not to be logically contradictory, and multiple means, steps, etc. may be combined into one or divided into one. is possible. Further, the configurations shown in each embodiment may be combined as appropriate.

1 Communication system 10 IMS server 20 Terminal 30 Network 40 EC server 50 PC

Claims (16)

A program executed by a terminal communicating with the first server,
performing a process of reading code information displayed on a display device for accessing the first server with a code reader of the terminal, by a control unit of the terminal;
performing a process of accessing the first server by the control unit based on reading of the code information;
receiving, by a communication unit of the terminal, authentication request information requesting authentication of a user of the terminal based on the process of accessing the first server;
Based on the authentication request information, the communication unit communicates with a second server that manages user information related to the code reader that has read the code information, and controls the processing related to authentication of the user of the terminal. The operations performed by the terminal are performed by the terminal. The program according to claim 1,
Based on a process related to authentication of a user of the terminal with the second server, receiving information provided by the first server by the communication unit is performed by the terminal. The program according to claim 1 or claim 2,
provided by the first server based on information related to the user information being received by the first server based on a process regarding authentication of the user of the terminal with the second server; The terminal displays information indicating that the user has been authenticated, which enables the user to obtain information on the display unit of the terminal. The program according to any one of claims 1 to 3,
The code information includes information for communicating with the first server. The program according to any one of claims 1 to 4,
The code information includes association information for associating the terminal with the display device or associating the user of the terminal with the display device. 6. The program according to claim 5,
When the user of the terminal is authenticated by the second server that manages the user information, receiving information related to the user information from the second server by the communication unit;
Sending information related to the user information to the first server by the communication unit is performed by the terminal. 7. The program according to claim 6,
The information related to the user information is information indicating that the user of the terminal has been authenticated by the second server,
The terminal transmits information indicating that the user of the terminal has been authenticated and the association information to the first server by the communication unit. 6. The program according to claim 5,
If the user of the terminal is authenticated by the second server, based on the first server receiving information related to the user information transmitted from the second server, by the first server: Displaying information on a display unit of the terminal indicating that the user has been authenticated to enable acquisition of the information provided by the first server is executed by the terminal. 9. The program according to claim 8,
The information related to the user information is information indicating that the user of the terminal has been authenticated by the second server,
information indicating that the user of the terminal has been authenticated based on the information indicating that the user of the terminal has been authenticated transmitted from the second server and the association information being received by the first server; Displaying on the display unit is executed by the terminal. The program according to claim 8 or 9,
If the user has been authenticated by the first server, information indicating that the user has been authenticated based on the communication unit receiving information indicating that the user has been authenticated transmitted from the second server. is executed by the terminal to display on the display unit. The program according to any one of claims 1 to 10,
The code information includes information regarding information provided by the first server. The program according to any one of claims 1 to 11,
The terminal may display, on a display unit of the terminal, information regarding association between information regarding the operator of the first server and information regarding the user of the terminal based on reading the code information with the code reader. executed by The program according to any one of claims 1 to 12,
Displaying an advertisement regarding a service of the second server associated with the code reader on a display unit of the terminal is executed by the terminal. The program according to any one of claims 1 to 13,
The code information is information for logging into the first server in order to obtain information provided by the first server. An information processing method of a terminal communicating with a first server, the method comprising:
performing a process of reading code information displayed on a display device for accessing the first server with a code reader of the terminal, by a control unit of the terminal;
performing a process of accessing the first server by the control unit based on reading of the code information;
receiving, by a communication unit of the terminal, authentication request information requesting authentication of a user of the terminal based on the process of accessing the first server;
Based on the authentication request information, the communication unit communicates with a second server that manages user information related to the code reader that has read the code information, and controls the processing related to authentication of the user of the terminal. including what is done by the department. A terminal communicating with a first server,
Control to perform processing of reading code information displayed on a display device for accessing the first server with a code reader of the terminal, and processing of accessing the first server based on reading of the code information. Department and
a communication unit that receives authentication request information requesting authentication of the user of the terminal based on the process of accessing the first server;
The control unit communicates with a second server that manages user information related to the code reader that has read the code information based on the authentication request information, and authenticates the user of the terminal. Perform related processing.

Images