Vehicle-mounted communication device, map service system, and vehicle-mounted communication method

Abstract

This application proposes an in-vehicle communication device, comprising: a navigation domain control unit configured to perform a first map service operation for navigation functions using a navigation SDK, and to transmit route coordination information for synchronizing navigation driving intentions to an intelligent driving domain control unit via an in-vehicle network; and an intelligent driving domain control unit configured to perform a second map service operation for intelligent driving functions using an intelligent driving SDK, and to match the executed second map service operation with the navigation driving intentions based on the received route coordination information. This application also proposes a map service system and an in-vehicle communication method. By deploying independent SDKs for the navigation domain and the intelligent driving domain respectively, and transmitting lightweight route coordination information only between the domains, the system coupling can be reduced, supporting independent upgrades and maintenance of navigation and autonomous driving modules.

Description

Technical Field

[0001] This application relates to an in-vehicle communication device, a map service system, and an in-vehicle communication method. Background Technology

[0002] In traditional automotive electronic and electrical architectures, the intelligent driving domain heavily relies on external navigation SDKs for map data and to broadcast intelligent driving-related data. This results in high system coupling, making it susceptible to cascading impacts on intelligent driving functions if the navigation domain SDK is upgraded or its data interfaces change. This increases the difficulty of system integration and maintenance. Furthermore, the frequent transmission of large-scale maps and intelligent driving-related data between the navigation and intelligent driving domains causes data redundancy, increases system network load and resource consumption, and reduces overall operational efficiency and safety.

[0003] Therefore, under the existing multi-domain collaborative architecture of vehicles, the map service operation scheme still has many shortcomings. Summary of the Invention

[0004] The purpose of this application is to provide an in-vehicle communication device, a map service system, and an in-vehicle communication method to at least solve some of the problems in the prior art.

[0005] According to a first aspect of this application, an in-vehicle communication device is provided, comprising: a navigation domain control unit configured to perform a first map service operation for navigation functions using a navigation SDK, and to transmit route coordination information for synchronizing navigation driving intentions to an intelligent driving domain control unit via an in-vehicle network; and an intelligent driving domain control unit configured to perform a second map service operation for intelligent driving functions using an intelligent driving SDK, and to match the performed second map service operation with the navigation driving intentions based on the received route coordination information.

[0006] This application specifically includes the following technical concept: by deploying independent SDKs for the navigation domain and the intelligent driving domain, and transmitting only lightweight route coordination information between the domains instead of complete map data or map service data specific to domain functions, the system coupling can be reduced, supporting independent upgrades and maintenance of navigation and autonomous driving modules. Furthermore, even though the map service operations of the two domains are isolated, the intelligent driving domain can still execute map service operations matching the navigation driving intent based on the received route coordination information, thereby ensuring a high degree of coordination between navigation and intelligent driving functions, avoiding path information conflicts and error accumulation, and improving the system's reliability, maintainability, and operational efficiency.

[0007] In an exemplary embodiment, the first map service operation includes: navigation route planning, point of interest search, navigation guidance, navigation map data acquisition and / or navigation map data display; and / or, the second map service operation includes: lane-level semantic information generation, most probable path calculation, lane-level reconstructed route generation and broadcasting, lane-level geometric data broadcasting, lane-level topology data broadcasting, static road facility data broadcasting and / or dynamic event data broadcasting.

[0008] In one exemplary embodiment, the navigation SDK and the intelligent driving SDK provide corresponding map service operations based on different map data sources; and / or, the navigation SDK provides the first map service operation based on a standard precision map data source, and the intelligent driving SDK provides the second map service operation based on a high precision map data source.

[0009] In one exemplary embodiment, the navigation domain control unit is further configured to transmit the route coordination information to the intelligent driving domain control unit only when preset triggering conditions are met; the preset triggering conditions include: navigation route generation completed, and / or navigation route changed; the route coordination information includes: a sequence of waypoints of the navigation route, a sequence of navigation guidance instructions, and / or a sequence of global identifiers and / or local road segment identifiers of the navigation route.

[0010] In one exemplary embodiment, the route coordination information is used to characterize the navigation route, and the intelligent driving domain control unit is further configured to obtain a lane-level reconstructed route matching the navigation route based on the route coordination information using the intelligent driving SDK, and provide the lane-level reconstructed route for intelligent driving functions; in particular, the intelligent driving domain control unit is further configured to report the route coordination information to the cloud service platform using the intelligent driving SDK, and receive the lane-level reconstructed route generated by the cloud service platform based on the route coordination information.

[0011] According to a second aspect of this application, a map service system is provided, comprising: a cloud service platform configured to perform at least a portion of the computational tasks in a second map service operation in response to route coordination information reported by a smart driving SDK; and an in-vehicle communication device according to a first aspect of this application.

[0012] In one exemplary embodiment, the at least part of the computational task includes generating a lane-level reconstructed route based on route coordination information, wherein: based on the route coordination information, corresponding road segments and / or lane segments are matched in a high-precision map; lane-level geometric information, lane-level topological connection relationship information, and attribute information are added to the matched road segments and / or lane segments to generate the lane-level reconstructed route; non-drivable road segments in the lane-level reconstructed route are corrected, and / or road segments that do not meet intelligent driving constraints are replaced or adjusted.

[0013] In one exemplary embodiment, the cloud service platform is further configured to: - Verify the structural integrity, continuity, and / or legality of the route coordination information; - Verify whether the high-precision map currently used by the intelligent driving domain control unit meets the compatibility requirements with the high-precision map adapted to the lane-level reconstructed route; and / or - Verify the feasibility of lane-level reconstructed routes in high-precision maps; The cloud service platform is also configured to mark the lane-level reconstructed route as a valid route and send it to the intelligent driving domain control unit only when the above verification passes.

[0014] In an exemplary embodiment, the cloud service platform is further configured to: assign a unique identifier to the lane-level reconstructed route; and record the corresponding route version number, timestamp information, generation source, update time, and the adapted high-precision map version information for the lane-level reconstructed route.

[0015] According to a third aspect of this application, a vehicle communication method is provided, which is executed by means of the vehicle communication device according to the first aspect of this application. The vehicle communication method includes: a navigation domain control unit performing a first map service operation for navigation functions using a navigation SDK and generating route coordination information for synchronizing navigation driving intentions; the navigation domain control unit transmitting the route coordination information to an intelligent driving domain control unit via an in-vehicle network; and the intelligent driving domain control unit performing a second map service operation for intelligent driving functions based on the received route coordination information and matching the navigation driving intentions using an intelligent driving SDK. Attached Figure Description

[0016] The principles, features, and advantages of this application will be better understood below with reference to the accompanying drawings. The drawings include: Figure 1 A block diagram of a map service system according to an exemplary embodiment of this application is shown; Figure 2 A schematic diagram illustrating inter-domain collaborative operation between the navigation domain and the intelligent driving domain using a map service system according to an exemplary embodiment of this application is shown. Figure 3 This illustration shows a schematic diagram of inter-domain cooperative operation between the navigation domain and the intelligent driving domain using a map service system, according to another exemplary embodiment of this application; and Figure 4 A flowchart of an exemplary embodiment of a vehicle communication method according to this application is shown. Detailed Implementation

[0017] To make the technical problems to be solved, the technical solutions, and the beneficial technical effects of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and several exemplary embodiments. It should be understood that the specific embodiments described herein are only for explaining this application and are not intended to limit the scope of protection of this application.

[0018] Figure 1 A block diagram of a map service system according to an exemplary embodiment of this application is shown.

[0019] The map service system 1 includes an in-vehicle communication device 2 and cloud service platforms 51 and 52. The navigation domain control unit 10 and the intelligent driving domain control unit 20 communicate via an in-vehicle network 31 (such as CAN, LIN, FlexRay, MOST, or in-vehicle Ethernet). Communication between the two typically requires routing and forwarding through relay devices such as a central gateway, regional gateway, or in-vehicle Ethernet switch (not shown in detail for simplicity). In addition, the navigation domain control unit 10 and the intelligent driving domain control unit 20 can also establish a wireless communication connection 32 (such as 4G / 5G, Wi-Fi, V2X, etc.) with the cloud service platforms 51 and 52 through an in-vehicle communication unit 40 (such as a telematics control unit) to realize data interaction between the vehicle and the cloud.

[0020] The vehicle communication device 2 is installed in a vehicle equipped with intelligent driving capabilities. Intelligent driving capabilities refer to, for example, the ability of a vehicle to perform all or part of dynamic driving tasks within a defined operating design domain, such as driving automation levels corresponding to L2+ to L4.

[0021] The navigation domain control unit 10 and the intelligent driving domain control unit 20 belong to different functional domains of the vehicle. The navigation domain control unit 10 is used to perform the vehicle's navigation function and can be located in the navigation domain, or in other architectures, in the cockpit domain or body domain. The intelligent driving domain control unit 20 is used to perform the vehicle's intelligent driving function and is typically located in the intelligent driving domain.

[0022] like Figure 1 As shown, the navigation domain control unit 10 is equipped with a navigation SDK 111, which provides first map service operations for navigation functions. These first map service operations include, but are not limited to: navigation route planning, point of interest search, navigation guidance, navigation map data acquisition, and / or navigation map data display.

[0023] The intelligent driving domain control unit 20 is equipped with an intelligent driving SDK 211 that is independent of the navigation SDK 111. This intelligent driving SDK 211 is used to provide second map service operations for intelligent driving functions. The second map service operations include, but are not limited to: lane-level semantic information generation, most probable path calculation, lane-level reconstructed route generation and broadcasting, lane-level geometric data broadcasting, lane-level topology data broadcasting, static road facility data broadcasting, and / or dynamic event data broadcasting.

[0024] In the context of this application, an SDK (Software Development Kit) refers to a software toolkit that encapsulates map data acquisition functionality and related basic functions, providing calling interfaces to upper-layer applications through an Application Programming Interface (API). For example, navigation SDK 111 could be Gaode Navigation SDK, Baidu Navigation SDK, etc., which encapsulates core capabilities such as high-precision map data processing capabilities, route planning engines, and POI search engines, for the navigation domain control unit 10 to call to execute navigation functions. Intelligent driving SDK 211, for example, encapsulates core capabilities such as high-precision map data processing capabilities, electronic horizon engines, and lane-level route planning engines, for the intelligent driving domain control unit 20 to call to execute intelligent driving functions.

[0025] Both the navigation domain control unit 10 and the intelligent driving domain control unit 20 include a processor and a memory (not specifically shown in the figure). The memory may include computer-readable storage media such as hard disk, RAM, and flash memory, and stores computer program instructions. The processor may be a central processing unit (CPU), microcontroller unit (MCU), graphics processing unit (GPU), neural network processing unit (NPU), digital signal processor (DSP), or other general-purpose or special-purpose processor. When the processor executes the computer program instructions in the memory, it can realize the corresponding map data acquisition and domain function execution logic.

[0026] In this embodiment, the navigation SDK 111 and the intelligent driving SDK 211 provide corresponding map service operations based on different map data sources. For example... Figure 1 As shown, the navigation SDK 111 communicates with the first cloud service platform 51 to provide first map service operations based on a standard precision map data source (SD Map). The intelligent driving SDK 211 communicates with the second cloud service platform 52 to provide second map service operations based on a high precision map data source (HD Map). However, this application is not limited to this. In other embodiments, the navigation SDK 111 and the intelligent driving SDK 211 may also provide map service operations based on the same map data source, or both may be based on a high precision map data source, or other heterogeneous map source combinations may be used.

[0027] Furthermore, the navigation domain control unit 10 and the intelligent driving domain control unit 20 are configured to perform any large-scale map data interaction directly without using the in-vehicle network 31, and the navigation SDK 111 is no longer responsible for broadcasting map service data to the various functional modules of the intelligent driving domain. For example... Figure 1 As shown, the navigation domain control unit 10 generates only lightweight route coordination information 201 for synchronizing navigation driving intentions and transmits it to the intelligent driving domain control unit 20 via the vehicle network 31. The intelligent driving domain control unit 20 then matches the second map service operation it performs with the navigation driving intentions based on the received route coordination information 201.

[0028] In the context of this application, "matching the second map service operation with the navigation driving intention" means that the intelligent driving domain control unit 20, with the help of the intelligent driving SDK 211, based on the route coordination information 201 received from the navigation domain, keeps the map service operations it performs, such as lane-level route planning, electronic horizon generation, and intelligent driving data broadcasting, consistent with the macro route planned by the navigation domain, so as to avoid route conflicts between navigation instructions and the executed intelligent driving functions (such as the navigation prompts "turn right ahead" while the vehicle goes straight).

[0029] It should be noted that, in this embodiment, although the navigation SDK 111 and the intelligent driving SDK 211 are shown to be deployed within the navigation domain control unit 10 and the intelligent driving domain control unit 20, respectively, this application is not limited thereto. In other embodiments, the navigation SDK 111 and the intelligent driving SDK 211 may also be deployed in other locations within the navigation domain and the intelligent driving domain (e.g., outside the respective control units).

[0030] Figure 2 This illustration shows a schematic diagram of inter-domain collaborative operation between the navigation domain and the intelligent driving domain using a map service system, according to an exemplary embodiment of this application.

[0031] like Figure 2 As shown, the navigation domain control unit 10 interacts with the first cloud service platform 51 via the navigation SDK 111 to request navigation route planning. The first cloud service platform 51 responds to this request, for example, planning multiple navigation routes 71, 72, and 73 (the three shown in the figure). The navigation domain control unit 10 selects one of these as the main route (e.g., route 71) and performs navigation guidance along that route 71. Simultaneously, the navigation domain control unit 10 generates path coordination information 201 corresponding to the main route 71, which characterizes the overall driving direction of the main route 71. The navigation domain control unit 10 transmits the path coordination information 201 to the intelligent driving domain control unit 20 via the vehicle network 31 to synchronize navigation driving intentions.

[0032] Unlike high-precision map features and map service data for intelligent driving functions that require frequent inter-domain transmission in traditional architectures, route coordination information 201 typically involves a smaller data volume. For example, the specific form of route coordination information 201 may include: - A sequence of waypoints for the navigation route (a series of latitude and longitude coordinates); - Navigation guidance command sequences (such as "Turn right in 300 meters" command sequences); and / or - A sequence of local road segment identifiers for the navigation route (e.g., Link ID1, Link ID2, etc.).

[0033] After receiving the route coordination information 201, the intelligent driving domain control unit 20 can determine the overall navigation route that the vehicle should follow and execute the second map service operation for intelligent driving functions based on this. Specifically, based on the received route coordination information 201, the intelligent driving domain control unit 20 obtains a lane-level reconstructed route 81 that matches the navigation route 71 with the help of the intelligent driving SDK 211, and uses the lane-level reconstructed route 81 for intelligent driving functions.

[0034] In the context of this application, lane-level reconstructed route 81 refers to structured path data generated based on high-precision map data, containing lane-level detailed information, including at least lane-level geometric information, lane-level topological connection information, and attribute information. Lane-level reconstructed route 81 can be, for example, electronic horizon data or structured data conforming to a vehicle-customized protocol.

[0035] Based on lane-level reconstruction route 81, the intelligent driving SDK 211 can continuously broadcast map service data such as the curvature, slope, and speed limit of the road ahead to functional modules in the intelligent driving domain, such as adaptive cruise control (ACC) and lane keeping assist (LKA), so that each functional module can respond in advance based on the road information ahead.

[0036] In one embodiment, the navigation domain control unit 10 transmits route coordination information 201 to the intelligent driving domain control unit 20 only when preset triggering conditions are met. These preset triggering conditions include, for example, the completion of navigation route generation (e.g., after selecting the main route 71 from multiple alternative routes) or changes to the navigation route (e.g., the user manually adjusts the route or the route is automatically switched due to real-time traffic conditions, such as switching from route 71 to alternative route 72). In this way, periodic, high-frequency cross-domain synchronization of large amounts of data is avoided, significantly reducing the communication load on the vehicle network 31.

[0037] In this embodiment, some technical tasks in the second map service operation are performed by the cloud service platform 52. For example, the generation of lane-level reconstructed routes 81 is completed with the help of the cloud service platform 52. By centralizing route matching and reconstruction logic in the cloud, the computing load on the vehicle can be reduced and the system operating efficiency can be improved. Specifically, the intelligent driving domain control unit 20 can report route coordination information 201 to the cloud service platform 52 with the help of the intelligent driving SDK 211, and receive the lane-level reconstructed routes 81 generated by the cloud service platform 52 based on the route coordination information 201. In other embodiments not shown, the lane-level reconstructed routes 81 can also be generated locally on the vehicle.

[0038] In one embodiment, the intelligent driving domain control unit 20 does not periodically and frequently report route coordination information 201, but can be configured according to the intelligent driving function requirements to report only when necessary. For example, the intelligent driving domain control unit 20 uploads route coordination information 201 to the cloud service platform 52 through the intelligent driving SDK 211 when any of the following conditions are met: - Received route coordination information 201 from navigation domain control unit 10; - Navigation route has changed; - The high-precision map version currently used by the Intelligent Driving Domain has been updated; and / or - The cloud service platform returned a route consistency check failure message.

[0039] The cloud service platform 52 can periodically or as needed distribute lane-level reconfiguration routes 81 in segments according to system configuration or vehicle location to further optimize communication load.

[0040] In the cloud service platform 52, based on the route coordination information 201 received from the intelligent driving domain control unit 20, a lane-level reconstructed route 81 can be generated in the following manner: First, based on the route coordination information 201, the path point sequence corresponding to the navigation route 71 is matched to the high-precision map to determine the road segments and / or lane segments covered by the path point sequence. For example, a series of GPS coordinate points corresponding to the navigation route are mapped onto the high-precision map to determine the overall road segments that the vehicle should pass through.

[0041] Then, while maintaining the overall driving direction of the route, lane-level geometric information, lane-level topological connection information, and attribute information are added to the matched road segments and / or lane segments to generate a lane-level reconstructed route 81 directly oriented towards intelligent driving function control. Specifically, the supplemented lane-level reconstructed route 81 includes at least the preceding and following connections between lanes (such as the end point of lane A connecting the start point of lane B, or lane A branching to connect lane B and lane C), as well as traffic rules and constraints (such as turning restrictions, traffic permissions, time restrictions, and vehicle type restrictions).

[0042] Next, the generated lane-level reconstructed route 81 is optimized, including correcting abnormal and / or drivable road segments, and / or replacing or adjusting road segments that do not meet the intelligent driving constraints. For example, if a road segment exceeds the intelligent driving operation design domain (ODD), the cloud service platform 52 can replan a detour route to replace the original road segment.

[0043] Finally, the optimized lane-level reconstruction route 81 is sent to the intelligent driving domain control unit 20.

[0044] In one embodiment, when the navigation route followed by the vehicle changes, the navigation domain control unit 10 regenerates updated route coordination information (e.g., corresponding to alternative route 72, or multiple routes) and transmits it to the intelligent driving domain control unit 20. Accordingly, the intelligent driving domain control unit 20 reports the changed route coordination information to the cloud service platform 52, which then generates and maintains corresponding lane-level reconstructed routes for each route and assigns a unique identifier (e.g., Path ID1, Path ID2, Path ID3) to each lane-level reconstructed route.

[0045] The cloud service platform 52 also records the corresponding version number, timestamp information, generation source, update time, and adapted high-precision map version information for each lane-level reconstructed route. Through the above route version management mechanism, the cloud service platform, as the authoritative source of high-precision map data, can provide clear version information for the lane-level reconstructed routes acquired and used by the intelligent driving domain.

[0046] In one embodiment, the cloud service platform 52 is also configured to perform at least one of the following verifications: - Verify the structural integrity, continuity, and legality of the route coordination information 201. For example, check whether the waypoint sequence of the navigation route is discontinuous, whether key road segments are missing, and whether it covers non-compliant road segments (such as restricted road segments), etc. - Verify whether the high-precision map currently used by the intelligent driving domain control unit 20 and the high-precision map adapted to the lane-level reconstructed route 81 meet the compatibility requirements. For example, check whether the two versions are consistent; if the version of the map currently used by the intelligent driving domain is lower than the version adapted to the reconstructed route, causing the vehicle to be unable to properly read or parse the reconstructed route sent from the cloud, then trigger the vehicle's high-precision map update process; - Verify the feasibility of lane-level reconstructed route 81 in the high-definition map, including whether there are any breaks, significant offsets, or inconsistencies with the map topology. For example, remap the generated lane-level reconstructed route 81 to the high-definition map to verify its feasibility; if the high-definition map version is the same but the reconstructed route does not match the high-definition map topology (for example, the reconstructed route requires a left turn at an intersection, but the attribute information stored in the high-definition map shows that left turns are prohibited at that intersection), then trigger the route reconstruction process.

[0047] Accordingly, the cloud service platform 52 is also configured to mark the lane-level reconstructed route 81 as a valid route and send it to the intelligent driving domain control unit 20 only when all the performed checks pass.

[0048] Figure 3 A schematic diagram illustrating inter-domain collaborative operation between the navigation domain and the intelligent driving domain using a map service system, according to another exemplary embodiment of this application, is shown.

[0049] exist Figure 3 In the illustrated embodiment, with Figure 2 The difference is that the map service system 1 includes a single cloud service platform 51, and the navigation SDK 111 and intelligent driving SDK of the vehicle communication device 2 interact with the same cloud service platform 51 to provide corresponding map service operations.

[0050] Although they share the same cloud service platform 51, the navigation SDK 111 and the intelligent driving SDK 211 communicate and interact with the cloud independently, and can be based on map data sources of different granularities. That is, the cloud service platform 51 can simultaneously maintain map data of multiple granularities, different data formats and versions (such as standard precision map data and high precision map data).

[0051] In this architecture, when the navigation domain control unit 10 and the intelligent driving domain control unit 20 synchronize their navigation driving intentions, the lightweight path coordination information 201 transmitted between the domains can be, for example, a global identifier of the navigation route (such as a Path ID), without needing to include a complete sequence of path points.

[0052] like Figure 3As shown, firstly, the navigation domain control unit 100 interacts with the cloud service platform 51 via the navigation SDK 111 to plan navigation routes. In response to requests from the navigation SDK 111, the cloud service platform 51 generates multiple navigation routes (e.g., three routes, namely routes 71, 72, and 73) and creates global identifiers 61, 62, and 63 (such as Path ID1, Path ID2, and Path ID3) for each route, maintaining and storing them in the cloud. For example, a route database 510 can be maintained in the cloud, storing all planned navigation routes and their corresponding global identifiers. These routes can be multiple alternative routes generated in the same planning process for the user to choose from, or routes generated at different times or for different destinations, supporting users to replan or switch routes mid-journey.

[0053] The cloud service platform 51 sends the planned navigation routes 71, 72, and 73, along with their corresponding global identifiers 61, 62, and 63, to the navigation domain control unit 10 via the navigation SDK 111. The navigation domain control unit 10 selects a navigation route (e.g., the main route) for vehicle navigation guidance and transmits the global identifier 61 of the navigation route 71 to the intelligent driving domain control unit 20 via the in-vehicle network 31.

[0054] The intelligent driving domain control unit 20, using the intelligent driving SDK 211, reports the received global identifier 61 to the cloud service platform 51. Based on the global identifier 61 reported by the vehicle, the cloud service platform 51 can directly retrieve the corresponding navigation route 71 from its maintained route database 510, without needing to receive the complete path point sequence used to anchor the navigation route from the vehicle. Subsequently, the cloud service platform 51 matches the navigation route 71 to a high-precision map, supplements lane-level semantic details, and follows... Figure 2 The process generates a corresponding lane-level reconstruction route 81, and finally the generated lane-level reconstruction route 81 is sent to the Intelligent Driving SDK 211.

[0055] In this embodiment, since navigation routes 71, 72, and 73 are maintained uniformly in the cloud, the global identifier 61 of the navigation route can be used instead of its complete path point sequence as route coordination information 201, which further reduces the cross-domain communication load and realizes a more efficient coordination mechanism.

[0056] Figure 4 A flowchart of an exemplary embodiment of a vehicle communication method according to this application is shown.

[0057] In step S1, the navigation domain control unit performs a first map service operation for navigation functions using the navigation SDK, and generates route coordination information for synchronizing navigation driving intentions; In step S2, the navigation domain control unit transmits the route coordination information to the intelligent driving domain control unit via the vehicle network. In step S3, the intelligent driving domain control unit, with the help of the intelligent driving SDK, performs a second map service operation for intelligent driving functions based on the received route coordination information and in accordance with the navigation driving intention.

[0058] It should be understood that the specific forms of the first map service operation and the second map service operation and the route coordination mechanism described in this embodiment are relatively brief. The relevant technical details are fully explained in the foregoing system embodiments and can be directly referred to in the description of the corresponding parts, and will not be repeated here.

[0059] Although specific embodiments of this application are described in detail herein, they are given for illustrative purposes only and should not be construed as limiting the scope of this application. Various substitutions, modifications, and alterations can be conceived without departing from the spirit and scope of this application.

Claims

1. A vehicle-mounted communication device (2), comprising: The navigation domain control unit (10) is configured to perform a first map service operation for navigation functions using the navigation SDK and transmit route coordination information (201) for synchronizing navigation driving intentions to the intelligent driving domain control unit (20) via the vehicle network (31). as well as The intelligent driving domain control unit (20) is configured to perform a second map service operation for intelligent driving functions using the intelligent driving SDK, and to match the performed second map service operation with the navigation driving intention based on the received route coordination information (201).

2. The vehicle-mounted communication device (2) according to claim 1, wherein, The first map service operation includes: navigation route (71) planning, point of interest search, navigation guidance, navigation map data acquisition and / or navigation map data display; and / or The second map service operation includes: lane-level semantic information generation, most likely path calculation, lane-level reconstructed route (81) generation and broadcasting, lane-level geometric data broadcasting, lane-level topology data broadcasting, static road facility data broadcasting and / or dynamic event data broadcasting.

3. The vehicle-mounted communication device (2) according to claim 1 or 2, wherein, The navigation SDK and intelligent driving SDK provide corresponding map service operations based on different map data sources; and / or The navigation SDK provides the first map service operation based on a standard precision map data source, and the intelligent driving SDK provides the second map service operation based on a high precision map data source.

4. The vehicle-mounted communication device (2) according to any one of claims 1 to 3, wherein, The navigation domain control unit (10) is also configured to transmit the route coordination information (201) to the intelligent driving domain control unit (20) only when a preset triggering condition is met. The preset triggering conditions include: the navigation route (71) has been generated, and / or the navigation route (71) has been changed; The route coordination information (201) includes: a sequence of waypoints of the navigation route (71), a sequence of navigation guidance instructions, and / or a sequence of global identifiers and / or local road segment identifiers of the navigation route (71).

5. The vehicle-mounted communication device (2) according to any one of claims 1 to 4, wherein, The route coordination information (201) is used to characterize the navigation route (71), and the intelligent driving domain control unit (20) is also configured to obtain a lane-level reconstructed route (81) matching the navigation route (71) based on the route coordination information (201) and with the help of the intelligent driving SDK, and provide the lane-level reconstructed route (81) for intelligent driving functions; Specifically, the intelligent driving domain control unit (20) is also configured to report route coordination information (201) to the cloud service platform (51) using the intelligent driving SDK, and to receive lane-level reconstructed routes (81) generated by the cloud service platform (51) based on the route coordination information (201).

6. A map service system (1), comprising: The cloud service platform (51) is configured to respond to the route coordination information (201) reported by the intelligent driving SDK, execute at least part of the calculation tasks in the second map service operation, and return the execution results of the at least part of the calculation tasks to the intelligent driving SDK; as well as The vehicle-mounted communication device (2) according to any one of claims 1 to 5.

7. The map service system (1) according to claim 6, wherein, The at least part of the computational task includes generating lane-level reconstructed routes (81) based on route coordination information (201), wherein: Based on the route coordination information (201), the corresponding road segment and / or lane segment are matched in the high-precision map; For the matched road segments and / or lane segments, supplement lane-level geometric information, lane-level topological connection relationship information and attribute information to generate the lane-level reconstructed route (81). The non-drivable sections in the lane-level reconstructed route (81) are modified, and / or sections that do not meet the intelligent driving constraints are replaced or adjusted.

8. The map service system (1) according to claim 6 or 7, wherein, The cloud service platform (51) is also configured as follows: - Verify the structural integrity, continuity, and / or legality of the route coordination information (201); - Verify whether the high-precision map currently used by the intelligent driving domain control unit (20) and the high-precision map adapted to the lane-level reconstructed route (81) meet the compatibility conditions; and / or - Verify the feasibility of the lane-level reconstructed route (81) in the high-precision map; The cloud service platform (51) is also configured to mark the lane-level reconstructed route (81) as a valid route and send it to the intelligent driving domain control unit (20) only when the above verification passes.

9. The map service system (1) according to any one of claims 6 to 8, wherein, The cloud service platform (51) is also configured as follows: Assign a unique identifier to the lane-level reconstructed route (81); For lane-level reconstructed routes (81), the corresponding route version number, timestamp information, generation source, update time, and the adapted high-precision map version information are recorded.

10. A vehicle-mounted communication method, performed by means of a vehicle-mounted communication device (2) according to any one of claims 1 to 5, the vehicle-mounted communication method comprising: The navigation domain control unit (10) performs a first map service operation for navigation functions using the navigation SDK and generates route coordination information (201) for synchronizing navigation driving intentions. The navigation domain control unit (10) transmits the route coordination information (201) to the intelligent driving domain control unit (20) via the vehicle network (31). as well as The intelligent driving domain control unit (20) uses the intelligent driving SDK to perform a second map service operation for intelligent driving functions based on the received route coordination information (201) and in accordance with the navigation driving intention.

Images