Internet of vehicles multi-path APN flow management method and vehicle

Abstract

A multi-path APN traffic management method for the Internet of Vehicles comprises: a traffic service type division step (S100) of dividing traffic service types of the Internet of Vehicles of vehicles according to vehicle functions and actual service requirements of the vehicles; a step (S200) of determining the number of APN channels and the number of VLAN subnets, according to the divided traffic service types, determining the number of VLAN subnets required to be divided by the entire vehicle and the number of APN channels required to be opened by the SIM card, both the number of VLAN subnets and the number of APN channels being the same as the number of traffic service types; a whole vehicle network construction step (S300), wherein the whole vehicle network of the vehicle is constructed according to the number of the VLAN subnets and the number of the APN channels; and a real-time traffic management and control step (S400), setting a traffic threshold value of each APN channel according to the actual demand of the traffic service type, and performing real-time traffic management and control. Therefore, refined and flexible flow control and management of all flow services related to the vehicle are realized. The invention further provides a vehicle adopting the multi-path APN flow management method of the Internet of Vehicles.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and more specifically, to a method for managing multi-path APN (Access Point Name) traffic in a vehicle networking and a vehicle using the management method. Background Art

[0002] With the development of intelligent connected vehicles and the evolution of vehicle electronic and electrical architecture, automotive Ethernet has gradually become one of the primary networks for communication between various domain controllers within the vehicle. In particular, automotive Ethernet VLAN division technology ensures efficient and secure communication between different functional domains within the vehicle. However, with the increasing demand for IoV traffic data from intelligent connected vehicles and the complexity of the services involved, achieving effective management and control of multi-channel APN traffic has become a pressing issue. Summary of the Invention

[0003] The purpose of the present invention is to provide a multi-APN traffic management method for the Internet of Vehicles, a multi-APN traffic control solution for the Internet of Vehicles based on the division of vehicle Ethernet VLAN (Virtual Local Area Network), which uniformly classifies all traffic-requiring services in the vehicle, and then uses VLAN division to achieve data isolation with different traffic requirements in the vehicle. At the same time, the services corresponding to each VLAN subnet and the multi-APN channels are uniformly mapped accordingly, and then the corresponding traffic threshold is set for each APN, thereby achieving refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0004] Another object of the present invention is to provide a vehicle that adopts the above-mentioned vehicle network multi-APN traffic management method to achieve refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0005] The present invention provides a method for managing multi-channel APN traffic in an Internet of Vehicles (IoV), which is used to manage the APN traffic of a vehicle through an IoV platform, an operator platform, and a user APP. The method includes a traffic service type division step, a step for determining the number of APN channels and the number of VLAN subnets, a step for building a whole vehicle network, and a step for real-time traffic control. In the traffic service type division step, the traffic service type of the IoV of the vehicle is divided according to the whole vehicle function and actual business needs of the vehicle. In the step for determining the number of APN channels and the number of VLAN subnets, the number of VLAN subnets that need to be divided for the whole vehicle and the number of APN channels that need to be opened for the SIM card are determined according to the divided traffic service types, wherein the number of VLAN subnets and the number of APN channels are the same as the number of traffic service types. In the step for building a whole vehicle network, the whole vehicle network of the vehicle is built according to the number of VLAN subnets and the number of APN channels. In the step for real-time traffic control, the traffic threshold of each APN channel is set according to the actual needs of the traffic service type, and real-time traffic control is performed.

[0006] The multi-APN traffic management method for the Internet of Vehicles provided by the present invention uniformly classifies all traffic-requiring services of the vehicle and constructs a multi-APN traffic management solution for the vehicle's traffic services based on the on-board Ethernet VLAN division, thereby realizing refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0007] In an exemplary embodiment of the multi-APN traffic management method for the Internet of Vehicles (IoV), the traffic service classification step includes: constructing a classification table for vehicle traffic services based on the vehicle's overall functions and actual service requirements. The classification table includes fields such as traffic service type, traffic service description, and traffic payer. This uniformly categorizes all traffic-requiring services for the vehicle.

[0008] In another exemplary embodiment of the multi-channel APN traffic management method for the Internet of Vehicles, the step of establishing a vehicle network includes: a VLAN subnet division step, a step of establishing a relationship between traffic service types, VLAN subnets, and APN channels, a step of configuring the vehicle IP network, and a step of configuring APN channels and VLAN subnets. In the VLAN subnet division step, the vehicle Ethernet VLAN subnet division scheme is determined based on the determined number of VLAN subnets, and a naming table for the vehicle Ethernet VLAN subnets is constructed. The naming table includes the following fields: VLAN name and VLAN ID. In the step of establishing a relationship between traffic service types, VLAN subnets, and APN channels, a traffic service type is assigned to each VLAN subnet, and a correspondence is established between the traffic service type, VLAN subnet, and APN channel. A table of correspondences between traffic service types, VLAN subnets, and APN channels is constructed, including the following fields: traffic service type, VLAN ID, and APN channel name. During the vehicle IP network configuration step, the mapping between traffic service types and VLAN subnet IP addresses is determined, and a mapping table is constructed to form the vehicle's Ethernet VLAN network topology. Based on this network topology, the vehicle's network physical connections are established, ensuring that network traffic within each VLAN subnet is routed through the vehicle's Ethernet switch to the vehicle's telematics module (T-BOX). The mapping table includes fields for traffic service type and the IP address corresponding to the VLAN ID. During the APN channel and VLAN subnet configuration step, an APN channel is enabled for the vehicle's SIM card on the operator platform, and a corresponding VLAN subnet is configured for each APN channel. This establishes the mapping between each traffic service, VLAN subnet, and APN channel, and constructs the vehicle network.

[0009] In another exemplary embodiment of a multi-APN traffic management method for the Internet of Vehicles (IoV), traffic service types include the telecommunications module, central gateway domain, smart cockpit domain - non-entertainment services, smart cockpit domain - entertainment services, smart cockpit domain - other screens, smart driving domain, body control domain, and powertrain domain. Traffic payers include vehicle owners and automakers. This enables refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0010] In another exemplary implementation of the multi-APN traffic management method for the Internet of Vehicles, the real-time traffic control step includes: a setting step of the default initial traffic threshold of the APN, setting the default initial traffic threshold of each APN channel on the Internet of Vehicles platform and synchronizing it to the operator platform; an APN traffic usage monitoring step, the operator platform continuously monitors the traffic usage of each APN channel and regularly feeds back the traffic usage to the Internet of Vehicles platform; an APN traffic usage judgment step, the operator platform judges whether the traffic usage of each APN channel reaches the traffic threshold, and if the traffic threshold is reached, for the traffic service paid by the car owner customer, executes: a feedback alarm information step, the operator platform feeds back to the Internet of Vehicles platform The system then proceeds with the following steps: a feedback alarm indicating that the APN channel's service has been suspended due to excessive traffic; a forwarding alarm message step, where the IoV platform pushes the alarm message to the car owner's user app; a traffic purchase step, where the vehicle user, after receiving the pushed alarm message, operates the user app to purchase traffic; and a traffic threshold update step, where the operator platform updates the traffic threshold and restores the APN channel's service. For traffic services paid for by car manufacturers, the system also executes the following steps: a feedback reminder message step, where the operator platform sends a reminder message to the IoV platform indicating that the APN service's traffic has exceeded its limit; and a traffic threshold modification step, where the IoV platform modifies the traffic threshold for the APN channel and synchronizes it with the operator platform. This allows for differentiated management of traffic services paid for by car owners and those paid for by car manufacturers.

[0011] In another exemplary embodiment of the multi-APN traffic management method for the Internet of Vehicles, each traffic service type corresponds to a separate VLAN subnet and a separate APN channel, thereby achieving data isolation and refined management of different traffic services.

[0012] The present invention also provides a vehicle that adopts the above-mentioned vehicle network multi-APN traffic management method to achieve refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0013] The vehicle network multi-channel APN traffic management method provided by the present invention is a vehicle network multi-channel APN traffic control solution based on the vehicle Ethernet VLAN division, which uniformly classifies all the services that require traffic in the vehicle, isolates different traffic services through different VLAN subnets, and realizes refined management of the traffic services of the entire vehicle. Then, data isolation with different traffic requirements in the vehicle is achieved through VLAN division, and at the same time, the services corresponding to each VLAN subnet and the multi-channel APN channels are uniformly mapped accordingly. An independent APN channel is configured for each VLAN subnet, and a corresponding traffic threshold is set for each APN to realize independent control and management of traffic in different VLAN subnets, meet traffic requirements in different scenarios, and realize refined and flexible traffic control and management of all traffic services involved in the vehicle. In addition, the method of the present invention distinguishes the definitions of different VLAN subnet divisions and APN channels, distinguishes the traffic services paid for by users, realizes a solution for users to flexibly purchase traffic, and improves user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The following drawings are only used to schematically illustrate and explain the present invention and are not intended to limit the scope of the present invention.

[0015] Figure 1 A flow chart of a method for managing multi-APN traffic in an Internet of Vehicles according to an exemplary embodiment of the present invention is shown.

[0016] Figure 2 A schematic diagram of a process for constructing a vehicle network according to an exemplary embodiment of the present invention is shown.

[0017] Figure 3 A schematic diagram of a vehicle Ethernet VLAN network topology constructed according to an exemplary embodiment of the present invention is shown.

[0018] Figure 4 A schematic diagram showing a corresponding matching relationship between VLAN subnets and APN channels according to an exemplary embodiment of the present invention is shown.

[0019] Figure 5 A schematic diagram illustrating a traffic control architecture according to an exemplary embodiment of the present invention is shown.

[0020] Figure 6 A schematic diagram of a process of real-time traffic control according to an exemplary embodiment of the present invention is shown.

[0021] Description of labels 10 Central Gateway 11 Ethernet switches 20 Remote Communication Module 30 Intelligent Cockpit Domain Controller 40 Intelligent Driving Domain Controller 50 Body Control Domain Controller 60 Powertrain Domain Controller S100 Traffic Service Type Classification Steps S200 APN channel number and VLAN subnet number determination steps S300 steps to build a vehicle network S310 VLAN subnet division steps S320 Traffic Service Type, VLAN Subnet, and APN Channel Relationship Establishment Steps S330 Vehicle IP Network Configuration Steps S340 APN channel and VLAN subnet configuration steps S400 real-time traffic control steps Steps to set the default initial traffic threshold for S410 APN S420 APN traffic usage monitoring steps S430 APN traffic usage determination steps S440 Feedback Alarm Information Steps S450 Forwarding Alarm Information Steps S460 Data Purchase Steps S470 Traffic Threshold Update Steps S480 Feedback Reminder Steps S490 flow threshold modification steps. DETAILED DESCRIPTION

[0022] In order to have a clearer understanding of the technical features, purposes and effects of the invention, the specific embodiments of the present invention are now described with reference to the accompanying drawings. The same reference numerals in the drawings represent components with the same structure or similar structures but the same functions.

[0023] In this document, “illustrative” means “serving as an example, instance or illustration”, and any diagram or implementation described in this document as “illustrative” should not be interpreted as a more preferred or more advantageous technical solution.

[0024] To simplify the drawings, each figure schematically shows only the parts related to the present invention, which do not represent the actual structure of the product.

[0025] Figure 1 FIG. 1 shows a flow chart of a method for managing multi-APN traffic in a vehicle network according to an exemplary embodiment of the present invention. Figure 1As shown, the vehicle network multi-channel APN traffic management method of the present invention is used to manage the APN traffic of the vehicle through the vehicle network platform, the operator platform and the user APP, and includes: a traffic service type classification step S100, a step S200 of determining the number of APN channels and the number of VLAN subnets, a step S300 of building a whole vehicle network and a step S400 of real-time traffic control.

[0026] In the traffic service classification step S100, the vehicle's IoV traffic service types are classified based on the vehicle's overall functions and actual service needs. For example, based on the vehicle's overall functions and actual service needs, such as traffic-related functions that the vehicle needs to handle, including remote control, vehicle condition data reporting, OTA upgrade package downloads, remote diagnostics, online weather, online navigation and logging, body control-related big data and log uploads, battery-related big data and log uploads, and other services that require network traffic support, such as online music, online video, large-screen sharing hotspots, and Internet access for the passenger and rear screens, the vehicle's IoV traffic services are classified into the following eight traffic service types: remote communication module, central gateway domain, smart cockpit domain - non-entertainment services, smart cockpit domain - entertainment services, smart cockpit domain - other screens, smart driving domain, body control domain, and powertrain domain, and designated payers for each type of traffic service. This uniformly categorizes all vehicle services requiring traffic.

[0027] The classification table of vehicle traffic services for a specific vehicle is shown in Table 1. Table 1 includes fields such as traffic service type, traffic service description, and traffic payer. The traffic service type field includes the eight traffic service types divided above; the traffic service description field is used to explain what traffic data each traffic service includes; the traffic payer field is used to identify the payer of each traffic service type. Traffic payers include two payers, namely, car owners and car manufacturers. The traffic services paid by car owners include smart cockpit domain-entertainment services and smart cockpit domain-other screens. Other traffic services are paid for by car manufacturers. Table 1 is stored in the vehicle's memory.

[0028] Table 1: Classification of vehicle traffic business Traffic service type Traffic service description Traffic payer Remote communication module Remote control + vehicle condition data reporting car manufacturers Central Gateway Domain OTA upgrade package download + remote diagnosis car manufacturers Smart cockpit domain - non-entertainment services Online weather, online navigation, log and other data uploads, etc. car manufacturers Smart Cockpit Domain - Entertainment Services Online music, online video, large-screen sharing hotspots, etc. Car owner customers Smart Cockpit Domain-Other Screens Internet access services for the co-pilot screen + rear screen, etc. Car owner customers Intelligent driving domain Video streaming data and other intelligent driving-related big data upload, log upload, etc. car manufacturers Body control domain Uploading big data related to body control, uploading logs, etc. car manufacturers Powertrain domain Upload big data related to batteries, logs, etc. car manufacturers

[0029] By distinguishing business traffic according to the above rules, for traffic services paid by car owners, targeted traffic purchase can be achieved; for traffic services paid by automobile manufacturers, traffic consumption in different functional domains can be distinguished, thereby achieving refined and flexible traffic control and management of each functional domain.

[0030] In step S200 of determining the number of APN channels and VLAN subnets, the number of VLAN subnets required for the vehicle and the number of APN channels required for the SIM card are determined based on the traffic service types. The number of VLAN subnets and APN channels is the same as the number of traffic service types. For example, to correspond to the eight traffic service types, the vehicle's Ethernet network is divided into eight VLAN subnets, and eight APN channels are enabled on the vehicle's SIM card.

[0031] In the step S300 of constructing the entire vehicle network, the entire vehicle network of the vehicle is constructed according to the number of VLAN subnets and the number of APN channels. Figure 2 FIG. 1 shows a flow chart of building a vehicle network according to an exemplary embodiment of the present invention. Figure 2 As shown, the vehicle network construction step S300 includes a VLAN subnet division step S310, a traffic service type and VLAN subnet and APN channel relationship construction step S320, a vehicle IP network configuration step S330 and an APN channel and VLAN subnet configuration step S340.

[0032] In the VLAN subnet division step S310, a vehicle Ethernet VLAN subnet division scheme is determined based on the determined number of VLAN subnets. For example, the eight divided VLAN subnets are named, such as VLAN_100, VLAN_101, ..., VLAN_107, and each VLAN subnet is assigned an ID. VLAN subnet VLAN_100 corresponds to VLAN ID 100, VLAN subnet VLAN_101 corresponds to VLAN ID 101, ..., and VLAN subnet VLAN_107 corresponds to VLAN ID 107. A vehicle Ethernet VLAN subnet naming table is shown in Table 2. Table 2 includes fields such as VLAN name and VLAN ID. Table 2 is stored in the vehicle's memory.

[0033] Table 2: Vehicle Ethernet VLAN subnet naming table VLAN name VLAN ID VLAN_100 100 VLAN_101 101 VLAN_102 102 VLAN_103 103 VLAN_104 104 VLAN_105 105 VLAN_106 106 VLAN_107 107

[0034] In the step S320 of establishing the relationship between traffic service type, VLAN subnet and APN channel, a traffic service type is assigned to each VLAN subnet, and a corresponding relationship between the traffic service type and the VLAN subnet and APN channel is established. For example, VLAN subnet VLAN_100, that is, the VLAN subnet with VLAN ID 100, is responsible for data transmission of the remote communication module, and the corresponding APN channel is APN0; VLAN subnet VLAN_101, that is, the VLAN subnet with VLAN ID 101, is responsible for data transmission of the central gateway domain, and the corresponding APN channel is APN1. The configuration of the remaining seven VLAN subnets is similar. In this way, the correspondence between each traffic service and the VLAN subnet and APN channel is established, and the entire vehicle network is constructed. Each traffic service type is responsible for quantity transmission by a separate VLAN subnet and a separate APN channel. Thus, data isolation and refined management of different traffic services are achieved. The correspondence table between traffic service type, VLAN subnet and APN channel is shown in Table 3. The table includes fields: the traffic service type, the VLAN ID and the APN channel name. Table 3 is stored in the vehicle's memory.

[0035] Table 3: Correspondence between traffic service types, VLAN subnets, and APN channels Traffic service type VLAN ID APN channel name Remote communication module 100 APN0 Central Gateway Domain 101 APN1 Smart cockpit domain - non-entertainment services 102 APN2 Smart Cockpit Domain - Entertainment Services 103 APN3 Smart Cockpit Domain-Other Screens 104 APN4 Intelligent driving domain 105 APN5 Body control domain 106 APN6 Powertrain domain 107 APN7

[0036] In the vehicle IP network configuration step S330, the correspondence between the traffic service type and the VLAN subnet IP address is determined. For example, the VLAN ID of the VLAN subnet corresponding to the remote communication module is 100, and the IP addresses are: 192.168.00.1, 192.168.01.1, 192.168.02.1, 192.168.03.1, 192.168.04.1, 192.168.05.1, 192.168.06.1 and 192.168.07.1; the VLAN subnet corresponding to the central gateway domain is VLAN 101, and the IP address is 192.168.01.2, which corresponds to the IP address 192.168.01.1 in the remote communication module; the VLAN subnet corresponding to the smart cockpit domain - non-entertainment services is VLAN The ID is 102, the IP address is 192.168.02.3, and the corresponding IP address in the remote communication module is 192.168.02.1; the VLAN ID of the VLAN subnet corresponding to the smart cockpit domain-entertainment business is 103, the IP address is 192.168.03.4, and the corresponding IP address in the remote communication module is 192.168.03.1; the VLAN ID of the VLAN subnet corresponding to the smart cockpit domain-other screens is 104, the IP address is 192.168.04.5, and the corresponding IP address in the remote communication module is 192.168.04.1; the VLAN subnet corresponding to the smart driving domain is 105, the IP address is 192.168.05.6, and the corresponding IP address in the remote communication module is 192.168.05.1; the VLAN subnet corresponding to the body control domain is The ID is 106, the IP address is 192.168.06.7, and the corresponding IP address in the remote communication module is 192.168.06.1. The VLAN subnet corresponding to the powertrain domain has a VLAN ID of 107 and an IP address of 192.168.07.8, which corresponds to the IP address 192.168.07.1 in the remote communication module. Table 4 shows the specific correspondence between traffic service types and VLAN subnet IP addresses. Table 4 includes fields such as traffic service type and the IP address corresponding to the VLAN ID.

[0037] Table 4: Correspondence between service types and VLAN subnet IP addresses .

[0038] The vehicle Ethernet VLAN network topology of the vehicle is formed according to the correspondence between the service type and the VLAN subnet IP address in Table 4. Figure 3 The schematic diagram of the vehicle Ethernet VLAN network topology constructed according to the exemplary embodiment of the present invention is shown. Figure 3The vehicle Ethernet VLAN network topology shown in the figure configures the corresponding VLAN ID for each device to ensure that each device can correctly join the corresponding VLAN subnet. Figure 3 As shown, the vehicle includes a central gateway 10, a remote communication module 20, an intelligent cockpit domain controller 30, an intelligent driving domain controller 40, a body control domain controller 50, and a powertrain domain controller 60. The VLAN subnet configured for the central gateway 10 has a VLAN ID of 101; the VLAN subnet configured for the remote communication module 20 has a VLAN ID of 100; the VLAN subnet configured for the intelligent cockpit domain controller 30 has VLAN IDs of 102, 103, and 104; the VLAN subnet configured for the intelligent driving domain controller 40 has a VLAN ID of 105; the VLAN subnet configured for the body control domain controller 50 has a VLAN ID of 106; and the VLAN subnet configured for the powertrain domain controller 60 has a VLAN ID of 107.

[0039] The central gateway 10 includes an Ethernet switch 11. For example, in the Ethernet switch 11, corresponding VLAN IDs and port ownership relationships are configured; multiple VLAN subnets are enabled, and MAC addresses and IP networks of multiple VLAN subnets are configured. Figure 3 The network topology shown completes the physical connection of the vehicle's entire vehicle network, so that the network traffic within each VLAN subnet is routed to the vehicle's remote communication module through the vehicle's Ethernet switch.

[0040] In the APN channel and VLAN subnet configuration step S340, APN channels are enabled for the vehicle's SIM card on the carrier platform, and a corresponding VLAN subnet is configured for each APN channel. For example, a certain number of APN channels, such as eight, are configured for the vehicle's telematics module SIM card on the carrier platform (e.g., China Mobile), and a corresponding VLAN network is assigned to each APN channel, i.e., the IP address of the corresponding VLAN subnet is set. Figure 4 FIG. 1 is a schematic diagram showing a corresponding matching relationship between a VLAN subnet and an APN channel according to an exemplary embodiment of the present invention. Figure 4 As shown, APN channel APN0 corresponds to the services of the remote communication module itself, APN channel APN1 corresponds to the IP address 192.168.01.1, and so on, and finally APN channel APN7 corresponds to the IP address 192.168.07.1. Therefore, within the remote communication module, Internet access requests are routed to the corresponding APN channel based on each virtual network card, thereby meeting the service Internet access needs of each VLAN subnet and isolating the service traffic of each VLAN subnet.

[0041] In the real-time traffic control step S400, the traffic threshold of each APN channel is set according to the actual demand of the traffic service type, and real-time traffic control is performed. Figure 5 FIG. 1 shows a schematic diagram of the architecture of traffic control according to an exemplary embodiment of the present invention. Figure 5 As shown in the figure, in order to accurately control the traffic of each APN, the upper threshold limit of each APN is set on the Internet of Vehicles platform, and then the setting information is synchronized to the operator platform. The operator platform monitors the traffic of each APN and feedbacks reminder information / alarm information when the traffic threshold is reached to avoid traffic exceeding the limit.

[0042] Figure 6 FIG. 1 shows a flow chart of real-time traffic control according to an exemplary embodiment of the present invention. Figure 6 As shown, the real-time traffic control step S400 includes: a step S410 of setting the default initial traffic threshold for the APN, in which the default initial traffic threshold for each APN channel is set on the IoV platform and synchronized with the operator platform. For example, for traffic paid for by the car owner, the company provides 10GB of traffic per month. This 10GB of traffic is the default initial traffic threshold, which is set by the car manufacturer on the IoV platform when the car leaves the factory. For traffic services paid for by the car manufacturer, the car manufacturer sets the default initial traffic threshold on the IoV platform when the car leaves the factory based on the actual needs of the traffic service type. For example, travel navigation is a frequently used function with high traffic usage. The data transmission of this function is carried out by the APN2 channel. In this case, the default initial traffic threshold of the APN2 channel is set to 10GB.

[0043] In the APN traffic usage monitoring step S420, the operator platform continuously monitors the traffic usage of each APN channel and regularly feeds back the traffic usage to the Internet of Vehicles platform, for example, monthly or quarterly.

[0044] In the APN traffic usage judgment step S430, the operator platform determines whether the traffic usage of each APN channel reaches the traffic threshold. If it reaches the traffic threshold, it determines whether it is a traffic service paid by the car owner customer. If it is a traffic service paid by the car owner customer, the traffic management process of the car owner customer paid service is executed. If it is not a traffic service paid by the car owner customer, that is, it is a traffic service paid by the automobile manufacturer, the traffic management process of the automobile manufacturer paid service is executed.

[0045] The traffic management process for the traffic service paid by the car owner customer includes a step of feeding back an alarm message S440, a step of forwarding the alarm message S450, a step of purchasing traffic S460 and a step of updating the traffic threshold S470.

[0046] In the step S440 of feeding back the alarm information, the operator platform feeds back the alarm information that the service of the APN channel is suspended due to excessive traffic to the Internet of Vehicles platform. For example, the operator platform feeds back the alarm information that "APN3 traffic usage has been used up" to the Internet of Vehicles platform.

[0047] In the step S450 of forwarding the alarm information, the Internet of Vehicles platform pushes the alarm information to the user APP of the car owner. For example, the Internet of Vehicles platform pushes the alarm information of "APN3 traffic usage has been used up" as the alarm information of "free traffic for entertainment services has been used up" to the user APP of the car owner.

[0048] In the traffic purchase step S460, the vehicle user operates the user APP to purchase traffic after receiving the pushed alarm information. For example, after the vehicle user receives the alarm information that "the free traffic for entertainment services has been used up", he purchases traffic on the operator platform.

[0049] In the traffic threshold update step S470, the operator platform updates the traffic threshold and restores the service of the APN channel. For example, after the vehicle user successfully purchases traffic through the user APP, the operator platform updates the traffic threshold and restores the service of the APN channel, and continues the service of the APN channel.

[0050] The traffic management process for the traffic service paid by the automobile manufacturer includes a step of feeding back reminder information S480 and a step of modifying the traffic threshold S490.

[0051] In the step S480 of feeding back reminder information, the operator platform feeds back to the Internet of Vehicles platform a reminder message that the traffic usage of the APN service has exceeded the standard. For example, the operator platform feeds back to the Internet of Vehicles platform a reminder message that "APN5 traffic usage has exceeded 500M".

[0052] In the traffic threshold modification step S490, the traffic threshold of the APN channel is modified on the Internet of Vehicles platform and synchronized to the operator platform. The automobile manufacturer regularly settles traffic fees with the operator. For example, the automobile manufacturer modifies the traffic threshold based on the traffic settlement between the automobile manufacturer and the operator.

[0053] For traffic paid for by car owners, in addition to the initial monthly data provided by the company, users can purchase additional data when the data usage exceeds the limit. For traffic services paid for by automakers, thresholds can be modified directly on the IoV platform, enabling flexible management of traffic for different services. This enables differentiated management of user-paid and automaker-paid traffic services.

[0054] Through the multi-APN traffic management method for the Internet of Vehicles provided by the present invention, the multi-APN traffic control solution for the Internet of Vehicles based on the vehicle Ethernet VLAN division is unified to classify all the services that require traffic in the vehicle, and then realize data isolation with different traffic requirements in the vehicle by performing VLAN division on the entire vehicle. At the same time, the services corresponding to each VLAN subnet and the multi-APN channels are uniformly mapped accordingly, and then the corresponding traffic threshold is set for each APN, so as to realize refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0055] The present invention also provides a vehicle that adopts the above-mentioned vehicle network multi-APN traffic management method, thereby achieving refined and flexible traffic control and management of all traffic services involved in the vehicle.

[0056] The series of detailed descriptions listed above are only specific descriptions of feasible embodiments of the present invention. They are not intended to limit the scope of protection of the present invention. Any equivalent implementation scheme or changes that do not deviate from the technical spirit of the present invention, such as the combination, division or repetition of features, should be included in the scope of protection of the present invention.

Claims

1. A multi-channel APN traffic management method for an Internet of Vehicles, which is used to manage the APN traffic of a vehicle through an Internet of Vehicles platform, an operator platform, and a user APP, characterized in that: The method comprises: A traffic service type classification step (S100) is to classify the traffic service type of the vehicle's Internet of Vehicles according to the vehicle's overall functions and actual service requirements; APN channel number and VLAN subnet number determination step (S200), determining the number of VLAN subnets that need to be divided for the vehicle and the number of APN channels that need to be opened for the SIM card according to the divided traffic service type, wherein the number of VLAN subnets and the number of APN channels are the same as the number of traffic service types; A vehicle network construction step (S300) is to construct the vehicle network according to the number of VLAN subnets and the number of APN channels; In the real-time traffic control step (S400), a traffic threshold for each APN channel is set according to the actual demand of the traffic service type, and real-time traffic control is performed.

2. The method for managing multi-APN traffic in an Internet of Vehicles according to claim 1, wherein: The traffic service type classification step (S100) includes: constructing a classification table of the vehicle's entire traffic service according to the vehicle's entire function and actual service requirements, the classification table including fields: traffic service type, traffic service description and traffic payer.

3. The method for managing multi-APN traffic in an Internet of Vehicles according to claim 1 or 2, wherein: The step of building a vehicle network (S300) includes: VLAN subnet division step (S310), determining a vehicle Ethernet VLAN subnet division scheme for the vehicle according to the determined number of VLAN subnets, and constructing a naming table for the vehicle Ethernet VLAN subnets, the naming table including the fields: VLAN name and VLAN ID; A step (S320) of establishing a relationship between traffic service types, VLAN subnets, and APN channels, allocating a traffic service type to each VLAN subnet, and establishing a correspondence between the traffic service type, the VLAN subnet, and the APN channel, and constructing a correspondence table between the traffic service type, the VLAN subnet, and the APN channel, including fields: the traffic service type, the VLAN ID, and the APN channel name; The vehicle IP network configuration step (S330) determines the correspondence between the traffic service type and the VLAN subnet IP address, constructs a correspondence table between the traffic service type and the VLAN subnet IP address, forms the vehicle Ethernet VLAN network topology of the vehicle, and completes the physical link of the vehicle network according to the network topology, so that the network traffic service in each VLAN subnet is routed to the vehicle's remote communication module through the vehicle's Ethernet switch, wherein the traffic service type and VLAN subnet IP address correspondence table includes fields: the traffic service type and the IP address corresponding to the VLAN ID; and The APN channel and VLAN subnet configuration step (S340) is to open an APN channel for the vehicle's SIM card on the operator platform and configure a corresponding VLAN subnet for each APN channel.

4. The method for managing multi-APN traffic in an Internet of Vehicles according to claim 3, wherein: The traffic service types include: remote communication module, central gateway domain, smart cockpit domain-non-entertainment services, smart cockpit domain-entertainment services, smart cockpit domain-other screens, smart driving domain, body control domain and powertrain domain; the traffic payers include: car owners and car manufacturers.

5. The method for managing multi-APN traffic in an Internet of Vehicles according to claim 4, wherein: The real-time traffic control step (S400) includes: A step of setting a default initial traffic threshold of the APN (S410), setting a default initial traffic threshold of each APN channel on the Internet of Vehicles platform and synchronizing it to the operator platform; APN traffic usage monitoring step (S420), the operator platform continuously monitors the traffic usage of each APN channel and regularly feeds back the traffic usage to the Internet of Vehicles platform; APN traffic usage determination step (S430), the operator platform determines whether the traffic usage of each APN channel reaches the traffic threshold. If it reaches the traffic threshold, For traffic services paid by car owners, execute: In the step of feeding back an alarm message (S440), the operator platform feeds back an alarm message to the Internet of Vehicles platform indicating that the service of the APN channel is suspended due to excessive traffic. In the step of forwarding the alarm information (S450), the Internet of Vehicles platform pushes the alarm information to the user APP of the car owner. In the step of purchasing traffic (S460), the user of the vehicle receives the pushed alert information and operates the user APP to purchase traffic, and Traffic threshold updating step (S470), the operator platform updates the traffic threshold and restores the service of the APN channel; For traffic services paid by car manufacturers, execute: Feedback reminder information step (S480), the operator platform feeds back to the Internet of Vehicles platform the reminder information that the traffic of the APN service on this road exceeds the standard, and In a traffic threshold modification step ( S490 ), after receiving the reminder information, the Internet of Vehicles platform modifies the traffic threshold of the APN channel on the Internet of Vehicles platform and synchronizes it to the operator platform.

6. The method for managing multi-APN traffic in an Internet of Vehicles according to claim 5, wherein: Each traffic service type corresponds to a separate VLAN subnet and a separate APN channel.

7. A vehicle, characterized in that: The vehicle adopts the vehicle network multi-path APN traffic management method as described in any one of claims 1 to 6.

Images