WO2018024116A1 - 基于卡片的信息展示方法、信息展示业务的处理方法及装置 - Google Patents

基于卡片的信息展示方法、信息展示业务的处理方法及装置 Download PDF

Info

Publication number
WO2018024116A1
WO2018024116A1 PCT/CN2017/093786 CN2017093786W WO2018024116A1 WO 2018024116 A1 WO2018024116 A1 WO 2018024116A1 CN 2017093786 W CN2017093786 W CN 2017093786W WO 2018024116 A1 WO2018024116 A1 WO 2018024116A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
client
version
target information
information
Prior art date
Application number
PCT/CN2017/093786
Other languages
English (en)
French (fr)
Inventor
张赣
范伟
王翔南
Original Assignee
阿里巴巴集团控股有限公司
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 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to SG11201900826QA priority Critical patent/SG11201900826QA/en
Priority to MYPI2019000483A priority patent/MY192398A/en
Publication of WO2018024116A1 publication Critical patent/WO2018024116A1/zh
Priority to PH12019500216A priority patent/PH12019500216A1/en
Priority to US16/265,881 priority patent/US10909314B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/197—Version control
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/453—Help systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72439—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for image or video messaging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725—Cordless telephones

Definitions

  • the present application relates to the field of computer technology, and in particular, to a card-based information display method, a method and a device for processing an information display service.
  • card stream card stream
  • the information to be displayed is usually configured as different types of cards depending on the type of information to be displayed.
  • the application APP cannot display a new type of card, it is usually handled by an operation of guiding the user to perform an application APP version update.
  • the new type of card will be displayed in the application APP used by the user.
  • the method of updating the version of the application APP to implement the display of the new type of card in the application APP exists: when the application APP server is busy and the application APP fails to update, the new type of card cannot be displayed. This reduces the user experience of using the app.
  • the embodiment of the present application provides a card-based information display method, a method and a device for processing an information display service, which are used to solve the problems in the prior art.
  • the embodiment of the present application provides a card-based information display method, and the method includes:
  • the target information and the version upgrade prompt information of the client are displayed by using the second card.
  • the whitelist includes a card type supported by the configured version of the client
  • the client includes a correspondence between a version identifier of a configuration version of the client and a card type supported by the configuration version;
  • the second card supported by the configuration version of the client according to the association identifier includes:
  • determining the target information to be displayed and the card type of the first card for displaying the target information specifically includes: acquiring target information to be displayed from the cached data of the client, and first card for displaying the target information. Card type; or
  • the target information to be displayed and the card type of the first card for displaying the target information are obtained from the server.
  • the method further includes: acquiring and caching the configuration version of the client supported by the server Second card; then,
  • Correlating the second card supported by the configuration version of the client according to the association identifier specifically: associating the cached second card according to the association identifier.
  • the embodiment of the present application further provides a method for processing an information display service, where the method includes:
  • the indication information is used to indicate that the client uses the second card display supported by the configured version of the client.
  • the returning the target information to the client and the indication information specifically include: returning the target information and the indication information to the client in the form of a json string.
  • the embodiment of the present application further provides a card-based information display device, where the device is located at a client, and includes: a determining unit, an associating unit, and a display unit, where:
  • Determining a unit determining target information to be displayed and a card type of the first card for displaying the target information
  • An association unit when determining that the configuration version of the client does not support the card type of the first card, determining an association identifier corresponding to the first card, and associating the second version supported by the configuration version of the client according to the association identifier card;
  • a display unit using the second card to display the target information and the version upgrade prompt information of the client.
  • the embodiment of the present application further provides a processing device for the information display service, where the device is located at the server, and includes: a receiving unit and a returning unit, where:
  • the receiving unit receives a service request for acquiring the target information sent by the client, where the service request includes a version identifier for determining a configuration version of the client, and the version identifier and a card type supported by the configured version of the client Corresponding relationship between them;
  • a returning unit when determining, according to the card type corresponding to the version identifier, that the configured version of the client does not support the card type of the first card for displaying the target information, returning the target information and the indication information to the client,
  • the indication information is used to indicate that the client displays the target information and the version upgrade prompt information of the client by using a second card supported by the configured version of the client.
  • the second card supported by the configuration version is associated with the association identifier in the first card, and the second card is used to display the target information and the version upgrade prompt of the client.
  • the information solves the problem that the configuration version of the client is not upgraded in the prior art, and the new card type cannot be displayed.
  • the card type of the second card can be uniformly configured as a card type supported by multiple configuration versions, so that when it is determined that the client does not support a certain type of card, the unified type of card is displayed, so that the displayed The cards are easier to manage.
  • FIG. 1 is a schematic flowchart of a specific implementation process of a card-based information display method according to Embodiment 1 of the present application;
  • FIG. 2 is a schematic diagram of a singular card in an actual application provided by Embodiment 1 of the present application;
  • FIG. 3 is a schematic flowchart of a specific implementation process of a method for processing an information display service according to Embodiment 2 of the present application;
  • FIG. 4 is a schematic diagram of generating a card type by a card base class in an actual application provided by Embodiment 2 of the present application;
  • FIG. 5 is an information display system in an actual application provided by Embodiment 2 of the present application.
  • FIG. 6 is a schematic structural diagram of a card-based information display apparatus according to Embodiment 3 of the present application.
  • FIG. 7 is a schematic structural diagram of a device for processing information display services according to Embodiment 4 of the present application.
  • card streams feed streams
  • the information to be displayed is usually configured as different types of cards depending on the type of information to be displayed.
  • the WeChat circle of friends uses the feed stream to configure the friend's status information (friend comments, status updates, etc.) as a card for display;
  • Weibo uses the feed stream to configure the news as a card for display. Since different presentations usually require different forms of presentation, there are many different types of cards. For example, when stock information is displayed, it usually needs to be able to display the trend of stocks; when the view information is displayed, it usually needs to be able to comment, etc. Therefore, in practical applications, it is usually necessary to configure a plurality of different types of cards.
  • the method of updating the version of the application APP to implement the display of the new type of card in the application APP exists: when the application APP server is busy and the application APP fails to update, the new type of card cannot be displayed. This reduces the user experience of using the app.
  • Embodiment 1 provides a card-based information display method for a client that can solve the problems in the prior art.
  • a schematic diagram of the specific process of the method is shown in FIG. 1 and includes the following steps:
  • Step S11 Receive a display instruction.
  • the client can usually be a client of an application APP or a client of a web application (Web APP).
  • the client will receive an impression instruction. For example, when a specified time point (9 am or other time point) arrives, the client can receive the display instruction; or, when the server needs the client to display certain information (advertising, information, etc.), it will send the client Sending the display instruction; or, according to the user's personal settings, under certain conditions (for example, the friend has a status update), the client receives the display instruction; or, the user triggers the client to receive the display instruction, and usually the user
  • the triggering method may be a mouse click method, a method of clicking a touch screen button or a method of pulling a touch screen.
  • the client receives the display instruction, and according to the display instruction, can display the status update of the WeChat friend and/or the advertisement pushed by the server;
  • the client of the microblog receives the display instruction to display the status update, news information, and the like of the friend concerned.
  • Step S12 determining target information to be displayed and a card type of the first card for displaying the target information.
  • the target information can usually be news information, advertising information, weather forecast messages, traffic conditions messages, fund or stock news, comment messages, status messages of friends, and the like.
  • the presentation elements of the target information may be text, pictures, audio, and/or video.
  • the new status message updated by the friend is the target information to be displayed, and the display elements of the target information may include text, pictures, audio, and/or video.
  • the cards used to display the target information have corresponding card types, and the card type reflects the classification category of the cards.
  • the card of the opinion class corresponds to the card type of the opinion class (abbreviation, opinion card)
  • the card type of the stock class corresponds to the card type of the stock class (abbreviation, stock card)
  • the card of the fund class corresponds to the card type of the fund class (abbreviation, fund) Cards, etc.
  • the client types of different configuration versions are usually able to display different types of cards, and the configuration version of the client usually has a corresponding relationship with the card types that can be displayed.
  • the client determines the target information and the card type of the first card, which may be to obtain the target information.
  • the card type of the first card and, generally, the target information and the card type of the first card are obtained from the cached data of the client, and the manner of obtaining from the cached data can speed up the response speed of the card display;
  • the target information and the card type of the first card may be obtained from the server.
  • Step S13 determining whether the configuration version of the client supports the card type of the first card, and if yes, executing step S14, and if no, executing step S15.
  • the whitelist can be configured in the client, and the card type supported by the configuration version of the client is recorded in the whitelist. Then, when determining whether the configuration version of the client supports the card type of the first card, The card type of the first card is matched with the card type included in the whitelist. According to the matching result, it is determined whether the configuration version of the client supports the card type of the first card. When the matching is successful, the configuration version of the client is determined. Supports the card type of the first card. When the matching fails, it is determined that the configured version of the client does not support the card type of the first card.
  • This method of judging by the white list can update the card type recorded in the white list when the card type supported by the client of the configuration version is newly added, which is easy to implement in practical applications.
  • the client usually includes a version identifier of the configuration version, and the version identifier identifies the client that can uniquely identify the configuration version.
  • the correspondence between the configured version of the client and the supported card type can be reflected as the correspondence between the version identifier and the supported card type. Therefore, when the client includes the correspondence between the version identifier of the configuration version and the card type supported by the configuration version, it is determined whether the configuration version of the client supports the card type of the first card, and the configuration version of the client may be determined first.
  • a version identifier determining, according to the correspondence, a card type supported by the configuration version corresponding to the version identifier, and then determining, according to the card type of the first card and the determined card type supported by the configured version of the client Whether the configuration version of the client supports the card type of the first card.
  • Step S14 displaying the target information by using the first card.
  • the target information may be displayed by the first card.
  • Step S15 determining an association identifier corresponding to the first card, and associating the second card supported by the configuration version of the client according to the association identifier, and displaying the target information and the client by using the second card Version upgrade prompt information.
  • the first card pair may be passed The associated ID, associated with the second card supported by the client's configuration version.
  • the card type of the second card is the card type supported by the client of the configuration version.
  • the configuration version of the client is "XYZ"
  • the card types supported by the client are A, B, and C
  • the card type of the first card is D.
  • D the card type of the first card
  • the type of card is called the second card.
  • the second card can usually be used.
  • the card type is set to the card type supported by multiple configuration versions. In this way, when the client determines that the card of a card type is not supported, the card is displayed by the same card of the specified card type, which can conveniently manage the displayed card.
  • step S12 when the target information and the card type of the first card are acquired from the server, the second card can also be acquired from the server at the same time, and the second card can be obtained after acquiring the second card.
  • the client caches. In this way, when the second card supported by the configuration version of the client is associated according to the association identifier, the second card that has been cached on the client may be associated according to the association identifier, thereby reducing the time for acquiring the second card. Improve response speed.
  • the second card supported by the configuration version is associated with the association identifier in the first card, and the second card is displayed by using the second card.
  • the target information and the version upgrade prompt information of the client thereby solving the problem that the configuration version of the client is not upgraded in the prior art, and the new card type cannot be displayed.
  • the card type of the second card can be uniformly configured as a card type supported by multiple configuration versions, so that when it is determined that the client does not support a certain type of card, the unified type of card is displayed, so that the displayed The cards are easier to manage.
  • the version upgrade prompt information of the client is also displayed, and the version upgrade prompt message prompts the user to perform the version upgrade.
  • the target information is displayed through the second card
  • the version upgrade prompt information of the client is not displayed at the same time
  • the user usually does not configure the client.
  • the version is upgraded, so that users can't experience the experience enhancement brought by the newly configured version of the client in time, and the company that provides the version upgrade service will also lose business volume.
  • the first card can display the target information (herein referred to as the first target information), and the second card can exhibit
  • the second target information corresponding to the first target information may be the same as the first target information, or may be the target information obtained by adjusting the corresponding display element in the first target information.
  • the second target information may be determined from the first target information according to actual needs.
  • the first target information includes the text A and the picture B and the picture C.
  • the second target information may be the text A and the picture B and the picture C, or may be only the text A, or the text A and the picture A (or the picture B). ), can also be part of the text A, etc.
  • the target information obtained by the client from the server, the card type of the first card, or the associated identifier is usually obtained in a fixed data format.
  • the fixed data format is usually defined by a protocol format defined in advance by both the client and the server.
  • the protocol format can be as follows.
  • FeedViewItem class diagram can be as shown in Table 1.
  • Attributes type of data Description feedId String Card id of the first card Type String Card type of the first card Content Json Target information of the first card Create time Long First card timestamp Singular Json Association identifier
  • the data of the "type” field ie, the card type of the first card
  • the data of the "singular” field ie, the associated identifier
  • the second card is associated to display the target information and the version upgrade prompt information of the client through the second card (which can be called "singular card", singular card).
  • the second card (singular point card) can also be abstracted into a data class, which can be as shown in Table 2.
  • the "clickUrl” field defines a link for implementing a page jump when the entire singularity card is clicked;
  • the "content” field defines the target information displayed in the singularity card;
  • the "referenceMap” field defines, and the target information includes Links, such as downloading links to new configuration versions and/or links to other users (for example, @other users);
  • the "tip” field defines the version upgrade prompt information in the singular card, which can be upgraded by this version. The prompt information reminds the user to upgrade the version;
  • the "tipReferenceMap” field defines the link included in the version upgrade prompt information, and the new configuration version can usually be downloaded through the link.
  • ReferenceData class can be as shown in Table 3.
  • Figure 2 shows the singularity card in the actual application.
  • A is the target information (including text content and video) in the singularity card, which is determined by the "content” field in Table 2, and
  • A there is a bold italic (in the actual application, it can also be highlighted, etc.).
  • the part is the link contained in the target information.
  • the address of the link is determined by the "referenceMap” field in Table 2.
  • the italicized bold display style is determined by the "referenceMap" field in Table 2.
  • the start character and the end character of the italic bold display are determined by the “referString”, “matchStart”, and “matchEnd” fields in Table 3 respectively;
  • B is the client version upgrade prompt information in the singular card, as shown in Table 2
  • the tip” field is determined, and in B, there is a bolded italic (which can be highlighted in the actual application, etc.) part of the link contained in B, the address of the link is determined by the "tipReferenceMap” field in Table 2, the link italic
  • the bold display style, the start character and the end character of the italic bold display are also determined by the "referString", "matchStart” and “matchEnd” fields in Table 3
  • C is the entire singular card interface, point Singularity card interface page jump, jump to the page address of the link is determined by the 2 "clickUrl” fields of the table.
  • Embodiment 1 The method provided in Embodiment 1 is used for a client.
  • Embodiment 2 of the present application will provide a method for processing an information display service, which is used for a server, and can solve the problems in the prior art.
  • FIG. 3 A schematic diagram of the specific process of the method is shown in FIG. 3, and includes the following steps:
  • Step S21 Receive a service request for acquiring target information sent by the client, where the service request includes a version identifier for determining a configuration version of the client, and the version identifier and a card type supported by the configuration version of the client There is a correspondence between them.
  • the target information here is the same as the target information in step S12, and will not be described again here.
  • the service request includes a version identifier of a configuration version of the client that sends the service request, and the version identifier has a correspondence relationship with a card type supported by the client of the configuration version.
  • Step S22 When it is determined that the configuration version of the client does not support the card type of the first card for displaying the target information according to the card type corresponding to the version identifier, returning the target information and the indication information to the client,
  • the indication information is used to indicate that the client displays the target information and the version upgrade prompt information of the client by using a second card supported by the configured version of the client.
  • the server can generally determine whether the client supports the card type of the first card.
  • the target information and the indication information are returned to the client, and the indication information is used to instruct the client to use the second card.
  • the card type of the first card may be a new card type
  • the second card The card type is the card type supported by the client's configured version. That is to say, the server determines whether the client supports the new card type.
  • the indication information indicates that the client displays the target information by using the supported card type.
  • the server when the server returns the target information and the indication information to the client, the target information and the indication information may be returned to the client in the form of a json (JavaScript Object Notation) character string.
  • json JavaScript Object Notation
  • the indication information indicates that the client displays the target information through the second card and the version upgrade prompt information of the client.
  • the method of the first embodiment can also be used to display the target information through the judgment of the client, thereby reducing the server's Calculation pressure.
  • the server when the server generates a new card type, it usually becomes a card base class (FeedBaseModel), and then generates a new card type through the card base class.
  • the FeedBaseModel can include four basic fields: feedID, type, content, and create time. When a new card type needs to be generated, a corresponding new field is added based on the four basic fields, as shown in FIG.
  • an information display system including a client 401 and a server 402 can be further divided into three levels, namely, a data parsing layer 4011, a card data distribution layer 4012, and a card rendering layer. 4013, where:
  • the server 402 generates card data of the card for displaying the target information according to the service request, and sends the card data to the client 401 in the form of a Json string, and usually maintains a card at the server 402.
  • the updated whitelist makes it possible to determine the type of card that the client 401 can support through the server 402, and generally can also synchronize the whitelist in the client 401 with the whitelist in the server 402;
  • the data parsing layer 4011 parsing the corresponding card type from the card data in the form of a json string delivered by the server 402;
  • the card data distribution layer 4012 analyzes the recognizable card types into corresponding types of cards according to the white list in the client 401, and uniformly analyzes the cards not in the white list into singular cards. Moreover, in practical applications, when the client 401 is just started (or at a specified point in time), the whitelist in the client 401 can also be synchronized with the whitelist maintained in the server 402.
  • the card rendering layer 4013 for rendering the result of the card data distribution layer 4012, rendering a corresponding type of card for display.
  • Embodiment 3 of the present application provides a card-based information display device, which is located at a client.
  • the apparatus 50 includes: a determining unit 501, an associating unit 502, and a displaying unit 503, where:
  • Determining unit 501 determining target information to be displayed and a card type of the first card for displaying the target information
  • the association unit 502 when determining that the configuration version of the client does not support the card type of the first card, determining an association identifier corresponding to the first card, and associating the configuration version supported by the client according to the association identifier Two cards;
  • the displaying unit 503 is configured to display the target information and the version upgrade prompt information of the client by using the second card.
  • the apparatus 50 since the apparatus 50 is based on the same inventive concept as that of the real-time example 1, the problems in the prior art can be solved. Moreover, in practical applications, the device 50 can also achieve other implementation effects by combining specific hardware devices.
  • the client of the device 50 is installed on the mobile terminal. Since the client can display the target information that cannot be displayed by the first card in the prior art through the second card, the user experience of the mobile terminal can be improved, thereby improving The commercial value of the mobile terminal.
  • Embodiment 4 of the present application provides a processing device for information display service, where the device is located at the server.
  • the device 60 includes a receiving unit 601 and a returning unit 602, where:
  • the receiving unit 601 receives a service request for acquiring target information sent by the client, where the service request includes a version identifier for determining a configuration version of the client, and the version identifier and a card supported by the configuration version of the client There is a correspondence between types;
  • the returning unit 602 when determining, according to the card type corresponding to the version identifier, that the configured version of the client does not support the card type of the first card for displaying the target information, returning the target information and the indication information to the client
  • the indication information is used to indicate that the client displays the target information and the version upgrade prompt information of the client by using a second card supported by the configured version of the client.
  • the device 60 since the device 60 adopts the same inventive concept as Embodiment 2, the problems in the prior art can be solved.
  • the device 60 is located at the server end, and determines whether the client can identify the first card through the server. Since the computing capability of the server is stronger than the client, the display speed of the target information can be improved.
  • the returning unit 602 when the returning unit 602 returns the target information and the indication information to the client, the target information and the indication information may be returned to the client in the form of a json string.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (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 disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Business, Economics & Management (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Artificial Intelligence (AREA)
  • Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请公开了基于卡片的信息展示方法、信息展示业务的处理方法及装置。该基于卡片的信息展示方法包括：确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。从而解决了现有技术中不升级客户端的配置版本，无法展示新的卡片类型的问题。

Description

基于卡片的信息展示方法、信息展示业务的处理方法及装置
本申请要求2016年08月03日递交的申请号为201610630286.0、发明名称为“基于卡片的信息展示方法、信息展示业务的处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及基于卡片的信息展示方法、信息展示业务的处理方法及装置。
背景技术
随着互联网的蓬勃发展，越来越多的应用APP采用卡片流(Feed流)的形式向用户进行信息展示。在通过Feed流进行信息展示的过程中，根据所要展示的信息类型的不同，通常将所要展示的信息配置为不同的类型的卡片。
然而，随着应用APP版本的不断更新，在新版本中通常会出现新的卡片类型。当用户所使用的应用APP版本未更新时，这些新类型的卡片将无法在该用户所使用的应用APP中展示。
针对应用APP无法对新类型的卡片进行展示的情况，通常通过引导用户执行应用APP版本更新的操作进行处理。当用户通过引导进行应用APP的版本更新后，将在该用户所使用的应用APP中展示该新类型的卡片。
然而，通过更新应用APP的版本实现新类型的卡片在应用APP中的展示这一方法存在：在应用APP服务器出现繁忙等情况导致应用APP更新失败时，依然无法对该新类型的卡片进行展示，使得用户对该应用APP的使用体验降低。
发明内容
本申请实施例提供基于卡片的信息展示方法、信息展示业务的处理方法及装置，用于解决现有技术中的问题。
本申请实施例提供了一种基于卡片的信息展示方法，该方法包括：
确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；
当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；
利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
优选的，若所述客户端包含白名单，所述白名单中包含所述客户端的配置版本所支持的卡片类型；则
确定客户端的配置版本是否支持所述第一卡片的卡片类型，具体包括：
将所述第一卡片的卡片类型与所述白名单中包含的卡片类型进行匹配；
根据匹配结果，确定所述客户端的配置版本是否支持所述第一卡片的卡片类型。
优选的，若所述客户端中包含所述客户端的配置版本的版本标识与所述配置版本所支持的卡片类型之间的对应关系；
确定客户端的配置版本是否支持所述第一卡片的卡片类型，具体包括：
确定所述客户端的配置版本的版本标识，并根据所述对应关系确定所述版本标识对应的配置版本所支持的卡片类型；
根据所述第一卡片的卡片类型和所确定的所述客户端的配置版本所支持的卡片类型，确定所述客户端的配置版本是否支持所述第一卡片的卡片类型。
优选的，根据所述关联标识关联所述客户端的配置版本所支持的第二卡片，包括：
根据所述关联标识，确定与所述第一卡片关联的第二卡片的卡片数据；
根据所述卡片数据，确定所述客户端的配置版本所支持的第二卡片。
优选的，确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型具体包括：从客户端的缓存数据获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；或
从服务端获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型。
优选的，当从服务端获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型时，所述方法还包括：从服务端获取并缓存所述客户端的配置版本所支持的第二卡片；则，
根据所述关联标识关联所述客户端的配置版本所支持的第二卡片，具体包括：根据所述关联标识关联已缓存的所述第二卡片。
本申请实施例还提供一种信息展示业务的处理方法，该方法包括：
接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系；
当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所 述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
优选的，所述向所述客户端返回目标信息以及指示信息具体包括：以json字符串的形式向所述客户端返回目标信息以及指示信息。
本申请实施例还提供一种基于卡片的信息展示装置，所述装置位于客户端，包括：确定单元、关联单元以及展示单元，其中：
确定单元，确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；
关联单元，当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；
展示单元，利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
本申请实施例还提供一种信息展示业务的处理装置，所述装置位于服务端，包括：接收单元以及返回单元，其中：
接收单元，接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系；
返回单元，当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
本申请实施例采用的上述至少一个技术方案能够达到以下有益效果：
当确定客户端的配置版本不支持述第一卡片的卡片类型时，通过第一卡片中的关联标识关联该配置版本所支持的第二卡片，利用该第二卡片展示目标信息和客户端的版本升级提示信息，从而解决了现有技术中不升级客户端的配置版本，无法展示新的卡片类型的问题。另外，还可以将第二卡片的卡片类型统一配置为多个配置版本均支持的卡片类型，这样当确定客户端不支持某个类型的卡片后，通过该统一类型的卡片进行展示，使得所展示的卡片更加易于管理。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例1提供的一种基于卡片的信息展示方法的具体实现流程示意图；
图2为本申请实施例1提供的实际应用中的一种奇点卡片的示意图；
图3为本申请实施例2提供的一种信息展示业务的处理方法的具体实现流程示意图；
图4为本申请实施例2提供的实际应用中通过卡片基类生成卡片类型的示意图；
图5为本申请实施例2提供的实际应用中的一种信息展示系统；
图6为本申请实施例3提供的一种基于卡片的信息展示装置的具体结构示意图；
图7为本申请实施例4提供的一种信息展示业务的处理装置的具体结构示意图。
具体实施方式
如上所述，随着互联网的蓬勃发展，越来越多的应用APP采用卡片流(Feed流)的形式向用户进行信息展示。在通过Feed流进行信息展示的过程中，根据所要展示的信息类型的不同，通常将所要展示的信息配置为不同的类型的卡片。
例如，微信朋友圈通过Feed流，将好友的状态信息(好友评论、状态更新等)配置为卡片进行展示；微博通过Feed流，将新闻配置为卡片进行展示。由于不同展示信息通常需要的展示形式不同，因此卡片对应有多种不同的类型。例如，股票信息在展示时，通常需要能够显示股票的变化趋势；观点类信息在展示时，通常需要能够评论等，因此，在实际应用中，通常需要配置出多种不同类型的卡片。
随着应用APP版本的不断更新，在新版本中通常会出现新的卡片类型，这些新的卡片类型通常在旧版本中无法进行展示。在现有技术中，当应用APP遇到无法展示的卡片类型时，通常会通过引导用户进行版本更新的形式进行处理。在用户通过引导进行应用APP的版本更新后，能够显示该类型的卡片。
然而，通过更新应用APP的版本实现新类型的卡片在应用APP中的展示这一方法存在：在应用APP服务器出现繁忙等情况导致应用APP更新失败时，依然无法对该新类型的卡片进行展示，使得用户对该应用APP的使用体验降低。
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
以下结合附图，详细说明本申请各实施例提供的技术方案。
实施例1
实施例1提供了一种基于卡片的信息展示方法，该方法用于客户端，能够解决现有技术中的问题。该方法的具体流程示意图如图1所示，包括下述步骤：
步骤S11：接收展示指令。
该客户端通常可以是应用APP的客户端，也可以是网页应用(Web APP)的客户端。
在特定条件下，客户端会接收到展示指令。例如，当指定时间点(上午9点或者其它时间点)到来时，客户端可以接收到展示指令；或者，当服务器需要客户端展示某些信息(广告、资讯信息等)时，会向客户端发送展示指令；或者，根据用户的个人设置，在一定条件下(例如，好友有状态更新)，客户端会接收到展示指令；或者，用户通过触发，使得客户端接收到展示指令，并且通常用户触发的方式可以为鼠标点击的方式、点击触控触摸屏按钮的方式或拉取触控触摸屏的方式等。
以用户刷新微信朋友圈为例，当用户触控触摸屏上的朋友圈按钮时，客户端会接收到展示指令，根据该展示指令能够展示微信好友的状态更新和/或服务端推送的广告等；在微博中，当用户通过拉取等方式刷新微博时，微博的客户端会接收到展示指令，用以展示所关注好友的状态更新、新闻资讯等。
步骤S12：确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型。
目标信息通常可以是新闻资讯、广告资讯、天气预报消息、交通路况消息、基金或股票消息、评论消息、朋友圈的状态消息等。并且，目标信息的展现元素可以为文字、图片、音频和/或视频等。
例如，当用户刷新微信朋友圈时，好友更新后的新的状态消息为待展示的目标信息，该目标信息的展示元素可以包括文字、图片、音频和/或视频等。
通常来说，用于展示目标信息的卡片都有对应的卡片类型，卡片类型反映了卡片的分类类别。例如，观点类的卡片对应观点类的卡片类型(简称，观点卡片)、股票类的卡片对应股票类的卡片类型(简称，股票卡片)，基金类的卡片对应基金类的卡片类型(简称，基金卡片)等，这些不同类型的卡片对应着不同的分类类别。另外，对于客户端来说，不同配置版本的客户端通常能够展示的卡片类型通常不同，客户端的配置版本与能够展示的卡片类型通常具有对应关系。
通常来说，客户端确定目标信息以及第一卡片的卡片类型，可以是获取目标信息以 及第一卡片的卡片类型；并且，通常还可以是从客户端的缓存数据中获取该目标信息以及第一卡片的卡片类型，这种从缓存数据中获取的方式，能够加快卡片展示的响应速度；另外，还可以是从服务端获取该目标信息以及第一卡片的卡片类型。
步骤S13：判断客户端的配置版本是否支持所述第一卡片的卡片类型，若是，则执行步骤S14，若否，则执行步骤S15。
通常来说，在实际应用中，判断客户端的配置版本是否支持第一卡片的卡片类型的方式可以有多种，这里列举几种优选方案：
优选方案一：可以在客户端中配置白名单，在该白名单中记录该客户端的配置版本所支持的卡片类型；则，在判断客户端的配置版本是否支持第一卡片的卡片类型时，可以将第一卡片的卡片类型与该白名单中包含的卡片类型进行匹配，根据匹配结果，判断该客户端的配置版本是否支持所述第一卡片的卡片类型，当匹配成功时，确定该客户端的配置版本支持第一卡片的卡片类型，当匹配失败时，确定该客户端的配置版本不支持第一卡片的卡片类型。
这种通过白名单进行判断的方式，当新增加了该配置版本的客户端支持的卡片类型时，可以对白名单中所记录的卡片类型进行更新，在实际应用中易于实现。
优选方案二：客户端通常会包括配置版本的版本标识，该版本标识能够唯一标识该配置版本的客户端。客户端的配置版本与所支持的卡片类型之间的对应关系，可以体现为版本标识与所支持的卡片类型之间的对应关系。因此，当客户端中包含配置版本的版本标识与该配置版本所支持的卡片类型之间的对应关系时，判断客户端的配置版本是否支持第一卡片的卡片类型，可以先确定该客户端的配置版本的版本标识，并根据该对应关系确定该版本标识对应的配置版本所支持的卡片类型，然后根据第一卡片的卡片类型和所确定的所述客户端的配置版本所支持的卡片类型，确定所述客户端的配置版本是否支持所述第一卡片的卡片类型。
步骤S14：利用所述第一卡片展示所述目标信息。
当确定客户端的配置版本支持所述第一卡片的卡片类型时，可以通过第一卡片展示该目标信息。
步骤S15：确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片，利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
当确定客户端的配置版本不支持所述第一卡片的卡片类型时，可以通过第一卡片对 应的关联标识，关联客户端的配置版本所支持的第二卡片。在这里，所说的第二卡片的卡片类型为该配置版本的客户端支持的卡片类型。
例如，客户端的配置版本为“XYZ”，客户支持的卡片类型为A、B和C，第一卡片的卡片类型为D，当确定该配置版本的客户端不支持第一卡片的卡片类型(D)时，可以通过第一卡片的关联标识，关联卡片类型A、B或C，然后利用A、B或C类型的卡片，展示目标信息以及客户端的版本升级提示信息，这里的A、B或C类型的卡片称之为第二卡片。
需要说明的是，在实际应用中，由于客户端的配置版本经常需要更新，为了使得客户端在确定不支持某个卡片类型时，能够通过同一个卡片类型的卡片进行展示，通常可以将第二卡片的卡片类型设置为多个配置版本均支持的卡片类型。这样可以使得，当客户端确定不支持某个卡片类型的卡片时，通过同一种指定卡片类型的卡片进行展示，这种方式可以方便的对所展示的卡片进行管理。
另外，在步骤S12中提到，当从服务端获取目标信息和第一卡片的卡片类型时，还可以同时从服务端获取第二卡片，并且在获取第二卡片后可以将该第二卡片在客户端进行缓存。这样可以使得，在根据所述关联标识关联所述客户端的配置版本所支持的第二卡片时，可以根据所述关联标识关联已缓存在客户端的第二卡片，从而减少获取第二卡片的时间，提高响应速度。
采用实施例1的该方法，当确定客户端的配置版本不支持述第一卡片的卡片类型时，通过第一卡片中的关联标识关联该配置版本所支持的第二卡片，利用该第二卡片展示目标信息和客户端的版本升级提示信息，从而解决了现有技术中不升级客户端的配置版本，无法展示新的卡片类型的问题。另外，还可以将第二卡片的卡片类型统一配置为多个配置版本均支持的卡片类型，这样当确定客户端不支持某个类型的卡片后，通过该统一类型的卡片进行展示，使得所展示的卡片更加易于管理。
另外，需要说明的是，在通过第二卡片展示目标信息时，还需要同时展示客户端的版本升级提示信息，通过该版本升级提示信息提示用户进行版本升级。在实际应用中，由于用户通常并不清楚客户端出现了新的配置版本，在通过第二卡片展示目标信息时，如果没有同时展示客户端的版本升级提示信息，用户通常并不会对客户端的配置版本进行升级，从而使得用户不能及时体验新配置版本的客户端所带来的体验提升，并且对于提供版本升级服务的公司也会造成业务量损失。
特别的，第一卡片能够展示目标信息(这里称为第一目标信息)，第二卡片能够展 示与第一目标信息对应的第二目标信息，这里的第二目标信息可以与第一目标信息相同，也可以为调整第一目标信息中的对应展示元素后得到的目标信息。可以根据实际需要由第一目标信息确定第二目标信息。
例如，第一目标信息包括文字A以及图片B和图片C，第二目标信息可以为文字A以及图片B和图片C，也可以只为文字A，也可以为文字A以及图片A(或图片B)，也可以为文字A的一部分等。
在实际应用中，客户端从服务端获取的目标信息、第一卡片的卡片类型或关联标识等，通常是以固定的数据格式进行获取。该固定的数据格式，通常由客户端和服务端双方事先定义的协议格式所规定。例如，该协议格式可以如下所示。
将第一卡片的数据抽象成一个FeedViewItem类，并在其中添加一个关联字段(可以形象地称为“奇点字段”或“singular”)，FeedViewItem类图可以如表1所示。
表1：实际应用中的FeedViewItem类
属性 数据类型 说明
feedId String 第一卡片的卡片id
type String 第一卡片的卡片类型
content json 第一卡片的目标信息
create time Long 第一卡片的时间戳
singular json 关联标识
在FeedViewItem类中，通过“type”字段的数据(即第一卡片的卡片类型)，当确定客户端的配置版本不支持第一卡片的卡片类型时，通过“singular”字段的数据(即关联标识)关联第二卡片，以便通过第二卡片(可以形象的称为“奇点卡片”，奇点card)展示目标信息以及客户端的版本升级提示信息。
在实际应用中，也可以将第二卡片(奇点卡片)抽象成一个数据类，该数据类可以如表2所示。
表2：实际应用中奇点卡片的数据类
属性 数据类型 说明
content String 奇点卡片中的目标信息
referenceMap json 目标信息中包含的链接
tip String 奇点卡片中的版本升级提示信息
tipReferenceMap json 版本升级提示信息中包含的链接
clickUrl String 点击奇点卡片跳转的链接
其中，“clickUrl”字段定义了，点击整个奇点卡片时，实现页面跳转的链接；“content”字段定义了，奇点卡片中展示的目标信息；“referenceMap”字段定义了，目标信息中包含的链接，例如下载新的配置版本的链接和/或关联其它用户(例如，@其它用户)的链接等；“tip”字段定义了，奇点卡片中的版本升级提示信息，可以通过该版本升级提示信息提醒用户进行版本升级；“tipReferenceMap”字段定义了，版本升级提示信息中包含的链接，通过该链接通常可以下载新的配置版本。
另外，在程序编写阶段，还可以为各个字段均增加占位符，以便于编写程序，下面是对各个占位符说明：
“U”代表用户名称；“G”代表图片；“S”代表股票；“F”代表基金；“T”代表话题；“V”代表视频；“L”代表链接。
需要说明的是，在将奇点卡片进行展示时，通常还需要根据预设规则约定该奇点卡片中各展示元素(文字、图片、音频、视频等)的大小、颜色、样式、链接地址等。在实际应用中，可以通过构建ReferenceData类来进行约定。该ReferenceData类可以如表3所示。
表3：实际应用中的ReferenceData类
Figure PCTCN2017093786-appb-000001
如图2所示为实际应用中的奇点卡片，在该奇点卡片中，A为奇点卡片中的目标信息(包括文本内容和视频)，由表2中“content”字段确定，并且在A中，有斜体加粗(实际应用中也可以为高亮显示等)部分为目标信息中包含的链接，该链接的地址由表2中“referenceMap”字段确定，另外，斜体加粗的显示样式，斜体加粗显示的起始字符、终止字符分别由表3中“referString”、“matchStart”以及“matchEnd”字段确定；B为奇点卡片中的客户端版本升级提示信息，由表2中“tip”字段确定，并且在B中，有斜体加粗(实际应用中可以为高亮显示等)部分为B中包含的链接，该链接的地址由表2中“tipReferenceMap”字段确定，该链接斜体加粗的显示样式，斜体加粗显示的起始字符、终止字符也分别由表3中“referString”、“matchStart”以及“matchEnd”字段确定；C为整个奇点卡片界面，点击奇点卡片界面进行页面跳转，该页面跳转链接的地址由表2中“clickUrl”字段确定。
实施例2
实施例1所提供的方法用于客户端，在实际应用中，当需要展示目标信息时，通常需要即时地从服务端获取数据。因此，本申请的实施例2将提供一种信息展示业务的处理方法，该方法用于服务端，能够解决现有技术中的问题。该方法的具体流程示意图如图3所示，包括下述步骤：
步骤S21：接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系。
这里的目标信息与步骤S12中的目标信息相同，这里就不再赘述。
该业务请求中包含发送该业务请求的客户端的配置版本的版本标识，该版本标识与该配置版本的客户端所支持的卡片类型具有对应关系。
步骤S22：当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
在实际应用中，通常可以通过服务端来判断客户端是否支持第一卡片的卡片类型，当不支持时，向该客户端返回目标信息以及指示信息，通过该指示信息指示客户端利用第二卡片展示目标信息。通常，该第一卡片的卡片类型可以是新的卡片类型，第二卡片 的卡片类型是该客户端的配置版本支持的卡片类型。也就是说，服务端判断客户端是否支持新的卡片类型，当不支持时，通过指示信息指示客户端利用能够支持的卡片类型展示目标信息。
另外，服务端向客户端返回目标信息以及指示信息时，可以通过json(JavaScript Object Notation)字符串的形式向所述客户端返回目标信息以及指示信息。
采用本申请实施例2所提供的该方法，通过服务端判断客户端的配置版本不支持第一卡片的卡片类型时，通过指示信息指示客户端通过第二卡片展示目标信息以及客户端的版本升级提示信息，从而解决了现有技术中的问题。另外，与实时例1相比，这种通过服务端判断客户端的配置版本是否支持第一卡片的卡片类型的方式，由于服务端的运算能力通常比客户端强，因此能够提高目标信息的展示速度。
需要说明的是，在实际应用中，当服务端的运算压力较大时，通常为了减轻服务端的运算压力，也可以通过实施例1的方法，通过客户端进行判断后展示目标信息，这样减轻服务端的运算压力。
实际应用中，服务端在生成新的卡片类型时，通常先生成一个卡片基类(FeedBaseModel)，再通过该卡片基类来生成新的卡片类型。该FeedBaseModel可以包括feedID、type、content、create time四个基本字段，当需要生成新的卡片类型时，在四个基本字段的基础上增加对应的新的字段，如图4所示。
例如，当需要生成奇点卡片时，在feedID、type、content、create time四个基本字段的基础上增加singular字段；当需要生成观点卡片(CommentFeedModel)时，在feedID、type、content、create time四个基本字段的基础上增加“Comment基字段；当需要生成股票卡片时，在feedID、type、content、create time四个基本字段的基础上增加“Stock段字段；此外，还可以通过对应的方式生成基金卡片(FundFeedModel)、SpecialFeedModel、FootmarkFeedModel等卡片类型。
如图5所示为包括客户端401和服务端402的一种信息展示系统，该系统中客户端401还可以分为三个层级，即数据解析层4011、卡片数据分发层4012以及卡片渲染层4013，其中：
服务端402：根据业务请求，生成用于展示目标信息的卡片的卡片数据，并以Json字符串的形式将卡片数据下发给客户端401，并且在该服务端402通常还可以维护一张可更新的白名单，使得可以通过服务端402来确定客户端401能够支持的卡片类型，并且通常还可以将客户端401中的白名单与服务端402中的白名单进行同步；
数据解析层4011：从服务端402下发的json字符串形式的卡片数据中解析出对应的卡片类型；
卡片数据分发层4012：依照客户端401中的白名单，把能够识别的卡片类型解析成对应的类型的卡片，把不在该白名单内的卡片，统一解析成奇点卡片。并且，在实际应用中，当客户端401刚启动时(或者在指定时间点)，还可以将客户端401中的白名单与服务端402中维护的白名单进行同步。
卡片渲染层4013：用于将卡片数据分发层4012的结果，渲染出对应类型的卡片，进行展示。
实施例3
基于与实施例1相同的发明构思，本申请实施例3提供了一种基于卡片的信息展示装置，所述装置位于客户端。如图6所示，该装置50包括：确定单元501、关联单元502以及展示单元503，其中：
确定单元501，确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；
关联单元502，当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；
展示单元503，利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
采用本申请实施例3所提供的该装置50，由于该装置50基于与实时例1相同的发明构思，因此能够解决现有技术中的问题。并且，在实际应用中，该装置50还可以通过结合具体的硬件设备取得其它的实施效果。例如，将该装置50的客户端安装在移动终端上，由于客户端能够通过第二卡片展示现有技术中通过第一卡片无法展示的目标信息，因此能够提高该移动终端的用户体验，从而提升该移动终端的商业价值。
实施例4
基于与实施例2相同的发明构思，本申请实施例4提供了一种信息展示业务的处理装置，所述装置位于服务端。如图7所示，该装置60包括：接收单元601以及返回单元602，其中：
接收单元601，接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系；
返回单元602，当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
采用本申请实施例4所提供的该装置60，由于该装置60采用与实施例2相同的发明构思，因此能够解决现有技术中的问题。另外，该装置60位于服务端，通过服务端判定客户端是否能识别第一卡片，由于服务端的运算能力强于客户端，因此能够提高目标信息的展示速度。
在实际应用中，通过返回单元602向客户端返回目标信息以及指示信息时，可以以json字符串的形式向所述客户端返回目标信息以及指示信息。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
以上仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替 换、改进等，均应包含在本申请的权利要求范围之内。

Claims (10)

  1. 一种基于卡片的信息展示方法，其特征在于，包括：
    确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；
    当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；
    利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
  2. 如权利要求1所述方法，其特征在于，若所述客户端包含白名单，所述白名单中包含所述客户端的配置版本所支持的卡片类型；则
    确定客户端的配置版本是否支持所述第一卡片的卡片类型，具体包括：
    将所述第一卡片的卡片类型与所述白名单中包含的卡片类型进行匹配；
    根据匹配结果，确定所述客户端的配置版本是否支持所述第一卡片的卡片类型。
  3. 如权利要求1所述方法，其特征在于，若所述客户端中包含所述客户端的配置版本的版本标识与所述配置版本所支持的卡片类型之间的对应关系；
    确定客户端的配置版本是否支持所述第一卡片的卡片类型，具体包括：
    确定所述客户端的配置版本的版本标识，并根据所述对应关系确定所述版本标识对应的配置版本所支持的卡片类型；
    根据所述第一卡片的卡片类型和所确定的所述客户端的配置版本所支持的卡片类型，确定所述客户端的配置版本是否支持所述第一卡片的卡片类型。
  4. 如权利要求1所述方法，其特征在于，根据所述关联标识关联所述客户端的配置版本所支持的第二卡片，包括：
    根据所述关联标识，确定与所述第一卡片关联的第二卡片的卡片数据；
    根据所述卡片数据，确定所述客户端的配置版本所支持的第二卡片。
  5. 如权利要求1所述方法，其特征在于，确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型具体包括：
    从客户端的缓存数据获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；或
    从服务端获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型。
  6. 如权利要求5所述方法，其特征在于，当从服务端获取待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型时，所述方法还包括：
    从服务端获取并缓存所述客户端的配置版本所支持的第二卡片；
    根据所述关联标识关联所述客户端的配置版本所支持的第二卡片，具体包括：
    根据所述关联标识关联已缓存的所述第二卡片。
  7. 一种信息展示业务的处理方法，其特征在于，包括：
    接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系；
    当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
  8. 如权利要求7所述方法，其特征在于，所述向所述客户端返回目标信息以及指示信息具体包括：
    以json字符串的形式向所述客户端返回目标信息以及指示信息。
  9. 一种基于卡片的信息展示装置，其特征在于，所述装置位于客户端，包括：确定单元、关联单元以及展示单元，其中：
    确定单元，确定待展示的目标信息和用于展示所述目标信息的第一卡片的卡片类型；
    关联单元，当确定客户端的配置版本不支持所述第一卡片的卡片类型时，确定所述第一卡片对应的关联标识，并根据所述关联标识关联所述客户端的配置版本所支持的第二卡片；
    展示单元，利用所述第二卡片展示所述目标信息和所述客户端的版本升级提示信息。
  10. 一种信息展示业务的处理装置，其特征在于，所述装置位于服务端，包括：接收单元以及返回单元，其中：
    接收单元，接收客户端发送的获取目标信息的业务请求，所述业务请求中包含用于确定所述客户端的配置版本的版本标识，所述版本标识与所述客户端的配置版本所支持的卡片类型之间具有对应关系；
    返回单元，当根据所述版本标识对应的卡片类型确定所述客户端的配置版本不支持用于展示所述目标信息的第一卡片的卡片类型时，向所述客户端返回目标信息以及指示信息，所述指示信息用于指示所述客户端利用所述客户端的配置版本所支持的第二卡片 展示所述目标信息和所述客户端的版本升级提示信息。
PCT/CN2017/093786 2016-08-03 2017-07-21 基于卡片的信息展示方法、信息展示业务的处理方法及装置 WO2018024116A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
SG11201900826QA SG11201900826QA (en) 2016-08-03 2017-07-21 Card-based information displaying method and apparatus, and information displaying service processing method and apparatus
MYPI2019000483A MY192398A (en) 2016-08-03 2017-07-21 Card-based information displaying method and apparatus, and information displaying service processing method and apparatus
PH12019500216A PH12019500216A1 (en) 2016-08-03 2019-01-29 Card-based information displaying method and apparatus, and information displaying service processing method and apparatus
US16/265,881 US10909314B2 (en) 2016-08-03 2019-02-01 Card-based information displaying method and apparatus, and information displaying service processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610630286.0 2016-08-03
CN201610630286.0A CN106899750A (zh) 2016-08-03 2016-08-03 基于卡片的信息展示方法、信息展示业务的处理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/265,881 Continuation US10909314B2 (en) 2016-08-03 2019-02-01 Card-based information displaying method and apparatus, and information displaying service processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2018024116A1 true WO2018024116A1 (zh) 2018-02-08

Family

ID=59191655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/093786 WO2018024116A1 (zh) 2016-08-03 2017-07-21 基于卡片的信息展示方法、信息展示业务的处理方法及装置

Country Status (7)

Country Link
US (1) US10909314B2 (zh)
CN (1) CN106899750A (zh)
MY (1) MY192398A (zh)
PH (1) PH12019500216A1 (zh)
SG (1) SG11201900826QA (zh)
TW (1) TW201805805A (zh)
WO (1) WO2018024116A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106899750A (zh) 2016-08-03 2017-06-27 阿里巴巴集团控股有限公司 基于卡片的信息展示方法、信息展示业务的处理方法及装置
US10635857B2 (en) * 2017-09-29 2020-04-28 Hewlett Packard Enterprise Development Lp Card system framework
CN109542558B (zh) * 2018-10-31 2021-10-01 爱捷软件开发(深圳)有限公司 看板的信息可视化方法、装置、计算机设备和存储介质
CN111131848A (zh) * 2019-12-24 2020-05-08 支付宝(杭州)信息技术有限公司 一种视频直播数据处理方法、客户端及服务器
CN111143020A (zh) * 2019-12-31 2020-05-12 贵阳货车帮科技有限公司 基于卡片的渲染方法、装置、电子设备及可读存储介质
CN115917512A (zh) * 2020-04-27 2023-04-04 梅特凯股份有限公司 人工智能请求和建议卡
CN112017031B (zh) * 2020-09-01 2023-11-10 中国银行股份有限公司 一种信息推送方法及装置
CN112269613A (zh) * 2020-10-23 2021-01-26 北京金和网络股份有限公司 一种数据展示方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101848368A (zh) * 2010-02-02 2010-09-29 深圳市同洲电子股份有限公司 一种收看数字电视节目的方法、系统及数字电视终端
CN102075528A (zh) * 2010-12-27 2011-05-25 上海聚欣网络科技有限公司 一种播放多种封装格式的网络多媒体文件的方法与设备
US20110173168A1 (en) * 2010-01-12 2011-07-14 Microsoft Corporation Data versioning through data transformations
CN104580375A (zh) * 2014-12-11 2015-04-29 百度在线网络技术（北京）有限公司 确定目标应用的ui样式信息的方法与设备
CN106899750A (zh) * 2016-08-03 2017-06-27 阿里巴巴集团控股有限公司 基于卡片的信息展示方法、信息展示业务的处理方法及装置

Family Cites Families (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7570943B2 (en) * 2002-08-29 2009-08-04 Nokia Corporation System and method for providing context sensitive recommendations to digital services
TWI258104B (en) 2002-12-17 2006-07-11 Je-An Jang Application infa operating system
US8499248B1 (en) 2004-04-29 2013-07-30 Paul Erich Keel Methods and apparatus for managing and exchanging information using information objects
JP2007536634A (ja) 2004-05-04 2007-12-13 フィッシャー−ローズマウント・システムズ・インコーポレーテッド プロセス制御システムのためのサービス指向型アーキテクチャ
US20070043766A1 (en) 2005-08-18 2007-02-22 Nicholas Frank C Method and System for the Creating, Managing, and Delivery of Feed Formatted Content
US7568182B2 (en) 2004-12-20 2009-07-28 Microsoft Corporation Method and system for controlling software to facilitate cross-version collaboration of files
US20130104251A1 (en) 2005-02-01 2013-04-25 Newsilike Media Group, Inc. Security systems and methods for use with structured and unstructured data
US20060230427A1 (en) 2005-03-30 2006-10-12 Gerard Kunkel Method and system of providing user interface
CA2672735A1 (en) 2006-12-13 2008-06-19 Quickplay Media Inc. Mobile media platform
US20130166580A1 (en) 2006-12-13 2013-06-27 Quickplay Media Inc. Media Processor
US8577957B2 (en) 2008-04-01 2013-11-05 Litl Llc System and method for streamlining user interaction with electronic content
CN102053903A (zh) * 2009-10-30 2011-05-11 国际商业机器公司 用于为在线运行程序保存和查询场景数据的方法和系统
US8559176B2 (en) * 2010-07-19 2013-10-15 Panduit Corp. Systems and methods for managing heat generated by electronic equipment in an electronic equipment enclosure
US8532464B2 (en) 2010-11-08 2013-09-10 Deluxe Digital Studios, Inc. Methods and systems for use in controlling playback of content in relation to recorded content
CN102012826A (zh) 2010-11-19 2011-04-13 奇智软件（北京）有限公司 一种软件智能安装/升级的方法及系统
US8756221B2 (en) 2010-12-03 2014-06-17 Salesforce.Com, Inc. Social files
CN102855131B (zh) * 2011-06-30 2016-01-13 国际商业机器公司 用于软件配置管理的装置和方法
US8495612B2 (en) 2011-10-21 2013-07-23 International Business Machines Corporation Systems and methods for upgrading a version of software
CN103166981B (zh) * 2011-12-08 2017-12-12 腾讯科技（深圳）有限公司 一种无线网页转码方法及装置
US8725124B2 (en) 2012-03-05 2014-05-13 Enterproid Hk Ltd Enhanced deployment of applications
US9467723B2 (en) 2012-04-04 2016-10-11 Time Warner Cable Enterprises Llc Apparatus and methods for automated highlight reel creation in a content delivery network
US20140004944A1 (en) * 2012-06-28 2014-01-02 Zynga Inc. Integrating online games with online feeds
US20140195675A1 (en) 2013-01-09 2014-07-10 Giga Entertainment Media Inc. Simultaneous Content Data Streaming And Interaction System
US20160366214A9 (en) * 2013-03-15 2016-12-15 Jean Alexandera Munemann Dual node network system and method
CN104427357A (zh) * 2013-09-04 2015-03-18 中兴通讯股份有限公司 语言种类设置方法和装置
CN105446996A (zh) * 2014-07-16 2016-03-30 阿里巴巴集团控股有限公司 页面展示方法和页面展示系统
US9674244B2 (en) 2014-09-05 2017-06-06 Minerva Project, Inc. System and method for discussion initiation and management in a virtual conference
WO2016057188A1 (en) * 2014-10-09 2016-04-14 Wrap Media, LLC Active receipt wrapped packages accompanying the sale of products and/or services
WO2016057192A1 (en) 2014-10-09 2016-04-14 Wrap Media, LLC Integrating feeds into a package of cards
US9448972B2 (en) 2014-10-09 2016-09-20 Wrap Media, LLC Wrap package of cards supporting transactional advertising
US20160321222A1 (en) * 2014-10-09 2016-11-03 Wrap Media, LLC Card based package for distributing electronic media and services
WO2016081856A1 (en) 2014-11-21 2016-05-26 Whip Networks, Inc. Media management and sharing system
CN104881224A (zh) * 2015-05-18 2015-09-02 百度在线网络技术（北京）有限公司 一种卡片的添加方法及装置
CN104965813B (zh) * 2015-06-23 2018-06-26 百度在线网络技术（北京）有限公司 文字素材的处理方法和装置
US20170010790A1 (en) * 2015-07-09 2017-01-12 Quixey, Inc. Multi-State Card Sharing Button
US9959558B2 (en) * 2015-08-18 2018-05-01 Samsung Electronics Co., Ltd. Application cards as advertisements
US10353534B2 (en) * 2016-05-13 2019-07-16 Sap Se Overview page in multi application user interface
US11687703B2 (en) * 2016-12-30 2023-06-27 Dropbox, Inc. Shortcut to move a selection into a new document
JP6407400B1 (ja) * 2017-12-26 2018-10-17 Tdk株式会社 積層コイル部品

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110173168A1 (en) * 2010-01-12 2011-07-14 Microsoft Corporation Data versioning through data transformations
CN101848368A (zh) * 2010-02-02 2010-09-29 深圳市同洲电子股份有限公司 一种收看数字电视节目的方法、系统及数字电视终端
CN102075528A (zh) * 2010-12-27 2011-05-25 上海聚欣网络科技有限公司 一种播放多种封装格式的网络多媒体文件的方法与设备
CN104580375A (zh) * 2014-12-11 2015-04-29 百度在线网络技术（北京）有限公司 确定目标应用的ui样式信息的方法与设备
CN106899750A (zh) * 2016-08-03 2017-06-27 阿里巴巴集团控股有限公司 基于卡片的信息展示方法、信息展示业务的处理方法及装置

Also Published As

Publication number Publication date
US20190171699A1 (en) 2019-06-06
PH12019500216A1 (en) 2019-07-01
TW201805805A (zh) 2018-02-16
SG11201900826QA (en) 2019-02-27
US10909314B2 (en) 2021-02-02
CN106899750A (zh) 2017-06-27
MY192398A (en) 2022-08-19

Similar Documents

Publication Publication Date Title
WO2018024116A1 (zh) 基于卡片的信息展示方法、信息展示业务的处理方法及装置
US10326715B2 (en) System and method for updating information in an instant messaging application
EP3172680B1 (en) Fast rendering of websites containing dynamic content and stale content
US20190122311A1 (en) Offline content sharing
US11743348B2 (en) Custom digital components
WO2017114182A1 (zh) 界面展示数据的方法及装置
WO2016026384A1 (zh) 一种客户端页面显示方法、装置及系统
WO2018040913A1 (zh) 一种界面展示方法及装置
US9787783B2 (en) Providing supplemental content in relation to embedded media
US8516041B1 (en) Pre-fetching asynchronously requested content
KR20140018276A (ko) 복수의 동적 아이콘 패널을 업데이트하기 위한 푸시 알림
WO2017121278A1 (zh) 信息推送装置、方法、客户端及机器可读存储介质
US11095598B2 (en) Managing messaging services
US20160182606A1 (en) Network Based Static Font Subset Management
US20100058167A1 (en) Displaying Subscribable Content
US20150365497A1 (en) Providing access to information across multiple computing devices
US10506400B2 (en) Data download method and apparatus
US8930443B1 (en) Distributed network page generation
CN111292049A (zh) 任务生成方法及装置
WO2015158262A1 (zh) 发送卡券、生成卡券的方法、公众账号服务端和移动终端
TWI680657B (zh) 一種微信ｈ５傳播監測分析方法及相關設備
US11068853B2 (en) Providing calendar utility to capture calendar event
US20200201929A1 (en) Managing Multi-Dimensional Array Of Data Definitions
US20190095542A1 (en) Method and system of dynamic website creation through url parameter analysis
WO2017024976A1 (zh) 实时信息的展现方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17836298

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17836298

Country of ref document: EP

Kind code of ref document: A1