Flow control method, cabin control device, vehicle and storage medium

Abstract

The embodiment of the invention discloses a flow control method, a cabin control device, a vehicle and a storage medium, the method is applied to a cabin system of the vehicle, the cabin system comprises at least one application program, and the method comprises the following steps: determining a current service type of a service currently executed by a target application program, the current service type comprises a system service or a non-system service, and the at least one application program comprises a target application program; and when the current service type is a non-system service and the non-system flow accumulated and consumed by the non-system service of the cockpit system in the preset period reaches a flow threshold value, blocking the consumption of the non-system flow by the service currently executed by the target application program. According to the embodiment of the invention, the network traffic of the application program of the cockpit system can be finely managed, and the increase of the use cost of non-system traffic of a user can be avoided.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle technology, and are related to but not limited to a flow control method, a cabin control device, a vehicle, and a storage medium. Background Art

[0002] A vehicle's in-cabin system can provide internet access for deployed applications, generating traffic. Currently, in-cabin system internet traffic is generally categorized as non-system traffic (e.g., entertainment traffic) and system traffic. System traffic is paid for by the vehicle manufacturer, while non-system traffic is paid for by the user.

[0003] Currently, cockpit systems typically have a limited monthly non-system traffic allocation. Exceeding this limit can easily increase users' non-system traffic costs. Therefore, it's necessary to manage the Internet traffic of applications deployed on the cockpit system. Summary of the Invention

[0004] In view of this, an embodiment of the present application provides a traffic control method, a cabin control device, a vehicle and a storage medium. This embodiment can perform fine-grained management of the Internet traffic of the application program of the vehicle's cabin system, thereby avoiding an increase in the user's non-system traffic usage cost.

[0005] An embodiment of the present application provides a flow control method, which is applied to a vehicle cabin system, wherein the cabin system includes at least one application program. The method includes:

[0006] determining a current service type of a service currently executed by a target application, wherein the current service type includes a system service or a non-system service, and the at least one application includes the target application;

[0007] When the current service type is the non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold, the consumption of non-system traffic by the service currently executed by the target application is blocked.

[0008] In the above embodiment, the non-system traffic consumed by the non-system services of the vehicle cockpit system reaches the traffic threshold, indicating that the use of non-system traffic has reached the limit. Then, if the service currently executed by the target application is a non-system service, the service currently executed by the target application is blocked, that is, the application executing the non-system service (such as entertainment Internet service) is blocked. In other words, the embodiment of the present application combines the current service type of the service currently executed by the target application and the non-system traffic consumed by the non-system services of the cockpit system within a preset period, and realizes the refined management of the Internet traffic of the application of the cockpit system in multiple dimensions, which can avoid the increase of the use cost of the non-system traffic consumed by the user's non-system services.

[0009] In some embodiments, determining the current business type of the business currently executed by the target application includes:

[0010] Monitoring an access request initiated by the target application to an external network, the access request being used to indicate a destination IP address of the external network accessed by the target application;

[0011] The current service type is determined according to the destination IP address, and the service type of the network resource of the external network accessed based on the destination IP address is the current service type.

[0012] In the above embodiment, since the access request carries the destination IP address of the external network accessed by the target application, the current business type of the business currently executed by the target application can be quickly determined through the destination IP address. In other words, this method of controlling whether to block non-system business executed by the target application based on the IP address improves the efficiency of the refined management of the Internet traffic of the cockpit system application.

[0013] In some embodiments, determining the current service type according to the destination IP address includes:

[0014] When the destination IP address does not belong to the IP address whitelist, the current service type is determined to be the non-system service, the IP address whitelist includes at least one IP address, and the service type of the network resources of the external network accessed based on each IP address is the system service.

[0015] In the above embodiment, since the service type of accessing network resources of the external network based on the IP address in the IP address whitelist is a system service, by judging whether the destination IP address is in the IP address whitelist corresponding to the system service, it is possible to quickly and accurately determine whether the service currently executed by the target application is a non-system service.

[0016] In some embodiments, when the destination IP address does not belong to the IP address whitelist, determining that the current service type is the non-system service includes:

[0017] In a case where the destination IP address does not belong to the IP address whitelist, determining a type of the target application, the type of the target application being a non-system application or a system application;

[0018] In a case where the type of the target application is the non-system application, the current service type is determined to be the non-system service.

[0019] In the above embodiment, since the same destination IP address may be accessed by different types of applications at the same time (such as non-system applications and system applications), in order to avoid blocking the system application's access to the destination IP address when the service currently being executed by the application is blocked based on the destination IP address, thereby affecting the normal operation of the system application, it is also possible to determine whether the type of the target application is a non-system application when it is determined that the destination IP address does not belong to the IP address whitelist. In other words, only when the type of the target application is a non-system application is it determined that the service currently being executed by the target application is a non-system service. Therefore, under the premise that the non-system traffic consumed by the non-system service of the cockpit system reaches the traffic threshold, the service currently being executed is blocked only when the destination IP address is accessed by a non-system application, effectively avoiding the system application being blocked when accessing the destination IP address, and further improving the level of refined management of the Internet traffic of the cockpit system's applications.

[0020] In some embodiments, the access request includes a destination domain name, the destination IP address is obtained by resolving the destination domain name, and determining the type of the target application includes:

[0021] The type of the target application is determined according to the destination domain name.

[0022] In the above embodiment, since the destination IP address is obtained by resolving the destination domain name, and the destination domain name is easy for users to remember and has the advantages of flexible design, when designing the domain name of the cockpit system, each domain name can be flexibly customized according to the type of application being accessed. Therefore, the method of determining the type of target application based on the destination domain name effectively improves the efficiency of determining the type of target application.

[0023] In some embodiments, determining the type of the target application according to the destination domain name includes:

[0024] The type of the target application is determined based on the domain name identifier corresponding to the destination domain name, wherein, when the domain name identifier is a non-system domain name identifier, the type of the target application is the non-system application; when the domain name identifier is a system domain name identifier, the type of the target application is the system application.

[0025] In the above embodiment, since the destination domain name is easy for users to remember and has the advantages of flexible design, when designing the domain name of the cockpit system, the domain name identifier corresponding to each domain name can be flexibly customized according to the type of application being accessed. Therefore, the method of determining the type of target application according to the domain name identifier corresponding to the destination domain name is easy to flexibly expand when the vehicle manufacturer wants to add or update the type of application, and it also effectively improves the efficiency of determining the type of target application at the application level.

[0026] In some embodiments, the method further comprises:

[0027] If the destination IP address does not belong to the IP address whitelist and the cumulative non-system traffic consumed by the non-system services of the cockpit system within a preset period is less than the traffic threshold, the IP address whitelist is updated according to the destination IP address.

[0028] In the above embodiment, the destination IP address does not belong to the IP address whitelist, which may be because the information in the IP address whitelist is incomplete. Therefore, when the non-system traffic consumed by the non-system business of the cockpit system within the preset period is less than the traffic threshold, that is, the entertainment traffic is not fully used, the IP address whitelist can be updated without the need for manual configuration by the vehicle manufacturer, thereby improving the accuracy of using the IP address whitelist to determine the current business type of the business currently executed by the target application, and further improving the level of refined management of the Internet traffic of the cockpit system application.

[0029] In some embodiments, the access request includes a destination domain name, the destination IP address is obtained by resolving the destination domain name, the IP address whitelist is obtained by resolving a domain name whitelist, and updating the IP address whitelist according to the destination IP address includes:

[0030] If the destination domain name matches a preset domain name rule, updating the domain name whitelist, wherein the preset domain name rule is used to indicate that the type of the destination domain name is a system domain name;

[0031] The updated domain name whitelist is parsed to obtain the updated IP address whitelist.

[0032] In the above embodiment, since the destination domain name is easy for users to remember and has advantages such as flexible design, by determining whether the destination domain name matches the preset domain name rule indicating that the destination domain name is a system domain name, it is possible to simply, conveniently, and quickly determine whether the destination domain name is a system domain name. Furthermore, since the IP address whitelist is obtained by parsing the domain name whitelist, if the destination domain name is determined to be a system domain name, updating the domain name whitelist is equivalent to completing the update of the IP address whitelist, thus simplifying the method of updating the IP address whitelist and facilitating implementation.

[0033] In some embodiments, when the destination domain name matches a preset domain name rule, updating the domain name whitelist includes:

[0034] When the destination domain name matches the preset domain name rule, the destination domain name is added to the domain name whitelist, or a domain name increment list is generated according to the destination domain name, and the domain name increment list is added to the domain name whitelist.

[0035] In the above embodiment, when the destination domain name matches the preset domain name rule, indicating that the destination domain name is a system domain name, one way is to add the target domain name to the domain name whitelist to update the domain name whitelist. This method is simple and direct, and improves the update efficiency; the other is to generate a domain name incremental list for the destination domain name to update the domain name whitelist. This method uses the newly added domain name as a new list, which is convenient for managing the newly added domain name and has higher flexibility.

[0036] An embodiment of the present application provides a cockpit control device, which is applied to a vehicle cockpit system. The cockpit system includes at least one application program. The cockpit control device includes:

[0037] a determination module, configured to determine a current service type of a service currently executed by a target application, wherein the current service type includes a system service or a non-system service, and the at least one application includes the target application;

[0038] The control module is used to block the consumption of non-system traffic by the business currently executed by the target application when the current business type is the non-system business and the cumulative non-system traffic consumed by the non-system business of the cockpit system within a preset period reaches a traffic threshold.

[0039] A vehicle provided in an embodiment of the present application includes a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the method described in the embodiment of the present application is implemented.

[0040] The computer-readable storage medium provided in the embodiment of the present application stores a computer program thereon, and when the computer program is executed by a processor, the method described in the embodiment of the present application is implemented.

[0041] The computer program product provided in the embodiments of the present application includes a computer program, which implements the method described in the embodiments of the present application when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to illustrate the technical solutions of the present application.

[0043] Figure 1 Schematic diagram of the cockpit system disclosed in the embodiment of the present application for achieving flow differentiation;

[0044] Figure 2 This is a flow chart of a flow control method disclosed in an embodiment of the present application;

[0045] Figure 3 This is a flow chart of another flow control method disclosed in an embodiment of the present application;

[0046] Figure 4 This is a flow chart of another flow control method disclosed in an embodiment of the present application;

[0047] Figure 5 This is a flow chart of another flow control method disclosed in an embodiment of the present application;

[0048] Figure 6 This is a schematic diagram of a system framework for domain name resolution disclosed in an embodiment of the present application;

[0049] Figure 7 This is a flow chart of another flow control method disclosed in an embodiment of the present application;

[0050] Figure 8 This is a schematic diagram of updating a domain name whitelist disclosed in an embodiment of the present application;

[0051] Figure 9 This is a structural diagram of a cockpit control device disclosed in an embodiment of the present application;

[0052] Figure 10 It is a structural schematic diagram of a vehicle disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0053] To make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the specific technical solutions of the present application will be further described in detail below in conjunction with the drawings in the embodiments of the present application. The following embodiments are used to illustrate the present application but are not intended to limit the scope of the present application.

[0054] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing the embodiments of this application only and are not intended to limit this application.

[0055] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0056] It should be pointed out that the terms "first\second\third" involved in the embodiments of the present application are used to distinguish similar or different objects, and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0057] As vehicle intelligence technology continues to improve, the vehicle's cockpit system can provide Internet services for deployed applications, and Internet services will generate Internet traffic. At present, the Internet traffic of the cockpit system is generally divided into non-system traffic (such as entertainment traffic) and system traffic. Among them, for example, the traffic consumed by the built-in services of the vehicle system is usually system traffic. System traffic is usually mainly used to support the basic services of the vehicle (such as OTA upgrades, refresh of application interfaces regardless of application, vehicle status monitoring, etc.). The quota and billing of system traffic are the responsibility of the vehicle manufacturer; the billing of non-system traffic is the responsibility of the user or third-party content producer. Non-system traffic is usually mainly used to support some value-added services (such as music applications playing music online, web browsing online, etc.). The traffic consumed by each service or application can include both system traffic and non-system traffic.

[0058] Accordingly, the cockpit system's telematics box (TBOX) is typically divided into two types: an entertainment access point name (APN) and a system access point (APN). The cockpit system tags different application messages based on the application's user identifier (UID), sets the message's IP address based on the tag, and then forwards the message to the entertainment access point or the system access point based on the IP address, sending it to the internet.

[0059] For example, see Figure, Figure 1 This is a schematic diagram of the cockpit system disclosed in the embodiment of the present application to achieve traffic differentiation. Among them, the Ethernet network port of the central display unit (CDU) of the cockpit system is assigned two IP addresses, for example, 192.168.2.1 and 192.168.2.2. The cockpit system marks different application messages according to the user identifier of the application, and sets the IP address of the message according to the mark, that is, selects the IP address; further, the on-board communication module forwards the application message to different traffic access points according to the IP address to access the network resources of the external network, for example, forwarding the application message corresponding to 192.168.2.1 to APN1, and forwarding the application message corresponding to 192.168.2.2 to APN2.

[0060] For example, in a scenario where a vehicle's cockpit system provides Internet access for deployed applications, the application on the cockpit system's central control screen accesses the Internet via the IP address 192.168.2.1, i.e., accesses the Internet via the system traffic channel, with the vehicle manufacturer paying for the generated system traffic. Alternatively, the application accesses the Internet via the IP address 192.168.2.2, i.e., accesses the Internet via the entertainment traffic channel, with the user paying for the generated entertainment traffic. It should be noted that the traffic channels corresponding to the above IP addresses are merely examples and do not constitute a limitation of the embodiments of this application.

[0061] Currently, cockpit systems typically have a limited monthly non-system traffic limit. Exceeding this limit can easily increase users' non-system traffic costs. Therefore, it's necessary to manage the Internet traffic of applications deployed on the cockpit system.

[0062] In view of this, an embodiment of the present application provides a traffic control method, a cockpit control device, a vehicle, and a storage medium. The method is applied to a vehicle's cockpit system, the cockpit system including at least one application, and the method includes: determining the current service type of a service currently executed by a target application, the current service type including a system service or a non-system service, and at least one application including a target application; if the current service type is a non-system service, and the cumulative non-system traffic consumed by the cockpit system's non-system services within a preset period reaches a traffic threshold, blocking the consumption of non-system traffic by the service currently executed by the target application. The embodiment of the present application can perform refined management of the Internet traffic of the cockpit system's applications, thereby avoiding an increase in the user's non-system traffic usage costs.

[0063] In order to make the purpose and technical solution of this application clearer and more intuitive, a flow control method disclosed in this application is described below with reference to the accompanying drawings. It should be noted that this method can be applied to a vehicle cabin system.

[0064] The following describes in detail a flow control method disclosed in this application, taking a vehicle cabin system as an example. Figure 2 , Figure 2 This is a flow chart of a flow control method disclosed in the embodiment of this application. Figure 2 The method shown may include the following steps:

[0065] In step 201 , a cockpit system of a vehicle determines a current service type of a service currently being executed by a target application.

[0066] In an embodiment of the present application, the vehicle's cockpit system includes at least one application, and the at least one application includes a target application. It can be understood that the target application is any one or more of the at least one application deployed in the vehicle's cockpit system.

[0067] As can be seen from the foregoing description, the vehicle's cockpit system can provide Internet access services for deployed applications. It should be noted that the services currently being executed by the target application in the embodiments of this application are used to indicate the aforementioned Internet access services. Furthermore, since Internet access services generate Internet traffic, the Internet traffic of the cockpit system is generally divided into non-system traffic (e.g., entertainment traffic) and system traffic. Different Internet services generate different amounts of traffic. In other words, different types of services currently being executed by the target application will generate different types of Internet traffic.

[0068] In the embodiment of the present application, the current service type of the service currently being executed by the target application includes system service or non-system service. It can be understood that system service is used to indicate Internet services that generate system traffic, and non-system service is used to indicate Internet services that generate entertainment traffic. In other words, if the current service type of the service currently being executed by the target application is system service, the generated Internet traffic is system traffic; if the current service type of the service currently being executed by the target application is non-system service, the generated Internet traffic is non-system traffic.

[0069] It is understandable that, in the process of providing Internet access services for the target application, the vehicle's cockpit system can detect the current business type of the business currently executed by the target application to determine the traffic generated by the business currently executed by the target application, so as to prepare for the management of the Internet access traffic of the application deployed on the cockpit system.

[0070] In some embodiments, the amount of traffic consumed by the target application's current business can be determined based on the target application's current business type. When the current business type is a system business, the amount of traffic consumed by the target application's current business is used to indicate the amount of system traffic. When the current business type is a non-system business, the amount of traffic consumed by the target application's current business is used to indicate the amount of non-system traffic. Thus, the cumulative traffic consumed by each application's business can be counted in real time based on the detected business type. This allows the vehicle's cabin system to obtain the cumulative traffic consumed by the cabin system's non-system business and the cumulative traffic consumed by its system business.

[0071] In step 202 , when the current service type of the vehicle's cockpit system is non-system service and the accumulated non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches a traffic threshold, the target application's current service consumption of non-system traffic is blocked.

[0072] In an embodiment of the present application, the cockpit system can also monitor whether the non-system traffic consumed by the non-system services of the cockpit system within a preset period has reached a traffic threshold. It should be noted that the size of the traffic threshold can be customized by the vehicle manufacturer or the user. For example, the traffic threshold can be 5GB, 10GB, etc., and this application does not limit this. The preset period indicates that the non-system traffic consumed by the non-system services of the cockpit system is counted according to a preset time period. The preset period can be customized by the vehicle manufacturer or the user. For example, it can be one week, one month, etc., and this application does not limit this.

[0073] In an embodiment of the present application, in addition to determining whether the cumulative non-system traffic consumed by the non-system services of the cockpit system reaches the traffic threshold, it is also necessary to comprehensively determine whether to block the service currently executed by the target application based on the judgment result of the current service type of the service currently executed by the target application.

[0074] In some implementations, if the target application is currently executing a non-system service and the cumulative non-system traffic consumed by the in-cabin system's non-system services reaches a traffic threshold, the target application's consumption of non-system traffic is blocked. In this scenario, if the cumulative non-system traffic consumed by the in-cabin system's non-system services reaches the traffic threshold, indicating that the entertainment traffic usage limit has been reached, the target application's consumption of non-system traffic needs to be blocked.

[0075] In some embodiments, if the target application is currently executing a system service and the cumulative non-system traffic consumed by the non-system services of the in-cabin system has reached a traffic threshold, the target application is controlled to continue executing the current service. In this scenario, although the cumulative non-system traffic consumed by the in-cabin system's non-system services has reached the traffic threshold, indicating that the entertainment traffic usage limit has been reached, since the target application is currently executing a system service, there is no need to block the target application's current system service, thereby ensuring the normal operation of the target application's current system service.

[0076] In some embodiments, if the target application is currently executing a non-system service and the cumulative non-system traffic consumed by the cabin system's non-system services has not reached a traffic threshold, the target application is controlled to continue executing the currently executed service. In this scenario, although the target application is currently executing a non-system service, since the cumulative non-system traffic consumed by the cabin system's non-system services has not reached the traffic threshold, indicating that the entertainment traffic has not been exhausted, there is no need to block the target application's current non-system service from consuming non-system traffic, thereby ensuring the normal operation of the target application's current non-system service.

[0077] It can be understood that in the above-mentioned different implementations, the consumption of non-system traffic by the service currently executed by the target application is blocked only when the current service type of the service currently executed by the target application is non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system reaches the traffic threshold.

[0078] In some embodiments, blocking the target application's current service's consumption of non-system traffic is accomplished by intercepting the target application's current service's consumption of non-system traffic. Specifically, if the target application's current service type is a non-system service, as long as the cumulative non-system traffic consumed by the cockpit system's non-system services reaches a traffic threshold, the target application's current service's consumption of non-system traffic is blocked to prevent additional non-system traffic from being used.

[0079] It can be seen that the implementation of the embodiment of the present application combines the current business type of the business currently executed by the target application and the non-system traffic consumed cumulatively by the non-system business of the cockpit system within a preset period, and realizes the refined management of the Internet traffic of the cockpit system application in multiple dimensions, which can avoid the increase in the usage cost of the non-system traffic consumed by the user's non-system business.

[0080] Based on the description of the preceding embodiments, we have a basic understanding of how to control cockpit system traffic based on the current service type of the application currently executing and the accumulated non-system traffic consumed by the cockpit system's non-system services. To further understand how to determine the current service type of the service currently executed by the application, we will provide a detailed explanation with reference to other diagrams below. Specifically, the implementation of determining the current service type of the service currently executed by the target application in step 201 can be seen in steps 301 to 302.

[0081] See Figure 3 , Figure 3 This is a flow chart of another flow control method disclosed in the embodiment of this application. Figure 3 The method shown may include the following steps:

[0082] In step 301 , the vehicle's cockpit system monitors an access request initiated by a target application to an external network. The access request is used to indicate a destination IP address of the external network accessed by the target application.

[0083] In an embodiment of the present application, the service currently executed by the target application may be generated by the target application initiating an access request to a destination IP address of an external network. It is understood that the destination IP address is used to indicate the address of the network resource of the external network accessed by the target application, that is, the target application can obtain the corresponding network resource by accessing the destination IP address. It should be noted that the destination IP address can be any IP address such as 192.168.2.1, 192.168.2.2, and this application does not limit this.

[0084] It is understandable that an access request usually carries a destination IP address. Therefore, the vehicle's cockpit system can detect the access request of the target application in real time to determine the destination IP address of the external network accessed by the target application.

[0085] It should be noted that the vehicle's cockpit system can detect the access requests of each deployed application in real time to determine the destination IP address of the external network accessed by each application. The destination IP address of the external network accessed by each application can be the same or different.

[0086] In step 302 , the vehicle's cockpit system determines the current service type based on the destination IP address. The service type of the network resource of the external network accessed based on the destination IP address is the current service type.

[0087] In this embodiment of the present application, after initiating an access request, the target application accesses network resources on the external network based on the destination IP address. This process of accessing network resources based on the destination IP address indicates the service currently being executed by the target application. Therefore, the current service type corresponding to the service currently being executed by the target application can be determined based on the destination IP address. In other words, the vehicle's cockpit system can determine the current service type of the service currently being executed by the target application based on the destination IP address.

[0088] In some embodiments, the destination IP address includes a service type identifier, and the vehicle's cockpit system determines the current service type based on the destination IP address, including: when the service type identifier of the destination IP address is a system service identifier, determining that the current service type of the service currently executed by the target application is a system service, or, when the service type identifier of the destination IP address is a non-system service identifier, determining that the current service type of the service currently executed by the target application is a non-system service.

[0089] In step 303, when the current service type of the vehicle's cockpit system is non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold, the target application's current service consumption of non-system traffic is blocked.

[0090] In some embodiments, blocking the consumption of non-system traffic by the target application's current business is accomplished by intercepting access requests initiated by the target application to the external network. In other words, by intercepting access requests initiated by the target application, the consumption of non-system traffic by the target application's current business is blocked.

[0091] For other implementations of step 303 , please refer to the contents of the aforementioned step 202 , which will not be described in detail here.

[0092] It can be seen that by implementing the embodiments of the present application, by combining the current business type of the business currently executed by the target application and the non-system traffic accumulated by the non-system business of the cockpit system within a preset period, a multi-dimensional refined management of the Internet traffic of the cockpit system application is achieved, which can avoid an increase in the cost of using the non-system traffic consumed by the user's non-system business. Since the access request carries the destination IP address of the external network accessed by the target application, the current business type of the business currently executed by the target application can be quickly determined through the destination IP address. In other words, this method of controlling whether to block the non-system business executed by the target application based on the IP address improves the efficiency of the refined management of the Internet traffic of the cockpit system application.

[0093] Based on the description of the preceding embodiments, we have a basic understanding of how to determine the current service type of a service currently being executed by an application based on the destination IP address. Below, in conjunction with other illustrations, we will detail other embodiments for determining that the current service type of a service currently being executed by an application is a non-system service based on the destination IP address. That is, the embodiment for determining a non-system service based on the destination IP address in step 302 above can be seen in steps 402 to 403.

[0094] See Figure 4 , Figure 4 This is a flow chart of another flow control method disclosed in the embodiment of this application. Figure 4 The method shown may include the following steps:

[0095] In step 401 , the vehicle's cockpit system monitors an access request initiated by a target application to an external network. The access request is used to indicate a destination IP address of the external network accessed by the target application.

[0096] Regarding the implementation of step 401, reference may be made to the content of the aforementioned step 301, which will not be repeated here.

[0097] In step 402 , when the destination IP address does not belong to the IP address whitelist, the vehicle's cockpit system determines that the current service type is a non-system service.

[0098] In some embodiments, the vehicle's cockpit system stores an IP address whitelist, which includes at least one IP address. The service type for external network resources accessed by each IP address is a system service. It should be noted that each IP address stored in the IP address whitelist corresponds to a pre-configured system service. That is, when an application initiates an access request to an IP address in the IP address whitelist and obtains the corresponding network resource, the service is a system service.

[0099] In an embodiment of the present application, the vehicle's cockpit system can determine whether the destination IP address is in the IP address whitelist corresponding to the system business. If the destination IP address is not in the IP address whitelist corresponding to the system business, that is, the destination IP address does not belong to the IP address whitelist, it means that the current business type of the business currently executed by the target application is non-system business.

[0100] It can be understood that if the destination IP address is in the IP address whitelist corresponding to the system service, that is, the destination IP address belongs to the IP address whitelist, it means that the current service type of the service currently executed by the target application is system service.

[0101] In some embodiments, the vehicle's in-cabin system stores an IP address blacklist, which includes at least one IP address, and the type of service for each IP address accessing external network resources is classified as non-system service. It should be noted that the configuration method for the IP address blacklist can be found in the aforementioned implementation method for purchasing an IP address blacklist, and is not further described here.

[0102] It should be noted that in the embodiments of the present application, each IP address stored in the IP address whitelist can be a pre-set IP address corresponding to a system service or an IP address corresponding to a non-system service; correspondingly, each IP address stored in the IP address blacklist can be a pre-set IP address corresponding to a non-system service or an IP address corresponding to a system service. It should be understood that when configuring the IP addresses in the IP address whitelist and the IP address blacklist, the service types corresponding to the IP addresses are opposite.

[0103] In step 403, when the current service type of the vehicle's cockpit system is non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold, the target application's current service consumption of non-system traffic is blocked.

[0104] In some implementations, the IP address whitelist is obtained by parsing the domain name whitelist.

[0105] As an example, the following policy can be used to block the services currently being executed by the target application:

[0106] (1)iptables -t filter-A OUTPUT -o eth0 -m set! --match-set testcn1 dst-jDROP, indicating that the destination IP address is not in the IP address whitelist obtained by domain name whitelist resolution, and the business currently executed by the target application will be dropped, that is, the access request initiated by the target application to the external network will be intercepted.

[0107] For other implementations of step 403 , reference may be made to the contents of the aforementioned steps 202 and 303 , which will not be repeated here.

[0108] It can be seen that by implementing the embodiments of the present application, by combining the current business type of the business currently executed by the target application and the non-system traffic accumulated by the non-system business of the cockpit system within a preset period, a multi-dimensional refined management of the Internet traffic of the cockpit system application is achieved, which can avoid an increase in the cost of using the non-system traffic consumed by the user's non-system business. Since the business type of accessing network resources on the external network based on the IP address in the IP address whitelist is a system business, by determining whether the destination IP address is in the IP address whitelist corresponding to the system business, it can be quickly and accurately determined whether the business currently executed by the target application is a non-system business.

[0109] Based on the description of the preceding embodiments, we have a basic understanding of how to determine the current service type as a non-system service based on the destination IP address and an IP address whitelist. To avoid erroneously blocking services currently being executed by system applications when the same destination IP address is accessed simultaneously by different applications, other embodiments for determining the current service type as a non-system service based on the destination IP address and an IP address whitelist will be described in detail below, in conjunction with other diagrams. Specifically, the implementation of step 402 above can be seen in the following steps 502 to 503.

[0110] See Figure 5 , Figure 5 This is a flow chart of another flow control method disclosed in the embodiment of this application. Figure 5 The method shown may include the following steps:

[0111] In step 501 , the vehicle's cockpit system monitors an access request initiated by a target application to an external network. The access request is used to indicate a destination IP address of the external network accessed by the target application.

[0112] Regarding the implementation of step 501, reference may be made to the content of the aforementioned step 301, which will not be repeated here.

[0113] In step 502 , the vehicle's cockpit system determines the type of the target application when the destination IP address does not belong to the IP address whitelist.

[0114] Since the same destination IP address may be accessed by different types of applications at the same time (such as non-system applications and system applications), in order to avoid blocking the currently executed business of the application based on the destination IP address, the access of both system applications and non-system applications to the destination IP address is blocked, thereby affecting the normal operation of the system application, the type of the target application can also be determined when it is determined that the destination IP address does not belong to the IP address whitelist.

[0115] In some implementations, the type of the target application is a non-system application or a system application. That is, when it is determined that the destination IP address does not belong to the IP address whitelist, the type of the target application can also be determined to be a non-system application or a system application.

[0116] It should be noted that non-system applications are used to indicate entertainment applications (such as music applications, video applications, etc.). System applications are used to indicate vehicle navigation and vehicle system-level applications, etc. Vehicle manufacturers can customize the classification of application types, and this application does not limit this.

[0117] In some embodiments, the access request includes a destination domain name, and determining the type of the target application includes: determining the type of the target application based on the destination domain name. It is understood that a domain name is an Internet identifier used to identify and locate a computer or group of computers on the Internet. It consists of a dot-separated string (e.g., xx.xxx.com) and is used instead of an IP address to facilitate user memory and access to network resources.

[0118] Since the destination IP address is obtained by resolving the destination domain name, and the destination domain name is easy for users to remember and has the advantages of flexible design, when designing the domain name of the cockpit system, each domain name can be flexibly customized according to the type of application being accessed. Therefore, the method of determining the type of target application based on the destination domain name effectively improves the efficiency of determining the type of target application.

[0119] As an example, when designing the domain name of the cockpit system, the domain name can be split, and the same domain name can be split into two domain name 1 / domain name 2. Domain name 1 is used for system business, and domain name 2 is used for entertainment business. In this way, the entertainment business domain name can be blocked without affecting the system business.

[0120] In some embodiments, determining the type of the target application based on the destination domain name includes: determining the type of the target application based on the domain name identifier corresponding to the destination domain name, wherein, when the domain name identifier is a non-system domain name identifier, the type of the target application is a non-system application, and when the domain name identifier is a system domain name identifier, the type of the target application is a system application.

[0121] In this implementation, a corresponding domain name identifier may be pre-configured for each domain name. The domain name identifier is used to indicate the type of application. It is understandable that the destination domain name also includes the corresponding domain name identifier.

[0122] As an example, you can configure the domain name identifier for non-system applications as a non-system domain name identifier, and the domain name identifier for system applications as a system domain name identifier. This allows you to determine whether the target application is a non-system application or a system application, depending on whether the domain name identifier of the target domain is a non-system domain name identifier or a system domain name identifier. For example, you can add "sys" as the system domain name identifier to the domain name.

[0123] With this implementation, since the destination domain name is easy for users to remember and has the advantages of flexible design, when designing the domain name of the cockpit system, the domain name identifier corresponding to each domain name can be flexibly customized according to the type of application being accessed. Therefore, the method of determining the type of target application based on the domain name identifier corresponding to the destination domain name is easy to flexibly expand when vehicle manufacturers want to add or update the type of application, and it also effectively improves the efficiency of determining the type of target application at the application level.

[0124] In some embodiments, the destination IP address is obtained by resolving the destination domain name. It should be understood that when the target application initiates an access request to the destination IP address, the access request carries the destination domain name to be accessed, and then the destination domain name is resolved to obtain the destination IP address, that is, the mapping relationship between the destination domain name and the destination IP address. For example, when accessing an external network (such as website 1), the destination domain name (such as xxxx.com) is resolved to the address identifier corresponding to website 1, that is, the destination IP address (such as 192.168.2.2).

[0125] It should be noted that the purpose of resolving the destination domain name is to convert the destination domain name that is easy for users to remember into the destination IP address that can be identified by the external network. The conversion between the destination domain name and the destination IP address is called domain name resolution, and the network host that performs domain name resolution can be a DNS server.

[0126] In some embodiments, upon receiving an access request from a target application, the vehicle's cockpit system may perform domain name resolution on the destination domain name in the access request to obtain the destination IP address. There are two ways to perform domain name resolution on the destination domain name in the access request:

[0127] Method 1: Perform domain name resolution on the target domain name based on the standard domain name resolution policy.

[0128] The standard domain name resolution policy is used to indicate that the destination domain name is resolved through the standard domain name resolution (legacy DNS). The standard domain name resolution is resolved through the operator's DNS server, and the operator's DNS server performs resolution through the network daemon (netd) process.

[0129] Method 2: Perform domain name resolution on the target domain name based on the network database domain name resolution policy.

[0130] The network library domain name resolution policy is used to instruct the target domain name to be resolved through the network library domain name resolution (http dns). The network library domain name resolution is resolved through a commercial DNS server, and the commercial DNS server performs resolution through the network library.

[0131] In some embodiments, after performing domain name resolution on the destination domain name in the access request and obtaining the destination IP address, the destination domain name and / or the destination IP address and / or the mapping relationship between the destination domain name and the destination IP address may be stored in the domain name management module. For example, when performing domain name resolution, the destination IP address corresponding to the destination domain name resolution is stored, using the ipset tool as an example:

[0132] (1)ipset create testcn1 hash:net;

[0133] (2)ipset add testcn1 xx.xx.xx.xx (where xx.xx.xx.xx is the destination IP address);

[0134] Among them, (1) indicates that an ipset set is created and the name is testcn1; (2) indicates that the destination IP address is stored in the IP address whitelist and the IP address whitelist is stored in testcn1.

[0135] As an example, see Figure 6 , Figure 6This is a schematic diagram of a system framework for domain name resolution disclosed in an embodiment of the present application. The system framework includes a cockpit system central domain and an on-board communication domain (TBOX domain). The cockpit system central domain is mainly used to resolve Internet access requests, and the on-board communication domain is mainly used to access corresponding network resources based on the resolved IP address. For example, when an Internet access request is detected, the standard domain name resolution (legacy DNS resolution) or network library domain name resolution (http DNS resolution) can be used to resolve the destination domain name in the Internet access request; further, the operator's DNS server stores the destination domain name, and / or the destination IP address, and / or the mapping relationship between the destination domain name and the destination IP address in the domain name management module (dnsmgr module). The commercial DNS server can also store the destination domain name, and / or the destination IP address, and / or the mapping relationship between the destination domain name and the destination IP address in the domain name management module (dnsmgr module) based on the process (native); and the resolved destination IP address is sent to the on-board communication module, and the on-board communication module forwards the application message to different traffic access points according to the destination IP address to access the corresponding network resources.

[0136] Optionally, to prevent LAN communications between the vehicle's electronic control units (ECUs) from being blocked, all LAN IP addresses can be pre-added to an IP address whitelist. For example, you can execute ipset addtestcn1 xx.xx.xx.xx (where xx.xx.xx.xx is the IP address corresponding to the LAN) to indicate that the LAN IP addresses are to be stored in the IP address whitelist, and then store the IP address whitelist in testcn1.

[0137] Step 503 : When the target application is a non-system application, the vehicle cockpit system determines that the current service type is a non-system service.

[0138] In the embodiment of the present application, only when the type of the target application is a non-system application is it determined that the service currently executed by the target application is a non-system service.

[0139] In step 504 , when the current service type of the vehicle's cockpit system is non-system service and the accumulated non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold, the target application's current service consumption of non-system traffic is blocked.

[0140] Regarding the implementation of step 504, reference may be made to the contents of the aforementioned steps 202, 303 and 403, which will not be repeated here.

[0141] It can be seen that by implementing the embodiment of the present application, by combining the current business type of the business currently executed by the target application and the non-system traffic accumulated by the non-system business of the cockpit system within a preset period, a multi-dimensional refined management of the Internet traffic of the cockpit system application is achieved, which can avoid an increase in the cost of using the non-system traffic consumed by the user's non-system business. Under the premise that the non-system traffic consumed by the non-system business of the cockpit system reaches the traffic threshold, the currently executed business is blocked only when the destination IP address is accessed by the non-system application, effectively avoiding the system application being blocked when accessing the destination IP address, and further improving the level of refined management of the Internet traffic of the cockpit system application.

[0142] Based on the description of the above embodiments, we have basically understood the role of the IP address whitelist in controlling the traffic of the cockpit system. Among them, the IP address whitelist can be updated in real time. The following will detail the implementation method of updating the IP address whitelist with reference to other figures.

[0143] See Figure 7 , Figure 7 FIG. 1 is a flow chart of another flow control method disclosed in an embodiment of the present application. Figure 7 The method shown may include the following steps:

[0144] In step 701 , the vehicle's cockpit system monitors an access request initiated by a target application to an external network. The access request is used to indicate a destination IP address of the external network accessed by the target application.

[0145] Regarding the implementation of step 701, reference may be made to the content of the aforementioned step 301, which will not be repeated here.

[0146] In step 702 , the vehicle's cockpit system updates the IP address whitelist according to the destination IP address if the destination IP address does not belong to the IP address whitelist and the non-system traffic consumed by the non-system services of the cockpit system within a preset period is less than the traffic threshold.

[0147] In an embodiment of the present application, if the cumulative non-system traffic consumed by the cabin system's non-system services within a preset period is less than a traffic threshold, this indicates that the entertainment traffic has not been fully used. The destination IP address may not be on the IP address whitelist because the information in the IP address whitelist is incomplete. Therefore, to improve the accuracy of determining the current service type of the service currently being executed by the application, the IP address whitelist may be updated if the cumulative non-system traffic consumed by the cabin system's non-system services is less than the traffic threshold, indicating that the entertainment traffic has not been fully used.

[0148] Based on the description of the aforementioned embodiment, it can be seen that the access request includes a destination domain name, and the destination IP address is obtained by resolving the destination domain name. Optionally, the IP address whitelist is obtained by resolving the domain name whitelist. It should be noted that the implementation method of performing domain name resolution on the domain name whitelist to obtain the IP address whitelist can be referred to the implementation method of performing domain name resolution on the destination domain name to obtain the destination IP address in step 502 above, and will not be repeated here.

[0149] In some embodiments, updating the IP address whitelist based on the destination IP address includes: updating the domain name whitelist when the destination domain name matches a preset domain name rule, the preset domain name rule being used to indicate that the type of the destination domain name is a system domain name; and parsing the updated domain name whitelist to obtain an updated IP address whitelist. The preset domain name rule is used to indicate that the type of the destination domain name is a system domain name. In other words, if the destination domain name matches the preset domain name rule, it indicates that the type of the destination domain name is a system domain name. In this case, the domain name whitelist can be updated based on the destination domain name.

[0150] Optionally, the destination domain name can be identified to obtain domain name features corresponding to the destination domain name; the domain name features corresponding to the destination domain name are matched with preset domain name rules, and when the domain name features corresponding to the destination domain name match the preset domain name rules, the domain name whitelist is updated.

[0151] Optionally, the domain name feature corresponding to the destination domain name may include a domain name identifier. When the domain name identifier corresponding to the destination domain name is a system domain name identifier, it is determined that the domain name feature corresponding to the destination domain name matches a preset domain name rule.

[0152] It should be noted that the preset domain name rules can be customized by the vehicle manufacturer. For example, the preset domain name rules can be a pre-set system domain name identifier, such as a second-level domain name, which is not limited in this application.

[0153] In this embodiment, after obtaining the updated domain name whitelist, the updated domain name whitelist can be parsed to obtain an updated IP address whitelist. It should be noted that the implementation method of performing domain name parsing on the updated domain name whitelist to obtain the updated IP address whitelist can be referred to the implementation method of performing domain name parsing on the target domain name to obtain the target IP address in the aforementioned step 502, and will not be repeated here.

[0154] This embodiment has the advantages of being easy for users to remember the destination domain name and having a flexible design. By determining whether the destination domain name matches a preset domain name rule indicating that the destination domain name is a system domain name, it is possible to simply, conveniently, and quickly determine whether the destination domain name is a system domain name. Furthermore, since the IP address whitelist is obtained by parsing the domain name whitelist, if the destination domain name is determined to be a system domain name, updating the domain name whitelist is equivalent to completing an update of the IP address whitelist, simplifying the method for updating the IP address whitelist and facilitating implementation.

[0155] In some embodiments, when the destination domain name matches the preset domain name rules, the domain name whitelist is updated, including: when the destination domain name matches the preset domain name rules, the vehicle's cockpit system adds the destination domain name to the domain name whitelist, or generates a domain name incremental list based on the destination domain name, and adds the domain name incremental list to the domain name whitelist.

[0156] Optionally, the destination domain name may be added to a domain name whitelist to obtain an updated domain name whitelist.

[0157] Optionally, the destination domain name can be added to the incremental domain name list, and the incremental domain name list can be added to the whitelist to obtain an updated whitelist. It is understood that the incremental domain name list is an independent domain name list and does not affect the original whitelist. In other words, the original whitelist and the incremental domain name list constitute the updated whitelist. Based on the matching results of the destination domain name and the preset domain name rules, the updated whitelist is continuously obtained, improving the real-time performance of the whitelist.

[0158] As an example, see Figure 8 , Figure 8 This is a schematic diagram of updating a domain name whitelist disclosed in an embodiment of the present application. When the destination domain name matches the preset domain name rule, the destination domain name is added to the domain name incremental list. The domain name whitelist includes the domain name incremental list and the preset domain name whitelist, wherein the preset domain name whitelist stores the original domain name before the update.

[0159] Using this implementation, when the destination domain name matches the preset domain name rule, indicating that the destination domain name is a system domain name, one way is to add the target domain name to the domain name whitelist to update the domain name whitelist. This method is simple and direct, and improves the update efficiency; the other is to generate a domain name incremental list for the destination domain name to update the domain name whitelist. This method uses the newly added domain name as a new list, which facilitates the management of the newly added domain name and is more flexible.

[0160] Optionally, if the destination domain name matches a preset domain name rule, the server can add the destination domain name to a domain name whitelist, or generate an incremental domain name list based on the destination domain name and add the incremental domain name list to the domain name whitelist. It should be noted that the server can be a cloud platform, cloud server, etc., without limitation.

[0161] Optionally, the domain name increment list can also be manually screened and determined by the vehicle manufacturer. That is, after generating a domain name increment list based on the target domain name and adding the domain name increment list to the domain name whitelist, the domain name increment list can be updated in response to a user update operation to obtain an updated domain name increment list, and the updated domain name increment list can be added to the domain name whitelist.

[0162] As can be seen, by implementing the embodiments of the present application, by combining the current service type of the target application and the cumulative non-system traffic consumed by the cockpit system's non-system services within a preset period, refined multi-dimensional management of the cockpit system's application's internet traffic can be achieved, thus avoiding increased costs associated with the non-system traffic consumed by the user's non-system services. The IP address whitelist can be automatically updated without requiring manual configuration by the vehicle manufacturer, improving the accuracy of using the IP address whitelist to determine the current service type of the target application's current service, further enhancing the refined management of the cockpit system's application's internet traffic.

[0163] It should be understood that, although the various steps in the above-mentioned flowcharts are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly restricted in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps. In addition, the above-mentioned multiple embodiments can be implemented independently or in combination with each other, and are not limited thereto.

[0164] Based on the aforementioned embodiments, embodiments of the present application provide a cockpit control device, which is applied to the vehicle cockpit system of the aforementioned embodiments, wherein the cockpit system includes at least one application program. The cockpit control device includes various modules and units included in each module, and can be implemented by a processor; of course, it can also be implemented by a specific logic circuit. During implementation, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA).

[0165] See Figure 9 , Figure 9 This is a structural diagram of a cockpit control device disclosed in an embodiment of the present application. Figure 9 The cockpit control device shown includes a determination module 901 and a control module 902 .

[0166] A determination module 901 is configured to determine a current service type of a service currently executed by a target application, where the current service type includes a system service or a non-system service, and at least one application includes the target application;

[0167] The control module 902 is used to block the consumption of non-system traffic by the service currently executed by the target application when the current service type is non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold.

[0168] In some embodiments, the determination module 901 determines the current service type of the service currently executed by the target application, specifically for:

[0169] Monitor access requests initiated by the target application to the external network. The access requests are used to indicate the destination IP address of the external network accessed by the target application.

[0170] The current service type is determined based on the destination IP address. The service type of the network resource of the external network accessed based on the destination IP address is the current service type.

[0171] In some embodiments, the determination module 901 determines the current service type based on the destination IP address, specifically for:

[0172] When the destination IP address does not belong to the IP address whitelist, the current service type is determined to be non-system service, the IP address whitelist includes at least one IP address, and the service type of the network resource of the external network accessed by each IP address is system service.

[0173] In some embodiments, when the destination IP address does not belong to the IP address whitelist, the determination module 901 determines that the current service type is a non-system service, and is further specifically configured to:

[0174] In a case where the destination IP address does not belong to the IP address whitelist, determining the type of the target application, the type of the target application being a non-system application or a system application;

[0175] In a case where the type of the target application is a non-system application, it is determined that the current service type is a non-system service.

[0176] In some embodiments, the access request includes a destination domain name, and the destination IP address is obtained by resolving the destination domain name. The determination module 901 determines the type of the target application, specifically for:

[0177] Determine the type of target application based on the destination domain name.

[0178] In some embodiments, the determination module 901 determines the type of the target application based on the destination domain name, specifically for:

[0179] The type of the target application is determined based on the domain name identifier corresponding to the target domain name. When the domain name identifier is a non-system domain name identifier, the type of the target application is a non-system application. When the domain name identifier is a system domain name identifier, the type of the target application is a system application.

[0180] In some embodiments, the cockpit control device further includes an update module;

[0181] The update module is used to update the IP address whitelist according to the destination IP address when the destination IP address does not belong to the IP address whitelist and the cumulative non-system traffic consumed by the non-system services of the cockpit system within a preset period is less than the traffic threshold.

[0182] In some embodiments, the access request includes a destination domain name, the destination IP address is obtained by resolving the destination domain name, and the IP address whitelist is obtained by resolving the domain name whitelist;

[0183] The update module updates the IP address whitelist based on the destination IP address. It is specifically used to:

[0184] If the destination domain name matches a preset domain name rule, the domain name whitelist is updated. The preset domain name rule is used to indicate that the type of the destination domain name is a system domain name.

[0185] The updated domain name whitelist is parsed to obtain an updated IP address whitelist.

[0186] In some embodiments, the update module updates the domain name whitelist when the destination domain name matches a preset domain name rule, specifically for:

[0187] When the destination domain name matches the preset domain name rule, the destination domain name is added to the domain name whitelist, or a domain name incremental list is generated based on the destination domain name, and the domain name incremental list is added to the domain name whitelist.

[0188] It should be noted that the division of modules in the cockpit control device shown in the embodiment of the present application is schematic and is merely a logical function division. There may be other division methods in actual implementation.

[0189] The embodiment of the present application provides a vehicle, please refer to Figure 10 , Figure 10 This is a schematic diagram of the structure of a vehicle disclosed in the embodiment of this application. Figure 10 As shown, the vehicle includes:

[0190] A memory 1001 storing executable program code;

[0191] a processor 1002 coupled to the memory 1001;

[0192] The processor 1002 calls the executable program code stored in the memory 1001 to execute any one of the flow control methods in the above method embodiments.

[0193] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, some or all of the steps in any one of the flow control methods provided in the above embodiments are implemented.

[0194] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements part or all of the steps in any one of the flow control methods provided in the above embodiments.

[0195] Those skilled in the art will understand that Figure 10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the vehicle to which the solution of the present application is applied. The specific vehicle may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0196] It should be noted that the descriptions of the above embodiments of the apparatus, vehicle, computer-readable storage medium, and computer program product are similar to the descriptions of the above-mentioned method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus, vehicle, computer-readable storage medium, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0197] It should be understood that "one embodiment" or "an embodiment" or "some embodiments" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The above description of the various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other. For the sake of brevity, they will not be repeated here.

[0198] The term "and / or" in this article is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, object A and / or object B can mean: object A exists alone, object A and object B exist at the same time, and object B exists alone.

[0199] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0200] In the several embodiments provided in this application, it should be understood that the disclosed methods, devices and vehicles can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of the modules above is only a logical function division. There may be other division methods in actual implementation, such as: multiple modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0201] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and other media that can store program codes.

[0202] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0203] The features disclosed in the several device embodiments provided in this application can be arbitrarily combined without conflict to obtain new device embodiments.

[0204] The above is merely an embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A flow control method, characterized in that: A cockpit system for a vehicle, the cockpit system including at least one application, and the method comprising: determining a current service type of a service currently executed by a target application, wherein the current service type includes a system service or a non-system service, and the at least one application includes the target application; When the current service type is the non-system service and the cumulative non-system traffic consumed by the non-system service of the cockpit system within a preset period reaches the traffic threshold, the consumption of non-system traffic by the service currently executed by the target application is blocked.

2. The method according to claim 1, characterized in that Determining the current business type of the business currently executed by the target application includes: Monitoring an access request initiated by the target application to an external network, the access request being used to indicate a destination IP address of the external network accessed by the target application; The current service type is determined according to the destination IP address, and the service type of the network resource of the external network accessed based on the destination IP address is the current service type.

3. The method according to claim 2, characterized in that The determining the current service type according to the destination IP address includes: When the destination IP address does not belong to the IP address whitelist, the current service type is determined to be the non-system service, the IP address whitelist includes at least one IP address, and the service type of the network resources of the external network accessed based on each IP address is the system service.

4. The method according to claim 3, characterized in that When the destination IP address does not belong to the IP address whitelist, determining that the current service type is the non-system service includes: In a case where the destination IP address does not belong to the IP address whitelist, determining a type of the target application, the type of the target application being a non-system application or a system application; In a case where the type of the target application is the non-system application, the current service type is determined to be the non-system service.

5. The method according to claim 4, characterized in that The access request includes a destination domain name, and the destination IP address is obtained by resolving the destination domain name. Determining the type of the target application includes: The type of the target application is determined according to the destination domain name.

6. The method according to claim 5, characterized in that Determining the type of the target application according to the destination domain name includes: The type of the target application is determined based on the domain name identifier corresponding to the destination domain name, wherein, when the domain name identifier is a non-system domain name identifier, the type of the target application is the non-system application; when the domain name identifier is a system domain name identifier, the type of the target application is the system application.

7. The method according to any one of claims 3 to 6, characterized in that The method further comprises: If the destination IP address does not belong to the IP address whitelist and the non-system traffic consumed cumulatively by the non-system services of the cockpit system within the preset period is less than the traffic threshold, the IP address whitelist is updated according to the destination IP address.

8. The method according to claim 7, characterized in that The access request includes a destination domain name, the destination IP address is obtained by resolving the destination domain name, the IP address whitelist is obtained by resolving the domain name whitelist, and updating the IP address whitelist according to the destination IP address includes: If the destination domain name matches a preset domain name rule, updating the domain name whitelist, wherein the preset domain name rule is used to indicate that the type of the destination domain name is a system domain name; The updated domain name whitelist is parsed to obtain the updated IP address whitelist.

9. The method according to claim 8, characterized in that When the destination domain name matches a preset domain name rule, updating the domain name whitelist includes: When the destination domain name matches the preset domain name rule, the destination domain name is added to the domain name whitelist, or a domain name increment list is generated according to the destination domain name, and the domain name increment list is added to the domain name whitelist.

10. A cockpit control device, characterized in that: A cockpit system for a vehicle, the cockpit system including at least one application, and the cockpit control device including: a determination module, configured to determine a current service type of a service currently executed by a target application, wherein the current service type includes a system service or a non-system service, and the at least one application includes the target application; The control module is used to block the consumption of non-system traffic by the business currently executed by the target application when the current business type is the non-system business and the cumulative non-system traffic consumed by the non-system business of the cockpit system reaches a traffic threshold.

11. A vehicle comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, wherein: When the processor executes the program, the steps of the method according to any one of claims 1 to 9 are implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

13. A computer program product, characterized in that The invention comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images