Interface focus control method and related device

Abstract

The embodiment of the invention provides an interface focus control method and a related device, and relates to the technical field of terminals. The method comprises the following steps: for an automobile supporting a knob control navigation system, establishing an association relationship between a rotation event or a click event of a knob and a clickable control in a map application interface; therefore, when a user operates the knob, the operation can be converted into selection or click operation on the clickable control in the interface, so that map application in the electronic equipment can be controlled, the navigation function is realized, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular to an interface focus control method and related devices. Background Art

[0002] With the development of technology, transportation has become more and more convenient, and some users may choose to travel by car. When choosing to travel by car, the user can connect an electronic device to the car. For example, the electronic device can be connected to the car via USB, so that the car can use the navigation application in the electronic device for route navigation.

[0003] Some cars can support knob control of the navigation system, which can also be understood as the in-vehicle navigation in the car having a knob. However, in some cars that support the knob control of the navigation system, the user cannot control the navigation application in the electronic device by rotating the knob, which reduces the user experience. Summary of the Invention

[0004] The interface focus control method and related devices provided in the embodiments of this application can establish an association relationship between the rotation event or click event of the knob and the clickable control in the map application interface for cars that support the knob control of the navigation system. In this way, when the user operates the knob, it can be converted into a selection or click operation on the clickable control in the interface, so as to be able to control the map application in the electronic device.

[0005] In a first aspect, the interface focus control method provided in the embodiments of this application includes:

[0006] The first electronic device establishes a communication connection with the second electronic device; the first electronic device transmits information for displaying a first interface to the second electronic device, and the first interface includes a first control for entering a first application. The information for displaying the first interface enables the second electronic device to display the first interface; when a first event of triggering the first control by the knob of the second electronic device is obtained, the first electronic device transmits information for displaying a second interface to the second electronic device. The second interface includes a first window and the interface of the first application. The first window covers the interface of the first application, and the first window does not block the interface of the first application. The position corresponding to the target control in the first window is set to be triggerable by the knob, and the target control is a triggerable control in the interface of the first application; when a second event generated by the rotation of the knob of the second electronic device is obtained, the focus of the interface of the first application in the second electronic device is controlled to move from a second control to a third control; wherein, a first position in the first window covers the second control, and a second position in the first window covers the third control, and the second position is a position adjacent to the first position set in the first window. In this way, for an automobile supporting a knob, the rotation event or click event of the knob can be associated with the triggerable control in the first application interface. In this way, the knob event can be converted into an operation on the triggerable control in the interface of the first application, so as to control the focus of the first application and improve the user experience.

[0007] In a possible implementation, before the first electronic device transmits information for displaying the second interface to the second electronic device, it further includes: the first electronic device obtains layout information of one or more controls when the interface of the first application is displayed in the second electronic device, and the layout information includes one or more of the following information: the name of the control, the size of the control, the position of the control, and one or more of the controls include the target control; the first electronic device determines the corresponding position of the target control in the first window based on the layout information of the target control. In this way, operations of triggering the rotation or click of the knob can be responded to in the cover window, and corresponding logic can be executed.

[0008] In a possible implementation, before controlling the focus of the interface of the first application in the second electronic device to move from the second control to the third control, it further includes: the first electronic device sorts the target controls based on the layout information of the target controls, wherein, in the sorting, the second control and the third control are adjacent controls in the sorting. In this way, the focus switching of adjacent controls in the sorting can be realized when the knob rotates.

[0009] In a possible implementation, when sorting target controls, one or more of the following sorting methods are included: sorting according to the distances from each target control to the target position, from near to far; sorting according to the order of rows or columns of the layout positions of each target control. In this way, by sorting the target controls, the focus switching of adjacent controls can be achieved, thereby controlling the movement of the focus in the first interface.

[0010] In a possible implementation, the electronic device further includes a first service, a window management service (WMS), and a first module. After obtaining a second event generated by the rotation of a knob of a second electronic device, it further includes: the first service responding to the second event and invoking the addWindow() function, where the addWindow() function is used to instruct the window management service (WMS) to update the first window; the window management service (WMS) invoking a preset interface of the first module, where the preset interface is used to instruct the first module to calculate the information of a second position in the first window; the window management service (WMS) updating the first window based on the information of the second position obtained by the first module, where the second position in the first window is highlighted. In this way, through the interaction between the first service, the window management service (WMS), and the first module, the calculation and drawing of the cover map window can be implemented based on the time of the knob.

[0011] In a possible implementation, the first service responding to the second event includes: if the second event is an event of rotating the knob clockwise, the first service executes a first function, where the first function is used to control the focus of the interface of a first application in the second electronic device to move from a second control to a third control, and the sorting of the second control is earlier than that of the third control; if the second event is an event of rotating the knob counterclockwise, the first service executes a second function, where the second function is used to control the focus of the interface of the first application in the second electronic device to move from the second control to the third control, and the sorting of the third control is earlier than that of the second control. In this way, by distinguishing the rotation direction of the knob, the jump between the controls in the interface of the first application can be achieved.

[0012] In a possible implementation, the method further includes: when obtaining a third event that a third control is triggered by the knob of the second electronic device, transmitting information for displaying a third interface to the second electronic device, where the third interface is the interface that should be displayed after triggering the third control in the interface of the first application. In this way, when triggering the click event of the knob on the third control, the click event of the third control can be responded to in the first application, and the third interface after clicking the third control is displayed.

[0013] In a possible implementation, the method further includes: when obtaining a fourth event generated by rotating a knob of a second electronic device, the first electronic device transmits information for displaying a first interface to the second electronic device for the second electronic device to return to the first interface; where when obtaining the fourth event, the focus of the interface of the first application is on a fourth control, and the fourth control is a control with adjacent controls on only one side. In this way, when the knob triggers the fourth control to jump to the side without adjacent controls, the cover window can be exited.

[0014] In a possible implementation, after obtaining a third event triggered by a knob of a second electronic device at a second position in a first window, it further includes: a first service executes a first function based on the fourth event and calls the removeWindow() function of a window management service WMS; the window management service WMS removes the first window. In this way, when exiting the interface of the first application, the first window can be removed in a timely manner, so that the knob cannot trigger events of other interface controls, thus enabling the knob event to correspond to the function of the interface display and improving the user experience.

[0015] In a second aspect, an embodiment of the present application provides an image recognition device, which may be an electronic device, or a chip or a chip system inside the electronic device. The device may include a processing unit. The processing unit is used to implement any method related to processing performed by the electronic device in the first aspect or any possible implementation manner of the first aspect. When the device is an electronic device, the processing unit may be a processor. The device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the electronic device to implement the method described in the first aspect or any possible implementation manner of the first aspect. When the device is a chip or a chip system inside the electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to enable the electronic device to implement the method described in the first aspect or any possible implementation manner of the first aspect. The storage unit may be a storage unit inside the chip (such as a register, a cache, etc.), or a storage unit outside the chip and inside the electronic device (such as a read-only memory, a random access memory, etc.).

[0016] Exemplarily, a display unit is used to display a first interface, and is further used to display a second interface, and is further used to display a third interface, and is further used to display a fourth interface. A processing unit is used to receive a first operation that triggers a first control.

[0017] In a possible implementation, a processing unit is configured to establish a communication connection with a second electronic device, and is further configured to transmit information for displaying a first interface to the second electronic device, and is further configured to transmit information for displaying a second interface to the second electronic device. Specifically, the processing unit is further configured to control the focus of the interface of the first application in the second electronic device to move from a second control to a third control.

[0018] In a possible implementation, a processing unit is configured to obtain layout information of one or more controls when the interface of the first application is displayed in the second electronic device, and is further configured to determine a corresponding position of a target control in a first window based on the layout information of the target control.

[0019] In a possible implementation, a processing unit is configured to sort target controls based on the layout information of the target controls.

[0020] In a possible implementation, when sorting target controls, one or more of the following sorting methods are included: sorting according to the distances from each target control to a target position from near to far; sorting according to the order of rows or columns of the layout positions of each target control.

[0021] In a possible implementation, a processing unit is configured to respond to a second event, call the addWindow() function, and is further configured to call a preset interface of a first module. Specifically, the processing unit is further configured to update the first window based on information about a second position obtained from the first module.

[0022] In a possible implementation, a processing unit is configured to execute a first function if the second event is an event of rotating a knob clockwise, and is further configured to execute a second function if the second event is an event of rotating the knob counterclockwise.

[0023] In a possible implementation, a processing unit is configured to transmit information for displaying a third interface to the second electronic device.

[0024] In a possible implementation, a processing unit is configured to transmit information for displaying a first interface to the second electronic device.

[0025] In a possible implementation, a processing unit is configured to execute a first function based on a fourth event, call the removeWindow() function of a window management service (WMS), and is further configured to remove the first window.

[0026] In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory. The memory is configured to store code instructions, and the processor is configured to run the code instructions to execute the method described in the first aspect or any possible implementation of the first aspect.

[0027] Fourthly, an embodiment of the present application provides a communication system, including a first electronic device and a second electronic device. The second electronic device includes a knob. The first electronic device is configured to execute the method described in the first aspect or any one of the possible implementation manners of the first aspect. The second electronic device is configured to receive the interface information transmitted by the first electronic device and perform interface display based on the interface information. The second electronic device is further configured to transmit an event triggered by the knob to the first electronic device.

[0028] Fifthly, the present application provides a chip or a chip system. The chip or the chip system includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instruction to execute the method described in the first aspect or any one of the possible implementation manners of the first aspect. Wherein, the communication interface in the chip may be an input / output interface, a pin, a circuit, etc.

[0029] In a possible implementation, the chip or the chip system described above in the present application further includes at least one memory, and instructions are stored in the at least one memory. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip (such as a read-only memory, a random access memory, etc.).

[0030] Sixthly, an embodiment of the present application provides a computer-readable storage medium. A computer program or instruction is stored in the computer-readable storage medium. When the computer program or instruction runs on a computer, the computer is caused to execute the method described in the first aspect or any one of the possible implementation manners of the first aspect.

[0031] Seventhly, an embodiment of the present application provides a computer program product including a computer program. When the computer program runs on a computer, the computer is caused to execute the method described in the first aspect or any one of the possible implementation manners of the first aspect.

[0032] It should be understood that the second to seventh aspects of the present application correspond to the technical solutions of the first aspect of the present application. The beneficial effects achieved by each aspect and the corresponding feasible implementation manners are similar and will not be elaborated herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

[0034] Figure 2 is a schematic software structure diagram of an electronic device provided by an embodiment of the present application;

[0035] Figure 3 is a schematic interface diagram of a vehicle-mounted screen provided by an embodiment of the present application;

[0036] Figure 4 A schematic diagram of the interface of a map application provided by an embodiment of the present application;

[0037] Figure 5 A schematic diagram of a map search interface provided by an embodiment of the present application;

[0038] Figure 6 A flowchart of the interaction between a mobile phone and a car machine provided by an embodiment of the present application;

[0039] Figure 7 A timing diagram of the interaction between modules in a mobile phone provided by an embodiment of the present application;

[0040] Figure 8 A schematic diagram of a method for controlling the interface focus provided by an embodiment of the present application;

[0041] Figure 9 A schematic diagram of the structure of a chip provided by an embodiment of the present application. Detailed implementation manners

[0042] For the convenience of clearly describing the technical solutions of the embodiments of the present application, the following briefly introduces some terms and technologies involved in the embodiments of the present application:

[0043] 1. Terms

[0044] In the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. For example, the first chip and the second chip are only used to distinguish different chips, and their sequence is not limited. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily mean different.

[0045] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0046] In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0047] With the development of technology, transportation is becoming more and more convenient, and some users may choose to travel by car. When choosing to travel by car, the user can connect the electronic device to the car. For example, the electronic device can be connected to the car via USB, so that the car can use the navigation application in the electronic device for route navigation. Among them, the navigation application can also be called a map application, and the electronic device can include, for example, a mobile phone, a tablet, etc. For the sake of convenience of description, hereinafter, the electronic device is taken as a mobile phone and the application is taken as a map application as an example for description.

[0048] Some cars can support a knob-controlled navigation system, which can also be understood as that the in-vehicle navigation in the car has a knob. When the user uses the in-vehicle navigation, the user can rotate or click the knob to implement functions such as map zooming, switching, and searching.

[0049] However, for cars that support a knob-controlled navigation system, when the car is connected to the electronic device and uses the map application in the electronic device for route navigation, the user cannot control the map application in the electronic device by rotating or clicking the knob, which reduces the user experience.

[0050] In view of this, the interface focus control method provided by the embodiments of the present application can establish an association relationship between the rotation event or click event of the knob and the clickable control in the map application interface for cars that support a knob-controlled navigation system. In this way, when the user operates the knob, it can be converted into a selection or click operation on the clickable control in the interface, so as to be able to control the map application in the electronic device, implement the navigation function, and improve the user experience.

[0051] It can be understood that the electronic device in the embodiments of the present application can also be a terminal device in any form. For example, the electronic device can further include: tablet computer, palmtop computer, laptop computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing devices connected to a wireless modem, in-vehicle device, wearable device, electronic device in a 5G network or electronic device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application do not limit this.

[0052] By way of example and not limitation, in the embodiments of the present application, the electronic device can also be a wearable device. A wearable device can also be referred to as a wearable intelligent device, which is the general term for devices developed by applying wearable technologies to intelligently design daily wearables, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0053] In addition, in the embodiments of the present application, the electronic device may also be an electronic device in an Internet of Things (IoT) system. The IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection.

[0054] The electronic device in the embodiments of the present application may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0055] In the embodiments of the present application, the electronic device or each network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement service processing through processes. For example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system, etc. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software.

[0056] Exemplarily, Figure 1 The structural schematic diagram of the electronic device is shown.

[0057] The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0058] It can be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented by hardware, software, or a combination of software and hardware.

[0059] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors. The controller may generate operation control signals according to the instruction operation code and timing signal to complete the control of fetching and executing instructions.

[0060] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory may store the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the above-mentioned memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system. For example, in the embodiments of the present application, the processor 110 may be used to process the binding of auxiliary services, the transmission of knob events, the drawing of windows, etc.

[0061] It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are only illustrative descriptions and do not constitute a structural limitation on the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0062] The internal memory 121 may be used to store computer-executable program codes, and the executable program codes include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, application programs required for at least one function, etc. The data storage area may store data created during the use of the electronic device. In addition, the internal memory 121 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor. For example, in the embodiments of the present application, the internal memory 121 may be used to store the vehicle-mounted touch type, sorting algorithms, codes related to monitoring window or control changes, etc.

[0063] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device may include one or N display screens 194, where N is a positive integer greater than 1. The electronic device realizes the display function through the GPU, the display screen 194, and the application processor, etc. For example, in the embodiments of the present application, the display screen 194 may be used to display the interface of a map application and may also display the selected controls, etc.

[0064] Figure 2 It is a software structure block diagram of the electronic device according to the embodiments of the present application.

[0065] The layered architecture divides software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided from top to bottom into the application layer, the application framework layer, the Android runtime and operating system libraries, and the kernel layer.

[0066] The application layer can also be referred to as the app layer, and the app layer can include a series of application packages. As Figure 2 shown, the application packages can include applications such as maps, phones, music, calendars, cameras, games, memos, videos, etc. The applications can include system applications and third-party applications.

[0067] For example, in the embodiments of the present application, the applications can include map applications, or other types of applications, which are not limited in the embodiments of the present application. The application can support auxiliary services and can also handle click events of the in-vehicle infotainment system knob. It can be understood that after the application supports the auxiliary service, the travel service can obtain the control information of the application interface, so as to implement the interface focus control method of the embodiments of the present application.

[0068] In addition, the app layer can also include the Android operating system AndroidOS and the travel service.

[0069] In the embodiments of the present application, the Android operating system can draw a new window on top of the map interface of the in-vehicle infotainment system screen based on the WindowManagerService (WMS). This window can also be referred to as a cover map window.

[0070] The travel service can be understood as a pre-installed screen mirroring application on the mobile phone. When the mobile phone is connected to the in-vehicle infotainment system via USB and the user agrees to use the travel service, the connected vehicle information can be viewed in the travel service, and some applications or services on the mobile phone can also be displayed on the in-vehicle infotainment system screen through the travel service. For example, map applications on the mobile phone can be displayed on the in-vehicle infotainment system screen, thus bringing a convenient driving experience to the user. In some implementations, the travel service can also be referred to as a vehicle connection service or a vehicle connection application.

[0071] The travel service can include a travel reverse control service and an interconnection service.

[0072] The travel reverse control service can be used to perform protocol conversion of knob operations, focus navigation operations and response monitoring, obtain the user interface (UI) control array, etc. In some scenarios, the control can also be referred to as a node. For the sake of convenience of description, controls will be used as examples for subsequent explanations.

[0073] Among them, the protocol conversion of the knob operation can convert the knob event into a corresponding control selection event or control click event. The focus navigation operation and response monitoring can determine the control where the focus is located on the current in-vehicle screen based on the rotation event or click event of the knob, and respond to the knob event. Obtaining the UI control array can obtain the layout tree of the in-vehicle screen interface based on the auxiliary service, sort the layout tree through relevant sorting algorithms, and perform focus calculation based on the currently sorted controls, so as to obtain the UI control array.

[0074] The interconnected service can also be understood as the service provided by the software development kit (SDK) of the CarLife application integrated in the mobile phone. It can be understood that the CarLife application can also be called the in-vehicle interconnection application. The Android application package (APK) of the CarLife application can be pre-installed in the in-vehicle unit. After the mobile phone integrates the CarLife SDK, communication between the mobile phone and the in-vehicle unit can be achieved. For example, the mobile phone can obtain the rotation event or click event of the in-vehicle knob based on the CarLife SDK.

[0075] The application framework layer can also be called the Framework layer. The Framework layer can provide application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The Framework layer can include some predefined functions.

[0076] As Figure 2 shown, the Framework layer can include the auxiliary service Accessibility Service and the in-vehicle interconnection service CarLife, etc.

[0077] The auxiliary service can also be called the accessibility service. It can be understood that when the mobile phone is connected to the in-vehicle unit, if the current in-vehicle unit supports the knob control navigation system, or the current in-vehicle unit supports both touch screen and knob control navigation system, the travel service can obtain the control information of the map application interface on the in-vehicle screen based on the auxiliary service.

[0078] The in-vehicle interconnection service can transmit the knob event to the interconnected service in the application layer, and can also transmit the response of the travel service to the knob event to the in-vehicle unit.

[0079] Android runtime includes the core library and the virtual machine. Android runtime is responsible for the control and management of the Android system.

[0080] The core library consists of two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

[0081] The application layer and the Framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the Framework layer as binary files. The virtual machine is used to manage the object lifecycle, stack management, thread management, security and exception management, and garbage collection and other functions. For example, in the embodiments of the present application, the virtual machine can be used to execute functions such as querying the touch type of the in-vehicle computer, constructing an array of UI controls, and passing knob events.

[0082] The operating system library can also be called the Native layer, and the Native layer can include multiple functional modules. For example: media library, function library, graphics processing library, etc.

[0083] The kernel layer is the layer between the hardware and the software. The kernel layer can include USB drivers, wireless fidelity (WiFi) drivers, Bluetooth drivers, etc.

[0084] It should be noted that only the Android system is taken as an example in the embodiments of the present application. In other operating systems (such as Windows system, IOS system, etc.), as long as the functions implemented by each functional module are similar to those of the embodiments of the present application, the solution of the present application can also be implemented.

[0085] In a possible scenario, when the mobile phone is connected to the in-vehicle computer, and with the user's consent to use the travel service, the map application in the mobile phone can be displayed on the in-vehicle computer screen through the travel service. Exemplarily, taking the map application in the mobile phone as an example, after the mobile phone is connected to the in-vehicle computer, the map application can be displayed on the in-vehicle computer screen.

[0086] Figure 3 The schematic diagram of the interface 301 of the in-vehicle computer screen is shown.

[0087] The interface 301 can include multiple controls, such as an application navigation bar 302 control, a map quick entry 303 control, a destination navigation quick entry 304 control, a weather quick entry 305 control, a music quick entry 306 control, etc.

[0088] The application navigation bar 302 control can display application icons for providing quick access to open applications. The application navigation bar 302 control can include an application icon 307 control, an application icon 2 control, an application icon 3 control, an application icon 4 control, etc.

[0089] The map quick access 303 control can be used to conveniently enter the map application. The destination navigation quick access 304 control can be used to conveniently open the route to go home or the route to the company for navigation. The weather quick access 305 control can be used to view the weather conditions and can also be used to conveniently enter the weather application. The music quick access 306 control can be used to play music and can also be used to conveniently enter the music application.

[0090] It can be understood that the above interface 301 is an exemplary interface. Different in-vehicle screens may have different interface displays, and the interface 301 may include more or less content. The content included in the specific interface 301 is not limited in the embodiments of the present application.

[0091] When the user wants to open the map application, assuming that the application icon 307 control is the application icon corresponding to the map application, in one possible scenario, the user can trigger an operation on the application icon 307 control. For example, this operation can be an operation of clicking the knob when the focus is on the application icon 307 control, or an operation of clicking the application icon 307 control, etc. The embodiments of the present application do not make a limitation. In response to the user's trigger operation, the in-vehicle system can enter the interface of the map application from the interface 301.

[0092] In another possible scenario, the user can trigger an operation on the map quick access 303 control. For example, this operation can be an operation of clicking the knob when the focus is on the map quick access 303 control, or an operation of clicking the map quick access 303 control, etc. The embodiments of the present application do not make a limitation. In response to the user's trigger operation, the in-vehicle system can enter the interface of the map application from the interface 301.

[0093] Figure 4 A schematic diagram of the interface 401 of the map application is shown.

[0094] The interface 401 of the map application may include multiple controls, such as a navigation indication 402 control, a "my location" 403 control, a bearing indication 404 control, a map zoom-in 405 control, a map zoom-out 406 control, etc.

[0095] The navigation indication 402 control can be used to indicate the direction in which the user is currently driving. The "my location" 403 control can be used to identify the location where the user is currently located. The bearing indication 404 control can be used to identify the bearing where the user is currently located. The map zoom-in 405 control can be used to zoom in on the map of the interface 401, and the map zoom-out 406 control can be used to zoom out the map of the interface 401.

[0096] It can be understood that the above interface 401 is an exemplary interface. Different applications may have different interface displays, and the interface 401 may include more or less content. The content included in the specific interface 401 is not limited in the embodiments of the present application.

[0097] It is understandable that the map application can also provide a map search function. Exemplarily, Figure 5 A schematic diagram of the map search interface 501 is shown.

[0098] The map search interface 501 may include multiple controls, such as a search box 502 control, a first search result 503 control, a second search result 505 control, a third search result 507 control, a "my location" 504 control, a direction indicator 506 control, a zoom-in map 508 control, a zoom-out map 509 control, etc.

[0099] Exemplarily, the search box 502 control can search for the input keywords. The search box 502 control may include a search keyword and a return control. For example, the search keyword may include "food", and the return control can be used to return to the previous interface.

[0100] The first search result 503 control may include information such as a location icon, the name of the search result, the distance from the current location, and / or the address of the search result. The second search result 505 control and the third search result 507 control are similar to the content included in the first search result 503 control and will not be elaborated here.

[0101] The "my location" 504 control may refer to the relevant description of the "my location" 403 control above; Figure 4 the direction indicator 506 control may refer to the relevant description of the direction indicator 404 control above; Figure 4 the zoom-in map 508 control may refer to the relevant description of the zoom-in map 405 control above; Figure 4 the zoom-out map 509 control may refer to the relevant description of the zoom-out map 406 control above, and will not be elaborated here. Figure 4 Figure 4

[0102] It is understandable that the above map search interface 501 is an exemplary interface. Different applications may have different interface displays, and the map search interface 501 may include more or less content. The specific content included in the map search interface 501 is not limited in the embodiments of the present application.

[0103] When the CarLife application in the vehicle detects that the map application is opened on the vehicle screen in the case of the connection between the vehicle and the mobile phone, the CarLife application can interact with the CarLife SDK in the mobile phone to open the auxiliary service in the mobile phone.

[0104] The travel service in the mobile phone can transmit the package name of the map application to the auxiliary service and obtain information about each control in the map application interface displayed on the in-vehicle screen based on the auxiliary service. The travel service can also traverse the controls on the map page of the in-vehicle screen to obtain control information such as the control name, control position, control size, and whether the control is clickable.

[0105] Exemplarily, taking the interface 501 above Figure 5 as an example, the travel service can obtain each control in the interface 501. The controls include the search box 502 control, the first search result 503 control, the second search result 505 control, the third search result 507 control, the "My Location" 504 control, the azimuth indicator 506 control, the zoom-in map 508 control, and the zoom-out map 509 control.

[0106] After obtaining the control information, the travel service can filter out the clickable controls. For example, the above-mentioned search box 502 control, the first search result 503 control, the second search result 505 control, the third search result 507 control, the "My Location" 504 control, the azimuth indicator 506 control, the zoom-in map 508 control, and the zoom-out map 509 control are all clickable controls.

[0107] The travel service can also use the operating system to overlay a new window on the interface 501 of the in-vehicle device. Among them, this window can be understood as a transparent window, which does not block the interface 501. In the embodiments of the present application, this window can also be called a cover map window or a window sticker. For the sake of description, the cover map window will be used for subsequent description.

[0108] The travel service can also use the operating system to draw these clickable controls in the cover map window based on the control information such as the position and size of the clickable controls in the interface 501. Thus, operations such as triggering the knob rotation or clicking can be responded to in the cover map window, and corresponding logic can be executed.

[0109] It can be understood that the travel service can also sort these clickable controls.

[0110] Taking control A as a reference object for illustration, among the possible sorting rules, the priority of the control above control A is higher than the priority of the control to the left of control A, the priority of the control to the left of control A is higher than the priority of the control to the right of control A, and the priority of the control to the right of control A is higher than the priority of the control below control A. That is to say, the closer the control is to the upper and left sides of the interface, the higher the priority.

[0111] Exemplarily, taking the above Figure 5Take the corresponding map search interface 501 as an example. If the above sorting rules are used to sort each clickable control in the map search interface 501, from the highest to the lowest priority, the sorting result can be control 502, control 503, control 504, control 505, control 506, control 507, control 508, and control 509.

[0112] It can be understood that the above sorting rules do not conform to the user's operation habits. For example, after the user selects and views control 503, it is very likely that the user will continue to select the second search result control 505 and / or the third search result control 507 for viewing, rather than viewing controls 504, 506, 507, and / or 508 on the right side of the interface.

[0113] Therefore, the embodiments of the present application can further optimize the above sorting rules.

[0114] In a possible implementation, the adjacent right control or adjacent lower control of control A can be preferentially viewed. The adjacent right control can be understood as the control that is adjacent to control A and is located on the right side of control A. The adjacent lower control can be understood as the control that is adjacent to control A and is located below control A. Among them, adjacent can be understood as the layout between two controls is adjacent, or the distance between two controls is less than or equal to a preset value.

[0115] Exemplarily, if the distance between the right position right of control A and the left position left of control B is less than or equal to the preset value, then control B is the adjacent right control of control A. If the distance between the bottom position bottom of control A and the top position top of control B is less than or equal to the preset value, then control B is the adjacent lower control of control A.

[0116] Among them, the preset value can be set according to experience or laboratory tests, and the preset value can be set to a smaller value. For example, the preset value can be set to 0dp, 1dp, or 5dp, etc. The specific value of the preset value is not limited in the embodiments of the present application.

[0117] In a possible scenario, after control A is sorted, if there is an adjacent right control for control A, the adjacent right control of control A has the highest priority and can be preferentially sorted.

[0118] In another possible scenario, after control A is sorted, if there is an adjacent lower control for control A, the adjacent lower control of control A has the highest priority and can be preferentially sorted.

[0119] In still another possible scenario, after control A is sorted, if there are both an adjacent right control and an adjacent lower control for control A, the priority of the adjacent right control of control A is greater than that of the adjacent lower control.

[0120] Optionally, the priority of the adjacent lower control of control A can also be greater than the priority of the adjacent right control. This is not limited in the embodiments of the present application.

[0121] The following takes the first search result 503 control in Figure 5 as an example for illustration.

[0122] According to the sorting rule before the above optimization, after the first search result 503 control, the "My Location" control 504 is located on the right side of the 503 control, and the second search result 505 control is located below the 503 control. Since the control on the right side of the 503 control has a higher priority than the control below the 503 control, the priority of the 504 control is higher than the priority of the 505 control. Therefore, in descending order of priority, the sorting result can be the 503 control, the 504 control, and the 505 control.

[0123] And according to the optimized sorting rule, since there is a 505 control below the 503 control and the 505 control is the adjacent lower control of the 503 control, the priority of the 505 control is higher than the priority of the 504 control.

[0124] If the controls in the map search interface 501 are sorted according to the optimized sorting rule, in descending order of priority, the sorting result can be the 502 control, the 503 control, the 505 control, the 507 control, the 504 control, the 506 control, the 508 control, and the 509 control. In this way, the optimized sorting rule can better conform to the user's operation habits and improve the user experience.

[0125] Figure 6 shows the interaction flow chart between the mobile phone and the vehicle head unit.

[0126] The interaction process between the mobile phone and the vehicle head unit can include a connection process, a monitoring process, and a process of executing the interface focus control method. Among them, the connection process can include the following step S601. The monitoring process can include the following steps S602 to step S604. The process of executing the interface focus control method can include the following steps S605 to step S621.

[0127] S601. The mobile phone is successfully connected to the vehicle head unit.

[0128] The mobile phone and the vehicle head unit can be connected via USB. Of course, they can also be connected via other methods such as Bluetooth and WiFi. This is not limited in the embodiments of the present application. After the connection is successful, the map application in the mobile phone can be displayed on the vehicle head unit screen through the travel service. The travel service can also execute step S602 to query the touch type of the vehicle head unit.

[0129] S602. Query the touch type of the vehicle head unit.

[0130] The travel service can query the touch type of the in-vehicle unit through the CarLife SDK. Exemplarily, the CarLife SDK can interact with the in-vehicle unit interconnection service in the Framework layer, and the in-vehicle unit interconnection service can interact with the CarLife application on the in-vehicle unit, so as to obtain the touch type supported by the in-vehicle unit.

[0131] Among them, the touch type of the in-vehicle unit can include a type that does not support a touch screen but supports a knob, a type that does not support a knob but supports a touch screen, and a type that supports both a touch screen and a knob. It can be understood that the method provided by the embodiments of the present application can be applicable to the type that does not support a touch screen but supports a knob and the type that supports both a touch screen and a knob.

[0132] S603. Feedback the touch type of the in-vehicle unit.

[0133] After the CarLife SDK on the mobile phone side obtains the touch type supported by the in-vehicle unit, it can feedback the touch type of the connected in-vehicle unit to the travel service.

[0134] S604. Touch or focus management page.

[0135] When the user triggers an operation to open the map application, in response to the user's operation, the in-vehicle unit screen can enter the relevant interface of the map application. For example, the relevant interface of the map application can include the above-mentioned Figure 4 map application interface 401 and Figure 5 map search interface 501.

[0136] The travel service can manage the travel desktop and the application page based on the user's trigger operation.

[0137] On the one hand, the travel service can manage the travel desktop, which can be understood as a covering map window. For example, the covering map window can be located above the above-mentioned Figure 4 map application interface 401 or Figure 5 map search interface 501.

[0138] On the other hand, the travel service can also manage the application page, which can be understood as the page on the mobile phone side related to the travel service.

[0139] The travel service can also execute step S605 to request the operating system to obtain the UI control information of the map application.

[0140] S605. The travel service sends a request to the operating system.

[0141] After the travel service detects that the in-vehicle unit screen enters the interface of the map application, it can send a request to the operating system to obtain the control information in the interface of the map application.

[0142] S606. The operating system transfers the control layout.

[0143] The operating system can determine whether the map application supports the auxiliary service. When the map application supports the auxiliary service, the operating system can obtain the control layout of the map application and transfer the control layout to the auxiliary service.

[0144] S607. The auxiliary service returns a list of UI controls to the travel service.

[0145] After obtaining the control layout, the auxiliary service can return a list of UI controls to the travel service, and the list of UI controls can include information related to the control layout.

[0146] S608. The travel service constructs an array of UI controls.

[0147] The travel service can construct an array of UI controls based on the control layout of the map application.

[0148] Exemplarily, taking the above Figure 5 as an example, the array of UI controls constructed by the travel service can include control information. For example, the array of UI controls can be [502, 503, 505, 507, 504, 506, 508, 509]. It can be understood that the array of UI controls can include the array of controls that has been sorted according to the above sorting rules and priority order.

[0149] S609. CarLife SDK obtains the knob rotation event from the in-vehicle unit.

[0150] CarLife SDK can interact with the in-vehicle unit interconnection service in the Framework layer, and the in-vehicle unit interconnection service can interact with the CarLife application on the in-vehicle unit side. In this way, when a knob rotation event occurs on the in-vehicle unit, the in-vehicle unit interconnection service can obtain the knob rotation event based on the CarLife application on the in-vehicle unit side and transfer the knob rotation event to CarLife SDK.

[0151] After obtaining the knob rotation event from the in-vehicle unit, CarLife SDK can execute step S610 to transfer the knob rotation event of the in-vehicle unit to the travel service.

[0152] S610. CarLife SDK transfers the knob rotation event of the in-vehicle unit to the travel service.

[0153] S611. The in-vehicle unit event converts UI controls.

[0154] After obtaining the knob rotation event of the in-vehicle unit, the travel service can convert the knob rotation event into a trigger event for the UI controls based on the array of UI controls.

[0155] Exemplarily, taking the above Figure 5 as an example, assume that the focus of the current knob is on the 503 control. When the travel service detects a knob rotation event, it can determine the control to be triggered based on the UI control array. For example, turning the knob to the right can switch the focus from the 503 control to the 505 control, and turning the knob to the left can switch the focus from the 503 control to the 502 control. Of course, turning the knob to the right can also switch the focus from the 503 control to the 502 control, and turning the knob to the left can switch the focus from the 503 control to the 505 control. The specific correspondence between the rotation direction of the knob and the control selection is not limited in the embodiments of the present application.

[0156] After determining the control where the current focus is located, the travel service can execute step S612 to transfer the control that needs to be highlighted to the operating system.

[0157] S612: The travel service transfers the control that needs to be highlighted to the operating system.

[0158] S613: The operating system highlights the control in the cover map window.

[0159] The operating system can highlight the control in the cover map window based on the control transferred by the travel service to indicate which control the current focus is on.

[0160] Exemplarily, assume that the focus of the knob was originally on the 502 control. When the travel service detects a right rotation event of the knob, it indicates that the focus has switched to the 503 control. Therefore, the travel service can transfer the information of the 503 control to the operating system, and the operating system can highlight the 503 control to indicate that the current focus is on the 503 control.

[0161] Among them, the highlighting can include highlighting the border of the control where the focus is located, or a text prompt for the control where the focus is located. The specific highlighting method is not limited in the embodiments of the present application, as long as it can prompt the user which control the current focus is on.

[0162] S614: The CarLife SDK obtains the knob click event from the in-vehicle unit.

[0163] When a knob click event occurs on the in-vehicle unit, the vehicle connectivity service can obtain the knob click event based on the CarLife application on the in-vehicle unit side and transfer the knob click event to the CarLife SDK.

[0164] After the CarLife SDK obtains the knob click event from the in-vehicle unit, it can execute step S615 to transfer the knob click event of the in-vehicle unit to the travel service.

[0165] S615. The CarLife SDK transfers the knob click event of the in-vehicle unit to the travel service.

[0166] S616. The in-vehicle unit event converts the UI control.

[0167] After the travel service obtains the knob click event of the in-vehicle unit, it can convert the knob click event into a click event on the UI control based on the UI control array.

[0168] Exemplarily, taking the above Figure 5 as an example, assuming that the focus of the current knob is on the 503 control, when the travel service detects the knob click event, it can determine that the user has triggered a click event on the 503 control based on the UI control array. Then the travel service can execute step S617 to transfer the click event of the control.

[0169] S617. Transfer the click event of the control.

[0170] The travel service can transfer the knob click event to the auxiliary service through the relevant interfaces provided by the auxiliary service. The auxiliary service can transfer the knob click event to the operating system. Furthermore, the operating system can transfer the knob click event to the map application.

[0171] After the map application obtains the knob click event, it can execute step S618 to perform corresponding processing on the knob click event.

[0172] S618. The map application processes the click event.

[0173] After the map application obtains the click event of the control, it can respond to the click event and execute the corresponding process. For example, the map application can enter the corresponding page, zoom in on the map, zoom out on the map, etc., which are not limited in the embodiments of the present application.

[0174] S619. The auxiliary service monitors the window or control changes.

[0175] When the map application responds to the click event, the corresponding interface may change. At this time, the auxiliary service can detect the change of the window or control of the map application and transfer the change event of the window or control to the travel service.

[0176] S620. Focus management, application UI change adaptation.

[0177] The travel service can redraw on the upper layer of the cover map window on the in-vehicle unit side through the operating system according to the interface change of the map application. The travel service can also re-obtain the control layout of the map application interface.

[0178] S621. Refresh the UI control array.

[0179] The travel service can reconstruct the UI control array based on the control layout of the map application interface and sort each clickable control. For details, refer to the relevant descriptions in steps S605 to S608 above, which will not be elaborated here.

[0180] Figure 7 It shows the interaction timing diagram among various modules in the mobile phone.

[0181] The travel service at the application layer can include the travel service class CarUiService, the application icon management module AppItem, the data channel module CarLifeDataChannel, the auxiliary service module CarAccessibilityService, and the auxiliary service adapter AccessibilityAdapter.

[0182] Among them, the travel service class can be used to receive the knob event of the in-vehicle unit triggered by the user. The application icon management module can include one or more application icons in the in-vehicle unit. Exemplarily, the AppItem module can include the Figure 3 application icons included in the application navigation bar 302 control mentioned above, such as the application icon 307 control, the application icon 2 control, the application icon 3 control, the application icon 4 control, etc. It can be understood that each application can have its corresponding AppItem information. Through the AppItem information, it can be determined which application's interface needs to be initialized currently. The data channel module can be used to transfer the knob event.

[0183] The auxiliary service module and the auxiliary service adapter can be regarded as classes in the travel service. The travel service can interact with the auxiliary service AccessibilityService through the auxiliary service module and the auxiliary service adapter.

[0184] The Framework layer can include the auxiliary service AccessibilityService, the window management service WMS, the window information calculation class ComputerFrameInfo, and the window information assistance class IhnComputerFrameHelper, etc.

[0185] Among them, the WMS can be used to manage the display and operation of windows. For example, the WMS can obtain the window information of applications or the system, and perform layout and display according to the attributes such as the size and position of the window. The WMS can also process window animations, touch events, and key events, etc.

[0186] The window information calculation class and the window information assistance class can be used for window calculations. It can be understood that the window information calculation class and the window information assistance class can be coordinated for execution. For example, both the window information calculation class and the window information assistance class can obtain the size of the in-vehicle screen, and calculate the display size and position of the window on the in-vehicle screen based on the size of the in-vehicle screen, etc.

[0187] S701. Initialize the map application.

[0188] After receiving the operation of the user to open the map application, in response to this operation, the travel service class can call the init() function to initialize the relevant interface of the map application. For example, the interface can include Figure 4 the corresponding interface 401 or the map search interface 501, etc., which are not limited in the embodiments of the present application.

[0189] S702. The travel service binds the auxiliary service.

[0190] The travel service class can start the auxiliary service module CarAccessibilityService and call the bindService() function to bind the auxiliary service AccessibilityService.

[0191] S703. The auxiliary service module instructs to start the auxiliary service.

[0192] After the auxiliary service module is started, it can send a message to the auxiliary service, and this message is used to instruct the travel service to bind the auxiliary service.

[0193] S704. Initialize the auxiliary service adapter.

[0194] The travel service can call the init() function to initialize the auxiliary service adapter AccessibilityAdapter.

[0195] It can be understood that steps S702 and S704 may not distinguish the execution order. That is to say, the travel service can first bind the auxiliary service and then initialize the auxiliary service adapter; or the travel service can first initialize the auxiliary service adapter and then bind the auxiliary service; or the travel service can execute the processes of initializing the auxiliary service adapter and binding the auxiliary service simultaneously, which are not limited in the embodiments of the present application.

[0196] S705. The auxiliary service returns the result.

[0197] After the auxiliary service is started, it can return the result of successful binding to the auxiliary service module.

[0198] S706. Trigger the onAccessibilityEvent() function.

[0199] After the auxiliary service module obtains the result returned by the auxiliary service, it can execute the onAccessibilityEvent() function. Among them, the onAccessibilityEvent() function can be used to traverse each control in the map application interface.

[0200] S707. Execute the SortFocusLeftList sorting algorithm.

[0201] In a possible implementation, the onAccessibilityEvent() function can store clickable controls in an array. The onAccessibilityEvent() function can execute the SortFocusLeftList sorting algorithm and sort the controls based on the sorting principle in the above embodiment to obtain the UI control array. Exemplarily, taking the above Figure 5 as an example, the UI control array can be [502, 503, 505, 507, 504, 506, 508, 509].

[0202] S708. The travel service receives the knob event of the in-vehicle computer.

[0203] S709. The travel service transfers the knob event of the in-vehicle computer to the data channel module.

[0204] After receiving the knob event of the in-vehicle computer, the travel service can call the setMapKeyEvent() function to transfer the knob event of the in-vehicle computer to the data channel module.

[0205] S710. The data channel module transfers the knob event of the in-vehicle computer to the auxiliary service module.

[0206] The data channel module can call the keyEventForMap() function to transfer the knob event of the in-vehicle computer to the auxiliary service module.

[0207] S711. The auxiliary service module transfers the knob event of the in-vehicle computer to the auxiliary service adapter.

[0208] The auxiliary service module can call the dealWithAccessibleKey() function to transfer the knob event of the in-vehicle computer to the auxiliary service adapter.

[0209] S712. The auxiliary service adapter responds to the knob event.

[0210] The auxiliary service adapter can execute the corresponding function based on the response to the knob event of the in-vehicle computer.

[0211] In possible implementations, the knob events may include events such as rotating the knob clockwise, rotating the knob counterclockwise, and clicking the knob. The event of rotating the knob clockwise may execute the updateCurrentNextNode() function, the event of rotating the knob counterclockwise may execute the updateCurrentPreNode() function, and the event of clicking the knob may execute the dealCurrentKey() function.

[0212] Among them, the updateCurrentNextNode() function can be used to handle the event of rotating the knob clockwise, and can also be understood as the event of rotating the knob to the previous control of the current control. The updateCurrentPreNode() function can be used to handle the event of rotating the knob counterclockwise, and can also be understood as the event of rotating the knob to the next control of the current control. The dealCurrentKey() function can be used to handle the click event of the current control.

[0213] It can be understood that the present application embodiments do not limit the specific processes executed for different knob events and the naming of each function.

[0214] S713. The auxiliary service adapter updates the interface.

[0215] The auxiliary service adapter can call the updateStaticView() function to update the window and highlight the control where the focus is located.

[0216] S714. Call the addWindow() function.

[0217] The updateStaticView() function can further call the addWindow() function of the WMS to draw the window.

[0218] It can be understood that the WMS can call the relevant functions of the window information calculation class and the window information assistance class, and pass information such as the name of the covering window, the size and position of the control corresponding to the focus, etc.

[0219] The window information calculation class and the window information assistance class can calculate the size and position adapted by the control corresponding to the focus in the covering window, etc., and return the adaptation result to the WMS. Then, the WMS can draw the window based on the results calculated by the window information calculation class and the window information assistance class.

[0220] The specific process can refer to the relevant descriptions in the following steps S715 to S720.

[0221] S715. Call the setFrame() function and the setWindowAttrs() function.

[0222] The WMS can call the setFrame() function and the setWindowAttrs() function of the window information calculation class to calculate the size and position of the controls in the covering map window based on the size and position of the selected controls.

[0223] S716. The window information calculation class calculates the adaptation of the covering map window.

[0224] The window information calculation class can perform relevant calculations for the adaptation of the covering map window.

[0225] S717. Return the adaptation result.

[0226] After completing the calculation of the adaptation of the covering map window, the window information calculation class can return the adaptation result to the WMS.

[0227] S718. Call the calculateFrameInfo() function.

[0228] The WMS can call the calculateFrameInfo() function of the window information assistance class to calculate the size and position of the controls in the covering map window based on the size and position of the controls.

[0229] S719. The adaptation of the covering map window.

[0230] The window information assistance class can perform relevant calculations for the adaptation of the covering map window.

[0231] S720. Return the adaptation result.

[0232] After completing the calculation of the adaptation of the covering map window, the window information assistance class can return the adaptation result to the WMS.

[0233] It can be understood that the window information calculation class and the window information assistance class can be coordinated to execute together to achieve the adaptation of the covering map window. The execution of step S715 and step S718 can be in any order.

[0234] S721. Respond to the updateCurrentPreNode() event.

[0235] It can be understood that if the current knob is at the first control, for example, the first control can be the 402 control in the above Figure 4 and the auxiliary service adapter obtains the event that the knob rotates counterclockwise, indicating that the user wants to exit the current interface, then the updateCurrentPreNode() function can be executed.

[0236] The auxiliary service adapter can execute step S722 to send an instruction to the WMS to remove the covering map window.

[0237] The auxiliary service adapter calls the removeWindow() function to remove the cover map window.

[0238] The auxiliary service adapter can call the removeWindow() function of the WMS to remove the cover map window.

[0239] S723. The WMS returns the removal result.

[0240] After the WMS removes the cover map window, it can return the removal result to the auxiliary service adapter.

[0241] The method of the embodiment of the present application will be described in detail below through specific embodiments. The following embodiments can be combined with each other or implemented independently, and the same or similar concepts or processes may not be repeated in some embodiments.

[0242] Figure 8 The interface focus control method of the embodiment of the present application is shown. The method includes:

[0243] S801. The first electronic device establishes a communication connection with the second electronic device.

[0244] In the embodiment of the present application, the first electronic device can be any form of terminal device. For example, the electronic device can include a mobile phone, a tablet, etc., which are not limited in the embodiment of the present application.

[0245] The second electronic device can be understood as a device such as a car machine that can establish a communication connection with the first electronic device, which is not limited in the embodiment of the present application.

[0246] The process of the first electronic device establishing a communication connection with the second electronic device can refer to the relevant description in step S601 of the corresponding embodiment above, and will not be repeated. Figure 6

[0247] S802. The first electronic device transmits information for displaying a first interface to the second electronic device. The first interface includes a first control for entering a first application, and the information for displaying the first interface enables the second electronic device to display the first interface.

[0248] Figure 3 In the embodiment of the present application, the first interface can be understood as the interface displayed by the second electronic device before entering the first application. For example, the first interface can include the interface 301 in the corresponding embodiment above. The specific first interface is not limited in the embodiment of the present application.

[0249]

[0250] The first application can include any application in the first electronic device. For example, the first application can be a map application. The specific first application is not limited in the embodiment of the present application.​​The first control can be a control for entering the first application. For example, the first control can include the application icon 307 control and the map quick access 303 control in the above Figure 3 , etc., which are not limited in the embodiments of the present application.

[0251] S803. When a first event of triggering the first control by the knob of the second electronic device is obtained, the first electronic device transmits information for displaying a second interface to the second electronic device. The second interface includes a first window and an interface of the first application. The first window covers the interface of the first application, and the first window does not block the interface of the first application. A position corresponding to the target control in the first window is set to be triggerable by the knob, and the target control is a triggerable control in the interface of the first application.

[0252] In the embodiments of the present application, the first event can be understood as an event of the knob triggering the first control.

[0253] The second interface can be understood as the interface of the first application. For example, the second interface can include the interface 401 of the map application in the above Figure 4 . The specific second interface is not limited in the embodiments of the present application.

[0254] The first window can be understood as the cover window in the above embodiments.

[0255] The target control can be understood as one or more controls in the controls of the second interface that can be triggered or clicked.

[0256] It can be understood that when the first electronic device transmits information for displaying the second interface to the second electronic device, it can transmit the first window and the interface of the first application simultaneously, or separately, which is not limited in the embodiments of the present application. For example, the first electronic device can first transmit the first window to the second electronic device, and then transmit the interface of the first application to the second electronic device.

[0257] S804. When a second event generated by the rotation of the knob of the second electronic device is obtained, control the focus of the interface of the first application in the second electronic device to move from the second control to the third control; wherein, a first position in the first window covers the second control, a second position in the first window covers the third control, and the second position is a position adjacent to the first position set in the first window.

[0258] In the embodiments of the present application, the second event can be understood as an event generated by the rotation of the knob.

[0259] The second control can be understood as the control where the focus of the interface of the first application is located before the knob rotates. The third control can be understood as the control where the focus of the interface of the first application is located after the knob rotates.

[0260] The first position can be understood as the position corresponding to the second control in the cover image window. The second position can be understood as the position corresponding to the third control in the cover image window.

[0261] The second position being the position adjacent to the first position set in the first window may include that the second position is adjacent to the first position in terms of layout, or may include that the second position is adjacent to the first position in terms of the sorting rule in the above embodiment. The embodiments of the present application do not make any limitations.

[0262] In the embodiments of the present application, for an automobile supporting a knob, the rotation event or click event of the knob can be associated with a triggerable control in the first application interface. In this way, when the knob event is triggered, it can be converted into a selection or click operation on the triggerable control in the interface of the first application, thereby being able to control the focus of the first application and improving the user experience.

[0263] Optionally, before Figure 8 Based on the corresponding embodiment, before the first electronic device transmits the information for displaying the second interface to the second electronic device, it may further include: the first electronic device obtains the layout information of one or more controls when the interface of the first application is displayed on the second electronic device, and the layout information includes one or more of the following information: the name of the control, the size of the control, the position of the control, and one or more controls include a target control; the first electronic device determines the corresponding position of the target control in the first window based on the layout information of the target control.

[0264] In the embodiments of the present application, the process for the first electronic device to obtain the layout information of the first application can refer to the relevant descriptions in steps S605 to S607 of the above Figure 6 corresponding embodiment, and will not be elaborated here.

[0265] The process for the first electronic device to determine the corresponding position of the target control in the first window based on the layout information of the target control can refer to the relevant descriptions in the above Figure 7 corresponding embodiment, and will not be elaborated here.

[0266] The first electronic device can establish an association relationship between the layout information of the first application and the position of the first window. In this way, when the knob event is triggered, the movement of the focus of the first application can be controlled. Thus, the operation of triggering the rotation or click of the knob can be responded to in the cover image window, and the corresponding logic can be executed.

[0267] Optionally, before Figure 8 Based on the corresponding embodiment, before controlling the focus of the interface of the first application in the second electronic device to move from the second control to the third control, it may further include: the first electronic device sorts the target controls based on the layout information of the target controls, where, in the sorting, the second control and the third control are adjacent controls in the sorting.

[0268] In the embodiments of the present application, the process of sorting the target controls may refer to the relevant descriptions of the sorting rules in the above embodiments, which will not be elaborated herein.

[0269] By sorting the target controls, the movement control of the focus in the first interface can be achieved. In this way, when the knob rotates, the focus switching of the adjacent controls in the sorting can be realized.

[0270] Optionally, based on the corresponding embodiments, when sorting the target controls, one or more of the following sorting methods may be included: sorting according to the distances from each target control to the target position from near to far; sorting according to the order of rows or columns of the layout positions of each target control. Figure 8 In the embodiments of the present application, the target position may be understood as the position of a certain target control, or may be understood as a certain position on the interface of the first application. For example, a certain position on the interface of the first application may include the position of a certain corner of the interface of the first application. The specific target position is not limited in the embodiments of the present application.

[0271] Sorting according to the distances from each target control to the target position from near to far may include the relevant descriptions of the optimized sorting rules in the above embodiments, and sorting according to the order of rows or columns of the layout positions of each target control may include the relevant descriptions of the non-optimized sorting rules in the above embodiments, which will not be elaborated herein.

[0272] By sorting the target controls, the focus switching of the adjacent controls in the sorting can be realized, so as to control the movement of the focus in the first interface.

[0273] Optionally, based on the corresponding embodiments, the electronic device further includes a first service, a window management service WMS, and a first module. After obtaining the second event generated by the rotation of the knob of the second electronic device, it may further include: the first service responds to the second event and calls the addWindow() function, and the addWindow() function is used to instruct the window management service WMS to update the first window; the window management service WMS calls the preset interface of the first module, and the preset interface is used to instruct the first module to calculate the information of the second position in the first window; the window management service WMS updates the first window based on the information of the second position obtained by the first module, wherein the second position in the first window is highlighted.

[0274] Optionally, Figure 8 In the corresponding embodiments, the first service may be understood as the travel service in the above corresponding embodiments.

[0275] In the embodiments of the present application, the first service may be understood as the above Figure 7 The first module may be understood as the above

[0276] In the corresponding embodiments, Figure 7The window information calculation class ComputerFrameInfo and the window information assistance class IhnComputerFrameHelper in the corresponding embodiment.

[0277] The process of the first service responding to the second event can refer to the relevant descriptions above Figure 7 for steps S708 to S713 in the corresponding embodiment, which will not be elaborated here.

[0278] The process of the window management service WMS calling the preset interface of the first module and updating the first window based on the information of the second position obtained by the first module can refer to the relevant descriptions above Figure 7 for steps S714 to S720 in the corresponding embodiment, which will not be elaborated here.

[0279] Highlighting may include high - lighting, where the high - lighting can refer to the relevant description above Figure 6 for step S613 in the corresponding embodiment, which will not be elaborated here.

[0280] Through the interaction among the first service, the window management service WMS, and the first module, the calculation and drawing of the covering map window based on the knob - based time can be realized.

[0281] Optionally, on the basis of the Figure 8 corresponding embodiment, the first service responding to the second event may include: if the second event is a clockwise rotation of the knob event, the first service executes a first function, and the first function is used to control the focus of the interface of the first application in the second electronic device to move from the second control to the third control, and the sorting of the second control is higher than that of the third control; if the second event is a counter - clockwise rotation of the knob event, the first service executes a second function, and the second function is used to control the focus of the interface of the first application in the second electronic device to move from the second control to the third control, and the sorting of the third control is higher than that of the second control.

[0282] In the embodiment of the present application, the first function can be understood as the Figure 7 updateCurrentNextNode() function in the corresponding embodiment, and the second function can be understood as the Figure 7 updateCurrentPreNode() function in the corresponding embodiment, which will not be elaborated here.

[0283] The specific processing processes for the clockwise rotation of the knob event and the counter - clockwise rotation of the knob event can refer to the relevant descriptions above Figure 7 for the relevant description in step S712 of the corresponding embodiment, which will not be elaborated here. In this way, by distinguishing the rotation direction of the knob, the jump between the controls on the interface of the first application can be realized.

[0284] Optionally, based on the Figure 8 corresponding embodiment, the method may further include: when obtaining a third event that a knob of a second electronic device triggers a third control, transmitting information for displaying a third interface to the second electronic device, where the third interface is an interface that should be displayed after the third control is triggered in the interface of a first application.

[0285] In the embodiments of the present application, the third control may be understood as a target control that can be clicked.

[0286] The third event may be understood as an event that the knob triggers the third control.

[0287] It can be understood that when the click event of the knob on the third control is triggered, the click event of the third control can be responded to in the first application, so that the third interface after clicking the third control can be displayed.

[0288] Optionally, based on the Figure 8 corresponding embodiment, the method may further include: when obtaining a fourth event generated by rotating the knob of the second electronic device, the first electronic device transmits information for displaying a first interface to the second electronic device for the second electronic device to return to the first interface; where when the fourth event is obtained, the focus of the interface of the first application is on a fourth control, and the fourth control is a control with adjacent controls on only one side.

[0289] In the embodiments of the present application, the fourth event may be understood as an event generated by rotating the knob.

[0290] The fourth control may be understood as the first or the last one in the control sorting. In this way, when the knob triggers the fourth control to jump to the side without adjacent controls, the cover map window can be exited. The fourth control may include the above Figure 4 navigation indication 402 control.

[0291] Optionally, based on the Figure 8 corresponding embodiment, after obtaining a third event that the knob of the second electronic device triggers a second position in a first window, it may further include: a first service executes a first function based on the fourth event and calls the removeWindow() function of the window management service WMS; the window management service WMS removes the first window.

[0292] In the embodiments of the present application, the process of the window management service WMS removing the first window may refer to the relevant descriptions of steps S721 to S723 in the above Figure 7 corresponding embodiment and will not be elaborated here.

[0293] When exiting the interface of the first application, the first window can be removed in a timely manner, so that other interface controls are not triggered by the knob, enabling the knob event to correspond to the function displayed on the interface and enhancing the user experience.

[0294] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or reject.

[0295] The above mainly introduces the solution provided by the embodiments of this application from the perspective of the method. To implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the method steps of each example described in the embodiments disclosed herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0296] The embodiments of this application can divide the device for implementing the method into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of this application is illustrative, only a logical functional division, and there can be other division methods in actual implementation.

[0297] As Figure 9 shown is a schematic structural diagram of a chip provided by an embodiment of this application. The chip 900 includes one or more than two (including two) processors 901, a communication line 902, a communication interface 903, and a memory 904.

[0298] In some embodiments, the memory 904 stores the following elements: executable modules or data structures, or subsets thereof, or extended sets thereof.

[0299] The method described in the embodiments of the present application above can be applied to or implemented by the processor 901. The processor 901 may be an integrated circuit chip with the ability to process signals. In the implementation process, the steps of the above method can be completed by the integrated logic circuit in the hardware of the processor 901 or the instructions in the form of software. The above-mentioned processor 901 may be a general-purpose processor (e.g., a microprocessor or a conventional processor), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate, transistor logic devices, or discrete hardware components. The processor 901 can implement or execute the various processing-related methods, steps, and logic block diagrams disclosed in the embodiments of the present application.

[0300] The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or implemented and completed by a combination of the hardware and software modules in the decoding processor. Among them, the software module can be located in a mature storage medium in the art such as a random access memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable read-only memory (EEPROM). This storage medium is located in the memory 904, and the processor 901 reads the information in the memory 904 and combines its hardware to complete the steps of the above method.

[0301] Communication can be carried out among the processor 901, the memory 904, and the communication interface 903 through the communication line 902.

[0302] In the above embodiments, the instructions stored in the memory for the processor to execute can be implemented in the form of a computer program product. Among them, the computer program product can be pre-written in the memory in advance, or downloaded and installed in the memory in the form of software.

[0303] Embodiments of the present application also provide a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrating one or more available media. For example, the available medium may include magnetic media (such as floppy disks, hard disks, or magnetic tapes), optical media (such as digital versatile discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)).

[0304] Embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The computer-readable medium may include computer storage media and communication media, and may also include any medium that can transfer a computer program from one place to another. The storage medium may be any target medium accessible by a computer.

[0305] As a possible design, the computer-readable medium may include a compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disc memories; the computer-readable medium may include magnetic disk memories or other magnetic disk storage devices. Moreover, any connecting line may also be appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, magnetic disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks usually reproduce data magnetically, while optical discs use lasers to reproduce data optically.

[0306] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processing unit of the computer or other programmable data processing device generate means for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or multiple blocks.

Claims

1. An interface focus control method, characterized in that, The method includes: The first electronic device establishes a communication connection with the second electronic device; The first electronic device transmits information for displaying a first interface to the second electronic device. The first interface includes a first control for entering a first application, and the information for displaying the first interface causes the second electronic device to display the first interface; When a first event of triggering the first control by a knob of the second electronic device is obtained, the first electronic device transmits information for displaying a second interface to the second electronic device. The second interface includes a first window and an interface of the first application. The first window covers the interface of the first application, and the first window does not block the interface of the first application. A position corresponding to a target control in the first window is set to be triggerable by the knob, and the target control is a triggerable control in the interface of the first application; When a second event generated by the rotation of the knob of the second electronic device is obtained, the focus of the interface of the first application in the second electronic device is controlled to move from a second control to a third control; wherein, a first position in the first window covers the second control, a second position in the first window covers the third control, and the second position is an adjacent position to the first position set in the first window.

2. The method according to claim 1, characterized in that, Before the first electronic device transmits information for displaying the second interface to the second electronic device, it further includes: The first electronic device obtains layout information of one or more controls when the interface of the first application is displayed in the second electronic device. The layout information includes one or more of the following information: the name of the control, the size of the control, the position of the control, and the one or more controls include the target control; The first electronic device determines the corresponding position of the target control in the first window based on the layout information of the target control.

3. The method according to claim 2, wherein Before controlling the focus of the interface of the first application in the second electronic device to move from the second control to the third control, it further includes: The first electronic device sorts the target controls based on the layout information of the target control. In the sorting, the second control and the third control are adjacent controls in the sorting.

4. The method according to claim 3, wherein When sorting the target controls, it includes one or more of the following sorting methods: Sorting according to the distance from each target control to a target position from near to far; Sorting according to the order of rows or columns of the layout positions of the target controls.

5. The method according to any one of claims 1-4, characterized in that, The electronic device further includes a first service, a window management service WMS, and a first module. After a second event generated by the rotation of the knob of the second electronic device is obtained, it further includes: The first service responds to the second event and calls the addWindow() function, and the addWindow() function is used to instruct the window management service WMS to update the first window; The window management service WMS calls a preset interface of the first module, and the preset interface is used to instruct the first module to calculate the information of the second position in the first window; The window management service WMS updates the first window based on the information of the second position obtained by the first module, where the second position in the first window is highlighted.

6. The method according to claim 5, wherein The first service responds to the second event, including: If the second event is an event of rotating the knob clockwise, the first service executes a first function, and the first function is used to control the focus of the interface of the first application in the second electronic device to move from the second control to the third control, and the sorting of the second control is higher than that of the third control; If the second event is an event of rotating the knob counterclockwise, the first service executes a second function, and the second function is used to control the focus of the interface of the first application in the second electronic device to move from the second control to the third control, and the sorting of the third control is higher than that of the second control.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: When obtaining a third event that the third control is triggered by the knob of the second electronic device, transmit information for displaying a third interface to the second electronic device, where the third interface is the interface that should be displayed after the third control is triggered in the interface of the first application.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: When obtaining a fourth event generated by rotating the knob of the second electronic device, the first electronic device transmits information for displaying the first interface to the second electronic device for the second electronic device to return to the first interface; where when obtaining the fourth event, the focus of the interface of the first application is on a fourth control, and the fourth control is a control with adjacent controls on only one side.

9. The method according to claim 8, wherein After obtaining a third event that the second position in the first window is triggered by the knob of the second electronic device, it further includes: The first service executes a first function based on the fourth event and calls the removeWindow() function of the window management service WMS; The window management service WMS removes the first window.

10. An electronic device, characterized in that, The electronic device includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program code, and the computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the electronic device to execute the method according to any one of claims 1 to 9.

11. A communication system, characterized in that, The communication system includes: a first electronic device and a second electronic device, the second electronic device includes a knob, the first electronic device is used to execute the method according to any one of claims 1 to 9, the second electronic device is used to receive the interface information transmitted by the first electronic device and perform interface display based on the interface information, and the second electronic device is further used to transmit the event triggered by the knob to the first electronic device.

12. A chip system, characterized in that, The chip system is applied to an electronic device, and the chip system includes one or more processors, and the one or more processors are used to call computer instructions to cause the electronic device to execute the method according to any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when run on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 9.

14. A computer program product, characterized in that, The computer program product includes computer program code that, when run on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 9.

Images