Information sharing method and device

Abstract

The present application discloses an information sharing method and device, which relates to the field of computer technology. A specific implementation method includes receiving an information sharing request, obtaining sharing parameters in the information sharing request; calling a preset service interface, generating a service page based on the sharing parameters; calling a sharing plug-in, grabbing the service page, generating a card link; and sharing the card link. Therefore, this implementation method can achieve that when different projects access the sharing plug-in, there is no need to configure the information required by the sharing plug-in multiple times, thereby streamlining the sharing process.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an information sharing method and device. Background Art

[0002] In actual development, sharing different projects requires the introduction of multiple social plug-ins. Developers need to repeatedly configure page tags for different social plug-ins to crawl on each project page, and then share them for different social plug-ins to crawl.

[0003] In the process of implementing this application, the inventors found that there are at least the following problems in the prior art:

[0004] Connecting different social plug-ins to different projects requires multiple configurations, which is a cumbersome process. Summary of the invention

[0005] In view of this, the embodiments of the present application provide an information sharing method and device, which can solve the problem that the existing different projects need to be connected to different social plug-ins, which requires multiple configurations and a cumbersome process.

[0006] To achieve the above objective, according to one aspect of an embodiment of the present application, there is provided an information sharing method, comprising:

[0007] Receive an information sharing request and obtain sharing parameters in the information sharing request;

[0008] Call the preset service interface and generate a service page based on the shared parameters;

[0009] Call the sharing plug-in, crawl the service page, and generate a card link;

[0010] Share the card link.

[0011] Optionally, generate a service page, including:

[0012] Call the preset service interface, map the sharing parameters to the page, and generate an HTML page that complies with the sharing plug-in to capture the open graph tags.

[0013] Optionally, generate a card link, including:

[0014] Get the service address of the service page and extract the sharing parameter value;

[0015] Call the sharing plug-in to fetch the corresponding open graph tag from the service page based on the sharing parameter value and generate a card link.

[0016] Optionally, share a link to the card, including:

[0017] Get the sharing channel ID in the information sharing request;

[0018] Based on the sharing channel identifier, determine the sharing channel;

[0019] Share cards link to sharing channels.

[0020] Optionally, the information sharing method further includes:

[0021] Receive a card link access request, jump to the service page, obtain the source link address, generate a corresponding jump code based on a preset automatic refresh frequency, and then execute the jump code to jump to the page corresponding to the source link address.

[0022] In addition, the present application also provides an information sharing device, including:

[0023] A receiving unit, configured to receive an information sharing request and obtain sharing parameters in the information sharing request;

[0024] A service page generating unit is configured to call a preset service interface and generate a service page based on the sharing parameters;

[0025] The card link generation unit is configured to call the sharing plug-in, crawl the service page, and generate a card link;

[0026] The sharing unit is configured to share a card link.

[0027] Optionally, the service page generating unit is further configured to:

[0028] Call the preset service interface, map the sharing parameters to the page, and generate an HTML page that complies with the sharing plug-in to capture the open graph tags.

[0029] Optionally, the card link generation unit is further configured to:

[0030] Get the service address of the service page and extract the sharing parameter value;

[0031] Call the sharing plug-in to fetch the corresponding open graph tag from the service page based on the sharing parameter value and generate a card link.

[0032] Optionally, the sharing unit is further configured to:

[0033] Get the sharing channel ID in the information sharing request;

[0034] Based on the sharing channel identifier, determine the sharing channel;

[0035] Share cards link to sharing channels.

[0036] Optionally, the information sharing device further includes an access unit configured to:

[0037] Receive a card link access request, jump to the service page, obtain the source link address, generate a corresponding jump code based on a preset automatic refresh frequency, and then execute the jump code to jump to the page corresponding to the source link address.

[0038] In addition, the present application also provides an information sharing electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the information sharing method as described above.

[0039] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned information sharing method is implemented.

[0040] One embodiment of the above invention has the following advantages or beneficial effects: This application generates a service page for different sharing plug-ins to capture based on the sharing parameters in the received information sharing request, so that when different projects access the sharing plug-in, there is no need to configure the information required by the sharing plug-in multiple times, thereby streamlining the sharing process. And by directly calling a sharing plug-in that is compatible with multiple sharing channels and capturing the generated service page, a card link can be quickly generated and shared. In addition, when it is necessary to modify the style or content of the shared card, the corresponding service page can be generated by uniformly modifying the sharing parameters once, without the need to modify them one by one, thereby reducing the workload and improving the sharing efficiency. In addition, when the sharing plug-in captures the content of the service page, it captures the content that can directly generate the card link, rather than the link domain name of the source page, so that the required card link can be generated more simply and conveniently, thereby improving the user experience.

[0041] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with specific implementation examples. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.

[0043] Figure 1 is a schematic diagram of the main process of the information sharing method according to the first embodiment of the present application;

[0044] Figure 2 is a schematic diagram of the main process of the information sharing method according to the second embodiment of the present application;

[0045] Figure 3 is a schematic diagram of an application scenario of the information sharing method according to the third embodiment of the present application;

[0046] Figure 4 is a schematic diagram of main modules of an information sharing device according to an embodiment of the present application;

[0047] Figure 5 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;

[0048] Figure 6 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0050] Figure 1 is a schematic diagram of the main process of the information sharing method according to the first embodiment of the present application, such as Figure 1 As shown, information sharing methods include:

[0051] Step S101: receiving an information sharing request and obtaining sharing parameters in the information sharing request.

[0052] In this embodiment, the execution subject of the information sharing method (for example, a server or a processor) can receive an information sharing request initiated by a user through a terminal device, such as a smart phone, a tablet computer, a laptop computer, a desktop computer, etc., through a wired connection or a wireless connection. For example, when a user opens a shopping software on a smart phone, when the user wants to share one or more shopping pages browsed with an instant messaging software installed on a smart phone of a family member or friend, the page sharing process can be triggered by clicking the sharing control on the current page, and then the information sharing request corresponding to the page to be shared is sent to the execution subject. The execution subject can obtain the sharing parameters in the information sharing request. Specifically, the sharing parameters may include but are not limited to the sharing title tit, sharing description des, shared picture src, and source link URL of the page to be shared.

[0053] Step S102, calling a preset service interface, and generating a service page based on sharing parameters.

[0054] After obtaining the sharing parameters in the sharing request, the execution subject can call the preset service interface to transmit the obtained sharing parameters to the preset service. The preset service can be a service that generates for the sharing plug-in to capture, which is used to generate a hypertext markup language HTML page that complies with the sharing plug-in capture according to the sharing parameters transmitted by the preset service interface, that is, a service page. The preset service can be a type of application that runs in the background and can provide users with the function of generating corresponding HTML pages locally and through the network, such as client / server applications, web servers, database servers, and other server-based applications. The service page only contains information for different sharing plug-ins to capture the content of the card link.

[0055] Specifically, HTML is a markup language that uses markup symbols to mark the various parts of the web page to be displayed. The web page file itself is a text file. By adding markup symbols to the text file, the browser can correctly display the content (such as: how to process text, how to arrange the screen, how to display pictures, etc.). The browser reads the web page file in sequence, and then interprets and displays the marked content according to the markup symbols. The error will not be pointed out for the markup with writing errors, and the interpretation and execution process will not be stopped. The user can only analyze the cause and location of the error through the display effect. However, it should be noted that different browsers may have different interpretations of the same markup symbol, and thus may have different display effects. The HTML service page can be a page to be displayed marked by markup symbols. HTML markup symbols can be represented by some codes, and the codes can be represented in two ways. That is, character code (named entity) and numeric code (numbered entity). The character code starts with the "&" symbol and ends with a semicolon ";", with the character name in between, such as ®;. The numeric code also starts with the "&#" symbol and ends with a semicolon ";", with the number in between, such as

[0056] Step S103, calling the sharing plug-in, crawling the service page, and generating a card link.

[0057] When generating a service page, the execution entity can configure the template based on the address of the preset service and the preset link parameters.

[0058] To configure the parameter values ​​corresponding to the parameters tit, des, src, and url to be shared in the link parameter configuration template.

[0059] That is, the parameter value can be changed according to the different pages that the user wants to share. When the user wants to share different pages, he only needs to modify the parameter values ​​corresponding to the different shared pages in the preset link parameter configuration template to achieve uniform modification of the generated card link. It is understandable that the content displayed on the card link can also be uniformly modified. For example, the parameter value corresponding to the parameter can be modified by adding or reducing the parameter by modifying the preset link parameter configuration template, so as to achieve the uniform modification of the shared card style or content.

[0060] Specifically, the configured parameter values ​​may be used to indicate information such as the location of the open graph mark corresponding to each parameter to be shared in the service page.

[0061] Specifically, when there are multiple pages that need to call the sharing plug-in to perform the sharing function, the executing entity does not need to repeatedly configure the information required by the sharing plug-in. It only needs to splice the address of the preset service: the sharing parameters (including sharing parameter name and sharing parameter value) corresponding to the page to be shared, and then share it to the corresponding sharing plug-in. The sharing plug-in directly captures the service page generated by the service and then generates a card link, so as to realize the function of generating sharing cards in different sharing plug-ins.

[0062] After configuring the parameters to be shared in the link parameter configuration template, the execution subject can generate a link to the service page corresponding to the page to be shared based on the newly configured parameters.

[0063] After configuring the link, the execution entity can call the sharing plug-in, based on the service page pointed to by the link, grab the open graph tag corresponding to the link from the service page, and then generate a card link for sharing. The open graph tag can be a page that meets the requirements of the sharing plug-in.

[0064] The card link can be a corresponding link

[0065] The card has a link access function, so it is called a card link. The card link can be displayed in the form of a card, and the user can jump to the source link address corresponding to the displayed card by clicking the displayed card.

[0066] Source link: The original link of the page that needs to be shared.

[0067] The card displayed by the card link can display the sharing title tit, sharing description des and sharing picture src. The sharing plug-in can be compatible with multiple sharing channels. Sharing channels, for example, can include instant messaging software, such as WeChat and QQ. Sharing channels can also be QQ space, Moments, etc. For example, the card link can be a product card generated by sharing the product details page in the shopping client to the instant messaging software.

[0068] Step S104, share the card link.

[0069] After generating the card link, the executing entity can share the card link to the instant messaging software specified in the information sharing request. It is understandable that the executing entity can also share the generated card link to the client itself where the page to be shared is located. For example, when a user browses a shopping page in client A, he wants to share page B with the preset family group members in client A. The user clicks the sharing control and sends an information sharing request to the executing entity. After receiving the user's sharing request, the executing entity generates a card link corresponding to page B based on the card link generation method described in the above embodiment, and shares the card link to the preset family group members in client A. It is understandable that the executing entity can also share the card link to instant messaging software C or client D. This application does not limit the target sharing channel of the card link.

[0070] This embodiment generates a service page for different sharing plug-ins to capture based on the sharing parameters in the received information sharing request, so that when different projects access the sharing plug-in, there is no need to configure the information required by the sharing plug-in multiple times, thereby streamlining the sharing process. And by directly calling the sharing plug-in that is compatible with multiple sharing channels and capturing the generated service page, a card link can be quickly generated and shared. In addition, when it is necessary to modify the style or content of the shared card, the corresponding service page can be generated by uniformly modifying the sharing parameters once, without the need to modify them one by one, thereby reducing the workload and improving the sharing efficiency. In addition, when the sharing plug-in captures the content of the service page, it captures the content that can directly generate the card link, rather than the link domain name of the source page, so that the required card link can be generated more simply and conveniently, thereby improving the user experience.

[0071] Figure 2 is a schematic diagram of the main flow of the information sharing method according to the second embodiment of the present application, such as Figure 2 As shown, information sharing methods include:

[0072] Step S201: receiving an information sharing request and obtaining sharing parameters in the information sharing request.

[0073] Step S202, calling a preset service interface, and generating a service page based on sharing parameters.

[0074] The principle of step S202 is similar to that of step S102 and will not be described in detail here.

[0075] Specifically, step S202 can also be implemented through step S2021:

[0076] Step S2021, calling a preset service interface, mapping sharing parameters to a page, and generating a hypertext markup language page that complies with the sharing plug-in to capture open graph tags.

[0077] After obtaining the sharing parameters in the information sharing request, the execution subject can call the preset service interface to map the sharing parameters into corresponding hypertext markup language on the page to generate a hypertext markup language page that complies with the sharing plug-in to capture the open graph markup.

[0078] This embodiment maps the sharing parameters on the page into the corresponding hypertext markup language by calling the preset service interface, so that the sharing plug-in can directly capture to generate a card link. There is no need to further configure the information required by the corresponding sharing plug-in when sharing each page to be shared, thereby simplifying the sharing path and improving sharing efficiency.

[0079] Step S203, calling the sharing plug-in, crawling the service page, and generating a card link.

[0080] The principle of step S203 is similar to that of step S103 and will not be described in detail here.

[0081] Specifically, step S203 can also be implemented through steps S2031 to S2032:

[0082] Step S2031, obtain the service address where the service page is located, and extract the sharing parameter value.

[0083] After or while generating the service page, the execution subject can obtain the address of the service page. After obtaining the service address of the service page, the execution subject can call the sharing plug-in to extract the sharing parameter value corresponding to the sharing parameter in the address.

[0084] Step S2032, calling the sharing plug-in to grab the corresponding open graph tag from the service page based on the sharing parameter value and generate a card link.

[0085] Step S204, share the card link.

[0086] After extracting the shared parameter value, the execution subject can fetch the newly configured parameter value from the service page based on the service page pointed to by the address where the service page is located.

[0087] The corresponding Open Graph tag generates a card link for sharing.

[0088] This embodiment determines and captures the open graph markup to be captured based on the service address of the service page by calling the sharing plug-in, so as to directly generate a card link without any specific configuration of the plug-in. When the sharing plug-in captures the service page, what is captured is the open graph markup that can directly generate a card link, rather than the link domain name of the source page, so that the process of generating a card link can be faster and more accurate.

[0089] The principle of step S204 is similar to that of step S104 and will not be described in detail here.

[0090] Specifically, step S204 can also be implemented through steps S2041 to S2043:

[0091] Step S2041, obtaining a sharing channel identifier in the information sharing request.

[0092] The information sharing request may include a sharing channel identifier. The sharing channel may be various instant messaging software, such as WeChat, Facebook, etc. The sharing channel identifier may be the initials of each instant messaging software, for example, the sharing channel identifier corresponding to WeChat may be WX or wx. The sharing channel identifier corresponding to Facebook may be Fb. The sharing channel identifier corresponding to Twitter may be Tt. This application does not specifically limit the naming of the sharing channel identifiers corresponding to each instant messaging software.

[0093] Step S2042: determining the sharing channel based on the sharing channel identifier.

[0094] Step S2043, sharing the card link to the sharing channel.

[0095] After obtaining the sharing channel identifier, the execution subject can determine the sharing channel corresponding to the sharing channel identifier according to the preset corresponding relationship between the sharing channel identifier and the sharing channel, and can share the generated card link to the determined sharing channel.

[0096] In this embodiment, the card link is shared to the sharing channel corresponding to the sharing channel identifier through the sharing channel identifier in the information sharing request, so that accurate sharing of page information can be achieved.

[0097] Step S205, receiving a card link access request, jumping to a service page, obtaining a source link address, generating a corresponding jump code based on a preset automatic refresh frequency, and then executing the jump code to jump to a page corresponding to the source link address.

[0098] The execution subject, after intercepting and sharing the card, can be shared with the family group members of the local client, for example. When the family group members click on the card link, the execution subject receives the card link access request, triggering the card link access process. Then, it first jumps to the service page corresponding to the link, and then obtains the source link address.

[0099] Then, a corresponding jump code is generated based on the source link address and the preset automatic refresh frequency. For example, the code can be generated by the automatic refresh function of the web page using the meta tag, which can make the current service page automatically jump to the page corresponding to the URL after 2 seconds. Among them, the 2 in the code represents the set interval time (in seconds), and the corresponding preset automatic refresh frequency is 0.5. The parameter value of the parameter content in the code is determined according to the preset automatic refresh frequency. The URL is the web page address that automatically jumps after the specified interval time. This application does not limit the specific value of the preset automatic refresh frequency, and does not specifically limit the set interval time.

[0100] The execution subject executes the jump code to jump from the current service page to the page corresponding to the source link address without perception.

[0101] It is understandable that the execution subject can also share the card link to other instant messaging software, such as WeChat. At this time, the execution subject can be a server that connects the client or terminal where the page to be shared is located and other instant messaging software. The server receives the card link access request sent by other instant messaging software, then jumps to the service page, obtains the source link address, generates the corresponding jump code based on the preset automatic refresh frequency, and then executes the jump code to jump to the page corresponding to the source link address.

[0102] This embodiment generates a jump code based on the source link address and a preset automatic refresh frequency, so that when a user accesses a card link, the user can jump from the service page to the sharing page corresponding to the source address without noticing, thereby improving the user experience.

[0103] Figure 3 2 is a schematic diagram of an application scenario of the information sharing method according to the third embodiment of the present application. The information sharing method of this embodiment is applied to a scenario where multiple pages need to access a sharing plug-in to share page content. Figure 3 As shown, the server or processor 304 receives the information sharing request 302 for the page 301, and obtains the sharing parameter 303 in the information sharing request 302. The server or processor 304 calls the preset service interface 305, and generates a service page 307 based on the sharing parameter 303. The server or processor 304 calls the sharing plug-in 306, grabs the service page 307, and generates a card link 308. The server or processor 304 shares the card link 308.

[0104] Figure 4 is a schematic diagram of the main modules of the information sharing device according to an embodiment of the present application. Figure 4 As shown, the information sharing device includes a receiving unit 401 , a service page generating unit 402 , a card link generating unit 403 and a sharing unit 404 .

[0105] The receiving unit 401 is configured to receive an information sharing request and obtain sharing parameters in the information sharing request.

[0106] The service page generating unit 402 is configured to call a preset service interface and generate a service page based on the sharing parameters.

[0107] The card link generating unit 403 is configured to call the sharing plug-in, capture the service page, and generate a card link.

[0108] The sharing unit 404 is configured to share the card link.

[0109] In some embodiments, the service page generation unit 402 is further configured to: call a preset service interface, map sharing parameters to a page, and generate a hypertext markup language page that complies with the sharing plug-in to capture open graph tags.

[0110] In some embodiments, the card link generation unit 403 is further configured to: obtain the service address of the service page and extract the sharing parameter value; call the sharing plug-in to grab the corresponding open graph tag from the service page based on the sharing parameter value and generate a card link.

[0111] In some embodiments, the sharing unit 404 is further configured to: obtain a sharing channel identifier in the information sharing request; determine a sharing channel based on the sharing channel identifier; and link the sharing card to the sharing channel.

[0112] In some embodiments, the information sharing device further includes Figure 4 The access unit not shown in the figure is configured to: receive a card link access request, jump to a service page, obtain a source link address, generate a corresponding jump code based on a preset automatic refresh frequency, and then execute the jump code to jump to a page corresponding to the source link address.

[0113] It should be noted that the information sharing method and the information sharing device in the present application have a corresponding relationship in terms of specific implementation content, so the repeated content will not be explained again.

[0114] Figure 5 An exemplary system architecture 500 is shown to which the information sharing method or information sharing device according to the embodiments of the present application can be applied.

[0115] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0116] Users can use terminal devices 501, 502, 503 to interact with server 505 through network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0117] The terminal devices 501, 502, 503 may be various electronic devices that can log in to shopping websites and support web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0118] The server 505 may be a server that provides various services, such as a background management server (only an example) that provides support for information sharing requests submitted by users using terminal devices 501, 502, and 503. The background management server may receive information sharing requests, obtain sharing parameters in the information sharing requests, call a preset service interface, generate a service page based on the sharing parameters, call a sharing plug-in, capture the service page, generate a card link, and share the card link.

[0119] It should be noted that the information sharing method provided in the embodiment of the present application is generally executed by the server 505 , and accordingly, the information sharing device is generally set in the server 505 .

[0120] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0121] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer system 600 of a terminal device suitable for implementing an embodiment of the present application. Figure 6 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0122] like Figure 6As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the computer system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0123] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.

[0124] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present application are executed.

[0125] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0126] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0127] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a receiving unit, a service page generating unit, a card link generating unit, and a sharing unit. The names of these units do not constitute limitations on the units themselves in some cases.

[0128] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device receives an information sharing request, obtains sharing parameters in the information sharing request; calls a preset service interface, generates a service page based on the sharing parameters; calls a sharing plug-in, captures the service page, generates a card link, and shares the card link.

[0129] According to the technical solution of the embodiment of the present application, by generating a service page for different sharing plug-ins to capture based on the sharing parameters in the received information sharing request, it can be achieved that when different projects access the sharing plug-in, there is no need to configure the information required by the sharing plug-in multiple times, thereby streamlining the sharing process. And by directly calling a sharing plug-in that is compatible with multiple sharing channels and capturing the generated service page, a card link can be quickly generated and shared. In addition, when it is necessary to modify the style or content of the shared card, the corresponding service page can be generated by uniformly modifying the sharing parameters once, without the need to modify them one by one, thereby reducing the workload and improving sharing efficiency. In addition, when the sharing plug-in captures the content of the service page, it captures the content that can directly generate a card link, rather than the link domain name of the source page, so that the required card link can be generated more simply and conveniently, thereby improving the user experience.

[0130] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. An information sharing method, characterized in that: include: Receiving an information sharing request, and obtaining sharing parameters in the information sharing request; Calling a preset service interface and generating a service page based on the sharing parameters; Calling a sharing plug-in, grabbing the service page, and generating a card link, including: obtaining a service address where the service page is located, extracting a corresponding sharing parameter value according to a preset link parameter configuration template, calling a sharing plug-in to grab a corresponding open graph tag from the service page based on the sharing parameter value, and generating a card link; Share the link to said card.

2. The method according to claim 1, characterized in that The generating service page includes: The preset service interface is called, the sharing parameters are mapped to the page, and a hypertext markup language page is generated that complies with the sharing plug-in to capture the open graph markup.

3. The method according to claim 1, characterized in that: The sharing of the card link includes: Obtaining a sharing channel identifier in the information sharing request; Determining a sharing channel based on the sharing channel identifier; Share the card link to the sharing channel.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: A card link access request is received, the service page is jumped to, a source link address is obtained, a corresponding jump code is generated based on a preset automatic refresh frequency, and then the jump code is executed to jump to a page corresponding to the source link address.

5. An information sharing device, characterized in that: include: A receiving unit, configured to receive an information sharing request and obtain a sharing parameter in the information sharing request; A service page generating unit is configured to call a preset service interface and generate a service page based on the sharing parameters; The card link generation unit is configured to call the sharing plug-in, capture the service page, and generate a card link, including: obtaining a service address where the service page is located, extracting a corresponding sharing parameter value according to a preset link parameter configuration template, calling the sharing plug-in to capture a corresponding open graph tag from the service page based on the sharing parameter value, and generating a card link; The sharing unit is configured to share the card link.

6. The device according to claim 5, characterized in that The service page generating unit is further configured to: The preset service interface is called, the sharing parameters are mapped to the page, and a hypertext markup language page is generated that complies with the sharing plug-in to capture the open graph markup.

7. The device according to claim 5, characterized in that The sharing unit is further configured to: Obtaining a sharing channel identifier in the information sharing request; Determining a sharing channel based on the sharing channel identifier; Share the card link to the sharing channel.

8. The device according to any one of claims 5 to 7, characterized in that The apparatus further comprises an access unit configured to: A card link access request is received, the service page is jumped to, a source link address is obtained, a corresponding jump code is generated based on a preset automatic refresh frequency, and then the jump code is executed to jump to a page corresponding to the source link address.

9. An information sharing electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 4.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images