JP2001318842A - System for distributing data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data distributing system for allowing a client terminal to safely and surely receive the distribution of data by reducing the number of ports and sockets. SOLUTION: When it is judged that a client terminal 20 has a right to use this system, an authentication key is transferred from an authentication server 21. Then, the client terminal requests the establishment of an update notifying route with the authentication key to an update notification relay server 22, and when it is approved, an update notification route is established between the client terminal and the update notification relay server. At the time of receiving the distribution service of the data from a data distributing agent in this state, the client terminal transmits a service request to a service registering server 24. When the client terminal is stored in a customer data base 25, the client terminal can receive the distribution of information from a desired service distributing server 23.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a data distribution system for distributing information via the Internet.

[0002]

2. Description of the Related Art FIG. 5 is a schematic diagram showing the relationship between a client terminal connected to a customer's LAN and a server that distributes data to the client terminal via the Internet. FIG. 5 shows a case where a plurality of client terminals are connected to a customer's LAN, and each of them receives information distribution from a server by a unique protocol.

[0003]

In the case shown in FIG. 5, if the protocol used by each client terminal is different, it is necessary to prepare a socket for each protocol. Also, in the case as shown in FIG.
For each port number. Also, if there is only one port, if this port is closed by a firewall for security, none of the clients can receive information from outside.

The present invention has been made in view of such a technical background, and an object of the present invention is to reduce the number of ports and sockets so that a client terminal can receive data delivery safely and reliably. It is to provide a data distribution system that can do the same.

[0005]

According to one aspect of the present invention, there is provided a data distribution system for distributing information from a distribution terminal to a client terminal via the Internet. A relay unit is provided between the client terminal and the client terminal, the distribution terminal adds predetermined header information to information to be distributed and sends the information to the relay unit, and the relay unit refers to the header information, The information is transmitted to a predetermined client terminal.

According to a second aspect of the present invention, in the data distribution system according to the first aspect, the client terminal desiring to use the system is authenticated as having the right, and the client terminal is requested to transmit information to the client terminal. An authentication unit for providing authentication information necessary for receiving distribution is provided.

According to a third aspect of the present invention, in the data distribution system of the second aspect, the authentication information is provided for each session.

According to a fourth aspect of the present invention, in the data distribution system according to the second or third aspect, the client terminal provided with the authentication information transmits the authentication information and the client information to a distribution terminal that wants to receive the information distribution. The terminal sends distribution destination information including the IP address of the relay means to have the information relayed, and the distribution terminal receiving this information sends the information to be distributed to the relay means corresponding to the IP address. It is characterized by transmitting.

According to a fifth aspect of the present invention, in the data distribution system according to any one of the second to fourth aspects,
For the client terminal whose use of the system has been approved by the authentication means, it is further determined whether or not the client terminal has been registered to be able to receive information distribution from a distribution terminal that wants to receive information distribution. It is characterized in that a registration determining means for permitting information distribution only to registered client terminals is provided.

According to a sixth aspect of the present invention, in the data distribution system according to any one of the first to fifth aspects,
Each client terminal has an API,
The relay unit transmits information sent from the distribution terminal to the client terminal via an API.

According to a seventh aspect of the present invention, in the data distribution system according to any one of the first to sixth aspects,
The relay means transmits the content of the information sent from the distribution terminal to the client terminal without interference.

According to an eighth aspect of the present invention, in the data distribution system according to any one of the first to seventh aspects,
The client terminal has a function of transferring information transmitted from the distribution terminal to a specific portable information terminal.

[0013]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram illustrating an overall configuration of a data distribution system according to the present embodiment.

The data distribution system according to the present embodiment
Client terminal 20, authentication server 21 (corresponding to "authentication means" in the claims), update notification relay server 2
2 (corresponding to “relay means” in claims), service distribution server 23 (corresponding to “distribution terminal” in claims), service registration server 24 (“registration determination means” in claims) , Etc.), which are mainly connected to the Internet. Further, a customer database 25 is connected to the service registration server 24. Here, the client terminal 20 belongs to a customer who receives data distribution, and is connected to the LAN 11 constructed by the customer. The authentication server 21 and the update notification relay server 22 are managed by a distribution broker. The service distribution server 23, the service registration server 24, and the customer database 25 are managed by a data distributor. However, such a membership relationship is merely an example, and which client terminal or server terminal belongs to which is not particularly limited. For example, the authentication server 21 and the update notification relay server 22 may belong to different companies, or the service registration server 24 and the customer database 25 may belong to different companies. Although FIG. 1 shows one customer and one data distributor for convenience, in an actual system, any number of customers and data distributors may subscribe to one distributor. it can.

In the above, the "data distributor" is a person who accumulates various data and distributes information to customers as necessary. Specifically, for example, a distributor who provides stock price information, There are various modes such as a company that provides exchange information, a company that provides weather information, and a company that distributes news in a specific field. As the number of data distributors who subscribe to this system increases, the types of information that can be provided as a whole system become rich, which leads to new customers subscribing. The “distribution broker” is a person who is entrusted by the data distributor and finally sends data to the client terminal 20 of the customer participating in this system. However, such a division of the type of business is merely an example, and for example, a data distributor may also serve as a distribution intermediary.

FIG. 2 is a diagram schematically showing how data is distributed from service distribution server 23 shown in FIG. 1 to client terminal 20 via update notification relay server 22. Although FIG. 2 shows a plurality of client terminals 20, for example, a case where a plurality of application programs are included in one client terminal can be similarly considered. As shown in FIG. 2, the port between the customer and the update notification relay server 22 is 1
The only thing that the customer puts on security by the firewall is the update notification relay server 2 used.
2 for each IP address. Therefore, even if there are a plurality of client terminals 20 on the customer side, only one socket is required for one IP address.

Each client terminal 20 has an API in advance.
(Application Program Interface) is installed. The API is, for example, the update notification relay server 22
This software is dedicated to this system and is prepared by a distribution intermediary that manages A dedicated protocol for transferring data is defined between the API and the update notification relay server 22.
2 is a service distribution server 2 according to this protocol.
3 from the client terminal 20
Send to PI.

Each client terminal 20 has installed therein a program for reading data sent from the service distribution server 23 and making the data available to the user. The API activates an application program corresponding to the type of data and causes the application program to read the received data. Each application program is distributed from each data distributor when applying for data distribution to the data distributor, for example. Of course, other commercially available general application programs can be used as they are.

When the API of the client terminal 20 receives the data from the update notification relay server 22, the update notification relay server 22 looks at the header information added to the data, determines the application program to read the data, and determines the application program. Start the program. The update notification relay server 22 merely relays the data sent from the service distribution server 23 except for adding the header information, and does not interfere with the content at all. For this reason, any protocol can be used between the service distribution server 23 and the application program installed in the client terminal 20.

As described above, the update notification relay server 22 is provided between the client terminal 20 and the service distribution server 23, and data is exchanged between the update notification relay server 22 and the API in the client terminal 20. With this configuration, only one port is required to connect between the client terminal 20 and the update notification relay server 22. Accordingly, unlike the related art, it is not necessary to prepare a port for each different protocol, so that the configuration as viewed from the client terminal side is simplified, and the cost required for joining the system can be reduced.

When a customer wants to receive some kind of data distribution, he / she first applies to a distribution intermediary for use of this data distribution system. When the use of the system is approved, the client terminal 20 of the customer
Is registered in the authentication server 21 as having authority to use this system. At that time or thereafter, the user selects a necessary number of those who want to receive the data distribution service from a large number of data distributors providing various services. When the customer selects a data distributor who wants to receive the service, the customer database 25 of the service registration server 24 belonging to the data distributor stores
Necessary information about the customer is stored. However, the IP address of the client terminal 20 is not notified to any of the service distribution server 23, the service registration server 24, and the customer database 25 belonging to the data distributor.

With the above procedure, the customer is ready to receive various data distribution services. Next, a procedure until the client terminal 20 belonging to the customer actually receives data distribution from the service distribution server 32 belonging to a certain data distributor will be described. FIG. 3 is a diagram showing this procedure.

First, the client terminal 20 requests the authentication server 21 for an authentication process. In this case, the client terminal 20 transmits information required to identify itself, such as an ID or a password, to the authentication server 21, and the authentication server 21 uses the system based on the information to allow the client terminal to use the system. It is determined whether or not the user has the authority to do so. As a result, when it is determined that the user has the authority, the authentication server 21 passes the “authentication key” to the client terminal. This client terminal 2
As a protocol for communication between the authentication server 21 and the authentication server 21, for example, HTTP (Hyper Text Transport)
Protocol).

This "authentication key" is valid during the session, that is, while the client terminal continues to use the system this time. When the use is interrupted, the authentication key is invalidated once, and then the system is re-used. When using, start with the process of obtaining a new authentication key.

On the other hand, if the authentication server 21 determines that the client terminal does not have authority, the authentication server 21 does not perform a process of returning an authentication key to the client terminal. Therefore, if an unauthorized person tries to use the system, it is excluded at this stage.

When the client terminal 20 receives the authentication key from the authentication server 21, the client terminal 20 next establishes an update notification route to the update notification relay server 22 with the authentication key received from the authentication server 21. Request. Although only one communication notification relay server 22 is shown in FIG. 1, a plurality of update notification relay servers are actually prepared, and a currently vacant update notification relay server is selected from among them. A request to establish an update notification route is sent from the client terminal there. Upon receiving the update notification route establishment request from the client terminal, the update notification relay server 22 performs necessary processing, and then returns a response to the client terminal indicating that the connection has been completed. This response includes the IP address of the update notification relay server used when the client terminal actually receives data distribution later among the plurality of update notification relay servers 22. A dedicated protocol is used for communication between the client terminal 20 and the update notification relay server 22 at this time.

As described above, the client terminal 20
The above-described processing (the processing up to the connection completion response) performed between the authentication server 21 and the update notification relay server 22 is almost instantaneously completed by the application program installed in the client terminal 20 and the update notification relay server 22. There are few actions that the user has to take towards the console.

At this stage, an update notification route is established between the client terminal and the update notification relay server 22. This update notification route is valid until the client terminal terminates the connection, during which the update notification relay server 22 checks whether the client terminal is functioning effectively, for example, every 5 seconds or every 10 seconds. Is sent to the API installed on the client terminal. When the client terminal receives this, it returns a corresponding message to the update notification relay server 21. As described above, this update notification route requires only one port even when a single customer LAN has a plurality of client terminals.

In a state where the update notification route is established with the update notification relay server 22, the client terminal 20
If the user wants to receive a data distribution service from any of the data distributors, the server first transmits a service request to the service registration server 24 belonging to the data distributor. At this time, the client terminal 20 transmits the authentication key that has already been acquired and the IP address of the update notification relay server 23 that has established the update notification route with itself. HTTP is used for the exchange between the client terminal 20 and the service registration server 24 at this time.

The service registration server 24 is provided with a customer database 25 storing client terminals that can receive the data distribution service. The service registration server 24 refers to the customer database 25 and checks whether or not the client terminal that has transmitted the service request is stored in the customer database 25. Therefore, even if the authentication server 21 recognizes that the user is authorized to use this system, a client terminal that is not stored as a customer in the customer database 25 cannot receive the data distribution service.

If the client terminal that has transmitted the service request is stored in the customer database 25, the service registration server 24 issues a registration request to the service distribution server 23 belonging to the same data distributor. The information sent at this time is the authentication key and the IP address of the update notification relay server. When receiving the registration request from the service registration server 24, the service distribution server 23 registers the client terminal. When the registration is completed, the service distribution server 23 returns a response to that effect to the service registration server 24. At this stage, the client terminal can receive information distribution from the desired service distribution server 23.

When the information to be distributed occurs, the service distribution server 23 distributes the information to the registered client terminals. At this time, the service distribution server 23 does not directly distribute the information to each client terminal, but always distributes the information. It is distributed via the update notification relay server 22 managed by the broker. As described above, none of the service distribution server 23, the service registration server 24, and the customer database 25 belonging to the data distributor are informed of the IP address of the client terminal. The service distribution server 23 and the like are notified only of the authentication key and the IP address of the update notification relay server 22.

For this reason, what the service distribution server 23 performs to the update notification relay server 22 of the IP address requests the client terminal corresponding to the authentication key to distribute the data to be transmitted. Only. Upon receiving the data distribution request together with the authentication key from the service distribution server 23, the update notification relay server 23 first transmits an update notification route based on the authentication key between the client terminal and the client terminal based on the authentication key. It is determined whether or not has been established. If the update notification route has been established, the update notification relay server 2
2 deletes the IP address identifying itself from the data sent from the service distribution server 23, adds predetermined header information, and transmits the data to the predetermined client terminal 20. Thus, the client terminal 20 can receive necessary data distribution.

In this case, as described above, the update notification relay server 22 does not interfere with the contents of the data at all, and simply transfers the data based on the authentication key received from the service distribution server 23. For this reason, the service distribution server 23, if necessary,
2 can be transmitted to the client terminal via the update notification relay server 23, even if the information is encrypted based on the agreement between the client terminal and the client terminal. The client terminal can use the data by receiving the encrypted data as it is and decrypting it. As a result, a sufficient level of security can be ensured.

The client terminal 20 looks at the header information added to the head of the transmitted data and determines where the data came from. Then, an application program to use the data is activated and read. Thus, the user
You can use the information sent.

If the update notification relay server 22 has established an update notification route with a certain client terminal,
As described above, whether the client terminal is functioning effectively is checked every 5 seconds or every 10 seconds. Therefore, for example, when the client terminal 20 goes down due to a power failure or the like and the communication is interrupted due to a line failure or the like, the update notification relay server 22 detects that the client terminal is not functioning effectively. Then, this is notified to all the service distribution servers 23. When each service distribution server 23 receives information indicating that a specific client terminal has gone down, it determines whether or not it is distributing data to that client terminal. , The distribution of the data is stopped. As a result, it is possible to prevent a situation in which an unnecessary message is continuously sent and the transmission efficiency is reduced.

As described above, each client terminal does not receive information distribution directly from the service distribution server 23 having information to be distributed but has the service distribution server 23 via the update notification relay server 23. A major feature of the system of the present embodiment is that information is distributed. With this configuration, the number of customers and the number of data distributors increase, and the scale of the entire system increases, and even if the system spreads over a wide area, it can sufficiently cope with it. is there.

When the terminal is connected to the Internet, in addition to important mail, mail that is not important may be sent from various places. When such mails and the like increase, the labor for determining which information is necessary and which is unnecessary information increases. In such a case, when the system according to the present embodiment is introduced, as described above, the data distributor does not know the IP address of the client terminal at all, and the information sent to the client terminal always updates the update notification. Server 2
2, the client terminal can determine that the information sent via the update notification relay server 22 is sufficiently reliable, and
There is an advantage that information can be easily distinguished.

Further, if the client terminal is connected to the Internet, there is always a danger that a file infected with a computer virus can be sent from a site that impersonates a good intention. However, in the case of the system according to the present embodiment, since the participating data distributors are considered to have passed a certain screening standard set by the distribution broker, the data distributors are sent via the update notification relay server 23. It is extremely unlikely that the information has been infected by a computer virus, and in that sense, high security is guaranteed.

In addition, since the service registration server 23 is provided for each data distributor, even if a large number of accesses for distributing information to a certain data distributor are temporarily concentrated, a sufficient margin is provided. It is possible to respond.

The system shown in FIG. 1 can be applied to a system for notifying a viewer that a homepage on the Internet has been updated. It is assumed that a certain person or a certain company publishes a homepage on the Internet and updates the content on an irregular basis. Until now, even if the updated content contained important content, it was not easy to notify many viewers that the content was updated unless the viewer accessed the homepage. . In such a case, the viewer is asked to subscribe to the system shown in FIG. 1 as the client terminal 20, and when the content of the home page is updated, the creator sends the home page to the client terminal 20 from the service distribution server 23. Is updated together with the URL of the homepage, so that the viewer can quickly access the updated homepage simply by clicking on the URL upon receiving this on the client terminal 20. Become.

Further, the system shown in FIG. 1 is used for a mobile phone, a PHS, a PDA (Personal Digital Assistants).
By combining with a so-called portable information terminal, a system for new information distribution can be constructed. FIG. 4 shows an outline of such a system. The client terminal shown in FIG. 4 is the client terminal 20 shown in FIG. 1 and distributes information from the client terminal to the portable information terminal 29. Therefore, when viewed from the portable information terminal 29, the client terminal 2
0 acts as a server. It is assumed that software and hardware necessary for transferring information sent from the service distribution server 23 to the portable information terminal are installed in the client terminal 20, and necessary settings relating to these are already completed. .

At present, a service for providing various information on the Internet at the request of a user has already been put into practical use as a service for mobile phones. However, all of the existing services are prerequisites for receiving a service from a user calling a predetermined number from the user's side, and when an important event occurs, the information source side will inform the service as soon as possible. Never before. Therefore, even if an event that the user wants to know, for example, an event such as a large change in the stock price of a specific issue occurs, unless the user takes the action of calling the predetermined number by himself / herself, this will be the same. Could not know.

On the other hand, when the system shown in FIG. 4 is used, when important information for a specific user is generated, for example, when the stock price of a specific brand fluctuates beyond a certain ratio. Can be easily realized.
That is, when a predetermined event occurs, it is agreed in advance that the service distribution server 23 distributes the information to the client terminal 20 to the client terminal 20. Is set so that it is immediately delivered to the portable information terminal 29 when the information is received. By doing so, it is possible to obtain information whenever a certain event occurs, regardless of where the user is, except where radio waves do not reach.

As described above, one embodiment of the present invention has been described. However, the present invention is not limited to the above-described embodiment, and various modifications may be made within the scope of the invention described in each claim. Can be changed, and they are also included in the technical scope of the present invention.

[0046]

As described above, according to the present invention,
Providing relay means between the distribution terminal and the client terminal,
By distributing the data via the relay means, it is not necessary to directly connect the client terminal and the distribution terminal, thereby improving security, and the client terminal can trust the transmitted data. In addition, even if there are a plurality of protocols used between the distribution terminal and the client terminal, a single port can be used.

[Brief description of the drawings]

FIG. 1 is a diagram showing an overall configuration of a data distribution system according to an embodiment of the present invention.

FIG. 2 is a diagram schematically illustrating a state when data is distributed from the service distribution server 23 illustrated in FIG. 1 to the client terminal 20 via the update notification relay server 22.

FIG. 3 is a diagram showing a procedure until a client terminal receives data distribution from a service distribution server.

FIG. 4 is a diagram showing a configuration when the system of FIG. 1 is applied to a system for distributing information to a portable information terminal.

FIG. 5 is a schematic diagram showing a relationship between a client terminal connected to a customer LAN and a server that distributes data to the client terminal via the Internet.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 10 ... Internet 11 ... Customer LAN 20 ... Client terminal 21 ... Authentication server 22 ... Update notification relay server 23 ... Service distribution server 24 ... Service registration server 25 ... Customer database 29 ... Portable information terminal

Continuation of the front page F term (reference) 5B089 GA11 GA21 HA10 JA33 JB14 KA17 KB06 KB13 KC58 KG03 5K030 GA04 GA15 HA07 HC01 HC14 JA11 JT02 JT09 LD20

Claims (8)

[Claims] 1. A data distribution system for distributing information from a distribution terminal to a client terminal via the Internet, wherein relay means is provided between the distribution terminal and the client terminal, and the distribution terminal should distribute the information. A data distribution system, wherein predetermined header information is added to information and transmitted to the relay unit, and the relay unit refers to the header information and transmits the information to a predetermined client terminal. 2. An authentication means for authenticating that a client terminal desiring to use the system has the authority and providing the client terminal with authentication information necessary for receiving information distribution. The data distribution system according to claim 1, wherein the data distribution system is provided. 3. The data distribution system according to claim 2, wherein the authentication information is provided for each session. 4. A client terminal to which authentication information has been assigned is transmitted to a distribution terminal that wants to receive information distribution, including the authentication information and an IP address of a relay unit that causes the client terminal to relay information distribution. And destination information,
4. The data distribution system according to claim 2, wherein the distribution terminal having received the information transmits information to be distributed to a relay unit corresponding to the IP address. 5. A client terminal for which use of the system has been approved by the authentication means, and whether or not the client terminal has been registered to be able to receive information distribution from a distribution terminal that wants to receive information distribution. The data distribution system according to any one of claims 2 to 4, further comprising a registration judging means for judging the distribution of information and permitting distribution of information only to a client terminal registered in advance. 6. An API is mounted on each of the client terminals, and the relay unit transmits information sent from the distribution terminal to the client terminal via the API. Item 6. The data distribution system according to any one of Items 1 to 5. 7. The relay device according to claim 1, wherein the relay unit transmits the content of the information transmitted from the distribution terminal to the client terminal without any interference. Data distribution system. 8. The client terminal according to claim 1, wherein the client terminal has a function of transferring information sent from the distribution terminal to a specific portable information terminal. Data distribution system.