WO2023228251A1

WO2023228251A1 - Communication path control system, relay device, communication terminal, communication path control method, and program

Info

Publication number: WO2023228251A1
Application number: PCT/JP2022/021125
Authority: WO
Inventors: 誠大野; 一成竹内
Original assignee: 楽天モバイル株式会社
Priority date: 2022-05-23
Filing date: 2022-05-23
Publication date: 2023-11-30

Abstract

Provided are a communication path control system, a relay device, a communication terminal, a communication path control method and a program that can properly control the communication path of target data that is transmitted from a data providing device to a communication terminal in response to a transmission request from the communication terminal. A virtual IP address issuance unit (72) issues a virtual IP address to UE (36). A correspondence data storage unit (70) stores correspondence data indicating the correspondence between the virtual IP address and each of a plurality of global IP addresses assigned to the UE (36). A target data relay unit (78) receives target data the destination address of which is set to the virtual IP address, and transmits the target data to a global IP address that is determined among from the plurality of global IP addresses associated with the virtual IP address in the correspondence data on the basis of the type indicated by type information.

Description

Communication route control system, relay device, communication terminal, communication route control method and program

The present invention relates to a communication route control system, a relay device, a communication terminal, a communication route control method, and a program.

Patent Document 1 describes a terminal device that can access multiple network slices.

Japanese Patent Application Publication No. 2018-170748

The inventor is considering switching the communication path through which the target data transmitted by the data providing device is transmitted, depending on the type of target data that the communication terminal requests the data providing device to transmit. For example, target data with low importance may be transmitted via a communication path with slow communication speed or high latency.

However, with the technology described in Patent Document 1, it was not possible to switch the communication route depending on the type of target data.

The present invention has been made in view of the above circumstances, and one of its objects is to accurately determine the communication path of target data transmitted from a data providing device to a communication terminal in response to a transmission request from a communication terminal. It is an object of the present invention to provide a communication route control system, a relay device, a communication terminal, a communication route control method, and a program that can be controlled.

In order to solve the above problems, a communication path control system according to the present invention includes a relay device and a communication terminal, and the relay device has virtual IP address issuing means for distributing a virtual IP address to the communication terminal. , a correspondence data storage means for storing correspondence data indicating a correspondence between a plurality of global IP addresses assigned to the communication terminal and the virtual IP address, and the communication terminal transmits data to the data providing device. A determination means for determining the type of target data to be requested; and a transmission request transmitting means for transmitting a transmission request for the target data associated with type information associated with the determination result of the type to the relay device, The relay device includes a transmission request relay unit that receives the transmission request and transmits the transmission request to the data providing device, and a virtual IP address that is transmitted from the data providing device that received the transmission request. Upon receiving the target data set as a destination address, the IP address is determined based on the type indicated by the type information from among the plurality of global IP addresses associated with the virtual IP address in the corresponding data. The communication terminal further includes target data relay means for transmitting the target data to the global IP address, and the communication terminal further includes target data reception means for receiving the target data.

In one aspect of the present invention, the communication terminal is capable of accessing a plurality of autonomous systems, and each of the plurality of global IP addresses indicated in the correspondence data is accessed from the communication terminal from a mutually different autonomous system. This is the global IP address assigned to .

Further, in one aspect of the present invention, the communication terminal sends the transmission request including an IP header in which the virtual IP address is set as a source address and the IP address of the data providing device is set as a destination address. further comprising terminal encapsulation means for adding a capsule header in which the IP address of the relay device is set as a destination address, and the transmission request sending means sends the transmission request to which the capsule header is added to the relay device. The relay device further includes relay decapsulation means for removing the capsule header from the transmission request, and the transmission request relay means transmits the transmission request from which the capsule header has been removed to the data providing device. Send.

Further, in one aspect of the present invention, the relay device performs relay encapsulation that adds to the target data a capsule header in which the global IP address determined based on the type indicated by the type information is set as a destination address. The target data relay means transmits the target data to which the capsule header is attached.

Further, in one aspect of the present invention, the relay device further includes a correspondence data update unit that updates the correspondence data in response to detection that the global IP address assigned to the communication terminal has been changed. .

In this aspect, the global IP address indicated in the correspondence data is associated with a communication route set between the communication terminal and the relay device, and the communication terminal is connected to the relay device. further comprising identification information transmitting means for transmitting identification information of a communication path set between the two to the relay device via the communication path, the relay device transmitting the identification information transmitted from the communication terminal. further comprising: an identification information receiving unit, wherein the corresponding data updating unit associates a global IP address set as a source address of the identification information with a communication route identified by the identification information in the corresponding data. If the specified global IP address is different, the global IP address indicated in the correspondence data may be updated to the global IP address set as the source address of the identification information.

Alternatively, the relay device further includes address notification means for notifying the communication terminal of the global IP address indicated in the correspondence data, and the communication terminal is configured such that the global IP address to be notified is a header option or The relay device further includes address transmitting means for transmitting notification address data shown in a payload to the relay device, and the relay device further includes address receiving means for receiving the notification address data transmitted from the communication terminal. , when the global IP address set as the source address of the notification address data and the global IP address indicated in the header option or payload of the notification address data are different, , the global IP address indicated in the correspondence data may be updated to the global IP address set as the source address of the notification address data.

Further, one aspect of the present invention further includes communication quality monitoring means for monitoring communication quality of a plurality of communication paths set between the relay device and the communication terminal, and the target data relay means includes: The target data is transmitted to the global IP address determined based on the communication quality monitoring result and the type indicated by the type information.

Furthermore, in one aspect of the present invention, the determining means determines the type of the target data based on the destination of the target data.

Further, the relay device according to the present invention shows a correspondence between a virtual IP address dispensing means for dispensing a virtual IP address to a communication terminal, a plurality of global IP addresses given to the communication terminal, and the virtual IP address. a correspondence data storage means for storing correspondence data, and receiving from the communication terminal a transmission request for the target data associated with type information associated with the type of target data requested to be transmitted to the data providing apparatus; a transmission request relay unit that transmits a transmission request to the data providing device; and receiving the target data in which the virtual IP address is set as a destination address, which is transmitted from the data providing device that has received the transmission request; Sending the target data to the global IP address determined based on the type indicated by the type information from among the plurality of global IP addresses associated with the virtual IP address in the correspondence data. Target data relay means.

Furthermore, the communication terminal according to the present invention includes a determining means for determining the type of target data that the data providing device is requested to transmit, and a request for transmitting the target data associated with type information that is associated with the determination result of the type. a transmission request transmitting means for transmitting a message to a relay device; and receiving the target data transmitted from the relay device to a global IP address determined based on the type indicated by the type information associated with the transmission request. and target data receiving means.

Further, the communication route control method according to the present invention includes a step in which the relay device allocates a virtual IP address to a communication terminal, and a step in which the communication terminal determines the type of target data that the data providing device is requested to transmit. , the communication terminal transmits a transmission request for the target data associated with type information associated with the type determination result to the relay device, and the relay device receives the transmission request, transmitting the transmission request to the data providing device; and the relay device receiving the target data, in which the virtual IP address is set as the destination address, transmitted from the data providing device that has received the transmission request. and select the type from among the plurality of global IP addresses associated with the virtual IP address in correspondence data indicating the correspondence between the plurality of global IP addresses assigned to the communication terminal and the virtual IP address. The method includes the step of transmitting the target data to the global IP address determined based on the type indicated by the information.

Further, the program according to the present invention includes a procedure for allocating a virtual IP address to a communication terminal, and a procedure for issuing a virtual IP address from the communication terminal to the data providing device, the target data being associated with type information that is associated with the type of target data that is requested to be transmitted to the data providing device. a procedure for receiving a transmission request and transmitting the transmission request to the data providing device; and the target data having the virtual IP address set as the destination address, which is transmitted from the data providing device that has received the transmission request. from among the plurality of global IP addresses associated with the virtual IP address in correspondence data indicating the correspondence between the plurality of global IP addresses assigned to the communication terminal and the virtual IP address. A computer is caused to execute a procedure for transmitting the target data to the global IP address determined based on the type indicated by the type information.

Another program according to the present invention includes a procedure for determining the type of target data that is requested to be transmitted to a data providing device, and a process for determining the type of target data that is requested to be transmitted by the data providing device, and a process for determining the type of target data that is associated with the type information that is associated with the determination result of the type. A procedure for transmitting the target data to a relay device, and a procedure for receiving the target data from the relay device to a global IP address determined based on the type indicated by the type information associated with the transmission request. have it executed.

1 is a diagram showing an example of a communication system according to an embodiment of the present invention. FIG. 1 is a diagram showing an example of the configuration of an agent server according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a configuration of a UE according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of a logical communication path set between a UE and an agent server. It is a diagram showing an example of a web page. FIG. 3 is a diagram showing an example of communication path management data. FIG. 3 is a diagram showing an example of communication route management data. FIG. 2 is a diagram schematically showing an example of the correspondence between global IP addresses and private IP addresses. FIG. 2 is a diagram schematically showing an example of an IP header of a packet requesting transmission of target data of video content. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 3 is a diagram schematically showing an example of an IP header of a packet of target data of video content. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 3 is a diagram schematically showing an example of an IP header of a packet requesting transmission of target data of advertising content. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 3 is a diagram schematically showing an example of an IP header of a packet of target data of advertising content. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of the correspondence between global IP addresses and private IP addresses. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 3 is a diagram showing an example of communication path management data. FIG. 2 is a diagram schematically showing an example of a capsule header and an IP header. FIG. 2 is a diagram schematically showing an example of an IP header of a packet requesting transmission of target data of video content. FIG. 2 is a functional block diagram illustrating an example of functions implemented in a UE and an agent server according to an embodiment of the present invention. FIG. 2 is a flow diagram showing an example of the flow of processing performed by a UE and an agent server according to an embodiment of the present invention. FIG. 2 is a flow diagram showing an example of the flow of processing performed by a UE and an agent server according to an embodiment of the present invention.

Hereinafter, one embodiment of the present invention will be described in detail based on the drawings.

FIG. 1 is a diagram showing an example of a communication system 1 according to an embodiment of the present invention.

As shown in FIG. 1, the communication system 1 according to the present embodiment includes an autonomous system (AS) 10a, an autonomous system 10b, an autonomous system 10c, and an autonomous system 10d.

The autonomous system 10a includes a radio access network (RAN) 20a, a core network system 22a, a carrier-grade NAT (Network Address Translation) server (CGN server) 24a, and a gateway router 26a.

The autonomous system 10b includes a RAN 20b, a core network system 22b, a CGN server 24b, and a gateway router 26b.

The autonomous system 10c includes a gateway router 26c and an agent server 28.

The autonomous system 10d includes a gateway router 26d, a video content server 30, and an advertising content server 32.

The autonomous system 10a is connected to an Internet exchange (IX) 34 via a gateway router 26a. Furthermore, the autonomous system 10b is connected to the Internet exchange 34 via a gateway router 26b. Furthermore, the autonomous system 10c is connected to the Internet exchange 34 via a gateway router 26c. Furthermore, the autonomous system 10d is connected to the Internet exchange 34 via a gateway router 26d.

The RAN 20 (RAN 20a and RAN 20b) is an eNB (eNodeB) in a fourth generation mobile communication system (hereinafter referred to as 4G) or a gNB (NR base) in a fifth generation mobile communication system (hereinafter referred to as 5G). It is a computer system equipped with an antenna, which corresponds to a radio station. The RAN 20 according to this embodiment may be implemented by a server group located in a data center or communication equipment equipped with an antenna.

The core network system 22 (core network system 22a and core network system 22b) is a system equivalent to EPC (Evolved Packet Core) in 4G and 5G core (5GC) in 5G. The core network system 22 according to this embodiment may be implemented by a group of servers located in a data center.

In this embodiment, for example, a UE (User Equipment) 36, which is a communication terminal that can access a plurality of autonomous systems 10, performs wireless communication with the RAN 20a and the RAN 20b.

The core network system 22a, RAN 20a, and UE 36 cooperate with each other to realize a mobile communication network. The RAN 20a and core network system 22a according to the present embodiment provide first network services such as voice communication services and data communication services to users who use the UE 36.

Furthermore, the core network system 22b, RAN 20b, and UE 36 cooperate with each other to realize a mobile communication network. The RAN 20b and core network system 22b according to this embodiment provide second network services such as voice communication services and data communication services to users who use the UE 36.

In this embodiment, for example, the first network service and the second network service are provided by different carriers (for example, communication carriers).

Note that the network services provided in this embodiment are not limited to voice communication services and data communication services. The network service provided in this embodiment may be, for example, an IoT (Internet of Things) service.

In this embodiment, a container-type virtualization application execution environment such as Docker (registered trademark) is installed on the servers on which the RAN 20 and the core network system 22 are installed, and containers are installed on these servers. You can now deploy and run it. In these servers, a cluster composed of one or more containers generated by such virtualization technology may be constructed. For example, a cluster (Kubernetes cluster) managed by a container management tool such as Kubernetes (registered trademark) may be constructed. Then, processors on the constructed cluster may execute container-type applications.

The network service provided in this embodiment may be composed of one or more functional units (for example, a network function (NF)). The functional unit is a type of VNF (Virtualized Network Function), and may be implemented by a CNF (Containerized Network Function) realized by container-type virtualization technology. Furthermore, the functional unit according to this embodiment may correspond to a network node.

For example, for the RAN 20, elements such as vDU (virtual Distributed Unit), vCU (virtual Central Unit), DU (Distributed Unit), and CU (Central Unit) may be implemented by CNF.

Further, regarding the core network system 22, elements such as UPF (User Plane Function), AMF (Access and Mobility Management Function), and SMF (Session Management Function) may be implemented by CNF.

FIG. 2 is a diagram showing an example of the configuration of the agent server 28 according to the present embodiment. The agent server 28 according to this embodiment is configured on a cloud infrastructure, for example, and includes a processor 28a, a storage section 28b, and a communication section 28c, as shown in FIG. The processor 28a is a program-controlled device such as a microprocessor that operates according to a program installed in the agent server 28. The storage unit 28b is, for example, a storage element such as ROM or RAM, a solid state drive (SSD), a hard disk drive (HDD), or the like. The storage unit 28b stores programs and the like executed by the processor 28a. The communication unit 28c is, for example, a communication interface such as a NIC (Network Interface Controller) or a wireless LAN (Local Area Network) module. Note that SDN (Software-Defined Networking) may be implemented in the communication unit 28c.

FIG. 3 is a diagram showing an example of the configuration of the UE 36 according to the present embodiment. As shown in FIG. 3, the UE 36 according to the present embodiment includes a processor 36a, a storage section 36b, a first communication section 36ca, a second communication section 36cb, a touch panel 36d, and the like. The processor 36a is a program-controlled device such as a microprocessor that operates according to a program installed in the UE 36. The storage unit 36b is, for example, a storage element such as a RAM or a flash memory. The storage unit 36b stores programs and the like executed by the processor 36a. The first communication unit 36ca and the second communication unit 36cb are communication interfaces such as RF (Radio Frequency) chips, baseband processors, and the like. The touch panel 36d is, for example, a combination of a touch sensor and a display such as a liquid crystal display or an organic EL display. The touch panel 36d displays a screen generated by the processor 36a.

The first communication unit 36ca according to this embodiment communicates with the autonomous system 10a, and the second communication unit 36cb according to this embodiment communicates with the autonomous system 10b. In this manner, in this embodiment, the two communication units 36c each access separate autonomous systems 10.

The CGN servers 24 (CGN servers 24a and CGN servers 24b) are servers equipped with a carrier grade NAT (CGN) function, and perform conversion between a global IP address and a private IP address.

The gateway router 26a is a node between the autonomous system 10a and the Internet exchange 34. Gateway router 26b is a node between autonomous system 10b and Internet exchange 34. Gateway router 26c is a node between autonomous system 10c and Internet exchange 34. The gateway router 26d is a node between the autonomous system 10d and the Internet exchange 34.

In this embodiment, the video content server 30 is a server that provides video content data in response to a request from the UE 36, for example.

In this embodiment, the advertising content server 32 is, for example, a server that provides advertising content data in response to a request from the UE 36.

The Internet exchange 34 is a group of devices that provides an interconnection environment between Internet service providers (ISPs). The Internet exchange 34 according to this embodiment provides full transit service to the autonomous system 10a, the autonomous system 10b, the autonomous system 10c, and the autonomous system 10d.

FIG. 4 is a diagram showing an example of a logical communication path set between the UE 36 and the agent server 28. As shown in FIG. 4, in this embodiment, for example, a plurality of logical communication paths are constructed between the UE 36 and the agent server 28. In the example of FIG. 4, two communication paths 40 (a communication path 40a and a communication path 40b) are constructed between the UE 36 and the agent server 28.

As shown in FIG. 4, the communication path 40a is a communication path that passes through the RAN 20a, core network system 22a, CGN server 24a, gateway router 26a, Internet exchange 34, and gateway router 26c. That is, the communication path 40a is a communication path that passes through the autonomous system 10a.

Furthermore, as shown in FIG. 4, the communication path 40b is a communication path that passes through the RAN 20b, the core network system 22b, the CGN server 24b, the gateway router 26b, the Internet exchange 34, and the gateway router 26c. That is, the communication path 40b is a communication path that passes through the autonomous system 10b.

Part or all of the communication path 40a may be a network slice. Further, part or all of the communication path 40b may be a network slice. Hereinafter, the identification information of the communication route 40 will be referred to as route ID. Further, it is assumed that the value of the route ID corresponding to the communication route 40a is "1", and the value of the route ID corresponding to the communication route 40b is "2". Note that the route ID according to this embodiment may be network slice identification information (for example, S-NSSAI (Single-Network Slice Selection Assistance Information)).

FIG. 5 is a diagram showing an example of the web page 42 displayed on the touch panel 36d of the UE 36 according to the present embodiment. Video content 44 and advertising content 46 are arranged on the web page 42 according to this embodiment.

In this embodiment, for example, data is transmitted from the data providing device to the UE 36 in response to a transmission request from the UE 36. The video content server 30 and advertising content server 32 described above correspond to an example of a data providing device. Hereinafter, the data transmitted from the data providing device to the UE 36 will be referred to as target data.

The UE 36 according to the present embodiment acquires target data of the video content 44 from the video content server 30 and acquires target data of the advertising content 46 from the advertising content server 32. Then, the UE 36 generates a web page 42 on which video content 44 and advertising content 46 are arranged based on the acquired target data, and displays the web page 42 on the touch panel 36d.

Hereinafter, a process related to acquiring target data executed by the communication system 1 according to the present embodiment will be described.

The agent server 28 according to this embodiment issues a virtual IP address in response to a request from the UE 36. Here, for example, an application for issuing a virtual IP address may be installed in the UE 36 in advance. Then, when the user performs a predetermined operation on the UE 36, the UE 36 may transmit a virtual IP address allocation request to the agent server 28. Then, the agent server 28 may transmit a new virtual IP address to the UE 36 in response to receiving the payout request.

Hereinafter, it is assumed that the virtual IP address issued from the agent server 28 to the UE 36 is "a1.a1.a1.a1".

Furthermore, the UE 36 according to this embodiment can be set with a plurality of real IP addresses. For example, a real IP address may be set in each of the first communication unit 36ca and the second communication unit 36cb.

Here, for example, it is assumed that "b1.b1.b1.b1" is set as the real IP address (global IP address) of the first communication unit 36ca. This global IP address is given to the UE 36 by, for example, the SMF included in the autonomous system 10a.

For example, it is assumed that "c1.c1.c1.c1" is set as the real IP address (global IP address) of the second communication unit 36cb. This global IP address is given to the UE 36 by, for example, the SMF included in the autonomous system 10b.

It is also assumed that "b2.b2.b2.b2" is set as the real IP address (private IP address) of the first communication unit 36ca. It is assumed that "c2.c2.c2.c2" is set as the real IP address (private IP address) of the second communication unit 36cb.

It is assumed that "b2.b2.b2.b2" is a private IP address associated with the global IP address "b1.b1.b1.b1". Furthermore, it is assumed that "c2.c2.c2.c2" is a private IP address associated with the global IP address "c1.c1.c1.c1".

It is assumed that the IP address "b1.b1.b1.b1" and the IP address "b2.b2.b2.b2" are IP addresses used in communication performed via the communication path 40a. Further, it is assumed that the IP address "c1.c1.c1.c1" and the IP address "c2.c2.c2.c2" are IP addresses used in communication performed via the communication path 40b.

Note that a plurality of virtual NICs may be installed in the UE 36, and a real IP address may be set for each of the plurality of virtual NICs. In this case, the UE 36 may include only one communication unit 36c.

Further, the IP address of the video content server 30 is "d1.d1.d1.d1", the IP address of the advertising content server 32 is "e1.e1.e1.e1", and the IP address of the agent server 28 is " f1.f1.f1.f1". It is also assumed that these IP addresses are stored in the UE 36, and that the UE 36 already recognizes, for example, the IP addresses of the video content server 30, advertising content server 32, and agent server 28.

Furthermore, in this embodiment, route information is exchanged in advance between the gateway router 26a, the gateway router 26b, the gateway router 26c, and the gateway router 26d via the Internet exchange 34 using the BGP protocol.

For example, the route information related to "b1.b1.b1.b1", which is the real IP address (global IP address) of the first communication unit 36ca, is advertised to the Internet exchange 34 by the gateway router 26a. Furthermore, the route information related to “c1.c1.c1.c1”, which is the real IP address (global IP address) of the second communication unit 36cb, is advertised to the Internet exchange 34 by the gateway router 26b.

As a result of the above-mentioned exchange of route information, packets that reach the Internet exchange 34 and have "b1.b1.b1.b1" set as the destination address are transferred to the gateway router 26a. This packet further reaches the UE 36 via the CGN server 24a, the core network system 22a, and the RAN 20a.

Also, packets that reach the Internet exchange 34 and have "c1.c1.c1.c1" set as the destination address are transferred to the gateway router 26b. This packet further reaches the UE 36 via the CGN server 24b, core network system 22b, and RAN 20b.

Furthermore, a private AS number is assigned to the agent server 28, and route information is exchanged between the gateway router 26c and the agent server 28 using the BGP protocol using the private AS number.

Then, the route information related to "a1.a1.a1.a1", which is the virtual IP address issued by the agent server 28, is advertised to the Internet exchange 34 by the gateway router 26c.

A packet whose destination address is set to "a1.a1.a1.a1" that reaches the Internet exchange 34 through the above-mentioned exchange of route information is transferred to the agent server 28 via the gateway router 26c. It looks like this.

Additionally, the gateway router 26c advertises the route information related to "f1.f1.f1.f1", which is the IP address of the agent server 28, to the Internet exchange 34.

A packet whose destination address is set to "f1.f1.f1.f1" that reaches the Internet exchange 34 through the above-mentioned exchange of route information is transferred to the agent server 28 via the gateway router 26c. It looks like this.

Further, the gateway router 26d provides route information related to "d1.d1.d1.d1", which is the IP address of the video content server 30, and "e1.e1.e1.e1", which is the IP address of the advertising content server 32. The route information related to the route is advertised to the Internet exchange 34.

As a result of the above-mentioned exchange of route information, the packet with "d1.d1.d1.d1" set as the destination address that reaches the Internet exchange 34 is transferred to the video content server 30 via the gateway router 26d. It has become so. Furthermore, packets that reach the Internet exchange 34 and have "e1.e1.e1.e1" set as the destination address are transferred to the advertising content server 32 via the gateway router 26d. .

FIG. 6 is a diagram showing an example of communication route management data according to the present embodiment. The communication route management data shown in FIG. 6 is stored in the agent server 28, for example.

The communication route management data includes, for example, a user ID, virtual IP address data, real IP address data, route ID, and type data.

The user ID included in the communication path management data is identification information of the user who uses the UE 36. The virtual IP address data included in the communication route management data is data indicating a virtual IP address issued to the UE 36. The real IP address data included in the communication path management data is data indicating the real IP address (here, for example, the global IP address) of the UE 36. The route ID included in the communication route management data is identification information of the communication route 40. The type data included in the communication route management data is identification information of the type of target data.

The communication route management data shown at the top in FIG. This is an example of communication route management data that is associated with. The value of the user ID of the communication route management data associated with the communication route 40a shown in FIG. 6 is "A", the value of the virtual IP address data is "a1.a1.a1.a1", The value of the real IP address data is "b1.b1.b1.b1", the value of the route ID is "1", and the value of the type data is "1". Further, the value of the user ID of the communication route management data associated with the communication route 40b shown in FIG. 6 is "A", and the value of the virtual IP address data is "a1.a1.a1.a1". Yes, the value of the real IP address data is "c1.c1.c1.c1", the value of the route ID is "2", and the value of the type data is "2".

In this embodiment, for example, the UE 36 may transmit a packet to the agent server 38 via each of the first communication unit 36ca and the second communication unit 36cb in response to receiving the virtual IP address. Each of these two packets may include a user ID and identification information of the communication path 40 through which the packet passes. Here, for example, the first communication unit 36ca may transmit a packet including a user ID having a value of "A" and identification information of the communication path 40 having a value of "1". Further, the second communication unit 36cb may transmit a packet including a user ID having a value of "A" and identification information of the communication path 40 having a value of "2".

Based on the packet received from the first communication unit 36ca, the agent server 38 may identify that the source address of this packet is "b1.b1.b1.b1". Then, the agent server 38 has the user ID value "A", the virtual IP address data value "a1.a1.a1.a1" which is the virtual IP address issued to the UE 36, and the real IP address Communication route management data may be generated in which the address data value is "b1.b1.b1.b1" and the route ID value is "1".

Furthermore, the agent server 38 may specify, based on the packet received from the second communication unit 36cb, that the source address of this packet is "c1.c1.c1.c1". Then, the agent server 38 has the user ID value "A", the virtual IP address data value "a1.a1.a1.a1" which is the virtual IP address issued to the UE 36, and the real IP address Communication route management data may be generated in which the address data value is "c1.c1.c1.c1" and the route ID value is "2".

Furthermore, in the present embodiment, the value of the identification information indicated in the type data included in the communication route management data may be determined in advance for each type of target data. In the following description, it is assumed that the value of type data associated with a video is "1", and the value of type data associated with an advertisement is "2".

In the example of FIG. 6, the value of the type data of the communication route management data associated with the communication route 40a generated as described above is set to "1", and the value of the type data of the communication route management data associated with the communication route 40b is set. The value of the type data is set to "2".

In this embodiment, a value determined based on the type of communication path 40 may be set as the value of the type data. For example, when the communication path 40 is a network slice, a value determined based on the type of network slice may be set as the value of the type data. For example, the value of the communication route management data type data corresponding to an eMBB (enhanced Mobile Broadband) network slice is set to "1", and the value of the communication route management data type data corresponding to a network slice other than eMBB is set to "1". may be set to "2".

Furthermore, for example, a value determined based on the performance specifications of the communication path 40, such as the upper limit of the bandwidth, may be set as the value of the type data. For example, the value of the communication route management data type data associated with the communication route 40 with higher performance specifications is set to "1", and the value of the communication route management data type data associated with the other communication route 40 is set to "1". may be set to "2".

Additionally, a measurement agent such as a TWAMP (A Two-Way Active Measurement Protocol) agent may be installed in the agent server 28 and the UE 36. Then, the measurement agent may measure the communication quality of the communication path 40, such as jitter value, error rate, latency, etc. Then, the measurement results of communication quality may be monitored. Then, the value of the type data of communication route management data associated with the communication route 40 with higher communication quality is set to "1", and the value of the type data of communication route management data associated with the other communication route 40 is set. may be set to "2".

In this case, the value of the type data of the communication route management data may be updated based on the communication quality measurement results.

For example, assume that it is detected that the communication quality of the communication path 40a has changed from a state where the communication quality is higher than that of the communication path 40b to a state where the communication quality of the communication path 40b is higher than that of the communication path 40a.

In this case, as shown in FIG. 7, the value of the type data of the communication route management data corresponding to the communication route 40a is updated from "1" to "2", and the value of the type data of the communication route management data corresponding to the communication route 40b is updated. The value of may be updated from "2" to "1".

As explained above, the communication route management data shows the correspondence between the plurality of global IP addresses given to the UE 36 and the virtual IP address issued to the UE 36. As shown in FIGS. 6 and 7, in this embodiment, one virtual IP address "a1.a1.a1.a1" is associated with multiple global IP addresses. Specifically, for example, the virtual IP address is associated with a first global IP address "b1.b1.b1.b1" and a second global IP address "c1.c1.c1.c1". There is.

FIG. 8 is a diagram schematically showing an example of the correspondence between global IP addresses and private IP addresses. As described above, the global IP address "b1.b1.b1.b1" is associated with the private IP address "b2.b2.b2.b2". Further, the global IP address "c1.c1.c1.c1" is associated with the private IP address "c2.c2.c2.c2". The CGN server 24a performs address translation between the global IP address "b1.b1.b1.b1" and the private IP address "b2.b2.b2.b2." The CGN server 24b performs address translation between the global IP address "c1.c1.c1.c1" and the private IP address "c2.c2.c2.c2."

FIG. 9 is a diagram schematically showing an example of an IP header of a packet requesting transmission of target data of the video content 44. As shown in FIG. 9, in the IP header, the virtual IP address of the UE 36 is set as the source address, and the IP address of the video content server 30 is set as the destination address.

Furthermore, the UE 36 according to the present embodiment has a function of determining the type of target data.

For example, a list of IP addresses of advertisement senders may be stored in the UE 36. Then, if the destination address of the IP header is included in the list, the UE 36 may determine that the type of target data is an advertisement.

Alternatively, the UE 36 may store a list of domain names of advertisement senders. Then, if the domain name corresponding to the destination address of the IP header is included in the list, the UE 36 may determine that the type of target data is an advertisement. In addition, by executing an inquiry to the DNS server, the UE 36 can specify the domain name corresponding to the IP address based on the IP address, or specify the IP address corresponding to the domain name based on the domain name. It is possible to do so.

Alternatively, a list of URLs of advertisement transmission sources may be stored in the UE 36. Then, if the URL of the destination of the transmission request is included in the list, the UE 36 may determine that the type of target data is an advertisement.

Furthermore, for example, a list of IP addresses of video transmission sources may be stored in the UE 36. Then, if the destination address of the IP header is included in the list, the UE 36 may determine that the type of target data is a moving image.

Alternatively, the UE 36 may store a list of domain names of video senders. Then, if the domain name corresponding to the destination address of the IP header is included in the list, the UE 36 may determine that the type of target data is a video.

Alternatively, a list of URLs of video transmission sources may be stored in the UE 36. Then, if the URL of the destination of the transmission request is included in the list, the UE 36 may determine that the type of target data is a moving image.

Note that the method for determining the type of target data is not limited to the above method. For example, the type of target data may be determined based on metadata such as URL options embedded in the web page 42.

In this embodiment, for example, the value of the route ID of the communication route 40 through which this transmission request passes, and the value of the option indicating the value of the type data corresponding to the type of target data identified as described above, are set. , is set in the IP header. In the example of FIG. 9, option values are shown in the format "(route ID value)-(type data value)".

Here, when the transmission request is transmitted via the communication route 40a via the first communication unit 36ca, "1" is set as the value of the route ID shown in the option. When the transmission request is transmitted via the communication path 40b via the second communication unit 36cb, "2" is set as the value of the path ID shown in the option.

For example, if the type of target data specified as described above is a moving image, "1" is set as the value of the type data shown in the option. If the type of target data is an advertisement, "2" is set as the value of the type data shown in the option.

Here, for example, it is assumed that the transmission request is transmitted via the communication path 40a via the first communication unit 36ca. In this case, as shown in FIG. 9, "1" is set in the IP header as the route ID value shown in the option.

For example, assume that the type of target data is determined to be a moving image based on the IP address "d1.d1.d1.d1" set as the destination address of the IP header. In this case, as shown in FIG. 9, "1" is set in the IP header as the value of the type data indicated in the option.

Then, as shown in FIG. 10, the UE 36 adds a capsule header to the transmission request to which the IP header shown in FIG. 9 has been added. The source address of the capsule header is set to the IP address "b2.b2.b2.b2" which is the private IP address of the first communication unit 36ca of the UE 36, and the destination address is set to the IP address of the agent server 28. "f1.f1.f1.f1" is set.

Then, the UE 36 transmits the transmission request to which the capsule header is added as described above. The transmission request is transmitted, for example, from the first communication unit 36ca.

Then, the transmission request reaches the CGN server 24a via the communication path 40a.

Then, as shown in FIG. 11, the CGN server 24a changes the source address of the capsule header of the transmission request to the IP address "b2.b2.b2.b2" which is the private IP address of the first communication unit 36ca of the UE 36. is rewritten to the IP address "b1.b1.b1.b1" which is the global IP address of the first communication unit 36ca of the UE 36.

Then, the CGN server 24a transmits the transmission request. Then, the transmission request reaches the agent server 28 via the gateway router 26a, the Internet exchange 34, and the gateway router 26c.

Then, the agent server 28 removes the capsule header from the transmission request. Then, the agent server 28 holds the value of the source address (the value of the virtual IP address of the UE 36) set in the IP header of the transmission request, and the value of the option. The agent server 28 then transmits the transmission request with the capsule header removed. This transmission request reaches the video content server 30 via the gateway router 26c, the Internet exchange 34, and the gateway router 26d.

Then, the video content server 30 transmits the target data of the video content 44 as a response to the transmission request.

FIG. 12 is a diagram schematically showing an example of an IP header of a packet of target data of this video content 44. As shown in FIG. 12, in the IP header, the IP address of the video content server 30 is set as the source address, and the virtual IP address of the UE 36 is set as the destination address.

The target data of the video content 44 reaches the agent server 28 via the gateway router 26d, the Internet exchange 34, and the gateway router 26c.

Then, the agent server 28 identifies the source address value and option value set in the IP header of the transmission request associated with the target data of the video content 44.

Then, the agent server 28 identifies, in the communication route management data, the value of real IP address data associated with the combination of the identified source address value and the type data value indicated in the option.

For example, communication path management data is specified that includes the value of the specified source address and the value of type data indicated in the specified option as the value of virtual IP address data and the value of type data, respectively. Here, for example, the communication path management data shown at the top of FIG. 6 is specified. The agent server 28 then identifies the value of the real IP address data included in the identified communication path management data.

Then, as shown in FIG. 13, the agent server 28 adds a capsule header to the target data of the video content 44 to which the IP header shown in FIG. 12 has been added. The source address of the capsule header is set to "f1.f1.f1.f1", which is the IP address of the agent server 28, and the destination address is set to the global IP address associated with the value of the specified real IP address data. Address is set.

Here, for example, as shown in FIG. 13, the agent server 28 sets the specified real IP address data value "b1.b1.b1.b1" to the destination address of the capsule header.

Then, the agent server 28 transmits the target data of the video content 44 to which the capsule header has been added as described above. The target data of the video content 44 reaches the CGN server 24a via the gateway router 26c, the Internet exchange 34, and the gateway router 26a.

Then, as shown in FIG. 14, the CGN server 24a changes the destination address of the capsule header of the transmission request from the IP address "b1.b1.b1.b1" which is the global IP address of the first communication unit 36ca of the UE 36. , is rewritten to the IP address "b2.b2.b2.b2" which is the private IP address of the first communication unit 36ca of the UE 36.

Then, the CGN server 24a transmits the target data of the video content 44. Then, the target data of the video content 44 reaches the UE 36 via the communication path 40a.

In this way, the UE 36 acquires the target data of the video content 44.

FIG. 15 is a diagram schematically showing an example of an IP header of a packet requesting transmission of target data of advertising content 46 generated by UE 36 according to the present embodiment. As shown in FIG. 15, in the IP header, the virtual IP address of the UE 36 is set as the source address, and the IP address of the advertising content server 32 is set as the destination address.

Then, the UE 36 determines the type of target data, as described above. Here, for example, assume that the type of target data is identified as advertisement based on the IP address "e1.e1.e1.e1" set as the destination address of the IP header. In this case, as shown in FIG. 15, "2" is set in the IP header as the value of the type data indicated in the option.

It is also assumed that this transmission request is also transmitted via the communication path 40a via the first communication unit 36ca. In this case, as shown in FIG. 15, "1" is set in the IP header as the route ID value shown in the option.

Then, as shown in FIG. 16, the UE 36 adds a capsule header to the transmission request to which the IP header shown in FIG. 15 has been added. Here, for example, a capsule header similar to the capsule header shown in FIG. 10 is added.

Then, as shown in FIG. 17, the CGN server 24a changes the source address of the capsule header of the transmission request to the IP address "b2.b2.b2.b2" which is the private IP address of the first communication unit 36ca of the UE 36. is rewritten to the IP address "b1.b1.b1.b1" which is the global IP address of the first communication unit 36ca of the UE 36.

Then, the agent server 28 removes the capsule header from the transmission request. Then, the agent server 28 holds the value of the source address (the value of the virtual IP address of the UE 36) set in the IP header of the transmission request, and the value of the option. The agent server 28 then transmits the transmission request with the capsule header removed. This transmission request reaches the advertising content server 32 via the gateway router 26c, the Internet exchange 34, and the gateway router 26d.

Then, the advertising content server 32 transmits the target data of the advertising content 46 as a response to the transmission request.

FIG. 18 is a diagram schematically showing an example of an IP header of a packet of target data of this advertising content 46. As shown in FIG. 18, in the IP header, the IP address of the advertising content server 32 is set as the source address, and the virtual IP address of the UE 36 is set as the destination address.

The target data of the advertising content 46 reaches the agent server 28 via the gateway router 26d, the Internet exchange 34, and the gateway router 26c.

Then, the agent server 28 identifies the source address value and option value set in the IP header of the transmission request associated with the target data of the advertising content 46.

Then, the agent server 28 identifies, in the communication path management data, the value of real IP address data associated with the combination of the identified source address value and the type data value indicated in the option. For example, communication path management data is specified that includes the value of the specified source address and the value of type data indicated in the specified option as the value of virtual IP address data and the value of type data, respectively. Here, for example, the communication route management data shown second from the top in FIG. 6 is specified.

Then, the agent server 28 identifies the value of the real IP address data included in the identified communication path management data.

Then, as shown in FIG. 19, the agent server 28 adds a capsule header to the target data of the advertising content 46 to which the IP header shown in FIG. 18 has been added. The source address of the capsule header is set to "f1.f1.f1.f1", which is the IP address of the agent server 28, and the destination address is set to the global IP address associated with the value of the specified real IP address data. Address is set.

Here, for example, as shown in FIG. 19, the agent server 28 sets the specified real IP address data value "c1.c1.c1.c1" to the destination address of the capsule header.

Then, the agent server 28 transmits the target data of the advertising content 46 to which the capsule header has been added as described above. The target data of the advertising content 46 reaches the CGN server 24b via the gateway router 26c, the Internet exchange 34, and the gateway router 26b.

Then, as shown in FIG. 20, the CGN server 24b changes the destination address of the capsule header of the transmission request from the IP address "c1.c1.c1.c1" which is the global IP address of the second communication unit 36cb of the UE 36. , is rewritten to the IP address "c2.c2.c2.c2" which is the private IP address of the second communication unit 36cb of the UE 36.

Then, the CGN server 24b transmits the target data of the advertising content 46. Then, the target data of the advertising content 46 reaches the UE 36 via the communication path 40b.

In this way, the UE 36 obtains target data of the advertising content 46.

In this embodiment, as described above, the communication path of the target data is controlled depending on the type of target data. In this manner, according to the present embodiment, it is possible to accurately control the communication path of target data transmitted from the data providing device to the UE 36 in response to a transmission request from the UE 36.

For example, target data with low importance can be transmitted via a communication path with a slow communication speed or a high latency.

In addition, for example, operators such as telecommunications carriers may impose certain restrictions on high-quality communication routes (e.g., high-quality network slices) (e.g., on the amount of data that users can communicate under pay-as-you-go charges). It is assumed that there will be an upper limit, etc.). For example, in such a situation, according to the present embodiment, it is possible to transmit the advertising content 46 while avoiding the communication route with such restrictions.

Note that in this embodiment, "c2.c2.c2.c2" may be set as the source address of the capsule header added to the transmission request instead of "b2.b2.b2.b2". Then, "2" may be set as the value of the route ID shown in the option. In this case, the transmission request will reach the agent server 28 via the second communication unit 36cb and the communication path 40b. For example, if the communication path 40a is a communication path with the above-mentioned restrictions, by doing so, it is possible to suppress the amount of communication on the communication path 40a.

Further, in the case where communication is encrypted in this embodiment, the UE 36 determines the type of target data, determines the communication route, and associates the communication route information with the transmission request before the communication is encrypted. may be performed.

In this embodiment, as described above, a global IP address is assigned to the UE 36 by the SMF or the like, but the assigned global IP address may be changed. Even if the agent server 28 transmits target data to the global IP address before the change after the global IP address is changed, this target data does not reach the UE 36.

In order to prevent such a situation from occurring, the agent server 28 according to the present embodiment may update the communication path management data in response to detecting that the global IP address assigned to the UE 36 has been changed. good.

For example, when the agent server 28 receives a transmission request, it may specify the source address value (the real IP address value of the UE 36) set in the capsule header of the transmission request. Furthermore, even if the agent server 28 specifies the value of the source address set in the IP header of the transmission request (the value of the virtual IP address of the UE 36) and the value of the route ID indicated in the option, good.

The agent server 28 then creates a communication route that includes the source address set in the IP header and the route ID value indicated in the specified option as the value of the virtual IP address data and the value of the route ID, respectively. Management data may also be specified.

Then, the agent server 28 determines whether the real IP address data included in the specified communication route management data matches the value of the source address set in the capsule header specified as described above. You may also check to see if they are the same or different.

Here, if it is confirmed that there is a difference, the agent server 28 changes the value of the real IP address data included in the communication path management data to the value of the source address set in the capsule header of the transmission request. It may be updated to a value.

For example, as shown in FIG. 21, assume that the global IP address assigned to the first communication unit 36ca is changed from "b1.b1.b1.b1" to "b1.b1.b1.bx". In this case, as shown in FIG. 22, the source address of the capsule header included in the transmission request received by the agent server 28 is "b1.b1.b1.bx".

For example, in response to receiving such a transmission request, the agent server 28 determines that the value of the virtual IP address data is "a1.a1.a1.a1" and the value of the route ID, as shown in FIG. The value of the real IP address data of the communication path management data where is "1" is updated from "b1.b1.b1.b1" to "b1.b1.b1.bx".

Then, as shown in FIG. 24, the agent server 28 adds a capsule with the value "b1.b1.b1.bx" set to the destination address to the target data transmitted from the video content server 30 that received the transmission request. Add header.

By doing the above, the agent server 28 can accurately transmit target data to the UE 36 even if the global IP address assigned to the UE 36 is changed.

Additionally, the agent server 28 may notify the UE 36 of the value of the real IP address data included in the communication route management data. Then, as shown in FIG. 25, the UE 36 may transmit to the agent server 28 a transmission request including an option indicating the value of the notified real IP address data instead of the route ID value. In the example of FIG. 25, the option value is shown in the format "(value of notified real IP address data)-(value of type data)".

Then, the agent server 28 determines whether the value of the real IP address data indicated in the option of the received transmission request and the value of the source address set in the capsule header of the transmission request match or are different. You may want to check if it is.

In this case as well, the agent server 28 will be able to accurately transmit the target data to the UE 36 even if the global IP address assigned to the UE 36 is changed.

Note that the value of the real IP address data of the communication route management data does not need to be updated based on the target data transmission request. For example, the IP header option or payload of a packet used to measure communication quality by the measurement agent may include the value of the route ID of the communication route 40 that the packet passes through. Further, the value of the virtual IP address issued to the UE 36 may be included in the option or payload of the IP header of the packet.

For example, when the agent server 28 receives this packet, it may specify the value of the source address of the packet (the value of the real IP address of the UE 36). Furthermore, the agent server 28 may specify the values (route ID value and virtual IP address value) shown in the options or payload of the IP header of the packet.

Then, the agent server 28 may specify communication route management data that includes the values of the specified virtual IP address and the specified route ID as the value of the virtual IP address data and the value of the route ID, respectively.

Then, the agent server 28 checks whether the value of the real IP address data included in the specified communication route management data matches or differs from the value of the source address specified as described above. You may.

Here, if it is confirmed that there is a difference, the agent server 28 updates the value of the real IP address data included in the communication route management data to the value of the source address specified as described above. You may.

In this case as well, even if a packet in which the value of the real IP address data notified from the agent server 28 is indicated in the option or payload of the IP header instead of the value of the route ID is sent to the agent server 28. good.

The agent server 28 then checks whether the value of the real IP address data indicated in the option or payload of the received packet matches or differs from the value of the source address of the packet. good.

Here, if it is confirmed that there is a difference, the agent server 28 may update the value of the real IP address data included in the communication route management data to the value of the source address of the packet.

Further, in the above explanation, the value of the real IP address data corresponding to the first communication unit 36ca in the communication route management data is updated based on the packet transmitted via the communication route 40a. , the value of the real IP address data corresponding to the second communication unit 36cb in the communication route management data may be updated based on the packet transmitted via the communication route 40b.

Hereinafter, the functions of the UE 36 and the agent server 28 according to the present embodiment, and the processes executed by the UE 36 and the agent server 28 according to the present embodiment will be further described.

FIG. 26 is a functional block diagram showing an example of functions implemented in the UE 36 and the agent server 28 according to the present embodiment. Note that the UE 36 and agent server 28 according to this embodiment do not need to implement all of the functions shown in FIG. 26, and functions other than those shown in FIG. 26 may be implemented.

As shown in FIG. 26, the UE 36 according to the present embodiment functionally includes, for example, a virtual IP address management section 50, a determination section 52, a transmission request generation section 54, a terminal encapsulation section 56, a transmission request transmission section 58. , a target data receiving section 60, a display control section 62, and a terminal monitoring agent section 64. The virtual IP address management section 50 is mainly implemented with a processor 36a, a storage section 36b, a first communication section 36ca, and a second communication section 36cb. The determination unit 52 is mainly implemented with a processor 36a and a storage unit 36b. The transmission request generation unit 54 and the terminal encapsulation unit 56 are mainly implemented in the processor 36a. The transmission request transmitting section 58 and the target data receiving section 60 are mainly implemented by the first communication section 36ca and the second communication section 36cb. The display control unit 62 is mainly implemented with a processor 36a and a touch panel 36d. The terminal monitoring agent section 64 is mainly implemented with a processor 36a, a first communication section 36ca, and a second communication section 36cb.

The above functions may be implemented by having the UE 36, which is a computer, execute a program installed in the UE 36 that includes commands corresponding to the above functions. Further, this program may be supplied to the UE 36 via a computer-readable information storage medium such as an optical disk, a magnetic disk, a magnetic tape, or a magneto-optical disk, or via the Internet.

Further, as shown in FIG. 26, the agent server 28 according to the present embodiment functionally includes, for example, a corresponding data storage section 70, a virtual IP address allocation section 72, a transmission request relay section 74, and a relay decapsulation section. 76, a target data relay unit 78, a relay encapsulation unit 80, a relay monitoring agent unit 82, and a corresponding data update unit 84. The corresponding data storage section 70 is mainly implemented with the storage section 28b. The virtual IP address issuing unit 72 and the relay monitoring agent unit 82 are mainly implemented using the processor 28a and the communication unit 28c. The transmission request relay section 74 is mainly implemented with the storage section 28b and the communication section 28c. The relay decapsulation unit 76, the relay encapsulation unit 80, and the corresponding data update unit 84 are mainly implemented in the processor 28a. The target data relay section 78 is mainly implemented with the communication section 28c.

The above functions may be implemented by having the agent server 28 execute a program that is installed on the agent server 28, which is a computer, and includes commands corresponding to the above functions. Further, this program may be supplied to the agent server 28 via a computer-readable information storage medium such as an optical disk, a magnetic disk, a magnetic tape, or a magneto-optical disk, or via the Internet.

In this embodiment, the virtual IP address management unit 50 transmits a virtual IP address allocation request to the agent server 28, for example.

In this embodiment, the virtual IP address issuing unit 72 issues a virtual IP address to the UE 36, for example. The virtual IP address issuing unit 72 transmits a new virtual IP address to the UE 38, for example, in response to receiving a request for issuing a virtual IP address transmitted from the UE 36.

The virtual IP address management unit 50 may receive the virtual IP address transmitted from the virtual IP address distribution unit 72 and hold virtual IP address data indicating the received virtual IP address.

Furthermore, the virtual IP address issuing unit 72 may generate correspondence data based on the virtual IP address issued to the UE 36, and store the generated correspondence data in the correspondence data storage unit 70.

In this embodiment, the determining unit 52 determines, for example, the type of target data that the data providing device is requested to transmit. As described above, the determination unit 52 may determine the type of target data based on the destination of the target data. The above-mentioned video content server 30 and advertising content server 32 correspond to an example of a data providing device.

The determining unit 52 may determine whether the target data is the advertising content 46.

As described above, the determination unit 52 includes a list of IP addresses of video senders, a list of domain names of video senders, a list of URLs of video senders, a list of IP addresses of advertisement senders, and a list of IP addresses of video senders. Reference data such as a list of domain names of senders of advertisements, a list of URLs of senders of advertisements, etc. may be stored in advance. The determination unit 52 may determine the type of target data based on the reference data.

In this embodiment, the transmission request generation unit 54 generates an IP header in which, for example, the virtual IP address stored in the virtual IP address management unit 50 is set as the source address, and the IP address of the data providing device is set as the destination address. Generate a request to send targeted data, including:

Here, the transmission request generation unit 54 may generate a transmission request that is associated with type information that is associated with the determination result of the type of target data by the determination unit 52. For example, the type data shown in the option set in the IP header shown in FIGS. 9 to 11 and FIGS. 15 to 17 corresponds to an example of type information associated with the transmission request. .

In this embodiment, the terminal encapsulation unit 56 adds, for example, to the transmission request generated by the transmission request generation unit 54, a capsule header in which the IP address of the relay device is set as the destination address. The agent server 28 described above corresponds to an example of a relay device.

In the present embodiment, the transmission request transmitter 58 transmits, for example, a request to transmit target data associated with type information associated with the determination result of the target data type by the determination unit 52 to the relay device. The transmission request transmitting unit 58 transmits, for example, a target data transmission request generated by the transmission request generating unit 54 and to which a capsule header is added by the terminal encapsulating unit 56 to the relay device.

Here, for example, as described above, a transmission request may be transmitted in which the value of the option associated with the determination result of the type of target data by the determination unit 52 is set in the IP header.

In the present embodiment, the correspondence data storage unit 70 stores, for example, correspondence data indicating the correspondence between a plurality of global IP addresses given to the UE 36 and a virtual IP address issued to the UE 36. For example, the communication route management data shown in FIGS. 6 and 7 corresponds to an example of the corresponding data.

In the present embodiment, the global IP address shown in the correspondence data may be associated with a communication route set between the UE 36 and the relay device.

Furthermore, in the present embodiment, each of the plurality of global IP addresses shown in the correspondence data may be a global IP address assigned to the UE 36 from a mutually different autonomous system 10.

In this embodiment, the transmission request relay unit 74 receives, for example, a target data transmission request from the UE 36 and transmits the transmission request to the data providing device.

In this embodiment, the relay decapsulation unit 76 removes the capsule header from the transmission request to which the capsule header is attached, for example.

Here, as described above, the transmission request relay unit 74 receives the transmission request from the UE 36, the relay decapsulation unit 76 removes the capsule header from the transmission request, and the transmission request relay unit 74 removes the capsule header from the transmission request. The removed transmission request may be transmitted to the data providing device.

In this embodiment, the target data relay unit 78 receives, for example, target data transmitted from a data providing device that has received a transmission request. As described above, the destination address of this target data is set to the virtual IP address issued to the UE 36, which is the source of the transmission request for the target data.

In this embodiment, the target data relay unit 78 selects the target data from among the plurality of global IP addresses that are associated with the virtual IP address in the correspondence data stored in the correspondence data storage unit 70, for example. The target data is transmitted to a global IP address determined based on the type indicated by the type information associated with the transmission request.

In this embodiment, the relay encapsulation unit 80 adds, for example, a capsule header to the target data received from the data providing device, in which the global IP address determined based on the type indicated by the above-mentioned type information is set as the destination address. do.

For example, the target data relay unit 78 adds an IP header in which the IP address of the data providing device is set as the source address and the virtual IP address of the UE 36 is set as the destination address, as shown in FIGS. 12 and 18. The target data may also be received.

Then, the relay encapsulation unit 80 may specify a plurality of communication path management data including the virtual IP address set as the destination address of the target data. Then, the relay encapsulation unit 80 identifies communication route management data that includes the type data value indicated in the option of the transmission request of the target data from among the plurality of identified communication route management data. good.

Then, as shown in FIGS. 13 and 19, the relay encapsulation unit 80 converts the value of the real IP address data included in the specified communication route management data into the target data as shown in FIGS. 12 and 18. A capsule header in which the global IP address is set as the destination address may be added.

For example, it is assumed that the communication path management data shown in FIG. 6 is stored in the correspondence data storage unit 70. In this case, if the value of the type data shown in the option set in the IP header of the transmission request is "1", the capsule header with "b1.b1.b1.b1" set as the destination address is It may be provided. If the value of the type data indicated in the option set in the IP header of the transmission request is "2", a capsule header with "c1.c1.c1.c1" set as the destination address is added. It is also possible to do so.

Here, as described above, the target data relay unit 78 receives the target data transmitted from the data providing device, the relay encapsulation unit 80 adds the above-mentioned capsule header to the target data, and the target data relay unit 78 may transmit the target data to which the capsule header is attached.

In this embodiment, the target data receiving unit 60 receives target data, for example.

In this embodiment, the display control unit 62 causes the touch panel 36d to display the target data received by the target data receiving unit 60, for example. For example, as shown in FIG. 5, the display control unit 62 generates a web page 42 in which video content 44 and advertising content 46 are arranged, and displays the generated web page 42 on the touch panel 36d.

The terminal monitoring agent unit 64 and the relay monitoring agent unit 82 monitor the communication quality (for example, jitter value, error rate, latency, etc.) of a plurality of communication paths set between the relay device and the UE 36. For example, the terminal monitoring agent section 64 and the relay monitoring agent section 82 communicate with each other to determine the communication quality (for example, jitter value, error rate, latency, etc.). Here, for example, the communication quality of the communication path 40a and the communication path 40b is measured. Then, the terminal monitoring agent section 64 and the relay monitoring agent section 82 monitor the communication quality of the communication path 40a and the communication path 40b, for example, by measuring the communication quality at predetermined time intervals.

Further, the UE 36 according to the present embodiment may include an identification information transmitting unit that transmits identification information of a communication path set between the UE 36 and the relay device to the relay device via the communication path.

For example, when generating a transmission request, the transmission request generation unit 54 may generate a transmission request associated with identification information of the communication path 40 through which the transmission request passes. Then, the transmission request transmitter 58 may transmit the transmission request associated with the identification information of the communication path 40 to the relay device via the communication path 40. For example, the route ID shown in the option set in the IP header shown in FIGS. 9 to 11 and FIGS. 15 to 17 is an example of the route information of the communication route associated with the transmission request. corresponds to Further, in this case, the transmission request transmitter 58 corresponds to an example of the above-mentioned identification information transmitter.

The relay device (for example, the agent server 28) according to the present embodiment may include an identification information receiving unit that receives communication path identification information transmitted from the UE 36. For example, the transmission request relay unit 74 may receive a transmission request for target data associated with communication path identification information. In this case, the transmission request relay section 74 corresponds to an example of an identification information receiving section.

In the present embodiment, the correspondence data updating unit 84 updates the correspondence data, for example, in response to detection that the global IP address assigned to the UE 36 has been changed.

The correspondence data update unit 84 updates the global IP address set as the source address of the communication route identification information transmitted from the UE 36 and the global IP address associated with the communication route identified by the identification information in the correspondence data. If the addresses are different, the global IP address indicated in the correspondence data may be updated to the global IP address set as the source address of the identification information.

For example, the corresponding data updating unit 84 may check the global IP address set as the source address of the capsule header of the target data transmission request transmitted from the UE 36. The corresponding data update unit 84 then updates the global IP address associated with the communication route identified by the communication route identification information associated with the target data transmission request transmitted from the UE 36 in the communication route management data. You may check. Then, the correspondence data updating unit 84 may check, for example, whether the two confirmed global IP addresses match or differ.

If the two confirmed global IP addresses are different, the corresponding data update unit 84 updates the global IP address indicated by the real IP address data included in the communication path management data to the encapsulation of the target data transmission request. It may be updated to the global IP address set in the source address of the header.

Note that, as described above, the IP header option or payload of a packet used to measure communication quality may include identification information of the communication path 40 that the packet passes through. Then, the global IP address set as the source address of the identification information (the source address of the packet) and the global IP address associated with the communication route identified by the identification information in the corresponding data are If different, the global IP address indicated in the corresponding data may be updated to the global IP address set in the source address of the identification information (the source address of the packet).

In this case, the terminal monitoring agent section 64 corresponds to an example of the above-mentioned identification information transmitting section, and the relay monitoring agent section 82 corresponds to an example of the above-mentioned identification information receiving section.

Additionally, the correspondence data updating unit 84 may update the correspondence data based on the monitoring result of the communication quality of the communication path set between the relay device and the UE 36.

Here, the corresponding data may be updated based on the monitoring results of the communication quality of the downlink communication path from the agent server 28 to the UE 36. Further, the correspondence data may be updated based on the monitoring result of the communication quality of the uplink communication path from the UE 36 to the agent server 28. Further, the corresponding data may be updated based on the monitoring results of the communication quality of the uplink communication path and the communication quality of the downlink communication path.

For example, as described above, the terminal monitoring agent unit 64 and the relay monitoring agent unit 82 determine that the communication path 40a has higher communication quality than the communication path 40b, so that the communication path 40b is higher than the communication path 40a. Suppose that it is detected that the communication quality has changed to a high state. In this case, the correspondence data updating unit 84 may update the communication path management data shown in FIG. 6 to the communication path management data shown in FIG. 7.

In this case, the video content 44 is sent to the global IP address "c1.c1.c1.c1", and the advertising content 46 is sent to the global IP address "b1.b1.b1.b1". That will happen. In this way, the target data relay unit 78 monitors the communication quality of the communication path set between the relay device and the UE 36 and the type indicated by the type information associated with the determination result of the target data type. The target data may be sent to a global IP address determined based on , .

Furthermore, the relay device (for example, the agent server 28) according to the present embodiment may include an address notification unit that notifies the UE 36 of the global IP address indicated in the correspondence data.

For example, the virtual IP address issuing unit 72 may notify the UE 36 of the global IP address indicated in the correspondence data. In this case, the virtual IP address dispensing unit 72 corresponds to an example of an address notification unit. Further, the relay monitoring agent unit 82 may notify the UE 36 of the global IP address indicated in the correspondence data. In this case, the relay monitoring agent section 82 corresponds to an example of an address notification section. Furthermore, the target data relay unit 78 may notify the UE 36 of the global IP address indicated in the corresponding data. In this case, the target data relay section 78 corresponds to an example of an address notification section.

Then, the UE 36 may include an address transmitting unit that transmits notification address data in which the global IP address to be notified is indicated in the header option or payload to the relay device.

The relay device (for example, the agent server 28) may include an address receiving unit that receives notification address data transmitted from the UE 36.

For example, the transmission request transmitter 58 may transmit a transmission request including an option indicating the global IP address to be notified, as shown in FIG. Then, the transmission request relay unit 74 may receive the transmission request. In this case, the transmission request transmitting section 58 corresponds to an example of an address transmitting section, and the transmission request relaying section 74 corresponds to an example of an address receiving section. Further, the transmission request corresponds to an example of notification address data.

Additionally, the terminal monitoring agent unit 64 may transmit a packet used for measuring communication quality, in which the global IP address to be notified is indicated in the option or payload of the IP header. Then, the relay monitoring agent unit 82 may receive the packet. In this case, the terminal monitoring agent section 64 corresponds to an example of an address transmitting section, and the relay monitoring agent section 82 corresponds to an example of an address receiving section. Furthermore, a packet used to measure communication quality corresponds to an example of notification address data.

Then, if the global IP address set as the source address of the notification address data and the global IP address indicated in the header option or payload of the notification address data are different, the corresponding data update unit 84 updates the notification address data. The global IP address indicated in the corresponding data may be updated to the global IP address set as the source address of the notification address data.

Here, an example of the flow of processing related to transmission of a target data transmission request performed by the UE 36 and the agent server 28 according to the present embodiment will be described with reference to flowcharts illustrated in FIGS. 27A and 27B. do.

In this processing example, a process will be described in which a target data transmission request is transmitted from the UE 36 to the data providing device, and target data corresponding to the transmission request is transmitted from the data providing device to the UE 36.

First, the determination unit 52 of the UE 36 determines the type of target data (S101).

Then, the transmission request generation unit 54 of the UE 36 generates a transmission request for target data (S102). The transmission request generated in the process shown in S102 is associated with type data indicating the determination result in the process shown in S101 and the route ID of the communication path 40 through which the transmission request passes. Further, the virtual IP address of the UE 36 is set as the source address of the transmission request generated in the process shown in S102, and the IP address of the data providing device that requests transmission of the target data is set as the destination address. .

Then, the terminal encapsulation unit 56 of the UE 36 adds a capsule header to the transmission request generated in the process shown in S102 (S103). The private IP address of the UE 36 is set to the source address of the capsule header added in the process shown in S103, and the IP address of the agent server 28 is set to the destination address.

Then, the transmission request transmitting unit 58 of the UE 36 transmits the transmission request to which the capsule header is attached in the process shown in S103 to the agent server 28, and the transmission request relay unit 74 of the agent server 28 receives the transmission request. (S104). During the transmission request, the source address of the capsule header is changed from the private IP address of the UE 36 to the global IP address associated with the private IP address by the CGN server 24a or the CGN server 24b.

Then, the transmission request relay unit 74 sets the route ID value and IP header associated with the transmission request received in the process shown in S104 from among the communication route management data stored in the corresponding data storage unit 70. The communication route management data whose combination with the value of the transmitted source address matches the combination of the value of the route ID and the value of the virtual IP address data is identified (S105).

Then, the corresponding data updating unit 84 updates the value of the real IP address data included in the communication route management data specified in the process shown in S105 and the value of the source address in the capsule header of the transmission request received in the process shown in S104. It is confirmed whether or not they are different from each other (S106).

If it is confirmed that they are different (S106: Y), the corresponding data update unit 84 updates the value of the real IP address data included in the communication route management data identified in the process shown in S105 to the process shown in S104. The value of the source address of the capsule header of the transmission request received is updated (S107).

When the process shown in S107 is completed, and when it is confirmed that they match in the process shown in S106 (S106: N), the relay decapsulation unit 76 of the agent server 28 performs the process shown in S104. The capsule header is removed from the received transmission request (S108).

Then, the transmission request relay unit 74 of the agent server 28 retains the value of the type data associated with the transmission request received in the process shown in S104 and the value of the source address set in the IP header (S109 ).

The transmission request relay unit 74 of the agent server 28 then addresses the transmission request from which the capsule header has been removed in the process shown in S108 to the data providing device associated with the destination address set in the IP header of the transmission request. Send (S110).

The data providing device that has received the transmission request transmits the target data according to the transmission request, and the target data relay unit 78 of the agent server 28 receives the target data (S111). The IP address of the data providing device is set in the source address of the target data, and the virtual IP address of the UE 36 is set in the destination address.

Then, the target data relay unit 78 of the agent server 28 identifies the IP address set as the destination address of the target data received in the process shown in S111 (S112). In the process shown in S112, for example, the value of the type data held in the transmission request relay unit 74 in the process shown in S109, the value of the source address, and the communication route management data stored in the corresponding data storage unit 70 are used. Based on this, the IP address to be set as the destination address is specified.

Then, the relay encapsulation unit 80 of the agent server 28 adds a capsule header to the target data received in the process shown in S111 (S113). The IP address of the agent server 28 is set in the source address of the capsule header added in the process shown in S113, and the IP address specified in the process shown in S112 is set in the destination address.

Then, the target data relay unit 78 of the agent server 28 transmits the target data to which the capsule header has been added in the process shown in S113 to the UE 36, and the target data receiving unit 60 of the UE 36 receives the target data (S114). ). During the target data, the destination address of the capsule header is changed from the global IP address of the UE 36 to the private IP address associated with the global IP address by the CGN server 24a or the CGN server 24b.

Then, the processing shown in this processing example is ended.

Note that the present invention is not limited to the above-described embodiments.

For example, the present invention is applicable not only to a situation where the UE 36 accesses a plurality of mutually different autonomous systems 10 but also to a situation where the UE 36 accesses a single autonomous system 10. In this case, communication path 40a and communication path 40b may be included in the same autonomous system 10.

Furthermore, the UE 36 according to the present embodiment does not need to be able to use network services provided by multiple operators.

Furthermore, the scope of application of this embodiment is not limited to mobile communication systems such as 4G and 5G, but is also applicable to communication lines such as wireless LAN (Local Area Network) and Bluetooth (registered trademark). For example, the communication path 40a may be a communication path of a mobile communication system, and the communication path 40b may be a communication path of a wireless LAN.

Additionally, the type of target data is not limited to videos and advertisements. For example, it may be determined whether the type of target data is email. Alternatively, it may be determined whether the type of target data is data related to a specific type of social media.

Furthermore, the functional unit according to this embodiment may be realized using hypervisor-type or host-type virtualization technology instead of container-type virtualization technology. Further, the functional unit according to this embodiment does not need to be implemented by software, and may be implemented by hardware such as an electronic circuit. Further, the functional unit according to this embodiment may be implemented by a combination of an electronic circuit and software.

Claims

Including a relay device and a communication terminal,
The relay device is
virtual IP address dispensing means for dispensing a virtual IP address to the communication terminal;
a correspondence data storage means for storing correspondence data indicating a correspondence between a plurality of global IP addresses given to the communication terminal and the virtual IP address;
The communication terminal is
determination means for determining the type of target data that the data providing device is requested to transmit;
a transmission request transmitting means for transmitting, to the relay device, a transmission request for the target data associated with type information associated with the type determination result;
The relay device is
Transmission request relay means that receives the transmission request and transmits the transmission request to the data providing device;
Upon receiving the target data in which the virtual IP address is set as a destination address, which is transmitted from the data providing device that has received the transmission request, the plurality of targets are associated with the virtual IP address in the corresponding data. further comprising: target data relay means for transmitting the target data to the global IP address determined from among the global IP addresses based on the type indicated by the type information;
The communication terminal is
further comprising target data receiving means for receiving the target data;
A communication path control system characterized by:
The communication terminal is capable of accessing multiple autonomous systems, and
Each of the plurality of global IP addresses indicated in the correspondence data is a global IP address assigned to the communication terminal from the autonomous system that is different from each other.
The communication path control system according to claim 1, characterized in that:
The communication terminal includes an IP header in which the virtual IP address is set as a source address and an IP address of the data providing device is set as a destination address, and the IP address of the relay device is set as a destination address. further comprising terminal encapsulation means for providing a capsule header set to
The transmission request transmitting means transmits the transmission request to which the capsule header is attached to the relay device,
The relay device further includes relay decapsulation means for removing the capsule header from the transmission request,
The transmission request relay means transmits the transmission request from which the capsule header has been removed to the data providing device.
The communication path control system according to claim 1, characterized in that:
The relay device further includes a relay encapsulation unit that adds to the target data a capsule header in which the global IP address determined based on the type indicated by the type information is set as a destination address,
The target data relay means transmits the target data to which the capsule header is attached.
The communication path control system according to claim 1, characterized in that:
The relay device further includes correspondence data updating means for updating the correspondence data in response to detection that the global IP address assigned to the communication terminal has been changed.
The communication path control system according to claim 1, characterized in that:
The global IP address indicated in the correspondence data is associated with a communication route set between the communication terminal and the relay device,
The communication terminal further includes identification information transmitting means for transmitting identification information of a communication path set with the relay device to the relay device via the communication path,
The relay device further includes identification information receiving means for receiving the identification information transmitted from the communication terminal,
The correspondence data updating means is configured to determine whether the global IP address set as the source address of the identification information and the global IP address associated with the communication route identified by the identification information in the correspondence data are different. If so, update the global IP address indicated in the corresponding data to the global IP address set as the source address of the identification information;
6. The communication path control system according to claim 5.
The relay device further includes address notification means for notifying the communication terminal of the global IP address indicated in the correspondence data,
The communication terminal further includes address transmitting means for transmitting notification address data in which the global IP address to be notified is indicated in a header option or payload to the relay device,
The relay device further includes address receiving means for receiving the notification address data transmitted from the communication terminal,
When the global IP address set as the source address of the notification address data and the global IP address indicated in the header option or payload of the notification address data are different, the corresponding data updating means may updating the global IP address indicated in the corresponding data to the global IP address set as the source address of the notification address data;
6. The communication path control system according to claim 5.
further comprising communication quality monitoring means for monitoring communication quality of a plurality of communication paths set between the relay device and the communication terminal,
The target data relay means transmits the target data to the global IP address determined based on the communication quality monitoring result and the type indicated by the type information.
The communication path control system according to claim 1, characterized in that:
The determination means determines the type of the target data based on the destination of the target data.
The communication path control system according to claim 1, characterized in that:
virtual IP address dispensing means for dispensing a virtual IP address to a communication terminal;
Correspondence data storage means for storing correspondence data indicating correspondence between a plurality of global IP addresses assigned to the communication terminal and the virtual IP address;
Receiving, from the communication terminal, a transmission request for the target data associated with type information associated with the type of target data that the data providing device is requested to transmit, and transmitting the transmission request to the data providing device. request relay means;
Upon receiving the target data in which the virtual IP address is set as a destination address, which is transmitted from the data providing device that has received the transmission request, the plurality of targets are associated with the virtual IP address in the corresponding data. target data relay means for transmitting the target data to the global IP address determined from among the global IP addresses based on the type indicated by the type information;
A relay device comprising:
determination means for determining the type of target data that the data providing device is requested to transmit;
a transmission request transmitting means for transmitting a transmission request for the target data associated with type information associated with the type determination result to a relay device;
Target data receiving means for receiving the target data transmitted from the relay device to a global IP address determined based on the type indicated by the type information associated with the transmission request;
A communication terminal comprising:
a step in which the relay device issues a virtual IP address to the communication terminal;
a step in which the communication terminal determines the type of target data that the data providing device is requested to transmit;
a step in which the communication terminal transmits a request to transmit the target data associated with type information associated with the type determination result to the relay device;
the relay device receiving the transmission request and transmitting the transmission request to the data providing device;
The relay device receives the target data, in which the virtual IP address is set as a destination address, transmitted from the data providing device that received the transmission request, and transmits a plurality of global IP addresses assigned to the communication terminal. The global IP address is determined based on the type indicated by the type information from among the plurality of global IP addresses associated with the virtual IP address in correspondence data indicating the correspondence between an address and the virtual IP address. sending the target data to;
A communication path control method characterized by comprising:
Procedure for issuing a virtual IP address to a communication terminal,
A step of receiving, from the communication terminal, a transmission request for the target data associated with type information associated with the type of target data that the data providing device is requested to transmit, and transmitting the transmission request to the data providing device. ,
Upon receiving the target data in which the virtual IP address is set as a destination address, which is transmitted from the data providing device that has received the transmission request, a plurality of global IP addresses assigned to the communication terminal and the virtual IP address are sent. to the global IP address determined based on the type indicated by the type information from among the plurality of global IP addresses associated with the virtual IP address in the correspondence data indicating the correspondence with the address; Steps to send target data,
A program that causes a computer to execute.
a step for determining the type of target data that the data providing device is requested to transmit;
a step of transmitting a transmission request for the target data associated with type information associated with the type determination result to a relay device;
a step of receiving the target data transmitted from the relay device to a global IP address determined based on the type indicated by the type information associated with the transmission request;
A program that causes a computer to execute.