Display content sharing method and system

Abstract

According to the display content sharing method and system provided by the invention, when the display content is shared, the sharing vehicle side converts the display content resource into the resource coding configuration set through coding standardization to upload the resource coding configuration set, so that the occupation of the shared content on cloud resources is reduced. And the shared vehicle end can reproduce the display content of the sharing vehicle end only by inputting the request short code. A unique short code is used for replacing a display content file for display content sharing, conversion from file transmission to short code interaction is achieved through display content sharing, consumption of system resources in the display content sharing process is reduced, display content sharing and reproduction operation is simplified, the data transmission amount is reduced by adopting a short code sharing mechanism, and the display content sharing efficiency is improved. The data transmission time is shortened, the sharing efficiency is improved, and the user experience is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle data sharing, and in particular to a display content sharing method and system. BACKGROUND

[0002] Personalization customization of display content of a vehicle-mounted instrument has gradually become an important demand for users to pursue differentiated experiences. However, the display content customized by the user often lacks a convenient sharing approach, and it is difficult to ensure the compatibility of the display content between different vehicles or system versions, which leads to the fact that the display content created by the user cannot be directly and efficiently experienced by other users, thereby limiting the spread and interaction of personalized experiences. SUMMARY

[0003] In view of the above, the purpose of the present application is to provide a display content sharing method and system for simplifying the sharing process of display content between different vehicles and systems and improving the sharing efficiency of display content.

[0004] To achieve the above purpose, the present application provides a display content sharing method applied to the cloud, which comprises the following steps: obtaining a resource code configuration set corresponding to the customized display content uploaded by a sharing vehicle end, determining a unique short code according to the resource code configuration set, and storing the unique short code and the resource code configuration set to a sharing database; in response to receiving a request short code sent by a shared vehicle end, verifying the validity of the request short code according to the sharing database; in response to the request short code being valid, issuing a display style graph corresponding to the request short code to the shared vehicle end; according to a confirmation instruction for the display style graph fed back by the shared vehicle end, sending a shared resource code configuration set corresponding to the request short code in the sharing database to the shared vehicle end.

[0005] Optionally, the step of determining a unique short code according to the resource code configuration set comprises the following steps: performing validity verification on the resource code configuration set to obtain a verification result; in response to the verification result being that the resource code configuration set is valid, determining a candidate short code according to the resource code configuration set; determining the unique short code according to the sharing database and the candidate short code.

[0006] Optionally, the step of determining a candidate short code according to the resource code configuration set comprises the following steps: performing hash calculation on the resource code configuration set to obtain a hash value; According to a preset default intercepting position, the hash value is intercepted to obtain an intercepted byte, and the intercepted byte is converted into integer data; The integer data is encoded to obtain the candidate short code.

[0007] Optionally, the determining the unique short code according to the shared database and the candidate short code comprises: In response to the absence of a conflict short code identical to the candidate short code in the shared database, the candidate short code is determined as the unique short code; In response to the presence of a conflict short code identical to the candidate short code in the shared database, a conflict number is determined; In response to the conflict number being less than or equal to a preset number threshold, a default intercepting position is adjusted to obtain a new intercepting position, and a new candidate short code is determined according to the new intercepting position; In response to the absence of a conflict short code identical to the new candidate short code in the shared database, the new candidate short code is determined as the unique short code.

[0008] Optionally, the verifying the validity of the request short code according to the shared database comprises: In response to the presence of a unique short code identical to the request short code in the shared database, the request short code is determined as valid; In response to the absence of a unique short code identical to the request short code in the shared database, the request short code is determined as invalid.

[0009] Optionally, the issuing, to the shared vehicle end, of a display style diagram corresponding to the request short code comprises: A shared resource encoding configuration set corresponding to the request short code is determined in the shared database; A display style diagram in the shared resource encoding configuration set is extracted, and the display style diagram is issued to the shared vehicle end.

[0010] Optionally, the sharing method of display content is also applied to a sharing vehicle end, and the method comprises: An original resource associated with display content is determined, and the original resource is classified and abstracted to obtain a standardized resource library; In response to receiving a sharing request of custom display content from a user, a display style diagram corresponding to the custom display content is determined, and a custom resource used by the custom display content is determined; A plurality of resource encodings corresponding to the custom resource are determined in the standardized resource library, and the plurality of resource encodings and the display style diagram are integrated to obtain a resource encoding configuration set, and the resource encoding configuration set is shared to a cloud end.

[0011] Optionally, the classifying and abstracting the original resources to obtain the standardized resource library comprises: classifying the original resources according to display content composition to obtain a plurality of single-class resources; abstracting core attributes of each single-class resource to obtain attribute data, and converting the attribute data into a unified standard format to obtain sequence data; generating a unique identification code based on the sequence data, integrating the unique identification code and the sequence data to obtain the standardized resource library.

[0012] Optionally, the display content sharing method is also applied to the shared vehicle end, and the method comprises: sending a request short code to the cloud end according to user demand, and receiving a display style graph corresponding to the request short code sent by the cloud end; displaying the display style graph and a preset selection pop-up window; wherein the selection pop-up window comprises a selection prompt text, a confirmation display control and a cancel display control; in response to a first touch operation of the confirmation display control, sending a confirmation instruction to the cloud end, and receiving a shared resource encoding configuration set corresponding to the request short code sent by the cloud end; restoring resource encoding in the shared resource encoding configuration set to display content resources, and generating display content according to the display content resources.

[0013] Based on the same inventive concept, the application further provides a display content sharing system, comprising a cloud end, a shared vehicle end and a shared vehicle end: The cloud end is configured to: obtain a resource encoding configuration set corresponding to custom display content uploaded by the shared vehicle end, determine a unique short code according to the resource encoding configuration set, and store the unique short code and the resource encoding configuration set to a shared database; in response to receiving a request short code sent by the shared vehicle end, verify the validity of the request short code according to the shared database; in response to the request short code being valid, issue a display style graph corresponding to the request short code to the shared vehicle end; and according to the confirmation instruction of the shared vehicle end feedback to the display style graph, send the shared resource encoding configuration set corresponding to the request short code in the shared database to the shared vehicle end; The shared vehicle end is configured to determine an original resource associated with the display content, classify and abstract the original resource to obtain a standardized resource library, determine a display style diagram corresponding to the custom display content and determine a custom resource used by the custom display content in response to receiving a sharing request of the custom display content by a user, determine a plurality of resource codes corresponding to the custom resource in the standardized resource library, integrate the plurality of resource codes and the display style diagram to obtain a resource code configuration set, and share the resource code configuration set to the cloud end. The shared vehicle end is configured to send a request short code to the cloud end according to a user demand, receive a display style diagram corresponding to the request short code sent by the cloud end, display the display style diagram and a preset selection pop-up window, wherein the selection pop-up window includes a selection prompt text, a confirmation display control and a cancel display control, send a confirmation instruction to the cloud end in response to a first touch operation of the confirmation display control, receive a shared resource code configuration set corresponding to the request short code sent by the cloud end, restore the resource code in the shared resource code configuration set to a display content resource, and generate display content according to the display content resource.

[0014] As can be seen from the above, the display content sharing method and system provided by the application obtain a resource code configuration set corresponding to custom display content uploaded by a sharing vehicle end, determine a unique short code according to the resource code configuration set, store the unique short code and the resource code configuration set in a sharing database, verify the validity of a request short code sent by a shared vehicle end according to the sharing database in response to receiving the request short code, issue a display style diagram corresponding to the request short code to the shared vehicle end in response to the request short code being valid, and send a shared resource code configuration set corresponding to the request short code in the sharing database to the shared vehicle end according to a confirmation instruction of the display style diagram fed back by the shared vehicle end. When sharing display content, the sharing vehicle end converts display content resources into a resource code configuration set through coding standardization for uploading, reducing the occupation of cloud resources by shared content. The shared vehicle end only needs to input a request short code to reproduce the display content of the sharing vehicle end. The unique short code is used instead of a display content file for display content sharing, the display content sharing is changed from file transmission to short code interaction, the consumption of system resources in the display content sharing process is reduced, the operation of display content sharing and reproduction is simplified, the short code sharing mechanism reduces the data transmission amount, shortens the data transmission time, improves the sharing efficiency, and improves the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the application or the related art, the drawings needed to be used in the embodiments or the related art description will be briefly introduced. Obviously, the drawings in the following description are only embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0016] Figure 1 Flow chart for the display content sharing method applied by the embodiment of the application to the cloud end; Figure 2a Flow chart for determining a unique short code according to a resource encoding configuration set by the embodiment of the application; Figure 2b Flow chart for generating a short code by the embodiment of the application; Figure 3a Flow chart for verifying the effectiveness of a request short code by the embodiment of the application; Figure 3b Flow chart for cloud end mapping an encoding configuration set by the embodiment of the application; Figure 4 Flow chart for issuing a display style map to a shared vehicle end by the embodiment of the application; Figure 5a Flow chart for the display content sharing method applied by the embodiment of the application to the shared vehicle end; Figure 5b Flow chart for classifying and abstracting an original resource by the embodiment of the application; Figure 6a Flow chart for the display content sharing method applied by the embodiment of the application to the shared vehicle end; Figure 6b Flow chart for the shared vehicle end to request display content by the embodiment of the application; Figure 6c Flow chart for the shared vehicle end to reproduce display content by the embodiment of the application; Figure 7 Schematic diagram of the display content sharing system by the embodiment of the application; Figure 8 Schematic diagram of the timing architecture of the sharing process by the embodiment of the application; Figure 9 Schematic diagram of the electronic device by the embodiment of the application. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the application more clear, the application will be further described in detail below with reference to the embodiments and the drawings.

[0018] For ease of description, unless otherwise defined, technical terms or scientific terms used in the embodiments of the present application shall have the ordinary meaning understood by one of ordinary skill in the art to which the present application pertains. The terms "first", "second", and similar terms used in the embodiments of the present application do not denote any order, quantity, or importance, but are used to distinguish different components. The terms "include", "contain", and similar terms mean that the elements or objects before the terms encompass the elements or objects listed after the terms and their equivalents, and do not exclude other elements or objects. The terms "connect" or "connected" and similar terms do not mean physical or mechanical connection, but can include electrical connection, whether direct or indirect. The terms "upper", "lower", "left", "right", and the like are used only to represent relative positional relationships, and when the absolute positions of the described objects change, the relative positional relationships can also change accordingly.

[0019] In this document, it should be understood that any number of elements in the drawings are used for illustration only and not limitation, and any naming is only for differentiation and does not have any limiting meaning.

[0020] Based on the description of the above background art, there are also the following cases in the related art: The personalized customization of the display content of the vehicle-mounted instrument gradually becomes an important demand for users to pursue differentiated experiences. However, the display content customized by the user often lacks a convenient sharing approach, and it is difficult to ensure the compatibility of the display content between different vehicles or system versions, which leads to the fact that the display content created by the user cannot be directly and efficiently experienced by other users, and limits the spread and interaction of personalized experiences. In the related art, the display content resource files are directly transmitted (or transmitted after compression) between different vehicles, different vehicle models, and different systems, and the strategy of directly transmitting the files has the following defects: System isolation: the real-time operating system (QNX Neutrino Real-Time Operating System, QNX) in the vehicle is an embedded real-time operating system, and the instrument display content resource is usually bound to a specific vehicle model and system version, which lacks universality and is not conducive to the sharing of personalized display content.

[0021] Weak compatibility: the types of display content resources supported by instruments of different vehicle models and different real-time operating system versions may differ, and directly applying display content resource files shared by other vehicles may cause display errors or functional abnormalities.

[0022] Large resource size and transmission dependent on network: display content resources are usually large in size, and direct transmission or downloading from a cloud server is time-consuming and unstable, and the problem of time-consuming downloading is more prominent when the network stability in the vehicle-mounted environment is insufficient.

[0023] Lack of lightweight and universal sharing media: unable to achieve cross-device fast reproduction of display content in a simple and efficient way, resulting in low efficiency of display content sharing.

[0024] As a real-time operating system, the QNX system has strict requirements on resource occupation and response speed in a vehicle scene. A display content sharing scheme directly transmitting display content resource files cannot meet the lightweight requirement. Therefore, an efficient and low-resource-consumption display content sharing method and system are urgently needed.

[0025] The display content sharing method and system provided by the embodiments of the application obtain a resource code configuration set corresponding to custom display content uploaded by a sharing vehicle end, determine a unique short code according to the resource code configuration set, and store the unique short code and the resource code configuration set to a sharing database. In response to receiving a request short code sent by a shared vehicle end, the validity of the request short code is verified according to the sharing database. In response to the request short code being valid, a display style graph corresponding to the request short code is issued to the shared vehicle end. According to the confirmation instruction of the shared vehicle end for the display style graph, the shared resource code configuration set corresponding to the request short code in the sharing database is sent to the shared vehicle end. When sharing display content, the sharing vehicle end converts display content resources into a resource code configuration set for uploading through coding standardization, reducing the occupation of cloud resources by shared content. The shared vehicle end only needs to input the request short code to reproduce the display content of the sharing vehicle end. Using a unique short code instead of a display content file for display content sharing changes the display content sharing from file transmission to short code interaction, reduces the consumption of system resources in the display content sharing process, simplifies the operation of display content sharing and reproduction, and uses a short code sharing mechanism to reduce the data transmission amount, shorten the data transmission time, improve the sharing efficiency, and improve the user experience.

[0026] The display content sharing method provided by the embodiments of the application will be described in detail below with reference to the accompanying drawings.

[0027] In some embodiments, as shown in Figure 1 The display content sharing method is applied to a cloud end, and the method comprises the following steps. Step 101: Obtain a resource code configuration set corresponding to custom display content uploaded by a sharing vehicle end, determine a unique short code according to the resource code configuration set, and store the unique short code and the resource code configuration set to a sharing database.

[0028] In a specific implementation, the display content includes a custom theme, a custom icon, a custom wallpaper, etc. Before sharing the display content, the sharing vehicle end and the shared vehicle end standardize the attributes of all original resources to obtain resource codes corresponding to the resource attributes, so that the same serialization result is generated as long as the attribute combinations of different resources are the same, the same display content is obtained, and the custom display content is compatible between different vehicles and systems, thereby avoiding the problems of display failure and error display.

[0029] Taking the custom theme as an example, the resource code standardization process of the sharing vehicle end (and the shared vehicle end) is as follows: 1. Preliminary processing and identification classification are performed on all original resources used for theme construction, mainly including five categories: icon category, color category, layout category, font category, and animation category. 2. Abstract attribute: For each category of original resources, the core attributes are extracted to obtain attribute data.

[0030] The icon category resource abstracts attributes such as size, color, and shape. The color category resource abstracts attributes such as color value and transparency. The layout category resource abstracts attributes such as size, position, and layout type. The font category resource abstracts attributes such as font type, font size, and font style. The animation category resource abstracts attributes such as playback time, definition, resolution, and frame rate.

[0031] 3. Serialization: The abstracted attribute data is converted into a uniform format, i.e., a JSON string with consistent length, to obtain sequence data, so that the same theme is generated as long as the attribute combinations of different theme resources are the same.

[0032] 4. Generate a unique identifier based on the serialized sequence data.

[0033] 5. Establish a standardized resource library: Store the serialized sequence resource data and the unique identifier in the resource library to complete resource storage and local management.

[0034] The user constructs custom display content on the sharing vehicle end through custom operations. The sharing vehicle end records the attribute composition of different custom resources in the custom display content in real time, determines the corresponding sequence data in the standardized resource library according to the attribute composition, obtains the resource code, and records the corresponding display style diagram after the custom display content is constructed. The display style diagram and the resource code are integrated to obtain a corresponding resource code configuration set. When the user agrees to share the custom display content, the resource code configuration set is uploaded to the cloud.

[0035] After the cloud obtains the resource encoding configuration set uploaded by the sharing vehicle end, determines that the resource encoding configuration set is valid, performs hash calculation according to the resource encoding configuration set, obtains a hash value corresponding to the resource encoding configuration set, intercepts at least one byte from the hash value, converts the intercepted byte into a frame number, encodes the integer into a Base62 encoded string, generates a candidate short code, and checks the uniqueness of the candidate short code: If the candidate short code already exists (there is a short code in the sharing database that is the same as the candidate short code, resulting in a conflict), record the conflict and check whether the maximum number of retries is reached.

[0036] If the maximum number of retries is reached, the process enters an error handling step, prompting "Error, unable to generate a unique short code". If the maximum number of retries is not reached, increase the retry counter and adjust the interception position to recalculate the hash value.

[0037] If the candidate short code is unique, the candidate short code is determined as the unique short code corresponding to the resource encoding configuration set, and the unique short code and the resource encoding configuration set are stored in the sharing database for sharing. At the same time, the unique short code is sent to the sharing vehicle end, so that the sharing vehicle end user can actively share the display content.

[0038] That is, the cloud does not need to upload the entire display content file from the sharing vehicle end, but only needs to upload the resource encoding configuration set to complete the sharing, realizes lightweight display content sharing, and improves sharing efficiency and stability.

[0039] Step 102: In response to receiving the request short code sent by the shared vehicle end, verify the validity of the request short code according to the sharing database.

[0040] In specific implementation, after the custom display content is shared to the cloud, the shared vehicle end can obtain the unique short code of the shared custom display content through various channels (such as online preview, offline user notification, etc.), and then request to reproduce the shared custom display content by inputting the unique short code. After the user inputs the unique short code, the shared vehicle end sends the input or selected unique short code to the source end as a request short code to request display content reproduction.

[0041] After the cloud receives the request short code sent by the shared vehicle end, the request short code is matched with the sharing database. If there is a short code in the sharing database that is the same as the request short code, it means that the request short code sent by the shared vehicle end is valid, and the request of the shared vehicle end can be responded. If there is no short code in the sharing database that is the same as the request short code, it means that the request short code sent by the shared vehicle end is invalid, and the request of the shared vehicle end is not responded, and the shared vehicle end is informed that the request short code is incorrect, please correct it and input again.

[0042] Step 103: in response to the request short code being valid, issuing a display style graph corresponding to the request short code to the shared vehicle end.

[0043] In specific implementation, after determining that the request short code is valid, the cloud end issues a display style graph corresponding to the request short code to the shared vehicle end, so that the shared vehicle end user can preview the display content style to be reproduced, and ensure that the reproduced display content meets the user's use requirements.

[0044] Step 104: according to the confirmation instruction for the display style graph fed back by the shared vehicle end, sending the shared resource encoding configuration set corresponding to the request short code in the sharing database to the shared vehicle end.

[0045] In specific implementation, if the user judges that the display style graph is consistent with the expected display content effect, the user applies the display content by performing a confirmation operation. At this time, the shared vehicle end feeds back a confirmation instruction for the display style graph to the cloud end. After receiving the confirmation instruction, the cloud end sends the shared resource encoding configuration set corresponding to the request short code in the sharing database to the shared vehicle end, so that the shared vehicle end determines the attributes of each resource type according to the shared resource encoding configuration set, and uses the same attributes of the same type of resources to realize the reproduction of the shared custom display content in the shared vehicle end.

[0046] In summary, the display content sharing method provided by the embodiments of the present application reduces the occupation of cloud resources by the shared content when sharing display content, by converting the display content resources into a resource encoding configuration set through encoding standardization for uploading. The shared vehicle end only needs to input a request short code to reproduce the display content of the shared vehicle end. Using a unique short code instead of a display content file for display content sharing changes the display content sharing from file transmission to short code interaction, reduces the consumption of system resources in the display content sharing process, simplifies the operation of display content sharing and reproduction, and reduces the data transmission amount by using a short code sharing mechanism, shortens the data transmission time, improves the sharing efficiency, and improves the user's use experience.

[0047] In some embodiments, as shown in Figure 2a determining a unique short code according to the resource encoding configuration set includes: Step 201: verifying the validity of the resource encoding configuration set to obtain a verification result.

[0048] In specific implementation, the process of generating a short code is as shown in Figure 2b After receiving the resource encoding configuration set, it is first necessary to check whether the resource encoding configuration set is valid. The validity of the resource encoding configuration set is verified to avoid invalid display content sharing.

[0049] If the resource encoding configuration set is invalid, the process enters an error handling step, and the invalid verification result is fed back to the sharing vehicle end to prompt the sharing vehicle end (voice or display text) to prompt "error, invalid configuration" to prompt the user to update the resource encoding configuration set and re-share the resource encoding configuration set.

[0050] If the resource encoding configuration set is valid, a unique short code is generated according to the resource encoding configuration set, the file transfer is converted to short code interaction, the resource transmission amount of the subject sharing process is reduced, and efficient display content sharing is realized.

[0051] Step 202: In response to the verification result that the resource encoding configuration set is valid, a candidate short code is determined according to the resource encoding configuration set.

[0052] In specific implementation, if the resource encoding configuration set is valid, the resource encoding configuration set needs to be encoded to generate a candidate short code, and the generation of the candidate short code is shown in the following embodiment.

[0053] In some embodiments, determining the candidate short code according to the resource encoding configuration set comprises: performing hash calculation on the resource encoding configuration set to obtain a hash value; cutting the hash value according to a preset default cutting position to obtain a cutting byte, and converting the cutting byte into integer data; encoding the integer data to obtain the candidate short code.

[0054] In specific implementation, if the resource encoding configuration set is valid, the hash value is calculated based on the serialized resource encoding configuration set (in the sequence data) to generate a hash value corresponding to the resource encoding configuration set. At least one byte is cut from the hash value according to the cutting position, to obtain a cutting byte, and the cutting byte is converted into an integer to obtain integer data. The integer data is converted into a Base62 encoded string by using Base62 encoding, and the generation of the candidate short code is completed.

[0055] After the candidate short code is generated, in order to avoid that different custom display contents correspond to one short code, the uniqueness of the short code needs to be determined, so the candidate short code also needs to be verified for uniqueness.

[0056] Step 203: Determining a unique short code according to the sharing database and the candidate short code.

[0057] In specific implementation, when checking the uniqueness of the candidate short code, it is necessary to check whether there is a conflict short code same as the candidate short code in the sharing database. If there is a conflict short code same as the candidate short code, it means that other shared display contents have used the short code. In order to avoid the conflict of the one-to-one mapping relationship between the short code and the resource encoding configuration set, the process of verifying the uniqueness of the candidate short code is shown in the following embodiment.

[0058] In some embodiments, determining the unique short code according to the shared database and the candidate short code comprises: determining the candidate short code as the unique short code in response to the shared database not containing a conflict short code identical to the candidate short code; determining a conflict number in response to the shared database containing a conflict short code identical to the candidate short code; adjusting a default truncation position to obtain a new truncation position and determining a new candidate short code according to the new truncation position in response to the conflict number being less than or equal to a preset number threshold; determining the new candidate short code as the unique short code in response to the shared database not containing a conflict short code identical to the new candidate short code.

[0059] In implementation, it is determined through traversing the shared database whether the shared database contains a conflict short code identical to the candidate short code. If the shared database does not contain a conflict short code identical to the candidate short code, it indicates that the candidate short code is unique, and the candidate short code is directly determined as the unique short code.

[0060] If there is a conflict short code, it indicates that other resource encoding configuration sets have occupied the short code. In order to guarantee the one-to-one mapping relationship between the resource encoding configuration sets, the candidate short code of the resource encoding configuration set uploaded this time needs to be recalculated. Before recalculation, the conflict number of the candidate short code of the resource encoding configuration set needs to be further determined. If the conflict number is less than or equal to a preset number threshold, it may be an accidental problem caused by the hash value truncation position.

[0061] At this time, the conflict number is counted and updated once (for example, conflict number = conflict number + 1) and the default truncation position is adjusted to obtain a new truncation position. A new truncation byte is determined according to the new truncation position, the new truncation byte is converted into a new integer data, the new integer data is encoded using Base62 to obtain a new candidate short code, and the new candidate short code is verified for uniqueness. When the new candidate short code passes the uniqueness verification (the shared database does not contain a conflict short code identical to the new candidate short code), the new candidate short code is determined as the unique short code. When the new candidate short code does not pass the uniqueness verification (the shared database contains a conflict short code identical to the new candidate short code), the truncation position is adjusted again to calculate the candidate short code until the shared database does not contain a conflict short code identical to the new candidate short code or the conflict number is greater than the number threshold to stop recalculating the candidate short code.

[0062] If the number of conflicts is greater than the number threshold, the short code conflict caused by chance in the interception position selection can be ruled out, and there can be a calculation error or other users illegally upload display content of other users with the same display content. The voice or text display prompt of "error: unable to generate a unique short code" is fed back to the shared vehicle end.

[0063] In some embodiments, as shown in Figure 3a and Figure 3b , the validity of the request short code is verified according to the sharing database, including: Step 301: In response to the existence of the same unique short code as the request short code in the sharing database, it is determined that the request short code is valid.

[0064] In specific implementation, if the same unique short code as the request short code exists in the sharing database, it indicates that the request short code is a correct short code, which is a legally shared short code, and there exists a resource code configuration set corresponding to the request short code. It is determined that the request short code is valid.

[0065] Further, in the sharing database, there is a one-to-one mapping relationship between the short code and the resource code configuration set. In order to avoid data damage or loss during storage, after it is determined that the same short code as the request short code exists, it is further determined whether the corresponding mapping relationship exists. If the corresponding mapping relationship exists, it indicates that the data stored in the sharing database has not been damaged or lost, and the resource code configuration set corresponding to the request short code can be determined. At this time, it is determined that the request short code is valid. If the mapping relationship does not exist, it is determined that the request short code is invalid, and the sharing vehicle end is prompted to re-upload the resource code configuration set.

[0066] Step 302: In response to the absence of the same unique short code as the request short code in the sharing database, it is determined that the request short code is invalid.

[0067] In specific implementation, if the same unique short code as the request short code does not exist in the sharing database, it indicates that the request short code is an incorrect short code, and there is no resource code configuration set corresponding to the request short code. It is determined that the request short code is invalid, and the voice or question display prompt of "error: short code does not exist, please re-enter" is fed back to the shared vehicle end.

[0068] In some embodiments, as shown in Figure 4 , the display style diagram corresponding to the request short code is issued to the shared vehicle end, including: Step 401: Determine the shared resource code configuration set uniquely corresponding to the request short code in the sharing database.

[0069] In specific implementation, in the shared database, since there is a one-to-one mapping relationship between the short code and the resource code configuration set, after a valid request short code is transmitted on the shared vehicle side, the shared resource code configuration set corresponding to the request short code is determined according to the one-to-one mapping relationship between the short code and the resource code configuration set.

[0070] Step 402: Extract the display style diagram in the shared resource code configuration set, and issue the display style diagram to the shared vehicle side.

[0071] In specific implementation, the resource code configuration set includes the display style diagram and the sequence data, the sequence data is used to calculate the short code, and the display style diagram is used to provide a preview diagram for the shared vehicle side, so that the shared vehicle side can know the display content to be reproduced, and the shared vehicle side can know the style of the display content before reproducing the display content, so as to ensure that the shared vehicle side can reproduce the display content meeting the user demand and improve the user experience.

[0072] In some embodiments, as shown in Figure 5a a display content sharing method applied to a sharing vehicle side, the method comprises: Step 501: Determine the original resource associated with the display content, and classify and abstract the original resource to obtain a standardized resource library.

[0073] In specific implementation, since the display content resources of different systems and different vehicles can be different, but the attributes of different display content resources can be the same, the display content effect presented is close to the same or even completely the same when the attributes of different display content resources are the same, so it is necessary to classify and abstract the original resource of the sharing vehicle side, abstract the attributes of each type of resource, change the display content sharing process from file transmission to short code interaction related to the attributes, reduce the resource transmission amount, reduce the dependence on network resources, and reduce the system resource consumption compared with the traditional scheme. The user only needs to input the short code to reproduce the display content of others, the operation steps are simple, and the display content sharing efficiency is improved. The process of classifying and abstracting the original resource is as shown in the following embodiments.

[0074] In some embodiments, as shown in Figure 5b classifying and abstracting the original resource to obtain a standardized resource library, comprising: classifying the original resource according to the display content composition to obtain a plurality of single resources; abstracting the core attributes of each single resource to obtain attribute data, converting the attribute data into a unified standard format to obtain sequence data; generating a unique identification code based on the sequence data, integrating the unique identification code and the sequence data to obtain the standardized resource library.

[0075] In implementation, the process of standardizing the resource code of the original resource is as follows: 1. Classify the original resources constituting the display content. The original resources mainly include five single-class resources, namely, icon class, color class, layout class, font class, and animation class. The icon class resource is mainly used to define the interface elements (such as buttons, menu items) of the display content, and its attributes are concentrated in visual presentation and state management. The color class resource is used to define the color collocation of the display content, and supports display content and dynamic switching. The layout class resource is used to define the interface structure of the display content, and its attributes are concentrated in control arrangement and positioning control. The font class resource is used to define the text style of the display content. The animation class resource is used to define the dynamic effect of the display content.

[0076] 2. Abstract the attributes of the classified single-class resources. For each single-class resource, extract its core attributes.

[0077] For the icon class resource, abstract the attributes of size, color, shape, icon identification code, display mode, and selectability. The size determines the display size of the icon in the display content (for example, 10x15), the color determines the display color of the icon in the display content (for example, gray-scale display), the shape determines the display shape of the icon in the display content (for example, rectangle), the icon identification code is used to specify the corresponding icon, the display mode is used to determine the display mode of the icon in the display content (for example, gradient display), and the selectability determines whether the icon in the display content can be selected.

[0078] For the color class resource, abstract the attributes of color value and transparency. The color value determines the specific display color, and the transparency determines the transparency degree of the color display.

[0079] For the layout class resource, abstract the attributes of size, position, and layout type. The layout type includes elastic layout, grid layout, and the like. The size determines the size of the layout, and the position determines the display position of different resources.

[0080] For the font class resource, abstract the attributes of font type, font size, and font style. The font type determines the font used by the text of the display content, such as KaiTi, SongTi, and the like. The font size determines the display size of the text of the display content, such as four, small four, and the like. The font style determines the display style of the text of the display content, such as bold display, italic display, and underline display.

[0081] For animation resources, attributes such as playing time, definition, resolution, frame rate, etc. are abstracted. The playing time determines the time required for the animation resource to complete a display, for example, 2 seconds. The definition determines the clarity of the animation resource, and the higher the clarity, the better the display effect. The resolution refers to the number of pixels of a single frame image (for example, 1920x1080), and the higher the value, the clearer the picture. The resolution determines the picture clarity and detail performance of the animation resource. The frame rate is the number of frames per second (such as 24fps) of the animation resource, which determines the smoothness of the animation resource together with the resolution.

[0082] 3. The attribute data after attribute extraction is serialized. The abstracted attribute data is converted into a string of uniform format and consistent length, which is the resource code corresponding to the attribute, ensuring that different resources can generate the same serialization result as long as the attribute combination is the same. Through serialization, the attribute data is standardized. Different vehicles and different systems can combine different single-class resource attributes based on serialized data. By using single-class resources with the same attributes but different resources, display content reproduction is achieved, and compatibility of display content resources between different vehicle models and different systems is achieved.

[0083] 4. Generate a unique ID. Based on the serialized sequence data, a unique identifier is generated as the unique search identifier for the sequence data.

[0084] 5. Establish a standardized resource library. The serialized sequence resource data and unique ID are stored in the local resource library, completing resource storage and management.

[0085] The vehicle end uses the standardized resource library to store standardized resources locally, supports the real-time needs of the system, and reduces cloud resource occupation through coding standardization.

[0086] Step 502: In response to receiving a user's sharing request for custom display content, determine the display style diagram corresponding to the custom display content, and determine the custom resources used by the custom display content.

[0087] In specific implementation, the user designs the display content through his own operation on the sharing vehicle end to obtain the custom display content. In order to facilitate the shared vehicle end to understand the style after display content reproduction, the display style diagram corresponding to the custom display content is determined on the sharing vehicle end, and the display style diagram is used as a preview diagram to provide a certain display content reproduction preview for the shared vehicle end, facilitating the selection of the shared vehicle end when reproducing the display content. At the same time, the custom resources used by the custom display content are determined to provide a basis for sharing the custom display content.

[0088] Step 503: determining a plurality of resource codes corresponding to the custom resources in the standardized resource library, integrating the plurality of resource codes and the display style diagram to obtain a resource code configuration set, and sharing the resource code configuration set to the cloud.

[0089] In specific implementation, after determining the custom resources used by the custom display content in the standardized resource library, the resource code corresponding to the attribute of each custom resource is determined, all resource codes and the display style diagram of the custom display content are integrated to obtain a resource code configuration set, and when the user agrees to share the custom display content, the resource code configuration set is uploaded to the cloud to realize sharing of the display content resource.

[0090] In some embodiments, as shown in Figure 6a A display content sharing method applied to a shared vehicle end, the method comprising: Step 601: sending a request short code to the cloud according to user demand, and receiving a display style diagram corresponding to the request short code sent by the cloud.

[0091] In specific implementation, the process of the shared vehicle end requesting display content is as shown in Figure 6b The user demand is a request short code input by the user of the shared vehicle end, and the request short code corresponds to the display content that the user wants to reproduce according to his own preference. After the user inputs the request short code, the shared vehicle end sends the request short code to the cloud. The cloud first sends the display style diagram to the shared vehicle end to provide the user with a preview of the display content according to the display style diagram.

[0092] Step 602: displaying the display content style diagram and a preset selection pop-up window.

[0093] The selection pop-up window includes a selection prompt text, a confirmation display control and a cancel display control.

[0094] In specific implementation, after receiving the display style diagram sent by the cloud, the shared vehicle end displays the display content style diagram through the display device, and simultaneously displays the corresponding selection pop-up window. The display content style diagram is used to provide the user with a preview of the display content, and the selection pop-up window is used to determine whether the user wants to reproduce the display content. The selection prompt text in the selection pop-up window can be "whether to reproduce the display content". After previewing the display style diagram, if the user determines that the display content is the display content that needs to be reproduced, the user clicks the confirmation display control in the selection pop-up window to reproduce the display content. If the user does not want to reproduce the display content, the user clicks the cancel display control in the selection pop-up window to interrupt the display content reproduction process.

[0095] Step 603: sending a confirmation instruction to the cloud for the first touch operation of the confirmation display control, and receiving the shared resource code configuration set corresponding to the request short code sent by the cloud.

[0096] In particular implementation, when the user performs the first exit operation on the confirmation display control, it indicates that the user needs to reproduce the display content corresponding to the request short code. Therefore, a confirmation instruction is sent to the cloud. After the cloud receives the confirmation instruction, the shared resource code configuration set corresponding to the request short code is sent to the shared vehicle end.

[0097] Step 604: restoring the resource code in the shared resource code configuration set to a display content resource, and generating display content according to the display content resource.

[0098] In particular implementation, the process of reproducing the display content by the shared vehicle end is as shown in Figure 6c The shared resource code configuration set returned from the cloud is received, the code is converted back to specific resource attributes, the complete display content resource is generated according to the parsed resource attributes, the generated display content resource is applied to the QNX system, the reproduction of the display content is realized, and the sharing of the display content is completed.

[0099] It should be noted that the method of the embodiments of the present application can be executed by a single device, such as a computer or a server. The method of the embodiments of the present application can also be applied to a distributed scenario, and can be completed by multiple devices cooperating with each other. In this distributed scenario, one of the multiple devices can only execute one or more steps in the method of the embodiments of the present application, and the multiple devices can interact with each other to complete the method.

[0100] It should be noted that some embodiments of the present application have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described above and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In some embodiments, multi-task processing and parallel processing can be possible or advantageous.

[0101] Based on the same inventive concept, the present application also provides a display content sharing system corresponding to any of the above-mentioned embodiment methods, as shown in Figure 7 The display content sharing system includes a cloud, a shared vehicle end, and a shared vehicle end. The cloud 10 is configured to: obtain a resource code configuration set corresponding to the custom display content uploaded by the sharing vehicle end, determine a unique short code according to the resource code configuration set, and store the unique short code and the resource code configuration set to a shared database; in response to receiving a request short code sent by the shared vehicle end, verify the validity of the request short code according to the shared database; in response to the request short code being valid, issue a display style diagram corresponding to the request short code to the shared vehicle end; and according to the confirmation instruction for the display style diagram fed back by the shared vehicle end, send the shared resource code configuration set corresponding to the request short code in the shared database to the shared vehicle end. The sharing vehicle end 20 is configured to: determine an original resource associated with the display content, classify and abstract the original resource to obtain a standardized resource library; in response to receiving a sharing request for custom display content from a user, determine a display style diagram corresponding to the custom display content and determine custom resources used by the custom display content; determine a plurality of resource codes corresponding to the custom resources in the standardized resource library, integrate the plurality of resource codes and the display style diagram to obtain a resource code configuration set, and share the resource code configuration set to the cloud; The shared vehicle end 30 is configured to: send a request short code to the cloud according to user demand, and receive a display style diagram corresponding to the request short code sent by the cloud; display the content style diagram and a preset selection popup window; wherein the selection popup window includes a selection prompt text, a confirmation display control and a cancel display control; in response to a first touch operation on the confirmation display control, send a confirmation instruction to the cloud, and receive a shared resource code configuration set corresponding to the request short code sent by the cloud; restore the resource code in the shared resource code configuration set to a display content resource, and generate the display content according to the display content resource.

[0102] In specific implementation, the sharing vehicle end and the shared vehicle end both include an Android system and an instrument QNX system, and a complete sharing process timing architecture of custom display content is shown in Figure 8 as an example of the custom display content being a custom theme.

[0103] The user of the sharing vehicle end builds a custom theme through the instrument QNX system, obtains the custom theme, and then the instrument QNX system sends a resource code configuration set corresponding to the custom theme to the cloud end, and the sharing vehicle end realizes sharing of the custom theme. The cloud end receives the resource code configuration set, generates a unique short code according to the resource code configuration set, and stores the unique short code and the resource code configuration set in a one-to-one mapping relationship in a shared database, and shares the generated short code on an Android end (which can be a central control display screen or a mobile terminal). After the short code is shared to the shared vehicle end, if the short code is valid, the short code is requested to be synchronized to the instrument QNX system, and the instrument QNX system receives the request short code, uploads the request short code to the cloud end, and when it is determined through a preview theme style diagram that the theme meets the expectation, the instrument QNX system requests the shared resource code configuration set from the cloud end. After receiving the request, the cloud end determines that there is a shared resource code configuration set corresponding to the request short code according to the mapping relationship, and returns the shared resource code configuration set to the instrument QNX system of the shared vehicle end, and the instrument QNX system generates and applies the theme according to the received shared resource code configuration set, and realizes the reproduction of the theme. If the short code input by the shared vehicle end is invalid, an error message is prompted, so that the user re-enters the correct short code.

[0104] The sharing system of the display theme has the following beneficial effects: The theme resources used to build the theme are stored in QNX locally, supporting the real-time requirements of the QNX system, reducing the cloud resource occupation through coding standardization, reducing the data transmission amount through the short code mechanism, and improving the analysis efficiency through the cloud mapping.

[0105] The theme sharing is changed from "file transmission" to "short code interaction", and the system resource consumption is lower than that of the traditional scheme. The user only needs to input a short code to reproduce the theme of others, and the operation steps are simple.

[0106] The problem of low theme sharing efficiency between users is solved, and the sharing time is shortened from minutes to seconds.

[0107] The individualization ecology of the QNX system is expanded, and the sharing and rapid retrieval of the custom theme configuration are supported.

[0108] Based on the same inventive concept, the present application also provides an electronic device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the program to realize the display content sharing method of any one of the embodiments.

[0109] Figure 9A more specific electronic device hardware structure schematic diagram provided by the embodiment is shown. The device can include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 for internal communication.

[0110] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, etc., for executing related programs to implement the technical solutions provided by the embodiments of the present specification.

[0111] The memory 1020 can be implemented by a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 can store an operating system and other application programs. When the technical solutions provided by the embodiments of the present specification are implemented by software or firmware, the related program codes are stored in the memory 1020 and called and executed by the processor 1010.

[0112] The input / output interface 1030 is used to connect input / output modules to realize information input and output. The input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. The input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.

[0113] The communication interface 1040 is used to connect a communication module (not shown in the figure) to realize the communication interaction between the device and other devices. The communication module can realize communication through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.).

[0114] The bus 1050 includes a channel for transmitting information between various components (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040) of the device.

[0115] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device can also only contain components necessary to implement the embodiments of the present application, and does not necessarily contain all the components shown in the figure.

[0116] The electronic device of the above embodiment is used to implement the sharing method of the display content corresponding to any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described here again.

[0117] Based on the same inventive concept, corresponding to any of the above embodiment methods, the present application also provides a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the sharing method of the display content as described in any of the above embodiments.

[0118] The computer readable medium of the present embodiment includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0119] The storage medium of the above embodiment stores computer instructions for causing the computer to perform the sharing method of the display content as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described here again.

[0120] Based on the same inventive concept, corresponding to any of the above embodiment methods, the present application also provides a vehicle including the electronic device of the above embodiment and performing the sharing method of the display content as described in any of the above embodiments through the electronic device of the above embodiment, and has the beneficial effects of the corresponding method embodiments, which are not described here again.

[0121] It can be understood that, before using the technical solutions of various embodiments in the present application, the user will be informed of the type, use range, use scenario, etc. of the personal information involved in a proper manner, and the authorization of the user will be obtained.

[0122] For example, in response to receiving the active request of the user, the user is sent prompt information to explicitly prompt the user that the operation requested to be performed will require obtaining and using the personal information of the user. Thus, the user can voluntarily choose whether to provide the personal information to the software or hardware such as an electronic device, an application program, a server or a storage medium, etc. performing the operation of the technical solutions of the present application according to the prompt information.

[0123] As an optional but non-limiting implementation manner, in response to accepting the active request of the user, the manner of sending the prompt information to the user may, for example, be a pop-up window manner, and the prompt information may, for example, be presented in the form of text in the pop-up window. In addition, the pop-up window may also carry selection controls for the user to select "agree" or "disagree" to provide the personal information to the electronic device.

[0124] It can be understood that the above notification and obtaining of the authorization of the user are only illustrative, and do not limit the implementation manners of the present application, and other manners meeting the relevant laws and regulations can also be applied to the implementation manners of the present application.

[0125] Those skilled in the art will understand that the discussion of any of the above embodiments is merely exemplary, and is not intended to suggest that the scope of the present application is limited to these examples; the above embodiments or technical features among different embodiments can also be combined, steps can be implemented in any order, and there are many other changes to the aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of brevity. Therefore, the true scope of the present application is defined only by the appended claims.

[0126] In addition, in order to simplify the description and discussion, and so as not to make the embodiments of the present application difficult to understand, the known power / ground connections of integrated circuit (IC) chips and other components can or can not be shown in the provided drawings. In addition, the devices can be shown in the form of block diagrams in order to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (i.e. these details should be fully within the understanding of those skilled in the art). Where specific details (e.g. circuits) are set forth in order to describe an illustrative embodiment of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be practiced without these specific details or with variations on these specific details. Therefore, these descriptions should be considered as illustrative rather than limiting.

[0127] While the present application has been described in connection with certain embodiments thereof, many modifications, substitutions, changes, and of forms will be apparent to those of ordinary skill in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) can use the embodiments discussed.

[0128] Embodiments of the present application are intended to embrace all such alterations, modifications, and variations that fall within the scope of the broadest possible interpretation of the appended claims. Accordingly, any and all such alterations, modifications, equivalents, improvements and the like are intended to be encompassed by the present application.

Claims

1. A sharing method of displaying content, characterized by, Applied to the cloud, the method comprises: Obtain the resource code configuration set corresponding to the custom display content uploaded on the shared vehicle end, determine a unique short code according to the resource code configuration set, and store the unique short code and the resource code configuration set to a shared database; In response to receiving a request short code sent by the shared vehicle end, verify the validity of the request short code according to the shared database; In response to the request short code being valid, issue a display style graph corresponding to the request short code to the shared vehicle end; According to the confirmation instruction of the display style graph fed back by the shared vehicle end, send the shared resource code configuration set corresponding to the request short code in the shared database to the shared vehicle end.

2. The method of claim 1, wherein, The unique short code is determined according to the resource code configuration set, comprising: validating the resource code configuration set to obtain a verification result; In response to the verification result being that the resource code configuration set is valid, determine a candidate short code according to the resource code configuration set; Determine the unique short code according to the shared database and the candidate short code.

3. The method of claim 2, wherein, The candidate short code is determined according to the resource code configuration set, comprising: Hash calculation is performed on the resource code configuration set to obtain a hash value; According to the preset default intercept position, the hash value is intercepted to obtain an intercepted byte, and the intercepted byte is converted into an integer data; Encode the integer data to obtain the candidate short code.

4. The method of claim 2, wherein, The unique short code is determined according to the shared database and the candidate short code, comprising: In response to the shared database not existing a conflict short code same as the candidate short code, the candidate short code is determined as the unique short code; In response to the shared database existing a conflict short code same as the candidate short code, determine the conflict times; In response to the conflict times being less than or equal to a preset number threshold, adjust the default intercept position to obtain a new intercept position, and determine a new candidate short code according to the new intercept position; In response to the shared database not existing a conflict short code same as the new candidate short code, the new candidate short code is determined as the unique short code.

5. The method of claim 1, wherein, The validity of the request short code is verified according to the shared database, comprising: In response to the shared database existing a unique short code same as the request short code, determine that the request short code is valid; In response to the shared database not existing a unique short code same as the request short code, determine that the request short code is invalid.

6. The method of claim 1, wherein, The display style graph corresponding to the request short code is issued to the shared vehicle end, comprising: Determine the shared resource code configuration set corresponding to the request short code uniquely in the shared database; Extract the display style graph in the shared resource code configuration set, and issue the display style graph to the shared vehicle end.

7. A sharing method of displaying content, characterized by, Applied to the shared vehicle end, the method comprises: Determine the original resource associated with the display content, classify and abstract the original resource to obtain a standardized resource library; In response to receiving a sharing request of the customized display content by the user, a display style diagram corresponding to the customized display content is determined, and a customized resource used by the customized display content is determined; A plurality of resource codes corresponding to the customized resource are determined in the standardized resource library, the plurality of resource codes and the display style diagram are integrated to obtain a resource code configuration set, and the resource code configuration set is shared to the cloud.

8. The method of claim 7, wherein, The classification and abstraction processing of the original resource to obtain the standardized resource library includes: The original resource is classified according to the display content composition to obtain a plurality of single-class resources; The core attributes of each single-class resource are abstracted to obtain attribute data, and the attribute data is converted into a unified standard format to obtain sequence data; A unique identification code is generated based on the sequence data, and the unique identification code and the sequence data are integrated to obtain the standardized resource library.

9. A sharing method of displaying content, characterized by, Applied to a shared vehicle end, the method includes: According to the user demand, a request short code is sent to the cloud, and a display style diagram corresponding to the request short code is received from the cloud; The display style diagram and a preset selection pop-up window are displayed; wherein the selection pop-up window includes a selection prompt text, a confirmation display control and a cancel display control; In response to a first touch operation of the confirmation display control, a confirmation instruction is sent to the cloud, and a shared resource code configuration set corresponding to the request short code is received from the cloud; The resource codes in the shared resource code configuration set are restored to display content resources, and display content is generated according to the display content resources.

10. A sharing system of displaying content, characterized by, The cloud, the shared vehicle end and the shared vehicle end include: The cloud is configured to: obtain a resource code configuration set corresponding to a customized display content uploaded by a shared vehicle end, determine a unique short code according to the resource code configuration set, and store the unique short code and the resource code configuration set to a shared database; in response to receiving a request short code sent by a shared vehicle end, verify the validity of the request short code according to the shared database; in response to the request short code being valid, a display style diagram corresponding to the request short code is sent to the shared vehicle end; according to the confirmation instruction of the shared vehicle end feedback to the display style diagram, the shared resource code configuration set corresponding to the request short code in the shared database is sent to the shared vehicle end; The shared vehicle end is configured to: determine an original resource associated with display content, and perform classification and abstraction processing on the original resource to obtain a standardized resource library; In response to receiving a sharing request of the customized display content by the user, a display style diagram corresponding to the customized display content is determined, and a customized resource used by the customized display content is determined; A plurality of resource codes corresponding to the customized resource are determined in the standardized resource library, the plurality of resource codes and the display style diagram are integrated to obtain a resource code configuration set, and the resource code configuration set is shared to the cloud. The shared vehicle end is configured to: send a request short code to the cloud end according to user demand, and receive a display style picture corresponding to the request short code sent by the cloud end; display the display style picture and a preset selection pop-up window; wherein the selection pop-up window comprises selection prompt text, a confirmation display control and a cancel display control; for a first touch operation of the confirmation display control, send a confirmation instruction to the cloud end, and receive a shared resource code configuration set corresponding to the request short code sent by the cloud end; restore a resource code in the shared resource code configuration set to display content resources, and generate display content according to the display content resources.

Images