JP5148961B2 - User authentication mechanism - Google Patents

Description

  The present invention relates to an authentication mechanism for permitting browsing only with respect to a browsing request for a specific web page from a user's mobile terminal registered in advance.

  The authentication mechanism according to the present invention is used, for example, for authentication for permitting browsing of member-specific web pages in a mailing list service.

  The mailing list service was originally started as a service provided by a system for sending and receiving e-mail between computers, and a plurality of e-mail addresses (mailing list accounts, hereinafter referred to as “ML accounts”) are assigned to a plurality of e-mails. List the user's personal email addresses in association with each other, and forward the email addressed to the ML account from any of the listed personal email addresses to all the personal email addresses listed Service. Here, an individual whose personal address is listed in any ML account is referred to as a “member” of a “mailing list (ML)” marked by the ML account. A member registered in any mailing list is referred to as a “user” of the mailing list service.

  In such a mailing list service, for each individual mailing list, the contents (text) of emails sent and received in the past are stored, and the contents are responded (viewed) every time a browsing request is made by each member. There are many web pages. In a conventional system for providing a mailing list service between personal computers, when a member of the mailing list requests access to a web page dedicated to each mailing list, the ID of the member registered in advance with respect to the mailing list. And prompting for the input and transmission of the password, and authenticating that the member is truly a member of the mailing list based on the combination of the ID and password transmitted from the personal computer operated by the member, Access (viewing) to the web page was permitted.

  In recent years, with the improvement of the network access function of mobile phones, provision of mailing list services including the use of the above-described web pages has become common in systems that send and receive e-mail between mobile phones. Compared to the SMTP protocol and POP protocol used for sending and receiving e-mails between personal computers, sending and receiving e-mails between mobile phones are carried out by the original protocol of each communication company, and the mail server receives e-mails. Then, the e-mail is immediately transferred directly to the destination mobile phone (that is, the mobile phone having a terminal ID previously associated with the destination address of the e-mail). For this reason, in the mailing list service, e-mail is transferred according to the original protocol. Therefore, in order to prevent the deterioration of the response due to the increase in traffic and the increase in the communication fee due to the increase in the number of packets, the mailing list service is provided. In general, the system that controls the device deletes an attached file (for example, an image file) having a large file size from the electronic mail received from the member and transfers it. In this way, files deleted from individual emails are published on the web page dedicated to the mailing list, so that each member who receives the email can browse by accessing the web page individually. It is configured.

  Therefore, in the mailing list service between mobile phones, it is almost essential to publish the attached file on a web page dedicated to each mailing list. To be able to access the page, an authentication mechanism is required that can quickly authenticate whether the access source mobile phone is operated by a member of the mailing list.

  Therefore, in the conventional mailing list service between mobile phones, the terminal ID uniquely possessed by each mobile phone is registered in association with the email addresses of the members listed in each mailing list. When an access request is made from any mobile phone to a web page dedicated to any mailing list, the terminal ID of the mobile phone is extracted from the header of the access request message (adopted by the communication company). Depending on the protocol, the terminal ID may not be included in the header, or if the header does not include the terminal ID, a request for transmitting the terminal ID is made to the message source mobile phone again. ) If the terminal ID is registered for the mailing list, It is determined that the request, responds with the screen data (allow the viewing of attachments that have been published on the web page) authentication mechanism, had been adopted many.

  However, when an authentication mechanism that uses the terminal ID of the mobile phone as personal identification information is adopted, if the member changes the mobile phone (so-called model change), the member can send e-mail based on the mailing list even if the mobile phone is replaced. Even if it is possible to send and receive, the web page dedicated to the mailing list cannot be accessed. In this case, if the application for changing the registered terminal ID is filed by reporting the fact that the mobile phone model has been changed online or offline to the service provider providing the mailing list service, The mailing list-dedicated page can be accessed again by telephone, but it is cumbersome if the service recipients who are members must take the initiative to do so, and the declaration procedure is complicated and requires manual labor. If intervening, the response of the change of the terminal ID deteriorates and stresses the service recipient, and in any case, it causes the service utilization rate to deteriorate.

  It should be noted that the authentication for permitting access to such a dedicated web page is not unique to the mailing list service, but can be applied to any service that allows the mobile phone to browse the dedicated web page, so this problem is also unique to the mailing list service. is not.

  In addition, since this service can be provided not only for mobile phones having a call function, but also for communication cards and PDAs (Personal Digital Assistance) without the call function, such a problem is not unique to the mobile phone, and such authentication is also required. This can occur in any portable terminal that can adopt the method.

  Therefore, the problem of the present invention is that a user who has previously registered the terminal ID and e-mail address of the mobile terminal in a service capable of browsing a specific web page changes the mobile terminal and then requests browsing of the web page. Provides an authentication mechanism that allows the user to identify that the mobile terminal is operated by the user only by asking the user for a simple operation through the mobile terminal, and to permit browsing of the web page. To do.

  The authentication mechanism according to the present invention devised to solve the above-described problems is predetermined from a plurality of portable terminals each having a unique terminal ID and an electronic mail address and having an Internet browsing function and an electronic mail transmission / reception function. Is a user authentication mechanism for authenticating a user who operates the mobile terminal in order to respond to the screen data of the web page when a web page browsing request is received, and for each user, the user Upon receipt of the storage device recording the terminal ID and the e-mail address of the portable terminal and the web page browsing request message transmitted from any portable terminal, the terminal ID is acquired from the portable terminal. Terminal ID acquisition means, and the terminal ID acquired by the terminal ID acquisition means is stored in the storage device. If it is recorded, the screen data of the web page is responded, and if the terminal ID is not registered in the storage device, the mobile terminal is requested to send an e-mail, and the request An authentication unit that responds to the screen data of the web page only when the e-mail transmitted by the portable terminal is received in response to the e-mail transmission source address registered in the storage device. It is characterized by.

  If comprised in this way, if the user who has registered the terminal ID and e-mail address of his / her mobile terminal in the storage device has not changed the mobile terminal after registration, the authentication means will acquire the terminal ID. Since it is determined that the terminal ID acquired by the means is stored in the storage device, the screen data of the web page requested to be browsed is returned as it is. On the other hand, when the user changes the portable terminal after registration, the authentication unit determines that the terminal ID acquired by the terminal ID acquisition unit is not stored in the storage device. The mobile terminal is requested to send an e-mail, and in response to this, it is checked whether the source address of the e-mail sent by the portable terminal is registered in the storage device. If it is registered in the storage device, it can be judged as a browsing request from the registered user, and screen data can be returned. As described above, according to the present invention, even when the user changes the portable terminal, the user can be authenticated only by sending an e-mail to the authentication mechanism in response to a request from the authentication mechanism. .

1. Hereinafter, an embodiment of a computer network including a system for providing a mailing list service between mobile phones adopting an authentication mechanism according to the present invention will be described with reference to the drawings. In the following embodiments, assuming that the service provider that provides the mailing list service is a different person (separate corporation) from the carrier that operates the mobile phone Internet network, the host computer that manages the service is connected to the mobile Internet network. However, the above-mentioned service provider may be the same person (same corporation) as the telecommunications carrier, in which case the host computer that manages the service is placed inside the mobile Internet network. Is done.
2. System Configuration FIG. 1 is a block diagram showing a schematic configuration of a computer network according to an embodiment of the present invention. As shown in FIG. 1, this computer network is a service host computer 1, which is a part of various servers existing on a network L operated by each ISP (Internet Service Provider), and authentication. Host computers 2 and routers 4, Internet networks (primary providers, backbones, secondary providers, portable Internet networks made up of a number of ground stations and switching offices) N, and a plurality operated by respective communication companies Mobile Internet network (communication network comprising a number of ground stations, a plurality of switching stations wired to each ground station and wiredly connected to each other in a hierarchical structure, a gateway to the Internet N, etc.) M and The mobile Internet network M is wirelessly connected to any of the ground stations and the mobile Internet It is composed of a large number of mobile phones (only two units are shown in FIG. 1) 6 and 6 'that can access the host computers 1 and 2 through the Internet network M, the Internet N, and the router 4.

  1 has a normal configuration (i.e., an external memory for storing a program, a processing device for executing the program, and a main memory in which a work area when the processing device executes the program is developed). , A keyboard for the user to input data, a display for displaying the processing result of the processing device on the screen, a wireless device for exchanging packets with the ground stations constituting the mobile Internet network M, a digital camera, etc. Mobile phone with Internet connection function. The program stored in the external memory of the mobile phone 6 and executed by the processing device includes screen data of a web page (screen) with respect to a server for content provision (including the host computer 1) existing on the Internet N. Requests data of various contents, analyzes various received data upon request, generates a browser program that displays web pages (screens) and various contents on the display, and generates e-mails according to user operations A mailer program is also included that displays the content of an e-mail that is transmitted to or received from the mobile Internet network M on the display. Since the functions of these browser programs and mailer programs are publicly known, detailed description thereof will be omitted.

  The mobile phones 6 and 6 ′ include members (hereinafter referred to as “members”) who have become members who receive various services (content providing services, etc.) provided by the ISP by making a contract with the ISP. Some are owned or rented, but others are owned or rented by members other than members. In other words, the mailing list service provided by the system has the mailing list opening authority limited to members only, but it is possible to register persons other than members on the mailing list once opened, and it is also provided to those other than members. It is a service.

  The service host computer 1 is actually a plurality of server devices existing on a network operated by the ISP. Such server devices include those that provide email services, those that provide content providing services to members, those that provide member management services, and billing the provided services to members. Things to do are included. However, here, in order to simplify the description, it is assumed that these service host programs are executed on one service host computer 1.

  The service host computer 1 includes a CPU 10, a communication adapter 11, a memory 12, and a hard disk 13 connected to each other by a bus B. Among these, the CPU 10 is a central processing unit (computer) that controls the entire service host computer 1. The memory 12 is a main storage device in which a work area is expanded when the CPU 10 executes various processes. The communication adapter 11 is an interface with a network (LAN) in the ISP, is connected to a dedicated line connected to the Internet N through the router 4, and is connected to another host computer 2 in the ISP.

  The hard disk 13 is a storage device that stores various programs and various data that are read and executed by the CPU 20.

  The various programs stored in the hard disk 13 include programs for performing the various functions described above (for example, the WWW server program 14 and various services for providing various services in cooperation with the WWW server program. The host program 15 receives an e-mail transferred from a mail server of a telecommunications company constituting each mobile phone Internet network M, or sends an e-mail based on the mailing list service to the mailing list through the mail server of each telecommunications company. A mail server program 16) for transmitting to a registered mobile phone or generating an e-mail by itself and transmitting it to a destination mobile phone is included. The processing contents of these programs 14 to 16 will be described in detail later with reference to the flowcharts of FIGS.

  The various data stored in the hard disk 13 is read by the CPU 10 executing the WWW server program 14 or each service host program 15 and is processed as it is or appropriately processed to each mobile phone 6. A large number of screen data 17 to be transmitted (refer to the screen examples in FIGS. 22 to 41), and a large number of tables 18 to be referred to by each service host program 15 and information appropriately registered (the data in FIGS. 3 to 10). This includes emails received by the mail server 16, especially emails received based on the mailing list service and their attachments.

  The data structure of each screen data 17 and each table 18 will be described in detail later together with the processing contents executed by the CPU 10 based on the WWW server program 14 and each service host program 15.

  In the hard disk 13, the e-mail is stored in the ML accommodating directory 19 which is a dedicated storage area. This ML accommodation directory is logically divided into a plurality of subdirectories, so that it has a tree-like hierarchical structure. The subdirectories of each layer are classified by whether or not the email is based on the mailing list service, a mailing list number, a posting number (a number for identifying each email in each mailing list), and the like. . A text file and an attached file of the corresponding electronic mail are accommodated in the terminal subdirectory. Therefore, in the ML accommodating directory 19, the text of the target e-mail is obtained by following the path (tree branch) according to whether the e-mail is based on the mailing list service, the mailing list number, the posting number, etc. You can access files and attachments.

  The authentication host computer 2 determines whether the person who operates the access source mobile phone 6 based on the request from the service host computer 1 is a member registered in advance as a recipient of the service in the ISP. A host computer that executes an authentication service for authenticating

  Similar to the service host computer 1, the authentication host computer 2 also includes a CPU 20, a communication adapter 21, a memory 22, and a hard disk 23 connected to each other via a bus B. Among these, the CPU 20 is a central processing unit (computer) that controls the entire authentication host computer 2. The memory 22 is a main storage device in which a work area is expanded when the CPU 20 executes various processes. The communication adapter 21 is an interface with a network (LAN) in the ISP, is connected to a dedicated line connected to the Internet N through the router 4, and is connected to another host computer 1 in the ISP.

The hard disk 23 is a storage device that stores various programs and various data read and executed by the CPU 20. The various programs stored in the hard disk 23 include an authentication server program 24. Details of processing performed by the authentication server program 24 will be described later in detail with reference to the flowchart of FIG. The various data stored in the hard disk 23 includes an ISP member table 25 having the data structure shown in FIG. As shown in FIG. 2, the ISP member table 25 has a large number of entries corresponding to each member, and each entry has a “member ID” field for recording the ID of the corresponding member. “Password” field for recording the password of the member to be registered, “Name” field indicating the name of the corresponding member, “Address” field indicating the address of the corresponding member, and charging for the service provision to the corresponding member "Billing information" field for recording information (credit card number, etc.), mobile phone operated by the corresponding member (mainly used for sending and receiving e-mails among mobile phones owned or leased by the member) E-mail address assigned by the carrier (that is, the message of the carrier). In the mail server, it is composed of a “mobile mail address” field for recording an electronic mail address registered in association with the terminal ID of the mobile phone (hereinafter referred to as “mobile mail address”), etc. Yes.
3. Processing contents Next, in the computer network of the present embodiment having the system configuration as described above, the service host computer 1 and the authentication host computer 2 are the Internet N and a plurality of portable Internets operated by a plurality of communication companies. In order to realize a mailing list service among a large number of mobile phones 6 through the network M, processing executed in accordance with the WWW server program 14, the service host program 15 and the mail server program 16, and the authentication host computer 2 is an authentication server program. The processing executed by 24 will be described based on the flowcharts of FIGS. Since the contents of the processing shown in these flowcharts are various, for convenience, the processing contents are divided into the following items and described below.

3-1. Processing that starts when the service request message is received (1) Processing that is executed to make a member open a mailing list (2) Processing that a user registered in the mailing list invites another user (3) Logs in the user (4) Processing required for displaying My Page or Member Top Screen 3-2. Processing started by reception of mail confirmation request message 3-3. Processing started upon reception of participation request message 3-1. Processing started upon reception of service request message First, the top page of the mailing list service transmitted from the cellular phone 6 operated by the member or the user of the mailing list service registered in each mailing list (a member of any mailing list). A process that starts when the service host computer 1 receives a request message (service request message) addressed to the URL will be described. In this service request message, the member or user inputs the URL of the top page of the mailing list service in a state where the browser program is executed on the processing device (not shown) of the mobile phone 6 operated by the member or user (or By operating the item linked to the top page of the mailing list service), it is transmitted to the service host computer 1 through the portable Internet network M and the Internet N.

  Upon receiving this service request message, the CPU 10 of the service host computer 1 (hereinafter simply referred to as “service host computer 1”) starts the processing shown in FIG. 11 in accordance with the WWW server 14 and the service host program 15. To do. This process is executed in parallel for each mobile phone 6 that has transmitted the service request message.

  In the first S001 after the start, the service host computer 1 transmits the screen data 17 for displaying the service top screen shown in FIG. 22 on the display of the mobile phone 6 to the mobile phone 6 that is the message transmission source. To do. This service top screen includes a login button 30 and a “create” button 32, as well as a local part field 31 in which the operator of the mobile phone 6 can input a character string by operating the input device. In the data, when the login button 30 is operated, a login request message is transmitted to the service host computer 1 and the “create” button 32 is operated in a state where an arbitrary character string is input to the local part field 31. And a setting (tag) for sending an opening request message to the service host computer 1 using the character string as a parameter indicating the desired local part.

Therefore, the service host computer 1 waits to receive any message from the mobile phone 6 in the next S002. If the login request message is received, the process proceeds to S003, and if the opening request message is received, the process proceeds to S101. The processing from S003 onward will be described as “(3) processing executed for logging in the user”, and the processing from S101 onward will be executed in order to “(1) Member open a mailing list. This will be described as “processing”.
(1) Processing executed to open a mailing list to a member In S101, the service host computer 1 refers to the mailing list information table (FIG. 3). As shown in FIG. 3, this mailing list information table has an entry corresponding to each mailing list established based on the mailing list service, and each entry is uniquely assigned to the corresponding mailing list. “Mailing list number” field for recording the mailing list number which is a serial number, “Mailing list account” field for recording the local part of the ML account assigned to the mailing list, the user number of the member who opened the mailing list (of the mailing list service) A "manager number" field for recording a serial number uniquely assigned to a "user" registered as a recipient.

  In the next S102, the service host computer 1 has already registered the same local part as the parameter included in the received opening request message in the “mailing list account” field of any entry in the mailing list information table (FIG. 3). Check if it has been done. If the same local part has already been registered, the service host computer 1 responds to the mobile phone 6 with screen data for displaying the opening alert screen in S103. As shown in FIG. 23, in this establishment alert screen, a text indicating that the desired local part input by the operator of the mobile phone 6 has been assigned to an existing mailing list and “Create” similar to the service top screen are displayed. A button 33 and a local part field 34 are included, and the screen data includes the desired character string when the “Create” button 33 is operated while an arbitrary character string is input to the local part field 34. A setting (tag) for sending an opening request message as a parameter indicating a local part to the service host computer 1 is included. For this reason, when the service host computer 1 completes S103, the service host computer 1 returns the process to S002, and waits for the opening request message to be sent again from the mobile phone 6.

  On the other hand, if it is determined in S102 that the same local part has not yet been registered, the service host computer 1 requests the authentication host computer 2 to execute an authentication process in S104.

  FIG. 21 is a flowchart showing processing executed by the CPU 20 of the authentication host computer 2 that has received the authentication request (hereinafter simply referred to as “authentication host computer 2”) in accordance with the authentication server program 24. The authentication host computer 2 starts authentication processing and transmits screen data for displaying an authentication screen in the first S701. As shown in FIG. 24, this authentication screen includes an ID column 35, a password column 36, and an authentication button 37 that allow the operator of the mobile phone 6 to input a character string by operating the input device. In this screen data, when the authentication button 37 is operated, a setting (tag) for transmitting a message including the character strings input in the ID column 35 and the password column 36 as the ID and password to the authentication host computer 2, respectively. It is included.

  Therefore, the authentication host computer 2 waits for reception of a message from the mobile phone 6 in the next S702. Upon receiving such a message, the authentication host computer 2 refers to the ISP member table 25 in the next S703.

  In next step S <b> 704, the mobile phone 6 checks whether the same combination as the ID and password included in the message received in step S <b> 702 is registered in any entry in the ISP member table 25. If the combination of the ID and password is registered in the ISP member table 25, the authentication host computer 2 ends the process. As a result, the processing being executed by the service host computer 1 is also interrupted, so that processing ahead is rejected for non-members.

  On the other hand, when such a combination of ID and password is registered in the member management DB 34, the authentication host computer 2 returns a process to the service host computer 1 with an argument that the authentication is successful. Then, the service host computer 1 can further proceed with the processing.

  The service host computer 1 that has advanced the process from S104 to S105 refers to the user table (FIG. 4). As shown in FIG. 4, this user table has an entry corresponding to each “user” who is the recipient of the mailing list service, and each entry is uniquely assigned to the corresponding “user”. "User number" field for recording the user number, which is a serial number assigned, "mail address" field for recording the mobile mail address assigned by the carrier to the mobile phone operated by the corresponding "user" It is composed of a “terminal ID” field for recording the terminal ID of the mobile phone operated by the “user”, a “member ID” field for recording the member ID when the corresponding “user” is a member, and the like. . That is, the hard disk 13 storing the user table (FIG. 4) corresponds to a storage device (first storage device).

  In next step S106, the service host computer 1 extracts the terminal ID of the request source mobile phone 6 from the header of the message received so far from the mobile phone 6 (the terminal ID is not included in the header). In this case, the mobile phone 6 is requested to transmit the terminal ID separately), and the terminal ID acquired in this way is already in the “terminal ID” field of any entry in the user table (FIG. 4). Check if it is already registered. If the terminal ID has already been registered, the service host computer 1 registers the member ID in the same entry where the terminal ID is recorded in the user table (FIG. 4) in S107. However, it is checked whether or not the registered member ID is different from the member ID authenticated in S104. Then, when the member ID is not registered in the same entry where the terminal ID is recorded in the user table (FIG. 4), and when the member ID is registered in the same entry as that recorded. If the member ID matches the member ID authenticated in S104, the process proceeds to S110. Otherwise, the process proceeds to S108.

  The case where S108 is executed, that is, the member who is operating the mobile phone 6 has another member ID in addition to the member ID authenticated in S104. The mailing list service was used using Therefore, the service host computer 1 transmits screen data for displaying a re-login screen so as to be subjected to the authentication process by the other member ID. As shown in FIG. 25, the re-login screen includes a re-login button 38. When the re-login button 38 is operated in this screen data, a re-login request message is sent to the service host computer 1. Settings (tags) to be sent to are included.

  Then, the service host computer 1 waits to receive a re-login request message from the mobile phone 6 in the next S109, and when receiving the re-login request message, returns the process to S104.

  On the other hand, in S110, the service host computer 1 is the case where the member ID is not registered in the same entry where the terminal ID is recorded in the user table (FIG. 4), or the terminal ID is recorded. It is checked whether the member ID registered in the same entry matches the member ID authenticated in S104.

  When the member ID is not registered in the same entry where the terminal ID is recorded in the user table (FIG. 4), that is, the member operating the mobile phone 6 opens a mailing list in the past in the past. The mailing list service was used without any problems, but this is the first time that the mailing list has been opened for the first time. Therefore, the service host computer 1 adds the member ID authenticated in S104 to the “member ID” field of the same entry where the terminal ID is recorded in the user table (FIG. 4) in S111. , The process proceeds to 129.

  In contrast, when the member ID registered in the same entry where the terminal ID is recorded matches the member ID authenticated in S104, that is, the mobile phone 6 is operated. The members who have opened their own mailing lists in the past. Therefore, the service host computer 1 proceeds directly to S129 without updating the user table (FIG. 4).

  On the other hand, if it is determined in S106 that the terminal ID is not registered, the service host computer 1 has registered the member ID authenticated in S104 in the user table (FIG. 4) in S112. Check if it exists.

  The case where the member ID authenticated in S104 has already been registered in the user table (FIG. 4), that is, the member who has operated the mobile phone 6 has opened a mailing list in the past. The situation is that the model 6 has been changed. Therefore, the service host computer 1 advances the processing to S113 and transmits screen data for displaying the mobile terminal information update screen to the mobile phone 6. As shown in FIG. 26, the mobile terminal information update screen includes a re-registration button 39, and the screen data includes a re-registration request message when the re-registration button 39 is operated. Settings (tags) to be transmitted to the computer 1 are included.

  Then, the service host computer 1 waits for reception of a terminal information registration request message from the mobile phone 6 in the next S114, and when receiving the terminal information registration request message, in S115, the member in the user table (FIG. 4). After overwriting the terminal ID of the mobile phone 6 in the “terminal ID” field of the same entry in which the ID is recorded, the process proceeds to S129.

  In contrast, the case where the member ID authenticated in S104 is not registered in the user table (FIG. 4), that is, the member operating the mobile phone 6 has used the mailing list service in the past. Or the user has used the mailing list service without using the other mobile phone 6 in the past without opening the mailing list. Therefore, the service host computer 1 advances the process to S116.

  In S116, the service host computer 1 communicates with the authentication host computer 2, and from the ISP member table 25, the mobile mail address recorded in the same entry as the member ID authenticated in S104 is recorded. Request to get. In response to this request, the authentication host computer 2 tries to read out the mobile mail address from the ISP member table 18 and, if it is read out, returns the read mobile mail address to the service host computer 1. . However, since the mobile mail address is an optional item in the ISP member table 25, the mobile mail address may not be registered. In this case, the authentication host computer 2 responds to the service host computer 1 that it could not be acquired.

  In S117, the service host computer 1 stores the member ID authenticated in S104, the local part included in the establishment request message received in S002, and the terminal ID of the mobile phone 6 in the temporary account table (FIG. 5). ). As shown in FIG. 5, this account temporary table is a table that temporarily stores information such as the member ID, local part, and terminal ID in association with each other.

  In next S 118, the service host computer 1 checks whether or not the mobile mail address has been acquired from the authentication host computer 2 as a result of the processing in S 116. If the mobile mail address can be acquired, the user number uniquely generated in S119, the mobile mail address acquired from the authentication host computer 2, the terminal ID of the mobile phone 6, and the member ID authenticated in S104. A new entry in which information such as this is recorded is registered in the user table (FIG. 4). When S119 is completed, the service host computer 1 advances the process to S129.

  On the other hand, if the mobile mail address cannot be acquired from the authentication host computer 2, the service host computer 1 sends screen data for displaying the mail address confirmation screen to the mobile phone 6 in S120. Send. As shown in FIG. 27, this mail address confirmation screen includes a blank mail transmission button 40. The screen data includes a service that activates a mailer program when the blank mail transmission button 40 is operated. The setting (tag or script) for preparing to send a blank mail addressed to the host computer 1 is included. Note that the mobile mail address of the mobile phone 6 is described as the sender mail address in the header of the empty mail by the normal function of the mailer program. When the operator of the mobile phone 6 performs a transmission operation in accordance with the function of the mailer program, this blank mail is transmitted to the service host computer 1.

  Therefore, the service host computer 1 waits to receive the above-described blank mail from the mobile phone 6 in the subsequent S121. Then, when receiving such a blank mail, the service host computer 1 advances the process to S122.

  In S122, the service host computer 1 generates a confirmation keyword by performing a predetermined conversion process on the transmission source mail address described in the received empty mail header. Then, the service host computer 1 registers the generated confirmation keyword and the original mail address in the new user temporary table (FIG. 6). As shown in FIG. 6, the new user temporary table is a table that stores these confirmation keywords and mail addresses in association with each other. When S122 is completed, the service host computer 1 advances the process to S123.

  In S123, the service host computer 1 sends a URL (registration) addressed to itself using the confirmation keyword generated in S122 as a parameter to the source mail address of the empty mail received in S121 (that is, to the mobile phone 6). E-mail describing the URL) as a link item. When the operator activates the mailer program and opens the e-mail in the mobile phone 6 that has received the e-mail, the URL for registration can be operated by the function of the mailer program, and the operator operates the registration URL. A message specifying the registration URL is transmitted to the service host computer 1 by the function of the browser program.

  Therefore, the service host computer 1 waits for the reception of the above-described message from the mobile phone 6 in subsequent S124. When receiving the message, the service host computer 1 advances the process to S125.

  In S125, the service host computer 1 requests the authentication host computer 2 to execute the authentication process again. Upon receiving the request, the authentication host computer 2 executes the authentication process shown in FIG. 21 as described above.

  If the authentication is successful, the service host computer 1 advances the process from S125 to S126. In S126, the service host computer 1 identifies the mail address associated with the confirmation keyword included in the message received in S124 in the new user temporary table (FIG. 6). As described above, it is confirmed that the mail address is not only set in the mobile phone 6 but actually used in the mobile Internet network M.

  In the next S127, the service host computer 1 identifies the local part associated with the member ID authenticated in S125 in the account temporary table (FIG. 5).

  In next S128, the service host computer 1 creates a new entry in which the unique user number, the e-mail address specified in S126, the terminal ID of the mobile phone 6 and the member ID specified in S123 are recorded in the user table ( Register in Figure 4). When S128 is completed, the service host computer 1 advances the process to S129.

  In S <b> 129, the service host computer 1 transmits screen data for displaying the establishment confirmation screen to the mobile phone 6. As shown in FIG. 28, this establishment confirmation screen is operated to confirm the description of the ML account including the desired local part input by the operator of the mobile phone 6 and the creation of the mailing list in the ML account. An OK button 41, a “Create” button 43 operated to change the local part, and a local part field 42 for inputting the changed local part. The screen data includes an OK button 41. When the “Create” button 43 is operated in a state where a message indicating this is transmitted to the service host computer 1 and an arbitrary character string is input to the local part field 42, the character string is displayed. A message with a parameter indicating the changed local part is sent to the service host computer 1 That setting (tag), are included.

  Therefore, the service host computer 1 waits for a message from the mobile phone 6 in the next S130. When receiving the message from the mobile phone 6, the service host computer 1 refers to the mailing list information table (FIG. 3) in S131.

  In the next S132, the service host computer 1 determines that the desired local part acquired most recently from the mobile phone 6 (or the changed local part if the changed local part is included in the message received in S130). Then, it is checked whether or not it is already registered in the “mailing list account” field of any entry in the mailing list information table (FIG. 3). If the same local part has already been registered, the service host computer 1 returns screen data for displaying the opening alert screen to the mobile phone 6 in S133, and then returns the process to S130.

  On the other hand, if the same local part has not yet been registered in any entry in the mailing list information table (FIG. 3), the service host computer 1 uses the unique mailing list number and the mobile phone 6 in S134. A new entry in which the user number (administrator number) registered in the user table (FIG. 4) is recorded in the mailing list information table (FIG. 3) for the latest acquired local part and the member who operates the mobile phone 6 is registered. sign up. At the same time, the service host computer 1 associates the mailing list number in the entry newly registered in the mailing list with the user number registered in the user table (FIG. 4) for the member operating the mobile phone 6, Register in the relation table (FIG. 7). As shown in FIG. 7, this mailing list relation table is a table that stores the mailing list number of each mailing list in association with the user numbers of all users who are members of that mailing list. The hard disk 13 storing the combination of the mailing list relation table (FIG. 7) and the mailing list information table (FIG. 3) corresponds to the second storage device. When S134 is completed, the service host computer 1 advances the process to S135.

In S <b> 135, the service host computer 1 transmits screen data for displaying an establishment completion screen to the mobile phone 6. As shown in FIG. 29, this opening completion screen includes a member top button 44, a My Page button 45, an invitation button 46, and an invitation address description column 47 in which one or a plurality of mail addresses can be entered by operating the input device. The screen data includes a setting (tag) for sending a message including a parameter indicating the operated button to the service host computer 1 when each button 44, 45 is operated, and an invitation address. When the invitation button 46 is operated in a state where one or more mail addresses are input in the description column 47, a message including each mail address input in the invitation address description column 47 as a parameter is used as the service host computer 1. Settings (tags) to be sent to are included. Therefore, the service host computer 1 waits to receive any message from the mobile phone 6 in the next S136. When the service host computer 1 receives a message including the fact that the member top button 44 has been operated, the service host computer 1 proceeds to step S012, and when receiving a message including the fact that the my page button 45 has been operated, the process proceeds to step S009. If a message including an invitation mail address is received, the process proceeds to S017. The process after S017 will be described later as “(2) process for inviting another user to a user registered in the mailing list”, and the process after S009 or S012 is described in “(4) My Page or This will be described later as “processing required from the state in which the member top screen is displayed”.
(2) Process for User Registered in Mailing List to Invite Other Users The process after S017 is performed for any user (member, ie mailing list relation table [FIG. 7]) registered in any mailing list. The user indicated by the user number associated with the mailing list number) invites (adds) another person as a new member of the mailing list.

  In S017, the service host computer 1 receives the message received from the mobile phone 6 (if S017 is executed immediately after S136, the message received in S136, and if S017 is executed immediately after S014, An invitation email is sent to all email addresses included as parameters in the message received in S014. In the invitation mail transmitted to each mail address, a URL (participation URL) addressed to the service host computer 1 using the confirmation keyword obtained by performing the predetermined conversion process on the mail address as a parameter. It is described as a link item. Accordingly, when the operator activates the mailer program and opens the invitation mail in the mobile phone 6 ′ that has received the invitation mail, the URL for participation can be operated by the function of the mailer program, and the operator can operate the participation mail. When the URL is operated, a message specifying the participation URL (participation request message) is transmitted to the service host computer 1 by the function of the browser program.

  In S018 executed after the completion of S017, the service host computer 1 determines, for each email address (invitation email address) that sent the invitation email in S017, a confirmation keyword generated based on the invitation email address, Identified mailing list (if S017 is executed immediately after S136, the mailing list registered in the mailing list in S134; if S017 is executed immediately after S014, the member whose screen data was sent in S013 The mailing list number of the mailing list corresponding to the top screen) and the expiration date of the invitation (for example, the date and time after a certain period from the time of processing) are associated and registered in the invitation table (FIG. 8). As shown in FIG. 8, an entry is prepared for each invitation email address in the invitation table, and each entry has a field for registering a confirmation keyword, a mailing list number, an invitation email address, and an expiration date, respectively. It is configured. When S018 is completed, the service host computer 1 advances the process to S012. The processing after S012 will be described later as “(4) processing required from the state where the my page or member top screen is displayed”.

Thereafter, when the participation request message described above is received from another mobile phone 6 ′ that has received the invitation mail, the service host computer 1 starts “3-3. Process started by reception of participation request message” to be described later. . As a result, the number of members of the mailing list increases (that is, the user number associated with the mailing list number of the mailing list by the mailing string table 18 increases).
(3) Process Performed to Log in User On the other hand, in S003, the service host computer 1 extracts the terminal ID from the header of the message received in S002 (when the terminal ID is not included in the header) (The terminal ID is acquired by separately requesting the mobile phone 6 to transmit the terminal ID) (corresponding to the terminal ID acquisition means).

  In next step S004, the service host computer 1 refers to the user table (FIG. 4).

  In next step S005, the service host computer 1 checks whether or not the terminal ID acquired in step S003 is registered in any entry in the user table (FIG. 4). When the terminal ID is registered in any entry in the user table (FIG. 4) (corresponding to the case where the terminal ID acquired by the terminal ID acquisition means is registered in the storage device), that is, the mobile phone In this situation, the operator of the telephone 6 is a member of any mailing list as a user of the mailing list service in the past. Therefore, the service host computer 1 advances the process to S007 as it is.

  On the other hand, if the terminal ID is not registered in any entry in the user table (FIG. 4) (corresponding to the case where the terminal ID is not registered in the storage device), the service In step S006, the host computer 1 executes registration information confirmation processing.

  FIG. 17 is a flowchart showing a registration information confirmation processing subroutine executed in S006. In the first step S401 after entering this subroutine, the service host computer 1 transmits image data for displaying a registration confirmation screen to the mobile phone 6. As shown in FIG. 30, this registration confirmation screen includes a blank mail transmission button 48. The screen data includes a mail host program that is activated when the blank mail transmission button 48 is operated, and a service host computer. 1 includes a setting (tag or script) that prepares to send a blank email addressed to 1 (corresponding to requesting a mobile terminal to send an email). Note that the mobile mail address of the mobile phone 6 is described as the sender mail address in the header of the empty mail by the normal function of the mailer program. When the operator of the mobile phone 6 performs a transmission operation in accordance with the function of the mailer program, this blank mail is transmitted to the service host computer 1.

  Therefore, the service host computer 1 waits to receive the above-described blank mail from the mobile phone 6 in the subsequent S402. Then, when receiving such an empty mail (corresponding to receiving an electronic mail transmitted by the mobile terminal in response to the request), the service host computer 1 advances the process to S403.

  In S403, the service host computer 1 extracts the source mail address described in the received empty mail header.

  In next step S404, the service host computer 1 refers to the user table (FIG. 4).

  In next step S405, the service host computer 1 checks whether or not the mail address extracted in step S404 is registered in the “mail address” field in any entry in the user table (FIG. 4). The case where the e-mail address extracted in S404 is not registered in any entry in the user table (FIG. 4), that is, the operator of the mobile phone 6 has used the mailing list service in the past. There is no situation at all, or the mailing list service has been used by using another mobile phone 6 in the past, but the mobile mail address has also changed at the same time as changing the model of the mobile phone 6 is there. Therefore, the service host computer 1 advances the process to S413. In contrast, when the mail address extracted in S404 is registered in the “mail address” field in any entry in the user table (FIG. 4) (the e-mail source address is registered in the storage device). In other words, the operator of the mobile phone 6 has used the mailing list service using another mobile phone 6 in the past, but then changed the model of the mobile phone 6 It is the situation. Therefore, the service host computer 1 advances the processing to S406 in order to update the mail address.

  In S406, the service host computer 1 generates a confirmation keyword by performing a predetermined conversion process on the mail address extracted in S403. Then, the service host computer 1 registers the generated confirmation keyword and the original e-mail address in the mobile change information table (FIG. 9). As shown in FIG. 9, this portable change information table is a table that stores these confirmation keywords and mail addresses in association with each other. When S406 is completed, the service host computer 1 advances the process to S407.

  In S407, the service host computer 1 links the URL addressed to itself (registration URL) with the confirmation keyword generated in S406 as a parameter to the mail address extracted in S403 (that is, to the mobile phone 6). Reply to emails described as items. When the operator activates the mailer program and opens the e-mail in the mobile phone 6 that has received the e-mail, the URL for registration can be operated by the function of the mailer program, and the operator operates the registration URL. A message specifying the registration URL is transmitted to the service host computer 1 by the function of the browser program.

  Therefore, the service host computer 1 waits for the reception of the above-described message from the mobile phone 6 in subsequent S408. When receiving the message, the service host computer 1 advances the process to S409.

  In S409, the service host computer 1 identifies the mail address associated with the mobile change information table (FIG. 9) for the confirmation keyword included in the message received in S408. As described above, it is confirmed that the mail address is not only set in the mobile phone 6 but actually used in the mobile Internet network M.

  Therefore, in the next S410, the service host computer 1 stores the message received in S408 in the “terminal ID” field of the entry in which the mail address specified in S409 is recorded in the user table (FIG. 4). The terminal ID included in the header (if the terminal ID is not included in the header, the terminal ID acquired by separately requesting the mobile phone 6) is overwritten. As a result, the terminal ID registered in the user table (FIG. 4) for the user is updated to the terminal ID of the mobile phone 6 currently used by the user.

  Therefore, in the next S411, the service host computer 1 transmits screen data for displaying a setting completion screen to the mobile phone 6. As shown in FIG. 31, this setting completion screen includes a “top” button 49, and when the “top” button 49 is operated, the screen data includes a top screen request message as a service host. Settings (tags) to be transmitted to the computer 1 are included.

  Therefore, the service host computer 1 waits for reception of a top screen request message from the mobile phone 6 in the next 412. Then, when receiving the top screen request message, the service host computer 1 advances the process to S007.

  In S007, the service host computer 1 refers to the mailing list relation table (FIG. 7).

  In next S008, the service host computer 1 associates the user number recorded in the same entry as the terminal ID of the mobile phone 6 in the user table (FIG. 4) in the mailing list relation table (FIG. 7). Check if there is only one or more mailing list numbers. If there is a plurality, the process proceeds to S009, and if there is only one, the process proceeds to S012. The processing after S009 or S012 will be described later as “(4) processing required from the state where the my page or member top screen is displayed”.

  On the other hand, in S413, the service host computer 1 returns an e-mail describing a registration URL not including the confirmation keyword as a parameter to the e-mail address extracted in S403. When the operator activates the mailer program and opens the e-mail in the mobile phone 6 that has received the e-mail, the URL for registration can be operated by the function of the mailer program, and the operator operates the registration URL. A message specifying the registration URL is transmitted to the service host computer 1 by the function of the browser program.

  Therefore, the service host computer 1 waits for the reception of the above-described message from the mobile phone 6 in subsequent S414. When receiving the message, the service host computer 1 advances the process to S415.

  In S415, the service host computer 1 requests the authentication host computer 2 to execute an authentication process. Upon receiving the request, the authentication host computer 2 executes the authentication process shown in FIG. 21 as described above.

  If the authentication is successful, the service host computer 1 advances the process from S415 to S416. In S416, the service host computer 1 refers to the user table (FIG. 4).

  In next S417, the service host computer 1 checks whether or not the member ID authenticated in S415 is registered in the “member ID” field of any entry of the user table (FIG. 4).

  If the authenticated member ID is not registered in the user table (FIG. 4), the service host computer 1 advances the process to S423. The case where S423 is executed means that the member operating the mobile phone 6 has never used the mailing list service in the past, or in addition to the member ID authenticated in S415. In the past, a mailing list was opened by using the mailing list service using the other member ID. Therefore, the service host computer 1 transmits screen data for displaying a re-login screen (FIG. 25) so as to be subjected to the authentication process by the other member ID.

  Then, the service host computer 1 waits to receive a re-login request message from the mobile phone 6 in the next S424, and when receiving the re-login request message, returns the process to S415. In a situation where the member operating the mobile phone 6 has never used the mailing list service in the past, the determination in S417 will not be YES even if re-login is repeated. This is because, unless a member is invited from an existing mailing list, in order for a member to use the mailing list for the first time, the above-mentioned "(1) Member" This is because it is necessary to follow the procedure in accordance with “the process executed to open the mailing list.”

  On the other hand, if the member ID authenticated in S415 is registered in the user table (FIG. 4), the service host computer 1 advances the process to S418. When S418 is executed, that is, a member who operates the mobile phone 6 has opened a mailing list by himself / herself using the mailing list service using another mobile phone 6 in the past. After that, the mobile phone 6 was changed in model and at the same time the mobile mail address was changed. The person who established such a mailing list is given various authorities (for example, closing of the mailing list, deleting members, etc.) as an administrator of the mailing list. Therefore, even when the mailing list opener changes the model of the mobile phone 6 and the mobile mail address at the same time (the above-described “(1) process executed to open a mailing list to a member”). Need to return to service immediately). Therefore, only the establishment person is allowed to update the terminal ID of the mobile phone 6 in the user table (FIG. 4) by the processing from S418 onward.

  Specifically, in S418, the service host computer 1 transmits screen data for displaying the mobile information update screen to the mobile phone 6. As shown in FIG. 32, this portable information update screen includes a terminal information update button 50, and the screen data includes a terminal information update request message when the terminal information update button 50 is operated. The setting (tag) to be transmitted to the host computer 1 is included.

  Then, the service host computer 1 waits for reception of a terminal information update request message from the mobile phone 6 in the next S419, and when receiving the terminal information update request message, in S420, S415 in the user table (FIG. 4). Overwrite the terminal ID of the mobile phone 6 extracted from the header of the message received in S419 in the “terminal ID” field of the same entry in which the member ID authenticated in is recorded. Proceed to S421.

  In S <b> 421, the service host computer 1 transmits screen data for displaying a registration information update screen to the mobile phone 6. As shown in FIG. 33, this registration information completion screen includes a My Page button 51, and when the My Page button 51 is operated, a message indicating that the My Page button 51 is operated is displayed in the screen data. Settings (tags) to be sent to are included. Therefore, the service host computer 1 waits for the reception of a message from the mobile phone 6 in the next S422.

When the service host computer 1 receives a message from the mobile phone 6, the service host computer 1 advances the process to S009. The processing after S009 will be described later as “(4) processing required from the state where the my page or member top screen is displayed”.
(4) Processing Requested from Displaying My Page or Member Top Screen In S009, the service host computer 1 generates screen data for displaying the My Page screen. Specifically, the service host computer 1 associates the user number recorded in the same entry as the terminal ID of the mobile phone 6 in the user table (FIG. 4) in the mailing list relation table (FIG. 7). Read all mailing list numbers. Then, the ML account associated with each read mailing list number is read from the mailing list information table (FIG. 3). Then, as shown in FIG. 41, the service host computer 1 has a group of buttons 51 associated with all of the read ML accounts, and an operator who is a member of any mailing list. When the e-mail address of the mobile phone 6 is changed or the operator who is a member opens the mailing list for the first time, the my page screen including the mail change button 52 to be operated to register the mobile e-mail address is displayed on the browser of the mobile phone 6 Is displayed, and when the button 51 or the change mail button 52 associated with any ML account is operated, an e-mail including parameters for specifying the buttons 51 and 52 is transmitted to the service host computer 1 Screen data including (tag) is generated. Then, the service host computer 1 transmits the generated screen data to the mobile phone 6.

  In the next step S010, the service host computer 1 waits to receive a message transmitted by the operator operating one of the buttons 51 and 52 on the My Page screen on the mobile phone 6. When the service host computer 1 receives a message including the fact that the mail change button has been operated, the service host computer 1 advances the process to S201.

  In S <b> 201, the service host computer 1 transmits a mail address change screen to the mobile phone 6. As shown in FIG. 34, this e-mail address change screen includes a blank e-mail transmission button 53, and when the empty mail transmission button 53 is operated, the mailer program is activated to display the screen data. The setting (tag or script) for preparing to send a blank mail addressed to the host computer 1 is included. Note that the mobile mail address of the mobile phone 6 is described as the sender mail address in the header of the empty mail by the normal function of the mailer program. When the operator of the mobile phone 6 performs a transmission operation in accordance with the function of the mailer program, this blank mail is transmitted to the service host computer 1.

  Therefore, the service host computer 1 waits to receive the above-described blank mail from the mobile phone 6 in the subsequent S202. Then, when receiving such an empty mail, the service host computer 1 advances the process to S203.

  In S203, the service host computer 1 generates a confirmation keyword by applying a predetermined conversion process to the transmission source mail address described in the received empty mail header. Then, the service host computer 1 registers the generated confirmation keyword and the e-mail address (post-change e-mail address) as a basis in the e-mail address change information table 18. As shown in FIG. 10, the mail address change information table 18 is a table that stores these confirmation keywords and changed mail addresses in association with each other. When S203 is completed, the service host computer 1 advances the process to S204.

  In S204, the service host computer 1 describes the URL (confirmation URL) addressed to itself using the confirmation keyword generated in S122 as a parameter to the post-change email address (that is, to the mobile phone 6) as a link item. Reply to the email. When the operator activates the mailer program and opens the email in the mobile phone 6 that has received the email, the confirmation URL can be operated by the function of the mailer program, and the operator operates the confirmation URL. Then, a message specifying the confirmation URL is transmitted to the service host computer 1 by the function of the browser program.

  Therefore, the service host computer 1 waits for the reception of the above-described message from the mobile phone 6 in subsequent S205. When receiving the message, the service host computer 1 advances the process to S206.

  In S206, the service host computer 1 extracts the terminal ID of the mobile phone 6 from the header of the message received in S205 (if the terminal ID is not included in the header, the service host computer 1 separately sends the mobile phone 6 to the mobile phone 6). To request and acquire the terminal ID).

  In next step S207, the service host computer 1 determines whether or not the same terminal ID as that acquired in S206 is registered in the “terminal ID” field of any entry in the user table (FIG. 4). To check. If the same terminal ID is not registered, it is determined that some error has occurred, and the process ends. On the other hand, when the same terminal ID is registered, since it is confirmed that the operator of the mobile phone 6 is a member of any mailing list, the service host computer 1 performs the process in S208. Proceed to

  In S208, the service host computer 1 identifies the post-change mail address associated with the mail address change information table 18 for the confirmation keyword included in the message received in S205. From the above, it is confirmed that the post-change email address is not only set in the mobile phone 6 but is actually valid in the mobile Internet network M. Then, the service host computer 1 overwrites the specified changed mail address in the “mail address” field of the same entry in which the terminal ID extracted in S206 in the user table is registered.

  In the next S209, the service host computer 1 transmits screen data for displaying the change completion screen to the mobile phone 6.

  In next step S <b> 210, the service host computer 1 waits to receive a top screen request message from the mobile phone 6. Then, when receiving the top screen request message, the service host computer 1 advances the process to S007.

  On the other hand, if it is determined in S010 that the message including the operation of the button 51 associated with any ML account has been received, the service host computer 1 advances the process to S011. In S011, the service host computer 1 identifies the mailing list number corresponding to the ML account associated with the operated button 51 from the mailing information table 18 based on the parameters included in the received message. After completion of S011, the service host computer 1 advances the process to S012.

  In S012, the mailing list to be browsed (that is, the only mailing list of which the operator is a member, the mailing list in which the mailing list number is specified in S011, the mailing list newly established by the process before S136) up to that point. The attached files of all the e-mails received in the above are read from the ML accommodating directory 19.

  In the next S103, the service host computer 1 generates screen data for displaying the member top screen. As shown in FIG. 35, small thumbnails generated based on the image data in each attached file read in S102 are displayed side by side on this member top screen, as well as a My Page button 54 and an invitation button. 55 and an invitation address description column 56 in which one or a plurality of e-mail addresses can be entered by operating the input device, and the screen data indicates that the My Page button 54 is operated. When the invitation button 55 is operated in a state where one or a plurality of mail addresses are input in the setting (tag) and invitation address description column 47 for sending a message including parameters to the service host computer 1, the invitation address description column A message containing each mail address entered in 56 as a parameter Set to be transmitted to the-bis host computer 1 (tag) is included. A large number of thumbnails displayed on the member top screen form blocks for each predetermined number of units, and each block itself is a link item. That is, in the image data, when each block is operated, the service host computer 1 determines the information for identifying the block (which e-mail corresponds to the block indicated by the information). A setting (tag) for transmitting a message including a parameter that needs to be stored in a temporary table (not shown) as a parameter to the service host computer 1 is included. The service host computer 1 transmits the screen data generated as having such contents to the mobile phone 6.

  In subsequent S014, the service host computer 1 waits to receive any message from the mobile phone 6. When the service host computer 1 receives a message including the fact that the invitation button 55 has been operated, the process proceeds to S017. When the service host computer 1 receives a message including the fact that the my page button 54 has been operated, the process proceeds to S009. When a message including the fact that any block has been operated is received, the process proceeds to S015. The processes after S017 are as described in “(2) Process for user registered in mailing list to invite other users”.

  In S015, the service host computer 1 generates a medium-sized thumbnail based on the attached file corresponding to the block corresponding to the parameter included in the message received in S014 among the attached files read in S012. Then, screen data for generating a list display screen for displaying the thumbnails as a list as shown in FIG. 35 is generated. As shown in FIG. 36, this list display screen includes a top button 58 in addition to the thumbnail 57, and the screen data is operated when each thumbnail 57 or the top button 58 is operated. A setting (tag) for transmitting a message including a parameter for specifying the thumbnail 57 or the top button 58 to the service host computer 1 is included.

  Therefore, the service host computer 1 waits to receive a message from the mobile phone 6 in the next 016. When the service host computer 1 receives a message including a parameter indicating that the top button 58 has been operated, the service host computer 1 returns the process to S012, and upon receiving a message including a parameter indicating that one of the thumbnails has been operated, The process proceeds to S301.

  In S301, the service host computer 1 attaches the selected e-mail (if it is executed immediately after S015, the attached file that is the origin of the thumbnail indicated by the parameter included in the message received in S016) Screen data for displaying a single display screen of an e-mail, an e-mail corresponding to the parameter [equivalent to ML account, post number] included in the attached file confirmation URL when executed after the processing of FIG. Is transmitted to the mobile phone 6. As shown in FIG. 37, the one-item display screen includes a subject 59, a source mail address 60, a photograph (image) based on a text file and an attached file read from the ML accommodating directory 19 regarding the selected electronic mail. 61, a text 62 are displayed, and a continuation button 63, a less button 64, and a top button 65 are included. The screen data includes a setting for sending a message to that effect to the service host computer 1 when the button 63 or the top button 65 is operated, and a mailer program is activated when the response button 64 is operated. A setting (tag or script) for preparing preparation and transmission of a reply mail addressed to the ML account is included. When the operator of the mobile phone 6 performs a transmission operation according to the function of the mailer program, a reply mail based on the mailing list service is transmitted to the service host computer 1.

  On the other hand, the service host computer 1 waits for reception of a message from the mobile phone 6 in the next S302 until a predetermined timeout time elapses. If a message indicating that the top button 65 has been operated before the predetermined timeout period has been received, the process proceeds to S012, and if a message indicating that the button 63 has been operated is received, the process proceeds to S303. .

  In step S <b> 303, the service host computer 1 transmits screen data for displaying an archive screen to the mobile phone 6. As shown in FIG. 38, this archive screen lists the contents of all reply mails for the e-mail that is the origin of the one-item display screen in the contents of the one-item display screen that sent the screen data in S301. It is. The service host computer 1 generates screen data for displaying the archive screen based on the text file and the attached file in the ML accommodation directory, and transmits the screen data to the mobile phone 6.

The service host computer 1 waits for reception of a message from the mobile phone 6 in the next S304 until a predetermined timeout time elapses. If a message indicating that the top button 66 has been operated before the predetermined time-out period has elapsed is received, the process proceeds to S012.
3-2. Processing Started by Receiving Mail Confirmation Request Message Although the flowchart is omitted because it is a known process, the service host computer 1 performs electronic processing based on the mailing list service in parallel with the processing based on the flowchart in FIG. Mail forwarding processing is being performed. That is, when receiving an e-mail from the mobile phone 6 with the ML account of any mailing list as the destination e-mail address and the mobile e-mail address of the mobile phone 6 as the sender e-mail address, the service host computer 1 The mailing list number corresponding to the local part in the ML account is read from the mailing list information table (FIG. 3), and the user number corresponding to the sender mail address is read from the user table (FIG. 4). When the mailing list number and the user number are associated with each other by the mailing list relation table (FIG. 7), it is determined that the mail is a mail from a member of the mailing list. It is stored in a predetermined position in the ML storage directory 19 together with the attached file. Also, all the user numbers associated with the mailing list number are read from the mailing list relation table (FIG. 7), and the mail addresses corresponding to the read user numbers are read from the user table (FIG. 4). The e-mail is transferred to the e-mail address using the ML account as the sender e-mail address. As described above, the attached file is deleted from the forwarded e-mail. Instead, a unique post number assigned to the ML account and the e-mail transmission order in the mailing list is added to the body of the e-mail. An URL (attached file confirmation URL) addressed to the service host computer 1 included as a parameter is embedded.

  When the operator activates the mailer program and opens the e-mail in the mobile phone 6 that has received the e-mail, the function for the mailer program makes it possible to operate the URL for confirming the attached file. When the file confirmation URL is operated, a message (mail confirmation request message) specifying the attached file confirmation URL is transmitted to the service host computer 1 by the function of the browser program.

  The service host computer 1 that has received this mail confirmation request message starts the process shown in FIG. 19 in parallel with other processes. In the first step S501, the service host computer 1 extracts the terminal ID of the mobile phone 6 from the header of the received message (if the terminal ID is not included in the header, the service host computer 1 separately sends the mobile phone 6 to the mobile phone 6). Requesting and obtaining a terminal ID) (corresponding to a terminal ID obtaining means).

  In next step S502, the service host computer 1 refers to the user table (FIG. 4).

  In next step S503, the service host computer 1 checks whether the terminal ID extracted in step S501 is registered in any entry of the user table (FIG. 4). If the terminal ID is not registered in any entry (corresponding to the case where the terminal ID is not registered in the storage device), the operator of the mobile phone 6 is a member of the mailing list, but is not mobile. Since there is a possibility that the model of the telephone 6 has been changed, a registration information confirmation process is executed in S504. Note that the registration information confirmation process executes a subroutine shown in the flowcharts of FIGS.

  On the other hand, when the terminal ID is registered in any entry (corresponding to the case where the terminal ID acquired by the terminal ID acquisition unit is registered in the storage unit), the service host computer 1 In S505, the mailing list information table (FIG. 3) and the mailing list relation table are referred to.

  In next step S506, the service host computer 1 reads out the mailing list number corresponding to the local part of the ML account included as a parameter in the received mail confirmation request message from the mailing list information table (FIG. 3) and extracts it in S501. The user number corresponding to the terminal ID is read from the user table (FIG. 4), and it is checked whether or not the mailing list number and the user number are associated by the mailing list relation table (FIG. 7). And when the said mailing list number and the said user number are not matched by the mailing list relation table (FIG. 7), since the user who is the operator of the said mobile telephone 6 is not a member of the said mailing list, In step S507, the host computer 1 transmits screen data for displaying an error screen to the mobile phone 6 and ends the process.

On the other hand, if it is determined in S607 that the mailing list number and the user number are associated with each other by the mailing list relation table (FIG. 7), the service host computer 1 advances the process to S301. Since the processing from S301 onward has already been described with reference to FIG.
3-3. Processing Started by Receiving Participation Request Message As described above, when the operator activates the mailer program and opens the invitation mail on the mobile phone 6 ′ that has received the invitation mail sent in S017, the mailer program The participation URL can be operated by the function, and when the operator operates the participation URL, a message (participation request message) specifying the participation URL is transmitted to the service host computer 1 by the function of the browser program. Is done.

  The service host computer 1 that has received this participation request message starts the process shown in FIG. 20 in parallel with other processes. In the first S601, the service host computer 1 refers to the invitation table (FIG. 8).

  In next step S602, the service host computer 1 registers in the invitation table (FIG. 8) a confirmation keyword that is the same as the confirmation keyword included in the received participation request message and that is within the expiration date at the time of processing. Check if it has been done. If the confirmation keyword is not registered in the invitation table (FIG. 8), the service host computer 1 transmits screen data for displaying an error screen to the mobile phone 6 in S603, and ends the process. To do.

  On the other hand, if the confirmation keyword is registered in the invitation table, the service host computer 1 extracts the terminal ID of the mobile phone 6 from the header of the received message in S604 (the terminal ID in the header). Is not included, the terminal ID is separately requested from the mobile phone 6 and acquired).

  In next step S605, the service host computer 1 refers to the user table (FIG. 4).

  In next step S606, the service host computer 1 checks whether or not the terminal ID acquired in step S604 is registered in any entry of the user table (FIG. 4).

  The case where the terminal ID acquired in S604 is registered in any entry of the user table (FIG. 4), that is, the situation where the operator of the mobile phone 6 has used the mailing list service in the past. It is. Therefore, the service host computer 1 is included in the participation request message in S607 in order to check whether or not the operator who is the user has changed the mobile mail address since the use of the mailing list service in the past. Whether the invitation email address registered in the invitation table (FIG. 8) corresponding to the confirmation keyword matches the email address registered in the user table (FIG. 4) corresponding to the terminal ID Check. If the two match, the operator has not changed the mobile mail address, and the service host computer 1 proceeds directly to S616.

  On the other hand, if the two do not match, since the operator has changed the mobile mail address, the service host computer 1 uses the screen data for displaying the mail address confirmation screen in S608. Is transmitted to the mobile phone 6. As shown in FIG. 39, the e-mail address confirmation screen includes a button 67 to be changed, and when the button 67 to be changed is operated, a message including a parameter indicating that is displayed in the screen data. Settings (tags) to be transmitted to the computer 1 are included.

  Therefore, the service host computer 1 waits for the reception of the message from the service host computer 1 in the next S609, and when received, in S610, invites corresponding to the confirmation keyword included in the participation request message. The invitation mail address registered in the table (FIG. 8) overwrites the mail address registered in the user table (FIG. 4) corresponding to the terminal ID. When S610 is completed, the service host computer 1 advances the process to S616.

  On the other hand, the case where the terminal ID acquired in S604 is not registered in any entry of the user table (FIG. 4), that is, the operator of the mobile phone 6 has never used the mailing list service in the past. It is a situation, or the operator of the mobile phone 6 has used the mailing list service in the past, but has subsequently changed the model of the mobile phone 6. Therefore, the service host computer 1 includes the participation request message in S611 in order to check whether the operator who is the user has used the mailing list service in the past based on the registration of the mobile mail address. Check whether the invitation email address registered in the invitation table (FIG. 8) corresponding to the confirmed keyword is registered in the “mail address” field of any entry in the user table (FIG. 4). To do.

  If the invitation email address is not registered in any entry in the user table, the service host computer 1 determines that the operator has not used the mailing list service in the past, and S615. Then, the operator information is newly registered in the user table. That is, the user number uniquely generated is recorded in the “user number” field, the invitation email address is recorded in the “mail address” field, and the new entry in which the terminal ID is recorded in the “terminal ID” field. And register in the user table (FIG. 4). When S615 is completed, the service host computer 1 advances the process to S616.

  On the other hand, when the invitation email address is registered in any entry in the user table, the service host computer 1 indicates that the operator of the mobile phone 6 has used the mailing list service in the past. Although it has been used, it is determined that the model of the mobile phone 6 has been changed, and screen data for displaying the mobile information update screen (FIG. 32) is transmitted to the mobile phone 6 in S612.

  In next step S612, the service host computer 1 waits for a terminal information update request message transmitted from the mobile phone 6 when the terminal information update button 50 in the mobile information update screen is operated, and the terminal information update request message is received. In S614, the terminal ID acquired in S604 is overwritten in the “terminal ID” field of the entry in which the invitation mail address is registered in the user table (FIG. 4). After completion of S614, the service host computer 1 advances the process to S616.

  In S616, the service host computer 1 reads the mailing list number registered in the invitation table (FIG. 8) corresponding to the invitation email address, and registers it in the user table (FIG. 4) corresponding to the invitation email address. The added user number is added to the mailing list relation table (FIG. 7) in association with the mailing list number.

  In next step S617, the service host computer 1 transmits screen data for displaying a participation completion screen to the mobile phone 6. As shown in FIG. 40, this participation completion screen includes a My Page button 67, and when the My Page button 67 is operated, a message to that effect is displayed to the service host computer 1 in the screen data. Settings (tags) to be sent are included. Therefore, the service host computer 1 waits for reception of a message from the mobile phone 6 in the next S618.

When the service host computer 1 receives a message from the mobile phone 6, the service host computer 1 advances the process to S009. The processing after S009 is as already described as “(4) processing required from the state where the my page or member top screen is displayed”.
4). Advantages of the present embodiment As described above, in the present embodiment, the qualification of the operator of the mobile phone 6 is divided into three stages and four types with respect to the mailing list service provided by the ISP. That is, it is possible to receive a high value-added service such as a paid service provided by the ISP. Therefore, detailed personal information such as billing information is registered in the ISP member table 25, and the mailing list service is provided. "Members" who can open a mailing list based on, and registered to that mailing list by receiving an invitation to the mailing list opened by any member (invitation by the founder or an invitation by a user who is already a member) “Member”, “User” of the mailing list service whose qualification is that it is a member of any mailing list, and others.

  First, a “member” becomes a “member” of the new mailing list by opening a mailing list by himself / herself, and thus becomes a “user” of the mailing list service. Even if the member does not open a mailing list himself, if he receives an invitation from a member of an existing mailing list, he / she becomes a member of the mailing list, and thus becomes a user of the mailing list service. It is possible. As described above, the “member” has the authority to open a mailing list by himself / herself, and has the powerful authority to close the mailing list established by himself / herself and to delete members as described above. Accordingly, the authentication of the qualification is performed by the authentication host computer 2 requesting the input of the member ID and password using the authentication screen (FIG. 24) and checking whether or not the combination is registered in the ISP member table 25. This is done through a strict procedure (S104, S125, S415, FIG. 21).

  Next, the “member” of any mailing list is a web page dedicated to that mailing list (member top page [FIG. 35], list display screen [FIG. 36], single message display screen [FIG. 37], archive screen [FIG. 38]. ]) And can also access a screen (e-mail address change screen [FIG. 34], etc.) below My Page 33 (FIG. 33).

  If a member becomes a “member” of the mailing list by opening the mailing list themselves, or if a member or another person receives an invitation from a “member” of an existing mailing list, these members will be the service host. Information such as the terminal ID of the mobile phone 6 used to access the computer 1 (unique user number, mobile mail address, member ID [only when the user is a member]) is registered in the ISP member table 25. By registering personal information (simple personal information) in the user table (FIG. 4), these persons become “users” of the mailing list service. It should be noted that the mailing list relation table (FIG. 7) indicates which mailing list the person registered in the user table as “user” is, specifically, a “member”.

  Therefore, authentication of whether or not the operator of the mobile phone 6 that has accessed (sends a message) to the service host computer 1 is a “member” of any mailing list is performed from the mobile phone 6 as a simple authentication means. The terminal ID of the mobile phone 6 included in the header of the received message (if the terminal ID is not included in the header, the terminal ID acquired by separately requesting the mobile phone 6) is stored in the user table ( It is made depending on whether or not it is registered in (FIG. 4) (S003 to S005, S501 to S503).

  However, the “user” does not use the single mobile phone 6 for a long time, and almost always changes (exchanges) the model of the mobile phone 6 every several months to several years. Accordingly, once the terminal ID of the mobile phone 6 of “user” is registered in the user table (FIG. 4), when the “user” changes the model of the mobile phone 6, the “user” is authenticated as it is. I can't do that.

  Therefore, in the present embodiment, the mobile mail address is registered in advance in the user table 4 in association with the terminal ID of the mobile phone 6 of the “user”, and authentication by the terminal ID is performed at the time of login and mail check request. If it fails (S005-NO, S503-NO), the mobile phone 6 is requested to send a blank email (S006, S504, S401), and the cellular phone is sent from the sender email address of the sent blank email. 6 is acquired (S402 to S403), and if the acquired mail address is registered in the user table, it is temporarily recognized that the authentication has been made (S405-YES), for further confirmation. Then, an e-mail describing a registration URL with a confirmation keyword as a parameter is transmitted to the mobile mail address (S 07) When a message transmitted by the browser when the registration URL is operated is received, the mobile email address is the new mobile phone of the “user” on the basis that the confirmation keyword is included in the message. It is possible to authenticate that the telephone 6 is being used continuously, that is, that the operator of the new mobile phone 6 is the “user”. That is, the CPU 10 of the service host computer 1 that executes these processes according to the various programs 14 to 16 corresponds to an authentication unit.

  If a “user” who is not a “member” changes the mobile mail address at the same time as the mobile phone 6, the “user” can no longer be automatically authenticated. However, as described above, when the “user” who has made such a change is also a “member”, the member ID can be authenticated by the authentication host computer 2.

  As described above, according to the present embodiment, when the terminal ID of the mobile phone 6 is used to realize simple authentication in the mailing list service using the mobile phone, the terminal of the mobile phone 6 used by itself once. Even when the “user” who registered the ID changes the model of the mobile phone 6 (exchange), authentication can be performed using the mobile mail address registered in advance. In addition, this authentication includes first-stage authentication (authentication of whether the sender address of the empty mail requested to the mobile phone 6 matches a pre-registered mobile mail address), and second-stage authentication. Since this is performed by (authentication of whether or not a message including the confirmation keyword returns after sending an email describing a URL including the confirmation keyword to the mobile mail address), there is no problem in reliability.

The block diagram which shows schematic structure of the computer network which is embodiment by this invention Table showing data structure of ISP member table The figure which shows the data structure of the mailing list information table Table showing data structure of user table Table showing data structure of temporary account table Table showing data structure of new user temporary table Table showing data structure of mailing list relation table Table showing the data structure of the invitation table Table showing data structure of mobile change information table Table showing the data structure of the email address change information table Flow chart showing processing upon reception of service request message Flow chart showing processing upon reception of service request message Flow chart showing processing upon reception of service request message Flow chart showing processing upon reception of service request message Flow chart showing processing upon reception of service request message Flow chart showing processing upon reception of service request message The flowchart which shows the authentication processing subroutine performed in S006 of FIG. 11 and S504 of FIG. The flowchart which shows the authentication processing subroutine performed in S006 of FIG. 11 and S504 of FIG. Flow chart showing the process when receiving an email confirmation request message Flow chart showing processing when receiving a participation request message A flowchart showing the authentication process executed by the authentication host computer Figure showing the service top screen Figure showing the opening alert screen Figure showing the authentication screen Figure showing the re-login screen The figure which shows the portable terminal information update screen Figure showing email address confirmation screen Figure showing the confirmation screen Figure showing the completion screen Figure showing the registration confirmation screen Figure showing the setting completion screen Figure showing the mobile information update screen Figure showing the registration information update screen Figure showing the email address change screen Figure showing member top page Diagram showing list display screen Figure showing a single display screen Figure showing the archive screen Figure showing the email address confirmation screen Figure showing the participation completion screen Figure showing my page

Explanation of symbols

1 Host computer for service 2 Host computer for authentication 6 Mobile phone 10 CPU
12 Memory 11 Communication Adapter 13 Hard Disk 15 Service Host Program 16 Mail Server Program 18 Table 19 ML Storage Directory N Internet Network M Mobile Internet Network

Claims (5)

When a browsing request for a predetermined web page is received from a plurality of portable terminals each having a unique terminal ID and an email address and having an Internet browsing function and an email transmission / reception function, screen data of the web page is displayed. A user authentication mechanism for authenticating a user who operates the mobile terminal to respond,
For each individual user, a storage device that records the terminal ID of the user's mobile terminal and the e-mail address;
Upon receiving the web page browsing request message transmitted from any portable terminal, terminal ID obtaining means for obtaining the terminal ID from the portable terminal;
When the terminal ID acquired by the terminal ID acquisition unit is registered in the storage device, the screen data of the web page is returned, and when the terminal ID is not registered in the storage device, Requesting transmission of an e-mail to the portable terminal and receiving an e-mail transmitted by the portable terminal in response to the request, only when the transmission source address of the e-mail is registered in the storage device A user authentication mechanism comprising: authentication means for responding to screen data of the web page. Said authentication means, wherein, when the source address of the e-mail is registered before Kiki憶apparatus further addressed the transmission source address, e-mail describing the URL of the self-addressed including predetermined parameters 2. The user authentication mechanism according to claim 1, wherein, when an address is transmitted and a message addressed to the URL is received, the screen data of the web page is responded. The predetermined parameter is an actively generated keyword, and the authentication unit stores the generated keyword in the storage device, and when the message is received, the keyword is included in the URL of the message. 3. The user authentication mechanism according to claim 2, wherein screen data of the web page is returned as a response. The authentication mechanism, when the source address of the electronic mail has been registered in the storage device, the terminal the terminal ID acquired by the ID acquisition means, before in association with the transmission source address crisis憶The user authentication mechanism according to claim 1, wherein the user authentication mechanism is overwritten. A plurality of users are registered for each individual mailing list among a plurality of portable terminals each assigned a unique terminal ID and an electronic mail address and having an Internet browsing function and an electronic mail transmission / reception function. When a mailing list account that is an e-mail address is assigned and an e-mail addressed to a mailing account of the mailing list is received from a mobile terminal of a user registered in any of the mailing lists, the mobile phones of all the users registered in the mailing list are received. When the e-mail is forwarded to the terminal and a browsing request for the web page dedicated to the mailing list is received from the user's mobile terminal registered in any mailing list, the mailing list that responds to the screen data of the web page is returned. A user authentication mechanism in door service,
For each user, a first storage device that records the identification information of the user, and the terminal ID and the e-mail address of the mobile terminal of the user;
For each individual mailing list, a second storage device that records the identification information of each user who is a member of the mailing list and the identification information of the mailing list;
A terminal ID acquisition means for acquiring the terminal ID from the mobile terminal when receiving a browse request message for a web page dedicated to any mailing list transmitted from any mobile terminal;
If the terminal ID obtained by the terminal ID acquisition unit is registered in the first storage device, identification information of the user in association with the terminal ID in the first storage device is the first If the terminal ID is not registered in the first storage device in response to the screen data dedicated to the mailing list associated with the identification information in the storage device 2, an e-mail is sent to the portable terminal. When the electronic mail transmitted by the portable terminal is received in response to the request, the first address is transmitted only when the transmission source address of the electronic mail is registered in the first storage device. and identification information of a user associated with the source address of the electronic mail is the identification information in said second storage device associated with the storage device User authentication mechanism, characterized in that it comprises an authentication means responsive mailing list dedicated screen data that.