A method and device for sharing information

Abstract

The purpose of the present application is to provide a method and device for sharing information, the method comprising: receiving a plurality of sharing information, the plurality of sharing information being sent by a plurality of first users, the sharing information sent by each of the plurality of first users comprising a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, the first native page being generated after native rendering of at least one first information stream in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address; classifying and aggregating the plurality of sharing information to generate a plurality of object information, and publishing the plurality of object information in the webpage native rendering application, each object information comprising at least one metadata representation information and a link address corresponding to each metadata representation information.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a technology for sharing information. Background Art

[0002] In the prior art, web pages are usually presented in the form of H5 (HTML5) or Native app. The H5 implementation has the advantages of being cross-platform, low development cost, available online at any time, and suitable for rapid iteration. However, since it needs to be rendered based on the browser kernel, the performance of this implementation is poor and there are security issues such as browser hijacking. The native application implementation is based on the native operating system of the user's device for rendering, with better performance and security, but higher development costs. Summary of the invention

[0003] One object of the present application is to provide a method and device for sharing information.

[0004] According to one aspect of the present application, a method for sharing information applied to a network device is provided, the method comprising:

[0005] Receive multiple sharing information, where the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, where the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address;

[0006] The multiple shared information are classified and aggregated to generate multiple object information, and the multiple object information is published in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information.

[0007] According to another aspect of the present application, a method for sharing information applied to a first user device is provided, the method comprising:

[0008] In response to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, generating sharing information corresponding to the sharing operation, wherein the first native page is generated after natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page;

[0009] The sharing information is sent to the network device.

[0010] According to another aspect of the present application, a method for sharing information applied to a second user device is provided, the method comprising:

[0011] In response to a browsing operation performed by a second user on target object information among a plurality of object information in a webpage native rendering application, wherein the plurality of object information is generated by a network device after classifying and aggregating a plurality of sharing information received from a plurality of first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information;

[0012] According to the target configuration file, obtaining at least one metadata from the HTML page corresponding to the link address;

[0013] The at least one metadata is presented on a second native page corresponding to the browsing operation according to the target configuration file.

[0014] According to one aspect of the present application, a network device for sharing information is provided, the device comprising:

[0015] A module, configured to receive a plurality of sharing information, wherein the plurality of sharing information is sent by a plurality of first users, wherein the sharing information sent by each of the plurality of first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, wherein the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address;

[0016] Module one and module two are used to classify and aggregate the multiple shared information, generate multiple object information, and publish the multiple object information in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information.

[0017] According to another aspect of the present application, a first user device for sharing information is provided, the device comprising:

[0018] Module 21, configured to generate sharing information corresponding to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, wherein the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page;

[0019] Module 22 is used to send the sharing information to the network device.

[0020] According to another aspect of the present application, a second user device for sharing information is provided, the device comprising:

[0021] A three-one module is used to respond to a browsing operation performed by a second user on target object information among a plurality of object information in a webpage native rendering application, wherein the plurality of object information is generated by a network device after classifying and aggregating a plurality of sharing information received from a plurality of first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information;

[0022] Module three-two is used to obtain at least one metadata from the HTML page corresponding to the link address according to the target configuration file;

[0023] The three-three module is used to present the at least one metadata on the second native page corresponding to the browsing operation according to the target configuration file.

[0024] According to one aspect of the present application, a device for sharing information is provided, wherein the device includes:

[0025] Processor; and

[0026] A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the following operations:

[0027] Receive multiple sharing information, where the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, where the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address;

[0028] The multiple shared information are classified and aggregated to generate multiple object information, and the multiple object information is published in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information.

[0029] According to another aspect of the present application, a device for sharing information is provided, wherein the device includes:

[0030] Processor; and

[0031] A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the following operations:

[0032] In response to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, generating sharing information corresponding to the sharing operation, wherein the first native page is generated after natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page;

[0033] The sharing information is sent to the network device.

[0034] According to another aspect of the present application, a device for sharing information is provided, wherein the device includes:

[0035] Processor; and

[0036] A memory arranged to store computer executable instructions which, when executed, cause the processor to perform the following operations:

[0037] In response to a browsing operation performed by a second user on target object information among a plurality of object information in a webpage native rendering application, wherein the plurality of object information is generated by a network device after classifying and aggregating a plurality of sharing information received from a plurality of first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information;

[0038] According to the target configuration file, obtaining at least one metadata from the HTML page corresponding to the link address;

[0039] The at least one metadata is presented on a second native page corresponding to the browsing operation according to the target configuration file.

[0040] According to one aspect of the present application, a computer readable medium storing instructions is provided, wherein when the instructions are executed, the system performs the following operations:

[0041] Receive multiple sharing information, where the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, where the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address;

[0042] The multiple shared information are classified and aggregated to generate multiple object information, and the multiple object information is published in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information.

[0043] According to one aspect of the present application, a computer readable medium storing instructions is provided, wherein when the instructions are executed, the system performs the following operations:

[0044] In response to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, generating sharing information corresponding to the sharing operation, wherein the first native page is generated after natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page;

[0045] The sharing information is sent to the network device.

[0046] According to one aspect of the present application, a computer readable medium storing instructions is provided, wherein when the instructions are executed, the system performs the following operations:

[0047] In response to a browsing operation performed by a second user on target object information among a plurality of object information in a webpage native rendering application, wherein the plurality of object information is generated by a network device after classifying and aggregating a plurality of sharing information received from a plurality of first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information;

[0048] According to the target configuration file, obtaining at least one metadata from the HTML page corresponding to the link address;

[0049] The at least one metadata is presented on a second native page corresponding to the browsing operation according to the target configuration file.

[0050] Compared with the prior art, the present application can classify and aggregate multiple sharing information sent by multiple first users, generate multiple object information and publish them in the web rendering native application for browsing by the second user, which can reduce the cost of generating object information. When the second user browses an object information in the web rendering native application, the metadata representation information in the object information and its corresponding link address can be used to obtain the corresponding metadata from the HTML page information corresponding to the link address and present it on the current page through native rendering, which can reduce the development cost of the object information browsing page. In addition, the server corresponding to the web rendering native application itself only needs to store the metadata representation information and its corresponding link address, but does not need to store the specific metadata itself, which can reduce the cost of the server and ensure that the metadata currently presented is always the latest each time the user browses an object information, without the need for the server to actively update the metadata, thereby reducing the maintenance cost of the object information. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0052] Figure 1 A flow chart of a method for sharing information applied to a network device according to an embodiment of the present application is shown;

[0053] Figure 2 A flow chart of a method for sharing information applied to a network device according to an embodiment of the present application is shown;

[0054] Figure 3A flow chart of a method for sharing information applied to a network device according to an embodiment of the present application is shown;

[0055] Figure 4 A flowchart of a system method for sharing information according to an embodiment of the present application is shown;

[0056] Figure 5 A diagram showing a network device structure for sharing information according to an embodiment of the present application;

[0057] Figure 6 A structural diagram of a first user device for sharing information according to an embodiment of the present application is shown;

[0058] Figure 7 A structural diagram of a second user device for sharing information according to an embodiment of the present application is shown;

[0059] Figure 8 An exemplary system is shown that can be used to implement the various embodiments described in this application.

[0060] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0061] The present application is described in further detail below in conjunction with the accompanying drawings.

[0062] In a typical configuration of the present application, the terminal, the device of the service network and the trusted party all include one or more processors (eg, a central processing unit (CPU)), an input / output interface, a network interface and a memory.

[0063] Memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash memory. Memory is an example of a computer-readable medium.

[0064] Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer readable instructions, data structures, modules of programs or other data. Examples of computer storage media include, but are not limited to, Phase-Change Memory (PCM), Programmable Random Access 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 technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0065] The devices referred to in this application include but are not limited to user devices, network devices, or devices formed by integrating user devices and network devices through a network. The user devices include but are not limited to any mobile electronic products that can interact with users (for example, interact with users through a touchpad), such as smart phones, tablet computers, etc. The mobile electronic products can use any operating system, such as Android operating system, iOS operating system, etc. Among them, the network device includes an electronic device that can automatically perform numerical calculations and information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic devices (Programmable Logic Device, PLD), field programmable gate arrays (Field Programmable Gate Array, FPGA), digital signal processors (Digital Signal Processor, DSP), embedded devices, etc. The network devices include but are not limited to computers, network hosts, single network servers, multiple network server sets or multiple servers. The cloud is composed of a large number of computers or network servers based on cloud computing (Cloud Computing), wherein cloud computing is a type of distributed computing, a virtual supercomputer composed of a group of loosely coupled computer sets. The network includes but is not limited to the Internet, a wide area network, a metropolitan area network, a local area network, a VPN network, a wireless self-organizing network (Ad Hoc network), etc. Preferably, the device may also be a program running on the user device, the network device, or a device formed by integrating the user device and the network device, the network device, the touch terminal, or the network device and the touch terminal through a network.

[0066] Of course, those skilled in the art should understand that the above-mentioned devices are only examples, and other existing or future devices that are applicable to the present application should also be included in the scope of protection of the present application and are included here by reference.

[0067] In the description of the present application, “plurality” means two or more, unless otherwise clearly and specifically defined.

[0068] Figure 1A flow chart of a method for sharing information applied to a network device according to an embodiment of the present application is shown, the method comprising steps S11 and S12. In step S11, the network device receives a plurality of sharing information, the plurality of sharing information being sent by a plurality of first users, wherein the sharing information sent by each of the plurality of first users comprises a link address of a first native page corresponding to a sharing operation initiated by the first user in a webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, the first native page being generated after native rendering of at least one first information stream in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address; in step S12, the network device classifies and aggregates the plurality of sharing information, generates a plurality of object information, and publishes the plurality of object information in the webpage native rendering application, wherein each of the plurality of object information comprises at least one metadata representation information and a link address corresponding to each metadata representation information.

[0069] In step S11, the network device receives a plurality of sharing information, wherein the plurality of sharing information is sent by a plurality of first users, wherein the sharing information sent by each of the plurality of first users includes the link address of the first native page corresponding to the sharing operation initiated by the first user in the webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, and the first native page is generated after native rendering of at least one first information stream in the HTML page corresponding to the link address according to the first configuration file corresponding to the link address. In some embodiments, the webpage native rendering application is used to render at least one information stream in the HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, the first configuration file includes template information and information stream parsing rule information, and the template information includes one or more native control description information, and the native control description information is used to describe the type and properties of the native control that needs to be rendered on the first native page, and according to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. In some embodiments, taking the Android system as an example, the native control can be a view preset by the user device system (for example, Button, TextView, RecyclerView, etc.), or a viewgroup preset by the user device system (the viewgroup includes one or more views or viewgroups, for example, LinearLayout, RelativeLayout, etc.), or a custom view or custom viewgroup. In some embodiments, one or more corresponding native controls are created according to one or more native control description information in the template information. For at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the link address of the first native page through the information flow parsing rule information and bind it to the corresponding native control. In some embodiments, the information flow parsing rule information may include one or more HTML tag path information, and the corresponding HTML tag can be obtained from the HTML page information according to the HTML tag path information, and the information flow in the HTML tag is used as at least one first information flow that needs to be bound to the corresponding native control. In some embodiments, one or more native controls in the template information are rendered on the first native page, wherein the rendering method is based on the native rendering of the user device operating system, rather than the rendering based on the browser kernel.In some embodiments, the first configuration file can be obtained from a server corresponding to the link address of the first native page, or the first configuration file can also be obtained from a server corresponding to the webpage native rendering application, or the first configuration file can also be obtained locally from the user device, or the link address can include the storage address of the first configuration file (for example, a third-party server address), and the first configuration file can be obtained according to the storage address of the first configuration file. In some embodiments, each first user performs a sharing operation on the first native page currently browsed in the webpage native rendering application, and sends sharing information including the link address of the first native page and metadata representation information corresponding to at least one metadata in the first native page to the network device. In some embodiments, the first native page is usually a detail page corresponding to one or more specific objects, and the detail page is used to describe the one or more specific objects. In some embodiments, the metadata is obtained from at least one first information stream presented on the first native page, wherein the metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. for describing a specific object in the first native page. In some embodiments, each sharing information includes the link address corresponding to the first native page and metadata representation information corresponding to at least one metadata obtained from at least one first information stream presented on the first native page. In some embodiments, one metadata corresponds to one sharing object, and multiple metadata in each sharing information may correspond to the same sharing object or to multiple different sharing objects, that is, each metadata representation information corresponds to one sharing object, and multiple metadata representation information may correspond to the same sharing object or to multiple different sharing objects. In some embodiments, the metadata representation information is used to represent the characteristic information or identification information of the metadata to which it corresponds, including but not limited to the object identification information of the sharing object corresponding to the metadata, the user identification information of the sharing user corresponding to the metadata, the metadata type information corresponding to the metadata, the metadata identification information corresponding to the metadata, and any other information used to represent the metadata.

[0070] In step S12, the network device classifies and aggregates the multiple sharing information to generate multiple object information, and publishes the multiple object information in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. In some embodiments, the multiple sharing information sent by multiple users is classified and aggregated to generate multiple object information, and each object information is used to describe a specific object. In some embodiments, multiple metadata representation information in multiple sharing information can be classified and aggregated according to the object identification information in the metadata representation information in each sharing information to generate at least one metadata set, wherein all metadata representation information in each metadata set corresponds to the same sharing object, and then for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, the object information corresponding to the metadata set is generated. In some embodiments, each object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, and the multiple object information is published in the web native rendering application. In some embodiments, one metadata representation information corresponds to one link address, and multiple different metadata representation information can correspond to the same link address or to multiple different link addresses. In some embodiments, when a user browses a piece of object information among multiple object information currently published in a web native rendering application, for each piece of metadata representation information in at least one metadata representation information in the object information, according to the link address corresponding to the metadata representation information, at least one corresponding metadata is obtained from the HTML page information corresponding to the link address, and the at least one metadata is rendered on the current page through native rendering.

[0071] The present application can classify and aggregate multiple sharing information sent by multiple first users, generate multiple object information and publish them in the web rendering native application for browsing by the second user, which can reduce the cost of generating object information. When the second user browses an object information in the web rendering native application, the metadata representation information in the object information and its corresponding link address can be used to obtain the corresponding metadata from the HTML page information corresponding to the link address and present it on the current page through native rendering, which can reduce the development cost of the object information browsing page. In addition, the server corresponding to the web rendering native application itself only needs to store the metadata representation information and its corresponding link address, but does not need to store the specific metadata itself, which can reduce the cost of the server and ensure that the metadata currently presented each time a user browses an object information is always the latest, without the need for the server to actively update the metadata, thereby reducing the maintenance cost of the object information.

[0072] In some embodiments, the metadata representation information includes but is not limited to:

[0073] 1) Object identification information of the sharing object corresponding to the at least one metadata

[0074] For example, a user performs a sharing operation on the details page of object T1. The metadata corresponding to the sharing operation includes "Introduction: XXX", "Title: YYY", and "Cover Image: ZZZ". The sharing object corresponding to these metadata is "Object T1". The metadata representation information may include object identification information of the sharing object, for example, the name information "T1" of the sharing object.

[0075] 2) User identification information of the sharing user corresponding to the at least one metadata

[0076] In some embodiments, the metadata representation information may include user identification information of the sharing user who performs the current sharing operation, for example, user name information, user ID information, etc.

[0077] 3) Metadata type information corresponding to the at least one metadata

[0078] For example, a user performs a sharing operation on the details page of object T1. The metadata corresponding to the sharing operation includes "Introduction: XXX", "Title: YYY", and "Cover Image: ZZZ". The metadata type information corresponding to these metadata are "Introduction", "Title", and "Cover Image", respectively. The metadata representation information may include these metadata type information.

[0079] 4) Metadata identification information of the at least one metadata

[0080] In some embodiments, the webpage native rendering application renders at least one first information flow in the HTML page corresponding to the link address of the first native page on the first native page by native rendering, and the metadata identification information may be the location information of the metadata in the at least one first information flow, and the corresponding metadata may be obtained from the at least one first information flow according to the location information. In some embodiments, the metadata identification information may also be the identification information of the information flow parsing rule information corresponding to the metadata in the first configuration file corresponding to the link address of the first native page in the first configuration file, and the corresponding information flow parsing rule may be obtained from the first configuration file according to the identification information, and the corresponding metadata may be obtained from the HTML page information corresponding to the link address according to the information flow parsing rule information.

[0081] 5) Any combination of the above metadata representation information

[0082] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0083] In some embodiments, the metadata representation information includes object identification information of a sharing object corresponding to the at least one metadata; wherein the classification and aggregation of the received multiple sharing information to generate multiple object information includes: classification and aggregation of multiple metadata representation information in the multiple sharing information according to the object identification information in the metadata representation information in each sharing information to generate at least one metadata set, wherein the sharing objects corresponding to all metadata representation information in each metadata set meet a predetermined similarity; for each metadata set, object information corresponding to the metadata set is generated according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address. In some embodiments, according to the sharing object corresponding to the object identification information in each metadata representation information, one or more metadata representation information corresponding to the same or similar sharing object are classified and aggregated in a metadata set, and each metadata set may have only one metadata representation information or multiple metadata representation information. In some embodiments. For two shared objects to meet the predetermined similarity, the two object identification information may be completely identical, or two different object identification information may correspond to the same shared object. For example, the two object identification information are "lol" and "League of Legends", and both of these object identification information correspond to the shared object "League of Legends". Alternatively, two different object identification information may correspond to two different shared objects, and the two shared objects meet the predetermined similarity. For example, the shared object corresponding to the object identification information "pineapple" is "pineapple", and the shared object corresponding to the object identification information "pineapple" is "pineapple". Since the two shared objects meet the predetermined similarity, two metadata sets may be generated, namely the metadata set "pineapple" and the metadata set "pineapple", and then the metadata representation information corresponding to the two object identification information may be simultaneously put into the metadata set "pineapple" and the metadata set "pineapple". In some embodiments, for each metadata set, the object information of the metadata set may include all metadata representation information in the metadata set, or may only include part of the metadata representation information in the metadata set. In addition, the object information also includes the link address corresponding to each metadata representation information in the object information. Different metadata representation information may correspond to the same link address, or may correspond to different link addresses.

[0084] In some embodiments, the metadata representation information further includes metadata type information corresponding to the at least one metadata; wherein, for each metadata set, generating object information corresponding to the metadata set according to at least one metadata representation information among all metadata representation information in the metadata set and its corresponding link address includes: for each metadata set, if multiple metadata representation information in the metadata set corresponds to the same metadata type information, determining at least one metadata representation information from the multiple metadata representation information, removing other metadata representation information from the multiple metadata representation information except the at least one metadata representation information, and generating object information corresponding to the metadata set according to the remaining at least one metadata representation information in the metadata set and its corresponding link address. In some embodiments, the metadata type information is used to indicate the type of each metadata, such as "introduction", "title", "cover image", etc. In some embodiments, for each metadata set, if multiple metadata representation information in the metadata set corresponds to the same metadata type information, determining at least one metadata representation information from the multiple metadata representation information, removing other metadata representation information from the multiple metadata representation information except the at least one metadata representation information from the metadata set. In some embodiments, for each metadata set, the above-mentioned removal operation may be performed only once, or multiple times, until there are no multiple metadata representation information corresponding to the same metadata type information in the metadata set. The object information corresponding to the metadata set may include all the remaining metadata representation information in the metadata set, or may only include part of the metadata representation information among all the remaining metadata representation information in the metadata set. In addition, the object information also includes the link address corresponding to each metadata representation information in the object information.

[0085] In some embodiments, each object information also includes weight information corresponding to each metadata representation information in the object information; wherein, the method further includes: for each object information, determining the weight information corresponding to each metadata representation information in the object information. In some embodiments, the object information also includes weight information corresponding to each metadata representation information in the object information. For each object information, it is necessary to determine the weight information corresponding to each metadata representation information in the object information. For example, the weight information corresponding to each metadata annotation information can be determined by the order of sharing time, or the weight information corresponding to each metadata representation information can also be determined by the user level of the sharing user or other user influencing factors. In some embodiments, since the page presentation space of the browsing page corresponding to each object information in the webpage native rendering application is limited, when the user enters the browsing page corresponding to the object information, the metadata with a larger weight information in at least one metadata corresponding to the object information will be presented first by default on the browsing page corresponding to the object information, and other metadata with smaller weight information will only be presented on the browsing page in response to the switching operation performed by the user on the browsing page.

[0086] In some embodiments, the method further includes: for each object information, generating a second configuration file corresponding to the object information, and publishing the second configuration file in the webpage native rendering application. In some embodiments, for each object information, the second configuration file corresponding to the object information includes template information and information flow parsing rule information, the template information includes one or more native control description information, one or more native controls corresponding to the one or more native control description information are created, and then according to the information flow parsing rule information, at least one corresponding metadata can be obtained from the HTML page information corresponding to at least one link address in the object information, and the at least one metadata is bound to at least one native control of the one or more native controls, and then according to the template information, the one or more native controls are rendered on the browsing page corresponding to the object information. In some embodiments, one or more default template information applicable to object information browsing pages can be preset in a web native rendering application. For each object information, a target default template information is determined from the one or more default template information as the template information corresponding to the object information. According to the metadata identification information in each metadata representation information in the object information and the first configuration file corresponding to the link address corresponding to each metadata representation information, the information flow parsing rule information corresponding to each metadata representation information can be obtained. Then, according to the template information corresponding to the object information and the information flow parsing rule information corresponding to each metadata representation information, a second configuration file corresponding to the object information can be generated. Subsequently, according to the information flow parsing rule information corresponding to each metadata representation information in the second configuration file, the metadata corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to the metadata representation information. In some embodiments, a second configuration file corresponding to the object information can also be generated based on the template information corresponding to the object information and the configuration file identification information of the first configuration file corresponding to the link address corresponding to each metadata representation information (for example, file name information, file storage server address information, file storage local path information, etc.). Subsequently, the first configuration file corresponding to the configuration file identification information can be obtained based on the configuration file identification information corresponding to each metadata representation information in the second configuration file, and then the metadata corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to the metadata representation information based on the information flow parsing rule information in the first configuration file and the metadata identification information in the metadata representation information.

[0087] In some embodiments, the metadata representation information includes metadata identification information of the at least one metadata; for each object information, generating a second configuration file corresponding to the object information, and publishing the second configuration file in the webpage native rendering application, includes: for each object information, according to the metadata identification information in each metadata representation information in the object information, and the first configuration file corresponding to the link address corresponding to each metadata representation information, generating the second configuration file corresponding to the object information. In some embodiments, for each object information, if the metadata identification information in the object information is the identification information of the information flow parsing rule information corresponding to the metadata in the first configuration file in the first configuration file, the information flow parsing rule information corresponding to each metadata representation information can be obtained, and then according to the template information corresponding to the object information and the information flow parsing rule information corresponding to each metadata representation information, the second configuration file corresponding to the object information can be generated. In some embodiments, for each object information, according to the first configuration file corresponding to the link address in the object information, at least one information flow presented on the first native page corresponding to the link address can be obtained from the HTML page information corresponding to the link address; if the metadata identification information in the object information is the location information of the metadata in at least one first information flow presented on the corresponding first native page, the information flow parsing rule information corresponding to each metadata representation information can be reversely deduced, and then the second configuration file corresponding to the object information can be generated according to the template information corresponding to the object information and the information flow parsing rule information corresponding to each metadata representation information.

[0088] Figure 2 A flow chart of a method for sharing information applied to a first user device according to an embodiment of the present application is shown, the method comprising steps S21 and S22. In step S21, the first user device generates sharing information corresponding to the sharing operation in response to a sharing operation initiated by the first user for a first native page in a webpage native rendering application, wherein the first native page is generated after native rendering of at least one first information stream in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information comprises the link address of the first native page and metadata representation information corresponding to at least one metadata in the first native page; in step S22, the first user device sends the sharing information to a network device.

[0089] In step S21, the first user device generates sharing information corresponding to the sharing operation in response to the first user initiating a sharing operation for the first native page in the webpage native rendering application, wherein the first native page is generated after native rendering of at least one first information flow in the HTML page corresponding to the first link address according to the first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page. In some embodiments, the webpage native rendering application is used to render at least one information flow in the HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, the first configuration file includes template information and information flow parsing rule information, and the template information includes one or more native control description information, and the native control description information is used to describe the type and attributes of the native control that needs to be rendered on the first native page. According to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. In some embodiments, according to the one or more native control description information in the template information, one or more corresponding native controls are created, and for at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the first link address through the information flow parsing rule information and bind it to the corresponding native control. In some embodiments, the information flow parsing rule information may include one or more HTML tag path information, and the corresponding HTML tag can be obtained from the HTML page information according to the HTML tag path information, and the information flow in the HTML tag is used as at least one first information flow that needs to be bound to the corresponding native control. In some embodiments, one or more native controls in the template information are rendered on the first native page by native rendering. In some embodiments, the first native page is usually a detail page corresponding to one or more specific objects, and the detail page is used to describe the one or more specific objects. In some embodiments, at least one metadata can be obtained from at least one first information flow presented on the first native page, wherein the metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. for describing a specific object in the first native page. In some embodiments, the metadata representation information includes but is not limited to any information used to represent the metadata, such as object identification information of the shared object corresponding to the metadata, user identification information of the sharing user corresponding to the metadata, metadata type information corresponding to the metadata, metadata identification information corresponding to the metadata, etc.

[0090] In step S22, the first user equipment sends the sharing information to the network equipment.

[0091] In some embodiments, the generating of the sharing information corresponding to the sharing operation includes: obtaining at least one metadata from the at least one first information stream; determining metadata representation information corresponding to the at least one metadata; and generating the sharing information corresponding to the sharing operation according to the metadata representation information and the first link address. In some embodiments, at least one metadata is obtained from at least one first information stream presented on the first native page, and the metadata is basic information such as title information, introduction information, cover image information, etc. of a specific object. For example, the metadata may be "Introduction: XXX", "Title: YYY", "Cover Image: ZZZ", etc. In some embodiments, the metadata representation information may include metadata type information corresponding to the metadata. For example, the metadata is "Introduction: XXX", and the metadata type information corresponding to the metadata is "Introduction". In some embodiments, the metadata representation information may also include object identification information of the sharing object corresponding to the metadata. For example, the first native page is the details page of object T1, and the metadata corresponding to the first native page includes "Title: YYY", and the sharing object corresponding to the metadata is object T1, then the name information "T1" of the object T1 may be used as the metadata type information corresponding to the metadata. In some embodiments, the metadata representation information may also be user identification information of the first user, such as user name information, user ID information, etc.

[0092] In some embodiments, the obtaining of at least one metadata from the at least one first information stream includes step S23 (not shown) and step S24 (not shown). In step S23, the network device determines one or more sharing objects corresponding to the first native page; in step S24, the network device obtains at least one metadata corresponding to the one or more sharing objects from the at least first information stream. In some embodiments, if the first native page is a detail page corresponding to one or more specific objects, and the detail page is used to describe the one or more specific objects, the specific object can be used as the sharing object corresponding to the first native page. In some embodiments, the sharing object corresponding to the first native page can be determined by semantically analyzing at least one first information stream presented on the first native page. In some embodiments, the corresponding page description information can also be obtained from the HTML page information corresponding to the first link address, and then the sharing object corresponding to the first native page is determined according to the page description information. In some embodiments, after determining the one or more sharing objects corresponding to the first native page, basic information such as title information, introduction information, cover image information, etc. used to describe the one or more sharing objects is obtained from at least one information stream presented on the first native page, and the basic information is determined as at least one metadata corresponding to the one or more sharing objects.

[0093] In some embodiments, the step S23 includes: determining one or more sharing objects corresponding to the first native page by performing semantic analysis on the at least first information stream. In some embodiments, by performing semantic analysis on at least one first information stream presented on the first native page, one or more specific objects described in the first native page can be obtained, and then the one or more specific objects are determined as the sharing objects corresponding to the first native page, or, according to the proportion of the description information corresponding to each specific object in at least one first information stream, or according to the importance of each specific object in the semantic content corresponding to at least one first information stream, at least one specific object can be determined from the one or more specific objects, and the at least one specific object can be determined as the sharing object corresponding to the first native page.

[0094] In some embodiments, the step S23 includes: obtaining page description information from the HTML page corresponding to the first link address; and determining one or more sharing objects corresponding to the first native page according to the page description information. In some embodiments, the Meta tag can be obtained from the HTML page information corresponding to the first link address, and then the page description information corresponding to the HTML page can be obtained from the Meta tag, for example, <meta name＝"Description"Content＝"页面描述信息"> In some embodiments, semantic recognition may be performed on the page description information to determine one or more specific objects described in the page description information as the sharing objects corresponding to the first native page. Alternatively, keyword extraction may be performed on the page description information to determine at least one keyword of the one or more extracted keywords whose corresponding word type is a specific object type as the sharing object corresponding to the first native page.

[0095] In some embodiments, the step S24 includes step S25 (not shown) and step S26 (not shown). In step S25, at least one sharing object is determined from the one or more sharing objects; in step S26, at least one metadata corresponding to the at least one sharing object is obtained from the at least first information stream. In some embodiments, it is necessary to determine at least one sharing object from the one or more sharing objects corresponding to the first native page, and then obtain basic information for describing the one or more sharing objects from at least one first information stream presented on the first native page, and determine the basic information as at least one metadata corresponding to the at least one sharing object.

[0096] In some embodiments, the step S25 includes: determining the weight information corresponding to each of the one or more sharing objects; and determining at least one sharing object that satisfies a predetermined weight condition from the one or more sharing objects according to the weight information corresponding to each sharing object. In some embodiments, the weight information corresponding to each sharing object can be determined according to the proportion of the description information corresponding to each sharing object, i.e., the metadata, in at least one first information stream presented on the first native page. In some embodiments, the weight information corresponding to each sharing object can be determined according to the importance of each sharing object in the semantic content corresponding to at least one first information stream. In some embodiments, according to the weight information corresponding to each sharing object, at least one sharing object that satisfies a predetermined weight condition is determined from one or more sharing objects corresponding to the first native page, wherein the predetermined weight condition can be that the weight information of the at least one sharing object is greater than or equal to a predetermined weight threshold, or it can also be that the at least one sharing object is a predetermined number of sharing objects with the largest corresponding weight information among the one or more sharing objects.

[0097] In some embodiments, step S25 includes: presenting the one or more sharing objects to the first user; obtaining at least one sharing object selected by the first user from the one or more sharing objects. In some embodiments, the one or more sharing objects corresponding to the first native page can be presented on the first native page, and the first user can select at least one sharing object from the one or more sharing objects. In some embodiments, at least one sharing object among the one or more sharing objects that meets a predetermined weight condition can also be presented on the first native page in a special presentation manner (e.g., highlighting). In some embodiments, the weight information of each sharing object can also be displayed directly in the vicinity of the first native page.

[0098] In some embodiments, the operation object of the sharing operation is the second information stream selected by the first user in the first native page; wherein, the step S23 includes: obtaining at least one second sharing object corresponding to the second information stream by semantically analyzing the second information stream; determining the at least one second sharing object as one or more sharing objects corresponding to the first native page. In some embodiments, the way in which the first user selects the second information stream in the first native page includes but is not limited to any form of interactive operation such as clicking, sliding, and long pressing. In some embodiments, the first user can directly select the page content on the first native page and determine the selected page content as the second information stream. For example, the user selects the text content "XXXXXXXXXXX" on the first native page through a sliding operation, and uses the text content as the second information stream. In some embodiments, the user can also select a page area on the first native page, and determine the page content located in the page area as the second information stream. For example, the user selects a rectangular page area Area1 on the first native page through a sliding operation, and uses the text content "YYYYYYYYYY" located in the rectangular page area Area1 as the second information stream. In some embodiments, by performing semantic analysis on the second information stream, at least one second sharing object described in the second information stream can be obtained, and then the at least one second sharing object can be determined as the sharing object corresponding to the first native page, or some of the at least one second sharing object can also be determined as the sharing objects corresponding to the first native page.

[0099] In some embodiments, the metadata representation information includes but is not limited to:

[0100] 1) Object identification information of the sharing object corresponding to the at least one metadata

[0101] 2) User identification information of the first user

[0102] 3) Metadata type information corresponding to the at least one metadata

[0103] 4) Metadata identification information of the at least one metadata

[0104] 5) Any combination of the above metadata representation information

[0105] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0106] In some embodiments, the metadata characterization information includes metadata identification information of the at least one metadata; wherein the method further comprises: obtaining metadata identification information of the at least one metadata. In some embodiments, the metadata identification information may be obtained by determining location information of the at least one metadata in at least one first information stream, and determining the location information as metadata identification information of the at least one metadata. In some embodiments, the metadata identification information may also be obtained by determining information stream parsing rule information corresponding to the at least one metadata in the first configuration file, and determining identification information of the information stream parsing rule information in the first configuration file as metadata identification information of the at least one metadata.

[0107] In some embodiments, the obtaining of metadata identification information of the at least one metadata includes at least one of the following: determining the location information of the at least one metadata in at least one first information flow, and determining the location information as the metadata identification information of the at least one metadata; determining the information flow parsing rule information corresponding to the at least one metadata in the first configuration file, and determining the identification information of the information flow parsing rule information in the first configuration file as the metadata identification information of the at least one metadata. In some embodiments, if the metadata identification information is the location information of each metadata in at least one first information flow in the HTML page corresponding to the link address corresponding to the metadata, then for each metadata representation information, at least one first information flow can be obtained from the HTML page corresponding to the link address according to the first configuration file corresponding to the link address corresponding to the metadata representation information, and at least one metadata can be obtained from the at least one first information flow according to the location information in the metadata representation information. In some embodiments, if the metadata identification information is the identification information of the information flow parsing rule information corresponding to each metadata in the first configuration file corresponding to the link address corresponding to the metadata, for each metadata representation information, the information flow parsing rule information corresponding to the link address can be subsequently obtained from the first configuration file corresponding to the link address corresponding to the metadata representation information according to the identification information in the metadata representation information, and at least one metadata can be obtained from the HTML page corresponding to the link address according to the information flow parsing rule information.

[0108] Figure 3A flow chart of a method for sharing information applied to a second user device according to an embodiment of the present application is shown, the method comprising steps S31, S32 and S33. In step S31, the second user device responds to a browsing operation performed by the second user on target object information among multiple object information in a webpage native rendering application, wherein the multiple object information is generated by a network device after classifying and aggregating multiple sharing information received from multiple first users, and the target object information comprises at least one metadata representation information and a link address corresponding to each metadata representation information; in step S32, the second user device obtains at least one metadata from an HTML page corresponding to the link address according to a target configuration file; in step S33, the second user device presents the at least one metadata on a second native page corresponding to the browsing operation according to the target configuration file.

[0109] In step S31, the second user device responds to a browsing operation performed by the second user on target object information among multiple object information in a web native rendering application, wherein the multiple object information is generated by a network device after classifying and aggregating multiple sharing information received from multiple first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. In some embodiments, the web native rendering application is used to render at least one information stream in an HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, when the second user performs a browsing operation on the target object information among the multiple object information currently published in the web native rendering application, a details page corresponding to the target object information, i.e., a second native page, will be presented on the web native rendering application. In some embodiments, the multiple object information is generated by the network device after classifying and aggregating at least one sharing information sent by multiple first users respectively. Each sharing information is generated in response to a sharing operation initiated by the first user for the first native page in the web native rendering application. The first native page is generated after native rendering of at least one first information flow in the HTML page corresponding to the link address of the first native page according to the first configuration file corresponding to the link address of the first native page. The first configuration file includes template information and information flow parsing rule information. The template information includes one or more native control description information. The native control description information is used to describe the type and properties of the native control that needs to be rendered on the first native page. According to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. According to the one or more native control description information in the template information, one or more corresponding native controls are created. For at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the link address of the first native page through the information flow parsing rule information and bind it to the corresponding native control, and render the one or more native controls on the first native page by native rendering. In some embodiments, the first native page is usually a details page corresponding to one or more specific objects, which is used to describe the one or more specific objects. The metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. used to describe a specific object in the first native page. The metadata representation information includes but is not limited to object identification information of the shared object corresponding to the metadata, user identification information of the sharing user corresponding to the metadata, metadata type information corresponding to the metadata, metadata identification information corresponding to the metadata, and any other information used to represent the metadata.In some embodiments, each object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. The link address corresponding to each metadata representation information is the link address of the first native page corresponding to the metadata representation information. Different metadata representation information can correspond to the same link address or to different link addresses.

[0110] In step S32, the second user device obtains at least one metadata from the HTML page corresponding to the link address according to the target configuration file. In some embodiments, the target configuration file may be a second configuration file corresponding to the target object information, or may be a first configuration file corresponding to the link address corresponding to each metadata representation information. In some embodiments, if the target configuration file is the second configuration file corresponding to the target object information, the second configuration file includes information flow parsing rule information corresponding to each metadata representation information in the target object information, and according to the information flow parsing rule information, the metadata corresponding to each metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to each metadata representation information. In some embodiments, if the target configuration file is the first configuration file corresponding to the link address corresponding to each metadata representation information, then for each metadata representation information, at least one metadata can be obtained from the HTML page corresponding to the link address according to the information flow parsing rule information in the first configuration file corresponding to the link address corresponding to the metadata representation information.

[0111] In step S33, the second user device presents the at least one metadata on the second native page corresponding to the browsing operation according to the target configuration file. In some embodiments, if the target configuration file is the second configuration file corresponding to the target object information, the at least one metadata obtained is rendered on the second native page by native rendering according to the template information in the second configuration file. In some embodiments, if the target configuration file is the first configuration file corresponding to the link address corresponding to each metadata representation information, the metadata is rendered on the second native page by native rendering according to the template information in the first configuration file corresponding to each metadata in the at least one metadata obtained, that is, the rendering presentation mode of the metadata on the first native page is the same as the rendering presentation mode of the metadata on the second native page.

[0112] In some embodiments, the target configuration file is a second configuration file corresponding to the target object information. In some embodiments, the network device side will publish the second configuration file corresponding to each object information in the web native rendering application. In some embodiments, the network device will send each object information and the second configuration file corresponding to the object information to the second user device side, and the second user device has already obtained the second configuration file corresponding to the target object when the second user performs a browsing operation on the target object. In some embodiments, the second user device needs to request the network device side to obtain the second configuration file corresponding to the target object when the second user performs a browsing operation on the target object. In some embodiments, the second configuration file includes information flow parsing rule information corresponding to each metadata representation information, then according to the information flow parsing rule information corresponding to each metadata representation information in the second configuration file, the metadata corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to the metadata representation information. In some embodiments, the second configuration file includes configuration file identification information of the first configuration file corresponding to the link address corresponding to each metadata representation information (for example, file name information, file storage server address information, file storage local path information, etc.). Then, based on the configuration file identification information corresponding to each metadata representation information in the second configuration file, the first configuration file corresponding to the configuration file identification information can be obtained, and then, based on the information flow parsing rule information in the first configuration file and the metadata identification information in the metadata representation information, the metadata corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to the metadata representation information.

[0113] In some embodiments, the target configuration file is a first configuration file corresponding to the link address corresponding to each metadata representation information; wherein, step S32 includes step S321 (not shown). In step S321, for each metadata representation information, the second user device obtains at least one metadata from the HTML page corresponding to the link address according to the first configuration file corresponding to the link address corresponding to the metadata representation information. In some embodiments, for each metadata representation information, according to the information flow parsing rule information in the first configuration file corresponding to the link address corresponding to the metadata representation information, the metadata corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address.

[0114] In some embodiments, the metadata representation information includes but is not limited to:

[0115] 1) Object identification information of the shared object

[0116] 2) Sharing user's user identification information

[0117] 3) Metadata type information

[0118] 4) Metadata identification information

[0119] 5) Any combination of the above metadata representation information

[0120] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0121] In some embodiments, the metadata representation information includes metadata identification information; wherein, the step S321 includes step S322 (not shown). In step S322, for each metadata representation information, the second user device obtains at least one metadata from the HTML page corresponding to the link address according to the first configuration file corresponding to the link address corresponding to the metadata representation information and the metadata identification information in the metadata representation information. In some embodiments, if the metadata identification information is the position information of each metadata in at least one first information flow in the HTML page corresponding to the link address corresponding to the metadata, then for each metadata representation information, according to the first configuration file corresponding to the link address corresponding to the metadata representation information, at least one first information flow is obtained from the HTML page corresponding to the link address, and at least one metadata is obtained from the at least one first information flow according to the position information in the metadata representation information. In some embodiments, if the metadata identification information is the identification information of the information flow parsing rule information corresponding to each metadata in the first configuration file corresponding to the link address corresponding to the metadata, for each metadata representation information, according to the identification information in the metadata representation information, the information flow parsing rule information corresponding to the link address corresponding to the metadata representation information is obtained from the first configuration file corresponding to the link address corresponding to the metadata representation information, and at least one metadata is obtained from the HTML page corresponding to the link address according to the information flow parsing rule information.

[0122] In some embodiments, the metadata identification information is the location information of each metadata in at least one first information flow in the HTML page corresponding to the link address corresponding to the metadata; wherein, the step S322 includes: for each metadata representation information, according to the first configuration file corresponding to the link address corresponding to the metadata representation information, obtaining at least one first information flow from the HTML page corresponding to the link address, and obtaining at least one metadata from the at least one first information flow according to the location information in the metadata representation information. In some embodiments, for each metadata representation information, according to the information flow parsing rule information in the first configuration file corresponding to the link address corresponding to the metadata representation information, at least one first information flow originally presented on the first native page corresponding to the metadata representation information can be obtained from the HTML page information corresponding to the link address, and then at least one metadata can be obtained from the at least one first information flow according to the location information in the metadata representation information.

[0123] In some embodiments, the metadata identification information is identification information of the information flow parsing rule information corresponding to each metadata in the first configuration file corresponding to the link address corresponding to the metadata; wherein, the step S322 includes: for each metadata representation information, according to the identification information in the metadata representation information, obtaining the information flow parsing rule information corresponding to the link address from the first configuration file corresponding to the link address corresponding to the metadata representation information, and according to the information flow parsing rule information, obtaining at least one metadata from the HTML page corresponding to the link address.

[0124] In some embodiments, the target object information also includes weight information corresponding to each metadata representation information; wherein presenting the at least one metadata on the second native page corresponding to the browsing operation includes: determining the target metadata in the at least one metadata according to the weight information corresponding to each metadata; presenting the target metadata on the second native page corresponding to the browsing operation; in response to the switching operation performed by the second user on the second native page; determining the second target metadata after switching corresponding to the target metadata in the at least one metadata; switching the target metadata currently presented on the second native page to the second target metadata. In some embodiments, the target object information also includes weight information corresponding to each metadata representation information in the target object information, and the weight information corresponding to each metadata is the weight information corresponding to the metadata representation information corresponding to the metadata, and according to the weight information of each metadata, one or more target metadata that meet a predetermined weight threshold are determined from the obtained at least one metadata, or one or more target metadata with a predetermined number of the largest weight information are determined from the obtained at least one metadata. In some embodiments, due to the limited page presentation space of the second native page, only one or more target metadata in the at least one metadata will be presented on the second native page. In response to the switching operation (e.g., left-right sliding operation, up-down sliding operation, click operation, etc.) performed by the second user on the second native page for the one or more target metadata, one or more second target metadata are determined in the remaining metadata other than the one or more target metadata in the at least one metadata, and then the metadata currently presented on the second native page is switched from the one or more target metadata to the one or more second target metadata. In some embodiments, each switching operation will present one or more metadata different from the metadata presented previously, until the at least one metadata has been fully presented, at which time the one or more target metadata will be re-presented. For example, a tab bar is presented at the top or bottom of the second native page, and the tab bar includes multiple tabs. The obtained at least one metadata will be divided into the tab page corresponding to each tab for presentation. Only one tab among the multiple tabs is selected at a time. The second native page will present one or more metadata in the tab page corresponding to the currently selected tab. When entering the second native page in response to the browsing operation of the second user, the tab corresponding to the one or more target metadata determined in the at least one metadata is used as the default selected tab, and the tab page corresponding to the tab will be presented first by default.

[0125] In some embodiments, the target object information further includes weight information corresponding to each metadata representation information, and the metadata representation information includes metadata type information corresponding to the at least one metadata; wherein presenting the at least one metadata on the second native page corresponding to the browsing operation includes: for each metadata type information among the multiple metadata type information corresponding to the multiple metadata, according to the weight information corresponding to each metadata among the multiple metadata corresponding to the metadata type information, determining the target metadata corresponding to the metadata type information; for each metadata type information, presenting the target metadata corresponding to the metadata type information on the second native page corresponding to the browsing operation, in response to the switching operation performed by the second user on the second native page; determining the second target metadata corresponding to the target metadata after switching among the multiple metadata corresponding to the metadata type information; switching the target metadata currently presented on the second native page to the second target metadata. In some embodiments, for each metadata type information among the multiple metadata types corresponding to the multiple metadata, one or more target metadata corresponding to the metadata type information will be determined from the multiple metadata according to the weight information corresponding to each metadata among the multiple metadata corresponding to the metadata type information, and the one or more target metadata may be metadata that meets a predetermined weight threshold among the multiple metadata, or the one or more target metadata may also be a predetermined number of metadata with the largest weight information among the multiple metadata. In some embodiments, due to the limited page presentation space of the second native page, for each metadata type information, only one or more target metadata among the multiple metadata corresponding to the metadata type information will be presented on the second native page, and in response to a switching operation (e.g., left-right sliding operation, up-down sliding operation, click operation, etc.) performed by the second user on the second native page for one or more target metadata among the multiple metadata corresponding to the metadata type information currently presented on the second native page, one or more second target metadata will be determined from the remaining metadata except the one or more target metadata among the multiple metadata corresponding to the metadata type information, and then the metadata corresponding to the metadata type information currently presented on the second native page will be switched from the one or more target metadata to the one or more second target metadata. In some embodiments, for each metadata type information, each switching operation for the metadata type information will present one or more metadata corresponding to the metadata type information that is different from the metadata corresponding to the metadata type information presented previously, until all the metadata corresponding to the metadata type information has been presented, at which time the one or more target metadata corresponding to the metadata type information will be presented again.

[0126] Figure 4FIG. 1 is a flowchart of a method for sharing information according to an embodiment of the present application. Figure 4 As shown, in step S41, the first user device generates sharing information corresponding to the sharing operation in response to the sharing operation initiated by the first user for the first native page in the web native rendering application, wherein the first native page is generated after native rendering of at least one first information stream in the HTML page corresponding to the first link address according to the first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page; in step S42, the first user device sends the sharing information to the network device; in step S43, the network device receives multiple sharing information sent by multiple first user devices; in step S44, the network device classifies and aggregates the multiple sharing information, generates multiple object information, and publishes the multiple object information in the web native rendering application, wherein each of the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. In step S45, the second user device responds to a browsing operation performed by the second user on target object information among multiple object information in a web native rendering application, wherein the target object information includes at least one target metadata representation information and a target link address corresponding to each target metadata representation information; in step S46, the second user device obtains at least one target metadata from an HTML page corresponding to the target link address according to a target configuration file; in step S47, the second user device presents the at least one target metadata on a second native page corresponding to the browsing operation according to the target configuration file.

[0127] Figure 5A structural diagram of a network device for sharing information according to an embodiment of the present application is shown, and the device includes a module-one 11 and a module-two 12. The module-one 11 is used to receive a plurality of sharing information, and the plurality of sharing information is sent by a plurality of first users, wherein the sharing information sent by each of the plurality of first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a web native rendering application and metadata representation information corresponding to at least one metadata in the first native page, and the first native page is generated after native rendering of at least one first information stream in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address; the module-two 12 is used to classify and aggregate the plurality of sharing information, generate a plurality of object information, and publish the plurality of object information in the web native rendering application, wherein each of the plurality of object information includes at least one metadata representation information and a link address corresponding to each metadata representation information.

[0128] A module 11 is used to receive multiple sharing information, wherein the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes the link address of the first native page corresponding to the sharing operation initiated by the first user in the web native rendering application and metadata representation information corresponding to at least one metadata in the first native page, and the first native page is generated after native rendering of at least one first information stream in the HTML page corresponding to the link address according to the first configuration file corresponding to the link address. In some embodiments, the web native rendering application is used to render at least one information stream in the HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, the first configuration file includes template information and information stream parsing rule information, and the template information includes one or more native control description information, and the native control description information is used to describe the type and properties of the native control that needs to be rendered on the first native page. According to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. In some embodiments, taking the Android system as an example, the native control can be a view preset by the user device system (for example, Button, TextView, RecyclerView, etc.), or a viewgroup preset by the user device system (the viewgroup includes one or more views or viewgroups, for example, LinearLayout, RelativeLayout, etc.), or a custom view or custom viewgroup. In some embodiments, one or more corresponding native controls are created according to one or more native control description information in the template information. For at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the link address of the first native page through the information flow parsing rule information and bind it to the corresponding native control. In some embodiments, the information flow parsing rule information may include one or more HTML tag path information, and the corresponding HTML tag can be obtained from the HTML page information according to the HTML tag path information, and the information flow in the HTML tag is used as at least one first information flow that needs to be bound to the corresponding native control. In some embodiments, one or more native controls in the template information are rendered on the first native page, wherein the rendering method is based on the native rendering of the user device operating system, rather than the rendering based on the browser kernel.In some embodiments, the first configuration file can be obtained from a server corresponding to the link address of the first native page, or the first configuration file can also be obtained from a server corresponding to the webpage native rendering application, or the first configuration file can also be obtained locally from the user device, or the link address can include the storage address of the first configuration file (for example, a third-party server address), and the first configuration file can be obtained according to the storage address of the first configuration file. In some embodiments, each first user performs a sharing operation on the first native page currently browsed in the webpage native rendering application, and sends sharing information including the link address of the first native page and metadata representation information corresponding to at least one metadata in the first native page to the network device. In some embodiments, the first native page is usually a detail page corresponding to one or more specific objects, and the detail page is used to describe the one or more specific objects. In some embodiments, the metadata is obtained from at least one first information stream presented on the first native page, wherein the metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. for describing a specific object in the first native page. In some embodiments, each sharing information includes the link address corresponding to the first native page and metadata representation information corresponding to at least one metadata obtained from at least one first information stream presented on the first native page. In some embodiments, one metadata corresponds to one sharing object, and multiple metadata in each sharing information may correspond to the same sharing object or to multiple different sharing objects, that is, each metadata representation information corresponds to one sharing object, and multiple metadata representation information may correspond to the same sharing object or to multiple different sharing objects. In some embodiments, the metadata representation information is used to represent the characteristic information or identification information of the metadata to which it corresponds, including but not limited to the object identification information of the sharing object corresponding to the metadata, the user identification information of the sharing user corresponding to the metadata, the metadata type information corresponding to the metadata, the metadata identification information corresponding to the metadata, and any other information used to represent the metadata.

[0129] The first and second modules 12 are used to classify and aggregate the multiple sharing information, generate multiple object information, and publish the multiple object information in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. In some embodiments, the multiple sharing information sent by multiple users received are classified and aggregated to generate multiple object information, and each object information is used to describe a specific object. In some embodiments, multiple metadata representation information in multiple sharing information can be classified and aggregated according to the object identification information in the metadata representation information in each sharing information to generate at least one metadata set, wherein all metadata representation information in each metadata set corresponds to the same sharing object, and then for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, the object information corresponding to the metadata set is generated. In some embodiments, each object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, and the multiple object information is published in the web native rendering application. In some embodiments, one metadata representation information corresponds to one link address, and multiple different metadata representation information can correspond to the same link address or to multiple different link addresses. In some embodiments, when a user browses a piece of object information among multiple object information currently published in a web native rendering application, for each piece of metadata representation information in at least one metadata representation information in the object information, according to the link address corresponding to the metadata representation information, at least one corresponding metadata is obtained from the HTML page information corresponding to the link address, and the at least one metadata is rendered on the current page through native rendering.

[0130] The present application can classify and aggregate multiple sharing information sent by multiple first users, generate multiple object information and publish them in the web rendering native application for browsing by the second user, which can reduce the cost of generating object information. When the second user browses an object information in the web rendering native application, the metadata representation information in the object information and its corresponding link address can be used to obtain the corresponding metadata from the HTML page information corresponding to the link address and present it on the current page through native rendering, which can reduce the development cost of the object information browsing page. In addition, the server corresponding to the web rendering native application itself only needs to store the metadata representation information and its corresponding link address, but does not need to store the specific metadata itself, which can reduce the cost of the server and ensure that the metadata currently presented each time a user browses an object information is always the latest, without the need for the server to actively update the metadata, thereby reducing the maintenance cost of the object information.

[0131] In some embodiments, the metadata representation information includes but is not limited to:

[0132] 1) Object identification information of the sharing object corresponding to the at least one metadata

[0133] 2) User identification information of the sharing user corresponding to the at least one metadata

[0134] 3) Metadata type information corresponding to the at least one metadata

[0135] 4) Metadata identification information of the at least one metadata

[0136] 5) Any combination of the above metadata representation information

[0137] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0138] Here, the relevant metadata represents information and Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0139] In some embodiments, the metadata representation information includes object identification information of a shared object corresponding to the at least one metadata; wherein the classification and aggregation of the received multiple shared information to generate multiple object information includes: classification and aggregation of multiple metadata representation information in the multiple shared information according to the object identification information in the metadata representation information in each shared information to generate at least one metadata set, wherein the shared objects corresponding to all metadata representation information in each metadata set meet a predetermined similarity; for each metadata set, object information corresponding to the metadata set is generated according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address. Here, the related operations are the same as Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0140] In some embodiments, the metadata representation information also includes metadata type information corresponding to the at least one metadata; wherein, for each metadata set, according to at least one metadata representation information among all metadata representation information in the metadata set and its corresponding link address, generating object information corresponding to the metadata set includes: for each metadata set, if multiple metadata representation information in the metadata set corresponds to the same metadata type information, determining at least one metadata representation information from the multiple metadata representation information, removing other metadata representation information from the multiple metadata representation information except the at least one metadata representation information from the metadata set, and generating object information corresponding to the metadata set according to the remaining at least one metadata representation information in the metadata set and its corresponding link address. Here, the relevant operations are the same as Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0141] In some embodiments, each object information further includes weight information corresponding to each metadata representation information in the object information; wherein the device is further used to: for each object information, determine the weight information corresponding to each metadata representation information in the object information. Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0142] In some embodiments, the device is further configured to: for each object information, generate a second configuration file corresponding to the object information, and publish the second configuration file in the webpage native rendering application. Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0143] In some embodiments, the metadata representation information includes metadata identification information of the at least one metadata; for each object information, generating a second configuration file corresponding to the object information, and publishing the second configuration file in the webpage native rendering application, includes: for each object information, according to the metadata identification information in each metadata representation information in the object information, and the first configuration file corresponding to the link address corresponding to each metadata representation information, generating the second configuration file corresponding to the object information. Here, the related operations are the same as Figure 1 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0144] Figure 6A structural diagram of a first user device for sharing information according to an embodiment of the present application is shown, and the device includes a 21 module 21 and a 22 module 22. The 21 module 21 is used to generate sharing information corresponding to the sharing operation in response to a sharing operation initiated by a first user for a first native page in a web native rendering application, wherein the first native page is generated after native rendering of at least one first information stream in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes the link address of the first native page and metadata representation information corresponding to at least one metadata in the first native page; the 22 module 22 is used to send the sharing information to a network device.

[0145] The second module 21 is used to generate sharing information corresponding to the sharing operation in response to a sharing operation initiated by a first user for a first native page in a webpage native rendering application, wherein the first native page is generated after native rendering of at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to at least one metadata in the first link address and the first native page. In some embodiments, the webpage native rendering application is used to render at least one information flow in an HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, the first configuration file includes template information and information flow parsing rule information, and the template information includes one or more native control description information, and the native control description information is used to describe the type and attributes of the native control that needs to be rendered on the first native page. According to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. In some embodiments, according to the one or more native control description information in the template information, one or more corresponding native controls are created, and for at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the first link address through the information flow parsing rule information and bind it to the corresponding native control. In some embodiments, the information flow parsing rule information may include one or more HTML tag path information, and the corresponding HTML tag can be obtained from the HTML page information according to the HTML tag path information, and the information flow in the HTML tag is used as at least one first information flow that needs to be bound to the corresponding native control. In some embodiments, one or more native controls in the template information are rendered on the first native page by native rendering. In some embodiments, the first native page is usually a detail page corresponding to one or more specific objects, and the detail page is used to describe the one or more specific objects. In some embodiments, at least one metadata can be obtained from at least one first information flow presented on the first native page, wherein the metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. for describing a specific object in the first native page. In some embodiments, the metadata representation information includes but is not limited to any information used to represent the metadata, such as object identification information of the shared object corresponding to the metadata, user identification information of the sharing user corresponding to the metadata, metadata type information corresponding to the metadata, metadata identification information corresponding to the metadata, etc.

[0146] The second module 22 is used to send the sharing information to the network device.

[0147] In some embodiments, the generating of the sharing information corresponding to the sharing operation includes: obtaining at least one metadata from the at least one first information stream; determining metadata representation information corresponding to the at least one metadata; and generating the sharing information corresponding to the sharing operation according to the metadata representation information and the first link address. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0148] In some embodiments, the obtaining of at least one metadata from the at least one first information stream includes a second module 23 (not shown) and a second module 24 (not shown). The second module 23 is used to determine one or more sharing objects corresponding to the first native page; the second module 24 is used to obtain at least one metadata corresponding to the one or more sharing objects from the at least first information stream. Here, the specific implementation of the second module 23 and the second module 24 is the same as Figure 2 The embodiments of steps S23 and S24 are the same or similar, so they are not repeated here and are included here by reference.

[0149] In some embodiments, the second and third modules 23 are used to: determine one or more sharing objects corresponding to the first native page by performing semantic analysis on the at least first information flow. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0150] In some embodiments, the second and third modules 23 are used to: obtain page description information from the HTML page corresponding to the first link address; and determine one or more sharing objects corresponding to the first native page according to the page description information. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0151] In some embodiments, the 24 module 24 includes a 25 module 25 (not shown) and a 26 module 26 (not shown). The 25 module 25 is used to determine at least one sharing object from the one or more sharing objects; the 26 module 26 is used to obtain at least one metadata corresponding to the at least one sharing object from the at least first information flow. Here, the specific implementation of the 25 module 25 and the 26 module 26 is the same as Figure 2 The embodiments of steps S25 and S26 are the same or similar, so they are not repeated here and are included here by reference.

[0152] In some embodiments, the 25 module 25 is used to: determine the weight information corresponding to each of the one or more sharing objects; and determine at least one sharing object that meets a predetermined weight condition from the one or more sharing objects according to the weight information corresponding to each sharing object. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0153] In some embodiments, the second five module 25 is used to: present the one or more sharing objects to the first user; obtain at least one sharing object selected by the first user from the one or more sharing objects. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0154] In some embodiments, the operation object of the sharing operation is the second information stream selected by the first user in the first native page; wherein the second and third modules 23 are used to: obtain at least one second sharing object corresponding to the second information stream by semantically analyzing the second information stream; and determine the at least one second sharing object as one or more sharing objects corresponding to the first native page. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0155] In some embodiments, the metadata representation information includes but is not limited to:

[0156] 1) Object identification information of the sharing object corresponding to the at least one metadata

[0157] 2) User identification information of the first user

[0158] 3) Metadata type information corresponding to the at least one metadata

[0159] 4) Metadata identification information of the at least one metadata

[0160] 5) Any combination of the above metadata representation information

[0161] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0162] Here, the relevant metadata represents information and Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0163] In some embodiments, the metadata representation information includes metadata identification information of the at least one metadata; wherein the device is further used to: obtain the metadata identification information of the at least one metadata. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0164] In some embodiments, the step of obtaining metadata identification information of the at least one metadata includes at least one of the following: determining location information of the at least one metadata in at least one first information flow, and determining the location information as metadata identification information of the at least one metadata; determining information flow parsing rule information corresponding to the at least one metadata in the first configuration file, and determining identification information of the information flow parsing rule information in the first configuration file as metadata identification information of the at least one metadata. Figure 2 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0165] Figure 7 A structural diagram of a second user device for sharing information according to an embodiment of the present application is shown, and the device includes a three-one module 31, a three-two module 32, and a three-three module 33. The three-one module 31 is used to respond to a browsing operation performed by a second user on target object information among multiple object information in a webpage native rendering application, wherein the multiple object information is generated by a network device after classifying and aggregating multiple sharing information sent by multiple first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information; the three-two module 32 is used to obtain at least one metadata from an HTML page corresponding to the link address according to a target configuration file; the three-three module 33 is used to present the at least one metadata on a second native page corresponding to the browsing operation according to the target configuration file.

[0166] The three-in-one module 31 is used to respond to the browsing operation performed by the second user on the target object information among the multiple object information in the web native rendering application, wherein the multiple object information is generated by the network device after classifying and aggregating the multiple sharing information sent by the multiple first users, and the target object information includes at least one metadata representation information and the link address corresponding to each metadata representation information. In some embodiments, the web native rendering application is used to render at least one information stream in the HTML page corresponding to a certain link address on the current native page by native rendering. In some embodiments, when the second user performs a browsing operation on the target object information among the multiple object information currently released in the web native rendering application, the details page corresponding to the target object information, i.e., the second native page, will be presented on the web native rendering application. In some embodiments, the multiple object information is generated by the network device after classifying and aggregating at least one sharing information sent by multiple first users respectively. Each sharing information is generated in response to a sharing operation initiated by the first user for the first native page in the web native rendering application. The first native page is generated after native rendering of at least one first information flow in the HTML page corresponding to the link address of the first native page according to the first configuration file corresponding to the link address of the first native page. The first configuration file includes template information and information flow parsing rule information. The template information includes one or more native control description information. The native control description information is used to describe the type and properties of the native control that needs to be rendered on the first native page. According to the template information, one or more native controls corresponding to the template information can be rendered on the first native page. According to the one or more native control description information in the template information, one or more corresponding native controls are created. For at least one of the one or more native controls, it is necessary to obtain the corresponding at least one first information flow from the HTML page information corresponding to the link address of the first native page through the information flow parsing rule information and bind it to the corresponding native control, and render the one or more native controls on the first native page by native rendering. In some embodiments, the first native page is usually a details page corresponding to one or more specific objects, which is used to describe the one or more specific objects. The metadata includes but is not limited to basic information such as title information, introduction information, cover image information, etc. used to describe a specific object in the first native page. The metadata representation information includes but is not limited to object identification information of the shared object corresponding to the metadata, user identification information of the sharing user corresponding to the metadata, metadata type information corresponding to the metadata, metadata identification information corresponding to the metadata, and any other information used to represent the metadata.In some embodiments, each object information includes at least one metadata representation information and a link address corresponding to each metadata representation information. The link address corresponding to each metadata representation information is the link address of the first native page corresponding to the metadata representation information. Different metadata representation information can correspond to the same link address or to different link addresses.

[0167] The third module 32 is used to obtain at least one metadata from the HTML page corresponding to the link address according to the target configuration file. In some embodiments, the target configuration file can be a second configuration file corresponding to the target object information, or a first configuration file corresponding to the link address corresponding to each metadata representation information. In some embodiments, if the target configuration file is the second configuration file corresponding to the target object information, the second configuration file includes information flow parsing rule information corresponding to each metadata representation information in the target object information, and according to the information flow parsing rule information, the metadata corresponding to each metadata representation information can be obtained from the HTML page information corresponding to the link address corresponding to each metadata representation information. In some embodiments, if the target configuration file is the first configuration file corresponding to the link address corresponding to each metadata representation information, then for each metadata representation information, at least one metadata can be obtained from the HTML page corresponding to the link address according to the information flow parsing rule information in the first configuration file corresponding to the link address corresponding to the metadata representation information.

[0168] Module 33 is used to present the at least one metadata on the second native page corresponding to the browsing operation according to the target configuration file. In some embodiments, if the target configuration file is the second configuration file corresponding to the target object information, the at least one metadata obtained is rendered on the second native page by native rendering according to the template information in the second configuration file. In some embodiments, if the target configuration file is the first configuration file corresponding to the link address corresponding to each metadata representation information, the metadata is rendered on the second native page by native rendering according to the template information in the first configuration file corresponding to each metadata in the at least one metadata obtained, that is, the rendering presentation mode of the metadata on the first native page is the same as the rendering presentation mode of the metadata on the second native page.

[0169] In some embodiments, the target configuration file is a second configuration file corresponding to the target object information. Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0170] In some embodiments, the target configuration file is a first configuration file corresponding to the link address corresponding to each metadata representation information; wherein the three-two module 32 includes a three-two-one module 321 (not shown). The three-two-one module 321 is used to obtain at least one metadata from the HTML page corresponding to the link address for each metadata representation information according to the first configuration file corresponding to the link address corresponding to the metadata representation information. Here, the specific implementation method of the three-two-one module 321 is the same as Figure 3 The embodiments of step S321 are the same or similar, so they are not described again and are included here by reference.

[0171] In some embodiments, the metadata representation information includes but is not limited to:

[0172] 1) Object identification information of the shared object

[0173] 2) Sharing user's user identification information

[0174] 3) Metadata type information

[0175] 4) Metadata identification information

[0176] 5) Any combination of the above metadata representation information

[0177] It should be noted that the above description of metadata representation information is only an example and not a limitation of the present application. Those skilled in the art should understand that any form of metadata representation information should be included in the protection scope of the present application.

[0178] Here, the relevant metadata represents information and Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0179] In some embodiments, the metadata representation information includes metadata identification information; wherein the 321 module 321 includes a 322 module 322 (not shown). The 322 module 322 is used to obtain at least one metadata from the HTML page corresponding to the link address for each metadata representation information according to the first configuration file corresponding to the link address corresponding to the metadata representation information and the metadata identification information in the metadata representation information. Here, the specific implementation method of the 322 module 322 is the same as Figure 3 The embodiments of step S321 are the same or similar, so they are not described again and are included here by reference.

[0180] In some embodiments, the metadata identification information is the location information of each metadata in at least one first information flow in the HTML page corresponding to the link address corresponding to the metadata; wherein the three-two-two module 322 is used to: for each metadata representation information, according to the first configuration file corresponding to the link address corresponding to the metadata representation information, obtain at least one first information flow from the HTML page corresponding to the link address, and according to the location information in the metadata representation information, obtain at least one metadata from the at least one first information flow. Here, the related operations are the same as Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0181] In some embodiments, the metadata identification information is the identification information of the information flow parsing rule information corresponding to the first configuration file corresponding to the link address corresponding to each metadata in the first configuration file; wherein the three-two-two module 322 is used to: for each metadata representation information, according to the identification information in the metadata representation information, obtain the information flow parsing rule information corresponding to the link address from the first configuration file corresponding to the link address corresponding to the metadata representation information, and according to the information flow parsing rule information, obtain at least one metadata from the HTML page corresponding to the link address. Here, the related operations are the same as Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0182] In some embodiments, the target object information also includes weight information corresponding to each metadata representation information; wherein, presenting the at least one metadata on the second native page corresponding to the browsing operation includes: determining the target metadata in the at least one metadata according to the weight information corresponding to each metadata; presenting the target metadata on the second native page corresponding to the browsing operation; responding to the switching operation performed by the second user on the second native page; determining the second target metadata corresponding to the target metadata after switching in the at least one metadata; and switching the target metadata currently presented on the second native page to the second target metadata. Here, the relevant operations are similar to Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0183] In some embodiments, the target object information also includes weight information corresponding to each metadata characterization information, and the metadata characterization information includes metadata type information corresponding to the at least one metadata; wherein, presenting the at least one metadata on the second native page corresponding to the browsing operation includes: for each metadata type information among the multiple metadata type information corresponding to the multiple metadata, determining the target metadata corresponding to the metadata type information according to the weight information corresponding to each metadata among the multiple metadata corresponding to the metadata type information; for each metadata type information, presenting the target metadata corresponding to the metadata type information on the second native page corresponding to the browsing operation, in response to the switching operation performed by the second user on the second native page; determining the switched second target metadata corresponding to the target metadata among the multiple metadata corresponding to the metadata type information; switching the target metadata currently presented on the second native page to the second target metadata. Here, the related operations are as follows: Figure 3 The embodiments shown are the same or similar, so they are not described again and are incorporated herein by reference.

[0184] Figure 8 An exemplary system is shown that can be used to implement the various embodiments described in this application.

[0185] like Figure 8 In some embodiments shown, the system 300 can be used as any of the devices in the various described embodiments. In some embodiments, the system 300 may include one or more computer-readable media (e.g., system memory or NVM / storage device 320) with instructions and one or more processors (e.g., (one or more) processors 305) coupled to the one or more computer-readable media and configured to execute instructions to implement modules to perform the actions described in this application.

[0186] For one embodiment, system control module 310 may include any suitable interface controller to provide any suitable interface to at least one of processor(s) 305 and / or any suitable device or component in communication with system control module 310 .

[0187] The system control module 310 may include a memory controller module 330 to provide an interface to the system memory 315. The memory controller module 330 may be a hardware module, a software module, and / or a firmware module.

[0188] The system memory 315 may be used, for example, to load and store data and / or instructions for the system 300. For one embodiment, the system memory 315 may include any suitable volatile memory, such as a suitable DRAM. In some embodiments, the system memory 315 may include double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

[0189] For one embodiment, system control module 310 may include one or more input / output (I / O) controllers to provide interfaces to NVM / storage device 320 and communication interface(s) 325 .

[0190] For example, NVM / storage device 320 may be used to store data and / or instructions. NVM / storage device 320 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives (HDDs), one or more compact disk (CD) drives, and / or one or more digital versatile disk (DVD) drives).

[0191] NVM / storage device 320 may include storage resources that are physically part of the device on which system 300 is installed, or it may be accessible to the device without being part of the device. For example, NVM / storage device 320 may be accessed over a network via communication interface(s) 325.

[0192] Communication interface(s) 325 may provide an interface for system 300 to communicate over one or more networks and / or with any other suitable devices. System 300 may wirelessly communicate with one or more components of a wireless network in accordance with any of one or more wireless network standards and / or protocols.

[0193] For one embodiment, at least one of the processor(s) 305 may be packaged together with the logic of one or more controllers of the system control module 310 (e.g., the memory controller module 330). For one embodiment, at least one of the processor(s) 305 may be packaged together with the logic of one or more controllers of the system control module 310 to form a system-in-package (SiP). For one embodiment, at least one of the processor(s) 305 may be integrated on the same die with the logic of one or more controllers of the system control module 310. For one embodiment, at least one of the processor(s) 305 may be integrated on the same die with the logic of one or more controllers of the system control module 310 to form a system on chip (SoC).

[0194] In various embodiments, the system 300 may be, but is not limited to: a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, the system 300 may have more or fewer components and / or a different architecture. For example, in some embodiments, the system 300 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an application specific integrated circuit (ASIC), and a speaker.

[0195] The present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer code. When the computer code is executed, the method described in any of the preceding items is executed.

[0196] The present application also provides a computer program product. When the computer program product is executed by a computer device, the method described in any of the preceding items is executed.

[0197] The present application also provides a computer device, the computer device comprising:

[0198] one or more processors;

[0199] a memory for storing one or more computer programs;

[0200] When the one or more computer programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any of the preceding items.

[0201] It should be noted that the present application can be implemented in software and / or a combination of software and hardware, for example, can be implemented using an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of the present application (including relevant data structures) can be stored in a computer-readable recording medium, for example, a RAM memory, a magnetic or optical drive or a floppy disk and similar devices. In addition, some steps or functions of the present application can be implemented using hardware, for example, as a circuit that cooperates with a processor to perform each step or function.

[0202] In addition, a part of the present application may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present application through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes but is not limited to source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0203] Communication media include media by which communication signals containing, for example, computer readable instructions, data structures, program modules, or other data are transmitted from one system to another. Communication media may include guided transmission media such as cables and wires (e.g., fiber optic, coaxial, etc.) and wireless (unguided transmission) media that can propagate energy waves, such as acoustic, electromagnetic, RF, microwave, and infrared. Computer readable instructions, data structures, program modules, or other data may be embodied as a modulated data signal in, for example, a wireless medium such as a carrier wave or similar mechanism such as embodied as part of spread spectrum technology. The term "modulated data signal" refers to a signal whose one or more characteristics are changed or set in such a manner as to encode information in the signal. Modulation may be analog, digital, or a hybrid modulation technique.

[0204] By way of example and not limitation, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable storage media include, but are not limited to, volatile memory, such as random access memory (RAM, DRAM, SRAM); and non-volatile memory, such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic / ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disks, magnetic tapes, CDs, DVDs); or other media now known or later developed that can store computer-readable information / data for use by a computer system.

[0205] Here, according to an embodiment of the present application, a device is included, which includes a memory for storing computer program instructions and a processor for executing the program instructions, wherein, when the computer program instructions are executed by the processor, the device is triggered to run the methods and / or technical solutions based on the aforementioned multiple embodiments of the present application.

[0206] It is obvious to those skilled in the art that the present application is not limited to the details of the above exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic features of the present application. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present application is limited by the attached claims rather than the above description, so it is intended to include all changes that fall within the meaning and scope of the equivalent elements of the claims in the present application. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

Claims

1. A method for sharing information, applied to a network device, wherein: The method comprises: Receive multiple sharing information, where the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in a web native rendering application and metadata representation information corresponding to at least one metadata in the first native page, wherein the first native page is generated by natively rendering at least one first information flow in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address, wherein the first native page is a page currently browsed by the first user in the web native rendering application, and the at least one metadata is obtained from at least one first information flow presented on the first native page , basic information used to describe a specific object in the first native page, the metadata representation information is used to represent feature information or identification information of the corresponding metadata, the first configuration file includes template information and information flow parsing rule information, the template information includes one or more native control description information, the native control description information is used to describe the type and attribute information of the native control to be rendered on the first native page, the information flow parsing rule information is used to obtain the corresponding HTML tag from the HTML page information, and use the information flow in the HTML tag as at least one first information flow that needs to be bound to the corresponding native control, and the metadata representation information includes object identification information of the shared object corresponding to the at least one metadata; According to the object identification information in the metadata representation information in each shared information, multiple metadata representation information in the multiple shared information are classified and aggregated to generate at least one metadata set, wherein the shared objects corresponding to all metadata representation information in each metadata set meet a predetermined similarity; for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, object information corresponding to the metadata set is generated, and multiple object information is published in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, and each object information is used to describe a specific object.

2. The method according to claim 1, wherein: The metadata representation information also includes metadata type information corresponding to the at least one metadata; The step of generating, for each metadata set, object information corresponding to the metadata set according to at least one metadata representation information among all metadata representation information in the metadata set and its corresponding link address includes: For each metadata set, if multiple metadata representation information in the metadata set corresponds to the same metadata type information, at least one metadata representation information is determined from the multiple metadata representation information, other metadata representation information except the at least one metadata representation information in the multiple metadata representation information is removed from the metadata set, and object information corresponding to the metadata set is generated according to the remaining at least one metadata representation information in the metadata set and its corresponding link address.

3. The method according to claim 1, wherein: The method further comprises: For each piece of object information, a second configuration file corresponding to the object information is generated, and the second configuration file is published in the webpage native rendering application.

4. The method according to claim 3, wherein: The metadata representation information includes metadata identification information of the at least one metadata; For each piece of object information, generating a second configuration file corresponding to the object information, and publishing the second configuration file in the webpage native rendering application, includes: For each object information, a second configuration file corresponding to the object information is generated according to the metadata identification information in each metadata representation information in the object information and the first configuration file corresponding to the link address corresponding to each metadata representation information.

5. A method for sharing information, applied to a first user device, wherein: The method comprises: In response to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, sharing information corresponding to the sharing operation is generated, wherein the first native page is generated after natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page, wherein the first native page is a page currently browsed by the first user in the webpage native rendering application, the at least one metadata is basic information obtained from at least one first information flow presented on the first native page and used to describe a specific object in the first native page, the metadata representation information is used to represent feature information or identification information of the metadata corresponding thereto, the first configuration file includes template information and information flow parsing rule information, the template information includes one or more native control description information, the native control description information is used to describe the type and attribute information of the native control to be rendered on the first native page, the information flow parsing rule information is used to obtain the corresponding HTML tag from the HTML page information, and use the information flow in the HTML tag as the at least one first information flow to be bound to the corresponding native control, and the metadata representation information includes object identification information of the sharing object corresponding to the at least one metadata; The sharing information is sent to a network device, so that the network device classifies and aggregates multiple metadata representation information in the multiple sharing information according to the object identification information in the metadata representation information in each sharing information, and generates at least one metadata set, wherein the sharing objects corresponding to all metadata representation information in each metadata set meet a predetermined similarity; for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, object information corresponding to the metadata set is generated, and multiple object information is published in the web native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, and each object information is used to describe a specific object.

6. The method according to claim 5, wherein: The generating sharing information corresponding to the sharing operation includes: Retrieving at least one metadata from the at least one first information stream; Determining metadata representation information corresponding to the at least one metadata; Sharing information corresponding to the sharing operation is generated according to the metadata representation information and the first link address.

7. The method according to claim 6, wherein: The acquiring at least one metadata from the at least one first information stream comprises: Determine one or more sharing objects corresponding to the first native page; At least one metadata corresponding to the one or more sharing objects is obtained from the at least one first information flow.

8. The method according to claim 7, wherein: The determining one or more sharing objects corresponding to the first native page includes at least one of the following: Determine one or more sharing objects corresponding to the first native page by performing semantic analysis on the at least one first information flow; or, Obtain page description information from the HTML page corresponding to the first link address, and determine one or more sharing objects corresponding to the first native page according to the page description information.

9. The method according to claim 7 or 8, wherein: The acquiring at least one metadata corresponding to the one or more sharing objects from the at least one first information stream includes: determining at least one sharing object from the one or more sharing objects; At least one metadata corresponding to the at least one sharing object is obtained from the at least one first information flow.

10. The method according to claim 9, wherein: The determining at least one sharing object from the one or more sharing objects includes at least one of the following: Determine weight information corresponding to each of the one or more sharing objects, and determine at least one sharing object that meets a predetermined weight condition from the one or more sharing objects according to the weight information corresponding to each sharing object; or, The one or more sharing objects are presented to the first user, and at least one sharing object selected by the first user from the one or more sharing objects is obtained.

11. A method for sharing information, applied to a second user device, wherein: The method comprises: In response to a browsing operation performed by a second user on target object information among multiple object information in a webpage native rendering application, wherein the multiple object information is generated by a network device after classifying and aggregating multiple sharing information sent by multiple first users, and the target object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, wherein the network device receives multiple sharing information, and the multiple sharing information is sent by multiple first users, wherein the sharing information sent by each of the multiple first users includes a link address of a first native page corresponding to a sharing operation initiated by the first user in the webpage native rendering application and metadata representation information corresponding to at least one metadata in the first native page, and the first native page is generated by natively rendering at least one first information stream in an HTML page corresponding to the link address according to a first configuration file corresponding to the link address, wherein the first native page is a page currently browsed by the first user in the webpage native rendering application, and the at least one metadata is basic information obtained from at least one first information stream presented on the first native page and used to describe a specific object in the first native page, and the metadata representation information is used to represent feature information or identification information of the metadata corresponding to it, and the first configuration file The method comprises template information and information flow parsing rule information, wherein the template information comprises one or more native control description information, wherein the native control description information is used to describe the type and attribute information of the native control to be rendered on the first native page, and the information flow parsing rule information is used to obtain the corresponding HTML tag from the HTML page information, and use the information flow in the HTML tag as at least one first information flow to be bound to the corresponding native control, and the metadata representation information comprises object identification information of the shared object corresponding to the at least one metadata; the network device classifies and aggregates multiple metadata representation information in the multiple shared information according to the object identification information in the metadata representation information in each shared information, and generates at least one metadata set, wherein the shared objects corresponding to all metadata representation information in each metadata set meet the predetermined similarity; for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, generates object information corresponding to the metadata set, and publishes multiple object information in the webpage native rendering application, wherein each object information in the multiple object information comprises at least one metadata representation information and a link address corresponding to each metadata representation information, and each object information is used to describe a specific object; According to the target configuration file, obtaining at least one metadata from the HTML page corresponding to the link address; The at least one metadata is presented on a second native page corresponding to the browsing operation according to the target configuration file.

12. The method according to claim 11, wherein: The target configuration file is a second configuration file corresponding to the target object information.

13. The method according to claim 11, wherein: The target configuration file is a first configuration file corresponding to the link address corresponding to each metadata representation information; Wherein, obtaining at least one metadata from the HTML page corresponding to the link address according to the target configuration file includes: For each metadata representation information, at least one metadata is obtained from an HTML page corresponding to the link address according to a first configuration file corresponding to the link address corresponding to the metadata representation information.

14. The method according to claim 13, wherein: The metadata representation information includes metadata identification information; The step of obtaining, for each metadata representation information, at least one metadata from an HTML page corresponding to the link address according to a first configuration file corresponding to the link address corresponding to the metadata representation information includes: For each metadata representation information, at least one metadata is obtained from an HTML page corresponding to the link address according to the first configuration file corresponding to the link address corresponding to the metadata representation information and the metadata identification information in the metadata representation information.

15. A method for sharing information, wherein: The method comprises: The first user device generates sharing information corresponding to the sharing operation in response to a sharing operation initiated by a first user on a first native page in a webpage native rendering application, wherein the first native page is generated after natively rendering at least one first information flow in an HTML page corresponding to the first link address according to a first configuration file corresponding to the first link address, and the sharing information includes metadata representation information corresponding to the first link address and at least one metadata in the first native page, wherein the first native page is a page currently browsed by the first user in the webpage native rendering application, the at least one metadata is basic information obtained from at least one first information flow presented on the first native page and used to describe a specific object in the first native page, the metadata representation information is used to represent feature information or identification information of the metadata corresponding thereto, the first configuration file includes template information and information flow parsing rule information, the template information includes one or more native control description information, the native control description information is used to describe the type and attribute information of the native control to be rendered on the first native page, the information flow parsing rule information is used to obtain the corresponding HTML tag from the HTML page information, and use the information flow in the HTML tag as the at least one first information flow to be bound to the corresponding native control, and the metadata representation information includes object identification information of the sharing object corresponding to the at least one metadata; The first user equipment sends the sharing information to a network device; The network device receives a plurality of sharing information sent by a plurality of first user devices; The network device classifies and aggregates multiple metadata representation information in the multiple shared information according to the object identification information in the metadata representation information in each shared information, and generates at least one metadata set, wherein the shared objects corresponding to all metadata representation information in each metadata set meet a predetermined similarity; for each metadata set, according to at least one metadata representation information in all metadata representation information in the metadata set and its corresponding link address, generates object information corresponding to the metadata set, and publishes multiple object information in the webpage native rendering application, wherein each object information in the multiple object information includes at least one metadata representation information and a link address corresponding to each metadata representation information, and each object information is used to describe a specific object; The second user device responds to a browsing operation performed by the second user on target object information among the plurality of object information in the webpage native rendering application, wherein the target object information includes at least one target metadata representation information and a target link address corresponding to each target metadata representation information; The second user device obtains at least one target metadata from an HTML page corresponding to the target link address according to the target configuration file; The second user device presents the at least one target metadata on a second native page corresponding to the browsing operation according to the target configuration file.

16. A device for sharing information, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions which, when executed, cause the processor to perform a method as claimed in any one of claims 1 to 4.

17. A device for sharing information, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions which, when executed, cause the processor to perform a method as claimed in any one of claims 5 to 10.

18. A device for sharing information, characterized in that: The device comprises: Processor; and A memory arranged to store computer executable instructions which, when executed, cause the processor to perform a method as claimed in any one of claims 11 to 14.

19. A computer readable medium storing instructions which, when executed, cause a system to perform the operations of the method of any one of claims 1 to 14.

Images