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 from a Chinese patent application filed with the China Patent Office on January 31, 2023, bearing application number 202310129492.3 and entitled "Method, device, electronic device, and storage medium for sharing subprograms between on-board units," the entire contents of which are incorporated herein by reference.

[0002] The present invention relates to the field of smart vehicles, and in particular to a subprogram sharing method, device, electronic device, and storage medium. [Background technology]

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

[0004] In some methods of sharing data with a smart vehicle, a non-driver transmits data via a Bluetooth connection between an electronic device and the smart vehicle. Summary of the Invention [Problem to be solved by the invention]

[0005] Embodiments of the present invention provide a subprogram sharing method, device, electronic device, and storage medium that can realize subprogram sharing between a smart vehicle and a user terminal using various communication methods and improve the user experience of the smart vehicle. [Means for solving the problem]

[0006] In an embodiment of the present invention, a sub-program sharing method executed by a terminal device is provided, the sub-program sharing method comprising: displaying a subprogram sharing page of the subprogram, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; Acquiring subprogram-related information of the subprogram from a target smart vehicle in response to a trigger operation on a target sharing method selection control of the sharing method selection controls; and a step of sending a sub-program sharing request to the target smart vehicle side based on a communication method corresponding to the target sharing method selection control, wherein the sub-program sharing request includes the sub-program related information, and a target sub-program page corresponding to the sub-program is displayed by the target smart vehicle side based on the sub-program related information.

[0007] In an embodiment of the present invention, another sub-program sharing method executed by a smart vehicle side is further provided. The sub-program sharing method includes: receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared by the terminal device, the target sharing method selection control being included in a subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method, the terminal device transmitting the subprogram sharing request after acquiring subprogram-related information of the subprogram from the target smart vehicle in response to a trigger operation on a target sharing method selection control among the sharing method selection controls; displaying a sharing acceptance confirmation page based on the subprogram-related information; and displaying a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation.

[0008] In an embodiment of the present invention, there is further provided a subprogram sharing device adapted for a terminal device, the subprogram sharing device comprising: a first page display unit for displaying a subprogram sharing page of a subprogram, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; an information acquisition unit for acquiring subprogram-related information of the subprogram from a target smart vehicle in response to a trigger operation on a target sharing mode selection control of the sharing mode selection controls; an information transmission unit that transmits a sub-program sharing request to the target smart vehicle side based on a communication method corresponding to the target sharing method selection control, wherein the sub-program sharing request includes the sub-program related information, and a target sub-program page corresponding to the sub-program is displayed by the target smart vehicle side based on the sub-program related information.

[0009] In an embodiment of the present invention, another sub-program sharing device applied to a smart vehicle side is further provided. The sub-program sharing device includes: a request receiving unit for receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared by the terminal device, the target sharing method selection control being included in a subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method, the terminal device responding to a trigger operation on a target sharing method selection control among the sharing method selection controls to acquire subprogram-related information of the subprogram from a target smart vehicle and then transmitting the subprogram sharing request; a second page display unit for displaying a sharing confirmation page based on the sub-program related information; and a sub-program page display unit that displays a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation.

[0010] An embodiment of the present invention further provides an electronic device including a memory and a processor, wherein the memory stores an application program, and the processor executes the application program in the memory to perform any one of the steps of the subprogram sharing method provided in the embodiment of the present invention.

[0011] In an embodiment of the present invention, there is further provided a computer-readable storage medium having stored thereon a plurality of instructions, the instructions being configured to, when loaded by a processor, cause execution of the steps of any one of the subprogram sharing methods provided in the embodiment of the present invention.

[0012] In an embodiment of the present invention, there is further provided a computer program product including a computer program or instructions which, when executed by a processor, implements the steps of any one of the subprogram sharing methods provided in the embodiment of the present invention. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 2 is a schematic diagram of a scenario of a subprogram sharing method provided in an embodiment of the present invention; [Figure 2] FIG. 2 is a flow diagram of a subprogram sharing method provided in an embodiment of the present invention; [Figure 3] FIG. 2 is a schematic diagram of a sub-program sharing page provided in an embodiment of the present invention; [Figure 4] FIG. 10 is another schematic diagram of a sub-program sharing page provided in an embodiment of the present invention; [Figure 5] FIG. 2 is a schematic diagram of the technical implementation of Bluetooth communication connection establishment provided in an embodiment of the present invention; [Figure 6] FIG. 10 is a flow diagram of another subprogram sharing method provided in an embodiment of the present invention; [Figure 7] FIG. 2 is a schematic diagram of the technical implementation of a subprogram sharing process provided in an embodiment of the present invention; [Figure 8] FIG. 10 is a schematic diagram of another technical implementation of a subprogram sharing process provided in an embodiment of the present invention; [Figure 9] FIG. 2 is another flow diagram of a subprogram sharing method provided in an embodiment of the present invention; [Figure 10] 1 is a schematic diagram of the configuration of a subprogram sharing device provided in an embodiment of the present invention; [Figure 11] FIG. 10 is a schematic diagram of the configuration of another subprogram sharing device provided in an embodiment of the present invention; [Figure 12] FIG. 10 is a schematic diagram of another configuration of a subprogram sharing device provided in an embodiment of the present invention; [Figure 13]1 is a schematic diagram illustrating the configuration of an electronic device provided in an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, the configuration of the embodiments of the present invention will be described clearly and completely with reference to the drawings of the embodiments of the present invention. It is clear that the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments that a person skilled in the art can obtain from the embodiments of the present invention without creative work fall within the scope of protection of the present invention.

[0015] Some methods for sharing data with smart vehicles involve non-drivers transmitting data via Bluetooth between their electronic devices and the smart vehicle, but this configuration only supports subprogram sharing between the smart vehicle and the electronic device through a single Bluetooth communication method, which limits the type of data that can be shared and reduces the effectiveness of sharing data such as audio and video, thereby affecting the user experience of the smart vehicle.

[0016] The embodiments of the present invention provide a subprogram sharing method, a device, an electronic device, and a computer-readable storage medium. The subprogram here is also called a mini-program or a small scene (usually called a small scene in an in-vehicle device). Specifically, the embodiments of the present invention provide a subprogram sharing method applied to a subprogram sharing device, and the subprogram sharing device 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, portable terminals include but are not limited to smartphones, smart watches, tablet computers, laptops, smart car devices, smart vehicles, etc. Stationary terminals include but are not limited to desktop computers, smart TVs, etc.

[0018] The electronic device may be a device such as a server, which may be an independent physical server, a server cluster or a distributed system consisting of multiple physical servers, or a cloud server that provides, but is not limited to, 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.

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

[0020] In the following, the method will be described taking as an example a case where the sharing initiator, the smart vehicle, and the cloud collaborate to realize the subprogram sharing method.

[0021] As shown in FIG. 1, the subprogram sharing system provided in the embodiment of the present invention includes a sharing initiation side (i.e., terminal device) 10, a smart vehicle side 20, and a cloud side (server) 30, and the sharing initiation side 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 initiation side 10 displays a subprogram sharing page of the subprogram, acquires subprogram-related information of the subprogram in response to a target vehicle sharing operation for a target sharing method selection control among the sharing method selection controls, and transmits 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 content information of the subprogram and at least one sharing method selection control, each of which 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 requested to be shared by the sharing initiation side 10.

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

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

[0025] As can be appreciated, in some embodiments, the sharing initiator 10 and the smart vehicle 20 may communicate directly.

[0026] Here, the sharing initiator 10 displays a subprogram sharing page of the subprogram, and in response to a trigger operation on a target sharing method selection control among the sharing method selection controls, acquires subprogram-related information of the subprogram from the target smart vehicle, and transmits 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 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 requested to be shared by the sharing initiator 10.

[0027] The smart vehicle side 20 can be used to receive a subprogram sharing request sent from the sharing initiating side 10, which includes subprogram-related information of the subprogram requested to be shared by the sharing initiating side 10, display a sharing acceptance confirmation page based on the subprogram-related information, and display a target subprogram page corresponding to the subprogram based on the subprogram-related information in response to the user's sharing acceptance operation.

[0028] Each of these will be described in detail below. Note that the order in which the following embodiments are described does not limit the preferred order of the embodiments.

[0029] The embodiment of the present invention will be described from the perspective of a subprogram sharing device, which may be specifically incorporated into a terminal.

[0030] 2, the subprogram sharing method of this embodiment is executed by the sharing initiator (that is, the terminal device). The specific flow may be as follows.

[0031] In step 201, a subprogram sharing page of the subprogram is displayed, and the subprogram sharing page includes 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.

[0032] Here, the subprogram is a program that operates depending on the host program. In the embodiment 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 (e.g., the mini-program of the present application) depends is called a 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 the host program and the sub-programs are not limited, for example, the host program may be an instant messaging client program, a music playing program, etc.

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

[0036] In some embodiments, the sharing method selection control may be used by the user to select a communication method for sharing a subprogram. For example, the sharing method selection control may be the control labeled "Send via Bluetooth" in FIG. 3 or 4. Alternatively, the sharing method selection control may be the control labeled "Share to vehicle device" in FIG. 4.

[0037] Here, different communication methods may correspond to different sharing method selection controls. For example, the control called "Send via Bluetooth" in Fig. 3 or 4 may correspond to a Bluetooth communication method, and the control called "Share with in-vehicle device" in Fig. 4 may correspond to a long-distance wireless communication method.

[0038] It is understood that the sharing page sub-program may include a sharing method selection control corresponding to other communication methods, such as a wired communication method, although the embodiment of the present invention is not limited thereto.

[0039] In step 202, in response to a trigger operation on a target sharing method selection control among the sharing method selection controls, the target smart vehicle side and 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 on the sharing initiation side in the vehicle-mounted device subprogram sharing process.

[0041] For example, a user may trigger the 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, the subprogram-related information may include, but is not limited to, a subprogram identifier (Appid) corresponding to the subprogram, page information, page parameters (params), etc. For example, the subprogram identifier may be a program ID in the host program corresponding to the subprogram.

[0043] As can be understood, the target sharing method selection control may directly correspond to one smart vehicle side. For example, the control called "Send via Bluetooth" in FIG. 3 may correspond to one smart vehicle side. In this case, in response to a trigger operation on the target sharing method selection control among the sharing method selection controls, the target smart vehicle side (i.e., the smart vehicle side corresponding to the target sharing method selection control) can be directly obtained.

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

[0045] As can be appreciated, if the sharing initiator can communicate with multiple smart vehicle sides, the target smart vehicle side can be determined from among the smart vehicle sides by the user's operation on the vehicle selection control.

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

[0047] Here, the trigger operation may include an operation such as clicking, double-clicking, long pressing, or sliding. In some examples, a trigger operation for a control may be realized by a predetermined quick operation. For example, a single press of the volume down key by a user of the terminal may be recognized as a single trigger operation for selecting a target-shared control. The present invention does not limit the specific quick operation.

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

[0049] In some embodiments, the target sharing mode selection control may correspond to a Bluetooth communication mode. In step 203, sending a sub-program sharing request to the target smart vehicle according to the communication mode corresponding to the target sharing mode selection control specifically includes: generating a Bluetooth share event according to the Bluetooth communication method and the sub-program related information; and transmitting a Bluetooth sharing event to the target smart vehicle side via a Bluetooth communication connection between the target smart vehicle side and the sharing initiator side.

[0050] Here, the Bluetooth sharing event is a sub-program sharing event generated when the sharing initiator shares a sub-program with the target smart vehicle via Bluetooth communication.

[0051] As can be seen, before a Bluetooth sharing event can be sent to the target smart vehicle side via a Bluetooth communication connection, a Bluetooth communication connection must first be established between the target smart vehicle side and the sharing initiator side.

[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). Then, 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 the Bluetooth communication connection is established, if the sharing initiator voluntarily calls the sharing interface of the target smart vehicle, the sharing initiator may transmit subprogram-related information (e.g., information such as App ID, page information, page parameters, etc.) to the target smart vehicle (on-board device) via the Bluetooth communication connection.

[0054] In some other embodiments, the target sharing mode selection control may correspond to a long-distance wireless communication mode. In step 203, sending a sub-program sharing request to the target smart vehicle according to the communication mode corresponding to the target sharing mode selection control specifically includes: generating a long-distance shared event based on the long-distance wireless communication method and the subprogram-related information; determining a cloud side corresponding to the target smart vehicle side; and transmitting a long-distance sharing event to the cloud side via a long-distance communication connection between the cloud side and the sharing initiator side, wherein the long-distance sharing event is transmitted by the cloud side to the target smart vehicle side.

[0055] Here, the long-distance sharing event is a subprogram sharing event generated when the sharing initiator shares a subprogram with the target smart vehicle via long-distance wireless communication. As can be understood, when long-distance subprogram sharing is required, Bluetooth technology cannot be used. In this case, the subprogram sharing may be realized via long-distance wireless communication, for example, wireless network communication.

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

[0057] Generally, when the sharing initiator needs to share a subprogram (mini-program), i.e., when a subprogram (mini-program) is opened, the user can click the "More" button in the upper right corner of the subprogram to pop up more options. Selecting the "Share to vehicle" button calls up a cloud-side interface, and subprogram-related information, such as the subprogram's AppID, page information, and page parameters, is directly transmitted to the cloud side via a long-distance communication connection. The cloud side may also directly transmit the subprogram-related information to the target smart vehicle side. The target smart vehicle side analyzes it and obtains all parameters necessary to open the subprogram.

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

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

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

[0061] Here, the first identity authentication information may be a digital certificate of the sharing initiator. The identity check result may be information indicating that the first identity authentication information is correct, i.e., check pass, or information indicating that the first identity authentication information is incorrect, i.e., check fail. If the identity check result is check pass, a long-distance sharing event is sent to the cloud side, and if the identity check result is check fail, the long-distance sharing event is not allowed to be sent to the cloud side.

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

[0063] In some embodiments, the sending of the sub-program sharing request may be realized by an interface call method. In step 203, sending the sub-program sharing request to the target smart vehicle according to the communication method corresponding to the target sharing method selection control specifically includes: calling a sharing interface on the target smart vehicle according to a communication method corresponding to the target sharing method selection control; and sending a sub-program sharing request to the target smart vehicle via a sharing interface.

[0064] In some embodiments, when sub-program sharing is performed through a Bluetooth communication method, the Bluetooth communication method can trigger the sharing interface on the target smart vehicle side to detect currently received data and obtain a sub-program sharing request from the currently received data.

[0065] For example, a detection event may be set in the sharing interface. If the event is recognized as being directed to the sharing interface, the message received via Bluetooth is acquired and analyzed to acquire a subprogram sharing request, and then subprogram-related information, such as the subprogram's AppID, page information, and page parameters, is analyzed from the subprogram sharing request.

[0066] Specifically, when calling a sharing interface using a Bluetooth communication method, the information transmitted may include an identifier indicating that the current information will be transmitted via Bluetooth, or an identifier indicating that the information will be transmitted via a sharing interface.

[0067] In some embodiments, when sharing a subprogram through long-distance wireless communication, the sharing interface may open a page interface for calling the subprogram, and then the network communication calling interface on the cloud side realizes the pull-up of the subprogram.

[0068] As shown in Figure 6, an embodiment of the present invention provides another sub-program sharing method executed by the smart vehicle side, the specific flow of which may be as follows:

[0069] In step 601, a subprogram sharing request containing subprogram-related information of the subprogram requested to be shared is received from the sharing initiator.

[0070] In the embodiment of the present invention, the meanings of some terms are the same as those in the above-mentioned subprogram sharing method, and specific implementation details can be referred to the description of the above-mentioned embodiment.

[0071] Here, the subprogram sharing request is request information from the sharing initiation side requesting that the subprogram be shared with the smart vehicle side. The sharing initiation side transmits the subprogram sharing request based on a communication method corresponding to the target sharing method selection control. The target sharing method selection control is included in a subprogram sharing page of the subprogram displayed on the sharing initiation side, 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 initiation side acquires subprogram-related information of the subprogram from the target smart vehicle side and then transmits the subprogram sharing request.

[0072] In some embodiments, receiving a sub-program sharing request including sub-program-related information of a sub-program requested to be shared from a sharing initiator in step 601 specifically includes: The method may include receiving a subprogram sharing request sent from a cloud side corresponding to the smart vehicle side, wherein the subprogram sharing request includes subprogram-related information of the subprogram requested to be shared by the sharing initiation side and second identity authentication information of the cloud side.

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

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

[0075] Accordingly, after receiving a sub-program sharing request in step 601, the sub-program sharing method provided in the embodiment of the present invention includes: performing an identity check on the cloud side based on the second identity authentication information to obtain an identity check result corresponding to the cloud side; In response to the identity check result being a pass, the method may further include analyzing the sub-program sharing request to obtain sub-program related information.

[0076] The identity check result may be information indicating that the second identity authentication information is correct, i.e., a check pass, or information indicating that the second identity authentication information is incorrect, i.e., a check fail. If the identity check result is a check pass, the sub-program-related information may be obtained by analyzing the sub-program sharing request. If the identity check result is a check fail, the analysis of the sub-program sharing request is not allowed.

[0077] As shown in Figure 7, assuming a secure connection has been established, when the mobile phone needs to share a subprogram, i.e., when a subprogram (called Small Scene in Figure 7) is opened, the user can click the "More" button in the upper right corner to pop up more options, and when the "Share to Vehicle Device" button is selected, the cloud-side interface is called and transmission is performed over the network. Before calling the interface, identity and authority authentication may be performed first. To improve communication security, the interface is called only after the authentication is passed.

[0078] In some embodiments, an exposed interface may be designed in the Microsoft Office Shell Point Server Software Development Kit (MossSDK) to receive parameters for a subprogram, including information such as the subprogram's AppID, page information, and page parameters.

[0079] In some embodiments, receiving a sub-program sharing request in step 601 specifically includes: receiving externally transmitted data and detecting the externally transmitted data by a detection code for a subprogram shared event; If the external transmission data includes a sub-program share event, the method may further include analyzing the external transmission data to obtain a sub-program share request corresponding to the sub-program share event.

[0080] As shown in Figure 8, a detection code for a sub-program (called small scene in Figure 8) sharing event may be designed in MossSDK. If it is recognized as a sub-program sharing event directed to MossSDK, the code acquires the message received via Bluetooth and performs message analysis.

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

[0082] In step 602, a sharing acceptance confirmation page is displayed based on the subprogram related information.

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

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

[0085] In practical application, the sharing acceptance confirmation page needs to be displayed based on the parameters in the sub-program related information. In step 602, displaying the sharing acceptance confirmation page based on the sub-program related information specifically includes: obtaining sub-program related information based on the sub-program sharing request; obtaining sub-program page display parameters by analyzing the sub-program related information; and displaying a share acceptance confirmation page based on the sub-program page display parameters.

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

[0087] In step 603, in response to the user's sharing acceptance operation, a target sub-program page corresponding to the sub-program is displayed based on the sub-program related information.

[0088] Specifically, the sharing acceptance operation may be an operation in which the user manually confirms, an operation in which the user confirms by voice, etc. Alternatively, the user may set in advance that sharing acceptance is set as a default when no operation is performed.

[0089] In some embodiments, when the user accepts sharing through a voice command, in step 603, displaying a target sub-program page corresponding to the sub-program based on the sub-program-related information in response to the user's sharing acceptance operation, specifically includes: receiving a voice input from a user and analyzing the voice input to obtain a sharing confirmation result; In response to the sharing confirmation result indicating acceptance of sharing, displaying a target sub-program page corresponding to the sub-program based on the sub-program related information.

[0090] Specifically, the analysis of the voice input content may be realized based on a technology such as voice recognition, although the embodiment of the present invention is 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 small scene of xxx type shared by xxx, or ignore it?" After the car owner confirms the message, the framework's openMiniProgram() method is triggered to open the small scene, allowing the small scene to be viewed and shared on the in-vehicle device.

[0092] In some embodiments, in order to ensure the user's safe driving and improve the user's driving experience, the user may be prompted by voice announcement whether to accept or decline the sharing of the subprogram. In step 603, in response to the user's acceptance of the sharing, before displaying the target subprogram page corresponding to the subprogram based on the subprogram-related information, the subprogram sharing method provided in the embodiments of the present invention: generating shared announcement information based on the sub-program related information; The method may further include a step of announcing the shared announcement information by voice.

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

[0094] For example, when the subprogram-related information is acquired, the voice announcement system of the SDK can be triggered to play the sharing announcement information. After the car owner confirms the information by voice, the openMiniProgram() method of the framework can be triggered to open the target subprogram page, allowing the subprogram to be viewed and shared on the in-vehicle device.

[0095] Specifically, the content of the shared announcement information may be, "XX Movie, a small scene of life services shared by your friend A, will soon open the details page of the movie 'YY'. Do you want to open it or ignore it?" or "Privileged Refueling, a small scene of car owner services shared by your friend A, 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 above embodiments, the following will provide further details by way of examples.

[0097] This embodiment will be described with reference to the system shown in FIG.

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

[0099] In step 901, the sharing initiator displays a subprogram sharing page of the subprogram, and 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.

[0100] When the sharing initiator (e.g., the mobile phone) needs to share a sub-program, i.e., when a sub-program is opened, the user can click the "More" button in the upper right corner to pop up more options and select a sharing method selection control from among them.

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

[0102] In step 903, if the target sharing method selection control corresponds to the Bluetooth communication method, a sub-program sharing request is sent to the target smart vehicle side through the Bluetooth communication connection between the target smart vehicle side and the sharing initiation side, and the sub-program sharing request includes sub-program related information of the sub-program requested to be shared by the sharing initiation side.

[0103] When sharing a subprogram over short distances, the mobile phone first selects "Share via Bluetooth" on the mini program page and pairs it with the in-vehicle device via Bluetooth. Once the connection is complete, the mobile phone automatically calls the sharing interface and transmits and stores information such as the subprogram's AppID, page information, and page parameters to the in-vehicle device via Bluetooth.

[0104] In step 904, the target smart vehicle receives a subprogram sharing request from the sharing initiator, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared.

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

[0106] Specifically, the MossSDK may recognize a keyword with moss transmitted from the sharing initiator after the Bluetooth communication connection is established.

[0107] In step 905, if the target sharing method selection control corresponds to a long-distance wireless communication method, determine a cloud side corresponding to the target smart vehicle side, and send a sub-program sharing request to the cloud side through the long-distance communication connection between the cloud side and the sharing initiation side, where the sub-program sharing request includes sub-program-related information of the sub-program requested to be shared by the sharing initiation side, and the sub-program sharing request is sent by the cloud side to the target smart vehicle side.

[0108] Bluetooth technology is not useful when sharing subprograms over long distances. In this case, subprogram sharing can be achieved through wireless network communication. First, the mobile phone still voluntarily selects "Share to vehicle device" from the mini program page. Before calling the interface, identity and authority authentication can be performed first. The interface can be called only after the authentication is passed. In MossSDK, an exposed interface can be designed to receive subprogram parameters, including information such as the subprogram's AppID, page information, and page parameters.

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

[0110] Assuming a secure connection has been established, if there is a need to share a subprogram on the mobile phone, i.e., when a subprogram is opened, the user can click the "More" button in the upper right corner to pop up more options, and by selecting the "Share to vehicle device" button, the cloud interface will be called, and information such as the subprogram's AppID, page information, and page parameters will be directly transmitted over the network. By analyzing this, all parameters that can open the subprogram can be obtained.

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

[0112] For example, if the subprogram is an in-vehicle small scene, the smart vehicle can trigger the SDK's voice announcement system to play, for example, "Do you want to open the xxx small scene of xxx type shared by xxx? Or do you want to ignore it?" After the car owner confirms the voice, the framework's openMiniProgram() method is triggered to open the small scene, allowing the small scene to be viewed and shared on the in-vehicle device.

[0113] In step 908, the target smart vehicle receives the user's voice input, analyzes the voice input, and obtains a sharing confirmation result. In response to the sharing confirmation result indicating that sharing is accepted, the target subprogram page corresponding to the subprogram is displayed based on the subprogram-related information.

[0114] As can be seen from the above, in an embodiment of the present invention, the sharing initiator displays a subprogram sharing page of a subprogram, and in response to a trigger operation on a target sharing method selection control among the sharing method selection controls, acquires subprogram-related information of the subprogram from the target smart vehicle, and transmits 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 subprogram content information and at least one sharing method selection control, each of which corresponds to a communication method. The subprogram sharing request includes subprogram-related information of the subprogram 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 an embodiment of the present invention, the user of the sharing initiator can select one communication method using the sharing method selection control on the subprogram sharing page to share and display the subprogram on the target smart vehicle. This enables subprogram sharing between a smart vehicle and a user terminal using various communication methods, improving the user experience of the smart vehicle.

[0115] In order to better implement the above method, the embodiment of the present invention accordingly further provides a sub-program sharing device, which may be incorporated into the sharing initiator. The meanings of the terms here are the same as those in the above sub-program sharing method, and specific implementation details can be found in the description of the embodiment of the method.

[0116] Referring to Figure 10, an embodiment of the present invention further provides a subprogram sharing device applicable to a sharing initiator. a first page display unit 1001 that can be used to display a subprogram sharing page of a subprogram, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; an information obtaining unit 1002, which can be used to obtain sub-program-related information of the sub-program in response to a trigger operation on a target sharing method selection control among the sharing method selection controls; The information transmitting unit 1003 may be used to send a sub-program sharing request to the target smart vehicle side based on a communication method corresponding to the target sharing method selection control, wherein the sub-program sharing request includes sub-program-related information of the sub-program requested to be shared by the sharing initiating side, and a target sub-program page corresponding to the sub-program is displayed by the target smart vehicle side based on the sub-program-related information.

[0117] To better implement the subprogram sharing method provided in the embodiments of the present application, in one embodiment, another subprogram sharing device is further provided, which may be integrated into the smart vehicle side. The terms used here have the same meaning as those in the above subprogram sharing method, and specific implementation details can be found in the description of the embodiments of the method.

[0118] Referring to Figure 11, an embodiment of the present invention further provides another sub-program sharing device applicable to a smart vehicle side. There is a communication connection between the smart vehicle side and at least one sharing initiator, and the device: a request receiving unit 1101 that can be used to receive a subprogram sharing request sent 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 requested to be shared by the sharing initiator, the target sharing method selection control being included in a subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one communication method, the terminal device responding to a trigger operation on the target sharing method selection control among the sharing method selection controls to obtain the subprogram-related information of the subprogram from the target smart vehicle side and then sending the subprogram sharing request; a second page display unit 1102 that can be used to display a sharing confirmation page based on the subprogram-related information; It may also include a sub-program page display unit 1103 that can be used to display a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation.

[0119] In some embodiments, as shown in FIG. 12 , the subprogram sharing device provided in the embodiments of the present invention may further include an audio announcement unit 1104, which can be used to generate shared announcement information based on the subprogram-related information and announce the shared announcement information audio-wise.

[0120] Furthermore, an embodiment of the present invention further provides an electronic device. This electronic device may be a terminal or a server. As shown in FIG. 13, a schematic diagram of the configuration of an electronic device according to an embodiment of the present invention is shown. Specifically, The electronic device may include components such as radio frequency (RF) circuitry 1301, memory 1302 including one or more computer-readable storage media, input unit 1303, display unit 1304, sensors 1305, audio circuitry 1306, wireless fidelity (WiFi) module 1307, processor 1308 including one or more processing cores, and power supply 1309. As will be appreciated by those skilled in the art, the configuration of the electronic device shown in FIG. 13 is not intended to limit the electronic device, and the electronic device may include more or fewer components than those shown, may combine some components, or may have a different arrangement of components. The RF circuitry 1301 can be used to send and receive signals during transmission and reception of information or during a call, and, in particular, receives downlink information from a base station and passes it to one or more processors 1308 for processing, as well as transmits data on the uplink to the base station. Typically, the RF circuitry 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, etc. The RF circuitry 1301 can also communicate with networks and other devices via wireless communications. Wireless communication may use any communication standard or protocol, including, but 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, Short Messaging Service (SMS), etc.

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

[0122] The input unit 1303 can be used to receive input numeric or character information and generate signal inputs via a keyboard, mouse, joystick, optical, or trackball for user settings and function control. Specifically, in one embodiment, the input unit 1303 may include a touch-sensitive surface and other input devices. The touch-sensitive surface, also known as a touch screen or touch pad, can collect a user's touch operations on or near the touch-sensitive surface (e.g., operations performed by a user on or near the touch-sensitive surface using any suitable object or accessory, such as a finger, stylus, etc.) and drive a corresponding connected device 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 user's touch direction, detects signals resulting from the touch operation, and transmits the signals to the touch controller. The touch controller can receive touch information from the touch detection device, convert it into touch point coordinates, and transmit them to the processor 1308, as well as receive and execute commands sent from the processor 1308. The touch-sensitive surface may also be realized in multiple forms, such as resistive, capacitive, infrared, or surface acoustic wave. The input unit 1303 may also include other input devices in addition to the touch-sensitive surface. Specifically, the other input devices may include, but are not limited to, one or more of 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 or provided by a user, as well as various graphical user interfaces of the electronic device. These graphical user interfaces may consist of graphics, text, icons, video, 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), organic light-emitting diode (OLED), or the like. Additionally, a touch-sensitive surface may cover the display panel. When the touch-sensitive surface detects a touch on or near the touch-sensitive surface, it transmits the touch to the processor 1308 to determine the type of touch event. The processor 1308 then provides a corresponding visual output to the display panel depending on the type of touch event. While the touch-sensitive surface and the display panel are shown as two separate components implementing input and output functions in FIG. 13 , in some embodiments, the touch-sensitive surface and the display panel may be integrated to implement 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, or 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 close 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) and can detect the magnitude and direction of gravity when the electronic device is stationary. This can be used for applications that recognize the mobile phone's orientation (e.g., switching the screen between portrait and landscape orientation, related games, magnetometer orientation calibration), vibration recognition-related functions (e.g., pedometer, tap), etc. Other sensors that can be installed in the electronic device, such as a gyroscope, barometer, hygrometer, thermometer, and infrared sensor, will not be described here.

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

[0126] WiFi is a short-range wireless transmission technology. The WiFi module 1307 enables electronic devices to help users send and receive emails, browse web pages, and access streaming media. WiFi provides users with wireless broadband Internet access. Although FIG. 13 shows the WiFi module 1307, it should be understood that the WiFi module 1307 is not an essential component of the electronic device and can be completely omitted, if necessary, without changing the essence of the invention.

[0127] The processor 1308 is the control center of the electronic device, connecting various parts of the entire mobile phone using various interfaces and lines, executing or executing software programs and / or modules stored in the memory 1302, and accessing data stored in the 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 processes the operating system, user interface, application programs, etc., while the modem processor mainly processes wireless communications. As can be appreciated, the modem processor need not be incorporated into the processor 1308.

[0128] The electronic device further includes a power source 1309 (e.g., a battery) that provides power to each component. In some embodiments, the power source may be logically connected to the processor 1308 via a power management system, which performs functions such as charging, discharging, and managing power consumption. The power source 1309 may include any component, such as one or more DC or AC power sources, a recharging system, a power fault detection circuit, a power converter or inverter, and a power status indicator.

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

[0130] An 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 the processor 1308 executes an application program stored in the memory 1302, a step of displaying a subprogram sharing page of the subprogram, the subprogram sharing page including content information of the subprogram and at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; Acquiring subprogram-related information of the subprogram from the target smart vehicle in response to a trigger operation on a target sharing method selection control of the sharing method selection controls; The method can also include the step of sending a subprogram sharing request to the target smart vehicle side 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 requested to be shared by the sharing initiation side, and a target subprogram page corresponding to the subprogram is displayed by the target smart vehicle side based on the subprogram-related information.

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

[0133] When the processor 1308 executes an application program stored in the memory 1302, receiving a subprogram sharing request from a sharing initiator, the subprogram sharing request including subprogram-related information of the subprogram for which sharing is requested; Displaying a sharing acceptance confirmation page based on the subprogram-related information; In response to a user's sharing acceptance operation, a step of displaying a target sub-program page corresponding to the sub-program based on the sub-program related information can be realized.

[0134] As can be understood by those skilled in the art, all or part of the steps of each method in the above embodiments may be performed by instructions or by controlling related hardware through instructions, which may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0135] To this end, an embodiment of the present invention provides a computer-readable storage medium storing a plurality of instructions, which, when loaded by a processor, can cause the processor to execute steps of any one of the subprogram sharing methods provided in the embodiment of the present invention. For example, the instructions can cause the processor to execute steps such as:

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

[0137] The instructions, when loaded by the processor, a step of displaying a subprogram sharing page of the subprogram, the subprogram sharing page including content information of the subprogram and at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; Acquiring subprogram-related information of the subprogram from the target smart vehicle in response to a trigger operation on a target sharing method selection control of the sharing method selection controls; The method can also include the step of sending a subprogram sharing request to the target smart vehicle side 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 requested to be shared by the sharing initiation side, and a target subprogram page corresponding to the subprogram is displayed by the target smart vehicle side based on the subprogram-related information.

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

[0139] The instructions, when loaded by the processor, receiving a subprogram sharing request from a sharing initiator, the subprogram sharing request including subprogram-related information of the subprogram for which sharing is requested; Displaying a sharing acceptance confirmation page based on the subprogram-related information; In response to a user's sharing acceptance operation, a step of displaying a target sub-program page corresponding to the sub-program based on the sub-program related information can be realized.

[0140] For the specific implementation of each of the above operations, please refer to the above-mentioned embodiment, but the description will be omitted here.

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

[0142] The instructions stored in the computer-readable storage medium can execute the steps of any one of the subprogram sharing methods provided in the embodiments of the present invention, thereby achieving the beneficial effects that can be achieved by any one of the subprogram sharing methods provided in the embodiments of the present invention, the details of which can be referred to the above-mentioned embodiments and will not be described again here.

[0143] According to one aspect of the present application, there is further provided a computer program product or computer program including computer instructions stored in a computer-readable storage medium, which a processor of an electronic device reads from the computer-readable storage medium and, when executed by the processor, causes the electronic device to perform the methods provided in various optional implementations of the above embodiments.

[0144] The above provides a detailed description of the subprogram sharing method, device, electronic device, and storage medium provided in the embodiments of the present invention. This specification describes the principles and embodiments of the present invention by applying specific examples. The above description of the examples is only used to help understand the method of the present invention and its core idea. Furthermore, those skilled in the art may change both the specific embodiment and the scope of application based on the idea 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 1st page display unit 1002 Information Acquisition Unit 1003 Information Transmission Unit 1101 Request Receiving Unit 1102 Second page display unit 1103 Subprogram page display unit 1104 Voice Announcement Unit 1301 Radio Frequency (RF) Circuits 1302 memory 1303 Input Unit 1304 Display unit 1305 Sensor 1306 Audio Circuit 1307 WiFi module 1308 processor 1309 Power supply

Claims

1. A subprogram sharing method executed by a terminal device, comprising: a step of displaying a subprogram sharing page of a subprogram, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; Acquiring subprogram-related information of the subprogram from a target smart vehicle in response to a trigger operation on a target sharing method selection control of the sharing method selection controls; sending a sub-program sharing request to the target smart vehicle side according to a communication method corresponding to the target sharing method selection control, the sub-program sharing request including the sub-program related information, and a target sub-program page corresponding to the sub-program is displayed by the target smart vehicle side according to the sub-program related information; Subprogram sharing method.

2. The target sharing method selection control corresponds to a Bluetooth communication method, and the step of sending a sub-program sharing request to the target smart vehicle according to the communication method corresponding to the target sharing method selection control includes: generating a Bluetooth sharing event based on the Bluetooth communication method and the sub-program related information; sending the Bluetooth sharing event to the target smart vehicle side via a Bluetooth communication connection between the target smart vehicle side and the terminal device; The subprogram sharing method according to claim 1 .

3. The target sharing mode selection control corresponds to a long-distance wireless communication mode, and the step of sending a sub-program sharing request to the target smart vehicle according to the communication mode corresponding to the target sharing mode selection control includes: generating a long-distance shared event based on the long-distance wireless communication method and the sub-program related information; determining a cloud side corresponding to the target smart vehicle side; sending the long-distance shared event to the cloud side through a long-distance communication connection between the cloud side and the terminal device, wherein the long-distance shared event is sent by the cloud side to the target smart vehicle side; The subprogram sharing method according to claim 1 .

4. the step of transmitting the long-distance shared event to the cloud side via a long-distance communication connection between the cloud side and the terminal device, sending 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 an identity check of the terminal device is performed by the cloud side based on the first identity authentication information; receiving an identity check result of the terminal device by the cloud side; In response to the identity check result being a pass, transmitting the long-distance sharing event to the cloud side via the long-distance communication connection. The subprogram sharing method according to claim 3 .

5. The step of sending a sub-program sharing request to the target smart vehicle according to a communication method corresponding to the target sharing method selection control includes: calling a sharing interface of the target smart vehicle according to a communication method corresponding to the target sharing method selection control; and sending a sub-program sharing request to the target smart vehicle through the sharing interface. The subprogram sharing method according to claim 1 .

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

7. A subprogram sharing method executed by a smart vehicle side, receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared by the terminal device, the target sharing method selection control being included in a subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method, the terminal device responding to a trigger operation on a target sharing method selection control among the sharing method selection controls to acquire subprogram-related information of the subprogram from a target smart vehicle and then transmitting the subprogram sharing request; displaying a sharing acceptance confirmation page based on the subprogram-related information; and displaying a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation. Subprogram sharing method.

8. before the step of displaying a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation, generating shared announcement information based on the sub-program related information; announcing the shared announcement information by voice. The subprogram sharing method according to claim 7 .

9. The step of displaying a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation includes: receiving a voice input from a user and analyzing the voice input to obtain a sharing confirmation result; and in response to the sharing confirmation result indicating that sharing is accepted, displaying a target sub-program page corresponding to the sub-program based on the sub-program related information. The subprogram sharing method according to claim 7 .

10. The step of displaying a sharing acceptance confirmation page based on the subprogram related information includes: obtaining the subprogram-related information based on the subprogram sharing request; obtaining sub-program page display parameters by analyzing the sub-program related information; and displaying a sharing acceptance confirmation page based on the sub-program 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 requested to be shared by the sharing initiation side, receiving a subprogram sharing request sent from a cloud side corresponding to the smart vehicle side, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared from 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 a target sharing method selection control; After the step of receiving a sub-program sharing request, the sub-program sharing method includes: performing an identity check on the cloud side based on the second identity authentication information to obtain an identity check result corresponding to the cloud side; and in response to the identity check result being a pass, analyzing the sub-program sharing request to obtain the sub-program related information. The subprogram sharing method according to claim 7 .

12. The step of receiving a subprogram sharing request comprises: receiving externally transmitted data and detecting the externally transmitted data according to a detection code for a sub-program shared event; If the external transmission data includes a sub-program share event, analyzing the external transmission data to obtain a sub-program share request corresponding to the sub-program share event. The subprogram sharing method according to claim 7 .

13. A subprogram sharing device applied to a terminal device, a first page display unit for displaying a subprogram sharing page of a subprogram, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method; an information acquisition unit for acquiring subprogram-related information of the subprogram from a target smart vehicle in response to a trigger operation on a target sharing mode selection control of the sharing mode selection controls; an information transmission unit for transmitting a sub-program sharing request to the target smart vehicle according to a communication method corresponding to the target sharing method selection control, wherein the sub-program sharing request includes the sub-program related information, and a target sub-program page corresponding to the sub-program is displayed by the target smart vehicle according to the sub-program related information; Subprogram sharing device.

14. A subprogram sharing device applied to a smart vehicle side, a request receiving unit for receiving a subprogram sharing request transmitted from a terminal device based on a communication method corresponding to a target sharing method selection control, the subprogram sharing request including subprogram-related information of the subprogram requested to be shared by the terminal device, the target sharing method selection control being included in a subprogram sharing page of the subprogram displayed on the terminal device, the subprogram sharing page including at least one sharing method selection control, each of the sharing method selection controls corresponding to one type of communication method, the terminal device responding to a trigger operation on a target sharing method selection control among the sharing method selection controls to acquire subprogram-related information of the subprogram from a target smart vehicle and then transmitting the subprogram sharing request; a second page display unit for displaying a sharing confirmation page based on the sub-program related information; a sub-program page display unit that displays a target sub-program page corresponding to the sub-program based on the sub-program related information in response to a user's sharing acceptance operation; Subprogram sharing device.

15. 13. An electronic device comprising a memory and a processor, wherein an application program is stored in the memory, and the processor executes the steps of the subprogram sharing method described in any one of claims 1 to 12 by executing the application program in the memory.

16. 13. A computer-readable storage medium having stored thereon a plurality of instructions, the instructions being configured, when loaded by a processor, to cause the execution of the steps of the method for sharing subprograms according to any one of claims 1 to 12.

17. A computer program product comprising a computer program or instructions which, when executed by a processor, causes the computer program or instructions to implement the steps of the method for sharing subprograms according to any one of claims 1 to 12.

Images