[go: up one dir, main page]

WO2023228252A1 - Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme - Google Patents

Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme Download PDF

Info

Publication number
WO2023228252A1
WO2023228252A1 PCT/JP2022/021126 JP2022021126W WO2023228252A1 WO 2023228252 A1 WO2023228252 A1 WO 2023228252A1 JP 2022021126 W JP2022021126 W JP 2022021126W WO 2023228252 A1 WO2023228252 A1 WO 2023228252A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
data
global
communication
target data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2022/021126
Other languages
English (en)
Japanese (ja)
Inventor
誠 大野
一成 竹内
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Rakuten Mobile Inc
Original Assignee
Rakuten Mobile Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rakuten Mobile Inc filed Critical Rakuten Mobile Inc
Priority to PCT/JP2022/021126 priority Critical patent/WO2023228252A1/fr
Publication of WO2023228252A1 publication Critical patent/WO2023228252A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses

Definitions

  • the present invention relates to a communication route control device, a communication route control method, and a program.
  • Patent Document 1 describes a terminal device that can access multiple network slices.
  • 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.
  • 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.
  • An object of the present invention is to provide a controllable communication path control device, a communication path control method, and a program.
  • a communication path control device includes a virtual IP address dispensing means for dispensing a virtual IP address to a communication terminal, a plurality of global IP addresses assigned to the communication terminal, and a virtual a correspondence data storage means for storing correspondence data indicating a correspondence between the IP address and the IP address; a transmission request relay means for receiving a transmission request for target data from the communication terminal and transmitting the transmission request to the data providing apparatus; a determining means for determining the type of target data; Target data relay means for transmitting the target data to the global IP address determined based on the type determination result from among the plurality of global IP addresses associated with the virtual IP address; including.
  • 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 .
  • the target data received from the data providing device is encapsulated with a capsule header in which the global IP address determined based on the type determination result is set as the destination address.
  • the target data relay means transmits the target data to which the capsule header is attached.
  • the transmission request relay unit 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 communication route control unit. a capsule header in which the IP address of the device is set as a destination address; and a decapsulation unit that receives the transmission request to which the IP address of the device is set as a destination address and removes the capsule header from the transmission request to which the capsule header is attached.
  • the transmission request relay means transmits the transmission request from which the capsule header has been removed to the data providing apparatus.
  • one aspect of the present invention further includes a correspondence data updating unit that updates the correspondence data in response to detection that the global IP address assigned to the communication terminal has been changed.
  • the global IP address indicated in the correspondence data is associated with a communication route set between the communication terminal and the communication route set between the communication terminal and the communication terminal.
  • identification information receiving means for receiving identification information from the communication terminal via the communication path, and the corresponding data updating means includes a global IP address set as the source address of the identification information and the corresponding identification information. If the global IP address associated with the communication route identified by the identification information in the data is different, the global IP address shown in the corresponding data is set to the source address of the identification information. It may be updated to the set global IP address.
  • an address notification means for notifying the communication terminal of the global IP address indicated in the correspondence data, and notification address data in which the global IP address to be notified is indicated in a header option or payload from the communication terminal.
  • the correspondence data updating means further includes a global IP address set as the source address of the notification address data and a global IP address indicated in the header option or payload of the notification address data. If the IP address is different, 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.
  • 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 communication terminal, and the target data relay means is configured to monitor the communication quality of a plurality of communication paths set between the communication terminal and the communication terminal.
  • the target data is transmitted to the global IP address determined based on the monitoring result and the type determination result.
  • the determining means determines the type of the target data based on the destination of the target data.
  • the communication route control method includes the steps of issuing a virtual IP address to a communication terminal, receiving a target data transmission request from the communication terminal, and transmitting the transmission request to a data providing device. , a step of determining the type of the target data; and receiving the target data with the virtual IP address set as a destination address transmitted from the data providing device that received the transmission request, and transmitting the target data to the communication terminal. Determined based on the determination result of 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 assigned global IP addresses and the virtual IP address. and transmitting the target data to the global IP address.
  • the program according to the present invention includes a procedure for allocating a virtual IP address to a communication terminal, a procedure for receiving a transmission request for target data from the communication terminal and transmitting the transmission request to a data providing device, and a procedure for transmitting the transmission request for target data to a data providing device.
  • the computer is caused to execute the procedure of transmitting the target data to.
  • FIG. 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. 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. 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.
  • FIG. 1 is a diagram showing an example of a communication system 1 according to an embodiment of the present invention.
  • the communication system 1 includes an autonomous system (AS) 10a, an autonomous system 10b, an autonomous system 10c, and an autonomous system 10d.
  • AS autonomous system
  • the communication system 1 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.
  • RAN radio access network
  • CGN server Network Address Translation server
  • 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.
  • IX Internet exchange
  • 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.
  • 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 provide first network services such as voice communication services and data communication services to users who use the UE 36.
  • 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.
  • the first network service and the second network service are provided by different carriers (for example, communication carriers).
  • 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.
  • IoT Internet of Things
  • 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.
  • a cluster composed of one or more containers generated by such virtualization technology may be constructed.
  • a cluster Kerpannetes cluster
  • a container management tool such as Kubernetes (registered trademark)
  • 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.
  • the functional unit according to this embodiment may correspond to a network node.
  • vDU virtual Distributed Unit
  • vCU virtual Central Unit
  • DU Distributed Unit
  • CU Central Unit
  • CU Central Unit
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • 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.
  • NIC Network Interface Controller
  • LAN Local Area Network
  • FIG. 3 is a diagram showing an example of the configuration of the UE 36 according to the present embodiment.
  • 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 are servers equipped with a carrier grade NAT (CGN) function, and perform conversion between a global IP address and a private IP address.
  • CGN carrier grade NAT
  • 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.
  • the video content server 30 is a server that provides video content data in response to a request from the UE 36, for example.
  • 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.
  • 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.
  • 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.
  • 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)).
  • 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.
  • 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.
  • the data transmitted from the data providing device to the UE 36 will be referred to as target data.
  • the UE 36 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.
  • the agent server 28 issues a virtual IP address in response to a request from the UE 36.
  • 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.
  • the UE 36 can be set with a plurality of real IP addresses.
  • a real IP address may be set in each of the first communication unit 36ca and the second communication unit 36cb.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 36 may include only one communication unit 36c.
  • IP address of the video content server 30 is "d1.d1.d1.d1”
  • IP address of the advertising content server 32 is “e1.e1.e1.e1”
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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”
  • the value of the type data is "1”.
  • the value of the user ID of the communication route management data associated with the communication route 40b 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 "c1.c1.c1.c1"
  • the value of the route ID is "2
  • the value of the type data is "2".
  • 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.
  • 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".
  • 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".
  • 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".
  • 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".
  • 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.
  • the value of type data associated with a video is "1"
  • the value of type data associated with an advertisement is "2”.
  • 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"
  • 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".
  • a value determined based on the type of communication path 40 may be set as the value of the type data.
  • a value determined based on the type of network slice may be set as the value of the type data.
  • the value of the communication route management data type data corresponding to an eMBB (enhanced Mobile Broadband) network slice is set to "1”
  • 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".
  • a value determined based on the performance specifications of the communication path 40 may be set as the value of the type data.
  • the value of the communication route management data type data associated with the communication route 40 with higher performance specifications is set to "1"
  • 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".
  • 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".
  • TWAMP Two-Way Active Measurement Protocol
  • the value of the type data of the communication route management data may be updated based on the communication quality measurement results.
  • the value of the type data of the communication route management data corresponding to the communication route 40a is updated from “1" to "2”
  • 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”.
  • 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.
  • one virtual IP address "a1.a1.a1.a1" is associated with multiple global IP addresses.
  • 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.
  • the global IP address "b1.b1.b1.b1” is associated with the private IP address "b2.b2.b2.b2”.
  • 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.
  • the virtual IP address of the UE 36 is set as the source address
  • the IP address of the video content server 30 is set as the destination address.
  • an optional value indicating the value of the route ID of the communication route 40 through which this transmission request passes is set in the IP header.
  • the transmission request is transmitted via the communication path 40a via the first communication unit 36ca.
  • "1" is set as the option value in the IP header.
  • the UE 38 adds a capsule header to the transmission request to which the IP header shown in FIG. 9 has been added.
  • the IP address "b2.b2.b2.b2" which is the private IP address of the UE 38 is set in the source address of the capsule header, and the IP address "f1.f1.f1" which is the IP address of the agent server 26 is set in the destination address. .f1" is set.
  • the UE 38 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.
  • the transmission request reaches the CGN server 24a via the communication path 40a.
  • 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.
  • 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.
  • the agent server 28 removes the capsule header from the transmission request.
  • the agent server 28 identifies the source address value (the virtual IP address value of the UE 36) set in the IP header of the transmission request.
  • the agent server 28 determines the type of target data.
  • the agent server 28 may store a list of IP addresses of advertisement senders. Then, if the destination address of the IP header is included in the list, the agent server 28 may determine that the type of target data is an advertisement.
  • the agent server 28 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 agent server 28 may determine that the type of target data is an advertisement. Note that by executing an inquiry to the DNS server, the agent server 28 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 specify.
  • the agent server 28 may store a list of URLs of advertisement transmission sources. Then, if the URL of the destination of the transmission request is included in the list, the agent server 28 may determine that the type of target data is an advertisement.
  • the agent server 28 may store a list of IP addresses of video transmission sources. Then, if the destination address of the IP header is included in the list, the agent server 28 may determine that the type of target data is a moving image.
  • the agent server 28 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 agent server 28 may determine that the type of target data is a video.
  • the agent server 28 may store a list of URLs of video transmission sources. Then, if the URL of the destination of the transmission request is included in the list, the agent server 28 may determine that the type of target data is a moving image.
  • the method for determining the type of target data is not limited to the above method.
  • the type of target data may be determined based on metadata such as URL options embedded in the web page 42.
  • the agent server 28 identifies the real IP address corresponding to the type of target data identified in this way based on the communication route management data.
  • the communication includes the value of the specified source address (the value of the virtual IP address of the UE 36) and the value corresponding to the determination result of the target data type as the value of the virtual IP address data and the value of the type data, respectively.
  • Route management data is identified. For example, if it is determined that the type of target data is a moving image, the communication path management data shown at the top of FIG. 6 is specified. Then, the agent server 28 specifies the value "b1.b1.b1.b1" of the real IP address data included in the specified communication route management data.
  • the agent server 28 holds the value of the real IP address data specified in this way.
  • the agent server 26 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.
  • 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.
  • the IP address of the video content server 30 is set as the source address
  • 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.
  • 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 value of the held real IP address data.
  • the agent server 28 sets the held real IP address data value "b1.b1.b1.b1" to the destination address of the capsule header.
  • 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.
  • 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.
  • 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.
  • 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.
  • the virtual IP address of the UE 36 is set as the source address
  • the IP address of the advertising content server 32 is set as the destination address.
  • this transmission request is also transmitted via the communication path 40a via the first communication unit 36ca.
  • "1" is set as the option value in the IP header.
  • the UE 36 adds a capsule header to the transmission request to which the IP header shown in FIG. 15 has been added.
  • a capsule header similar to the capsule header shown in FIG. 10 is added.
  • 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.
  • the transmission request reaches the CGN server 24a via the communication path 40a.
  • 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.
  • 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.
  • the agent server 28 removes the capsule header from the transmission request.
  • the agent server 28 identifies the source address value (the virtual IP address value of the UE 36) set in the IP header of the transmission request.
  • the agent server 28 determines the type of target data.
  • the agent server 28 identifies the value of the real IP address data corresponding to the determination result of the type of target data in this way based on the communication path management data. For example, if it is determined that the type of target data is an advertisement, the communication path management data shown second from the top in FIG. 6 is specified. The agent server 28 then specifies the value "c1.c1.c1.c1" of the real IP address data included in the specified communication path management data.
  • the agent server 28 holds the value of the real IP address data specified in this way.
  • the agent server 26 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.
  • 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.
  • the IP address of the advertising content server 32 is set as the source address
  • 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.
  • 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 value of the held real IP address data.
  • the agent server 28 sets the held real IP address data value "c1.c1.c1.c1" to the destination address of the capsule header.
  • 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.
  • 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.
  • 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.
  • the UE 36 obtains target data of the advertising content 46.
  • 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.
  • target data with low importance can be transmitted via a communication path with a slow communication speed or a high latency.
  • 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.
  • high-quality communication routes e.g., high-quality network slices
  • 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 option value.
  • the transmission request will reach the agent server 28 via the second communication unit 36cb and the communication path 40b.
  • 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.
  • 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.
  • the agent server 28 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.
  • the agent server 28 may specify the source address value (the real IP address value of the UE 36) set in the capsule header of the transmission request. Further, the agent server 28 may specify the source address value (the virtual IP address value of the UE 36) and the option value set in the IP header of the transmission request.
  • the agent server 28 then specifies communication route management data that includes the source address set in the IP header and the value of the specified option as the value of virtual IP address data and the value of route ID, respectively. good.
  • 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.
  • 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.
  • the global IP address assigned to the first communication unit 36ca is changed from “b1.b1.b1.b1” to "b1.b1.b1.bx”.
  • the source address of the capsule header included in the transmission request received by the agent server 28 is "b1.b1.b1.bx”.
  • 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".
  • 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.
  • 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.
  • 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 a transmission request including an option indicating the value of the notified real IP address data to the agent server 28.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the agent server 28 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 36 functionally includes, for example, a virtual IP address management unit 50, a transmission request generation unit 52, a terminal encapsulation unit 54, a transmission request transmission unit 56, a target data reception section 58, display control section 60, and terminal monitoring agent section 62.
  • 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 transmission request generation section 52 and the terminal encapsulation section 54 are mainly implemented in the processor 36a.
  • the transmission request transmitting section 56 and the target data receiving section 58 are mainly implemented with a first communication section 36ca and a second communication section 36cb.
  • the display control unit 60 is mainly implemented with a processor 36a and a touch panel 36d.
  • the terminal monitoring agent section 62 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.
  • 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.
  • the agent server 28 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 determination unit 78, a target data relay unit 80, a relay encapsulation unit 82, a relay monitoring agent unit 84, and a corresponding data update unit 86.
  • the corresponding data storage section 70 is mainly implemented with the storage section 28b.
  • the virtual IP address issuing section 72 and the relay monitoring agent section 84 are mainly implemented by the processor 28a and the communication section 28c.
  • the transmission request relay section 74 and the target data relay section 80 are mainly implemented by the communication section 28c.
  • the relay decapsulation unit 76, the determination unit 78, the relay encapsulation unit 82, and the corresponding data update unit 86 are mainly implemented in the processor 28a.
  • 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.
  • 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.
  • the virtual IP address management unit 50 transmits a virtual IP address allocation request to the agent server 28, for example.
  • 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.
  • 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.
  • the transmission request generation unit 52 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:
  • the terminal encapsulation unit 54 adds, for example, to the transmission request generated by the transmission request generation unit 52, 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.
  • the transmission request transmitting unit 56 transmits, for example, a transmission request for target data to the relay device.
  • the transmission request transmitting unit 56 transmits, for example, a target data transmission request generated by the transmission request generating unit 52 and to which a capsule header is added by the terminal encapsulating unit 54 to the relay device.
  • 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.
  • 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.
  • the communication route management data shown in FIGS. 6 and 7 corresponds to an example of the correspondence data.
  • 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.
  • 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.
  • 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.
  • the relay decapsulation unit 76 removes the capsule header from the transmission request to which the capsule header is attached, for example.
  • 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.
  • the determining unit 78 determines, for example, the type of target data that the data providing device is requested to transmit. As described above, the determination unit 78 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 78 may determine whether the target data is the advertising content 46.
  • the determining unit 78 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 78 may determine the type of target data based on the reference data.
  • the target data relay unit 80 receives, for example, target data transmitted from a data providing device that has received a transmission request.
  • 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.
  • the target data relay unit 80 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 determination result.
  • the relay encapsulation unit 82 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 determination result of the type of target data is set as the destination address. do.
  • the target data relay unit 80 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.
  • the relay encapsulation unit 82 may specify a plurality of communication route management data including the virtual IP address set as the destination address of the target data. Then, the relay encapsulation unit 82 may specify communication path management data including a value of type data corresponding to the determination result of the type of target data from among the plurality of communication path management data specified.
  • the relay encapsulation unit 82 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.
  • the communication path management data shown in FIG. 6 is stored in the correspondence data storage unit 70.
  • a capsule header with "b1.b1.b1.b1" set as the destination address may be added.
  • a capsule header with "c1.c1.c1.c1" set as the destination address may be added.
  • the target data relay unit 80 receives the target data transmitted from the data providing device, and the relay encapsulation unit 82 adds the above-mentioned capsule header to the target data, and the target data relay unit 80 may transmit the target data to which the capsule header is attached.
  • the target data receiving unit 58 receives, for example, target data.
  • the display control unit 60 causes the touch panel 36d to display the target data received by the target data receiving unit 58, for example.
  • the display control unit 60 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 62 and the relay monitoring agent unit 84 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.
  • the terminal monitoring agent section 62 and the relay monitoring agent section 84 communicate with each other to determine the communication quality (for example, jitter value, error rate, latency, etc.).
  • the communication quality of the communication path 40a and the communication path 40b is measured.
  • the terminal monitoring agent section 62 and the relay monitoring agent section 84 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.
  • the UE 36 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.
  • the transmission request generation unit 52 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 56 may transmit the transmission request associated with the identification information of the communication path 40 to the relay device via the communication path 40.
  • the options set in the IP header shown in FIGS. 9 to 11 and FIGS. 15 to 17 correspond to an example of route information of a communication path associated with a transmission request. Further, in this case, the transmission request transmitter 56 corresponds to an example of the above-mentioned identification information transmitter.
  • the relay device may include an identification information receiving unit that receives communication path identification information transmitted from the UE 36.
  • the transmission request relay unit 74 may receive a transmission request for target data associated with communication path identification information.
  • the transmission request relay section 74 corresponds to an example of an identification information receiving section.
  • the correspondence data updating unit 86 updates the correspondence data in response to, for example, detecting that the global IP address assigned to the UE 36 has been changed.
  • the correspondence data update unit 86 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.
  • the corresponding data updating unit 86 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 86 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 86 may check, for example, whether the two confirmed global IP addresses match or differ.
  • the corresponding data update unit 86 updates the global IP address indicated by the real IP address data included in the communication route 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.
  • 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).
  • the terminal monitoring agent section 62 corresponds to an example of the above-mentioned identification information transmitting section
  • the relay monitoring agent section 84 corresponds to an example of the above-mentioned identification information receiving section.
  • the correspondence data updating unit 86 may update the correspondence data based on the results of monitoring the communication quality of the communication path set between the relay device and the UE 36.
  • 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.
  • the terminal monitoring agent unit 62 and the relay monitoring agent unit 84 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.
  • the correspondence data updating unit 86 may update the communication path management data shown in FIG. 6 to the communication path management data shown in FIG. 7.
  • the video content 44 is sent to the global IP address "c1.c1.c1.c1”
  • the advertising content 46 is sent to the global IP address "b1.b1.b1.b1”. That will happen.
  • the target data relay unit 80 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 , .
  • 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.
  • the virtual IP address issuing unit 72 may notify the UE 36 of the global IP address indicated in the correspondence data.
  • the virtual IP address dispensing unit 72 corresponds to an example of an address notification unit.
  • the relay monitoring agent unit 84 may notify the UE 36 of the global IP address indicated in the correspondence data.
  • the relay monitoring agent section 84 corresponds to an example of an address notification section.
  • the target data relay unit 80 may notify the UE 36 of the global IP address indicated in the corresponding data. In this case, the target data relay section 80 corresponds to an example of an address notification section.
  • 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 may include an address receiving unit that receives notification address data transmitted from the UE 36.
  • the transmission request transmitter 56 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.
  • the transmission request transmitting section 56 corresponds to an example of an address transmitting section
  • the transmission request relaying section 74 corresponds to an example of an address receiving section.
  • the transmission request corresponds to an example of notification address data.
  • the terminal monitoring agent unit 62 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 84 may receive the packet.
  • the terminal monitoring agent section 62 corresponds to an example of an address transmitting section
  • the relay monitoring agent section 84 corresponds to an example of an address receiving section.
  • a packet used to measure communication quality corresponds to an example of notification address data.
  • the corresponding data update unit 86 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.
  • 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.
  • the transmission request generation unit 52 of the UE 36 generates a transmission request for target data (S101).
  • the transmission request generated in the process shown in S101 is associated with the route ID of the communication route 40 through which the transmission request passes. Further, the virtual IP address of the UE 36 is set in the source address of the transmission request generated in the process shown in S101, and the IP address of the data providing device requesting transmission of target data is set in the destination address. .
  • the terminal encapsulation unit 54 of the UE 36 adds a capsule header to the transmission request generated in the process shown in S101 (S102).
  • the private IP address of the UE 36 is set to the source address of the capsule header added in the process shown in S102, and the IP address of the agent server 28 is set to the destination address.
  • the transmission request transmitting unit 56 of the UE 36 transmits the transmission request to which the capsule header is attached in the process shown in S102 to the agent server 28, and the transmission request relay unit 74 of the agent server 28 receives the transmission request. (S103).
  • 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.
  • 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 S103 from among the communication route management data stored in the corresponding data storage unit 70.
  • the communication route management data whose combination with the determined source address value matches the combination of the route ID value and the virtual IP address data value is identified (S104).
  • the corresponding data updating unit 86 updates the value of the real IP address data included in the communication route management data specified in the process shown in S104 and the value of the source address in the capsule header of the transmission request received in the process shown in S103. It is confirmed whether or not they are different (S105).
  • the corresponding data update unit 86 updates the value of the real IP address data included in the communication route management data specified in the process shown in S104 to the process shown in S103.
  • the value of the source address of the capsule header of the transmission request received is updated (S106).
  • the relay decapsulation unit 76 of the agent server 28 performs the process shown in S103.
  • the capsule header is removed from the received transmission request (S107).
  • the determination unit 78 of the agent server 28 determines the type of target data (S108).
  • the determination unit 78 of the agent server 28 identifies the value of the real IP address data that is associated with the type of target data determined in the process shown in S108 (S109).
  • the determination unit 78 of the agent server 28 holds the value of the real IP address data specified in the process shown in S109 (S110).
  • 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 S107 to the data providing device associated with the destination address set in the IP header of the transmission request. Send (S111).
  • 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 80 of the agent server 28 receives the target data (S112).
  • 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.
  • the target data relay unit 80 of the agent server 28 identifies the IP address set as the destination address of the target data received in the process shown in S112 (S113).
  • the value of the real IP address data held in the determination unit 78 in the process shown in S110 is specified as the IP address to be set as the destination address of the target data.
  • the relay encapsulation unit 82 of the agent server 28 adds a capsule header to the target data received in the process shown in S112 (S114).
  • the IP address of the agent server 28 is set in the source address of the capsule header added in the process shown in S114, and the IP address specified in the process shown in S113 is set in the destination address.
  • the target data relay unit 80 of the agent server 28 transmits the target data to which the capsule header has been added in the process shown in S114 to the UE 36, and the target data reception unit 58 of the UE 36 receives the target data ( S115).
  • 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.
  • 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.
  • communication path 40a and communication path 40b may be included in the same autonomous system 10.
  • the UE 36 does not need to be able to use network services provided by multiple operators.
  • 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).
  • the communication path 40a may be a communication path of a mobile communication system
  • the communication path 40b may be a communication path of a wireless LAN.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un dispositif de commande de trajet de communication, un procédé de commande de trajet de communication et un programme qui peuvent commander correctement le trajet de communication de données cibles qui sont transmises d'un dispositif de fourniture de données à un terminal de communication en réponse à une demande de transmission provenant du terminal de communication. Une unité de délivrance d'adresse IP virtuelle (72) délivre une adresse IP virtuelle à un UE (36). Une unité de stockage de données de correspondance (70) stocke des données de correspondance indiquant la correspondance entre l'adresse IP virtuelle et chaque adresse IP globale d'une pluralité d'adresses IP globales attribuées à l'UE (36). Une unité de détermination (78) détermine le type des données cibles. Une unité de relais de données cibles (80) reçoit des données cibles dont l'adresse de destination est réglée sur l'adresse IP virtuelle, et transmet les données cibles à une adresse IP globale qui est déterminée parmi la pluralité d'adresses IP globales associées à l'adresse IP virtuelle dans les données de correspondance sur la base du résultat de détermination du type des données cibles.
PCT/JP2022/021126 2022-05-23 2022-05-23 Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme Ceased WO2023228252A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/021126 WO2023228252A1 (fr) 2022-05-23 2022-05-23 Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/021126 WO2023228252A1 (fr) 2022-05-23 2022-05-23 Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme

Publications (1)

Publication Number Publication Date
WO2023228252A1 true WO2023228252A1 (fr) 2023-11-30

Family

ID=88918676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/021126 Ceased WO2023228252A1 (fr) 2022-05-23 2022-05-23 Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme

Country Status (1)

Country Link
WO (1) WO2023228252A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005269500A (ja) * 2004-03-22 2005-09-29 Hitachi Communication Technologies Ltd パケット転送装置
JP2011024078A (ja) * 2009-07-17 2011-02-03 Nakayo Telecommun Inc アドレス変更対応機能を有するルータ装置及びｉｐ電話端末
JP2018201084A (ja) * 2017-05-26 2018-12-20 富士通株式会社 制御装置、通信システム、通信経路切替方法、及び通信経路切替プログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005269500A (ja) * 2004-03-22 2005-09-29 Hitachi Communication Technologies Ltd パケット転送装置
JP2011024078A (ja) * 2009-07-17 2011-02-03 Nakayo Telecommun Inc アドレス変更対応機能を有するルータ装置及びｉｐ電話端末
JP2018201084A (ja) * 2017-05-26 2018-12-20 富士通株式会社 制御装置、通信システム、通信経路切替方法、及び通信経路切替プログラム

Similar Documents

Publication Publication Date Title
US12278842B2 (en) Method and system for virtual machine aware policy management
US12120029B2 (en) Method for implementing service continuity and related device
US10187459B2 (en) Distributed load balancing system, health check method, and service node
EP3968610B1 (fr) Procédé, dispositif et système de sélection d'un noeud informatique en périphérie de réseau mobile
US8356346B2 (en) VPN secure sessions with dynamic IP addresses
US10389628B2 (en) Exposing a subset of hosts on an overlay network to components external to the overlay network without exposing another subset of hosts on the overlay network
US9094482B2 (en) Apparatus and method for controlling data transmission/reception path between server and mobile terminal in heterogeneous network environment
US20190037033A1 (en) Integrating service appliances without source network address translation in networks with logical overlays
WO2019183978A1 (fr) Technologies pour réseau de distribution de contenu avec informatique en périphérie à accès multiples
AU2022202022B2 (en) Device shaping in a communications network
CN112165725A (zh) 报文处理的方法及设备
CN109672698B (zh) 内容分发方法、设备及系统
US10397791B2 (en) Method for auto-discovery in networks implementing network slicing
EP3606005B1 (fr) Procédé de redirection, élément de réseau de plan de commande, élément de réseau de plan utilisateur d'agrégation, serveur de contenu et dispositif terminal
US20230164111A1 (en) Method and apparatus for sending domain name system request
CN112566164A (zh) 一种通信系统及服务质量控制方法
EP3629559B1 (fr) Procédé de configuration d'une table de transfert pour un équipement utilisateur et appareil
WO2023228252A1 (fr) Dispositif de commande de trajet de communication, procédé de commande de trajet de communication, et programme
WO2023228251A1 (fr) Système de commande de chemin de communication, dispositif relais, terminal de communication, procédé de commande de chemin de communication et programme
WO2023228250A1 (fr) Dispositif de commande d'itinéraire de communication, procédé de commande d'itinéraire de communication et programme
EP4161207A1 (fr) Dispositif de station de base et procédé d'exploitation du dispositif de station de base
WO2023228249A1 (fr) Système de commande de trajet de communication, terminal de communication, dispositif relais, procédé de commande de trajet de communication et programme
JP2020517171A (ja) Ｉｐアドレス設定方法および装置
JP2014138248A (ja) 通信システム及び端末の通信経路制御方法
JP2014239322A (ja) 代理配信装置、コンテンツ配信システム、コンテンツ配信方法及びコンテンツ配信プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22943658

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22943658

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP