JP5476447B1 - Transfer condition changing device, program, information providing system, and transfer condition changing method - Google Patents

Abstract

Access to a server from a client terminal is given priority over other client terminals in accordance with a user attribute of the client terminal.
An identification information acquisition unit for acquiring terminal identification information for identifying a client terminal with which communication with a server has been established, and a packet transmitted from the client terminal identified by the terminal identification information acquired by the identification information acquisition unit The transfer condition held by the node that forwards the packet according to the transfer condition between the server and the client terminal that accesses the server, so that the packet is transferred to the server with priority over packets transmitted from other client terminals. A transfer condition changing unit.
[Selection] Figure 1

Description

  The present invention relates to a transfer condition changing device, a program, an information providing system, and a transfer condition changing method.

A system that distributes the load of a server using an open flow (sometimes referred to as a programmable flow) technology is known (see, for example, Patent Document 1).
(Prior art documents)
(Patent Literature)
(Patent Document 1) Japanese Patent Application Laid-Open No. 2011-170718

  Even when the load is distributed among a plurality of servers, the load may exceed the capacity of the system.

  In the first aspect of the present invention, an identification information acquisition unit that acquires terminal identification information that identifies a client terminal that has established communication with a server, and a client that is identified by the terminal identification information acquired by the identification information acquisition unit A node that forwards packets according to the forwarding conditions between the server and the client terminal that accesses the server holds it so that packets sent from the terminal are transferred to the server with priority over packets sent from other client terminals. There is provided a transfer condition changing device including a transfer condition changing unit for changing a transfer condition to be performed.

  In the second aspect of the present invention, at least a part of the transfer condition held by the node that transfers the packet according to the transfer condition between the server and the client terminal that accesses the server is predetermined with respect to the user life log information. A life log condition storage unit that stores the information in association with a specified condition and life log information of each user of one or more client terminals, and stores the life log information in association with terminal identification information that identifies each of the one or more client terminals. An identification information specifying unit that specifies terminal identification information stored in association with life log information that matches a predetermined condition with reference to the life log information storage unit, and a terminal identification specified by the identification information specifying unit A packet transmitted from a client terminal identified by information is referred to as a packet transmitted from another client terminal. In order to preferentially transfer to the server, the node forwarding condition changing device and a transfer condition changing unit for changing the transfer conditions to be held is provided.

  In a third aspect of the present invention, a program is provided for causing a computer to function as the transfer condition changing device. According to a fourth aspect of the present invention, there is provided an information providing system that includes the above-described transfer condition changing device and a server, and the server provides information to a client terminal via a network.

  In a fifth aspect of the present invention, a step of acquiring terminal identification information for identifying a client terminal with which communication with a server has been established, and a packet transmitted from the client terminal identified by the acquired terminal identification information A step of changing a forwarding condition held by a node that forwards a packet according to the forwarding condition between the server and the client terminal accessing the server, so that the packet is preferentially forwarded to the server over a packet transmitted from another client terminal. A transfer condition changing method is provided.

  In the sixth aspect of the present invention, at least a part of the transfer condition held by the node that transfers the packet according to the transfer condition between the server and the client terminal that accesses the server is determined in advance regarding the user life log information. And storing life log information corresponding to the terminal identification information for identifying each of the one or more client terminals. The terminal identification information stored in association with the life log information that matches a predetermined condition with reference to the section, and transmitted from the client terminal identified by the identified terminal identification information In order to transfer packets to the server with priority over packets sent from other client terminals Transfer condition changing method having the steps of changing the transfer condition to hold is provided.

  It should be noted that the above summary of the invention does not enumerate all the necessary features of the present invention. In addition, a sub-combination of these feature groups can also be an invention.

An example of information providing system 100 is shown roughly. An example of the information provision server 110 is shown schematically. An example of the flow table 300 of the node control apparatus 130 is shown. An example of the flow table 400 of the node 120 is shown. An example of the table 500 stored in the life log condition storage unit 242 is shown. An example of the table 600 stored in the life log condition storage unit 242 is shown. An example of the table 700 stored in the life log server 114 is shown. An example of the table 800 stored in the life log server 114 is shown. An example of the table 900 stored in the life log server 114 is shown. An example of operation | movement of the information provision system 100 is shown roughly. The other example of operation | movement of the information provision system 100 is shown roughly. 1 schematically shows an example of an information providing system 1200.

  Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. In addition, not all the combinations of features described in the embodiments are essential for the solving means of the invention. In the drawings, the same or similar parts are denoted by the same reference numerals, and redundant description may be omitted.

  FIG. 1 schematically shows an example of an information providing system 100. The information providing system 100 includes an information providing server 110, an authentication server 112, a life log server 114, a node 120, and a node control device 130. The information providing system 100 and the information providing server 110 may be an example of a transfer condition changing device. The life log server 114 may be an example of a life log information storage unit.

  Each of the information providing server 110, the authentication server 112, the life log server 114, the node 120, and the node control device 130 is an information providing device having a general configuration. The information providing server 110, the authentication server 112, the life log server 114, the node 120 and the node control device 130 may be realized by starting software that defines the operation of each unit. The information processing apparatus includes a data processing apparatus having a CPU, ROM, RAM, communication interface, an input device such as a keyboard, a touch panel, and a microphone, an output device such as a display device and a speaker, and a storage such as a memory and an HDD. And a device.

  Each of the information providing server 110, the authentication server 112, the life log server 114, the node 120, and the node control device 130 may be a virtual server or a cloud system. The functions of the information providing server 110, the authentication server 112, the life log server 114, the node 120, and the node control device 130 may be realized by a plurality of servers.

  In the present embodiment, the information providing system 100 and each part of the information providing system 100 will be described by taking as an example a case where each part of the information providing system 100 and the information providing system 100 is constructed on a virtual server. However, the information providing system 100 is not limited to this embodiment. Each of the information providing server 110, the authentication server 112, the life log server 114, and the node control device 130 may be constructed on a physically different information processing device, and the node 120 may be a physical switch. .

  In the present embodiment, the information providing server 110 transmits and receives information to and from the client terminal 20 and the client terminal 22 via the communication network 10 and the node 120. The information providing server 110, the authentication server 112, the life log server 114, the node 120, and the node control device 130 exchange information with each other via the communication network 12.

  Each of the communication network 10 and the communication network 12 may be a wired communication transmission line, a wireless communication transmission line, or a combination thereof. Each of the communication network 10 and the communication network 12 may be the Internet, a dedicated line, a wireless packet communication network, or a combination thereof.

  Each of the client terminal 20 and the client terminal 22 is communicably connected to the information providing server 110 via the communication network 10, the node 120, and the communication network 12. Each of the client terminal 20 and the client terminal 22 may be any device that can send and receive information to and from the information providing server 110. A personal computer, a mobile phone, or a mobile terminal (PDA, tablet, or notebook computer) in which Web browser software is installed. Or a laptop computer etc. can be illustrated.), A wireless terminal etc. may be sufficient.

  Each of the client terminal 20 and the client terminal 22 may be realized by activating software that defines the operation of each part of the client terminal 20 and the client terminal 22 in an information processing apparatus having a general configuration. The information processing device includes a data processing device having a CPU, ROM, RAM, communication interface, etc., an input device such as a keyboard, a touch panel, a microphone, a GPS information acquisition device, an acceleration sensor, and a gyro sensor, a display device, a speaker, You may provide output devices, such as a vibration apparatus, and memory | storage devices, such as memory and HDD. Each of the client terminal 20 and the client terminal 22 may be an application that operates on the same physical information processing apparatus and is identified by a different port number.

  The information providing system 100 provides information to at least one of the client terminal 20 and the client terminal 22 via the communication network 10. The information providing system 100 provides information to a client terminal that has established communication with the information providing server 110, thereby providing a service to the user of the client terminal.

  The information providing server 110 provides information to at least one of the client terminal 20 and the client terminal 22 via the communication network 10, the node 120, and the communication network 12. The information providing server 110 may control the transfer operation of the node 120. The information providing server 110 may control the transfer operation of the node 120 by changing a transfer condition that defines the transfer operation of the node 120.

  The information providing server 110 may control the transfer operation of the node 120 via the node control device 130. For example, the information providing server 110 newly generates a transfer condition that defines the transfer operation of the node 120 in accordance with the load status of the information providing server 110 or the service provided by the information providing server 110, and the generated new transfer The condition is transmitted to the node control device 130. The information providing server 110 requests the node control device 130 to set the transmitted new transfer condition as the transfer condition of the node 120. Thereby, the information providing server 110 can dynamically update the transfer condition of the node 120.

  For example, the information providing server 110 controls the transfer operation of the node 120 to cause the packet transmitted from the client terminal 20 to be transferred to the information providing server 110 with higher priority than the packet transmitted from the client terminal 22. In one embodiment, if communication between the client terminal 20 and the information providing server 110 has already been established, and communication between the client terminal 22 and the information providing server 110 has not yet been established, the information providing server 110 Controls the transfer operation of the node 120 to cause the packet transmitted from the client terminal 20 to be transferred to the server with higher priority than the packet transmitted from the client terminal 22. Thereby, for example, even when the load on the information providing server 110 is heavy, it is possible to stably maintain a session with the client terminal 20 that has already established communication with the information providing server 110.

  In another embodiment, when the life log information of each user of the client terminal 20 and the client terminal 22 is compared with a predetermined condition regarding the life log information, the life log information of the user of the client terminal 20 satisfies the condition. If they match and the life log information of the user of the client terminal 22 does not match the condition, the information providing server 110 controls the transfer operation of the node 120 to transmit the packet transmitted from the client terminal 20 from the client terminal 22. It is transferred to the server with priority over the transmitted packet.

  Thereby, access to the information providing server 110 can be controlled according to the user's life log information. As a result, access to the information providing server 110 can be controlled according to the service provided by the information providing server 110. For example, when the information providing server 110 provides a service for reserving a railway ticket, the information providing server 110 preferentially transfers a packet transmitted from a client terminal of a user existing near a station to the information providing server 110. As such, the node 120 can be controlled.

  The authentication server 112 performs user authentication of the user of the service provided by the information providing server 110. In the present embodiment, in response to a request from the information providing server 110, the authentication server 112 allows a user of a client terminal that has established communication with the information providing server 110 to be a valid user of a service provided by the information providing server 110. (This determination may be referred to as user authentication). The authentication server 112 receives the user ID and password of the user of the client terminal for which communication with the information providing server 110 is established from the information providing server 110, and executes user authentication based on the received user ID and password. It's okay.

  The life log server 114 stores each life log information of users of one or more client terminals in association with terminal identification information for identifying each of the one or more client terminals. The life log information of each user of one or more client terminals may be associated with terminal identification information that identifies each of the one or more client terminals via user identification information that identifies each user.

  For example, the life log server 114 stores the life log information and user identification information of each user of one or more client terminals in association with each other in a specific database. Further, the life log server 114 stores the user identification information and the terminal identification information of the client terminal of the user identified by the user identification information in association with each other in a database. The life log server 114 can associate the life log information with the terminal identification information via the user identification information by referring to the two databases.

  The terminal identification information may be an address, an identifier, or a combination of layer 1 to layer 4 of the OSI (Open Systems Interconnection) reference model. For example, when the client terminal 20 or the client terminal 22 is a mobile terminal, the terminal identification information is sometimes referred to as individual identification information, and is information that is associated with contractor information by a communication carrier and identifies the terminal. Also good. Information associated with the contract information may be referred to as a carrier open ID, and may be referred to as a uid, a subscriber ID, an i-mode (registered trademark) ID, or the like depending on a communication carrier.

  The life log information is information in which the user's life, behavior or experience is recorded as digital data. The current location information of the client terminal, the movement history of the client terminal, the user's schedule information, the browsing history of the website, Examples include search history, purchase history of products or services, information associated with SNS (Social Networking Service) accounts, information associated with accounts of Web mail services such as G-mail, and the like.

  The node 120 receives the packet and transfers the received packet. In the present embodiment, the node 120 transfers a packet between the information providing server 110 and the client terminal 20 or the client terminal 22 that accesses the information providing server 110. The node 120 may transfer the packet in accordance with transfer conditions that define the transfer operation of the node 120. The node 120 may identify the received packet and forward the packet according to a forwarding condition that matches the received packet.

  The node 120 may hold a table defining transfer conditions (sometimes referred to as a routing policy, a flow entry, etc.). The transfer condition may include information in which packet identification information for identifying a packet is associated with information for defining a processing method for the packet identified by the packet identification information. The transfer condition includes transfer condition identification information for identifying each of the transfer conditions, node identification information for identifying a node to which the transfer conditions identified by the transfer condition identification information are applied, packet identification information for identifying the packet, and a packet It may be information associated with information defining a processing method for a packet identified by the identification information.

  The transfer condition of the node 120 may be set by the node control device 130 via the communication network 12. The node 120 may be a hardware switch or a software switch. The node 120 may be an OpenFlow Switch or may be an Open vSwitch.

  The OpenFlow Switch is a network switch that supports the open flow technology proposed by the OpenFlow Consortium. The OpenFlow technology is a technology in which transfer operations and the like of a plurality of switches constituting a computer network are centrally controlled by an external controller. Open vSwitch is a kind of software switch and is a virtual OpenFlow Switch.

  OpenFlow Switch refers to a flow table that stores a flow entry that is an example of a transfer condition, and operates according to the flow entry. A flow entry is defined as a combination of a “rule” that identifies a packet to be processed and an “action” that defines an operation to be performed on a packet that matches the “rule”. The flow entry is set or deleted by an external controller. The flow table may define QoS for each flow, information related to encryption, and the like.

  As the “rule”, for example, an address, an identifier, or a combination of layers 1 to 4 of an OSI (Open Systems Interconnection) reference model included in header information in TCP / IP packet data can be specified. For example, a layer 1 physical port, a layer 2 MAC address, a layer 3 IP address, a layer 4 port number, a VLAN tag (sometimes referred to as a VLAN ID), or a combination thereof is specified. . A priority order may be given to the VLAN tag. As the “action”, operations such as forwarding to another port, rewriting the header, and discarding the packet can be designated.

  In the present embodiment, the node 120 is arranged between the information providing server 110 and the communication network 10, and the node 120 transmits packets between the information providing server 110 and the client terminal 20 or the client terminal 22. The case of transferring was explained. However, the arrangement of the nodes 120 is not limited to this embodiment. The node 120 may be arranged between the communication network 10 and the client terminal 20 or the client terminal 22, and may transfer a packet between the information providing server 110 and the client terminal 20 or the client terminal 22.

  The node control device 130 controls the node 120. The node control device 130 may control the transfer operation of the node 120 via the communication network 12. For example, the node control device 130 receives from the information providing server 110 a request for updating the transfer condition of the node 120 and information related to the new transfer condition. Based on the information received from the information providing server 110, the node control device 130 generates data for updating the transfer condition held by the node 120. The node control device 130 transmits the generated data to the node 120 and sets the transfer condition of the node 120.

  FIG. 2 schematically shows an example of the information providing server 110. The information providing server 110 includes an information providing unit 210 and an access control unit 220. The access control unit 220 includes an identification information acquisition unit 230, an identification information identification unit 240, a life log condition storage unit 242, a transfer condition change unit 250, and a load monitoring unit 252.

  The information providing unit 210 provides information in response to a request from the client terminal 20 or the client terminal 22. The access control unit 220 controls access from the client terminal 20 and the client terminal 22 to the information providing server 110. The access control unit 220 may be an example of a transfer condition changing device.

  The identification information acquisition unit 230 acquires terminal identification information for identifying a client terminal that has established communication with the information providing server 110. The terminal identification information may be an address, an identifier, or a combination of layer 1 to layer 4 of the OSI (Open Systems Interconnection) reference model. For example, in one embodiment, the identification information acquisition unit 230 acquires the IP address of the client terminal 20 or the client terminal 22. In another embodiment, the IP address and port number of the client terminal 20 or the client terminal 22 are acquired. The identification information acquisition unit 230 transmits the acquired terminal identification information to the transfer condition change unit 250.

  The identification information specifying unit 240 refers to the life log information for each user or client terminal stored in the life log server 114 and stores the terminal identification stored in association with the life log information that matches a predetermined condition. Identify information. The identification information specifying unit 240 transmits the specified terminal identification information to the transfer condition changing unit 250.

  For example, the identification information specifying unit 240 first acquires a condition (sometimes referred to as a life log condition) related to the user's life log information stored in the life log condition storage unit 242. Next, the identification information specifying unit 240 transmits the acquired condition to the life log server 114 and requests to extract terminal identification information associated with the life log information that matches the condition. The identification information specifying unit 240 can specify the terminal identification information associated with the life log information that matches the above condition by receiving the extraction result from the life log server 114.

  The life log condition storage unit 242 stores at least a part of the transfer conditions held by the node 120 in association with the life log conditions. For example, when the node 120 is OpenFlow Switch, the life log condition storage unit 242 stores information relating to the “action” of the flow entry and a predetermined condition relating to the user life log information in association with each other. As life log conditions, the condition that the current position of the user is within a specific range, the condition that the user has purchased a specific product or service, and the update frequency of the life log information is greater than a specific value. Conditions can be exemplified.

  The transfer condition changing unit 250 changes the transfer condition of the node 120. The transfer condition changing unit 250 may change the transfer condition held by the node 120 via the node control device 130. The transfer condition changing unit 250 may periodically change the transfer condition of the node 120. Thereby, appropriate access control according to the access status of the information providing server 110 can be realized.

  The transfer condition changing unit 250 may change the transfer condition of the node 120 based on the notification from the load monitoring unit 252. For example, the transfer condition changing unit 250 receives a request for changing the transfer condition of the node 120 from the load monitoring unit 252 (sometimes referred to as a change request). Upon receiving the change request, the transfer condition changing unit 250 changes the transfer condition of the node 120. As a result, when the load on the information providing server 110 increases, priority can be provided to the client terminals to restrict access to the information providing server 110.

  The transfer condition changing unit 250 is configured to transfer a packet transmitted from a client terminal with which communication with the information providing server 110 is established, to the information providing server 110 with higher priority than a packet transmitted from another client terminal. The transfer condition held by the node 120 may be changed. Thereby, the transfer conditions of the node 120 can be dynamically updated according to the access status of the information providing server 110.

  For example, the transfer condition changing unit 250 receives the terminal identification information acquired by the identification information acquiring unit 230 from the identification information acquiring unit 230. The transfer condition changing unit 250 generates a new transfer condition for causing the packet transmitted from the client terminal identified by the received terminal identification information to be transferred to the server with higher priority than the packet transmitted from another client terminal. To do.

  The transfer condition changing unit 250 transmits the generated new transfer condition to the node control device 130 and requests to update the transfer condition of the node 120. In response to the request from the transfer condition changing unit 250, the node control device 130 sets the new transfer condition received from the transfer condition changing unit 250 as the transfer condition of the node 120.

  The transfer condition changing unit 250 transfers the packet transmitted from the client terminal of the user that matches the specific life log condition to the information providing server 110 with higher priority than the packet transmitted from the other client terminal. The transfer conditions held by may be changed. Thereby, the transfer conditions of the node 120 can be dynamically updated according to the user's life log information.

  For example, the transfer condition changing unit 250 receives the terminal identification information of the client terminal associated with the life log information matching the specific life log condition from the identification information specifying unit 240. The transfer condition changing unit 250 generates a new transfer condition for causing the packet transmitted from the client terminal identified by the received terminal identification information to be transferred to the server with higher priority than the packet transmitted from another client terminal. To do. The transfer condition changing unit 250 may generate a new transfer condition based on the terminal identification information acquired by the identification information acquiring unit 230 and the terminal identification information specified by the identification information specifying unit 240.

  The transfer condition changing unit 250 transmits the generated new transfer condition to the node control device 130 and requests to update the transfer condition of the node 120. In response to the request from the transfer condition changing unit 250, the node control device 130 sets the new transfer condition received from the transfer condition changing unit 250 as the transfer condition of the node 120.

  The load monitoring unit 252 monitors the load on the information providing server 110. When the load monitoring unit 252 determines that the load on the information providing server 110 is larger than a predetermined value, the load monitoring unit 252 requests the transfer condition changing unit 250 to change the transfer condition. Thereby, the information providing server 110 can dynamically update the transfer condition of the node 120 when the load becomes large, for example.

  In the present embodiment, the access control unit 220 has been described as an example in which the access control unit 220 is arranged in the information providing server 110. However, the access control unit 220 is not limited to this embodiment. In other embodiments, the access control unit 220 and the information providing server 110 may be constructed on physically different information processing apparatuses. In the present embodiment, the case where the identification information acquisition unit 230 and the identification information specifying unit 240 of the access control unit 220 are realized by different modules has been described. However, the access control unit 220 is not limited to this embodiment. In another embodiment, the identification information acquisition unit 230 and the identification information specifying unit 240 may be realized by the same module.

  FIG. 3 schematically shows an example of the flow table 300 held in the node control device 130. The flow table 300 includes a plurality of flow entries. In FIG. 3, each of the plurality of flow entries is described as a row of the flow table 300. Each of the plurality of flow entries and the flow table 300 may be an example of a transfer condition.

  The flow table 300 stores a flow entry ID 310, a node ID 320, a rule 330, and action information 340 in association with each other for each of a plurality of flow entries. The flow entry ID 310 is identification information for identifying each of a plurality of flow entries. The node ID 320 is identification information for identifying a node that is a setting target of the corresponding flow entry.

  The rule 330 is information that identifies a packet or flow that is a processing target of the corresponding flow entry. The rule 330 includes a packet or flow access source IP address 332 and a packet or flow access destination IP address 334. Each of the rule 330 and the access source IP address 332 may be an example of packet identification information that identifies a packet. The action information 340 is information that defines an operation (sometimes referred to as an action) performed on a packet that matches the corresponding rule 330.

  FIG. 4 schematically shows an example of the flow table 400 held in the node 120. The flow table 400 includes a plurality of flow entries. In FIG. 3, each of the plurality of flow entries is described as a row of the flow table 400. Each of the plurality of flow entries and the flow table 400 may be an example of a transfer condition.

  The flow table 400 stores a flow entry ID 310, a node ID 320, a rule 330, and action information 340 in association with each other for each of a plurality of flow entries. The flow table 400 may be generated when the node control device 130 extracts a flow entry related to the node 120 from a plurality of flow entries included in the flow table 300.

  FIG. 5 schematically shows an example of a table 500 that defines life log conditions. The table 500 stores life log conditions 510 and action information 520 in association with each other. The life log condition 510 defines a predetermined condition regarding the user's life log information. The action information 520 defines the operation of the node 120 for a packet or flow from the user's client terminal that matches the life log condition 510.

  The table 500 may be used when the transfer condition changing unit 250 generates a new transfer condition based on the terminal identification information specified by the identification information specifying unit 240. For example, the identification information specifying unit 240 refers to information on the current position of the client terminal stored in the life log server 114 and specifies the terminal identification information of the client terminal that matches each of the life log conditions 510. For each action information 520, the transfer condition changing unit 250 associates the terminal identification information of the client terminal that matches the life log condition 510 corresponding to each of the action information 520 with the action information 520, and performs a new transfer. Generate a condition.

  FIG. 6 schematically shows an example of a table 600 defining life log conditions. The table 600 stores life log conditions 610, communication status conditions 612, and action information 620 in association with each other. The life log condition 610 defines a predetermined condition related to the user's life log information. The communication status condition 612 defines a condition regarding the communication establishment status of the client terminal. The action information 620 defines the operation of the node 120 for a packet or flow from a client terminal that matches the life log condition 610 and the communication status condition 612.

  In the table 600, when the transfer condition changing unit 250 generates a new transfer condition based on the terminal identification information acquired by the identification information acquiring unit 230 and the terminal identification information specified by the identification information specifying unit 240. May be used. For example, the identification information acquisition unit 230 acquires terminal identification information for identifying a client terminal that has established communication with the information providing server 110. The identification information specifying unit 240 specifies terminal identification information of the client terminal that matches each of the life log conditions 610 with reference to the information regarding the current position of the client terminal stored in the life log server 114. The transfer condition changing unit 250 associates, for each action information 620, the terminal identification information of the client terminal that matches the life log condition 610 and the communication status condition 612 corresponding to each action information 620 and the action information 620. To generate new transfer conditions.

  In the present embodiment, a case has been described in which the action information 620 defines the operation of the node 120 for a packet or flow from a client terminal that matches the life log condition 610 and the communication status condition 612. However, the action information 620 is not limited to this embodiment. The action information 620 may specify the operation of the node 120 for a packet or flow from a client terminal that matches the life log condition 610 or the communication status condition 612.

  FIG. 7 schematically shows an example of a table 700 stored in the life log server 114. The table 700 stores a terminal ID 710 for identifying each client terminal and life log information 720 in association with each other. The life log information 720 may include information 722 regarding the current location of the client terminal, information 724 regarding the user's schedule of the client terminal, information 726 regarding the user's search history, and information 728 regarding the user's browsing history. .

  The life log server 114 can extract the terminal identification information of the client terminal that matches the life log condition received from the identification information specifying unit 240 using the table 700. For example, the life log server 114 compares the life log information 720 with the received life log condition for each of the plurality of client terminals. Next, a client terminal including information that matches the life log condition received from the identification information specifying unit 240 is extracted from the life log information 720. Thereafter, the life log server 114 transmits the extracted terminal ID 710 of the client terminal to the identification information specifying unit 240.

  FIG. 8 schematically shows an example of a table 800 stored in the life log server 114. FIG. 9 schematically shows an example of a table 900 stored in the life log server 114. The table 800 and the table 900 may be used when the life log server 114 associates the life log information with the terminal identification information via the user identification information.

  The table 800 stores a user ID 810 for identifying each user of the information providing server 110 and life log information 820 of each user in association with each other. The life log information 820 may include information 822 regarding the current location of the user's client terminal, information 824 regarding the user's schedule, information 826 regarding the user's search history, and information 828 regarding the user's browsing history.

  The table 900 stores a user ID 810 that identifies each user of the information providing server 110 and a terminal ID 920 that identifies each user's client terminal in association with each other. The life log server 114 can associate the life log information 820 of the table 800 with the terminal ID 920 of the table 900 via the user ID 810.

  The table 900 may be created by a communication carrier when a user contracts with the communication carrier. The table 900 may be generated by the information providing server 110. For example, the information providing server 110 acquires the terminal identification information of the client terminal with which communication has been established from the identification information acquisition unit 230. The information providing server 110 requests the user ID and password of the service provided by the information providing server 110 from the user of the client terminal with which communication has been established. Upon receiving the user ID from the client terminal, the information providing server 110 generates the table 900 by associating the terminal identification information received from the identification information acquisition unit 230 with the user ID received from the client terminal.

  FIG. 10 schematically shows an example of the operation of the information providing system 100. Using FIG. 10, a packet transmitted from a client terminal for which communication with the information providing server 110 has already been established has been transmitted from a client terminal for which communication with the information providing server 110 has not yet been established. An example of the operation of the information providing system 100 when the node 120 is controlled to be transferred to the information providing server 110 with priority over the packet will be described.

  According to the present embodiment, in step 1002 (the abbreviation S may be used for step), the client terminal 20 transmits a packet specifying the information providing server 110 as a destination IP address. The packet transmitted from the client terminal 20 is received by the node 120 and buffered at the node 120 at one end.

  The node 120 refers to the rule 330 of the flow table 400 to determine whether there is a flow entry for the received packet. If there is a flow entry for the received packet, the node 120 processes the packet according to the action information 340 of the flow entry. An example of processing for a packet is transfer or discard of the packet.

  On the other hand, if there is no flow entry for the received packet, the packet is transferred to the node control device 130. In addition, the node 120 notifies the node control device 130 that a new flow has been detected. In the present embodiment, the operation of the information providing system 100 will be described by taking as an example a case where there is no flow entry for the received packet.

  According to the present embodiment, in S1012, the node 120 transfers the packet to the node control device 130 to notify that a new flow has been detected. Upon receiving the above notification from the node 120, the node control device 130 analyzes the header of the packet transferred from the node 120 and acquires information regarding the transmission source and transmission destination of the packet. In S1014, the node control device 130 sets the flow table 400 of the node 120 so that the packet is transferred to the information providing server 110. For example, a new flow entry is added to the flow table 400 of the node 120.

  In the new flow entry rule 330, the access source IP address 332 may be the IP address of the client terminal 20, and the access destination IP address 334 may be the IP address of the information providing server 110. The action information 340 of the new flow entry may define a process of transferring the packet or flow specified by the rule 330 to the destination specified by the access destination IP address 334. In S1022, the node 120 transfers the packet received from the client terminal 20 to the information providing server 110 in accordance with the flow entry added to the flow table 400.

  In S1030, the information providing server 110 provides information to the user of the client terminal 20 by providing information in response to a request from the client terminal 20. For example, when communication is established between the information providing server 110 and the client terminal 20, the identification information acquisition unit 230 of the information providing server 110 acquires terminal identification information for identifying the client terminal 20. The terminal identification information may be a packet transmission source IP address or a combination of an IP address and a port number.

  Next, the information providing server 110 may request the client terminal 20 to transmit the user ID and password regarding the service provided by the information providing server 110 of the user of the client terminal 20. The node 120 may transfer the packet transmitted by the information providing server 110 to the client terminal 20 according to the flow table 400.

  The client terminal 20 requests the user to input a user ID and password related to the service provided by the information providing server 110. The client terminal 20 acquires the above user ID and password based on the input from the user. The client terminal 20 transmits the acquired user ID and password to the information providing server 110. The node 120 transfers the packet transmitted by the client terminal 20 to the information providing server 110 according to the flow table 400.

  The information providing server 110 transmits the user ID and password received from the client terminal 20 to the authentication server 112 and requests user authentication of the user of the client terminal 20. The authentication server 112 performs user authentication and transmits the result to the information providing server 110. When the user of the client terminal 20 is authenticated as a valid user, the information providing server 110 starts providing information to the client terminal 20.

  In S1040, the load monitoring unit 252 of the information providing server 110 monitors the load of the information providing server 110. When determining that the load on the information providing server 110 is greater than a predetermined value, the load monitoring unit 252 requests the transfer condition changing unit 250 to change the transfer condition.

  In S1050, the transfer condition changing unit 250 of the information providing server 110 receives the request from the load monitoring unit 252. When the transfer condition change unit 250 receives the above request, the transfer condition change unit 250 starts an update process of the flow table 400 held by the node 120. Specifically, the transfer condition changing unit 250 establishes communication with the information providing server 110 based on a packet transmitted from a client terminal (for example, the client terminal 20) with which communication with the information providing server 110 is established. The flow table 400 held by the node 120 is dynamically changed so as to be transferred to the information providing server 110 with higher priority than packets transmitted from other client terminals (for example, the client terminal 22).

  For example, the transfer condition changing unit 250 transmits a packet transmitted from a client terminal that has established communication with the information providing server 110 from another client terminal that has not established communication with the information providing server 110. A new flow entry is generated to be transferred to the server with higher priority than the packet. Thereafter, in S1052, the transfer condition changing unit 250 transmits the generated new flow entry to the node control device 130 and requests to update the flow table 300 held by the node control device 130.

  The node control device 130 updates the flow table 300 based on the received new flow entry. For example, a new flow entry is compared with the flow table 300, and a flow entry is added or deleted.

  In the new flow entry rule 330, the access source IP address 332 is the IP address of the client terminal that has established communication with the information providing server 110 at a specific time or period, and the access destination IP address 334 provides the information. It may be the IP address of the server 110. The action information 340 of the new flow entry may define a process for making the priority of the packet or flow specified by the rule 330 higher than the priority of other packets or flows.

  In S1054, the node control apparatus 130 sets the flow table 400 of the node 120 based on the updated flow table 300. As a result, the node 120 prioritizes packets transmitted from client terminals that have established communication with the information providing server 110 over packets transmitted from client terminals that have not established communication with the information providing server 110. Then, it can be transferred to the information providing server 110.

  FIG. 11 schematically shows another example of the operation of the information providing system 100. Using FIG. 11, the packet transmitted from the client terminal that matches the life log condition is transferred to the information providing server 110 with higher priority than the packet transmitted from the client terminal that does not match the life log condition. An example of the operation of the information providing system 100 when controlling the node 120 will be described.

  In S1110, the load monitoring unit 252 of the information providing server 110 monitors the load of the information providing server 110. When determining that the load on the information providing server 110 is greater than a predetermined value, the load monitoring unit 252 requests the transfer condition changing unit 250 to change the transfer condition.

  In S <b> 1130, the transfer condition changing unit 250 of the information providing server 110 receives a request from the load monitoring unit 252. When the transfer condition change unit 250 receives the above request, the transfer condition change unit 250 starts an update process of the flow table 400 held by the node 120. Specifically, the transfer condition changing unit 250 prioritizes packets transmitted from client terminals associated with life log information that matches a specific life log condition over packets transmitted from other client terminals. The flow table 400 held by the node 120 is dynamically changed so as to be transferred to the information providing server 110.

  For example, in S1132, the identification information specifying unit 240 transmits the life log condition 510 stored in the life log condition storage unit 242 in association with the action information 520 to the life log server 114. The identification information specifying unit 240 requests the life log server 114 to extract terminal identification information associated with life log information that matches the life log condition 510. In S1134, the life log server 114 transmits the extraction result to the identification information specifying unit 240. The identification information specifying unit 240 transmits the received extraction result to the transfer condition changing unit 250.

In S1142,
The transfer condition changing unit 250 transfers the packet transmitted from the client terminal identified by the terminal identification information included in the received extraction result to the information providing server 110 with higher priority than the packet transmitted from the other client terminal. A new flow entry is generated for this purpose. In S1142, the transfer condition changing unit 250 transmits the generated new flow entry to the node control device 130, and requests to update the flow table 300 held by the node control device 130.

  The node control device 130 updates the flow table 300 based on the received new flow entry. For example, a new flow entry is compared with the flow table 300, and a flow entry is added or deleted.

  In the new flow entry rule 330, the access source IP address 332 is the IP address of the client terminal identified by the terminal identification information included in the extraction result, and the access destination IP address 334 is the IP address of the information providing server 110. It may be. The action information 340 of the new flow entry may specify a process for transferring the packet or flow specified by the rule 330 based on the priority specified by the action information 520.

  In S1144, the node control device 130 sets the flow table 400 of the node 120 based on the updated flow table 300. Thereby, the node 120 gives priority to the packet transmitted from the client terminal associated with the life log information matching the specific life log condition over the packet transmitted from the other client terminal. It can be transferred to the server 110.

  FIG. 12 schematically shows an example of the information providing system 1200. The information providing system 1200 includes an information providing server 110, an authentication server 112, a life log server 114, a node control device 130, a node 1220, and a node 1222. The information providing system 1200 may be an example of a transfer condition changing device.

  The information providing system 1200 is different from the information providing system 100 in that the information providing server 110, the authentication server 112, the life log server 114, and the node control device 130 transmit and receive information to and from each other via the communication network 10. The information providing system 1200 is different from the information providing system 100 in that the client terminal 20 is connected to the communication network 10 via the node 1220 and the client terminal 22 is connected to the communication network 10 via the node 1222. In other respects, the information providing system 1200 may have the same configuration as the information providing system 100 and can execute the same processing as the information providing system 100.

  In the above description, each part of the information providing system 100 and the information providing system 100 and each part of the information providing system 1200 and the information providing system 1200 may be realized by hardware or may be realized by software. Further, it may be realized by a combination of hardware and software. The information providing system 100 and the information providing system 1200 may be a system specialized for each application, or may be a general-purpose information processing apparatus such as a personal computer. The specialized system and information processing apparatus described above may be configured by a single computer or may be configured by a plurality of computers distributed on a network.

  Moreover, a computer may function as each part of the information provision system 100 or each part of the information provision system 1200 by running a program. The program may be stored in a computer-readable medium, or may be stored in a storage device connected to a network. In an information processing apparatus having a general configuration including a data processing apparatus having a CPU, a ROM, a RAM, a communication interface, and the like, an input apparatus, an output apparatus, and a storage apparatus, each unit of the information providing system 100 or the information providing system Each part of the information providing system 100 or each part of the information providing system 1200 may be realized by starting software or a program that defines the operation of each part of the 1200.

  A program that is installed in a computer and causes the computer to function as each part of the information providing system 100 or each part of the information providing system 1200 according to the present embodiment is a module that defines the operation of each part of the information providing system 100 or each part of the information providing system 1200 Is provided. These programs or modules work on the CPU or the like to cause the computer to function as each part of the information providing system 100 or each part of the information providing system 1200. Information processing described in these programs functions as a specific means in which software and the various hardware resources described above cooperate with each other by being read by a computer. A specific measurement device according to the purpose of use can be constructed by realizing calculation or processing of information according to the purpose of use of the computer in the present embodiment by these specific means.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiment. In addition, the matters described in the specific embodiment can be applied to other embodiments within a technically consistent range. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

  The order of execution of each process such as operations, procedures, steps, and stages in the apparatus, system, program, and method shown in the claims, the description, and the drawings is particularly “before” or “prior to”. It should be noted that the output can be realized in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flow in the claims, the description, and the drawings, even if it is described using “first”, “next”, etc. for convenience, it means that it is essential to carry out in this order. It is not a thing.

  10 communication network, 12 communication network, 20 client terminal, 22 client terminal, 100 information providing system, 110 information providing server, 112 authentication server, 114 life log server, 120 node, 130 node control device, 210 information providing unit, 220 access Control unit, 230 identification information acquisition unit, 240 identification information specification unit, 242 life log condition storage unit, 250 transfer condition change unit, 252 load monitoring unit, 300 flow table, 310 flow entry ID, 320 node ID, 330 rule, 332 Access source IP address, 334 access destination IP address, 340 action information, 400 flow table, 500 table, 510 life log condition, 520 Information, 600 table, 610 life log condition, 612 communication status condition, 620 action information, 700 table, 710 terminal ID, 720 life log information, 722 information, 724 information, 726 information, 728 information, 800 table, 810 user ID 820 life log information, 822 information, 824 information, 826 information, 828 information, 900 table, 920 terminal ID, 1200 information providing system, 1220 node, 1222 node

Claims (12)

An identification information acquisition unit for acquiring terminal identification information for identifying a client terminal that has established communication with the server at a specific time or period ;
A packet transmitted from a client terminal identified by the terminal identification information acquired by the identification information acquisition unit is transmitted from another client terminal that has not established communication with the server at the specific time or period. A transfer condition changing unit that changes the transfer condition held by a node that transfers a packet according to a transfer condition between the server and a client terminal that accesses the server in order to transfer the server to the server more preferentially;
With
The transfer condition includes information in which packet identification information for identifying a packet is associated with information for defining a processing method of the packet identified by the packet identification information.
Transfer condition change device. A node control device for setting the transfer condition held by the node via a network;
The transfer condition changing unit
Generates a new transfer condition for causing a packet transmitted from the client terminal identified by the terminal identification information acquired by the identification information acquisition unit to be transferred to the server with priority over packets transmitted from other client terminals. And
Sending the new transfer condition to the node controller;
The node control device sets the new transfer condition received from the transfer condition change unit as the transfer condition of the node;
The transfer condition changing device according to claim 1. Store at least a part of the transfer conditions held by the node that transfers packets according to the transfer conditions between the server and the client terminal that accesses the server in association with a predetermined condition related to the user life log information. A life log condition storage unit to
The life log information storage unit that stores the life log information of each of the users of one or more client terminals in association with the terminal identification information that identifies each of the one or more client terminals. An identification information identification unit that identifies terminal identification information stored in association with life log information that matches the condition;
The node held by the node to preferentially transfer a packet transmitted from a client terminal identified by the terminal identification information identified by the identification information identifying unit to the server over a packet transmitted from another client terminal. A transfer condition changing section for changing the transfer condition;
A transfer condition changing device. A node control device for setting the transfer condition held by the node via a network;
The transfer condition changing unit
Generates a new transfer condition for causing a packet transmitted from a client terminal identified by the terminal identification information identified by the identification information identifying unit to be transferred to the server with higher priority than a packet transmitted from another client terminal. And
Sending the new transfer condition to the node controller;
The node control device sets the new transfer condition received from the transfer condition change unit as the transfer condition of the node;
The transfer condition changing device according to claim 3. A load monitor that monitors the load on the server and transmits a change request for changing the transfer condition to the transfer condition change unit when it is determined that the load on the server is greater than a predetermined value. Further comprising
The transfer condition changing unit changes the transfer condition held by the node when the change request is received from the load monitoring unit.
The transfer condition changing device according to any one of claims 1 to 4. An identification information acquisition unit that acquires terminal identification information for identifying a client terminal that has established communication with the server;
A transfer condition changing unit that changes the transfer condition held by a node that transfers packets according to a transfer condition between the server and a client terminal that accesses the server;
A load for monitoring a load on the server and transmitting a change request for requesting the transfer condition change unit to change the transfer condition when it is determined that the load on the server is larger than a predetermined value. A monitoring unit;
With
The transfer condition changing unit generates a new transfer condition when the change request is received from the load monitoring unit,
The new transfer condition includes packet identification information for identifying a packet transmitted from a client terminal that has established communication with the server at the time of receiving the change request from the load monitoring unit, and the packet identification information. Including information associated with information that prescribes that the priority of the packet identified by is higher than the packet transmitted from another client terminal,
The transfer condition changing unit changes the transfer condition held by the node so that a packet identified by the packet identification information is transferred to the server with priority over a packet transmitted from the other client terminal. ,
Transfer condition change device. A node control device for setting the transfer condition held by the node via a network;
The transfer condition changing unit
Sending the new transfer condition to the node controller;
The node control device sets the new transfer condition received from the transfer condition change unit as the transfer condition of the node;
The transfer condition changing device according to claim 6. A program for causing a computer to function as the transfer condition changing device according to any one of claims 1 to 7 . The transfer condition changing device according to any one of claims 1 to 7 ,
The server;
With
The server provides information to the client terminal via a network;
Information provision system. Obtaining terminal identification information for identifying a client terminal that has established communication with a server at a specific time or period ;
The packet transmitted from the client terminal identified by the acquired terminal identification information is prioritized over the packet transmitted from another client terminal that has not established communication with the server at the specific time or period. Changing the forwarding condition held by a node that forwards a packet according to the forwarding condition between the server and a client terminal accessing the server to forward to the server;
A transfer condition changing method. Obtaining terminal identification information identifying a client terminal with which communication with the server has been established;
Changing the forwarding conditions held by a node that forwards packets according to forwarding conditions between the server and a client terminal accessing the server;
Monitoring the load on the server, and when determining that the load on the server is greater than a predetermined value, sending a change request for requesting a change in the transfer condition;
Have
The step of changing the transfer condition includes a step of generating a new transfer condition when the change request is received,
The new transfer condition includes packet identification information for identifying a packet transmitted from a client terminal that has established communication with the server at the time of receiving the change request, and a packet identified by the packet identification information. Including information associated with information specifying that the priority is higher than packets transmitted from other client terminals,
The step of changing the transfer condition includes the transfer condition held by the node so that the packet identified by the packet identification information is transferred to the server preferentially over the packet transmitted from the other client terminal. Including stages to change,
Transfer condition change method. Store at least a part of the transfer conditions held by the node that transfers packets according to the transfer conditions between the server and the client terminal that accesses the server in association with a predetermined condition related to the user life log information. And the stage of
The life log information storage unit that stores the life log information of each of the users of one or more client terminals in association with the terminal identification information that identifies each of the one or more client terminals. Identifying the terminal identification information stored in association with the life log information matching the conditions;
The transfer condition held by the node is changed so that a packet transmitted from a client terminal identified by the identified terminal identification information is preferentially transferred to the server over a packet transmitted from another client terminal. Stages,
A transfer condition changing method.