CN115996215A

CN115996215A - Method and device for pushing real-time data

Info

Publication number: CN115996215A
Application number: CN202111176054.XA
Authority: CN
Inventors: 苟亚明
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-10-09
Filing date: 2021-10-09
Publication date: 2023-04-21

Abstract

The embodiment of the application provides a method and a device for pushing real-time data, wherein the method comprises the following steps: the method comprises the steps of receiving a data transmission message, wherein the data transmission message comprises a live broadcast data stream and first information, the first information is packaged at the head of the data transmission message, and the first information is used for describing recommended data; and acquiring the recommended data according to the first information. According to the embodiment of the invention, the first information for describing the recommended data is packaged at the head of the data transmission message, so that the data pushing does not need customized development, the timeliness of pushing the data is improved, and the data pushing cost is reduced.

Description

Method and device for pushing real-time data

Technical Field

The embodiment of the application relates to the technical field of Internet, in particular to a method and a device for pushing real-time data.

Background

With the rapid development of internet technology, internet live broadcast has become a current trend. In general, the anchor terminal may push live data to the server and then the viewer terminal pulls live data from the server. In the live broadcast process, the anchor terminal can recommend the item information to the audience terminal, and the corresponding audience terminal can display the recommended item information.

During push-pull streaming of live data, data transfer protocols such as Real-time messaging protocol (Real Time Messaging Protocol, RTMP), web instant messaging (Web Real-Time Communication, webRTC), and proprietary protocols encapsulated based on user datagram protocol (User Datagram Protocol, UDP) may be employed to transfer streaming media data. When the recommended items in the live scenario include financial products, the data transfer is typically via an extensible messaging and presence protocol (Extensible Messaging and Presence Protocol, XMPP), or hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP), since the financial products do not belong to streaming media data. Therefore, the pushing of data of financial products requires customized development, and the cost is high. Therefore, a low cost data push solution is needed.

Disclosure of Invention

The embodiment of the application provides a method and a device for pushing real-time data, which enable pushing of the data to be free from customized development by packaging first information for describing recommended data at the head of a data transmission message, thereby being beneficial to improving timeliness of pushing the data and reducing cost of pushing the data.

In a first aspect, an embodiment of the present application provides a method for pushing real-time data, where the method includes:

the method comprises the steps of receiving a data transmission message, wherein the data transmission message comprises a live broadcast data stream and first information, the first information is packaged at the head of the data transmission message, and the first information is used for describing recommended data;

and acquiring the recommended data according to the first information.

In some alternative embodiments, the method may be performed by a first device that may receive a data transfer message from a second device.

Optionally, the first device comprises an audience terminal and the second device comprises a server. Alternatively, the first device includes a server, and the second device includes a anchor terminal, without limitation.

In some alternative embodiments, the method further comprises: and sending the recommended data according to the first information, for example, the recommended data can be sent to a third device.

In some alternative embodiments, the third device comprises an audience terminal when the first device comprises a server and the second device comprises a anchor terminal.

In some alternative embodiments, the recommended data includes financial products.

In a second aspect, embodiments of the present application provide a method for pushing real-time data, including:

acquiring recommended data;

determining first information, wherein the first information is used for describing the recommended data;

and sending a data transmission message, wherein the data transmission message comprises a live broadcast data stream and the first information, and the first information is encapsulated at the head of the data transmission message.

In some alternative embodiments, the method may be performed by a second device, which may send the data transfer message to the first device.

In a third aspect, an apparatus for pushing real-time data is provided, including:

the receiving and transmitting unit is used for receiving a data transmission message, wherein the data transmission message comprises a live broadcast data stream and first information, the first information is packaged at the head of the data transmission message, and the first information is used for describing recommended data;

and the processing unit is used for acquiring the recommended data according to the first information.

In a fourth aspect, an apparatus for real-time data push is provided, including:

an acquisition unit configured to acquire recommended data;

a processing unit for determining first information describing the recommended data;

the receiving and transmitting unit is used for transmitting a data transmission message, the data transmission message comprises a live broadcast data stream and the first information, and the first information is packaged at the head of the data transmission message.

In a fifth aspect, there is provided an electronic device, comprising: a processor and a memory;

the memory is used for storing a computer program;

the processor is configured to execute the computer program to implement the method described above.

In a sixth aspect, a chip is provided, including: a processor for calling and running a computer program from the memory, causing the device on which the chip is mounted to perform the method as described above.

In a seventh aspect, there is provided a computer readable storage medium comprising computer instructions which, when executed by a computer, cause the computer to implement a method as previously described.

In an eighth aspect, there is provided a computer program product comprising computer program instructions which, when run on a computer, cause the computer to perform the method as described above.

According to the embodiment of the application, the first information for describing the recommended data is packaged at the head of the data transmission message, namely, the first information is pushed by adopting the same data transmission protocol as the live data stream, so that customized development is not needed to realize the pushing of the real-time data, on one hand, the timeliness of pushing the data can be improved, and on the other hand, the cost of pushing the real-time data can be reduced.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic diagram of a system architecture suitable for use in embodiments of the present application;

FIG. 2 is a schematic flow chart of a live method provided in an embodiment of the present application;

fig. 3 is an example of a display interface of a hosting terminal provided in an embodiment of the present application;

fig. 4 is another example of a display interface of a hosting terminal provided in an embodiment of the present application;

FIG. 5 is an example of an RTMP message provided by an embodiment of the present application;

FIG. 6 is an example of parsed index information provided by an embodiment of the present application;

FIG. 7 is an example of an actor-cache pool list provided by an embodiment of the present application;

FIG. 8 is a schematic block diagram of an apparatus for real-time data pushing provided in an embodiment of the present application;

FIG. 9 is a schematic block diagram of another apparatus for real-time data pushing provided by an embodiment of the present application;

fig. 10 is a schematic block diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be understood that in the embodiments of the present application, "B corresponding to a" means that B is associated with a. In one implementation, B may be determined from a. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

In the description of the present application, unless otherwise indicated, "at least one" means one or more, and "a plurality" means two or more.

In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

In order to facilitate understanding of the embodiments of the present application, the following brief description will be first given to related concepts related to the embodiments of the present application:

live broadcast plug flow: the method refers to a process of transmitting the packaged content in the acquisition stage to a server, namely, a process of transmitting an on-site audio and video signal to a network. Specifically, the collected audio and video content may be encoded, and the encoded audio and video content may be uploaded to a server based on a specific data transmission protocol.

Live broadcast stream pulling: the method refers to a process of pulling live broadcast content existing in a server by using a designated address, namely, a process of transmitting audio and video signals on a network to a playing end. Specifically, the audio and video content can be pulled from the server based on a specific data transmission protocol, and decoded and played.

By way of example, data transfer protocols such as RTMP, webRTC, UDP encapsulation-based proprietary protocols, and the like are not limited.

Financial product data (FinancialProductData, FPD): and (5) indicating a financial product data structure in the live broadcast scene. The financial products include securities, funds, stocks, options, combinations thereof, and the like, without limitation. The FPD may include at least one of identification ID, name, minimum amount, annual rate, landing page uniform resource locator (Uniform Resource Locator, URL) and time limit of the financial product. Complete financial products require well-configured FPDs. In the embodiment of the application, the anchor terminal side and the server side can be configured to package unified FPDs.

RTMP, based on the Transmission control protocol (Transmission Control Protocol, TCP), is a family of protocols that includes variations of the RTMP base protocol and RTMPT/RTMPS/RTMPE. RTMP is a network protocol designed for real-time data communication, and is mainly used for audio-video and data communication between Flash/AIR platform and streaming media/interactive server supporting RTMP protocol. In the embodiment of the application, information for indicating a financial product or an FPD is transmitted in an RTMP protocol header.

an actor object: an actor object refers to a most basic computational unit. It can receive the message and perform calculations based thereon. And the actor object is stateful, either self-controlling or by the sender of the message. In the embodiment of the present application, the actor object is associated with recommended data, for example, a financial product (such as an FPD of the financial product), and the sending of the recommended data, for example, the data of the financial product (such as the data in the FPD) may be controlled by controlling the state of the actor object to be the execution state.

The application scenarios to which the technical solution of the embodiment of the present application may be applied will be described in some simple ways. Fig. 1 is a schematic diagram of a network system to which the embodiments of the present application are applicable. As shown in fig. 1, the system includes at least one anchor terminal 101 (1 in fig. 1 for example), at least one viewer terminal 102 (3 in fig. 1 for example), and a server 103. Wherein the anchor terminal 101, the audience terminal 102 and the server may be connected by a wireless or wired network. By way of example, the anchor terminal 101 or the audience terminal 102 may include a computer, a mobile phone, a tablet phone, a smart television, or other terminals, and the server 103 may be a background server, or a cloud server that provides cloud computing or cloud storage services, which is not limited in this application.

In the embodiments of the present application, the anchor terminal and the audience terminal are taken as examples to distinguish the terminals implementing the live broadcasting method of the embodiments of the present application, but the embodiments of the present application are not limited thereto, and for example, the anchor terminal may also be referred to as a first terminal, the audience terminal may also be referred to as a second terminal, or others.

By way of example, an application may be installed on the anchor terminal 101 or the audience terminal 102, and the anchor terminal 101 or the audience terminal 102 may implement functions such as data transmission, message interaction, and the like through the server 103 through the application. Alternatively, the application may be an application in an operating system, or an application provided by a third party, without limitation. For example, the application may be a live application having live video functionality. Alternatively, the live application may have other functions, such as a shopping function, a music function, a game function, etc., which are not limited in this application.

It should be noted that the application scenario described above is only for illustrating the embodiments of the present application and is not limiting. In specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs. For example, the embodiment of the application may also be applied to a scenario of targeted message pushing, or advertisement pushing, without limitation.

In a live broadcast scene, the anchor terminal 101 and the audience terminal 102 can log in a live broadcast application program based on an account, the corresponding anchor terminal 101 uses the live broadcast application program to carry out live broadcast, the collected live broadcast content push stream is uploaded to the server 103 to realize live broadcast push stream, and the audience terminal 102 pulls the live broadcast content from the server 103 through the live broadcast application to realize live broadcast pull stream. During the live broadcast, the anchor terminal 101 may push real-time data, such as data of recommended items in the live broadcast, data of financial products, etc., to the viewer terminal 102, without limitation. Currently, in the case of recommended articles including financial products, development of customization is required, for example, data transmission is performed through XMPP or HTTP protocol, and maintenance cost is high.

In view of this, an embodiment of the present application provides a method for pushing real-time data, where in the method, first information may be encapsulated in a data transmission packet (for example, a header) including a live data stream, where the first information is used to describe recommended data, so as to implement pushing of the real-time data. Because the embodiment of the application encapsulates the first information for describing the recommended data in the data transmission message (such as the header), the real-time data pushing can be realized without customized development, so that on one hand, the timeliness of pushing the data can be improved, and on the other hand, the cost of data pushing can be reduced.

The recommended data is, for example, but not limited to, an item recommended in a live broadcast process (such as a financial product), or an advertisement message, or a targeting message, etc.

Fig. 2 shows a schematic flow chart of a method 200 for real-time data pushing according to an embodiment of the present application. The anchor terminal in the method 200 may be, for example, the anchor terminal 101 in fig. 1, the audience terminal may be, for example, the audience terminal 102 in fig. 1, and the server may be, for example, the server 103 in fig. 1, without limitation. As shown in fig. 2, method 200 includes steps 210 through 250.

And 210, acquiring recommended data by the anchor terminal.

For example, during the live broadcast, a host (an example of a user) at the host terminal side may operate the host terminal in real time to input a pushed (recommended) product according to the content of the current live broadcast explanation, or preset the pushed product by operating the host terminal before the start of the broadcast. And responding to the operation of the anchor, and acquiring the recommended product by the anchor terminal. As one example, the item recommended by the anchor may include a financial product, at which point the recommended data includes the financial product.

In some alternative embodiments, when the recommended data includes a financial product, the anchor terminal may display the financial product according to the FPD of the recommended financial product. And then, acquiring a pushing instruction input by a user through the first input area, wherein the pushing instruction is used for indicating to push the financial product. Based on the push instruction, the anchor terminal may determine to recommend the financial product. Optionally, the anchor terminal may display the first input area on the interface, and the corresponding user may input the push instruction by clicking or touching the first input area.

As shown in table 1, the FPD may include at least one of identification ID, name, minimum amount, annual rate, landing page uniform resource locator (Uniform Resource Locator, URL) and time limit of the financial product.

TABLE 1

Field name	Description of the invention
		productID	Product ID
productName	Product name
		minAmount	Minimum amount of money
rateOfYear	Annual rate of interest
		deatailUrl	Floor page Url
timeLimit	Time limitation

Fig. 3 shows an example of a display interface of a anchor terminal. As shown in fig. 3, the anchor terminal may display at least one (2 in fig. 3) financial product according to the pre-stored FPD, for example, may display data of each financial product, such as information of product name, minimum amount, annual rate, time limit, etc. Optionally, the anchor terminal may also display a "push" button (i.e., one example of an input area) for each financial product. When a financial product is recommended by the anchor, the "push" button corresponding to the financial product may be clicked or touched. In response to clicking or touching the push button, the anchor terminal may obtain a push instruction, and determine that the financial product corresponding to the push button is a recommended financial product.

As one possible implementation, the anchor terminal may have a built-in create FPD tool (tool). When the anchor terminal is about to begin live, or during the live process, the FPD may be constructed, or modified based on creating the FPDtool. Illustratively, as shown in FIG. 4, creating the FPDtool may display the names of the plurality of associated products, and/or other information of the financial product, such as minimum amount, annual rate, time limit, risk level, etc., to the anchor terminal via an interface. A user (e.g., a host) may select one or more financial products from the plurality of associated products (e.g., a shanxi security ultrashort bond C is selected in fig. 4). In response to a user selection, creating an FPDtool creates an FPD for the financial product.

In some alternative embodiments, the anchor may input the time, type, recipient group, etc. of the push data. For example, the anchor may enter event or time information to indicate the time, type, or group of recipients that push the data. Accordingly, the anchor terminal may acquire the event or time information. That is, when a certain event(s) or time is (are) reached during the live broadcast, data may be pushed to the viewer terminal. For example, for different audience members, the server will push different data, such as items or financial products, such as those currently being taught by the host.

As an example, the event or time information may include one or more of the following:

1) The user is focused on the anchor (i.e., the account the user is logged on the live application of the audience terminal is focused on the account the anchor is logged on the live application of the anchor terminal);

2) The time of watching the live broadcast by the user reaches a certain duration (namely, the time of playing the live broadcast data stream of the anchor terminal by the audience terminal reaches a certain duration);

3) The number of views of the user into the live broadcast reaches a certain amount (i.e. the number of times the live data stream of the anchor terminal is played by the audience terminal)

4) A certain point in time is reached.

220, the anchor terminal obtains the first information.

The first information is used to describe recommended data, that is, recommended data obtained in step 210, which may be, for example, an article or a financial product.

In some alternative embodiments, the first information includes at least one of type information, time information, and service information of the recommended data. Wherein the type information may be used to indicate a type of the recommended data, the time information may be used to indicate a valid period of the recommended data, and the service information may be used to indicate service contents of the recommended data.

Illustratively, when the recommended data includes a financial product, the type of financial product includes securities, funds, stocks, options, combinations thereof, or the like. As one example, the type information may include data communication protocol information, wherein the data communication protocol information corresponds to a type of recommended data. For example, when the type information transmitted starts with codeM:// v17, the recommended financial product is a security.

For example, when the recommended data includes a financial product, the business information may indicate data of the financial product, such as an FPD. As a specific example, the business information may include at least one of ID, name, or index of a financial product (or FPD), without limitation.

In some alternative embodiments, the anchor terminal may further obtain a public key issued by the server, and encrypt the first information according to the public key. That is, the first information may be information after being encrypted. Alternatively, the anchor terminal may obtain the public key issued by the server in advance and store the public key.

As an example, the anchor terminal may encrypt an index of financial product data, such as a 2-bit 16-ary data, by means of a Hash-message authentication code (Hash-based Message Authentication Code, HMAC), to generate a string and index information (index msg). By way of example, the string may be 64 bits in length, as this application is not limited in this regard. At this time, the character string and the index information may be regarded as the first information. According to the method and the device for pushing the financial product, the first information is obtained by encrypting the data of the financial product, and the safety and reliability of pushing the financial product can be further improved.

In some alternative embodiments, the anchor terminal may also obtain second information indicating a condition that triggers the server to push the financial product to the audience terminal. The second information may be, for example, the event or time information described above. That is, when the condition, or time, or event indicated by the second information is satisfied, the server pushes the corresponding financial product to the viewer terminal.

And 230, the anchor terminal sends a data transmission message to the server. Here, the data transmission message is a push data message encapsulated according to a data stream transmission protocol.

The data transmission message comprises a live broadcast data stream and the first information, and the first information is encapsulated at the head of the data transmission message. As an example, when the data transmission packet is an RTMP packet, the first information may be encapsulated in a basic header (basic header) and/or a message header (message header), for example, may be encapsulated in an extensible field in the basic header or the message header, without limitation.

In some embodiments, the data may be formatted into an RTMP message (message) when the RTMP protocol is transmitted. In actual transmission, the sending end divides the message into blocks (chunk) with message IDs, and each chunk may be a separate message or may be a part of the message. The receiving end can restore the chunk into a complete message according to the message ID contained in the chunk, so as to realize the information receiving and transmitting.

Fig. 5 shows an example of a format (chunk format) of a chunk, in which one chunk includes a chunk header (chunk header) and chunk data (chunk data), and the chunk header includes a basic header, a message header, and an extended timestamp (extendedtimestamp). In some alternative embodiments, the first information may be encapsulated in a basic loader in a chunkloader, or a messageloader, which is not limited in this application.

As an example, when the first information includes index information, the index information may be encapsulated in a basic header in the chunk header and the character string may be placed in a message header in the chunk header when the character string and the index information are encrypted by the HMAC method.

In some alternative embodiments, the data transfer message may also include second information. For example, the second information may be encapsulated in a header of the data transmission packet, such as a basic header or a message header of the RTMP protocol packet, which is not limited, and may be specifically described with reference to the first information. As a specific example, the second information may be encapsulated with the first information in an adjacent field, which is not limited.

Correspondingly, the server receives the data transmission message and acquires the first information from the data transmission message. For example, after receiving the data transmission message, the server may check the header of the message to obtain the first information. Optionally, the server may also check the header of the message to obtain the second information.

In some alternative embodiments, when the index information is encapsulated in a basic header in the chunk header, and the character string is placed in a message header in the chunk header, the index information in the basic header and the character string in the message header of the data transmission packet may be checked, and the index information may be parsed according to the HMAC algorithm by the character string, so as to obtain the parsed index information as the first information.

And 240, the server acquires recommended data according to the first information.

For example, the server may acquire the recommended data according to at least one of type information, time information, and service information included in the first information.

As a specific example, when the type information includes data communication protocol information, for example, beginning with code M:// v17, the receiving end (such as a server) parses the first information according to the product type (for example, security type) corresponding to the agreed protocol information (i.e., code M:// v 17) to determine the recommended financial product.

As another specific example, when the service information may be used to indicate the FPD, for example, at least one of ID, name, or index of the FPD may be included. At this time, the server may determine the FPD of the recommended financial product according to the service information.

As a specific example, fig. 6 shows one example of index information. Here, the first information includes index information composed of 6-bit 16-ary data, which may be used to indicate recommended financial products. Illustratively, the index value of the first 2 bits of the 6-bit 16-ary data may be used to indicate the FPD of the financial product. For example, the server may store a correspondence between the index value and the FPD, and when the first 2 bits of the index information are analyzed, the FPD may be determined from the correspondence.

In some alternative embodiments, the server may also distribute the recommended data to different hosts on the server side for service processing according to the service information. For example, when it is determined that the recommended financial product corresponds to the first FPD according to the service information, the first FPD is allocated to the host B to perform service processing, for example, the recommended first FPD is acquired by the host B, and data of the first FPD is transmitted to the viewer terminal.

In some specific implementations of the present application, a data transmission protocol or transmission format may be defined between the anchor terminal and the server, which may correspond to different data types. For example, for securities-like financial products, a transmission protocol or transmission format of codeM:// v17 may be defined. For example, a parser may be built in the server to parse information sent by the anchor terminal for describing the recommended product, where the parser confirms the communication protocol of the anchor terminal and the encapsulation format of the data when the anchor terminal and the server establish a push connection. After receiving the information for describing the recommended product, the server can analyze the data according to the agreed protocol format to obtain the recommended data. Specifically, the parsing process may be referred to the above description, and will not be repeated.

The server sends the recommended data to the viewer terminal 250.

For example, when the recommended data is a financial product, the server may transmit the data of the financial product to the viewer terminal according to the first information. Accordingly, the audience terminal receives the data of the financial product, and further the financial product can be displayed on a screen of the audience terminal, so that the audience is helped to know the products regularly taught by the anchor in real time.

Therefore, in the embodiment of the application, the first information for describing the recommended data is encapsulated at the head of the data transmission message, namely, the first information is pushed by adopting the same data transmission protocol as the live data stream, so that customized development is not needed to realize the pushing of the real-time data, on one hand, the timeliness of pushing the data can be improved, and on the other hand, the cost of pushing the real-time data can be reduced.

In some alternative embodiments, the server may acquire an actor object associated with the recommended data according to the first information, and then may determine a state of the actor object as an execution state to send the recommended data to the viewer terminal. In some embodiments, an inside of an actor object may hold a status field to identify status information of data associated with the actor object. That is, the state of the recommended data may be controlled according to the state of the actor object, for example, when the actor object is controlled to be in an execution state, the recommended data associated with the actor may be transmitted to the audience terminal.

According to the embodiment of the invention, the actor object is associated with the recommended data, so that the sending state of the recommended data can be controlled by controlling the state of the actor object, and the recommended data is sent to the audience terminal, thereby being beneficial to further improving the timeliness of pushing the data and improving the efficiency of data transmission.

For example, the financial product (e.g., FPD indicated by the business information) described in the first information may be associated with the actor object, and for example, an association relationship between the financial product (or FPD) and the actor object may be pre-stored in the server. The server may determine an actor object according to the first information and the association relationship. Here, the association relationship of the financial product (or FPD) and the actor object, that is, the association relationship of the data of the financial product (or the data contained in the FPD) and the actor object. As a possible implementation, the data of the financial product (or the data contained in the FPD) may be associated in the actor object by an index function, that is, the data of the financial product (or the data of the FPD) associated with the actor object may be acquired through the index function of the actor object. When the actor object is determined to be in an execution state, data of an FPD associated with the actor object is transmitted to the audience terminal.

In some alternative embodiments, the server (e.g., in memory) may maintain a cache pool list, which may contain at least one actor object. When the fact that the data (i.e. recommended data) described by the first information are associated with the actor object is determined to be included in the cache pool list, the state of the actor object is changed from the multiplexing state to the waiting state. In some embodiments, the actor object may also be saved to memory. When the fact that the data (i.e. recommended data) described by the first information are not included in the cache pool list is determined, the fact that the data described by the first information are related to the fact that the fact is related to the data is not included in the cache pool list is established, and the fact that the state of the fact is a waiting state is determined.

For example, as shown in fig. 7, the server may store an actor cache pool list (e.g., may store in the form of an array list), where at least one actor object may be included, e.g., actor_a, actor_b, actor_c, actor_d, etc., where each actor object may correspond to an index value. In addition, the state of each actor object in the actor cache pool is a multiplexing state. Here, the multiplexing state indicates that the actor object has been executed and has not been destroyed. Illustratively, the processing module (e.g., a processor) in the server may obtain the actor object from the actor cache pool list, or store the actor object in the actor cache pool list, and the like, which is not limited.

Referring to fig. 6, when the server receives push data of the anchor terminal and obtains an index value "05" from the push data, an actor object corresponding to "05" may be searched from the actor cache pool. When the actor cache pool list includes an actor object corresponding to "05", for example, an actor_b, the state of the actor_b object is modified from the multiplexing state to the waiting state. Here, the waiting state means that the actor object waits to be executed and has associated data (e.g., data of a financial product). When the actor cache pool list does not comprise an actor object corresponding to '05', establishing an actor object associated with the '05', and determining the state of the actor object as a waiting state.

In some alternative embodiments, in the case where the recommended data includes a financial product, the FPD of the financial product may be obtained from the database according to the first information, and an actor object associated with the FPD may be established. For example, an index field corresponding to the FPD may be determined according to an index function, and then an actor object may be established according to the index field, where the actor object includes the index field. Here, the index function may be a preset function, and is not limited. Optionally, after the actor object is established, the state of the actor may be determined to be a waiting state. In this way, when the state of the actor object is determined to be the execution state, the data in the FPD corresponding to the index field of the actor object may be transmitted to the third device. For example, after the actor object is in the execution state, the data of the corresponding FPD may be obtained in the database according to the index field and the index function in the actor object, and the data in the FPD may be sent.

Continuing with the above example, when the actor object corresponding to "05" is established, the FPD of the financial product corresponding to "05" may be determined first, then the actor object associated with the FPD, for example, index "05", may be established, and the state of the actor may be determined to be the waiting state. For example, an index field corresponding to the FPD corresponding to "05" may be determined according to an index function, and then an actor object including the index field, i.e., an actor object corresponding to "05" may be created. After the actor object is in the execution state, the data of the FPD corresponding to the index "05" may be obtained in the database according to the index field and the index function in the actor object, and the data in the FPD may be sent.

Therefore, according to the embodiment of the application, the information for describing the recommended financial product is packaged at the head part of the data transmission message, namely, the financial product is pushed by adopting the same data transmission protocol as the live data stream, so that customized development is not needed to realize pushing of the financial product, on one hand, the timeliness of pushing the financial product can be improved, and on the other hand, the cost of pushing the financial product can be reduced.

It should be noted that, in the embodiment of the present application, the method provided in the embodiment of the present application is described by taking the case that the first information includes the index of the FPD, that is, the FPD is determined according to the index of the FPD, but the embodiment of the present application is not limited thereto, and for example, the first information may also include the ID, the name, or other information of the FPD.

In some optional embodiments, after determining that the state of the actor object is the execution state, the actor object may also be put into the cache pool list, and the state of the actor object is determined to be the multiplexing state. Therefore, when the recommended data is received again, the actor object associated with the recommended data can be directly obtained from the cache pool list without establishing the actor object, so that the timeliness of pushing the data can be further improved, and the efficiency of data transmission is improved.

In some optional embodiments, when the second information is acquired at the header of the data transmission packet, the data of the financial product may be sent to the audience terminal when it is determined that the condition indicated by the second information is satisfied, for example, the state of the actor object is changed from the waiting state to the executing state, so as to send the data in the actor object to the audience terminal, so that the data may be pushed in a directional manner, and user experience is improved.

In some alternative embodiments, the data of the financial product may be sent to the viewer terminal along with the live pull stream, for example, the server may continue to encapsulate information describing the recommended data in the header of a data transmission message, from which the viewer terminal may obtain the live data stream and the first information, and may further obtain the recommended data from the first information.

Similarly, a data transmission protocol or transmission format may be defined between the server and the viewer terminal. For example, a parser may be built into the viewer terminal for parsing information of data describing the recommendation sent by the server, and the parser may be initialized when the viewer terminal enters the living room. After the initialization is successful, the communication protocol and the data encapsulation format of the two parties can be confirmed when the pull stream connection is established between the server and the audience terminal. After receiving the information for describing the recommended product, the audience terminal can analyze the data according to the agreed protocol format by the analyzer to acquire the recommended data. In particular, the procedure is similar to the procedure of transmitting information describing recommended data between the anchor terminal and the server hereinabove, and reference is made to the description hereinabove.

In some alternative embodiments, the server may also send the data of the financial product to the viewer terminal by pushing by the manufacturer, or by creating a long link from the manufacturer, which is not limited in this application.

The specific embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described in detail. As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be considered as disclosed herein.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Method embodiments of the present application are described above in detail in connection with fig. 1-7, and apparatus embodiments of the present application are described below in connection with fig. 8-10.

Fig. 8 shows a schematic block diagram of an apparatus 400 for real-time data pushing according to an embodiment of the present application. As shown in fig. 8, the apparatus 400 includes a transceiving unit 410 and a processing unit 420.

The transceiver unit 410 is configured to receive a data transmission packet, where the data transmission packet includes a live data stream and first information, the first information is encapsulated in a header of the data transmission packet, and the first information is used to describe recommended data.

And the processing unit 420 is configured to obtain the recommended data according to the first information.

Alternatively, the transceiver unit 410 may be configured to receive a data transmission packet from the second device.

In some embodiments, the apparatus 400 for pushing real-time data may be a server, or a chip or a circuit disposed in the server. At this point, the second device may be a anchor terminal. That is, the push of real-time data can be realized by encapsulating information describing recommended data in the header of a data transmission message between the anchor terminal and the server.

In some embodiments, the apparatus 400 for pushing real-time data may be an audience terminal, or a chip or circuit provided in the audience terminal. At this time, the second device may be a server. That is, the pushing of real-time data between the server and the viewer terminal may be achieved by encapsulating information describing recommended data in the header of the data transmission message.

In some alternative embodiments, the first information includes at least one of type information, time information, and service information of the recommended data.

In some alternative embodiments, the type information includes data communication protocol information, wherein the data communication protocol information corresponds to a type of the recommended data.

In some alternative embodiments, the data transfer message comprises a real-time messaging protocol (RTMP) message, and the first information is encapsulated in a base header or a message header of the RTMP message.

In some alternative embodiments, the transceiver unit 410 is further configured to send the recommended data according to the first information. For example, the recommended data may be sent to a third device. In the case where the first device is a server and the second device is a anchor terminal, the third device is, for example, an audience terminal.

In some alternative embodiments, the transceiver unit 410 is specifically configured to:

acquiring an actor object associated with the recommended data according to the first information;

and determining the state of the actor object as an execution state so as to send the recommended data.

In some optional embodiments, the processing unit 420 is further configured to put the actor object into a cache pool list, and determine that a state of the actor object is a multiplexing state.

In some alternative embodiments, the transceiver unit 410 is specifically configured to: :

when determining that the cache pool list comprises the recommended data-associated actor object, modifying the state of the actor object from a multiplexing state to a waiting state;

when the fact that the recommended data associated actor object is not included in the cache pool list is determined, the recommended data associated actor object is established, and the state of the actor object is determined to be a waiting state.

In some alternative embodiments, where the recommended data includes a financial product, the transceiver unit 410 is specifically configured to: acquiring financial product data FPD from a database according to the first information, wherein the FPD comprises at least one of identification ID, name, minimum amount, annual rate, landing page uniform resource locator URL and time limit of the financial product;

Determining an index field corresponding to the FPD according to an index function;

establishing an actor object associated with the FPD, wherein the actor object comprises the index field;

and determining the state of the actor object as an execution state, so as to send data in the FPD corresponding to the index field of the actor object to the third device.

In some alternative embodiments, the data transmission message further includes second information, the first information being encapsulated in a header of the data transmission message, the second information being used to indicate a condition that triggers the server to push the financial product to the viewer terminal.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus 400 for real-time data recommendation shown in fig. 8 may correspond to a server or an audience terminal performing the method 200 in the embodiment of the present application, and the foregoing and other operations and/or functions of each module in the apparatus 400 are respectively for implementing a corresponding flow executed by the server or the audience terminal in fig. 2, and are not repeated herein for brevity.

Fig. 9 shows a schematic block diagram of an apparatus 600 for real-time data pushing according to an embodiment of the present application. As shown in fig. 9, the apparatus 600 for pushing real-time data includes an acquisition unit 610, a processing unit 620, and a transceiver unit 630.

And an acquisition unit 610 for acquiring recommended data.

The processing unit 620 is configured to determine first information, where the first information is used to describe the recommended data.

The transceiver 630 is configured to send a data transmission packet, where the data transmission packet includes a live data stream and the first information, and the first information is encapsulated in a header of the data transmission packet.

Optionally, the transceiver unit 630 may be configured to send a data transmission packet to the first device.

In some embodiments, the apparatus 600 for pushing real-time data may be a hosting terminal, or a chip or a circuit provided in the hosting terminal. At this time, the first device may be a server. That is, the push of real-time data can be realized by encapsulating information describing recommended data in the header of a data transmission message between the anchor terminal and the server.

In some embodiments, the apparatus 600 for pushing real-time data may be a server, or a chip or a circuit disposed in the server. At this time, the first device may be a viewer terminal. That is, the pushing of real-time data between the server and the viewer terminal may be achieved by encapsulating information describing recommended data in the header of the data transmission message.

In some alternative embodiments, the acquiring unit 610 is specifically configured to:

displaying the financial product according to the recommended financial product data FPD of the financial product, wherein the FPD comprises at least one of identification, name, minimum amount, annual rate, landing page uniform resource locator URL and time limit of the financial product;

acquiring a pushing instruction input by a user through a first input area, wherein the pushing instruction is used for indicating to push the financial product;

and determining to recommend the financial product according to the pushing instruction.

In some alternative embodiments, the data transmission message further includes second information, the second information being encapsulated in a header of the data transmission message, the second information being used to indicate a condition that triggers the server to push the financial product to the viewer terminal.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus 600 for pushing real-time data shown in fig. 9 may correspond to a hosting terminal or a server executing the method 200 in the embodiment of the present application, and the foregoing and other operations and/or functions of each module in the apparatus 600 are respectively for implementing a corresponding flow executed by the hosting terminal or the server in fig. 2, and are not repeated herein for brevity.

The apparatus of the embodiments of the present application are described above in terms of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiments in the embodiments of the present application may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in software, and the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented as a hardware processor or implemented by a combination of hardware and software modules in the processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.

Fig. 10 is a block diagram of an electronic device according to an embodiment of the present application, which may be the server shown in fig. 1, or a hosting terminal, for performing the method for real-time data recommendation described in the foregoing embodiment, and specifically, see the description in the foregoing method embodiment.

The electronic device 800 shown in fig. 10 comprises a memory 801, a processor 802, and a communication interface 803. The memory 801, the processor 802, and the communication interface 803 are communicatively connected to each other. For example, the memory 801, the processor 802, and the communication interface 803 may be connected by a network. Alternatively, the electronic device 800 may also include a bus 804. The memory 801, the processor 802, and the communication interface 803 are communicatively connected to each other through a bus 804. Fig. 10 is an electronic device 800 in which a memory 801, a processor 802, and a communication interface 803 are communicatively connected to each other via a bus 804.

The Memory 801 may be a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a random access Memory (Random Access Memory, RAM). The memory 801 may store a program, and when the program stored in the memory 801 is executed by the processor 802, the processor 802 and the communication interface 803 are used to perform the above-described method.

The processor 802 may employ a general-purpose central processing unit (Central Processing Unit, CPU), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), graphics processor (graphics processing unit, GPU) or one or more integrated circuits.

The processor 802 may also be an integrated circuit chip with signal processing capabilities. In implementation, the methods of the present application may be performed by integrated logic circuitry in hardware or instructions in software in processor 802. The processor 802 described above may also be a general purpose processor, a digital signal processor (digital signal processing, DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 801, and the processor 802 reads information in the memory 801 and combines the hardware thereof to implement the method of the embodiments of the present application.

The communication interface 803 enables communication between the electronic device 800 and other devices or communication networks using a transceiver module such as, but not limited to, a transceiver. For example, data transfer messages may be sent or received through the communication interface 803.

When the electronic device 800 includes a bus 804, the bus 804 may include a path that communicates information between the various components of the electronic device 800 (e.g., memory 801, processor 802, communication interface 803).

There is also provided according to the present application a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the method embodiments described above.

There is also provided in accordance with the present application a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the method of the above-described method embodiments.

In other words, when implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces, in whole or in part, a flow or function consistent with embodiments of the present application. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein. In addition, the method embodiments and the apparatus embodiments may be referred to each other, and the same or corresponding content in different embodiments may be referred to each other, which is not described in detail.

Claims

1. A method of real-time data pushing, comprising:

receiving a data transmission message, wherein the data transmission message comprises a live broadcast data stream and first information, the first information is packaged at the head of the data transmission message, and the first information is used for describing recommended data;

And acquiring the recommended data according to the first information.

2. The method of claim 1, wherein the first information includes at least one of type information, time information, and traffic information of the recommended data;

wherein the type information includes data communication protocol information, wherein the data communication protocol information corresponds to a type of the recommended data.

3. The method according to claim 1 or 2, wherein the data transfer message comprises a real time messaging protocol, RTMP, message, the first information being encapsulated in a basic header or a message header of the RTMP message.

4. A method according to any one of claims 1-3, further comprising:

and sending the recommended data according to the first information.

5. The method of claim 4, wherein the sending the recommended data based on the first information comprises:

6. The method as recited in claim 5, further comprising:

And placing the actor object into a cache pool list, and determining that the state of the actor object is a multiplexing state.

7. The method according to claim 5 or 6, wherein the acquiring the recommended data-associated actor object according to the first information includes:

8. The method of claim 7, wherein, in the case where the recommended data includes a financial product, the creating the recommended data-associated actor object includes:

acquiring financial product data FPD from a database according to the first information, wherein the FPD comprises at least one of identification ID, name, minimum amount, annual rate, landing page uniform resource locator URL and time limit of the financial product;

wherein the determining that the state of the actor object is an execution state, so as to send the recommended data to the third device, includes:

9. The method of any of claims 1-8, wherein the data transfer message further includes second information, the first information being encapsulated in a header of the data transfer message, the second information being indicative of a condition that triggers the server to push the financial product to an audience terminal.

10. A method of real-time data pushing, comprising:

acquiring recommended data;

11. The method of claim 10, wherein the first information includes at least one of type information, time information, and traffic information of the recommended data;

12. The method according to claim 10 or 11, wherein the data transfer message comprises a real time messaging protocol, RTMP, message, the first information being encapsulated in a basic header or a message header of the RTMP message.

13. The method of any of claims 10-12, wherein the obtaining recommended data comprises:

14. The method of any of claims 10-13, wherein the data transfer message further includes second information encapsulated in a header of the data transfer message, the second information indicating a condition that triggers the server to push the financial product to an audience terminal.

15. A device for pushing real-time data, comprising:

16. A device for pushing real-time data, comprising:

an acquisition unit configured to acquire recommended data;

17. An electronic device, comprising: a processor and a memory;

the memory is used for storing a computer program;

the processor for executing the computer program to implement the method of any one of claims 1 to 14.

18. A computer readable storage medium comprising computer instructions which, when executed by a computer, cause the computer to implement the method of any one of claims 1 to 14.

19. A computer program product comprising computer program code which, when run by an electronic device, causes the electronic device to perform the method of any one of claims 1 to 14.