CN111125565A - Method and equipment for inputting information in application - Google Patents

Method and equipment for inputting information in application Download PDF

Info

Publication number
CN111125565A
CN111125565A CN201911061657.8A CN201911061657A CN111125565A CN 111125565 A CN111125565 A CN 111125565A CN 201911061657 A CN201911061657 A CN 201911061657A CN 111125565 A CN111125565 A CN 111125565A
Authority
CN
China
Prior art keywords
information
link address
metadata
application
metadata information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201911061657.8A
Other languages
Chinese (zh)
Inventor
曹强辉
苏勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Zhangmen Science and Technology Co Ltd
Original Assignee
Shanghai Zhangmen Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Zhangmen Science and Technology Co Ltd filed Critical Shanghai Zhangmen Science and Technology Co Ltd
Priority to CN201911061657.8A priority Critical patent/CN111125565A/en
Publication of CN111125565A publication Critical patent/CN111125565A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

The application aims to provide a method and equipment for inputting information in an application, wherein the method comprises the following steps: responding to a link input operation executed by a user in a first input area of a first application, and acquiring a link address corresponding to the link input operation; sending the link address to a network device corresponding to the first application; receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address; inputting at least one of the one or more metadata information into a second input area of the first application. The method and the device can greatly save time cost, can bring great convenience to users, and improve user experience.

Description

Method and equipment for inputting information in application
Technical Field
The present application relates to the field of communications, and more particularly, to a technique for inputting information in an application.
Background
With the development of the times, functions provided by application programs are more and more diversified, in some scenarios, when a user browses a page corresponding to a link address, there may be a publishing requirement or an input requirement for content in the page, for example, when the user browses a page corresponding to a link address, the user desires to share or publish the content in the page, so that other users can see the content. In the prior art, when a user has a release demand or an input demand for page content corresponding to a link address, a series of processes of inputting the link address, a title, a text and uploading a cover page and the like generally need to be manually executed in sequence, and in the process, the user needs to manually input more content.
Disclosure of Invention
An object of the present application is to provide a method and apparatus for inputting information in an application.
According to an aspect of the present application, there is provided a method for inputting information in an application, applied to a user equipment, the method including:
responding to a link input operation executed by a user in a first input area of a first application, and acquiring a link address corresponding to the link input operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
inputting at least one of the one or more metadata information into a second input area of the first application.
According to another aspect of the present application, there is provided a method for inputting information in an application, applied to a network device, the method including:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
According to another aspect of the present application, there is provided a method for publishing information in an application, applied to a user equipment, the method including:
responding to a link publishing trigger operation executed in a first application of user equipment by a user, and acquiring a link address corresponding to the link publishing trigger operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
generating release information in the first application according to at least one of the one or more pieces of metadata information;
and issuing the issuing information through the first application.
According to another aspect of the present application, there is provided a method for publishing information in an application, applied to a network device, the method including:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library according to the link address to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
According to an aspect of the present application, there is provided a user equipment for inputting information in an application, the apparatus comprising:
the system comprises a one-to-one module, a first application module and a second application module, wherein the one-to-one module is used for responding to a link input operation executed by a user in a first input area of a first application and acquiring a link address corresponding to the link input operation;
a second module, configured to send the link address to a network device corresponding to the first application;
a third module, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from page information corresponding to the link address;
a fourth module for entering at least one of the one or more metadata information into a second input area of the first application.
According to another aspect of the present application, there is provided a network device for inputting information in an application, the device including:
the first module is used for receiving a link address sent by user equipment;
a second module, configured to perform domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
a third module, configured to parse, according to the tag template, page information corresponding to the link address to obtain one or more metadata information, where each metadata information corresponds to content information of at least one metadata node that is successfully parsed;
a twenty-four module for sending the one or more metadata information to the user equipment.
According to another aspect of the present application, there is provided a user equipment for publishing information in an application, the user equipment comprising:
the system comprises a first module, a second module and a third module, wherein the first module is used for responding to a link publishing triggering operation executed by a user in a first application of user equipment and acquiring a link address corresponding to the link publishing triggering operation;
a third module and a second module, which are used for sending the link address to the network equipment corresponding to the first application;
a third module, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is obtained from page information corresponding to the link address;
a third module and a fourth module, configured to generate release information in the first application according to at least one piece of metadata information in the one or more pieces of metadata information;
and the third and fifth modules are used for releasing the release information through the first application.
According to another aspect of the present application, there is provided a network device for publishing information in an application, the device comprising:
a fourth module, configured to receive a link address sent by a user equipment;
a fourth module, configured to perform domain name matching on the link address and a tag template library according to the link address, to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
a fourth module and a third module, which are used for analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
a fourteen module to send the one or more metadata information to the user equipment.
According to an aspect of the present application, there is provided an apparatus for inputting information in an application, wherein the apparatus includes:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
responding to a link input operation executed by a user in a first input area of a first application, and acquiring a link address corresponding to the link input operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
inputting at least one of the one or more metadata information into a second input area of the first application.
According to another aspect of the present application, there is provided an apparatus for inputting information in an application, wherein the apparatus includes:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
According to another aspect of the present application, there is provided an apparatus for publishing information in an application, wherein the apparatus comprises:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
responding to a link publishing trigger operation executed in a first application of user equipment by a user, and acquiring a link address corresponding to the link publishing trigger operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
generating release information in the first application according to at least one of the one or more pieces of metadata information;
and issuing the issuing information through the first application.
According to another aspect of the present application, there is provided an apparatus for publishing information in an application, wherein the apparatus comprises:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library according to the link address to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
According to one aspect of the application, there is provided a computer-readable medium storing instructions that, when executed, cause a system to:
responding to a link input operation executed by a user in a first input area of a first application, and acquiring a link address corresponding to the link input operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
inputting at least one of the one or more metadata information into a second input area of the first application.
According to one aspect of the application, there is provided a computer-readable medium storing instructions that, when executed, cause a system to:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
According to one aspect of the application, there is provided a computer-readable medium storing instructions that, when executed, cause a system to:
responding to a link publishing trigger operation executed in a first application of user equipment by a user, and acquiring a link address corresponding to the link publishing trigger operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
generating release information in the first application according to at least one of the one or more pieces of metadata information;
and issuing the issuing information through the first application.
According to one aspect of the application, there is provided a computer-readable medium storing instructions that, when executed, cause a system to:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library according to the link address to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information corresponds to the content information of at least one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
Compared with the prior art, the method and the device can realize intelligent extraction of the metadata information corresponding to the link address, so that quick information input and quick content release can be realized, and the method and the device have the advantages of automation and high efficiency; the user only needs to execute the link input operation or the link release triggering operation, so that the information can be automatically input in the application or released in the application, and the user does not need to perform any operation except the link input operation or the link release triggering operation, so that the time cost is greatly saved, great convenience can be brought to the user, and the user experience is improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 illustrates a flow chart of a method applied to a user device for inputting information in an application according to one embodiment of the present application;
FIG. 2 illustrates a flow chart of a method applied to a network device for inputting information in an application according to one embodiment of the present application;
FIG. 3 illustrates a flowchart of a method applied to a user equipment for publishing information in an application according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a method applied to a network device for publishing information in an application according to an embodiment of the present application;
FIG. 5 illustrates a flow diagram of a method for publishing information in an application, according to one embodiment of the present application;
FIG. 6 illustrates a flow diagram of a method for entering information in an application, according to one embodiment of the present application;
FIG. 7 illustrates a flow diagram of a system method for entering information in an application, according to one embodiment of the present application;
FIG. 8 illustrates a flow diagram of a system method for publishing information in an application, according to one embodiment of the present application;
FIG. 9 illustrates a block diagram of a user equipment for entering information in an application, according to one embodiment of the present application;
FIG. 10 illustrates a network device architecture diagram for entering information in an application, according to one embodiment of the present application;
FIG. 11 illustrates a user equipment structure diagram for publishing information in an application, according to one embodiment of the present application;
FIG. 12 illustrates a network device architecture diagram for publishing information in an application, according to one embodiment of the present application;
FIG. 13 illustrates an exemplary system that can be used to implement the various embodiments described in this application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
The device referred to in this application includes, but is not limited to, a user device, a network device, or a device formed by integrating a user device and a network device through a network. The user equipment includes, but is not limited to, any mobile electronic product, such as a smart phone, a tablet computer, etc., capable of performing human-computer interaction with a user (e.g., human-computer interaction through a touch panel), and the mobile electronic product may employ any operating system, such as an android operating system, an iOS operating system, etc. The network device includes an electronic device capable of automatically performing numerical calculation and information processing according to a preset or stored instruction, and hardware thereof includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like. The network device includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud of a plurality of servers; here, the Cloud is composed of a large number of computers or web servers based on Cloud Computing (Cloud Computing), which is a kind of distributed Computing, one virtual supercomputer consisting of a collection of loosely coupled computers. Including, but not limited to, the internet, a wide area network, a metropolitan area network, a local area network, a VPN network, a wireless Ad Hoc 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 touch terminal, or the network device and the touch terminal through a network.
Of course, those skilled in the art will appreciate that the foregoing is by way of example only, and that other existing or future devices, which may be suitable for use in the present application, are also encompassed within the scope of the present application and are hereby incorporated by reference.
In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
Fig. 1 shows a flowchart of a method for a user equipment to input information in an application according to an embodiment of the present application, the method including step S11, step S12, step S13 and step S14. In step S11, the user equipment, in response to a link input operation performed by a user in a first input area of a first application, acquires a link address corresponding to the link input operation; in step S12, the user equipment sends the link address to the network device corresponding to the first application; in step S13, the user device receives one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address; in step S14, the user device inputs at least one of the one or more metadata information into a second input area of the first application.
In step S11, the user device acquires, in response to a link input operation performed by the user in the first input area of the first application, a link address corresponding to the link input operation. In some embodiments, the link input operation includes, but is not limited to, manually entering a link address in the first input area, and manually pasting the link address on the system clipboard in the first input area.
In step S12, the user equipment sends the link address to the network device corresponding to the first application. In some embodiments, the acquired link in the first input area is sent to a network device corresponding to the first application.
In step S13, the user device receives one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address. In some embodiments, the network device parses HTML page information corresponding to the link address through an HTML parsing technique according to the received link address, obtains one or more metadata information corresponding to the link address, and sends the one or more metadata information to the user device, where the metadata information includes, but is not limited to, title information, content summary information, picture address information, and the like corresponding to the link address.
In step S14, the user device inputs at least one of the one or more metadata information into a second input area of the first application. In some embodiments, all or part of the content of one or more metadata information may be input into the second input area of the first application, or part of the metadata information may be determined from one or more metadata information and all or part of the content of part of the metadata information may be input into the second input area of the first application, where the first input area and the second input area may be two independent input areas in the first application or two independent sub-input areas of the same input area in the first application.
In some embodiments, the step S14 includes: and the user equipment inputs the at least one piece of metadata information into a second input area of the first application according to the corresponding label attribute information of each piece of metadata information in the page information. In some embodiments, the network device corresponding to the first application performs domain name matching on the received link address and a tag template library, obtains a tag template matched with the link address from the tag template library, and parses according to the tag template to obtain attribute information or content information corresponding to one or more tags in HTML page information corresponding to the link address, and uses the parsing result as metadata information corresponding to the link address, where the tag template includes one or more tag attribute information (e.g., "title", "img _ src", etc.) and corresponding tag parsing rules, the tag attribute information is used to indicate metadata category information (e.g., "title", "picture address", etc.) corresponding to the metadata information parsed according to the tag parsing rules corresponding thereto, parses the HTML page information according to the tag parsing rules to obtain metadata information corresponding to each tag attribute information, and sending metadata information including the tag attribute information to the user equipment, selecting at least one piece of metadata information, of which the corresponding tag attribute information meets the input requirement of the second input area, from one or more pieces of metadata information by the first application according to the tag attribute information corresponding to the metadata information, and inputting all or part of the content of the at least one piece of metadata information into the second input area of the first application.
In some embodiments, the second input region comprises one or more second sub-input regions; the step S14 includes: and the user equipment determines the metadata information corresponding to each second sub-input area in the second input area from the one or more metadata information according to the corresponding tag attribute information of each metadata information in the page information, and inputs the metadata information into the second sub-input area, wherein the tag attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area. In some embodiments, the second input region includes one or more sub-input regions (e.g., a title input region, a content summary input region, a picture address input region, etc.), each sub-input region has a corresponding sub-region category information (e.g., the sub-region category information of the title input region is "title"), and the sub-region category information is used to indicate a category of input content corresponding to the sub-input region. In some embodiments, at least one piece of metadata information corresponding to the matching of the corresponding tag attribute information and the sub-region category information of each second sub-input region (for example, the sub-region category information of the second sub-input region is "title", and the tag attribute information matched with the sub-region category information may be "title") is determined from the one or more pieces of metadata information, and all or part of the content of the metadata information is input into the second sub-input region.
In some embodiments, the step S14 includes: and the user equipment acquires the sub-region category information of each second sub-input region in the second input regions, matches the sub-region category information with the corresponding label attribute information of the metadata information in the one or more metadata information in the page information, acquires the metadata information matched with the sub-region category information, and inputs the metadata information into the second sub-input regions. In some embodiments, all sub-input regions of the second input region are traversed, and for each sub-input region, sub-region category information corresponding to the sub-input region is obtained, matching the sub-region category information with the label attribute information corresponding to each metadata information, inputting all or part of the content of at least one metadata information with the matching degree meeting a preset matching degree threshold into the second sub-input region, or, inputting all or part of the contents of a predetermined number of at least one metadata information having the highest degree of matching into the second sub-input area, or, the sub-region category information and the tag attribute information corresponding to the metadata information may be respectively matched, and if the matching degree with some metadata information satisfies a predetermined matching degree threshold, the matching is stopped and all or part of the contents of the metadata information is input to the second sub input area.
In some embodiments, the method further comprises: and the user equipment responds to the editing operation of the user on the second input area to obtain at least one piece of edited metadata information. In some embodiments, the second input area is editable, and the user may perform an editing operation on the metadata information input in the second input area to manually correct the input content and obtain edited metadata information.
In some embodiments, the method further comprises: the user equipment receives failure indication information returned by the network equipment based on the link address, wherein the failure indication information is used for indicating that the link address fails to be matched or failed to be analyzed; presenting the failure indication information in the first application. In some embodiments, in the network device corresponding to the first application, if the link address fails to match the domain name of the tag template library or the tag template matching the link address fails to resolve the metadata information, failure indication information indicating that the link address fails to match or fails to resolve is generated and sent to the user device, where the failure indication information includes, but is not limited to, the link address, a reason why the link address corresponds to the matching failure or a reason why the link address corresponds to the resolving failure, and the first application presents the received failure indication information to prompt the user.
In some embodiments, the second input area of the first application comprises one or more second sub-input areas; wherein the step S12 includes: the user equipment sends the link address and the sub-area category information of each second sub-input area in the second input area to the network equipment corresponding to the first application; the step S14 includes: and the user equipment inputs at least one piece of metadata information in the one or more pieces of metadata information into a corresponding second sub-area in a second input area of the first application, wherein the label attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area. In some embodiments, the second input area includes one or more sub-input areas, and the first application transmits a link address and sub-area category information of each sub-input area to the network device corresponding to the first application, so that the network device can parse one or more metadata information matched with the sub-area category information of the sub-input area, and input at least one metadata information of the one or more metadata information received from the network device into the corresponding sub-input area in the second input area, wherein the tag attribute information (e.g., "title", "img _ src", etc.) corresponding to the input metadata information is matched with the sub-area category information (e.g., the sub-area category information of the title input area is "title") of the sub-input area.
Fig. 2 is a flowchart illustrating a method for a network device to input information in an application according to an embodiment of the present application, where the method includes step S21, step S22, step S23, and step S24. In step S21, the network device receives the link address sent by the user device; in step S22, the network device performs domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes; in step S23, the network device parses the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes a parsing result corresponding to a metadata node that is successfully parsed; in step S24, the network device sends the one or more metadata information to the user device.
In step S21, the network device receives the link address sent by the user device.
In step S22, the network device performs domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes. In some embodiments, the domain name matching is performed on the link address and the tag template library, wherein the domain name matching may determine whether the link address matches a domain name of a certain tag template in the tag template library by detecting whether the link address is the same as or similar to a link address corresponding to each tag template in the tag template library, or may also determine whether the link address matches a link address corresponding to a certain tag template in the tag template library according to a predetermined matching rule by performing domain name matching on the link address and the tag template library. In some embodiments, the tag template includes one or more metadata nodes and a parsing rule corresponding to each metadata node, where the parsing rule is formulated according to a specific parsing algorithm or parsing library (e.g., XPath parsing library) for indicating how to extract corresponding metadata information from the HTML page information corresponding to the link address, and the format and content of the parsing rule are not limited as long as the parsing rule can be identified by the corresponding parsing algorithm or parsing library. In some embodiments, each metadata node in the tag template may be in the form of a key-value (key-value pair), the key may be tag attribute information (e.g., "title", "content") corresponding to the metadata node, the tag attribute information is used to indicate metadata category information corresponding to metadata information parsed according to a tag parsing rule corresponding to the key, and the value may be a parsing rule corresponding to the metadata node (e.g., "///[ @ id ═ wrapper" ]/div [1]/div [2]/h1 ","/[ @ id ═ param "]).
In step S23, the network device parses the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes a parsing result corresponding to a metadata node that is successfully parsed. In some embodiments, according to an analysis rule corresponding to each metadata node in the tag template, the HTML page information corresponding to the link address is analyzed, and an analysis result corresponding to a metadata node that is successfully analyzed is used as the metadata information corresponding to the metadata node. For example, the tag template includes a plurality of metadata nodes in the form of key-value, where the key of one metadata node is "title", and the value is "// [ @ id ═ wrapper" ]/div [1]/div [2]/h1 ", the HTML page information corresponding to the link address is analyzed according to the tag template, the metadata node is successfully analyzed, and the corresponding analysis result is" ABC ", so that" ABC "may be used as the metadata information corresponding to the metadata node, or" title: ABC "is used as the metadata information corresponding to the metadata node.
In step S24, the network device sends the one or more metadata information to the user device.
In some embodiments, the step S22 includes: and the network equipment performs domain name matching on the link address and a label template library according to a preset matching rule to obtain a label template matched with the link address. In some embodiments, the domain name matching of the link address and the tag template library may be performed according to a predetermined matching rule pre-stored on the network device, so as to determine whether the link address corresponds to a link address corresponding to a certain tag template in the tag template library and meets the predetermined matching rule.
Wherein the predetermined matching rules include, but are not limited to:
1) link address type matching
For example, the link address type corresponding to a certain tag template is a video type, and if the link address type is also a video type, it is determined that the link address matches the tag template.
2) Linked address prefix matching
For example, a tag template corresponds to a link address prefix of "www.abc.com", if the link address is"www.abc.comX/y' because the link address is "www.abc.com"start, thus determining that the link address matches the tag template.
3) Link address canonical matching
For example, the link address regular expression corresponding to a certain label template is "[ a ] (http]+ "if the link address is"http://www.abc.com", because the link address conforms to the filtering rule specified by the regular expression, the link address is determined to match the label template.
4) Linked address domain name matching
For example, if the domain name of the link address corresponding to a certain label template is "abc.com", and the link address is "mail.abc.com", because the domain name of the link address is also "abc.com", it is determined that the link address matches the label template.
5) Any combination of the above predetermined matching rules
In some embodiments, the method further comprises: if the domain name matching of the link address fails, the network equipment generates failure indication information for indicating the failure of the link address matching; and sending the failure indication information to the user equipment. In some embodiments, if the link address fails to match the domain name of the tag template library, failure indication information indicating that the link address fails to match is generated and sent to the user equipment, where the failure indication information includes, but is not limited to, the link address and a reason for the failure in matching corresponding to the link address, and the first application presents the received failure indication information to prompt the user.
In some embodiments, the method further comprises: if the link address analysis fails, the network equipment generates failure indication information for indicating the link address analysis failure; and sending the failure indication information to the user equipment. In some embodiments, if the metadata information fails to be resolved through the tag template matching the link address, failure indication information indicating that the link address fails to be resolved is generated and sent to the user equipment, where the failure indication information includes, but is not limited to, the link address and a resolution failure reason corresponding to the link address, and the first application presents the received failure indication information to prompt the user.
In some embodiments, the method further comprises: the network equipment responds to the template generation operation of the user aiming at the link address, and generates a label template matched with the link address; and updating the label template library according to the link address and the label template matched with the link address. In some embodiments, if the link address fails to match the domain name of the tag template library, or if the metadata information is failed to be resolved by the tag template matching the link address, the HTML page information corresponding to the link address may be manually resolved in a one-to-one mapping storage manner, that is, a node path, a node name, a node attribute, and the like of each metadata information and the metadata information in the HTML page information are manually determined, so as to generate a resolution rule corresponding to the metadata information, generate a tag template matching the link address, where the tag template includes tag attribute information corresponding to the metadata information and a resolution rule corresponding to the metadata information, and update or add the tag template in the tag template library.
In some embodiments, the step S21 includes: the network equipment receives the link address sent by the user equipment and the sub-area category information of each second sub-input area in the second input area of the first application; wherein the step S23 includes: and the network equipment analyzes the page information corresponding to the link address according to the label template and the sub-region category information of each second sub-input region to obtain one or more pieces of metadata information, wherein each piece of metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed, and the label attribute information corresponding to each piece of metadata information is matched with the sub-region category information of at least one second sub-input region. In some embodiments, a link address sent by a first application and sub-region category information of each input sub-region are received, one or more metadata nodes are selected from one or more metadata nodes in the tag template, corresponding tag attribute information (for example, "title") of the one or more metadata nodes is matched with sub-region category information (for example, the sub-region category information of the title input region is "title") of at least one sub-input region according to the tag template matched with the link address and the sub-region category information of each input sub-region, HTML page information corresponding to the link address is analyzed according to an analysis rule corresponding to the metadata nodes in the tag template, and an analysis result corresponding to a metadata node successfully analyzed in the metadata nodes is used as the metadata information corresponding to the link address.
Fig. 3 shows a flowchart of a method for a user equipment to publish information in an application according to an embodiment of the present application, the method includes step S31, step S32, step S33, step S34 and step S35. In step S31, the user equipment, in response to a link publishing trigger operation executed by a user in a first application of the user equipment, acquires a link address corresponding to the link publishing trigger operation; in step S32, the user equipment sends the link address to the network device corresponding to the first application; in step S33, the user device receives one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address; in step S34, the user equipment generates publishing information in the first application according to at least one of the one or more metadata information; in step S35, the user equipment publishes the publishing information through the first application.
In step S31, the user equipment acquires, in response to a link issuance trigger operation executed by the user in the first application of the user equipment, a link address corresponding to the link issuance trigger operation. In some embodiments, the link publishing trigger operation includes, but is not limited to, performing a predetermined operation (e.g., a click operation) in the first application for a certain link address, automatically pasting the link address on the system clipboard when the first application is entered or opened, and receiving the link address sent by the other application by calling a sharing interface provided by the first application.
In step S32, the user equipment sends the link address to the network device corresponding to the first application. In some embodiments, the acquired link in the first input area is sent to a network device corresponding to the first application.
In step S33, the user device receives one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address. In some embodiments, the network device parses HTML page information corresponding to the link address through an HTML parsing technique according to the received link address, obtains one or more metadata information corresponding to the link address, and sends the one or more metadata information to the user device, where the metadata information includes, but is not limited to, title information, content summary information, picture address information, and the like corresponding to the link address.
In step S34, the user equipment generates publishing information in the first application according to at least one of the one or more metadata information. In some embodiments, the user device may perform data transformation, layout, and the like on all or a portion of the one or more metadata information, transform the metadata information into published information suitable for publishing and presentation in the first application and suitable for reading by other users of the first application.
In step S35, the user equipment publishes the publishing information through the first application. In some embodiments, the generated publishing information is sent to a network device corresponding to the first application to publish the publishing message through the first application, so that other users of the first application can read the publishing message published by the user.
In some embodiments, the step S35 includes a step S351 (not shown) and a step S352 (not shown). In step S351, the user equipment presents preview information of the release information through the first application; in step S352, the user equipment issues the issue information through the first application in response to the user' S confirmation issue operation on the issue information. In some embodiments, preview information of the published message is presented in the first application, and after the preview message is read by the user, if the published message is perceived as having no problem, a publish-determining operation (for example, clicking a "publish-determining" button) may be performed on the published message, and the published message is sent to a network device corresponding to the first application, so as to publish the published message through the first application.
In some embodiments, the step S352 includes: the user equipment responds to the editing operation of the user on the release information, and presents the preview information of the edited release information through the first application; and responding to the confirmation issuing operation of the user on the edited issuing information, and issuing the edited issuing information through the first application. In some embodiments, after the user finishes reading the preview message, if the user feels that the published message has a problem, an editing operation may be performed on the published message, and then the preview information of the edited published message is presented in the first application, and after the user finishes reading the edited preview message again, if the user feels that the edited published message has no problem, a determined publishing operation (for example, clicking a "determine publishing" button) may be performed on the edited published message, and the edited published message is sent to the network device corresponding to the first application, so as to publish the edited published message through the first application.
In some embodiments, the step S34 includes: and the user equipment generates release information in the first application according to the at least one piece of metadata information and the release template information corresponding to the first application. In some embodiments, the publishing template information includes any information related to a predetermined publishing template, preferably, the publishing template information includes, but is not limited to, identification information, style information, layout information, and the like of the publishing template, optionally, a plurality of publishing templates are stored in the first application in advance, publishing template information corresponding to a default publishing template may be obtained, or publishing template information corresponding to a certain publishing template set by a user may also be obtained, and the publishing information is generated based on the obtained publishing template information.
In some embodiments, the publication template information includes a plurality of publication unit information; wherein the step S34 includes: for each piece of publishing unit information in the plurality of pieces of publishing unit information, the user equipment determines metadata information matched with the publishing unit information from the one or more pieces of metadata information according to the publishing unit information and the corresponding label attribute information of each piece of metadata information in the page information; and generating release information in the first application according to the metadata information corresponding to each piece of release unit information and the release template information. In some embodiments, a plurality of publishing units are included in the publishing template, and a plurality of publishing unit information corresponding to the plurality of publishing units are included in the publishing template information, where one piece of publishing unit information uniquely corresponds to one publishing unit and each publishing unit corresponds to a different tag attribute, and the publishing unit information includes a tag attribute corresponding to the publishing unit, and the tag attribute is used to indicate a category of the publishing content corresponding to the publishing unit, and preferably, the publishing unit information further includes identification information, style information, restriction conditions (such as word number restriction, and the like) of the publishing unit. In some embodiments, for each piece of publishing unit information, the user equipment matches the tag attribute with tag attribute information corresponding to each piece of metadata information according to the tag attribute indicated by the publishing unit information to obtain the metadata information matching with the publishing unit information, and then fills each piece of metadata information into a corresponding publishing unit in the publishing template.
Fig. 4 is a flowchart illustrating a method for a network device to publish information in an application according to an embodiment of the present application, where the method includes step S41, step S42, step S43, and step S44. In step S41, the network device receives the link address sent by the user device; in step S42, the network device performs domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes; in step S43, the network device parses the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes a parsing result corresponding to a metadata node that is successfully parsed; in step S44, the network device sends the one or more metadata information to the user device.
In step S41, the network device receives the link address sent by the user device.
In step S42, the network device performs domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes. In some embodiments, the domain name matching is performed on the link address and the tag template library, wherein the domain name matching may determine whether the link address matches a domain name of a certain tag template in the tag template library by detecting whether the link address is the same as or similar to a link address corresponding to each tag template in the tag template library, or may also determine whether the link address matches a link address corresponding to a certain tag template in the tag template library according to a predetermined matching rule by performing domain name matching on the link address and the tag template library. In some embodiments, the tag template includes one or more metadata nodes and a parsing rule corresponding to each metadata node, where the parsing rule is formulated according to a specific parsing algorithm or parsing library (e.g., XPath parsing library) for indicating how to extract corresponding metadata information from the HTML page information corresponding to the link address, and the format and content of the parsing rule are not limited as long as the parsing rule can be identified by the corresponding parsing algorithm or parsing library. In some embodiments, each metadata node in the tag template may be in the form of a key-value (key-value pair), the key may be tag attribute information (e.g., "title", "content") corresponding to the metadata node, the tag attribute information is used to indicate metadata category information corresponding to metadata information parsed according to a tag parsing rule corresponding to the key, and the value may be a parsing rule corresponding to the metadata node (e.g., "///[ @ id ═ wrapper" ]/div [1]/div [2]/h1 ","/[ @ id ═ param "]).
In step S43, the network device parses the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes a parsing result corresponding to a metadata node that is successfully parsed. In some embodiments, according to an analysis rule corresponding to each metadata node in the tag template, the HTML page information corresponding to the link address is analyzed, and an analysis result corresponding to a metadata node that is successfully analyzed is used as the metadata information corresponding to the metadata node. For example, the tag template includes a plurality of metadata nodes in the form of key-value, where the key of one metadata node is "title", and the value is "// [ @ id ═ wrapper" ]/div [1]/div [2]/h1 ", the HTML page information corresponding to the link address is analyzed according to the tag template, the metadata node is successfully analyzed, and the corresponding analysis result is" ABC ", so that" ABC "may be used as the metadata information corresponding to the metadata node, or" title: ABC "is used as the metadata information corresponding to the metadata node.
In step S44, the network device sends the one or more metadata information to the user device.
Compared with the prior art, the method and the device can realize intelligent extraction of the metadata information corresponding to the link address, so that quick information input and quick content release can be realized, and the method and the device have the advantages of automation and high efficiency; the user only needs to execute the link input operation or the link release triggering operation, so that the information can be automatically input in the application or released in the application, and the user does not need to perform any operation except the link input operation or the link release triggering operation, so that the time cost is greatly saved, great convenience can be brought to the user, and the user experience is improved.
FIG. 5 illustrates a flow diagram of a method for publishing information in an application, according to one embodiment of the present application.
As shown in fig. 5, a network device corresponding to a first application queries whether a template matching a domain name of a link address exists in a template library according to the link address, if the matching is successful, the HTML page information corresponding to the link address is analyzed according to the template matching the domain name of the link address to obtain one or more metadata information corresponding to the link address, and the metadata information is sent to a user device, the first application generates corresponding release information according to the received metadata information and generates a release page, the release information is automatically filled in the release page, if the user feels that the automatically filled release information needs to be edited, the release information can be corrected manually, and then the release information is released in the first application; if the matching fails, the failure indication information is sent to the user equipment, the first application generates an empty publishing page, the user needs to manually input various publishing contents into the publishing page, and then the publishing information is published in the first application.
FIG. 6 illustrates a flow diagram of a method for entering information in an application, according to one embodiment of the present application.
As shown in fig. 6, a network device corresponding to a first application queries whether a tag template matching a domain name of a link address exists in a massive tag template library according to the link address, if the matching is successful, the HTML page information corresponding to the link address is parsed according to the template matching the domain name of the link address, one or more pieces of metadata information corresponding to the link address are intelligently extracted, if the matching is failed or the parsing is failed, one or more pieces of metadata information corresponding to the link address are manually extracted, a parsing rule corresponding to the link address is generated, and a tag template matching the link address is generated, where the tag template includes the parsing rule corresponding to the link address, and then the tag template is updated or newly added in the massive tag template library.
FIG. 7 illustrates a flow diagram of a system method for entering information in an application, according to one embodiment of the present application.
As shown in fig. 7, in step S51, in response to a link input operation performed by the user in the first input area of the first application, the user equipment obtains a link address corresponding to the link input operation, where step S51 is the same as or similar to step S11, and is not repeated here; in step S52, the ue sends the link address to the network device corresponding to the first application, and step S52 is the same as or similar to step S12, which is not described herein again; in step S53, the network device receives the link address sent by the user equipment, and step S53 is the same as or similar to step S21, which is not described herein again; in step S54, the network device performs domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes, and step S54 is the same as or similar to step S22, and is not described herein again; in step S55, the network device analyzes the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes an analysis result corresponding to a metadata node that is successfully analyzed, and step S55 is the same as or similar to step S23, and is not repeated here; in step S56, the network device sends the one or more pieces of metadata information to the user equipment, where step S56 is the same as or similar to step S24, and is not described herein again; in step S57, the user equipment receives one or more metadata information returned by the network equipment based on the link address, where each metadata information is taken from the page information corresponding to the link address, and step S57 is the same as or similar to step S13, and is not described herein again; in step S58, the user equipment inputs at least one of the one or more metadata information into the second input area of the first application, and step S58 is the same as or similar to step S14, which is not repeated herein.
FIG. 8 illustrates a flow diagram of a system method for publishing information in an application, according to one embodiment of the present application.
As shown in fig. 8, in step S61, the user equipment obtains a link address corresponding to a link publishing trigger operation in response to the link publishing trigger operation executed by the user in the first application of the user equipment, where step S61 is the same as or similar to step S31, and is not repeated herein; in step S62, the ue sends the link address to the network device corresponding to the first application, and step S62 is the same as or similar to step S32, which is not described herein again; in step S63, the network device receives the link address sent by the user equipment, and step S63 is the same as or similar to step S41, which is not described herein again; in step S64, the network device performs domain name matching on the link address and a tag template library according to the link address to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes, and step S64 is the same as or similar to step S42, and is not described herein again; in step S65, the network device analyzes the page information corresponding to the link address according to the tag template to obtain one or more metadata information, where each metadata information includes an analysis result corresponding to a metadata node that is successfully analyzed, and step S65 is the same as or similar to step S43, and is not repeated here; in step S66, the network device sends the one or more pieces of metadata information to the user equipment, where step S66 is the same as or similar to step S44, and is not described herein again; in step S67, the user equipment receives one or more metadata information returned by the network equipment based on the link address, where each metadata information is taken from the page information corresponding to the link address, and step S67 is the same as or similar to step S33, and is not described herein again; in step S68, the user equipment generates release information in the first application according to at least one piece of metadata information in the one or more pieces of metadata information, where step S68 is the same as or similar to step S34, and is not repeated herein; in step S69, the ue issues the release information through the first application, and step S69 is the same as or similar to step S35, which is not described herein again.
Fig. 9 shows a user equipment for inputting information in an application according to an embodiment of the present application, the equipment comprising a one-module 11, a two-module 12, a three-module 13 and a four-module 14. A one-to-one module 11, configured to respond to a link input operation performed by a user in a first input area of a first application, and obtain a link address corresponding to the link input operation; a second module 12, configured to send the link address to a network device corresponding to the first application; a third module 13, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address; a fourth module 14, configured to input at least one metadata information of the one or more metadata information into a second input area of the first application.
A module 11, configured to, in response to a link input operation performed by a user in a first input area of a first application, obtain a link address corresponding to the link input operation. In some embodiments, the link input operation includes, but is not limited to, manually entering a link address in the first input area, and manually pasting the link address on the system clipboard in the first input area.
A second module 12, configured to send the link address to a network device corresponding to the first application. In some embodiments, the acquired link in the first input area is sent to a network device corresponding to the first application.
A module 13, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address. In some embodiments, the network device parses HTML page information corresponding to the link address through an HTML parsing technique according to the received link address, obtains one or more metadata information corresponding to the link address, and sends the one or more metadata information to the user device, where the metadata information includes, but is not limited to, title information, content summary information, picture address information, and the like corresponding to the link address.
A fourth module 14, configured to input at least one metadata information of the one or more metadata information into a second input area of the first application. In some embodiments, all or part of the content of one or more metadata information may be input into the second input area of the first application, or part of the metadata information may be determined from one or more metadata information and all or part of the content of part of the metadata information may be input into the second input area of the first application, where the first input area and the second input area may be two independent input areas in the first application or two independent sub-input areas of the same input area in the first application.
In some embodiments, the one-four module 14 is configured to: and inputting the at least one piece of metadata information into a second input area of the first application according to the corresponding label attribute information of each piece of metadata information in the page information. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
In some embodiments, the second input region comprises one or more second sub-input regions; the four modules 14 are configured to: and according to the tag attribute information corresponding to each metadata information in the page information, determining the metadata information corresponding to each second sub-input area in the second input area from the one or more metadata information, and inputting the metadata information into the second sub-input area, wherein the tag attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
In some embodiments, the one-four module 14 is configured to: for each second sub-input area in the second input area, obtaining sub-area category information of the second sub-input area, matching the sub-area category information with tag attribute information corresponding to metadata information in the one or more metadata information in the page information, obtaining metadata information matched with the sub-area category information, and inputting the metadata information into the second sub-input area. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
In some embodiments, the apparatus is further configured to: and responding to the editing operation of the user on the second input area, and obtaining at least one edited metadata information. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
In some embodiments, the apparatus is further configured to: receiving failure indication information returned by the network equipment based on the link address, wherein the failure indication information is used for indicating that the link address fails to be matched or failed to be analyzed; presenting the failure indication information in the first application. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
In some embodiments, the second input area of the first application comprises one or more second sub-input areas; wherein the second module 12 is configured to: sending the link address and the sub-region category information of each second sub-input region in the second input region to the network device corresponding to the first application; the four modules 14 are configured to: and inputting at least one of the one or more metadata information into a corresponding second sub-area in a second input area of the first application, wherein the tag attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.
Fig. 10 shows a network device for inputting information in an application according to an embodiment of the present application, the device includes a two-to-one module 21, a two-to-two module 22, a two-to-three module 23, and a two-to-four module 24. A second-first module 21, configured to receive a link address sent by a user equipment; a second module 22, configured to perform domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes; a second and third module 23, configured to analyze, according to the tag template, page information corresponding to the link address to obtain one or more metadata information, where each metadata information includes an analysis result corresponding to a metadata node that is successfully analyzed; a twenty-four module 24, configured to send the one or more metadata information to the user equipment.
And a module 21, configured to receive the link address sent by the user equipment.
A second module 22, configured to perform domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes. In some embodiments, the domain name matching is performed on the link address and the tag template library, wherein the domain name matching may determine whether the link address matches a domain name of a certain tag template in the tag template library by detecting whether the link address is the same as or similar to a link address corresponding to each tag template in the tag template library, or may also determine whether the link address matches a link address corresponding to a certain tag template in the tag template library according to a predetermined matching rule by performing domain name matching on the link address and the tag template library. In some embodiments, the tag template includes one or more metadata nodes and a parsing rule corresponding to each metadata node, where the parsing rule is formulated according to a specific parsing algorithm or parsing library (e.g., XPath parsing library) for indicating how to extract corresponding metadata information from the HTML page information corresponding to the link address, and the format and content of the parsing rule are not limited as long as the parsing rule can be identified by the corresponding parsing algorithm or parsing library. In some embodiments, each metadata node in the tag template may be in the form of a key-value (key-value pair), the key may be tag attribute information (e.g., "title", "content") corresponding to the metadata node, the tag attribute information is used to indicate metadata category information corresponding to metadata information parsed according to a tag parsing rule corresponding to the key, and the value may be a parsing rule corresponding to the metadata node (e.g., "///[ @ id ═ wrapper" ]/div [1]/div [2]/h1 ","/[ @ id ═ param "]).
And a third module 23, configured to parse, according to the tag template, the page information corresponding to the link address to obtain one or more metadata information, where each metadata information includes a parsing result corresponding to a metadata node that is successfully parsed. In some embodiments, according to an analysis rule corresponding to each metadata node in the tag template, the HTML page information corresponding to the link address is analyzed, and an analysis result corresponding to a metadata node that is successfully analyzed is used as the metadata information corresponding to the metadata node. For example, the tag template includes a plurality of metadata nodes in the form of key-value, where the key of one metadata node is "title", and the value is "// [ @ id ═ wrapper" ]/div [1]/div [2]/h1 ", the HTML page information corresponding to the link address is analyzed according to the tag template, the metadata node is successfully analyzed, and the corresponding analysis result is" ABC ", so that" ABC "may be used as the metadata information corresponding to the metadata node, or" title: ABC "is used as the metadata information corresponding to the metadata node.
A twenty-four module 24, configured to send the one or more metadata information to the user equipment.
In some embodiments, the two modules 22 are configured to: and according to a preset matching rule, performing domain name matching on the link address and a label template library to obtain a label template matched with the link address. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 2, and therefore are not described again, and are included herein by reference.
Wherein the predetermined matching rules include, but are not limited to:
1) link address type matching
2) Linked address prefix matching
3) Link address canonical matching
4) Linked address domain name matching
5) Any combination of the above predetermined matching rules
Here, the related predetermined matching rule is the same as or similar to the embodiment shown in fig. 2, and therefore, the description thereof is omitted, and the related predetermined matching rule is incorporated herein by reference.
In some embodiments, the apparatus is further configured to: if the domain name matching of the link address fails, generating failure indication information for indicating the failure of the link address matching; and sending the failure indication information to the user equipment. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 2, and therefore are not described again, and are included herein by reference.
In some embodiments, the apparatus is further configured to: if the link address analysis fails, generating failure indication information for indicating the link address analysis fails; and sending the failure indication information to the user equipment. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 2, and therefore are not described again, and are included herein by reference.
In some embodiments, the apparatus is further configured to: responding to a template generating operation of a user aiming at the link address, and generating a label template matched with the link address; and updating the label template library according to the link address and the label template matched with the link address. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 2, and therefore are not described again, and are included herein by reference.
In some embodiments, the two-in-one module 21 is configured to: receiving a link address sent by user equipment and sub-region category information of each second sub-input region in a second input region of the first application; wherein the two and three modules 23 are configured to: and analyzing the page information corresponding to the link address according to the tag template and the sub-region category information of each second sub-input region to obtain one or more pieces of metadata information, wherein each piece of metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed, and the tag attribute information corresponding to each piece of metadata information is matched with the sub-region category information of at least one second sub-input region. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 2, and therefore are not described again, and are included herein by reference.
Fig. 11 shows a user equipment for publishing information in an application according to an embodiment of the present application, the device comprising a three-in-one module 31, a three-in-two module 32, a three-in-three module 33, a three-in-four module 34 and a three-in-five module 35. A third-to-first module 31, configured to respond to a link publishing trigger operation executed by a user in a first application of user equipment, and acquire a link address corresponding to the link publishing trigger operation; a third-second module 32, configured to send the link address to a network device corresponding to the first application; a triplex module 33, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from page information corresponding to the link address; a thirty-four module 34, configured to generate release information in the first application according to at least one piece of metadata information in the one or more pieces of metadata information; a thirty-five module 35, configured to publish the publishing information through the first application.
A third-to-first module 31, configured to, in response to a link publishing trigger operation executed by a user in a first application of user equipment, obtain a link address corresponding to the link publishing trigger operation. In some embodiments, the link publishing trigger operation includes, but is not limited to, performing a predetermined operation (e.g., a click operation) in the first application for a certain link address, automatically pasting the link address on the system clipboard when the first application is entered or opened, and receiving the link address sent by the other application by calling a sharing interface provided by the first application.
A third and second module 32, configured to send the link address to a network device corresponding to the first application. In some embodiments, the acquired link in the first input area is sent to a network device corresponding to the first application.
A triplex module 33, configured to receive one or more pieces of metadata information returned by the network device based on the link address, where each piece of metadata information is taken from the page information corresponding to the link address. In some embodiments, the network device parses HTML page information corresponding to the link address through an HTML parsing technique according to the received link address, obtains one or more metadata information corresponding to the link address, and sends the one or more metadata information to the user device, where the metadata information includes, but is not limited to, title information, content summary information, picture address information, and the like corresponding to the link address.
A thirty-four module 34, configured to generate the publishing information in the first application according to at least one metadata information of the one or more metadata information. In some embodiments, the user device may perform data transformation, layout, and the like on all or a portion of the one or more metadata information, transform the metadata information into published information suitable for publishing and presentation in the first application and suitable for reading by other users of the first application.
A thirty-five module 35, configured to publish the publishing information through the first application. In some embodiments, the generated publishing information is sent to a network device corresponding to the first application to publish the publishing message through the first application, so that other users of the first application can read the publishing message published by the user.
In some embodiments, the thirty-five module 35 includes a thirty-five module 351 (not shown) and step S352 (not shown). A thirty-five-one module 351, configured to present preview information of the release information through the first application; a thirty-five-two module 352, configured to respond to a confirmation issue operation of the user on the issue information, and issue the issue information through the first application. Here, the specific implementation of the thirty-five-one module 351 and the thirty-five-two module 352 is the same as or similar to the embodiment of the steps S351 and S352 in fig. 3, and therefore, the detailed description thereof is omitted, and the detailed description thereof is incorporated herein by reference.
In some embodiments, the thirty-five-two module 352 is to: responding to the editing operation of the user on the release information, and presenting preview information of the edited release information through the first application; and responding to the confirmation issuing operation of the user on the edited issuing information, and issuing the edited issuing information through the first application. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 3, and therefore are not described again, and are included herein by reference.
In some embodiments, the thirty-four module 34 is configured to: and generating release information in the first application according to the at least one piece of metadata information and release template information corresponding to the first application. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 3, and therefore are not described again, and are included herein by reference.
In some embodiments, the publication template information includes a plurality of publication unit information; wherein the three-four module 34 is configured to: for each piece of publishing unit information in the plurality of pieces of publishing unit information, determining metadata information matched with the publishing unit information from the one or more pieces of metadata information according to the corresponding tag attribute information of the publishing unit information and the metadata information in the page information; and generating release information in the first application according to the metadata information corresponding to each piece of release unit information and the release template information. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 3, and therefore are not described again, and are included herein by reference.
Fig. 12 shows a network device for publishing information in an application, according to an embodiment of the present application, the device including a quad one module 41, a quad two module 42, a quad three module 43, and a quad four module 44. A fourth module 41, configured to receive a link address sent by a user equipment; a fourth-second module 42, configured to perform domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes; a fourth and third module 43, configured to analyze, according to the tag template, page information corresponding to the link address to obtain one or more pieces of metadata information, where each piece of metadata information includes an analysis result corresponding to one metadata node that is successfully analyzed; a fourteen module 44, configured to send the one or more metadata information to the user equipment.
A fourth module 41, configured to receive the link address sent by the user equipment.
A fourth and second module 42, configured to perform domain name matching on the link address and a tag template library to obtain a tag template matched with the link address, where the tag template includes one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes. In some embodiments, the domain name matching is performed on the link address and the tag template library, wherein the domain name matching may determine whether the link address matches a domain name of a certain tag template in the tag template library by detecting whether the link address is the same as or similar to a link address corresponding to each tag template in the tag template library, or may also determine whether the link address matches a link address corresponding to a certain tag template in the tag template library according to a predetermined matching rule by performing domain name matching on the link address and the tag template library. In some embodiments, the tag template includes one or more metadata nodes and a parsing rule corresponding to each metadata node, where the parsing rule is formulated according to a specific parsing algorithm or parsing library (e.g., XPath parsing library) for indicating how to extract corresponding metadata information from the HTML page information corresponding to the link address, and the format and content of the parsing rule are not limited as long as the parsing rule can be identified by the corresponding parsing algorithm or parsing library. In some embodiments, each metadata node in the tag template may be in the form of a key-value (key-value pair), the key may be tag attribute information (e.g., "title", "content") corresponding to the metadata node, the tag attribute information is used to indicate metadata category information corresponding to metadata information parsed according to a tag parsing rule corresponding to the key, and the value may be a parsing rule corresponding to the metadata node (e.g., "///[ @ id ═ wrapper" ]/div [1]/div [2]/h1 ","/[ @ id ═ param "]).
A fourth and third module 43, configured to analyze, according to the tag template, the page information corresponding to the link address to obtain one or more metadata information, where each metadata information includes an analysis result corresponding to one metadata node that is successfully analyzed. In some embodiments, according to an analysis rule corresponding to each metadata node in the tag template, the HTML page information corresponding to the link address is analyzed, and an analysis result corresponding to a metadata node that is successfully analyzed is used as the metadata information corresponding to the metadata node. For example, the tag template includes a plurality of metadata nodes in the form of key-value, where the key of one metadata node is "title", and the value is "// [ @ id ═ wrapper" ]/div [1]/div [2]/h1 ", the HTML page information corresponding to the link address is analyzed according to the tag template, the metadata node is successfully analyzed, and the corresponding analysis result is" ABC ", so that" ABC "may be used as the metadata information corresponding to the metadata node, or" title: ABC "is used as the metadata information corresponding to the metadata node.
A fourteen module 44, configured to send the one or more metadata information to the user equipment.
FIG. 13 illustrates an exemplary system that can be used to implement the various embodiments described in this application.
In some embodiments, as shown in FIG. 13, the system 300 can be implemented as any of the devices in the various embodiments described. In some embodiments, system 300 may include one or more computer-readable media (e.g., system memory or NVM/storage 320) having instructions and one or more processors (e.g., processor(s) 305) coupled with the one or more computer-readable media and configured to execute the instructions to implement modules to perform the actions described herein.
For one embodiment, system control module 310 may include any suitable interface controllers 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.
The system control module 310 may include a memory controller module 330 to provide an interface to the system memory 315. Memory controller module 330 may be a hardware module, a software module, and/or a firmware module.
System memory 315 may be used, for example, to load and store data and/or instructions for system 300. For one embodiment, system memory 315 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, the system memory 315 may include a double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).
For one embodiment, system control module 310 may include one or more input/output (I/O) controllers to provide an interface to NVM/storage 320 and communication interface(s) 325.
For example, NVM/storage 320 may be used to store data and/or instructions. NVM/storage 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 Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives).
NVM/storage 320 may include storage resources that are physically part of the device on which system 300 is installed or may be accessed by the device and not necessarily part of the device. For example, NVM/storage 320 may be accessible over a network via communication interface(s) 325.
Communication interface(s) 325 may provide an interface for system 300 to communicate over one or more networks and/or with any other suitable device. System 300 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols.
For one embodiment, at least one of the processor(s) 305 may be packaged together with logic for one or more controller(s) (e.g., memory controller module 330) of the system control module 310. For one embodiment, at least one of the processor(s) 305 may be packaged together with logic for one or more controller(s) 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 logic for one or more controller(s) 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 logic for one or more controller(s) of the system control module 310 to form a system on a chip (SoC).
In various embodiments, system 300 may be, but is not limited to being: a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a holding computing device, a tablet, a netbook, etc.). In various embodiments, system 300 may have more or fewer components and/or different architectures. For example, in some embodiments, 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 speakers.
The present application also provides a computer readable storage medium having stored thereon computer code which, when executed, performs a method as in any one of the preceding.
The present application also provides a computer program product, which when executed by a computer device, performs the method of any of the preceding claims.
The present application further provides a computer device, comprising:
one or more processors;
a memory for storing one or more computer programs;
the one or more computer programs, when executed by the one or more processors, cause the one or more processors to implement the method of any preceding claim.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Those skilled in the art will appreciate that the form in which the computer program instructions reside on a computer-readable medium includes, but is not limited to, source files, executable files, installation package files, and the like, and that the manner in which the 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. Computer-readable media herein can be any available computer-readable storage media or communication media that can be accessed by a computer.
Communication media includes media by which communication signals, including, for example, computer readable instructions, data structures, program modules, or other data, are transmitted from one system to another. Communication media may include conductive transmission media such as cables and wires (e.g., fiber optics, coaxial, etc.) and wireless (non-conductive transmission) media capable of propagating energy waves such as acoustic, electromagnetic, RF, microwave, and infrared. Computer readable instructions, data structures, program modules, or other data may be embodied in a modulated data signal, for example, in a wireless medium such as a carrier wave or similar mechanism such as is embodied as part of spread spectrum techniques. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The modulation may be analog, digital or hybrid modulation techniques.
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 disk, tape, CD, DVD); or other now known media or later developed that can store computer-readable information/data for use by a computer system.
One embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions are executed by the processor when the computer program instructions are executed
When the device is triggered to operate, the method and/or the technical scheme based on the plurality of the embodiments of the application are/is triggered.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.

Claims (19)

1. A method for inputting information in an application, applied to a user equipment, wherein the method comprises the following steps:
responding to a link input operation executed by a user in a first input area of a first application, and acquiring a link address corresponding to the link input operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
inputting at least one of the one or more metadata information into a second input area of the first application.
2. The method of claim 1, wherein said entering at least one of the one or more metadata information into a second input area of the first application comprises:
and inputting the at least one piece of metadata information into a second input area of the first application according to the corresponding label attribute information of each piece of metadata information in the page information.
3. The method of claim 2, wherein the second input region comprises one or more second sub-input regions;
the entering at least one of the one or more metadata information into a second input area of the first application comprises:
and according to the tag attribute information corresponding to each metadata information in the page information, determining the metadata information corresponding to each second sub-input area in the second input area from the one or more metadata information, and inputting the metadata information into the second sub-input area, wherein the tag attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area.
4. The method of claim 3, wherein said entering at least one of the one or more metadata information into a second input area of the first application comprises:
for each second sub-input area in the second input area, obtaining sub-area category information of the second sub-input area, matching the sub-area category information with tag attribute information corresponding to metadata information in the one or more metadata information in the page information, obtaining metadata information matched with the sub-area category information, and inputting the metadata information into the second sub-input area.
5. The method of any of claims 1-4, wherein the method further comprises:
and responding to the editing operation of the user on the second input area, and obtaining at least one edited metadata information.
6. The method of claim 1 or 5, wherein the second input area of the first application comprises one or more second sub-input areas;
wherein the sending the link address to the network device corresponding to the first application includes:
sending the link address and the sub-region category information of each second sub-input region in the second input region to the network device corresponding to the first application;
the entering at least one of the one or more metadata information into a second input area of the first application comprises:
and inputting at least one of the one or more metadata information into a corresponding second sub-area in a second input area of the first application, wherein the tag attribute information corresponding to the metadata information is matched with the sub-area category information of the second sub-input area.
7. A method for inputting information in an application, applied to a network device, wherein the method comprises the following steps:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes;
analyzing page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
8. The method of claim 7, wherein the domain name matching the link address with a tag template library to obtain a tag template matching the link address, wherein the tag template comprises one or more metadata nodes and resolution rules corresponding to the one or more metadata nodes, and comprises:
according to a preset matching rule, performing domain name matching on the link address and a label template library to obtain a label template matched with the link address;
wherein the predetermined matching rule comprises at least one of:
the link address types are matched;
link address prefix matching;
link address regular matching;
the link address domain names match.
9. The method according to claim 7 or 8, wherein if the link address domain name matching fails or the resolution fails;
wherein the method further comprises:
responding to a template generating operation of a user aiming at the link address, and generating a label template matched with the link address;
and updating the label template library according to the link address and the label template matched with the link address.
10. The method according to any one of claims 7 to 9, wherein the receiving the link address sent by the user equipment comprises:
receiving a link address sent by user equipment and sub-region category information of each second sub-input region in a second input region of the first application;
analyzing the page information corresponding to the link address according to the tag template to obtain one or more pieces of metadata information, wherein each piece of metadata information includes an analysis result corresponding to a metadata node that is successfully analyzed, and the analyzing includes:
and analyzing the page information corresponding to the link address according to the tag template and the sub-region category information of each second sub-input region to obtain one or more pieces of metadata information, wherein each piece of metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed, and the tag attribute information corresponding to each piece of metadata information is matched with the sub-region category information of at least one second sub-input region.
11. A method for publishing information in an application, applied to user equipment, wherein the method comprises the following steps:
responding to a link publishing trigger operation executed in a first application of user equipment by a user, and acquiring a link address corresponding to the link publishing trigger operation;
sending the link address to a network device corresponding to the first application;
receiving one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
generating release information in the first application according to at least one of the one or more pieces of metadata information;
and issuing the issuing information through the first application.
12. The method of claim 11, wherein said publishing the publication information by the first application comprises:
presenting preview information of the release information through the first application;
and responding to the confirmation issuing operation of the user on the issuing information, and issuing the issuing information through the first application.
13. The method of claim 12, wherein said publishing the published information by the first application in response to the user confirming the publishing operation of the published information comprises:
responding to the editing operation of the user on the release information, and presenting preview information of the edited release information through the first application;
and responding to the confirmation issuing operation of the user on the edited issuing information, and issuing the edited issuing information through the first application.
14. A method for publishing information in an application, applied to a network device, wherein the method comprises:
receiving a link address sent by user equipment;
performing domain name matching on the link address and a label template library according to the link address to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
analyzing page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed;
sending the one or more metadata information to the user equipment.
15. A method of inputting information in an application, wherein the method comprises:
the method comprises the steps that user equipment responds to a link input operation executed by a user in a first input area of a first application, and a link address corresponding to the link input operation is obtained;
the user equipment sends the link address to network equipment corresponding to the first application;
the network equipment receives a link address sent by the user equipment;
the network equipment carries out domain name matching on the link address and a label template library to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
the network equipment analyzes the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed;
the network device sends the one or more metadata information to the user device;
the user equipment receives one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
the user device enters at least one of the one or more metadata information into a second input area of the first application.
16. A method of publishing information in an application, wherein the method comprises:
the method comprises the steps that user equipment responds to a link release triggering operation executed by a user in a first application of the user equipment, and a link address corresponding to the link release triggering operation is obtained;
the user equipment sends the link address to network equipment corresponding to the first application;
the network equipment receives a link address sent by the user equipment;
the network equipment carries out domain name matching on the link address and a label template library according to the link address to obtain a label template matched with the link address, wherein the label template comprises one or more metadata nodes and an analysis rule corresponding to the one or more metadata nodes;
the network equipment analyzes the page information corresponding to the link address according to the tag template to obtain one or more metadata information, wherein each metadata information comprises an analysis result corresponding to one metadata node which is successfully analyzed;
the network device sends the one or more metadata information to the user device;
the user equipment receives one or more pieces of metadata information returned by the network equipment based on the link address, wherein each piece of metadata information is taken from page information corresponding to the link address;
the user equipment generates release information in the first application according to at least one piece of metadata information in the one or more pieces of metadata information;
and the user equipment publishes the publishing information through the first application.
17. An apparatus for inputting information in an application, wherein the apparatus comprises:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the operations of the method of any of claims 1 to 10.
18. A computer-readable medium storing instructions that, when executed, cause a system to perform the operations of any of the methods of claims 1-14.
19. An apparatus for publishing information in an application, wherein the apparatus comprises:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the operations of the method of any of claims 11 to 14.
CN201911061657.8A 2019-11-01 2019-11-01 Method and equipment for inputting information in application Pending CN111125565A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911061657.8A CN111125565A (en) 2019-11-01 2019-11-01 Method and equipment for inputting information in application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911061657.8A CN111125565A (en) 2019-11-01 2019-11-01 Method and equipment for inputting information in application

Publications (1)

Publication Number Publication Date
CN111125565A true CN111125565A (en) 2020-05-08

Family

ID=70496119

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911061657.8A Pending CN111125565A (en) 2019-11-01 2019-11-01 Method and equipment for inputting information in application

Country Status (1)

Country Link
CN (1) CN111125565A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113297827A (en) * 2021-02-08 2021-08-24 上海连尚网络科技有限公司 Method and equipment for presenting content information

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247494A (en) * 2007-01-05 2008-08-20 索尼株式会社 Information processing apparatus and method, and program
CN101655844A (en) * 2008-08-19 2010-02-24 联想(北京)有限公司 Device, method and equipment for information data interaction for processing information data
CN101916285A (en) * 2010-08-20 2010-12-15 北京新岸线网络技术有限公司 Method and device for analyzing internet web page contents
CN101950312A (en) * 2010-08-18 2011-01-19 赵清政 Method for analyzing webpage content of internet
CN101957816A (en) * 2009-07-13 2011-01-26 上海谐宇网络科技有限公司 Webpage metadata automatic extraction method and system based on multi-page comparison
CN102087653A (en) * 2009-12-08 2011-06-08 阿里巴巴集团控股有限公司 Method and device for issuing website information
CN102567532A (en) * 2011-12-30 2012-07-11 奇智软件（北京）有限公司 Information distribution method and information distribution device
CN103544320A (en) * 2013-11-05 2014-01-29 从兴技术有限公司 Webpage generation method and device
CN104516892A (en) * 2013-09-26 2015-04-15 腾讯科技（北京）有限公司 Distribution method, system and terminal of user generated content associated with rich media information
CN110020236A (en) * 2017-08-29 2019-07-16 北京国双科技有限公司 Web analysis method, apparatus, storage medium, processor and equipment

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247494A (en) * 2007-01-05 2008-08-20 索尼株式会社 Information processing apparatus and method, and program
CN101655844A (en) * 2008-08-19 2010-02-24 联想(北京)有限公司 Device, method and equipment for information data interaction for processing information data
CN101957816A (en) * 2009-07-13 2011-01-26 上海谐宇网络科技有限公司 Webpage metadata automatic extraction method and system based on multi-page comparison
CN102087653A (en) * 2009-12-08 2011-06-08 阿里巴巴集团控股有限公司 Method and device for issuing website information
CN101950312A (en) * 2010-08-18 2011-01-19 赵清政 Method for analyzing webpage content of internet
CN101916285A (en) * 2010-08-20 2010-12-15 北京新岸线网络技术有限公司 Method and device for analyzing internet web page contents
CN102567532A (en) * 2011-12-30 2012-07-11 奇智软件（北京）有限公司 Information distribution method and information distribution device
CN104516892A (en) * 2013-09-26 2015-04-15 腾讯科技（北京）有限公司 Distribution method, system and terminal of user generated content associated with rich media information
CN103544320A (en) * 2013-11-05 2014-01-29 从兴技术有限公司 Webpage generation method and device
CN110020236A (en) * 2017-08-29 2019-07-16 北京国双科技有限公司 Web analysis method, apparatus, storage medium, processor and equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113297827A (en) * 2021-02-08 2021-08-24 上海连尚网络科技有限公司 Method and equipment for presenting content information

Similar Documents

Publication Publication Date Title
CN108958780B (en) Method and equipment for presenting update information of hosted program
CN111026470B (en) System and method for verification and conversion of input data
CN109062563B (en) Method and device for generating page
CN109359237B (en) Method and equipment for searching hosted program
CN112241506B (en) User behavior backtracking method, device, equipment and system
CN106610774B (en) Webpage table editing method and device
CN104423961A (en) Method and system for generating testing script
US8959426B1 (en) Loading customer-supplied network page generation code
CN113495797A (en) Message queue and consumer dynamic creation method and system
CN110968314A (en) Page generation method and device
CN110519250B (en) Method and equipment for providing information flow
WO2023092580A1 (en) Page display method and apparatus, storage medium, and electronic device
CN111796741B (en) Method and equipment for providing recommended books
CN111125565A (en) Method and equipment for inputting information in application
CN107291524B (en) Remote command processing method and device
CN110941437A (en) Method and equipment for installing application
US9690753B1 (en) Caching of a site model in a hierarchical modeling system for network sites
CN112256991B (en) Method and equipment for native rendering of information flow fusing multiple link addresses
CN115309657A (en) Method, device, medium and program product for providing test case
CN111651160B (en) Plug-in construction and webpage design method and device
CN115080154A (en) Page display method and device, storage medium and electronic equipment
CN112256992A (en) Native rendering method and device for information stream fusing multi-link addresses
CN111078654A (en) Method and equipment for sharing information
CN111079038B (en) Method and equipment for inputting information in application
US11960560B1 (en) Methods for analyzing recurring accessibility issues with dynamic web site behavior and devices thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination