Subprogram sharing method, subprogram sharing device, electronic device, and computer program

Abstract

An embodiment of the present invention discloses a subprogram sharing method, device, electronic device, and storage medium. In the embodiment of the present invention, a subprogram sharing page of a subprogram is displayed. In response to a trigger operation on a target sharing method selection control among the sharing method selection controls, subprogram-related information of the subprogram can be acquired from a target smart vehicle and a subprogram sharing request can be sent to the target smart vehicle based on a communication method corresponding to the target sharing method selection control. The subprogram sharing page includes at least one sharing method selection control, each of which corresponds to one communication method. The subprogram sharing request includes subprogram-related information, and a target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information.

Description

Technical Field

[0001] This application claims priority based on a Chinese patent application filed with the China National Intellectual Property Administration on January 31, 2023, with an application number of 202310129492.3 and an invention title of "Sub-program Sharing Method, Apparatus, Electronic Device, and Storage Medium between In-vehicle Devices", and all its contents are incorporated herein by reference.

[0002] The present invention relates to the field of smart vehicles, and specifically, to a sub-program sharing method, apparatus, electronic device, and storage medium.

Background Art

[0003] With the rapid development of the current economy and science and technology, smart vehicles have become increasingly common in people's daily lives. For the driver of a smart vehicle, it is difficult to perform complex and accurate operations on the smart vehicle while driving the vehicle. However, since a non-driver can use an electronic device to share data, the driver can also obtain relevant information.

[0004] In some methods of sharing data with a smart vehicle, a non-driver performs data transmission through a Bluetooth connection between an electronic device and the smart vehicle.

Summary of the Invention

Problems to be Solved by the Invention

[0005] Embodiments of the present invention provide a sub-program sharing method, apparatus, electronic device, and storage medium that can realize sub-program sharing between a smart vehicle and a user terminal in various communication methods and improve the usage experience of users of the smart vehicle.

Means for Solving the Problems

[0006] Embodiments of the present invention provide a sub-program sharing method executed by a terminal device. The sub-program sharing method includes A step of displaying a subprogram sharing page of a subprogram, wherein the subprogram sharing page includes at least one sharing method selection control, and each of the sharing method selection controls corresponds to one type of communication method. In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the steps include obtaining information from the target smart vehicle and the subprogram-related information of the subprogram, The method includes the step of sending a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information.

[0007] In embodiments of the present invention, other subprogram sharing methods executed by the smart vehicle are further provided. The subprogram sharing method is: A step of receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram to be shared by the terminal device, the target sharing method selection control is included in the subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page includes at least one sharing method selection control, each of the sharing method selection controls corresponds to one type of communication method, and the terminal device, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, obtains the target smart vehicle side and the subprogram-related information of the subprogram, and then transmits the subprogram sharing request. Based on the subprogram-related information, the steps include displaying a shared acceptance confirmation page, The process includes the step of displaying a target subprogram page corresponding to the subprogram based on the subprogram-related information in response to a user's sharing request.

[0008] Embodiments of the present invention further provide a subprogram sharing device applicable to terminal equipment. The subprogram sharing device is A first page display unit for displaying a subprogram sharing page of a subprogram, wherein the subprogram sharing page includes at least one sharing method selection control, and each of the sharing method selection controls corresponds to one type of communication method, and the first page display unit, In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the target smart vehicle and an information acquisition unit that acquires subprogram-related information of the subprogram, An information transmission unit that transmits a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes the subprogram-related information, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information.

[0009] In embodiments of the present invention, other subprogram sharing devices applied to the smart vehicle side are further provided. The subprogram sharing device is A request receiving unit that receives a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared by the terminal device, the target sharing method selection control is included in the subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page includes at least one sharing method selection control, each of the sharing method selection controls corresponds to one type of communication method, and the terminal device, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, transmits the subprogram sharing request after obtaining the target smart vehicle side and the subprogram-related information of the subprogram. Based on the aforementioned subprogram-related information, Reception A second page display unit that displays a confirmation page, The system includes a subprogram page display unit that, in response to a user's sharing request, displays a target subprogram page corresponding to the subprogram based on the subprogram-related information.

[0010] In embodiments of the present invention, an electronic device comprising memory and a processor is further provided. The memory stores an application program, and the processor performs a step of any one of the subprogram sharing methods provided in embodiments of the present invention by executing the application program in the memory.

[0011] In embodiments of the present invention, a computer-readable storage medium storing a plurality of instructions is further provided. The instructions, when loaded by a processor, are configured to execute a step of any one of the subprogram sharing methods provided in embodiments of the present invention.

[0012] Embodiments of the present invention further provide a computer program product including a computer program or instruction. When the computer program or instruction is executed by a processor, it enables the implementation of a step of any one of the subprogram sharing methods provided in embodiments of the present invention. [Brief explanation of the drawing]

[0013] [Figure 1] This is a schematic diagram of a scenario for a subprogram sharing method provided in an embodiment of the present invention. [Figure 2] This is a schematic flowchart of the subprogram sharing method provided in an embodiment of the present invention. [Figure 3] This is a schematic diagram of a subprogram sharing page provided in an embodiment of the present invention. [Figure 4] This is another schematic diagram of a subprogram sharing page provided in an embodiment of the present invention. [Figure 5] This is a schematic diagram of the technical realization of establishing a Bluetooth communication connection as provided in an embodiment of the present invention. [Figure 6] This is a schematic flowchart of another subprogram sharing method provided in an embodiment of the present invention. [Figure 7] This is a schematic diagram of the technical implementation of the subprogram sharing process provided in an embodiment of the present invention. [Figure 8] This is a schematic diagram of another technical realization of the subprogram sharing process provided in the embodiment of the present invention. [Figure 9] This is another schematic flowchart of the subprogram sharing method provided in an embodiment of the present invention. [Figure 10] This is a schematic diagram of the configuration of a subprogram sharing device provided in an embodiment of the present invention. [Figure 11] This is a schematic diagram of the configuration of another subprogram sharing device provided in an embodiment of the present invention. [Figure 12] This is a schematic diagram of another configuration of the subprogram sharing device provided in an embodiment of the present invention. [Figure 13]It is a schematic diagram of the configuration of an electronic device provided in an embodiment of the present invention.

Modes for Carrying Out the Invention

[0014] Hereinafter, while referring to the drawings of the embodiments of the present invention, the configurations of the embodiments of the present invention will be clearly and completely described. As is clear, the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments obtained by those skilled in the art from the embodiments of the present invention without creative labor belong to the protection scope of the present invention.

[0015] In some methods of sharing data with a smart vehicle, a non-driver performs data transmission via a Bluetooth connection between an electronic device and the smart vehicle. However, in this configuration, only sharing of sub-programs between the smart vehicle and the electronic device can be realized by a single Bluetooth communication method, the type of data that can be shared is single, the sharing effect of data such as audio and video is poor, and it will affect the usage experience of the user of the smart vehicle.

[0016] Embodiments of the present invention provide a sub-program sharing method, apparatus, electronic device, and computer-readable storage medium. The sub-program here is also called a mini-program or a small scene (in in-vehicle devices, it is usually called a small scene). Specifically, embodiments of the present invention provide a sub-program sharing method applied to a sub-program sharing apparatus, and this sub-program sharing apparatus may be incorporated into an electronic device.

[0017] The electronic device may be a device such as a terminal, including but not limited to a portable terminal and a stationary terminal. Here, the portable terminal includes but is not limited to a smart phone, a smart watch, a tablet computer, a notebook computer, a smart in-vehicle device , a smart vehicle, etc. The stationary terminal includes but is not limited to a desktop computer, a smart TV, etc.

[0018] The electronic device may be a server or other device. The server may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and base cloud computing services such as big data and artificial intelligence platforms, but is not limited to these.

[0019] The subprogram sharing method of the embodiment of the present invention may be implemented by a server, or it may be implemented jointly by a terminal and a server.

[0020] The following explanation will describe the method using an example where the sharing initiator, the smart vehicle, and the cloud jointly implement the subprogram sharing method.

[0021] As shown in Figure 1, the subprogram sharing system provided in the embodiment of the present invention includes a sharing initiator (i.e., terminal device) 10, a smart vehicle side 20, and a cloud side (server) 30, and the sharing initiator 10, the smart vehicle side 20, and the cloud side 30 are connected via a network, for example, via a wired or wireless network.

[0022] Here, the sharing initiator 10 can display the subprogram sharing page of the subprogram, and in response to a target vehicle sharing operation for the target sharing method selection control among the sharing method selection controls, obtain subprogram-related information of the subprogram, and send a subprogram sharing request to the cloud side 30 corresponding to the target smart vehicle side based on the communication method corresponding to the target sharing method selection control. The subprogram sharing page includes the content information of the subprogram and at least one sharing method selection control, and each sharing method selection control corresponds to one type of communication method. The target smart vehicle side responds to the target vehicle sharing operation, and the subprogram sharing request includes subprogram-related information of the subprogram that is being requested to be shared by the sharing initiator 10.

[0023] The cloud-side 30 can send a subprogram sharing request to the smart vehicle-side 20.

[0024] The smart vehicle side 20 can receive a subprogram sharing request sent from the cloud side 30, which contains subprogram-related information of a subprogram that is requested to be shared by the sharing initiator, and can display a sharing acceptance confirmation page based on the subprogram-related information, and in response to the user's sharing acceptance operation, it can display the target subprogram page corresponding to the subprogram based on the subprogram-related information.

[0025] To make it easier to understand, in some embodiments, the sharing initiator 10 and the smart vehicle side 20 may communicate directly.

[0026] Here, the sharing initiator 10 displays the subprogram sharing page of the subprogram, and in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, it can obtain the target smart vehicle and the subprogram-related information of the subprogram, and send a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control. The subprogram sharing page includes the content information of the subprogram and at least one sharing method selection control, each of which corresponds to one type of communication method. The subprogram sharing request includes the subprogram-related information of the subprogram that is being requested to be shared by the sharing initiator 10.

[0027] The smart vehicle side 20 can receive a subprogram sharing request sent from the sharing initiator side 10, which contains subprogram-related information of the subprogram that the sharing initiator side 10 is requesting to be shared, and can display a sharing acceptance confirmation page based on the subprogram-related information, and in response to the user's sharing acceptance operation, it can display a target subprogram page corresponding to the subprogram based on the subprogram-related information.

[0028] Each of these will be explained in detail below. Note that the order of description of the following examples is not limited to any preferred order.

[0029] Embodiments of the present invention will be described from the perspective of a subprogram sharing device. Specifically, this subprogram sharing device may be incorporated into a terminal.

[0030] As shown in Figure 2, the subprogram sharing method in this embodiment is executed by the sharing initiator (i.e., the terminal device). The specific flow may be as follows.

[0031] Step 201 displays the subprogram sharing page of the subprogram, which contains the subprogram's content information and at least one sharing method selection control, each of which corresponds to one type of communication method.

[0032] Here, the subprogram is a program that operates in accordance with the host program. In embodiments of the present invention, the subprogram may be a program that depends on any host program.

[0033] Generally, in a computer environment, the software environment on which software (for example, the miniprogram in this application) depends is called the host environment (host program). The host environment (host program) may be an operating system, a server program, an application program, etc.

[0034] In this embodiment, the types of host programs and subprograms are not limited. For example, the host program may be an instant messaging client program, a music playback program, or the like.

[0035] Here, the subprogram sharing page is a page where users of a subprogram can choose to share the subprogram with themselves or other users. For example, the subprogram sharing page may be as shown in Figure 3 or Figure 4.

[0036] In some embodiments, the sharing method selection control can be used by the user to select the communication method when sharing a subprogram. For example, the sharing method selection control may be the control called "Transmit via Bluetooth" in Figure 3 or Figure 4. Alternatively, the sharing method selection control may be the control called "Share to In-Vehicle Device" in Figure 4.

[0037] Here, the communication methods corresponding to the different sharing method selection controls may be different. For example, the control called "Transmit via Bluetooth" in Figure 3 or Figure 4 may correspond to the Bluetooth communication method, while the control called "Share with in-vehicle unit" in Figure 4 may correspond to the long-range wireless communication method, and so on.

[0038] To make it easier to understand, the subprogram sharing page may include a sharing method selection control that supports other communication methods. For example, the subprogram sharing page may include a sharing method selection control that supports wired communication methods. The embodiments of the present invention are not limited thereto.

[0039] In step 202, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the target smart vehicle and the subprogram-related information of the subprogram are obtained.

[0040] Here, the target sharing method selection control is the sharing method selection control triggered by the user initiating the sharing in the in-vehicle device subprogram sharing process.

[0041] For example, a user can trigger a control called "Send via Bluetooth" in Figure 3 or Figure 4. In this case, the control called "Send via Bluetooth" is the target sharing method selection control.

[0042] Specifically, subprogram-related information may include, but is not limited to, information such as the subprogram identifier (Appid), page information, and page parameters (params) corresponding to the subprogram. For example, the subprogram identifier may be the program ID corresponding to the subprogram in the host program.

[0043] To make it easier to understand, the target sharing method selection control may directly correspond to one smart vehicle. For example, the control called "Transmit via Bluetooth" in Figure 3 may correspond to one smart vehicle. In this case, the target smart vehicle (i.e., the smart vehicle corresponding to the target sharing method selection control) can be directly obtained in response to a trigger operation on the target sharing method selection control among the sharing method selection controls.

[0044] Alternatively, the target sharing method selection control may correspond to a single shared vehicle selection page, which includes a vehicle selection control corresponding to at least one smart vehicle. In this case, obtaining the target smart vehicle in response to a trigger operation on the target sharing method selection control among the sharing method selection controls would specifically involve: Steps include: displaying a shared vehicle selection page in response to a trigger operation on a target shared vehicle selection control among the shared vehicle selection controls, wherein the shared vehicle selection page includes a vehicle selection control corresponding to at least one smart vehicle side; The method may include the step of determining a target smart vehicle in response to a trigger operation on a target vehicle selection control among the vehicle selection controls, wherein the target smart vehicle corresponds to the target vehicle selection control.

[0045] To make it easier to understand, if the sharing initiator can communicate with multiple smart vehicles, the user can determine the target smart vehicle from among the smart vehicles by operating the vehicle selection control.

[0046] For example, the sharing initiator can communicate with smart vehicle 1 using Bluetooth communication and with smart vehicle 2 and smart vehicle 3 using long-range wireless communication. The shared vehicle selection page may include vehicle selection controls corresponding to smart vehicle 1, smart vehicle 2, and smart vehicle 3. When a user triggers a vehicle selection control corresponding to smart vehicle 2, the vehicle selection control corresponding to smart vehicle 2 becomes the target vehicle selection control, and smart vehicle 2 becomes the target smart vehicle.

[0047] Here, the trigger operation may include operations such as clicking, double-clicking, long-pressing, and sliding. In some examples, a predetermined quick operation may be used to trigger the control. For example, the device user may be configured to recognize a single press of the volume down key as a single trigger operation for selecting a target sharing method control. The present invention does not limit specific quick operations.

[0048] In step 203, a subprogram sharing request is sent to the target smart vehicle based on the communication method corresponding to the target sharing method selection control. The subprogram sharing request includes subprogram-related information for the subprogram that is being requested to be shared by the sharing initiator, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information.

[0049] In some embodiments, the target sharing method selection control may support a Bluetooth communication method. Specifically, in step 203, sending a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control means: A step of generating a Bluetooth sharing event based on the Bluetooth communication method and subprogram-related information, The process may also include the step of sending a Bluetooth sharing event to the target smart vehicle via a Bluetooth communication connection between the target smart vehicle and the sharing initiator.

[0050] Here, a Bluetooth sharing event is a subprogram sharing event generated when the sharing initiator shares a subprogram with the target smart vehicle using the Bluetooth communication method.

[0051] To make it easier to understand, before sending a Bluetooth sharing event to the target smart vehicle via a Bluetooth communication connection, a Bluetooth communication connection must first be established between the target smart vehicle and the sharing initiator.

[0052] Specifically, as shown in Figure 5, the target smart vehicle and the sharing initiator need to perform device discovery (i.e., steps 1, 2, and 3). After that, the target smart vehicle and the sharing initiator may perform device connection through steps 4, 5, and 6. In this way, a Bluetooth communication connection is established.

[0053] After a Bluetooth communication connection is established, if the sharing initiator voluntarily invokes the sharing interface on the target smart vehicle side, the sharing initiator may transmit subprogram-related information (e.g., information such as Appid, page information, and page parameters) to the target smart vehicle side (in-vehicle device side) via the Bluetooth communication connection.

[0054] In some other embodiments, the target sharing method selection control may support a long-range wireless communication method. Specifically, in step 203, sending a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control means: A step of generating a long-distance shared event based on the long-distance wireless communication method and subprogram-related information, The steps include determining the cloud side that corresponds to the target smart vehicle, The process may include the step of sending a remote sharing event to the cloud side via a remote communication connection between the cloud side and the sharing initiator, wherein the remote sharing event is sent by the cloud side to the target smart vehicle side.

[0055] Here, a long-range sharing event is a subprogram sharing event generated when the sharing initiator shares a subprogram with the target smart vehicle using a long-range wireless communication method. As can be understood, when long-range subprogram sharing is required, Bluetooth technology cannot be used. In this case, subprogram sharing may be achieved by long-range wireless communication, such as wireless network communication.

[0056] In the wireless network communication process, the participating nodes in the entire network include the target smart vehicle, the cloud, and the sharing initiator, and these three entities are independent entities within the system.

[0057] Generally, if the sharing initiator has a need for subprogram sharing, that is, when a subprogram (miniprogram) is opened, the user can click the "More" button in the upper right corner of the subprogram to bring up more options. If the user selects the "Share to In-Vehicle Device" button, the cloud-side interface is invoked, and subprogram-related information such as the subprogram's AppID, page information, and page parameters (params) is transmitted directly to the cloud via a long-distance communication connection. The cloud side may also transfer the subprogram-related information directly to the target smart vehicle. The target smart vehicle then parses this information to obtain all the parameters necessary to open the subprogram.

[0058] Alternatively, the cloud side may analyze subprogram-related information to obtain all the parameters necessary to open the subprogram, and then transmit these parameters to the target smart vehicle.

[0059] In some examples, a reliable and secure trust relationship authentication may be established between the target smart vehicle, the cloud, and the sharing initiator to ensure the security of the subprogram sharing process. Specifically, sending remote sharing events to the cloud via a remote communication connection between the cloud and the sharing initiator is possible. The steps include: sending the first identity authentication information of the sharing initiator to the cloud side via a long-distance communication connection between the cloud side and the sharing initiator, wherein the identity check of the sharing initiator is performed by the cloud side based on the first identity authentication information; The steps include receiving the identity check result from the sharing initiator, which is returned from the cloud side, The process may also include the step of sending a remote sharing event to the cloud in response to the identity check result being successful.

[0060] In practical applications, corresponding digital certificates may be issued to the target smart vehicle, the cloud, and the sharing initiator's devices and individuals, and these certificates may be used as proof of identity authentication to verify the other party's digital signature. This authentication method can recognize the identity of individual devices and allows for flexible control over the scope and expiration date of use.

[0061] Here, the first identity authentication information may be a digital certificate from the sharing initiator. The identity check result may be information indicating that the first identity authentication information is correct, i.e., the check passed, or information indicating that the first identity authentication information is incorrect, i.e., the check failed. If the identity check result is a pass, the remote sharing event is sent to the cloud side; if the identity check result is a fail, sending the remote sharing event to the cloud side is not permitted.

[0062] In some embodiments, identity authentication may be performed based on the host program's user information. For example, the host program may be an instant messaging client. In this case, any user registered with the instant messaging program can use the subprogram sharing method of this embodiment.

[0063] In some embodiments, the transmission of a subprogram sharing request may be implemented by an interface call method. Specifically, in step 203, transmitting a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control means: The steps include calling the shared interface on the target smart vehicle side based on the communication method corresponding to the target sharing method selection control, The process may also include the step of sending a subprogram sharing request to the target smart vehicle via a shared interface.

[0064] In some embodiments, when sharing subprograms using Bluetooth communication, the Bluetooth communication method can trigger detection of currently received data by the sharing interface on the target smart vehicle side, and a subprogram sharing request can be obtained from the currently received data.

[0065] For example, a detection event may be set in the shared interface. If it is recognized as an event directed to the shared interface, the message received via Bluetooth is retrieved, the message is parsed, a subprogram sharing request is obtained, and then subprogram-related information, such as the subprogram's AppID, page information, and page parameters (params), is parsed from the subprogram sharing request.

[0066] Specifically, when calling a shared interface using Bluetooth communication, the information transmitted may include an identifier indicating that the current information is being transmitted via Bluetooth, or an identifier indicating that the information is being transmitted via the shared interface.

[0067] In some embodiments, when sharing subprograms using long-range wireless communication, the sharing interface may open the subprogram call page interface. Subsequently, the cloud-side network communication call interface implements the subprogram pull-up.

[0068] As shown in Figure 6, the embodiment of the present invention provides another subprogram sharing method that is executed by the smart vehicle. The specific flow may be as follows.

[0069] In step 601, the sharing initiator receives a subprogram sharing request that contains subprogram-related information for the subprogram being requested for sharing.

[0070] In the embodiments of the present invention, the meanings of some terms are the same as those in the subprogram sharing method described above, and for specific implementation details, please refer to the description of the embodiments described above.

[0071] Here, a subprogram sharing request is request information that the sharing initiator requests to share a subprogram with the smart vehicle. The sharing initiator sends a subprogram sharing request based on the communication method corresponding to the target sharing method selection control. The target sharing method selection control is included in the subprogram sharing page of the subprogram displayed to the sharing initiator, and the subprogram sharing page includes at least one sharing method selection control, each of which corresponds to one type of communication method. In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the sharing initiator obtains the target smart vehicle and the subprogram-related information of the subprogram, and then sends a subprogram sharing request.

[0072] In some embodiments, receiving a subprogram sharing request in step 601, which includes subprogram-related information of the subprogram being requested for sharing from the sharing initiator, specifically means: The smart vehicle side may include a step of receiving a subprogram sharing request sent from the cloud side, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is being shared by the sharing initiator and second identity authentication information from the cloud side.

[0073] In practical applications, corresponding digital certificates may be issued to the target smart vehicle, the cloud, and the sharing initiator's devices and individuals, and these certificates may be used as proof of identity authentication to verify the other party's digital signature. This authentication method can recognize the identity of individual devices and allows for flexible control over the scope and expiration date of use.

[0074] Here, the second identity authentication information may be a digital certificate on the cloud side.

[0075] Accordingly, after receiving a subprogram sharing request in step 601, the subprogram sharing method provided in the embodiment of the present invention is: Based on the second identity authentication information, an identity check is performed on the cloud side, and the corresponding identity check results are obtained from the cloud side. The process may further include the step of obtaining subprogram-related information by parsing the subprogram sharing request in response to the identity check result being successful.

[0076] The identity check result may indicate that the second identity authentication information is correct, i.e., the check passed, or it may indicate that the second identity authentication information is incorrect, i.e., the check failed. If the identity check result is a pass, subprogram-related information may be obtained by analyzing the subprogram sharing request. If the identity check result is a fail, analysis of the subprogram sharing request is not permitted.

[0077] As shown in Figure 7, assuming a secure connection is established, if the mobile phone has a need to share a subprogram, i.e., if a subprogram (referred to as a small scene in Figure 7) is opened, the user can click the "More" button in the upper right corner to bring up more options. Selecting the "Share to In-Car Device" button will invoke the cloud-side interface, and transmission will take place over the network. Identity verification and authorization verification may be performed before calling the interface. To improve the security of the communication, the interface call is made only after the verification is successful.

[0078] In some embodiments, the Microsoft Office Shell Point Server Software Development Kit (MossSDK) may be designed to have an exposed interface for receiving subprogram parameters, which may include information such as the subprogram's Appid, page information, and page parameters (params).

[0079] In some embodiments, receiving a subprogram sharing request in step 601 specifically means The steps include receiving external transmission data and detecting the external transmission data using a detection code for a subprogram shared event, The method may also include the step of obtaining a subprogram sharing request corresponding to a subprogram sharing event by analyzing the externally transmitted data if the externally transmitted data contains a subprogram sharing event.

[0080] As shown in Figure 8, detection code for subprogram (referred to as small scenes in Figure 8) sharing events can be designed within MossSDK. If a subprogram sharing event is recognized as being directed to MossSDK, the message received via Bluetooth is retrieved and message analysis is performed.

[0081] In some embodiments, the code for detecting subprogram sharing events may be a Bluetooth event detection method designed in MossSDK, such as getSharedMiniProInfoByBlueTooth(). The code for detecting subprogram sharing events can obtain all information about the shared subprogram from the sharing initiator, i.e., subprogram-related information, and by parsing it, all parameters that allow the subprogram to be opened can be obtained.

[0082] Step 602 displays a sharing acceptance confirmation page based on the subprogram-related information.

[0083] Here, the sharing acceptance confirmation page may be a page displayed on the smart vehicle side during the process of confirming whether or not the user on the smart vehicle side accepts the sharing of the subprogram.

[0084] In some embodiments, the sharing acceptance confirmation page may include a sharing acceptance confirmation control and / or a sharing rejection control, etc. The user can accept the sharing of a subprogram by manually triggering the sharing acceptance confirmation control.

[0085] In actual application, the shared acceptance confirmation page needs to be displayed based on the parameters in the subprogram-related information. Displaying the shared acceptance confirmation page based on the subprogram-related information in step 602 specifically means: The steps include obtaining subprogram-related information based on a subprogram sharing request, The steps include: obtaining subprogram page display parameters by analyzing subprogram-related information; The procedure may also include the step of displaying a shared acceptance confirmation page based on the subprogram page display parameters.

[0086] For example, the shared acceptance confirmation page may include the question, "Do you want to open the BBB type CCC small scene shared from AAA, or ignore it?" Here, AAA, BBB, and CCC may be subprogram page display parameters obtained by parsing subprogram-related information.

[0087] In step 603, in response to the user's sharing request, the target subprogram page corresponding to the subprogram is displayed based on the subprogram-related information.

[0088] Specifically, the sharing acceptance process could be a manual confirmation by the user, an audio confirmation, or something similar. Alternatively, the user could pre-configure settings, such as setting sharing acceptance as the default when no action is taken.

[0089] In some embodiments, when a user accepts sharing via voice command, in step 603, in response to the user's sharing acceptance operation, displaying the target subprogram page corresponding to the subprogram based on subprogram-related information is, specifically, The process involves receiving the user's voice input, analyzing the voice input, and obtaining the shared confirmation result. The step may also include, in response to the sharing confirmation result being that sharing has been accepted, displaying the target subprogram page corresponding to the subprogram based on the subprogram-related information.

[0090] Specifically, the analysis of the voice input content may be implemented based on technologies such as speech recognition. The embodiments of the present invention are not limited thereto.

[0091] By triggering the SDK's voice announcement system, the smart vehicle can play a message such as, "Do you want to open the xxx type xxx small scene shared by xxx, or ignore it?" After the car owner confirms via voice, the framework's openMiniProgram() method is triggered to open the small scene, enabling viewing and sharing of the small scene on the in-vehicle system.

[0092] In some embodiments, to ensure safe driving and improve the user's driving experience, the user may be informed by voice announcement whether or not to accept the sharing of the subprogram. Before displaying the target subprogram page corresponding to the subprogram based on the subprogram-related information in response to the user's sharing acceptance operation in step 603, the subprogram sharing method provided in the embodiments of the present invention: The steps include generating shared announcement information based on subprogram-related information, The step may further include announcing the shared announcement information verbally.

[0093] In some embodiments, the shared announcement information may be text-type information, and during voice announcements, audio corresponding to the text of the shared announcement information may be concatenated and played back. Alternatively, the shared announcement information may be audio-type information, and during voice announcements, the shared announcement information may be played back directly.

[0094] For example, when subprogram-related information is obtained, the SDK's voice announcement system may be triggered to play the shared announcement information. After the car owner confirms it by voice, the framework's openMiniProgram() method may be triggered to open the target subprogram page, enabling viewing and sharing of the subprogram on the in-vehicle device.

[0095] Specifically, the content of the shared announcement information could be something like, "Your friend A shared a small scene of lifestyle services about the movie XX, which will soon open the details page for the movie 'YY'. Do you want to open it or ignore it?" or, "Your friend A shared a small scene of car owner services about special refueling, which will soon open the details of a certain gas station. Do you want to open it or ignore it?"

[0096] Based on the methods described in the previously mentioned embodiments, the following will provide further details with examples.

[0097] This embodiment will be explained with reference to the system shown in Figure 1.

[0098] As shown in Figure 9, the specific flow of the subprogram sharing method in this embodiment may be as follows.

[0099] In step 901, the sharing initiator displays the subprogram sharing page of the subprogram, which includes the subprogram content information and at least one sharing method selection control, each of which corresponds to one type of communication method.

[0100] If the sharing initiator (for example, the mobile phone) has a need for subprogram sharing, that is, if a subprogram is opened, the user can click the "More" button in the upper right corner to bring up more options, from which they can select a sharing method.

[0101] In step 902, the sharing initiator responds to a trigger operation on the target sharing method selection control among the sharing method selection controls to obtain information on the target smart vehicle and subprogram-related information of the subprogram.

[0102] In step 903, if the target sharing method selection control supports Bluetooth communication, a subprogram sharing request is sent to the target smart vehicle via the Bluetooth communication connection between the target smart vehicle and the sharing initiator. The subprogram sharing request includes subprogram-related information for the subprogram that the sharing initiator is requesting to be shared.

[0103] When sharing a subprogram over a short distance, the mobile phone first proactively selects "Share via Bluetooth" from the miniprogram page to pair with the in-car unit via Bluetooth. Once the connection is complete, the mobile phone proactively invokes the sharing interface and transmits information such as the subprogram's App ID, page information, and page parameters to the in-car unit via Bluetooth for storage.

[0104] In step 904, the target smart vehicle receives a subprogram sharing request from the sharing initiator, which contains subprogram-related information for the subprogram that is being requested to be shared.

[0105] In MossSDK, when a detection event, such as getSharedMiniProInfoByBlueTooth(), is set and recognized as an event directed to MossSDK, the message received via Bluetooth is retrieved, the message is parsed, and subprogram-related information, such as the subprogram's AppID, page information, and page parameters (params), is obtained. Based on this information, an audio announcement is triggered to the driver, and after the driver confirms it, the in-vehicle device opens the corresponding subprogram.

[0106] Specifically, MossSDK may recognize the moss-related keyword transmitted from the sharing initiator after the Bluetooth communication connection has been established.

[0107] In step 905, if the target sharing method selection control supports long-range wireless communication, the cloud side corresponding to the target smart vehicle is determined, and a subprogram sharing request is sent to the cloud side via the long-range communication connection between the cloud side and the sharing initiator. The subprogram sharing request contains subprogram-related information of the subprogram that the sharing initiator is requesting to be shared, and the subprogram sharing request is sent to the target smart vehicle side by the cloud side.

[0108] Bluetooth technology becomes ineffective when sharing subprograms over long distances. In this case, subprogram sharing may be achieved via wireless network communication. First, the mobile phone still voluntarily selects "Share to in-car device" from the miniprogram page. Identity and permission verification may be performed before calling the interface. The interface call is made only after the verification is successful. In MossSDK, an exposed interface may be designed to receive subprogram parameters, including information such as the subprogram's Appid, page information, and page parameters (params).

[0109] In step 906, the target smart vehicle receives a subprogram sharing request sent from the cloud, and the subprogram sharing request contains subprogram-related information of the subprogram that is being requested to be shared by the sharing initiator.

[0110] Assuming a secure connection is established, if the mobile phone has a need to share a subprogram, that is, if a subprogram is opened, the user can click the "More" button in the upper right corner to bring up more options. Selecting the "Share to In-Car" button will invoke the cloud interface, and information such as the subprogram's AppID, page information, and page parameters will be transmitted directly over the network. By analyzing this information, all the parameters necessary to open the subprogram can be obtained.

[0111] In step 907, the target smart vehicle generates shared announcement information based on subprogram-related information and announces the shared announcement information by voice.

[0112] Taking the case of an in-vehicle small scene with a subprogram as an example, the smart vehicle can trigger the SDK's voice announcement system to play a message such as, "Do you want to open the xxx type xxx small scene shared from xxx, or ignore it?" After the car owner confirms via voice, the framework's openMiniProgram() method is triggered to open the small scene, enabling viewing and sharing of the small scene on the in-vehicle system.

[0113] In step 908, the target smart vehicle receives the user's voice input, analyzes the voice input to obtain a sharing confirmation result, and in response to the sharing confirmation result being that sharing has been accepted, displays the target subprogram page corresponding to the subprogram based on the subprogram-related information.

[0114] As can be seen from the above, in the embodiment of the present invention, the sharing initiator displays the subprogram sharing page of the subprogram, and in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, obtains subprogram-related information of the subprogram from the target smart vehicle, and can send a subprogram sharing request to the target smart vehicle based on the target communication method corresponding to the target sharing method selection control. The subprogram sharing page includes the content information of the subprogram and at least one sharing method selection control, each of which corresponds to one type of communication method. The subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared by the sharing initiator, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information. In the embodiment of the present invention, the user of the sharing initiator can select one of the communication methods in the sharing method selection control on the subprogram sharing page and share and display the subprogram on the target smart vehicle, thereby enabling subprogram sharing between the smart vehicle and the user terminal using various communication methods and improving the user experience of the smart vehicle.

[0115] To better implement the above method, embodiments of the present invention further provide a subprogram sharing device. This subprogram sharing device may be incorporated into the sharing initiation side. The meaning of the terms herein is the same as that in the subprogram sharing method described above, and specific implementation details should be referred to in the description of the embodiments of the method.

[0116] Referring to Figure 10, an embodiment of the present invention further provides a subprogram sharing device applicable to the sharing initiation side. The device is A first page display unit 1001 that can be used to display the subprogram sharing page of a subprogram, wherein the subprogram sharing page includes at least one sharing method selection control, and each sharing method selection control corresponds to one type of communication method, and the first page display unit 1001 An information acquisition unit 1002 that can be used to acquire subprogram-related information of a subprogram in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, An information transmission unit 1003 that can be used to send a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared from the sharing initiator, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information, and the information transmission unit 1003 may also include

[0117] To better implement the subprogram sharing method provided in the embodiments of the present application, in one embodiment, other subprogram sharing devices are further provided. These subprogram sharing devices may be incorporated into the smart vehicle. The meaning of the terms herein is the same as that in the subprogram sharing method described above, and specific implementation details should be referred to in the description of the embodiments of the method.

[0118] Referring to Figure 11, embodiments of the present invention further provide other subprogram sharing devices applicable to the smart vehicle side. There is a communication connection between the smart vehicle side and at least one sharing initiator, and the device is A request receiving unit 1101 that can be used to receive a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, wherein the subprogram sharing request may include subprogram-related information of the subprogram for which sharing is requested from the sharing initiator, the target sharing method selection control is included in the subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page includes at least one sharing method selection control, each of the sharing method selection controls corresponds to one type of communication method, and the terminal device transmits the subprogram sharing request after obtaining the subprogram-related information of the subprogram from the target smart vehicle side in response to a trigger operation on the target sharing method selection control among the sharing method selection controls. Based on subprogram-related information, share Reception A second page display unit 1102 that can be used to display a confirmation page, The system may also include a subprogram page display unit 1103 that can be used to display a target subprogram page corresponding to a subprogram based on subprogram-related information in response to a user's sharing request operation.

[0119] In some embodiments, as shown in Figure 12, the subprogram sharing device provided in the embodiments of the present invention may further include a voice announcement unit 1104 that can be used to generate shared announcement information based on subprogram-related information and to announce the shared announcement information by voice.

[0120] Furthermore, in the embodiments of the present invention, an electronic device is provided. This electronic device may be a terminal or a server, etc. As shown in Figure 13, a schematic diagram of the configuration of the electronic device according to the embodiment of the present invention is shown. Specifically, This electronic device may include components such as a radio frequency (RF) circuit 1301, a memory 1302 containing one or more computer-readable storage media, an input unit 1303, a display unit 1304, a sensor 1305, an audio circuit 1306, a wireless fidelity (WiFi) module 1307, a processor 1308 containing one or more processing cores, and a power supply 1309. As those skilled in the art will understand, the configuration of the electronic device shown in Figure 13 is not limiting to the electronic device, and the electronic device may contain more or fewer components than shown, or may be a combination of some components, or may have different arrangements of components. Here, The RF circuit 1301 can be used to send and receive signals during information transmission or communication, and in particular, to receive downlink information from a base station and pass it to one or more processors 1308 for processing, and to transmit uplink data to the base station. Typically, the RF circuit 1301 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, and the like. The RF circuit 1301 can also communicate with networks and other devices via wireless communication. Wireless communication includes, but is not limited to, Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, and Short Messaging Service (SMS), and any other communication standard or protocol may be used.

[0121] Memory 1302 can be used to store software programs and modules. Processor 1308 executes various functional applications and data processing by executing software programs and modules stored in memory 1302. Memory 1302 may mainly include a program storage area and a data storage area. Of these, the program storage area may store an operating system, application programs required for at least one function (e.g., sound playback function, image playback function, etc.), etc. The data storage area may store data created in accordance with the use of the electronic device (e.g., audio data, phone book, etc.). Memory 1302 may also include high-speed random access memory, or non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. Accordingly, memory 1302 may further include a memory controller. This provides access to memory 1302 by processor 1308 and input unit 1303.

[0122] The input unit 1303 can be used to receive input numerical or character information and to generate signal inputs from a keyboard, mouse, joystick, optical or trackball related to user settings and function control. Specifically, in one specific embodiment, the input unit 1303 may include a touch-sensitive surface and other input devices. The touch-sensitive surface, also called a touchscreen or touchpad, can collect user touch operations on or near it (for example, operations performed by the user on or near the touch-sensitive surface using any suitable object or accessory such as a finger or stylus) and drive corresponding connected devices according to a preset program. In some embodiments, the touch-sensitive surface may include two parts: a touch detection device and a touch controller. Here, the touch detection device detects the direction of the user's touch, detects the signal from the touch operation, and transmits the signal to the touch controller. The touch controller can receive touch information from the touch detection device, convert it into touch point coordinates and transmit it to the processor 1308, and can also receive and execute commands transmitted from the processor 1308. Furthermore, touch-sensitive surfaces may be realized by multiple forms such as resistive films, capacitive sensors, infrared rays, or surface acoustic waves. In addition to the touch-sensitive surface, the input unit 1303 may also include other input devices. Specifically, the other input devices may include, but are not limited to, one or more of the following: a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc.

[0123] The display unit 1304 can be used to display information entered by the user or information provided to the user, and various graphical user interfaces of the electronic device. These graphical user interfaces may consist of graphics, text, icons, videos, and any combination thereof. The display unit 1304 may include a display panel. In some embodiments, the display panel may be in the form of a liquid crystal display (LCD) or an organic light-emitting diode (OLED). Furthermore, a touch-sensitive surface may cover the display panel. When the touch-sensitive surface detects a touch operation on or near it, it transmits the touch operation to the processor 1308 to determine the type of touch event. The processor 1308 then provides the display panel with a corresponding visual output depending on the type of touch event. In Figure 13, the touch-sensitive surface and the display panel are two separate components, and the input function and output While the functionality is achieved, in some embodiments, the touch-sensitive surface and display panel may be integrated to realize input and output functions.

[0124] The electronic device may further include at least one type of sensor 1305, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. Here, the ambient light sensor can adjust the brightness of the display panel according to the brightness of the ambient light, and the proximity sensor can turn off the display panel and / or backlight when the electronic device is moved to the ear. As a type of motion sensor, a gravity acceleration sensor can detect the magnitude of acceleration in each direction (usually three axes), can detect the magnitude and direction of gravity when stationary, and can be used in applications that recognize the orientation of a mobile phone (e.g., switching between portrait and landscape orientations, related games, magnetometer orientation calibration), vibration recognition-related functions (e.g., pedometer, tap), etc. Other sensors that can be placed in the electronic device, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., are not described here.

[0125] The audio circuit 1306, speaker, and microphone can provide an audio interface between the user and the electronic device. The audio circuit 1306 can transmit the electrical signal converted from the received audio data to the speaker. The speaker converts the electrical signal into an acoustic signal and outputs it. Meanwhile, the microphone converts the collected acoustic signal into an electrical signal. The audio circuit 1306 receives the electrical signal, converts it into audio data, outputs the audio data to the processor 1308, and after the processor 1308 processes the audio data, it transmits the audio data to, for example, another electronic device via the RF circuit 1301, or outputs the audio data to the memory 1302 for further processing. The audio circuit 1306 may also include an earphone jack for providing communication between an external earphone and the electronic device.

[0126] WiFi belongs to the category of short-range wireless transmission technologies. The WiFi module 1307 allows the electronic device to assist users in sending and receiving emails, browsing web pages, and accessing streaming media. WiFi provides users with wireless broadband internet access. While Figure 13 shows the WiFi module 1307, it is important to understand that, as is essential to the electronic device, the WiFi module 1307 is not a required component and can be completely omitted as needed, without altering the essence of the invention.

[0127] The processor 1308 is the control center of the electronic device, connecting all parts of the entire mobile phone using various interfaces and lines, executing or performing software programs and / or modules stored in memory 1302, and retrieving data stored in memory 1302 to perform various functions of the electronic device and process data. In some embodiments, the processor 1308 may include one or more processing cores. In some embodiments, the processor 1308 may incorporate an application processor and a modem processor. Here, the application processor mainly handles the operating system, user interface, and application programs, etc., and the modem processor mainly handles wireless communication. To understand this, the modem processor does not necessarily have to be incorporated into the processor 1308.

[0128] The electronic device further includes a power supply 1309 (e.g., a battery) that supplies power to each component. In some embodiments, the power supply may be logically connected to a processor 1308 via a power management system. This allows the power management system to perform functions such as charging, discharging, and power consumption management. The power supply 1309 may include one or more DC or AC power supplies, a recharge system, a power fault detection circuit, a power converter or inverter, a power status indicator, and other optional components.

[0129] Although not shown, the electronic device may include a camera, a Bluetooth module, and the like. A detailed explanation is omitted here. Specifically, in this embodiment, the processor 1308 of the electronic device loads executable files corresponding to the processes of one or more application programs into memory 1302 according to the following instructions, and the processor 1308 executes the application programs stored in memory 1302 to realize various functions.

[0130] The application program is applicable to the sharing initiator, and there is a communication connection between the sharing initiator and at least one smart vehicle.

[0131] When processor 1308 executes the application program stored in memory 1302, A step of displaying the subprogram sharing page of a subprogram, wherein the subprogram sharing page includes content information of the subprogram and at least one sharing method selection control, each of which corresponds to one type of communication method. The steps include: In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, acquiring information from the target smart vehicle and subprogram-related information of the subprogram; The steps of sending a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared by the sharing initiator, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information, can be implemented.

[0132] Alternatively, the application program is applicable to the smart vehicle, and there is a communication connection between the smart vehicle and at least one sharing initiator.

[0133] When processor 1308 executes the application program stored in memory 1302, The steps include receiving a subprogram sharing request from the sharing initiator, which contains subprogram-related information for the subprogram that is being shared, Based on subprogram-related information, the steps include displaying a sharing acceptance confirmation page, In response to a user's request for sharing, it is possible to implement the step of displaying the target subprogram page corresponding to the subprogram based on subprogram-related information.

[0134] As those skilled in the art will understand, all or part of the steps of each of the above embodiments may be performed by instructions, or by controlling the relevant hardware via instructions. These instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0135] Therefore, embodiments of the present invention provide a computer-readable storage medium storing a plurality of instructions. When loaded by a processor, these instructions can be used to execute a step of any one of the subprogram sharing methods provided in embodiments of the present invention. For example, these instructions can be used to execute the following steps:

[0136] Instructions stored in a computer-readable storage medium are applicable to the sharing initiator, and there is a communication connection between the sharing initiator and at least one smart vehicle.

[0137] When the instruction is loaded by the processor, A step of displaying the subprogram sharing page of a subprogram, wherein the subprogram sharing page includes content information of the subprogram and at least one sharing method selection control, each of which corresponds to one type of communication method. The steps include: In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, acquiring information from the target smart vehicle and subprogram-related information of the subprogram; The steps of sending a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared by the sharing initiator, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information, can be implemented.

[0138] Alternatively, instructions stored in a computer-readable storage medium are applicable to the smart vehicle, and there is a communication connection between the smart vehicle and at least one sharing initiator.

[0139] When the instruction is loaded by the processor, The steps include receiving a subprogram sharing request from the sharing initiator, which contains subprogram-related information for the subprogram that is being shared, Based on subprogram-related information, the steps include displaying a sharing acceptance confirmation page, In response to a user's sharing request, it is possible to implement the step of displaying the target subprogram page corresponding to the subprogram based on subprogram-related information.

[0140] The specific implementation of each of the above operations can be found in the previously mentioned examples, but the explanation will be omitted here.

[0141] Here, the computer-readable storage medium may include read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] Since the instructions stored in the computer-readable storage medium can be used to execute the steps of any one of the subprogram sharing methods provided in the embodiments of the present invention, the beneficial effects that can be achieved by any one of the subprogram sharing methods provided in the embodiments of the present invention can be achieved. Details can be found in the embodiments described above, but are omitted here.

[0143] According to one aspect of the present application, a computer program product or computer program including computer instructions is further provided. The computer instructions are stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and when the processor executes the computer instructions, causes the electronic device to perform the method provided in various optional implementations of the above embodiment.

[0144] The above describes in detail the subprogram sharing method, apparatus, electronic device, and storage medium provided in embodiments of the present invention. This specification describes the principles and embodiments of the present invention by applying specific individual examples. The above description of embodiments is used solely to aid in understanding the methods and central ideas of the present invention. Furthermore, those skilled in the art will know that both specific embodiments and scopes can be modified based on the ideas of the present invention. In summary, the contents of this specification should not be understood as limiting the present invention. [Explanation of Symbols]

[0145] 1. Smart vehicle side 2 Smart vehicle side 3. Smart vehicle side 10 Sharing initiator 20 Smart Vehicle Side 30. Cloud side 1001 First page display unit 1002 Information Acquisition Unit 1003 Information transmission unit 1101 Request receiving unit 1102 Page 2 Display Unit 1103 Subprogram page display unit 1104 Voice Announcement Unit 1301 Radio Frequency (RF) Circuit 1302 memory 1303 Input Unit 1304 Display Unit 1305 Sensor 1306 Audio Circuit 1307 WiFi module 1308 Processor 1309 Power supply

Claims

1. A method for sharing subprograms executed by terminal devices, A step of displaying a subprogram sharing page of a subprogram, wherein the subprogram sharing page includes at least one sharing method selection control, and each of the sharing method selection controls corresponds to one type of communication method. In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the steps include obtaining information from the target smart vehicle and the subprogram-related information of the subprogram, A step of sending a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes the subprogram-related information, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information. How to share subprograms.

2. The step of sending a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control, where the target sharing method selection control is compatible with the Bluetooth communication method, is as follows: A step of generating a Bluetooth sharing event based on the Bluetooth communication method and the subprogram-related information, The step of transmitting the Bluetooth sharing event to the target smart vehicle via a Bluetooth communication connection between the target smart vehicle and the terminal device is included. The subprogram sharing method according to claim 1.

3. The step of sending a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, where the target sharing method selection control corresponds to a long-range wireless communication method, is as follows: A step of generating a long-distance shared event based on the long-distance wireless communication method and the subprogram-related information, The steps include determining the cloud side corresponding to the target smart vehicle side, The steps include: transmitting the remote sharing event to the cloud via a remote communication connection between the cloud and the terminal device, wherein the remote sharing event is transmitted by the cloud to the target smart vehicle. The subprogram sharing method according to claim 1.

4. The step of transmitting the remote sharing event to the cloud side via a remote communication connection between the cloud side and the terminal device is: A step of transmitting first identity authentication information of the terminal device to the cloud side via a long-distance communication connection between the cloud side and the terminal device, wherein the identity check of the terminal device is performed by the cloud side based on the first identity authentication information. The steps include receiving the identity check result of the terminal device by the cloud side, The step of sending the remote sharing event to the cloud side via the remote communication connection in response to the identity check result being successful, The subprogram sharing method according to claim 3.

5. The step of sending a subprogram sharing request to the target smart vehicle based on the communication method corresponding to the target sharing method selection control is: The steps include calling the shared interface on the target smart vehicle side based on the communication method corresponding to the target sharing method selection control, The steps include sending a subprogram sharing request to the target smart vehicle via the shared interface, The subprogram sharing method according to claim 1.

6. The step of acquiring the target smart vehicle in response to a trigger operation on the target sharing method selection control among the sharing method selection controls is as follows: Steps include: displaying a shared vehicle selection page in response to a trigger operation on a target shared vehicle selection control among the shared vehicle selection controls, wherein the shared vehicle selection page includes a vehicle selection control corresponding to at least one smart vehicle side; A step of determining a target smart vehicle in response to a trigger operation on a target vehicle selection control among the vehicle selection controls, wherein the target smart vehicle corresponds to the target vehicle selection control. The subprogram sharing method according to claim 1.

7. A method for sharing subprograms executed by the smart vehicle, A step of receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of a subprogram that is requested to be shared by the terminal device, the target sharing method selection control is included in the subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page includes at least one sharing method selection control, each of the sharing method selection controls corresponds to one type of communication method, and the terminal device, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, obtains the target smart vehicle side and the subprogram-related information of the subprogram, and then transmits the subprogram sharing request. Based on the subprogram-related information, the steps include displaying a shared acceptance confirmation page, The process includes the step of displaying a target subprogram page corresponding to the subprogram based on the subprogram-related information in response to a user's sharing request operation, How to share subprograms.

8. In response to a user's sharing request, before the step of displaying the target subprogram page corresponding to the subprogram based on the subprogram-related information, The steps include generating shared announcement information based on the aforementioned subprogram-related information, The process further includes the step of announcing the shared announcement information by voice, The subprogram sharing method according to claim 7.

9. The step of displaying a target subprogram page corresponding to the subprogram based on the subprogram-related information in response to a user's sharing request operation is: The steps include receiving the user's voice input content, analyzing the voice input content, and obtaining the shared confirmation result, The process includes the step of displaying a target subprogram page corresponding to the subprogram based on the subprogram-related information in response to the sharing confirmation result being a sharing acceptance. The subprogram sharing method according to claim 7.

10. The step of displaying the shared acceptance confirmation page based on the subprogram-related information is: The steps include obtaining the subprogram-related information based on the subprogram sharing request, The steps include: obtaining subprogram page display parameters by analyzing the aforementioned subprogram-related information; The steps include: displaying a shared acceptance confirmation page based on the subprogram page display parameters; The subprogram sharing method according to claim 7.

11. The step of receiving a subprogram sharing request, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared from the terminal device, The step of receiving a subprogram sharing request sent from the cloud side corresponding to the smart vehicle side, wherein the subprogram sharing request includes subprogram-related information of the subprogram to be shared by the terminal device and second identity authentication information of the cloud side, and the cloud side sends the subprogram sharing request after receiving the subprogram sharing request sent from the terminal device based on a communication method corresponding to the target sharing method selection control, After the step of receiving a subprogram sharing request, the subprogram sharing method: The steps include: performing an identity check on the cloud side based on the second identity authentication information, thereby obtaining the corresponding identity check result on the cloud side; The further step includes obtaining subprogram-related information by analyzing the subprogram sharing request in response to the identity check result being successful. The subprogram sharing method according to claim 7.

12. The step of receiving a subprogram sharing request is: The steps include receiving external transmission data and detecting the external transmission data using a detection code for a subprogram shared event, If the external transmission data contains a subprogram sharing event, the method includes the step of analyzing the external transmission data to obtain a subprogram sharing request corresponding to the subprogram sharing event. The subprogram sharing method according to claim 7.

13. A subprogram sharing device applicable to terminal equipment, A first page display unit for displaying a subprogram shared page of a subprogram, wherein the subprogram shared page includes at least one sharing method selection control, and each of the sharing method selection controls corresponds to one type of communication method, and the first page display unit, In response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the target smart vehicle and an information acquisition unit that acquires subprogram-related information of the subprogram, An information transmission unit that transmits a subprogram sharing request to the target smart vehicle based on a communication method corresponding to the target sharing method selection control, wherein the subprogram sharing request includes the subprogram-related information, and the target subprogram page corresponding to the subprogram is displayed by the target smart vehicle based on the subprogram-related information, the information transmission unit includes: Subprogram sharing device.

14. A subprogram sharing device applied to the smart vehicle side, A request receiving unit that receives a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, wherein the subprogram sharing request includes subprogram-related information of the subprogram that is requested to be shared by the terminal device, the target sharing method selection control is included in the subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page includes at least one sharing method selection control, each of the sharing method selection controls corresponds to one type of communication method, and the terminal device, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, transmits the subprogram sharing request after obtaining the target smart vehicle side and the subprogram-related information of the subprogram. A second page display unit that displays a shared acceptance confirmation page based on the subprogram-related information, A subprogram page display unit that, in response to a user's sharing request operation, displays a target subprogram page corresponding to the subprogram based on the subprogram-related information, includes: Subprogram sharing device.

15. An electronic device comprising memory and a processor, wherein an application program is stored in the memory, and the processor executes the application program in the memory to perform the subprogram sharing method according to any one of claims 1 to 6.

16. A computer program that causes a computer to execute the subprogram sharing method described in any one of claims 1 to 6.

17. An electronic device comprising memory and a processor, wherein an application program is stored in the memory, and the processor executes the application program in the memory to perform the subprogram sharing method according to any one of claims 7 to 12.

18. A computer program that causes a computer to execute the subprogram sharing method described in any one of claims 7 to 12.

Images