Communication control system

Abstract

The present application relates to a communication control system. In the communication control system, an information processing terminal transmits link information about a communication link whose connection is newly made or whose state is changed to a gateway server in a case where the communication link for making encapsulation communication is newly connected or in a case where the state of the connected communication link is changed, encapsulates a data packet received from an application by giving connection destination information about a connection destination of the data packet, transmits the encapsulated data packet to the gateway server via the communication link, the gateway server determines a charging method of the communication link based on the link information received from the information processing terminal, determines the connection destination of the received data packet based on the connection destination information received from the information processing terminal, and aggregates the communication volume of the data packet received from the information processing terminal per connection destination and per charging method.

Description

Technical Field

[0001] This disclosure relates to communication control systems. Background Technology

[0002] Japanese Patent Application Publication No. 2020-099097 discloses a technology that can provide communication services corresponding to the network destination of the terminal.

[0003] To charge based on the node and service at the connection destination, it is necessary to determine the connection destination of each data packet. This can be achieved, for example, using DNS spoofing. However, this is sometimes not feasible in a WAN configuration with multiple internet connections.

[0004] For example, suppose a terminal connects to a wireless LAN and performs name resolution via a defined WAN. In this situation, the data center lacks the information to associate the packet header information with the connection destination. Furthermore, when the terminal switches its connection from the wireless LAN to a cellular line, the data center cannot determine the connection destination of the packets that become subject to billing. As a result, the data center cannot aggregate traffic for each connection destination and cannot charge accordingly. Summary of the Invention

[0005] This disclosure was made in view of the above circumstances, and its purpose is to provide a communication control system capable of accurately charging based on the destination of the connection.

[0006] The communication control system disclosed herein controls encapsulated communication between an information processing terminal and a gateway server, wherein the information processing terminal and the gateway server are configured to encapsulate data packets for communication.

[0007] The information processing terminal includes a first processor configured to: when a new communication link for the encapsulated communication is established, or when the state of the connected communication link is changed, send link information related to the communication link whose connection or state has changed to the gateway server; encapsulate the data packet by assigning connection destination information related to the connection destination of the data packet received from the application; and send the encapsulated data packet to the gateway server via the communication link.

[0008] The gateway server has a second processor configured to: determine the charging method of the communication link based on the link information received from the information processing terminal; determine the connection destination of the received data packet based on the connection destination information received from the information processing terminal; and sum the communication volume of the data packet received from the information processing terminal for each connection destination and each charging method.

[0009] In the communication control system disclosed herein, the second processor aggregates the communication volume of the data packets received from the information processing terminal according to each of the connection destinations or groups of the connection destinations and each of the billing methods.

[0010] In the communication control system disclosed herein, the first processor uses a Domain Name System (DNS) proxy to determine the connection destination of the data packet.

[0011] In the communication control system disclosed herein, if the first processor determines that the connection destination cannot be determined, it will discard the data packet received from the application or send it to the gateway server via the free communication link.

[0012] In the communication control system disclosed herein, when the first processor determines that the connection destination has been successfully determined, it encapsulates the data packet received from the application by assigning the connection destination information to the data packet.

[0013] According to this disclosure, a communication control system is available that can accurately charge based on the destination of the connection. Attached Figure Description

[0014] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, wherein the same symbols denote the same elements.

[0015] Figure 1 This is a simplified structural diagram of the communication control system involved in the implementation method.

[0016] Figure 2 This is a timing diagram illustrating a usage example of a communication link.

[0017] Figure 3 This is a flowchart representing the processing performed by DCM.

[0018] Figure 4 This is a flowchart representing the processes performed by the gateway server.

[0019] Figure 5This is a flowchart representing the processing performed by DCM.

[0020] Figure 6 It is a diagram showing the structure of the encapsulated data packet.

[0021] Figure 7 This is a flowchart representing the processes performed by the gateway server.

[0022] Figure 8 It is a diagram showing the structure of the encapsulated data packet. Detailed Implementation

[0023] The communication control system according to embodiments of this disclosure will be described with reference to the accompanying drawings. The constituent elements in the following embodiments include elements that can be easily substituted by those skilled in the art, or elements that are substantially the same.

[0024] Implementation

[0025] Communication system

[0026] Figure 1 This is a simplified structural diagram of the communication control system involved in the implementation method. Figure 1 The communication control system 100 shown includes a vehicle 1, a gateway server 2, and a server 3. The vehicle 1 includes an electronic control unit (ECU) 11 and a data communication module (on-board communicator, DCM) 12, which serves as an information processing terminal. The following description uses an example of a vehicle 1 equipped with both ECU 11 and DCM 12, but ECU 11 can also perform the functions of DCM 12.

[0027] The communication control system 100 controls encapsulated communication between the DCM 12 and the gateway server 2, which involves encapsulating data packets for communication. This description illustrates an example of the communication control system 100 controlling communication between the DCM 12 and the gateway server 2, but is not limited to this. The communication control system 100 can control communication between various terminals and the gateway server, such as personal computers and smartphones.

[0028] Both DCM12 and Gateway Server 2 have communication capabilities, enabling them to communicate with each other and exchange various information via a network. This network may consist of public line networks such as the Internet and mobile phone (cellular) networks, wireless communications such as WiFi (Wireless Fidelity) and BLE (Bluetooth Low Energy), and satellite communication links via satellite.

[0029] exist Figure 1The document describes examples of a 5G line N1, a wireless WiFi line N2, and a satellite communication (SatCom) line N3, which serve as the communication link between DCM12 and gateway server 2. The 5G line N1, for example, connects to the Internet via a RAN (Radio Access Network) standardized by 3GPP (3rd Generation Partnership Project). The WiFi line N2, for example, connects to the Internet via a wireless LAN (WLAN). The SatCom line N3, for example, connects to the Internet via a non-terrestrial network (NTN).

[0030] The ECU11 uses a microcomputer as its main component, including a processor such as a CPU (Central Processing Unit) and memory such as ROM (Read Only Memory) and RAM (Random Access Memory). Various application programs are installed on the ECU11. The ECU11 and DCM12 are connected via a wired Ethernet standard.

[0031] The DCM12 comprises a microcomputer as its main components, including a first processor such as a CPU and a memory such as ROM and RAM. The DCM12 sends data received from the application in the ECU11 to the gateway server 2 via a communication link selected through PBR (Policy-Based Routing).

[0032] Gateway server 2 is implemented, for example, by a general-purpose computer such as a workstation or personal computer, which includes a second processor such as a CPU and a memory such as ROM and RAM. Gateway server 2 distributes and transmits data received from DCM 12 to connection destinations via PBR and NAPT (Network Address Port Translation). The connection destination is a specified node or service designated by the application. Additionally, gateway server 2 monitors data traffic while snooping on the DNS of data received from DCM 12, and calculates the traffic volume of received data for each connection destination and each billing method. Gateway server 2 and server 3 are connected via a wired Ethernet standard.

[0033] Server 3 is implemented, for example, through a general-purpose computer such as a workstation or personal computer, which includes a processor such as a CPU and a memory such as ROM and RAM. Server 3 is the application's request server (Billing Server), which obtains the communication volume and charging method of the data sent from gateway server 2 to server 3, and charges based on the information obtained.

[0034] Processing of communication control systems

[0035] Figure 2 This is a timing diagram illustrating a usage example of a communication link. Figure 2 The horizontal axis represents time. DCM12 switches between the 5G line N1, WiFi line N2, and SatCom line N3, using communication links that change over time, while simultaneously encapsulating and sending data packets received from the application to gateway server 2. At times t1 and t2, the charging method for 5G line N1 is changed. Furthermore, at times t11, t12, t13, and t14, WiFi line N2 or SatCom line N3 is connected as a new communication link. Thus, when the charging method changes or a new line is connected, DCM12 is required to send the changed charging method or the charging method for the new communication link to server 3.

[0036] Notification of payment method processing

[0037] Next, the process of DCM12 notifying the gateway server 2 of the billing method will be explained. Since the billing method changes when a new communication link is established or when the state of the connected communication link changes, DCM12 needs to notify the gateway server 2 of the billing method.

[0038] Figure 3 This is a flowchart representing the processes performed by the DCM. For example... Figure 3 As shown, DCM12 detects a new connection to a communication link for encapsulated communication or a change in the state of the connected communication link (S1).

[0039] Next, when DCM12 detects a change in the connection or status of the communication link, it sends the link information related to the communication link with the changed connection or status to the gateway server 2 (S2).

[0040] Then, DCM12 determines whether a specified indication input indicating the end of communication exists (S3). If DCM12 determines that the specified indication input exists (S3: Yes), the series of processes ends.

[0041] On the other hand, if DCM12 determines that there is no specified instruction input (S3: No), it returns to S1 to continue processing.

[0042] By performing S1 to S3 processes at a predetermined cycle, DCM12 can send the latest communication link information to gateway server 2.

[0043] Figure 4 This is a flowchart illustrating the processes performed by the gateway server. For example... Figure 4 As shown, gateway server 2 receives link information from DCM12 (S11).

[0044] Next, gateway server 2 determines the charging method for the communication link based on the received link information (S12).

[0045] Next, gateway server 2 determines whether there is a specified instruction input indicating the end of communication (S13). If gateway server 2 determines that the specified instruction input exists (S13: Yes), the series of processes ends.

[0046] On the other hand, if the gateway server 2 determines that there is no specified instruction input (S13: No), it returns to S11 to continue processing.

[0047] If gateway server 2 receives link information, it executes processes S11 to S13. As a result, gateway server 2 is able to grasp the latest charging method for communication links.

[0048] Data packet sending processing

[0049] Next, the process of sending data packets sent by the application to server 3 via DCM12 and gateway server 2 will be explained. Figure 5 This is a flowchart representing the processes performed by the DCM. For example... Figure 5 As shown, DCM12 receives data packets from the application installed on ECU11 (S21).

[0050] Next, DCM12 uses a DNS (Domain Name System) proxy to determine the connection destination of the data packet (S22).

[0051] Furthermore, DCM12 determines whether the connection destination of the data packet has been successfully determined (S23). If DCM12 determines that the connection destination has been successfully determined (S23: Yes), DCM12 determines the communication link to be used (S24).

[0052] Then, DCM12 encapsulates the data packet with connection destination information related to the connection destination of the data packet received from the application (S25).

[0053] Figure 6 This is a diagram showing the structure of the encapsulated data packet. For example... Figure 6 As shown, DCM12 adds an encapsulation header to the outside of user data packets containing IP packets, TCP (Transmission Control Protocol) packets, and application data. The encapsulation header contains IP packets and UDP (User Datagram Protocol) packets, and DCM12 uses the source port corresponding to the UDP connection destination.

[0054] Then, DCM12 sends the encapsulated data packet to gateway server 2 via the determined communication link (S26).

[0055] Next, DCM12 determines whether there is a specified indication input indicating the end of communication (S27). If DCM12 determines that the specified indication input exists (S27: Yes), the series of processes ends.

[0056] On the other hand, if DCM12 determines that there is no specified instruction input (S27: No), it returns to S21 to continue processing.

[0057] In S23, if DCM12 determines that it cannot determine the connection destination (S23: No), DCM12 will discard the data packet received from the application or send it to the gateway server via a free communication link (S28).

[0058] If DCM12 receives a data packet from the application, it executes the processing steps S21 to S28. As a result, DCM12 is able to encapsulate the data packet received from the application with connection destination information and send it to gateway server 2.

[0059] Figure 7 This is a flowchart illustrating the processes performed by the gateway server. For example... Figure 7 As shown, gateway server 2 receives the encapsulated data packet from DCM12 (S31).

[0060] Next, the gateway server 2 determines the connection destination of the received data packet based on the connection destination information received from the DCM12 (S32).

[0061] Furthermore, the traffic volume of data packets received from DCM12 is totaled for each connection destination and each charging method (S33).

[0062] Then, gateway server 2 decapsulates the encapsulated data packets (S34).

[0063] Furthermore, gateway server 2 transmits the decapsulated data packet to the connection destination of the encapsulated header (S35).

[0064] Next, gateway server 2 determines whether there is a specified instruction input indicating the end of communication (S36). If gateway server 2 determines that the specified instruction input exists (S36: Yes), the series of processes ends.

[0065] On the other hand, if the gateway server 2 determines that there is no specified instruction input (S36: No), it returns to S31 to continue processing.

[0066] If gateway server 2 receives a data packet from DCM12, it executes processes S31 to S36. As a result, gateway server 2 can sum the traffic of data packets received from DCM12 for each connection destination and each charging method, and send it to server 3 at the connection destination.

[0067] According to the implementation described above, DCM12 encapsulates data packets received from the application with connection destination information, and gateway server 2 sums the communication volume of the data packets according to each connection destination and each charging method. As a result, communication control system 100 can accurately charge according to the connection destination.

[0068] Variations

[0069] Figure 8 This is a diagram showing the structure of the encapsulated data packet. For example... Figure 8 As shown, DCM12 adds an encapsulation header to the outside of user packets containing IP packets, TCP packets, and application data. The encapsulation header contains IP packets, UDP packets, and ext (extra) packets. DCM12 writes the connection destination ID corresponding to the connection destination to the ext packet. In this case, even connection destination IDs that are too long for the source code to handle can be written.

[0070] The implementation example illustrates how DCM12 uses a DNS proxy to determine the connection destination of data packets, but it is not limited to this. DCM12 can also capture DNS communication from the application client (AppClient) and determine the connection destination based on its content. Alternatively, DCM12 can use the DNS proxy on the gateway server 2 side to determine the connection destination. Furthermore, DCM12 can also encapsulate DNS communication from the application client, with gateway server 2 capturing the DNS communication and determining the connection destination based on its content.

[0071] Furthermore, the implementation describes an example of DCM12 utilizing the source port corresponding to the UDP connection destination in the encapsulated header, but it is not limited to this. DCM12 can be encapsulated via TCP / IP tunneling, defining the connection destination ID field as a TCP option field. Alternatively, DCM12 can also be encapsulated via tunneling protocols that include IP headers such as ipinip, UDP / IP, TCP / IP, and GRE, defining the connection destination ID field within the option field of the IP header.

[0072] Furthermore, the connection destination is not limited to a single node, but can also be a group of multiple nodes. In this case, the gateway server 2 aggregates the traffic of data packets received from DCM12 based on each connection destination or group of connection destinations and each billing method.

[0073] Those skilled in the art can readily derive further effects and variations. Therefore, the invention is not limited to the specific details and representative embodiments shown and described above. Thus, various modifications can be made without departing from the conceptual spirit or scope of the general invention as defined by the technical solution and its equivalents.

Claims

1. A communication control system that controls encapsulated communication between an information processing terminal and a gateway server, wherein... Equipped with the information processing terminal and the gateway server, The information processing terminal includes a first processor, which is configured as follows: When a new communication link for the encapsulated communication is established, or when the state of the connected communication link is changed, link information related to the communication link whose connection or state has changed is sent to the gateway server. The data packet is then encapsulated by assigning connection destination information related to the connection destination of the data packet received from the application. The encapsulated data packet is then sent to the gateway server via the communication link. The gateway server has a second processor configured as follows: The billing method for the communication link is determined based on the link information received from the information processing terminal, the connection destination of the received data packet is determined based on the connection destination information received from the information processing terminal, and the communication volume of the data packet received from the information processing terminal is totaled according to each connection destination and each billing method.

2. The communication control system according to claim 1, wherein, The second processor aggregates the communication volume of the data packets received from the information processing terminal according to each of the connection destinations or groups of the connection destinations and each of the billing methods.

3. The communication control system according to claim 1, wherein, The first processor uses a DNS proxy, also known as a Domain Name System proxy, to determine the connection destination of the data packet.

4. The communication control system according to claim 1, wherein, If the first processor determines that it cannot determine the destination of the connection, it will either discard the data packet received from the application or send it to the gateway server via the free communication link.

5. The communication control system according to claim 1, wherein, If the first processor determines that the connection destination has been successfully determined, it encapsulates the data packet received from the application with the connection destination information.

Images