Automatic driving navigation method and system for mobile terminal

Abstract

The embodiment of the invention provides an automatic driving navigation method and system for a mobile terminal. The method comprises the following steps: acquiring an initialization parameter; registering an automatic driving navigation component; initializing an automatic driving navigation module through an automatic driving navigation component based on the initialization parameters; receiving real-time navigation information sent by the server; and displaying an automatic driving navigation interface based on the real-time navigation information.

Description

Technical Field

[0001] The present invention relates to the field of computers, and more particularly to an autonomous driving navigation method and system for a mobile terminal. Background Art

[0002] With the development of autonomous driving technology, the use of unmanned autonomous driving technology is becoming more and more common. When users want to view navigation information such as real-time traffic conditions, they can do so through the unmanned navigation application installed on the onboard central control of the unmanned vehicle. However, since the onboard central control is a fixed device pre-installed in advance, and providing navigation display is not a necessary function for unmanned vehicles, users hope to be able to view the navigation information of unmanned vehicles through their own mobile terminals (e.g., mobile phones, etc.). For reasons such as data security and hardware solidification, unmanned vehicle developers usually do not open their autonomous driving modules to external application developers, that is, they do not support users to directly view the onboard central control identification data. For internal application developers, since the autonomous driving module is a native module, internal application developers need to access the software development kit (SDK) for secondary development. It needs to be developed for multiple mobile and desktop system platforms (e.g., iOS, Android, Hongmeng, Windows, etc.), which is difficult to develop, has a long cycle, and consumes a lot of resources.

[0003] Therefore, it is desirable to provide an autonomous driving navigation method and system for a mobile terminal, so as to conveniently provide unmanned driving navigation information to users on the mobile terminal. Summary of the invention

[0004] One of the embodiments of this specification provides an automatic driving navigation method for a mobile terminal. The method includes: obtaining initialization parameters; registering an automatic driving navigation component; initializing an automatic driving navigation module through the automatic driving navigation component based on the initialization parameters; receiving real-time navigation information sent by a server; and displaying an automatic driving navigation interface based on the real-time navigation information.

[0005] In some embodiments, the autonomous driving navigation component includes a preset identifier, and the autonomous driving navigation component can be mapped to the autonomous driving navigation module based on the preset identifier.

[0006] In some embodiments, the autonomous driving navigation module can establish a data connection with the server based on the initialization parameters.

[0007] In some embodiments, based on the real-time navigation information, the autonomous driving navigation module can be controlled to render the autonomous driving navigation interface; based on at least part of the real-time navigation information, additional information can be displayed on the autonomous driving navigation interface through the autonomous driving navigation component.

[0008] In some embodiments, controlling the autonomous driving navigation module to render the autonomous driving navigation interface may be performed through same-layer rendering.

[0009] In some embodiments, the autonomous driving navigation component can be implemented as a mini-program component.

[0010] In some embodiments, the autonomous driving navigation module can be implemented in a native manner.

[0011] In some embodiments, the autonomous driving navigation component and the autonomous driving navigation module may be included in a mini-program engine.

[0012] In some embodiments, the initialization parameters may include connection parameters and setup parameters.

[0013] One of the embodiments of the present specification provides an autonomous driving navigation system for a mobile terminal, comprising a parameter acquisition module, a navigation registration module, a navigation initialization module, an information receiving module and a navigation display module; the parameter acquisition module is used to acquire initialization parameters; the navigation registration module is used to register an autonomous driving navigation component; the navigation initialization module is used to initialize the autonomous driving navigation module through the autonomous driving navigation component based on the initialization parameters; the information receiving module is used to receive real-time navigation information sent by a server; the navigation display module is used to display an autonomous driving navigation interface based on the real-time navigation information.

[0014] One of the embodiments of the present specification provides a computer-readable storage medium, which stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the autonomous driving navigation method for a mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0016] Figure 1 is a schematic diagram of an application scenario of an automatic driving navigation system for a mobile terminal according to some embodiments of this specification;

[0017] Figure 2is a schematic diagram of an automatic driving navigation system for a mobile terminal according to some embodiments of this specification;

[0018] Figure 3 is an exemplary flow chart of an automatic driving navigation method for a mobile terminal according to some embodiments of this specification;

[0019] Figure 4 is a schematic diagram of an automatic driving navigation method for a mobile terminal according to some embodiments of this specification;

[0020] Figure 5 is a schematic diagram of registering an autonomous driving navigation component according to some embodiments of this specification;

[0021] Figure 6 is a schematic diagram of an autonomous driving navigation interface according to some embodiments of this specification;

[0022] Figure 7 is a schematic diagram of data callback of an autonomous driving navigation component according to some embodiments of this specification;

[0023] Figure 8 It is a schematic diagram of an automatic driving navigation method for a mobile terminal according to some embodiments of this specification. DETAILED DESCRIPTION

[0024] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0025] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0026] As shown in this specification and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0027] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed precisely in order. Instead, the steps may be processed in reverse order or simultaneously. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0028] Figure 1 It is a schematic diagram of an application scenario of an autonomous driving navigation system for a mobile terminal according to some embodiments of this specification.

[0029] In this specification, the automatic driving navigation system 100 is referred to as the system 100. Figure 1 As shown, in some embodiments, the system 100 may include a server 110 , a mobile terminal 120 , a storage device 130 , and a network 140 .

[0030] The server 110 can obtain navigation data and information of the autonomous driving vehicle. In some embodiments, the server 110 may include a vehicle central control of the autonomous driving vehicle, which can obtain navigation data (e.g., vehicle location, vehicle driving status, surrounding environment data, etc.) through various methods such as on-board sensors, generate real-time navigation information based on the navigation data, and send the autonomous driving real-time navigation information to the mobile terminal 120. In some embodiments, the server 110 may include a backend server, and the vehicle central control can send the autonomous driving real-time navigation information to the backend server, which is then sent to the mobile terminal 120 by the backend server. The backend server may include a backend server of a travel platform that provides online travel services through autonomous driving vehicles, a backend server of a developer of autonomous driving vehicles, etc.

[0031] The mobile terminal 120 can be used by the user to view the autonomous driving navigation information. In some embodiments, the mobile terminal 120 executes the autonomous driving navigation method for the mobile terminal as shown in some embodiments of this specification to synchronously display the real-time navigation information of the autonomous driving vehicle to the user. In some embodiments, the mobile terminal 120 may include a mini-program engine (also referred to as a mini-program engine SDK), and the mobile terminal 120 may display the autonomous driving navigation interface through the autonomous driving navigation module and the autonomous driving navigation component in the mini-program engine, and display the real-time navigation information of the autonomous driving vehicle thereon. In some embodiments, the mobile terminal 120 may be one of a mobile device 120-1, a tablet computer 120-2, a laptop computer 120-3, etc., or any combination thereof.

[0032] In some embodiments, the server 110 and / or the mobile terminal 120 may include one or more sub-processing devices (e.g., a single-core processing device or a multi-core multi-core processing device). As an example only, the server 110 and / or the mobile terminal 120 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic circuit (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), a microprocessor, etc., or any combination thereof.

[0033] The storage device 130 can store data or information generated by other devices. In some embodiments, the storage device 130 can store data and / or information collected by the vehicle central control of the autonomous driving vehicle, such as navigation information such as vehicle location, vehicle driving status, and surrounding environment data. In some embodiments, the storage device 130 can store other data and information, such as autonomous driving real-time navigation information, mini-program engine code, etc. The storage device 130 may include one or more storage components, each of which may be an independent device or part of another device. The storage device may be local or implemented through the cloud.

[0034] The network 140 can connect the components of the system and / or connect the system with external resources. The network 140 enables communication between the components and with other parts outside the system to facilitate the exchange of data and / or information. In some embodiments, one or more components in the system 100 (e.g., the server 110, the mobile terminal 120, the storage device 130) can send data and / or information to other components via the network 140. In some embodiments, the network 140 can be any one or more of a wired network or a wireless network.

[0035] It should be noted that the above description is provided for illustrative purposes only and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various changes and modifications can be made under the guidance of the contents of this specification. The features, structures, methods and other features of the exemplary embodiments described in this specification can be combined in various ways to obtain additional and / or alternative exemplary embodiments. For example, the backend server in the service end 110 can be based on a cloud computing platform, such as a public cloud, a private cloud, a community and a hybrid cloud. However, these changes and modifications will not deviate from the scope of this specification.

[0036] Figure 2 It is a schematic diagram of an autonomous driving navigation system for a mobile terminal according to some embodiments of the present specification.

[0037] like Figure 2 As shown, the autonomous driving navigation system 200 includes a parameter acquisition module 210, a navigation registration module 220, a navigation initialization module 230, an information receiving module 240 and a navigation display module 250. In some embodiments, each module of the autonomous driving navigation system 200 can be implemented by the mobile terminal 120.

[0038] In some embodiments, the parameter acquisition module 210 may be used to acquire initialization parameters.

[0039] In some embodiments, the initialization parameters may include connection parameters and setup parameters, among others.

[0040] In some embodiments, the navigation registration module 220 can be used to register the autonomous driving navigation component.

[0041] In some embodiments, the autonomous driving navigation component can be implemented as a mini-program component.

[0042] In some embodiments, the autopilot navigation component may include a preset identifier. The navigation registration module 220 may map the autopilot navigation component to the autopilot navigation module based on the preset identifier.

[0043] In some embodiments, the autonomous driving navigation module can be implemented in a native manner.

[0044] In some embodiments, the autonomous driving navigation component and the autonomous driving navigation module may be included in the mini-program engine.

[0045] In some embodiments, the navigation initialization module 230 may be configured to initialize the autonomous driving navigation module through the autonomous driving navigation component based on initialization parameters.

[0046] In some embodiments, the navigation initialization module 230 may enable the autonomous driving navigation module to establish a data connection with a server (eg, server 110 ) based on initialization parameters.

[0047] In some embodiments, the information receiving module 240 may be used to receive real-time navigation information sent by a server.

[0048] In some embodiments, the navigation display module 250 can be used to display an autonomous driving navigation interface based on real-time navigation information.

[0049] In some embodiments, the navigation display module 250 can control the autonomous driving navigation module to render the autonomous driving navigation interface based on real-time navigation information; and display additional information on the autonomous driving navigation interface through the autonomous driving navigation component based on at least part of the real-time navigation information.

[0050] In some embodiments, the navigation display module 250 can control the autonomous driving navigation module to render the autonomous driving navigation interface through same-layer rendering.

[0051] Figure 3 This is an exemplary flowchart of an autonomous driving navigation method for a mobile terminal according to some embodiments of this specification.

[0052] like Figure 3 As shown, the process 300 includes the following steps. In some embodiments, the process 300 may be executed by the mobile terminal 120 .

[0053] When using an autonomous driving vehicle for travel, users (e.g., passengers, vehicle testers, etc.) often want to view the real-time navigation information of the autonomous driving vehicle on their mobile terminals (e.g., mobile phones, tablet computers, laptops, etc.), but this is difficult to achieve due to various reasons such as hardware solidification, data security, and software development difficulty. Taking data security as an example, the developer and operator of the driverless vehicle usually do not want to open the hardware / software modules and data of the driverless vehicle to a third party to avoid malicious attacks and improper use. In addition, for commercial purposes, the developer and operator of the driverless vehicle do not want a third party to master this information and data. In some embodiments, the automatic navigation page can be displayed in the form of a mini program to show real-time navigation information to the user. In some embodiments, the mobile terminal 120 can display the navigation information using the autonomous driving navigation component in the mini program by executing the steps shown in process 300, wherein the autonomous driving navigation component is connected to the vehicle central control of the autonomous driving vehicle through the autonomous driving navigation module and obtains navigation information through it.

[0054] Step S310 , obtaining initialization parameters. In some embodiments, step S310 may be performed by the parameter obtaining module 210 .

[0055] Initialization parameters refer to parameters used to initialize the autonomous driving navigation component and the autonomous driving navigation module, such as parameters used to establish a network connection, parameters used for configuration, etc. In some embodiments, the initialization parameters may include connection parameters and setting parameters, etc. Among them, the connection parameters may include the type of network connected, the connection source, etc.; the setting parameters may include whether to enable voice, navigation style (e.g., light, dark), callback function, network status notification function, etc.

[0056] In some embodiments, the mobile terminal 120 may obtain the initialization parameters in a variety of ways.

[0057] In some embodiments, the mobile terminal 120 can manually or automatically obtain connection parameters through a user (e.g., a passenger), wherein the user (e.g., user 810) may include passengers using travel services, developers and testers of autonomous vehicles, etc. For example, a user can manually scan the logo (e.g., QR code, etc.) on the autonomous vehicle to obtain parameters such as deviceId or the IP address of the vehicle-mounted central control service. When the deviceId is obtained, it can be determined that the connected network type is Bluetooth, etc.; when the IP address is obtained, if it is an intranet address (e.g., an address of the type 192.168.XX), the connected network type is determined to be a local area network (rpc link), and if it is a public network address (e.g., an address of the type 128.11.XX), the connected network type is determined to be a public network (tcp link). For another example, when a user uses the autonomous driving service provided by the travel platform to travel, he places an order on the travel platform application program, and after opening the door and getting on the car, the backend server (e.g., server 820) of the travel platform (i.e., the business party) can automatically send the initialization parameters such as the tcp link of the current vehicle-mounted central control to the travel platform application used by the user. In this specification, the business party refers to the provider of autonomous driving vehicles, which may include travel platforms that provide travel services, developers of autonomous driving vehicles, etc.

[0058] In some embodiments, the mobile terminal 120 may use the preset value (i.e., default value) of the setting parameter as its value. For example, when the user does not actively set it, whether to enable voice can be set to the default value True, i.e., enable voice; and the navigation style can be set to the default value light, i.e., the conventional light mode.

[0059] In some embodiments, the mobile terminal 120 can also obtain initialization parameters through other means, for example, confirming the user's identity through biometric identification methods such as fingerprint recognition and face recognition integrated in the vehicle's central control, and then automatically issuing initialization parameters based on the user's identity.

[0060] Step S320 , registering the autonomous driving navigation component. In some embodiments, step S320 may be performed by the navigation registration module 220 .

[0061] The autonomous driving navigation component is a component for displaying navigation information of an autonomous driving vehicle, for example, the autonomous driving navigation component 830. Navigation information may include various information, for example, displaying the vehicle position, vehicle speed, vehicle direction, pedestrians around the vehicle, motor vehicles around the vehicle, non-motor vehicles around the vehicle, and traffic light status. In some embodiments, the navigation information may include real-time navigation information and historical navigation information, and the user may view real-time navigation information and / or historical navigation information through the autonomous driving navigation component (for example, the autonomous driving navigation component 830). For example, a passenger of an autonomous driving vehicle can understand the current travel status by viewing real-time navigation information. For another example, the developer of an autonomous driving vehicle can determine whether the operation of the autonomous driving vehicle is normal by viewing historical navigation information.

[0062] In some embodiments, the autonomous driving navigation component can be implemented in the form of a mini-program component, that is, the autonomous driving navigation component can be part of a mini-program, and the mini-program can run in an application on a travel platform (for example, applications on various mobile and / or desktop system platforms such as iOS, Android, Hongmeng, Windows, etc.).

[0063] In some embodiments, the autonomous driving navigation component may include multiple attributes of multiple types. Among them, the attribute types of the autonomous driving navigation component may include initialization attributes, state attributes, etc. The initialization attributes are used to initialize the autonomous driving navigation component and may correspond to initialization parameters, such as connection attributes, setting attributes, etc. The state attributes may be used to display relevant information of the navigation status, such as network status attributes, driving status attributes, etc.

[0064] In some embodiments, the initialization attributes may include attributes as shown in Table 1. Table 1 Among them, the attributes mode and src are connection attributes, and the attributes enable-sound, navigation-style, bindstatechange, and bindnetstatus are setting attributes. They correspond one-to-one to the parameters in the initialization parameters. The attribute mode is the type of the connected network, the attribute src is the connection source, the attribute enable-sound is whether to enable voice, the attribute navigation-style is the navigation style, the attribute bindstatechange is the callback function, and the attribute bindnetstatus is the network status notification function; type indicates the type of the attribute value, string indicates that the value is a string, boolean indicates that the value is a Boolean value, and function indicates that the value is a function; default value indicates the preset value of the attribute; description indicates additional description of the attribute. For example, the description of the attributes mode, src, and navigation-style includes a description of the attribute value. For another example, the description of the attributes enable-sound and navigation-style includes a description of the attribute function. For another example, the description of the attributes bindstatechange and bindnetstatus includes a description of the attribute trigger condition.

[0065] In some embodiments, the attributes included in the state attributes may be as shown in Table 2 and Table 3, wherein Table 2 may represent network state attributes, and Table 3 may represent driving state attributes. Table 2 property type illustrate delay number Network latency state string Link Status … As shown in Table 2, network status attributes may include dealy (network delay), state (link status), etc.; the value type of the attribute delay is number (numeric type), and the value type of the attribute state is string (string type); the descriptions of the attributes delay and state include descriptions of their respective functions. Table 3 As shown in Table 3, driving status attributes may include people (number of pedestrians), motors (number of motor vehicles), vehicles (number of non-motor vehicles), trafficlight (traffic light status), driving (driving status), lane (lane), etc.; the value type of the attributes people, motors and vehicles is number (numeric type), and the value type of the attributes trafficlight, driving and lane is string (string type); the description of the attributes people, motors and vehicles includes a description of their respective functions, and the description of the attributes trafficlight, driving and lane includes a description of their respective functions and possible values.

[0066] The autonomous driving navigation module is a module for connecting to the vehicle central control of the autonomous driving vehicle to obtain navigation information, for example, the autonomous driving navigation module 840. In some embodiments, the autonomous driving navigation module can be implemented in a native manner, that is, the autonomous driving navigation module can include a native module. In some embodiments, the autonomous driving navigation module can include multiple modules developed separately for different system platforms, for example, an autonomous driving navigation module for an iOS system, an autonomous driving navigation module for an Android system, an autonomous driving navigation module for a Hongmeng system, an autonomous driving navigation module for a Windows system, etc.

[0067] In some embodiments, the autonomous driving navigation module can convert the road condition identification data returned by the vehicle central control hardware of the autonomous driving vehicle into 2D and / or 3D projection and render it to the page, which is then drawn by the 2D and / or 3D engine and added to the native view layer.

[0068] In some embodiments, the autonomous driving navigation component and the autonomous driving navigation module may be included in a mini-program engine. The mini-program engine is software used to support the mini-program to run in native applications (e.g., various client-side platform applications, etc.). Native applications refer to applications that can run independently. Mini-programs refer to applications that need to run in an application container and cannot run independently from the container.

[0069] like Figure 4As shown, in some embodiments, the autonomous driving navigation component 420 and the autonomous driving navigation module 430 can be built into the mini-program engine 410, and the vehicle-mounted central control 440 and the autonomous driving navigation component 420 are connected through the autonomous driving navigation module 430. Among them, the autonomous driving navigation component 420 is a mini-program component, which can be provided by the mini-program engine developer; the autonomous driving navigation module 430 is a native module, which can be provided by the autonomous driving vehicle software developer; the vehicle-mounted central control 440 is the vehicle-mounted central control of the autonomous driving vehicle. In some embodiments, the vehicle-mounted central control 440 can send real-time and / or navigation information to the autonomous driving navigation module 430, and the autonomous driving navigation module 430 performs rendering and displays it in the autonomous driving navigation component 420. In some embodiments, the container of the mini-program (for example, platform applications such as taxi, shopping, and finance) can integrate the mini-program engine 410, and the container starts the mini-program through the mini-program engine 410, and the mini-program can use the autonomous driving navigation component 420 to display the automatic navigation page.

[0070] In some embodiments, the autonomous driving navigation component may include a preset identifier, wherein the preset identifier may include any non-empty string, for example, id_robotaxi, id_autonavrobot, etc. In some embodiments, the mobile terminal 120 may register the autonomous driving navigation component in the mini-program according to the preset identifier, that is, map the autonomous driving navigation component to the autonomous driving navigation module according to the preset identifier. For example, a built-in component named robotaxi (i.e., the autonomous driving navigation component) may be pre-registered in the basic library of the mini-program engine, and its identifier may be set to id_robotaxi, and a mapping between the autonomous driving navigation module and the mini-program component with the identifier id_robotaxi may be established, so that the autonomous driving navigation module may communicate with the robotaxi built-in component through a bridge mode.

[0071] Step S330, based on the initialization parameters, initialize the autonomous driving navigation module through the autonomous driving navigation component. In some embodiments, step S330 can be performed by the navigation initialization module 230.

[0072] In some embodiments, the mobile terminal 120 may initialize the autonomous driving navigation module through the autonomous driving navigation component according to the initialization parameters obtained in step S310. Specifically, the mobile terminal 120 may set the initialization properties of the autonomous driving navigation component according to the initialization parameters. Since the autonomous driving navigation component has established a mapping with the autonomous driving navigation module, the initialization parameters may be transparently transmitted to the autonomous driving navigation module in the form of initialization properties; the autonomous driving navigation module may complete the initialization according to the initialization parameters.

[0073] The service end refers to the provider of navigation information of the autonomous driving vehicle, for example, the vehicle's on-board central control, the backend server of the travel platform, etc. In some embodiments, the on-board central control may include the on-board central control of any vehicle, for example, the on-board central control of an autonomous driving vehicle, the on-board central control of an online car-hailing vehicle, the on-board central control of a self-use vehicle, etc. By obtaining the information sent by the vehicle's on-board central control (for example, navigation information, vehicle status information such as water temperature, etc.), the vehicle user (for example, the driver, the passenger) can better understand the use of the vehicle. In some embodiments, the autonomous driving navigation module can directly or indirectly obtain navigation information from the on-board central control of the autonomous driving vehicle through a network connection. For example, the autonomous driving navigation module can directly connect to the on-board central control through Bluetooth, a local area network, etc. to obtain navigation information. For another example, the backend server of the travel platform can obtain navigation information from the on-board central control through the network, and then send the navigation information to the automatic navigation driving module through the public network.

[0074] In some embodiments, the autonomous driving navigation module can establish a data connection with the server (e.g., server 110, vehicle-mounted central control 850) according to the initialization parameters. In some embodiments, after the initialization parameters are transparently transmitted to the autonomous driving navigation module in the form of initialization attributes, the mobile terminal 120 can establish a two-way data connection between the autonomous driving navigation module and the server according to the connection attributes in the initialization attributes.

[0075] In some embodiments, the mobile terminal 120 may also set the autonomous driving navigation module according to the setting attributes in the initialization attributes. For example, the autonomous driving navigation module may be set to play voice according to the attribute enable-sound. For another example, the display mode of the autonomous driving navigation module may be set according to the attribute navigation-style.

[0076] In some embodiments, after the autonomous driving navigation module completes initialization, the server may send information to the autonomous driving navigation module, wherein the information may include navigation information (e.g., real-time navigation information, etc.), vehicle status information (e.g., water temperature, engine speed, etc.), vehicle fault information, etc. In some embodiments, the autonomous driving navigation component may monitor data changes of the autonomous driving navigation module, such as changes in navigation information therein, by setting a callback function in a property (e.g., bindstatechange).

[0077] Figure 5 The figure shows an autonomous driving navigation component named robotaxi, and its properties can be shown in Table 1. Figure 5As shown, the attribute src value is "10.10.0.1:8080", indicating that the autonomous driving navigation module is connected to the server through the link address 10.10.0.1:8080; the attribute mode value is "rpc", indicating that the connection between the autonomous driving navigation module and the server is a local area network connection; the attribute enable-sound value is "true", indicating that the autonomous driving navigation module has voice turned on; the attribute navigation-style value is "light", indicating that the navigation style displayed by the autonomous driving navigation module is the usual light mode; the attribute bindstatechange value is "statechangeHandler", indicating that the autonomous driving navigation module returns data (for example, navigation information) to the autonomous driving navigation component through the function statechangeHandler.

[0078] Step S340 , receiving the real-time navigation information sent by the server. In some embodiments, step S340 may be executed by the information receiving module 240 .

[0079] In some embodiments, after a data connection is established between the automatic driving navigation module and the server, the mobile terminal 120 may receive information sent by the server through the automatic navigation module, such as navigation information. In some embodiments, the received information may include at least one of real-time navigation information, historical navigation information, etc. For example, the vehicle-mounted central control may send the acquired real-time traffic information as real-time navigation information to the automatic driving navigation module directly or indirectly (i.e., through a background server).

[0080] In some embodiments, the mobile terminal 120 may send the received information to the autonomous driving navigation component through a callback function or the like. Figure 5 The autonomous driving navigation component in can receive this information through the callback function statechangeHandler.

[0081] Step S350 , displaying the autonomous driving navigation interface based on the real-time navigation information. In some embodiments, step S350 may be performed by the navigation display module 250 .

[0082] In some embodiments, the mobile terminal 120 may display an autonomous driving navigation interface (e.g., autonomous driving navigation interface 600, autonomous driving navigation interface 860) in an autonomous driving navigation component based on the navigation information. The autonomous driving navigation interface may be used to display information to the user in various ways, such as navigation information and additional information. In some embodiments, the display method may include one or any combination of 2D / 3D graphics, text, voice, etc. In some embodiments, when the navigation information is real-time navigation information, the user can understand the autonomous driving status of the current autonomous driving vehicle through the real-time navigation information displayed on the autonomous driving navigation interface, such as the real-time position, real-time speed, and driving direction of the vehicle. In some embodiments, the autonomous driving navigation interface may also display other information, such as vehicle status information. By displaying the vehicle status information to the vehicle user, the vehicle user can understand the current operating status of the vehicle. The following is an example of navigation information being real-time navigation information.

[0083] In some embodiments, the mobile terminal 120 can control the autonomous driving navigation module to render the autonomous driving navigation interface based on the real-time navigation information.

[0084] In some embodiments, the mobile terminal 120 can control the autonomous driving navigation module to render the autonomous driving navigation interface through the same-layer rendering method. The autonomous driving navigation module is a native module, and is a native component when integrated in the mini-program. By using the same-layer rendering method, the native component can be rendered directly to the WebView level. At this time, the "native component layer" relative to the mini-program component no longer exists, and the native component has been directly mounted on the WebView node, so that the native component can control the rendering hierarchy relationship like the mini-program component. Therefore, the autonomous driving navigation module can complete the page rendering of the navigation display internally, and the navigation information data is closed in the autonomous driving navigation module. Except for the data transmitted to the autonomous driving navigation component through the callback function, no other data is leaked to the outside of the autonomous driving navigation module.

[0085] In some embodiments, the mobile terminal 120 may also display additional information on the autonomous driving navigation interface through the autonomous driving navigation component based on at least part of the real-time navigation information. The additional information may correspond to the driving state attribute in the autonomous driving navigation component attribute, for example, at least one of the number of pedestrians, the number of motor vehicles, the number of non-motor vehicles, the state of traffic lights, the driving state, and the lane. By displaying the additional information, the user can obtain more comprehensive navigation information, so as to better understand the current state of the autonomous driving vehicle.

[0086] In some embodiments, the mobile terminal 120 can display additional information by overlaying a built-in component of the mini-program on top of the page rendered by the autonomous driving navigation module, that is, the additional information is displayed as a built-in component of the mini-program component of the autonomous driving navigation component and integrated into the autonomous driving navigation interface.

[0087] like Figure 6 The figure shows an autonomous driving navigation interface 600, wherein the autonomous driving navigation interface 600 includes a display area 610 and a display area 620. The display area 610 is rendered by the autonomous driving navigation module through a same-layer rendering method, and is used to display graphical real-time navigation information, for example, real-time navigation information displayed in a 3D projection method. The display area 620 is located above the display area 610 and is used to display additional information, including mini-program built-in components 621, 622, and 623, which are respectively used to display the driving state attributes in the autonomous driving navigation component attributes: the number of pedestrians, the number of motor vehicles, and the number of non-motor vehicles.

[0088] In some embodiments, Figure 6 The autonomous driving navigation interface 600 in Figure 5 The corresponding autonomous driving navigation component named robotaxi in Figure 5 As shown in the figure, in the autonomous driving navigation component named robotaxi, its view, i.e., view, includes three components of class type item, corresponding to Figure 6 621, 622 and 623.

[0089] In some embodiments, the additional information can be obtained through the callback function properties in the autopilot navigation component properties, wherein the parameters of the callback function include the real-time navigation information returned by the autopilot navigation module. Figure 7 The callback function statechangeHandler shown can correspond to Figure 5 In the robotaxi autonomous driving navigation component, we can see that the real-time navigation information returned by parameter e includes people, motors, vehicles, trafficlight, driving, and lane, which correspond to the properties of the autonomous driving navigation component listed in Table 3. Figure 5 In the robotaxi autonomous driving navigation component shown in the figure, only people, motors, and vehicles in the real-time navigation information are used in its view. Figure 6 The three additional information shown in 621, 622 and 623 correspond to each other.

[0090] In some embodiments of the present specification, the navigation information of the autonomous driving vehicle is displayed in the mini-program by integrating the autonomous driving navigation module and the autonomous driving navigation component in the mini-program engine. Since the mini-program can be used without the need for user installation and downloading, and can be used on multiple system platforms (for example, iOS, Android, Hongmeng, Windows, etc.) after one-time development, and since its data is closed in the mini-program container (for example, platform applications such as taxi-hailing, shopping, and finance), data security is guaranteed, thereby greatly improving the development efficiency of navigation applications on mobile terminals and meeting user needs well.

[0091] Figure 8 It is a schematic diagram of an automatic driving navigation method for a mobile terminal according to some embodiments of this specification.

[0092] In some embodiments, the steps shown in process 800 may be performed to achieve Figure 3 The autonomous driving navigation method for a mobile terminal is shown.

[0093] Step S815, manually obtain initialization parameters and initialize.

[0094] In some embodiments, the user 810 may manually obtain initialization parameters and initialize the autonomous driving navigation component 830 and the autonomous driving navigation module 840 according to the initialization parameters. Initializing the autonomous driving navigation module 840 may be performed by initializing the autonomous driving navigation component 830. In some embodiments, the user 810 may include passengers using travel services, development and testing personnel of autonomous driving vehicles, and the like.

[0095] Step S825, sending initialization parameters and automatically initializing.

[0096] In some embodiments, user 810 can automatically obtain initialization parameters through server 820, and automatically initialize the autonomous driving navigation component 830 and the autonomous driving navigation module 840. Specifically, user 810 can obtain authentication of its legal identity by server 820 by placing an order to server 820, etc. After passing the authentication, server 820 can issue initialization parameters and automatically initialize the autonomous driving navigation component 830 and the autonomous driving navigation module 840 according to these initialization parameters. In some embodiments, server 820 may include a backend server of a travel service platform, an autonomous driving vehicle developer, etc. For more information on how to manually / automatically obtain initialization parameters, please refer to the relevant description of step S310, which will not be repeated here. For more information on how to initialize the autonomous driving navigation component and the autonomous driving navigation module according to the initialization parameters, please refer to the relevant description of step S330, which will not be repeated here.

[0097] Step S835, establishing a mapping.

[0098] In some embodiments, the mobile terminal 120 may establish a mapping between the autonomous driving navigation component 830 and the autonomous driving navigation module 840 through a preset identifier in the autonomous driving navigation component 830. For more information on how to establish a mapping between the autonomous driving navigation component and the autonomous driving navigation module, please refer to the relevant description of step S320, which will not be repeated here.

[0099] Step S845, establish a connection.

[0100] In some embodiments, after the autonomous driving navigation module 840 is initialized, the mobile terminal 120 may establish a two-way data connection between the autonomous driving navigation module 840 and the vehicle-mounted central control 850. The vehicle-mounted central control 850 may include the vehicle-mounted central control of the autonomous driving vehicle.

[0101] Step S855, sending data.

[0102] In some embodiments, after step S845, the vehicle-mounted central control 850 can send data, such as real-time navigation information, historical navigation information, etc., to the automatic driving navigation module 840 through the established data connection.

[0103] Step S865, rendering and displaying on the same layer.

[0104] In some embodiments, after step S855, the autonomous driving navigation module 840 may display the autonomous driving navigation interface 860 through same-layer rendering according to the received navigation information, and display various information on the autonomous driving navigation interface 860, such as real-time navigation information displayed in a 3D projection manner. For more information on how to display the autonomous driving navigation interface, please refer to the relevant description of step S350, which will not be repeated here.

[0105] Step S875, data callback.

[0106] In some embodiments, after step S855, the autonomous driving navigation module 840 may transmit the received information to the autonomous driving navigation component 830 through the callback function set in the properties of the autonomous driving navigation component 830. In some embodiments, the autonomous driving navigation component 830 may display the attachment information according to the information received in the callback function. Among them, the additional information may be integrated into the autonomous driving navigation interface 860 in the form of a built-in component of a small program, and these built-in components of the small program are displayed in an overlay manner on the page rendered by the autonomous driving navigation module 840. For more information on how to implement data callback and how to display additional information, please refer to the relevant description of step S350, which will not be repeated here.

[0107] It should be noted that the above description of processes 300 and 800 is only for example and illustration, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to processes 300 and 800 under the guidance of this specification. However, these modifications and changes are still within the scope of this specification. For example, step S320 can be performed before step S310.

[0108] The beneficial effects that may be brought about by the embodiments of this specification include but are not limited to: (1) By integrating the autonomous driving navigation module and the autonomous driving navigation component in the mini program engine, the navigation information of the autonomous driving vehicle is displayed in the mini program. Since the mini program can be used without the user's installation and download, and can be used on multiple system platforms after one development, the difficulty of development and use is reduced. At the same time, since its data is closed in the container of the mini program, data security is guaranteed, the development efficiency of navigation applications on mobile terminals is greatly improved, and the needs of multiple parties (for example, autonomous driving vehicle developers, operators and passengers) are well met; (2) The navigation information is obtained from the vehicle-mounted central control through the native module of the autonomous driving navigation module, and the autonomous driving navigation interface is directly rendered and displayed by the autonomous driving navigation module on the same layer, which realizes the closed loop of data, guarantees data security, and improves the execution efficiency of the program; (3) By superimposing the built-in components of the mini program on the page rendered by the autonomous driving navigation module, additional information related to navigation is displayed, so that the user has a more comprehensive grasp of the information, which facilitates the user to better grasp the status of the autonomous driving vehicle and improves user satisfaction. It should be noted that different embodiments may have different beneficial effects. In different embodiments, the beneficial effects that may be produced may be any one or a combination of the above, or any other beneficial effects that may be obtained.

[0109] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to this specification. Such modifications, improvements and corrections are suggested in this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0110] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0111] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

[0112] Similarly, it should be noted that in order to simplify the description disclosed in this specification and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the subject matter of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0113] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of this specification are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0114] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification are hereby incorporated by reference in their entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this specification (currently or later attached to this specification) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0115] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. An automatic driving navigation method for a mobile terminal, comprising: Get initialization parameters; Register the autopilot navigation component; Initializing an autonomous driving navigation module through the autonomous driving navigation component based on the initialization parameters; Receive real-time navigation information sent by the server; An automatic driving navigation interface is displayed based on the real-time navigation information.

2. The method of claim 1, wherein the autonomous driving navigation component comprises a preset identifier, and wherein registering the autonomous driving navigation component comprises: The autonomous driving navigation component is mapped to the autonomous driving navigation module based on the preset identifier.

3. The method according to claim 1, wherein initializing the autonomous driving navigation module through the autonomous driving navigation component based on the initialization parameter comprises: Based on the initialization parameters, the autonomous driving navigation module establishes a data connection with the server.

4. The method according to claim 1, wherein displaying an automatic driving navigation interface based on the real-time navigation information comprises: Based on the real-time navigation information, controlling the autonomous driving navigation module to render the autonomous driving navigation interface; Based on at least part of the real-time navigation information, additional information is displayed on the autonomous driving navigation interface through the autonomous driving navigation component.

5. According to the method as claimed in claim 4, controlling the autonomous driving navigation module to render the autonomous driving navigation interface is performed through same-layer rendering.

6. According to the method described in claim 1, the autonomous driving navigation component is implemented by way of a mini-program component.

7. The method according to claim 1, wherein the autonomous driving navigation module is implemented in a native manner.

8. In the method of claim 1, the autonomous driving navigation component and the autonomous driving navigation module are included in a mini-program engine.

9. The method of claim 1, wherein the initialization parameters include connection parameters and setting parameters.

10. An automatic driving navigation system for a mobile terminal, comprising a parameter acquisition module, a navigation registration module, a navigation initialization module, an information receiving module and a navigation display module; The parameter acquisition module is used to obtain initialization parameters; The navigation registration module is used to register the autonomous driving navigation component; The navigation initialization module is used to initialize the autonomous driving navigation module through the autonomous driving navigation component based on the initialization parameters; The information receiving module is used to receive real-time navigation information sent by the server; The navigation display module is used to display the automatic driving navigation interface based on the real-time navigation information.

Images