CN113076294A

CN113076294A - Information sharing method and device

Info

Publication number: CN113076294A
Application number: CN202110411104.1A
Authority: CN
Inventors: 郭会茹
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2021-04-16
Filing date: 2021-04-16
Publication date: 2021-07-06

Abstract

The application discloses an information sharing method and device, and relates to the technical field of computers, wherein a specific embodiment comprises the steps of 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, capturing a service page, and generating a card link; the sharing card links. Therefore, the implementation method can realize that information required by the sharing plug-in is not required to be configured for many times when different projects access the sharing plug-in, thereby simplifying the sharing process.

Description

Information sharing method and device

Technical Field

The application relates to the technical field of computers, in particular to an information sharing method and device.

Background

In actual development, sharing of different projects requires introduction of a variety of social plug-ins. The developer needs to repeatedly configure page tags for different social plugins to grab in the page of each project and then share the page tags for different social plugins to grab.

In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:

and the access of different projects to different social plugins needs to be configured for many times, and the process is complicated.

Disclosure of Invention

In view of this, the embodiment of the application provides an information sharing method and device, which can solve the problems that the existing different projects need to be configured for multiple times when accessing different social plugins, and the process is complicated.

In order to achieve the above object, according to an aspect of the embodiments of the present application, there is provided an information sharing method, including:

receiving an information sharing request, and acquiring 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, capturing a service page, and generating a card link;

the sharing card links.

Optionally, generating a service page includes:

and calling a preset service interface, mapping the sharing parameters to a page, and generating a hypertext markup language page which accords with the sharing plug-in to capture the open atlas mark.

Optionally, generating a card link includes:

acquiring a service address of a service page, and extracting a sharing parameter value;

and calling the sharing plug-in to capture the corresponding open map mark from the service page based on the sharing parameter value, and generating a card link.

Optionally, the sharing card link includes:

acquiring a sharing channel identifier in an information sharing request;

determining a sharing channel based on the sharing channel identifier;

the sharing cards are linked to a sharing channel.

Optionally, the information sharing method further includes:

receiving a card link access request, jumping to a service page, acquiring a source link address, generating a corresponding jump code based on a preset automatic refreshing frequency, and executing the jump code to jump to a page corresponding to the source link address.

In addition, this application still provides an information sharing device, includes:

the receiving unit is configured to receive the information sharing request and acquire a sharing parameter in the information sharing request;

the service page generation 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 a service page and generate a card link;

the sharing unit is configured to share the card link.

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

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

Optionally, the sharing unit is further configured to:

acquiring a sharing channel identifier in an information sharing request;

determining a sharing channel based on the sharing channel identifier;

the sharing cards are linked to a sharing channel.

Optionally, the information sharing apparatus further includes an access unit configured to:

In addition, this application still provides an information sharing electronic equipment, includes: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by one or more processors, the one or more processors realize the information sharing method.

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

One embodiment of the above invention has the following advantages or benefits: according to the method and the device, the service page for different sharing plugins to grab is generated based on the sharing parameters in the received information sharing request, so that information needed by the sharing plugins does not need to be configured for many times when different projects access the sharing plugins, and the sharing process is simplified. And the generated service page is captured by directly calling the sharing plug-in compatible with various sharing channels, and the card link can be generated and shared quickly. And when the shared card style or content needs to be modified, the sharing parameters are uniformly modified once to generate the corresponding service page, so that the modification one by one is not needed, the workload is reduced, and the sharing efficiency is improved. In addition, when the sharing plug-in captures the content of the service page, what is captured is the content capable of directly generating the card link, but not the link domain name of the source page, so that the required card link can be generated more simply and conveniently, and the user experience is improved.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a further understanding of the application and are not to be construed as limiting the application. Wherein:

fig. 1 is a schematic view of a main flow of an information sharing method according to a first embodiment of the present application;

fig. 2 is a schematic view of a main flow of an information sharing method according to a second embodiment of the present application;

fig. 3 is a schematic view of an application scenario of an information sharing method according to a third embodiment of the present application;

fig. 4 is a schematic diagram of main modules of an information sharing apparatus according to an embodiment of the present disclosure;

FIG. 5 is an exemplary system architecture diagram to which embodiments of the present application may be applied;

fig. 6 is a schematic structural diagram of a computer system suitable for implementing the terminal device or the server according to the embodiment of the present application.

Detailed Description

The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a schematic view of a main flow of an information sharing method according to a first embodiment of the present application, and as shown in fig. 1, the information sharing method includes:

step S101, receiving an information sharing request, and acquiring sharing parameters in the information sharing request.

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

And step S102, calling a preset service interface, and generating a service page based on the sharing parameters.

After obtaining the sharing parameters in the sharing request, the execution main body may call a preset service interface to transmit the obtained sharing parameters to a preset service. For example, the address of the preset service may be: http:// shareserver. The preset service can be a service for generating a sharing plug-in to capture, and is used for generating a hypertext markup language (HTML) page, namely a service page, which accords with the capture of the sharing plug-in according to the sharing parameters transmitted by the preset service interface. The default service may be a type of application that runs in the background and may provide functionality for generating corresponding HTML pages for users locally and over a 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 linked content of the card.

In particular, HTML is a markup language that marks parts of a web page to be displayed by markup symbols. The web page file is a text file, and by adding a marker in the text file, the browser can correctly display the content (such as how the words are processed, how the pictures are arranged, how the pictures are displayed, etc.) in the text file. The browser reads the webpage files in sequence, then explains and displays the marked content according to the marker, the written error mark does not indicate the error of the written error mark, the explanation execution process is not stopped, and the user can analyze the error reason and the error part only through the display effect. It should be noted that different browsers may have different interpretations of the same token and thus different display effects. The HTML service page may be a page marked for display by a markup symbol. The HTML markup symbols can be represented by a number of codes, which can have 2 representations. Namely a character code (named entity) and a number code (numbered entity). Character code in "&"begin with symbol, with semicolon"; "end with character name in between, e.g.® . The number code also "&The "#" symbol starts with a semicolon "; "end with numbering in between, e.g.

Step S103, calling the sharing plug-in, capturing a service page, and generating a card link.

While the execution subject generates the service page, the execution subject may configure the template based on the address of the preset service and the preset link parameter, for example:

http://shareserver.aa.co.th/？tit＝TestTitle&des＝helloworld&src＝https://mstatic.wx.co.th/email/images/qrCode.jpg&url＝http://mhome.wx.co.th/order/orderList#/

the parameter values corresponding to the parameters to be shared, tit, des, src and url, in the link parameter configuration template are configured. For example, the corresponding parameter values may be configured to:

TestTitle

Helloworld

https://mstatic.jd.co.th/email/images/qrCode.jpg

http://mhome.jd.co.th/order/orderList#/

that is, the parameter value can be changed according to the page to be shared by the user. When a user needs to share different pages, the generated card links can be modified uniformly only by modifying the parameter values corresponding to the different shared pages in the preset link parameter configuration template. It is understood that the content displayed on the card link may also be modified uniformly. For example, the parameter value corresponding to the parameter may be modified by modifying the preset link parameter configuration template to increase or decrease the parameter, so that the shared card style or content may be modified uniformly.

Specifically, the configured parameter value may be used to indicate information such as a position where an open map corresponding to each parameter to be shared is marked in a service page.

Specifically, when a plurality of pages all need to call the sharing plug-in to serve as a scene of the sharing function, the execution main body does not need to repeatedly configure information needed by the sharing plug-in, and only needs to preset the address of the service: http:// shareserver. aa.co.th is spliced with sharing parameters (including sharing parameter names and sharing parameter values) corresponding to the pages to be shared, and then shared to corresponding sharing plug-ins, and the sharing plug-ins directly grab service pages generated by services to generate card links, so that the function of generating sharing cards in different sharing plug-ins can be realized.

After configuring the parameters to be shared in the link parameter configuration template, the execution subject may generate a link corresponding to the service page of the page to be shared based on the newly configured parameters, for example, the link may be:

http://shareserver.aa.co.th/？tit＝TestTitle&des＝helloworld&src＝https://mstatic.jd.co.th/email/images/qrCode.jpg&url＝http://mhome.jd.co.th/order/orderList#/

after the execution main body configures the link, the sharing plug-in can be called, based on the service page pointed by the link, the open map mark corresponding to the link is captured from the service page, and then the card link is generated for sharing. The open atlas label may be a page that conforms to the grasp of the sharing plug-in.

The card link may be a corresponding link:

http:// shareserver. tit TestTitle & des helloworld & src https:// mstatic.jd.co.th/email/images/qrcode.jpg & url:// mhome.jd.co.th/order #/card. The card has a link access function and is therefore called a card link. The card link can be displayed in the form of a card, and a user clicking the displayed card can jump to a source link address corresponding to the displayed card:

url ═ http:// mhome.jd.co.th/order/orderList #/corresponding page.

Source linking: the original links of the outgoing pages need to be shared.

The card link may display a sharing title tit, a sharing description des, and a sharing picture src on the displayed card. The sharing plug-in can be compatible with various sharing channels. The sharing channel may include, for example, instant messaging software, which may be WeChat, QQ. The sharing channel may also be a QQ space, circle of friends, etc. Example, card linking: the commodity detail page in the shopping client can be shared with the commodity card generated by the instant messaging software.

Step S104, sharing the card link.

After the execution main body generates the card link, the card link can be shared and the instant messaging software specified by the information sharing request can be obtained. It can be understood that the execution subject may also share the generated card link to the client itself where the page to be shared is located. For example, when browsing a shopping page in the client a, a user needs to share the page B with a preset family member in the client a, and clicks the sharing control, and sends an information sharing request to the execution main body. After receiving a sharing request of a user, the execution main body generates a card link corresponding to the page B based on the card link generation mode in the embodiment, and shares the card link to a preset family member in the client a. It can be understood that the execution main body can also share the card link to the C instant messaging software or the D client, and the target sharing channel of the card link is not limited in the present application.

According to the method and the device for sharing the information, the service page for different sharing plugins to capture is generated based on the sharing parameters in the received information sharing request, so that when different projects access the sharing plugins, the information needed by the sharing plugins does not need to be configured for many times, and the sharing process is simplified. And the generated service page is captured by directly calling the sharing plug-in compatible with various sharing channels, and the card link can be generated and shared quickly. And when the shared card style or content needs to be modified, the sharing parameters are uniformly modified once to generate the corresponding service page, so that the modification one by one is not needed, the workload is reduced, and the sharing efficiency is improved. In addition, when the sharing plug-in captures the content of the service page, what is captured is the content capable of directly generating the card link, but not the link domain name of the source page, so that the required card link can be generated more simply and conveniently, and the user experience is improved.

Fig. 2 is a schematic main flow diagram of an information sharing method according to a second embodiment of the present application, and as shown in fig. 2, the information sharing method includes:

step S201, receiving an information sharing request, and acquiring a sharing parameter in the information sharing request.

Step S202, a preset service interface is called, and a service page is generated based on the sharing parameters.

The principle of step S202 is similar to that of step S102, and is not described here.

Specifically, step S202 can also be realized by step S2021:

step S2021, calling a preset service interface, mapping sharing parameters to a page, and generating a hypertext markup language page which accords with the sharing plug-in to capture an open graph mark.

After obtaining the sharing parameters in the information sharing request, the execution main body can call a preset service interface, and map the sharing parameters into corresponding hypertext markup language on the page to generate a hypertext markup language page which accords with the sharing plug-in to capture the open atlas mark.

According to the method and the device for sharing the card, the sharing parameters are mapped to the corresponding hypertext markup language on the page by calling the preset service interface, so that the sharing plug-in can be directly grabbed to generate the card link, the information required by the corresponding sharing plug-in is not required to be further configured when each page to be shared is shared, the sharing approach is simplified, and the sharing efficiency is improved.

Step S203, call the sharing plug-in, capture the service page, and generate a card link.

The principle of step S203 is similar to that of step S103, and is not described here.

Specifically, step S203 can also be realized by step S2031 to step S2032:

step S2031, obtain the service address of the service page, and extract the sharing parameter value.

After or while generating the service page, the execution subject may obtain an address where the service page is located, for example:

after obtaining the service address where the service page is located, the execution subject may call the sharing plug-in, and extract a sharing parameter value corresponding to the sharing parameter in the address, which may be, for example:

tit＝TestTitle&des＝helloworld&src＝https://mstatic.jd.co.th/email/images/qrCode.jpg&url＝http://mhome.jd.co.th/order/orderList#/

step S2032, calling the sharing plug-in to capture the corresponding open atlas mark from the service page based on the sharing parameter value, and generating the card link.

In step S204, the sharing card link is performed.

After extracting the sharing parameter value, the execution subject may capture a newly configured parameter value from the service page based on the service page pointed by the address where the service page is located:

tit TestTitle & des helloworld & src https:// mstatic.jd.co.th/email/images/qrcode.jpg & url http:// mhome.jd.co.th/order #/corresponding open-graph label, thereby generating card links for sharing.

According to the embodiment, the sharing plug-in is called, the open map mark to be captured is determined and captured based on the service address of the service page, so that the card link is directly generated, and specific configuration of the plug-in is not needed. And when the sharing plug-in captures the service page, the open map mark capable of directly generating the card link is captured instead of the link domain name of the source page, so that the process of generating the card link is quicker and more accurate.

The principle of step S204 is similar to that of step S104, and is not described here again.

Specifically, step S204 can also be realized by step S2041 to step S2043:

step S2041, a sharing channel identifier in the information sharing request is obtained.

The information sharing request may include a sharing channel identifier. The sharing channel can be various instant messaging software, such as WeChat, Facebook, and the like. The sharing channel identifier may be an acronym of each instant messaging software, for example, the sharing channel identifier corresponding to the 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. The naming of the sharing channel identifier corresponding to each instant messaging software is not specifically limited.

Step S2042, determining a sharing channel based on the sharing channel identifier.

In step S2043, the sharing card is linked to a sharing channel.

After acquiring the sharing channel identifier, the execution main body may determine the sharing channel corresponding to the sharing channel identifier according to a preset corresponding relationship between the sharing channel identifier and the sharing channel. And the generated card link can be shared to the determined sharing channel.

According to the method and the device for sharing the page information, the card link is shared to the sharing channel corresponding to the sharing channel identification through the sharing channel identification in the information sharing request, and accurate page information sharing can be achieved.

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

The execution main part is sharing the back with the card interception, for example can share the family group member for local client, and when the family group member clicked this card and linked the back, the execution main part received the card promptly and linked the access request, triggered the card and linked:

http:// shareserver. tit TestTitle & des helloworld & src https:// mstatic.jd.co.th/email/images/qrcode.jpg & url:// mhome.jd.co.th/order #/access process. And then jump to the service page corresponding to the link first, and then obtain the source link address:

url＝http://mhome.jd.co.th/order/orderList#/

and generating a corresponding jump code based on the source link address and a preset auto-refresh frequency, for example, a code generated by using the function of auto-refresh web page of meta tag:

< meta http-equ ═ refresh "content ═ 2; the code can enable the skipped current service page to automatically jump to the page corresponding to the URL after 2 seconds. Wherein 2 in the code represents a set interval time (unit is second), the corresponding preset automatic refresh frequency is 0.5, and the parameter value of the parameter content in the code is determined according to the preset automatic refresh frequency. The URL is the address of the web page that automatically jumps after a specified interval. The method and the device do not limit the specific numerical value of the preset automatic refreshing frequency, and do not limit the set interval time.

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.

It is understood that the executing agent may also share the card link with other instant messaging software, such as WeChat. At this time, the execution main body may be a server connecting the client or the terminal where the page to be shared is located and other instant messaging software. The server receives card link access requests sent by other instant messaging software, then jumps to a service page, acquires a source link address, generates a corresponding jump code based on a preset automatic refreshing frequency, and then executes the jump code to jump to a page corresponding to the source link address.

According to the method and the device, the skip code generated based on the source link address and the preset automatic refreshing frequency can enable the user to skip from the service page to the sharing page corresponding to the source address without perception when the user accesses the card link, and user experience is improved.

Fig. 3 is a schematic view of an application scenario of an information sharing method according to a third embodiment of the present application. The information sharing method is applied to a scene that a plurality of pages need to access a sharing plug-in to share page contents. As shown in fig. 3, a server or processor 304 receives an information sharing request 302 for a page 301, and obtains a sharing parameter 303 in the information sharing request 302. The server or processor 304 calls the pre-set service interface 305 and generates a service page 307 based on the sharing parameters 303. The server or processor 304 invokes the sharing plug-in 306 to crawl the service page 307, generating a card link 308. The server or processor 304 shares the card link 308.

Fig. 4 is a schematic diagram of main modules of an information sharing apparatus according to an embodiment of the present disclosure. As shown in fig. 4, the information sharing apparatus includes a receiving unit 401, a service page generating unit 402, a card link generating unit 403, and a sharing unit 404.

The receiving unit 401 is configured to receive an information sharing request, and obtain a sharing parameter in the information sharing request.

The service page generating unit 402 is configured to invoke a preset service interface, and generate a service page based on the sharing parameter.

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

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

In some embodiments, the service page generation unit 402 is further configured to: and calling a preset service interface, mapping the sharing parameters to a page, and generating a hypertext markup language page which accords with the sharing plug-in to capture the open atlas mark.

In some embodiments, the card link generation unit 403 is further configured to: acquiring a service address of a service page, and extracting a sharing parameter value; and calling the sharing plug-in to capture the corresponding open map mark from the service page based on the sharing parameter value, and generating a card link.

In some embodiments, the sharing unit 404 is further configured to: acquiring a sharing channel identifier in an information sharing request; determining a sharing channel based on the sharing channel identifier; the sharing cards are linked to a sharing channel.

In some embodiments, the information sharing apparatus further includes an access unit, not shown in fig. 4, configured to: receiving a card link access request, jumping to a service page, acquiring a source link address, generating a corresponding jump code based on a preset automatic refreshing frequency, and executing the jump code to jump to a page corresponding to the source link address.

It should be noted that, in the information sharing method and the information sharing apparatus of the present application, the specific implementation contents have corresponding relationships, and therefore, the repeated contents are not described again.

Fig. 5 shows an exemplary system architecture 500 to which the information sharing method or the information sharing apparatus according to the embodiment of the present application may be applied.

As shown in fig. 5, the system architecture 500 may include

terminal devices

501, 502, 503, a network 504, and a server 505. The network 504 serves to provide a medium for communication links between the

terminal devices

501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The

terminal devices

501, 502, 503 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

501, 502, 503 may be various electronic devices that may log into a shopping website and support web browsing, including but not limited to smart phones, tablets, laptop and desktop computers, and the like.

The server 505 may be a server providing various services, such as a background management server (for example only) providing support for information sharing requests submitted by users using the

terminal devices

501, 502, 503. The background management server can receive the information sharing request and acquire 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, capturing a service page, and generating a card link; the sharing card links.

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 apparatus is generally disposed in the server 505.

It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a terminal device of an embodiment of the present application. The terminal device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that 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 section 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the computer system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output section 607 including a signal processing section such as a Cathode Ray Tube (CRT), a liquid crystal credit authorization inquiry processor (LCD), and the like, and a speaker and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 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, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.

In particular, according to embodiments disclosed herein, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments disclosed herein include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are executed when the computer program is executed by the Central Processing Unit (CPU) 601.

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 two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor comprises a receiving unit, a service page generating unit, a card link generating unit and a sharing unit. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs, and when the one or more programs are executed by one device, the device receives an information sharing request and acquires 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, capturing a service page, and generating a card link; the sharing card links.

According to the technical scheme of the embodiment of the application, the service page for different sharing plugins to capture is generated based on the sharing parameters in the received information sharing request, so that information needed by the sharing plugins does not need to be configured for many times when different projects access the sharing plugins, and the sharing process is simplified. And the generated service page is captured by directly calling the sharing plug-in compatible with various sharing channels, and the card link can be generated and shared quickly. And when the shared card style or content needs to be modified, the sharing parameters are uniformly modified once to generate the corresponding service page, so that the modification one by one is not needed, the workload is reduced, and the sharing efficiency is improved. In addition, when the sharing plug-in captures the content of the service page, what is captured is the content capable of directly generating the card link, but not the link domain name of the source page, so that the required card link can be generated more simply and conveniently, and the user experience is improved.

The above-described embodiments should not be construed as limiting the scope of the present application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An information sharing method, comprising:

calling a sharing plug-in, capturing the service page, and generating a card link;

and sharing the card link.

2. The method of claim 1, wherein the generating a service page comprises:

3. The method of claim 1, wherein the generating the card link comprises:

acquiring a service address of the service page, and extracting a sharing parameter value;

and calling a sharing plug-in to capture a corresponding open map mark from the service page based on the sharing parameter value, and generating a card link.

4. The method of claim 1, wherein the sharing the card link comprises:

acquiring a sharing channel identifier in the information sharing request;

determining a sharing channel based on the sharing channel identification;

sharing the card is linked to the sharing channel.

5. The method according to any one of claims 1 to 4, further comprising:

receiving a card link access request, jumping to the service page, acquiring a source link address, generating a corresponding jump code based on a preset automatic refreshing frequency, and executing the jump code to jump to a page corresponding to the source link address.

6. An information sharing apparatus, comprising:

the receiving unit is configured to receive an information sharing request and acquire a sharing parameter in the information sharing request;

the service page generation unit is configured to call a preset service interface and generate a service page based on the sharing parameter;

the card link generation unit is configured to call a sharing plug-in, capture the service page and generate a card link;

a sharing unit configured to share the card link.

7. The apparatus of claim 6, wherein the service page generation unit is further configured to:

8. The apparatus of claim 6, wherein the card link generation unit is further configured to:

9. The apparatus of claim 6, wherein the sharing unit is further configured to:

acquiring a sharing channel identifier in the information sharing request;

determining a sharing channel based on the sharing channel identification;

sharing the card is linked to the sharing channel.

10. The apparatus according to any one of claims 6 to 9, further comprising an access unit configured to:

11. An information sharing electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.

12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-5.