JP2017073113A - Administration system and communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide techniques that allow bill transmission, payment and the like to be performed with a portable terminal and also allow flexible change of a payment environment, while using an SMS.SOLUTION: An SMS transmission of an SMS document, which comprises an SMS text and a specific URL specific to each SMS transmission, is performed to a phone number of a portable terminal obtained from a provider server. A URL access condition allowing setting of multiple conditions is set for the destination of the specific URL. When access matching the URL access condition is performed from the portable terminal through a network line, prescribed display is presented to the portable terminal, whereas when access not matching the access condition is performed, the prescribed display is not presented to the portable terminal.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a payment method for a product using a short message service (hereinafter referred to as “SMS”) of a mobile terminal, a method for providing a product using a short message service of a mobile terminal, and a management system used in the method, Regarding the contact system.

  Bills for utilities such as gas and electricity bills are sent to each home by mail. If the invoice can be sent using the communication network instead of sending by mail, the sending side can reduce the cost of printing and mailing. Specifically, if bill data is sent to each individual mobile terminal (mobile phone, smart phone, etc.) using the communication network of the mobile terminal, payment at a convenience store or payment by the mobile terminal itself Can be useful.

  When sending invoice data or the like to a mobile terminal, it is conceivable to send it to an e-mail address. However, competition for user acquisition among telecommunications carriers (hereinafter referred to as “carriers”) is fierce, and various preferential measures are taken for users who transfer from other carriers. There are many users. Since the domain of the email address differs depending on the carrier, the bill data cannot be delivered if the email address of the mobile phone user is changed by changing carriers.

  On the other hand, a mobile terminal provided by a carrier generally has an SMS function. SMS is a service that designates a telephone number as a destination between portable terminals and transmits a short message. Unlike mail addresses, even if the carrier changes due to number portability, the phone number does not change. Therefore, SMS using the phone number of the mobile terminal can use the same destination for customers who have changed carriers. In addition, since SMS uses a communication line of a mobile terminal without going through the Internet, it also has an advantage of high real-time performance and safety.

  However, since SMS has a limited number of characters to be sent, there is a disadvantage that the number of characters is small in order to send bill data. Recently, there are cases where a maximum of 670 characters can be transmitted at one time, but when transmitting to a mobile phone, only about 70 characters can be transmitted. Therefore, it is difficult to send bill data by SMS.

  Therefore, it is conceivable to send an URL using SMS instead of an email address and send data such as an invoice to a portable terminal (Patent Document 1).

Japanese translation of PCT publication No. 2008-511667 Japanese Patent No. 5401593

  However, there is a time lag between the transmission of a URL by SMS and the access to the URL, and it has not been possible to cope with various situations that occur during that time.

  The present invention makes it possible to use SMS to make a payment by sending an invoice, to provide a product, to provide a product, etc., and to flexibly change the settlement and product provision environment. It is an object of the present invention to provide a management system and a contact system that can be used.

In order to solve the above problems, the present invention has the following configuration.
(1) The present invention is a management system that is connected to an operator server and a carrier and is connected to a mobile terminal through the carrier, and includes an SMS text, an SMS text, SMS data receiving means for receiving SMS data having the telephone number of the portable terminal as a destination to which the SMS text is sent, the SMS text of the SMS data received by the SMS data receiving means, and the SMS SMS transmission means for sending an SMS document having a unique URL for each transmission to the portable terminal of the telephone number of the SMS data, URL access conditions are set in the access destination of the unique URL, and the portable When the unique URL is accessed from a terminal via a network line, the URL access condition is met. Te is a management system, characterized in that it comprises a URL access means for accessing the different URL.

  (2) Further, the present invention is the management system according to (1), wherein the unique URL includes a predetermined URL determined for each business operator and a unique character string unique to each SMS transmission.

  (3) Further, the present invention is the management system according to (1) or (2), wherein the URL access condition can be changed or added after the SMS transmission.

  (4) The present invention is the management system according to any one of (1) to (3), wherein the URL access condition is determined for each SMS transmission.

  (5) In the management according to any one of (1) to (4), the URL access condition includes information determined for each SMS transmission and a condition for sorting according to the information. System.

  (6) In the present invention, the URL access condition is a condition related to a deadline date, a condition related to payment completion, a condition related to the address of the mobile terminal owner, or a condition related to age. The management system according to any one of (1) to (5).

  (7) Further, the present invention is a communication system comprising the provider server and the management system according to any one of (1) to (6).

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to perform payment of goods and provision of goods simply and safely by utilizing the SMS function of the portable terminal which a consumer has.

It is a figure which shows the whole structure containing the management system and contact system in this invention. It is a figure explaining the billing data memorize | stored in the provider server. It is a figure explaining the management claim data memorize | stored in the management server. It is a flowchart which shows the production | generation process of specific URL. It is a figure explaining a URL access condition storage table. It is a figure which shows the whole flow regarding this invention. It is a figure which shows the example of a display of the portable terminal 40 when an SMS document is received. It is a flowchart which shows URL access condition check. It is a figure which shows the notification screen display of the portable terminal.

  With reference to FIGS. 1-9, the communication system 1 which concerns on embodiment of this invention is demonstrated.

  FIG. 1 is a diagram showing an overall configuration including a management system and a contact system 1 according to the present invention. The overall configuration including the present invention includes provider servers 10 and 11, a management server (management system) 20, carriers 30 and 31, and portable terminals 40 and 41. The communication system 1 includes business server 10 and 11 and a management server 20. The company servers 10 and 11 are servers of each company and are normally managed by the company. The management server 20 is a management system according to the present invention and is a manager's server, and is connected to a plurality of provider servers 10 and 11.

  The management server 20 is connected to the portable terminal 40 via the carriers 30, 31,. The management server 20 is connected to a plurality of business operator servers 10, 11,. .. And the management server 20, carriers 30, 31,... Are connected by a dedicated line or an Internet line after ensuring security. In addition, a normal mobile phone line and a network line are used between the carrier 30 and the mobile terminal 40 and between the carrier 31 and the mobile terminal 41. The network line is a line connected to the Internet via carriers 30 and 31.

  The enterprise servers 10, 11,... Are servers that the enterprise has. The business may be a business that charges a fee by performing meter reading of gas, water, electricity, etc., or a business that sells products. The business assumed mainly is a business that charges or pays to the owner of the mobile terminals 40 and 41, but may be other business. In the case of a business that charges a fee, the management server 20 receives billing data from the business servers 10, 11,... Send to. The mobile terminal 40 is a device (such as a mobile phone or a smartphone) capable of receiving SMS, and is connected to the carrier 30 via a mobile phone line and a network line. Similarly, the portable terminal 41 is connected to the carrier 31 by a cellular phone line and a network line. In addition, a mobile phone line is provided between the carrier 30 and the carrier 31 so that a call and SMS can be performed between the mobile terminal 40 and the mobile terminal 41 using different carriers 30 and 31. ing.

Hereinafter, an embodiment in which a gas company charges a gas fee will be described.
FIG. 2 is a diagram for explaining billing data stored in the business operator server 10. The billing data, which is SMS data, is data for the gas company to charge the customer using SMS, and is transmitted from the gas company's company server 10 to the management server 20. The billing data includes “1. Business ID”, “2. Mobile number”, “3. SMS text”, “4. Authentication information”, “5. Product name”, “6. Usage amount”, “7. “Amount”, “8. Settlement means”, “9. Transmission date and time”, “10. URL access condition”, and “11. Remarks”. “1. Business ID” is an ID unique to each business that identifies each business. “2. Mobile number” is the telephone number (hereinafter referred to as “mobile number”) of the mobile terminal that is the billing destination to which the SMS text is sent. “3. SMS text” can be sent by SMS, for example, “Thank you for using <Notice of usage amount from OO Gas> Please check the usage amount at the following URL.” It is a sentence of length. “4. Authentication information” is a personal identification number for requesting personal identification number input when connecting from a mobile terminal to a URL sent by SMS, but information for authentication when automatic authentication is performed at the time of connection. It may be. “5. Product name” is gas because it is an example for the purpose of billing for gas in this embodiment. “6. Amount used” is the amount of gas used in this embodiment. “7. Amount charged” is an amount charged by the business operator to the customer. “8. Payment means” indicates payment means that can be used for payment, and is information such as convenience store payment, credit card payment, and payment by bank transfer. “9. Transmission date and time” is the date and time when SMS is transmitted. This “9. transmission date and time” is not limited to the date and time, but can be set to be “immediately” and transmitted to the portable terminals 40 and 41 by SMS as soon as the processing in the management server 20 is completed.

  “10. URL access condition” is a condition for determining whether or not to access a normal URL, such as accessing a URL different from a normal URL by the URL access means when a predetermined date and time has passed or payment is completed. It is. That is, this is a condition for determining whether or not to display a regular connection screen, for example, an input screen for a personal identification number, on the mobile terminals 40 and 41 when accessing the unique URL described later from the mobile terminals 40 and 41. In this embodiment, since the access destination of the unique URL is the management server 20, URL access conditions are set in the management server 20.

  The business server 10 creates such billing data and transmits it to the management server 20.

  In addition, the provider server 10 only needs to have the above function, and does not need to be configured as one server. For example, the billing data may be stored in a plurality of servers, and a set of these servers corresponds to the business server 10. The same applies to the management server 20.

  FIG. 3 is a diagram for explaining management request data stored in the management server 20. The management billing data is formed based on the billing data received from the provider server 10 and stored in the management server 20. The management billing data includes “a. System ID”, “b. Default URL”, “c. Unique character string”, and billing data sent from the provider server 10. “A. System ID” is an ID unique to each management billing data assigned to each billing data received from the provider server 10. Individual data in the management request data such as “a. System ID” or “1. business ID” of the request data may be stored as one table, but is associated with “a. System ID”. The individual data may be stored discretely in association with “a. System ID”.

  “B. Default URL” is a URL defined for each business operator. A default URL is selected from the business ID of the received billing data and stored as “b. Default URL” in the management billing data.

  “C. Unique character string” is a unique character string provided for each system ID, and the same unique character string is not associated with a plurality of system IDs. Then, a unique character string is connected after the default URL to generate a unique URL.

  In order to transmit SMS from the management server 20 that is not a mobile terminal to the mobile terminal, the SMS is transmitted to a carrier to which the mobile terminal is connected (hereinafter, information specifying this carrier is referred to as “carrier information”). There is a need. However, since it is secret information linked to personal information, an administrator who is generally not a carrier cannot obtain carrier information directly from the carrier. In the present embodiment, the carrier is specified as carrier information by the difference in the disconnection message or the like returned when the call setting message is transmitted with the mobile number (Patent Document 2).

If the carrier information can be obtained from the carrier by the individual mobile number, the carrier information thus obtained may be used.
Based on the carrier information obtained in this way, the carrier connected to the portable terminal is specified, and the SMS is transmitted to the carrier.

FIG. 4 is a flowchart showing a unique URL generation process. In the present embodiment, first, a random 8-digit character string made up of uppercase and lowercase letters and halfwidth numerals of a half-width alphabet is created by a random value generation function (step S1). Next, the management server 20 checks whether there is a unique character string that is already stored in association with another system ID. If it exists, it is generated again (step S2). If it does not exist, it is stored as management request data in association with the system ID as a unique character string (step S3).
Then, a unique character string is added after the default URL to generate a unique URL (step S4), which is used for a document transmitted by SMS.

In step S4 of FIG.
https://smss.jp/ag/
Is the default URL determined by the operator,
********
Is a random 8-digit unique character string made up of uppercase and lowercase letters and halfwidth numbers.
The default URL
ag /
Represents an individual operator.

  As described above, the same unique URL and unique character string are not set in a plurality of system IDs. The system ID is provided for each SMS transmission, and a unique URL and a unique character string are uniquely set for each SMS transmission.

  FIG. 5 is a diagram for explaining the URL access condition storage table. The URL access conditions are stored in association with “a. System ID” in the URL access condition storage table as shown in FIG. “10-1. Expiration date / time” indicates the expiration date / time when the URL can be accessed. When the access to the management server 20 by the unique URL from the portable terminals 40 and 41 has passed the expiration date and time, the password input screen and the gas usage notification screen are not displayed.

In addition, when the payment is completed, such as when the payment of the gas fee is completed, the password input screen and the gas usage amount notification screen are not displayed by “10-2. Payment completion information”.
This eliminates the possibility of double payments.

  In addition, “Billing postponement information” can be included in the URL access conditions. For example, even if a unique URL is transmitted by SMS for billing a utility bill, billing may be delayed if a wide-area disaster such as an earthquake occurs. In this case, the business operator can determine the target person to postpone the charge from the address of the owner of the portable terminal, and pass it to the administrator who operates the management server 20 as the postponement of charge information. As shown in FIG. 5A, the administrator stores the postponement charge information in association with each system ID in the URL access condition storage table. Then, even if there is access to the unique URL from the mobile terminals 40 and 41, a screen that leads to billing is not displayed.

  Further, as shown in FIG. 5B, the address of the customer who is the owner of the mobile terminal can be stored in the URL access condition storage table. In that case, it is possible to pass to the administrator who operates the management server 20 billing postponement region information indicating which region is postponed from the business. The management server 20 determines whether “10-3. Customer address” applies to the area of the postponement charge area information, and stores the postponement of charge in “10-4.

  In addition to the address, in the URL access condition storage table, the request grace information is generated and stored according to the customer's age, or the grace age and the individual customer age are stored, and the request is postponed according to the age. Also good.

  In the URL access condition storage table, as shown in FIG. 5A, various identification information is stored in addition to the postponement billing information, and when the unique URL is accessed, a screen connected to the billing by the URL access means It is possible to divide whether to access the URL or to access the URL of inaccessible display.

  As shown in FIGS. 5A and 5B, a plurality of conditions can be set as URL access conditions. Thus, for example, not only the expiration date of URL access but also payment completion information can be managed, and further, it can be managed by billing grace and various identification information. The URL access condition can be changed after the SMS transmission. For example, the expiration date and time can be extended or shortened after SMS transmission. Further, the postponement billing information is set after the SMS transmission. As described above, the present invention is advantageous in that the URL access condition can be set or changed without performing additional SMS transmission even after SMS transmission.

FIG. 6 is a diagram showing an overall flow relating to the present invention.
The business operator creates billing data (step S11) and stores it in the business operator servers 10 and 11. Then, the company servers 10 and 11 transmit billing data that is SMS data to the management server 20 (step S12). When the billing data is received by the SMS data receiving means, the management server 20 assigns a system ID to each SMS to be sent, and sends it back to the business servers 10 and 11 as a reception proof (step S13). Further, the management server 20 selects a corresponding default URL from the business operator ID in the billing data, stores it as management billing data in association with the system ID, generates a unique character string as described above, and associates it with the system ID. And stored as management billing data (step S14).

  When it is time to transmit the management server 20 according to the transmission date and time information of the management request data, the management server 20 transmits an SMS document composed of the SMS text and the unique URL by the SMS transmission means. This transmission is an SMS transmission. At that time, the management server 20 transmits a call setting message to an appropriate carrier 30 toward the mobile number in the billing data, that is, makes a call (step S15) and receives a reply such as a disconnect message (step S16). . The management server 20 identifies the carrier 30 to which the portable terminal 40 is connected from the disconnect message or the like and sets it as carrier information (step S17). In accordance with the carrier information, the SMS document is transmitted to the carrier 30 to which the portable terminal 40 is connected (step S18). The carrier 30 transmits the SMS document to the mobile terminal 40 via the mobile phone line (step S19).

  FIG. 7 is a diagram illustrating an example of display on the portable terminal 40 when an SMS document is received. The SMS document will be displayed in the SMS text as “Thank you for using <Announcement of usage amount from OO Gas> Please check the usage amount at the URL below”, and the unique URL is “https : //smss.jp/ag/******** "is displayed.

  When the owner of the mobile terminal 40 viewing the SMS document performs a URL selection operation that touches the unique URL for confirmation (step S20), the mobile terminal 40 attempts to access the unique URL via the network line (step S20). S21). A unique URL is sent from the carrier 30 to the management server 20 via the Internet. The management server 20 performs URL access condition check (step S22).

  FIG. 8 is a flowchart showing the URL access condition check (step S22). The management server 20 reads the unique character string from the unique URL as shown in FIG. 8 and checks whether there is a system ID associated with the database (step S22-1). If there is a linked system ID, the unique character string is not linked to a plurality of system IDs, and therefore one system ID is specified. Further, the URL access condition is checked by the URL access condition storage table of FIG. If “1. Expiration date / time” set in the URL access condition has passed, or “2. Payment completion information” or “3. The URL is accessed to display that the mobile terminal 40 cannot be accessed (step S22-2).

  The display at this time may be changed by changing the URL to be accessed according to a condition that does not satisfy the URL access condition. For example, when the deadline date has passed, “URL access deadline has passed. Please contact XXX.” May be displayed on the mobile terminal 40, or when there is payment completion information, “ You have already paid, thank you. " In addition, if the request is postponed, you may display “This request has been postponed due to circumstances. We will contact you later regarding this matter.”

  If the URL access condition is satisfied, a normal URL is accessed by the URL access means, and a login screen is displayed on the portable terminal 40 via the network line (step S22-3). When the authentication code is input here (step S23), it is sent to the management server 20 via the network line (step S24), and the management server 20 checks the authentication information of the management billing data against the authentication code (step). S25). When authenticated, the contents of the notification screen are generated from “6. Usage amount”, “7. Amount charged”, “8. Payment means”, “11. Remarks”, etc. of the management request data stored in the management server 20 Then, the information is transmitted to the portable terminal 40 via the network line (step S26), and the portable terminal 40 displays a notification screen (step S27).

  FIG. 9 is a diagram showing a notification screen display of the mobile terminal 40. In this example, the amount of gas used and the amount charged are displayed, and you can select from three payment methods: “Pay at convenience store”, “Pay by credit card”, and “Pay by bank transfer”. ing. What can be displayed as selectable payment means can be changed by setting “8. Settlement means”.

  In the above embodiment, the management server 20 manages the product name, usage amount, billing amount, payment means, etc., and generates a notification screen from these, assigns a URL, and stores it in the management server 20. You may memorize | store a screen etc. in the provider server 10. FIG. In that case, the URL of the notification screen or the like is stored as management request data of the management server 20 and transferred from the access to the unique URL to the URL of the notification screen or the like stored in the business server 10.

  Moreover, although the said Example is an example regarding the payment of goods called gas, it can be used also for provision of goods. For example, in the case of insurance products, personal information such as address and age is required when insurance is applied to an operator by telephone. Therefore, when the operator hears the mobile number and inputs it to the business operator server 10, the unique URL is sent to the applicant's mobile terminal via SMS via the management server 20. Then, the applicant accesses from the unique URL and inputs an address, age, and the like. Thereby, since personal information is memorize | stored in a system without a person, personal information does not leak through a person. Even in procedures that require personal information such as issuance of membership cards, personal information is not leaked. In this case as well, when a member application is made at the telephone or convenience store and the mobile phone number is transmitted, it is input to the terminal, and a unique URL is sent from the business server 10 to the mobile terminal of the applicant via the management server 20 via SMS. The personal information is input by accessing from the unique URL. As a result, personal information is handled without human intervention, and security is improved. In addition, the management server 20 displays statuses such as SMS transmission (invoice has been issued), access to a unique URL (invoice has been viewed), and settlement (payment has been completed). Centralized management is possible.

1 Contact System 10, 11 Business Server 20 Management Server (Management System)
30, 31 carrier 40, 41 portable terminal

Claims (7)

A management system connected to a carrier server and a carrier and connected to a mobile terminal via the carrier;
SMS data receiving means for receiving SMS data having the SMS text and the telephone number of the portable terminal that is associated with the SMS text and is a destination to which the SMS text is sent, from the provider server;
SMS sending means for sending an SMS document having the SMS text of the SMS data received by the SMS data receiving means and a unique URL unique to each transmission of the SMS to the portable terminal having the telephone number of the SMS data When,
URL access means for setting a URL access condition for the access destination of the unique URL, and allowing access to a different URL according to the URL access condition when the mobile terminal is accessed via the network line And a management system comprising:   The management system according to claim 1, wherein the unique URL includes a default URL determined for each business operator and a unique character string unique to each SMS transmission.   The management system according to claim 1 or 2, wherein the URL access condition can be changed or added after the SMS transmission.   4. The management system according to claim 1, wherein the URL access condition is determined for each SMS transmission.   5. The management system according to claim 1, wherein the URL access condition includes information determined for each SMS transmission and a condition for sorting based on the information.   6. The URL access condition according to claim 1, wherein the URL access condition is a condition related to an expiration date / time, a condition related to payment completion, a condition related to an address of a portable terminal owner, or a condition related to age. A management system according to any one of the above.   A communication system comprising the provider server according to any one of claims 1 to 6 and the management system.

Images